Spatial serving: indexes, snapshot consistency and stale locations

Last updated: 7 Oct 20265 min read

tutorial

A location service needs indexed candidate retrieval, explicit freshness and a safe response to moved or withdrawn sites.

Index the right geometry

Index site points or zone geometries in the same coordinate reference used for the query predicate. A spatial index narrows candidates; it does not replace the exact distance or containment check. A radius query expressed in meters against degree-based geometry can be wrong unless the database type or projection gives the units intended. The distance contract determines the predicate.

Version the snapshot

A site move changes location and may alter zone membership. Publish a coherent version of site coordinates, operating status and zone boundaries, then log that version with every response. A partial refresh can combine the new site location with an old boundary map. Atomic publication keeps the answer reproducible.

Gate withdrawal immediately

A closed site should leave results before a large spatial index rebuild finishes. Apply an eligibility filter at serving time and rebuild the index under a versioned process. If the location is stale, return a qualified result or decline the location-sensitive action according to the workflow. Do not silently reuse an old coordinate as current.

Rehearse a swap

Serve index version 47 while preparing 48. Move site P-47 across a zone border, close site P-48 and update one boundary. Verify every response logs one coherent version and never returns the closed site. If version 48 fails geometry checks, keep version 47 but retain the closure gate.

Implementation

def eligible_site_candidates(site_rows, current_version):
    return [site for site in site_rows
            if site["snapshot_version"] == current_version and site["open"]
            and site["latitude"] is not None and site["longitude"] is not None]

Performance and operating cost

Filtering S sites is O(S) time and O(E) output memory for E eligible sites. An indexed service can reduce per-request candidate work, but index builds, stale-key checks and atomic version swaps add operational cost.

Common Mistakes

Do not mistake an index hit for an exact spatial match.
Do not mix coordinates and boundaries from different snapshots.
Do not return a closed site from a stale index.