app.certified.location
Schema Diff
+1 -1
Compatibility Analysis
Backward Compatible
No changes detected.
1
1
{
2
2
"id": "app.certified.location",
3
3
"defs": {
4
4
"main": {
5
5
"key": "tid",
6
6
"type": "record",
7
7
"record": {
8
8
"type": "object",
9
9
"required": [
10
10
"lpVersion",
11
11
"srs",
12
12
"locationType",
13
13
"location",
14
14
"createdAt"
15
15
],
16
16
"properties": {
17
17
"srs": {
18
18
"type": "string",
19
19
"format": "uri",
20
20
"maxLength": 100,
21
21
"description": "The Spatial Reference System URI (e.g., http://www.opengis.net/def/crs/OGC/1.3/CRS84) that defines the coordinate system."
22
22
},
23
23
"name": {
24
24
"type": "string",
25
25
"maxLength": 1000,
26
26
"description": "Human-readable name for this location (e.g. 'Golden Gate Park', 'San Francisco Bay Area')",
27
27
"maxGraphemes": 100
28
28
},
29
29
"location": {
30
30
"refs": [
31
31
"org.hypercerts.defs#uri",
32
32
"org.hypercerts.defs#smallBlob",
33
33
"#string"
34
34
],
35
35
"type": "union",
36
36
"description": "The location of where the work was performed as a URI, blob, or inline string."
37
37
},
38
38
"createdAt": {
39
39
"type": "string",
40
40
"format": "datetime",
41
41
"description": "Client-declared timestamp when this record was originally created"
42
42
},
43
43
"lpVersion": {
44
44
"type": "string",
45
45
"maxLength": 10,
46
46
"description": "The version of the Location Protocol"
47
47
},
48
48
"description": {
49
49
"type": "string",
50
50
"maxLength": 2000,
51
51
"description": "Additional context about this location, such as its significance to the work or specific boundaries",
52
52
"maxGraphemes": 500
53
53
},
54
54
"locationType": {
55
55
"type": "string",
56
56
"maxLength": 20,
57
-
"description": "An identifier for the format of the location data (e.g., coordinate-decimal, geojson-point). See the Location Protocol spec for the full registry: https://spec.decentralizedgeo.org/specification/location-types/#location-type-registry",
57
+
"description": "An identifier for the format of the location data. Use `geojson-point` for a single GeoJSON Point; use `geojson` as the catch-all for any other GeoJSON geometry (Polygon, MultiPolygon, FeatureCollection, etc.) — the inner payload's own GeoJSON `type` field carries the specifics. Values beyond the known set are permitted; see the Location Protocol spec for the canonical registry: https://spec.decentralizedgeo.org/specification/location-types/#location-type-registry",
58
58
"knownValues": [
59
59
"coordinate-decimal",
60
60
"geojson-point",
61
61
"geojson",
62
62
"h3",
63
63
"geohash",
64
64
"wkt",
65
65
"address",
66
66
"scaledCoordinates"
67
67
]
68
68
}
69
69
}
70
70
},
71
71
"description": "A location reference"
72
72
},
73
73
"string": {
74
74
"type": "object",
75
75
"required": [
76
76
"string"
77
77
],
78
78
"properties": {
79
79
"string": {
80
80
"type": "string",
81
81
"maxLength": 10000,
82
82
"description": "The location string value",
83
83
"maxGraphemes": 1000
84
84
}
85
85
},
86
86
"description": "A location represented as a string, e.g. coordinates or a small GeoJSON string."
87
87
}
88
88
},
89
89
"$type": "com.atproto.lexicon.schema",
90
90
"lexicon": 1
91
91
}