A location reference
tid
Timestamp-based ID
Properties
createdAt
string
datetime
Required
Client-declared timestamp when this record was originally created
description
string
Optional
Additional context about this location, such as its significance to the work or specific boundaries
maxLength: 2000 bytesmaxGraphemes: 500 graphemeslocation
union
Required
The location of where the work was performed as a URI, blob, or inline string.
locationType
string
Required
An identifier for the format of the location data. Use `country-code` for uppercase ISO 3166-1 alpha-2 codes in `location.string` (e.g. `CH`). Although this lexicon requires `srs`, it has no meaning for this type and consumers must ignore it. 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
maxLength: 20 bytescoordinate-decimal, geojson-point, geojson, h3, geohash, wkt, address, country-code, scaledCoordinateslpVersion
string
Required
The version of the Location Protocol
maxLength: 10 bytesname
string
Optional
Human-readable name for this location (e.g. 'Golden Gate Park', 'San Francisco Bay Area')
maxLength: 1000 bytesmaxGraphemes: 100 graphemessignatures
ref
app.certified.signature.defs#list
Optional
Optional cryptographic signatures attesting to this record's content.
srs
string
uri
Required
The Spatial Reference System URI (e.g., http://www.opengis.net/def/crs/OGC/1.3/CRS84) that defines the coordinate system.
maxLength: 100 bytesView raw schema
{
"description": "A location reference",
"key": "tid",
"record": {
"properties": {
"createdAt": {
"description": "Client-declared timestamp when this record was originally created",
"format": "datetime",
"type": "string"
},
"description": {
"description": "Additional context about this location, such as its significance to the work or specific boundaries",
"maxGraphemes": 500,
"maxLength": 2000,
"type": "string"
},
"location": {
"description": "The location of where the work was performed as a URI, blob, or inline string.",
"refs": [
"org.hypercerts.defs#uri",
"org.hypercerts.defs#smallBlob",
"#string"
],
"type": "union"
},
"locationType": {
"description": "An identifier for the format of the location data. Use `country-code` for uppercase ISO 3166-1 alpha-2 codes in `location.string` (e.g. `CH`). Although this lexicon requires `srs`, it has no meaning for this type and consumers must ignore it. 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",
"knownValues": [
"coordinate-decimal",
"geojson-point",
"geojson",
"h3",
"geohash",
"wkt",
"address",
"country-code",
"scaledCoordinates"
],
"maxLength": 20,
"type": "string"
},
"lpVersion": {
"description": "The version of the Location Protocol",
"maxLength": 10,
"type": "string"
},
"name": {
"description": "Human-readable name for this location (e.g. 'Golden Gate Park', 'San Francisco Bay Area')",
"maxGraphemes": 100,
"maxLength": 1000,
"type": "string"
},
"signatures": {
"description": "Optional cryptographic signatures attesting to this record's content.",
"ref": "app.certified.signature.defs#list",
"type": "ref"
},
"srs": {
"description": "The Spatial Reference System URI (e.g., http://www.opengis.net/def/crs/OGC/1.3/CRS84) that defines the coordinate system.",
"format": "uri",
"maxLength": 100,
"type": "string"
}
},
"required": [
"lpVersion",
"srs",
"locationType",
"location",
"createdAt"
],
"type": "object"
},
"type": "record"
}