Skip to content

Commit 2ab332d

Browse files
committed
Add date, editor, repo fields and an abstract heading
1 parent eabc13d commit 2ab332d

File tree

1 file changed

+60
-33
lines changed

1 file changed

+60
-33
lines changed

geojson-ld.md

Lines changed: 60 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,35 @@ title: GeoJSON-LD
55

66
# GeoJSON-LD 1.0
77

8+
<dl>
9+
<dt>Date</dt>
10+
<dd>2016-10-14</dd>
11+
<dt>Editor</dt>
12+
<dd>Sean Gillies, Mapbox</dd>
13+
<dt>Repository</dt>
14+
<dd>https://github.com/geojson/geojson-ld</dd>
15+
</dl>
16+
17+
## Abstract
18+
819
A vocabulary and JSON-LD context for GeoJSON
920

1021
GeoJSON-LD 1.0 defines a base context for processing GeoJSON according
1122
to the [JSON-LD](https://www.w3.org/TR/json-ld/) processing model. When
1223
a JSON-LD processor encounters a GeoJSON document with the
1324
`application/geo+json` media type that does not contain a `@context` member, it
1425
may use the context defined here. JSON-LD implementations may add to the
15-
context defined here but MUST NOT override or change the meaning of its terms.
26+
context defined here but must not override or change the meaning of its terms.
27+
28+
## Vocabulary
29+
30+
The GeoJSON-LD 1.0 vocabulary is published at
31+
[http://geojson.org/vocab#](http://geojson.org/vocab#).
32+
33+
## Context
1634

17-
The vocabulary is published at [http://geojson.org/vocab#](http://geojson.org/vocab#) and the context is
18-
published at [http://geojson.org/geojson-context.jsonld](http://geojson.org/geojson-context.jsonld).
35+
The GeoJSON-LD 1.0 context is published at
36+
[http://geojson.org/geojson-context.jsonld](http://geojson.org/geojson-context.jsonld).
1937

2038
## Example
2139

@@ -26,24 +44,8 @@ Pasting the following GeoJSON-LD document
2644
"@context": {
2745
"geojson": "http://geojson.org/vocab#",
2846
"Feature": "geojson:Feature",
29-
"FeatureCollection": "geojson:FeatureCollection",
30-
"GeometryCollection": "geojson:GeometryCollection",
31-
"LineString": "geojson:LineString",
32-
"MultiLineString": "geojson:MultiLineString",
33-
"MultiPoint": "geojson:MultiPoint",
34-
"MultiPolygon": "geojson:MultiPolygon",
3547
"Point": "geojson:Point",
36-
"Polygon": "geojson:Polygon",
37-
"bbox": {
38-
"@container": "@list",
39-
"@id": "geojson:bbox"
40-
},
4148
"coordinates": "geojson:coordinates",
42-
"description": "http://purl.org/dc/terms/description",
43-
"features": {
44-
"@container": "@set",
45-
"@id": "geojson:features"
46-
},
4749
"geometry": "geojson:geometry",
4850
"id": "@id",
4951
"properties": "geojson:properties",
@@ -62,30 +64,55 @@ Pasting the following GeoJSON-LD document
6264
```
6365

6466
into the [JSON-LD Playground](http://json-ld.org/playground/) form yields
65-
the following compacted JSON-LD.
67+
the following JSON-LD in expanded form.
6668

6769
```json
68-
{
69-
"@id": "http://example.com/features/1",
70-
"@type": "http://geojson.org/vocab#Feature",
71-
"http://geojson.org/vocab#geometry": {
72-
"@type": "http://geojson.org/vocab#Point",
73-
"http://geojson.org/vocab#coordinates": [
74-
0,
75-
0
70+
[
71+
{
72+
"http://geojson.org/vocab#geometry": [
73+
{
74+
"http://geojson.org/vocab#coordinates": [
75+
{
76+
"@value": 0
77+
},
78+
{
79+
"@value": 0
80+
}
81+
],
82+
"@type": [
83+
"http://geojson.org/vocab#Point"
84+
]
85+
}
86+
],
87+
"@id": "http://example.com/features/1",
88+
"http://geojson.org/vocab#properties": [
89+
{
90+
"http://purl.org/dc/terms/description": [
91+
{
92+
"@value": "A fictional island in the Gulf of Guinea"
93+
}
94+
],
95+
"http://purl.org/dc/terms/title": [
96+
{
97+
"@value": "Null Island"
98+
}
99+
]
100+
}
101+
],
102+
"@type": [
103+
"http://geojson.org/vocab#Feature"
76104
]
77-
},
78-
"http://geojson.org/vocab#properties": {
79-
"http://purl.org/dc/terms/description": "A fictional island in the Gulf of Guinea",
80-
"http://purl.org/dc/terms/title": "Null Island"
81105
}
82-
}
106+
]
83107
```
84108

85109
## Outstanding issues
86110

87111
Nested GeoJSON coordinate arrays are incompatible with the processing model
88112
of JSON-LD 1.0. There are no current best practices for addressing this issue.
113+
Applications that process GeoJSON as JSON-LD using the GeoJSON-LD 1.0 context
114+
must take extra steps not defined here to ensure that geometric coordinates
115+
are processed appropriately.
89116

90117
## See Also
91118

0 commit comments

Comments
 (0)