serve versioned regulatory boundaries through the MDS Geography API
domain: github.com/openmobilityfoundation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Publish each boundary as a Geography object with geography_id (UUID), name, geography_json (a GeoJSON FeatureCollection), published_date, and optional effective_date/retire_date/description.
Set geography_type to a recommended value like municipal_boundary, policy_zone, council_district, or right_of_way, or omit it/use custom text — it's for discovery only and carries no implicit rule meaning.
Treat published geographies as immutable: to change a boundary, publish a new Geography with prev_geographies listing the UUID(s) it replaces, rather than editing in place.
Serve via GET /geographies (all) and GET /geographies/{geography_id} (one), or via a geographies.json flat file with the same shape, and make the endpoint public/unauthenticated.
Reference geography_id from Policy rules or Jurisdiction objects rather than duplicating boundary geometry in multiple places.
Known gotchas
Retired geographies must still be returned in the /geographies list for historical audit, not deleted — old policies referencing a retired geography_id still need to resolve.
Geography is a separate spec purpose from Jurisdiction: Jurisdiction communicates agency authority/boundaries between agencies, while Geography just stores the reusable GeoJSON shapes referenced by Policy and Jurisdiction.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?