app.kalangitan.location.snapshot
A discrete "here's where I was" location record. A snapshot, like any other post. Contrast with app.kalangitan.location.live, which is a single continuously-overwritten record. Belongs to a persona via profileUri; the persona's location.visibility defaults govern whether snapshots are recorded at all and at what precision.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | location.kalangitan.app |
| Indexed |
Record
record · key tidProperties
When the location was actually captured by the device.
AT-URI of the app.kalangitan.actor.profile record this snapshot belongs to.
#geo
objectShared location shape, referenced by feed.post, feed.note, feed.story, and location.snapshot. Coordinates must already be coarsened to the persona's configured precision before the record is written. The precision field records which level was applied.
Properties
label
stringOptional human-readable place name.
maxLength: 256maxGraphemes: 256
Latitude in E7 microdegrees (degrees x 10^7), i.e. 145995000 = 14.5995N. The atproto data model has no float type, so coordinates are signed fixed-point integers.
minimum: -900000000maximum: 900000000
Longitude in E7 microdegrees (degrees x 10^7).
minimum: -1800000000maximum: 1800000000
exact: precise point. neighborhood: coarsened to ~1km. city: coarsened to city centroid/extent.
knownValues: exact | neighborhood | city
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Live location: a single continuously-overwritten record, NOT a growing collection. Belongs to a persona via profileUri; near-real-time updates are feasible because Spaces support direct PDS-to-PDS sync without a relay, so this record never bloats the repo. Only written when the owning persona's location.visibility mode is 'live'. CONVENTION: this record's repo key (rkey) MUST match the rkey of the app.kalangitan.actor.profile record named in profileUri, so the two records pair up deterministical
-
Per-persona location defaults: whether location is shared at all (mode) and at what granularity (precision). These defaults keep posting low-friction. Location behavior is configured once per persona, not per post. CONVENTION: this record's repo key (rkey) MUST match the rkey of the app.kalangitan.actor.profile record named in profileUri, so the two records pair up deterministically.
-
A standard post. Location is a required part of every record in this app, not an optional tag. Belongs to exactly one persona via profileUri; the persona's location.visibility defaults govern how the location is stored and shared. For a gated persona this record lives inside the persona's Space. Spaces provide access control, not confidentiality. The space host and PDS operator can technically read this data.
-
app.certified.location
recordA location reference
-
A short, lightweight status note. Location is optional. Belongs to exactly one persona via profileUri. For a gated persona this record lives inside the persona's Space; Spaces provide access control, not confidentiality.