Map-match GIS or curb data to SharedStreets' shared street-segment reference IDs
domain: sharedstreets.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the referencing system concepts (OSM-derived tile-based Reference IDs) in the sharedstreets.io getting-started docs
Use the SharedStreets CLI or API to match your own geometry (e.g., a city's curb or parking dataset) to SharedStreets segment references
Fetch reference tiles directly from the tiles.sharedstreets.io endpoint for a given OSM planet snapshot and z-12 tile coordinate if working offline
Use the returned shared reference IDs as a common join key to combine your dataset with other SharedStreets-referenced datasets, such as curb regulations
Pin to a specific planet.osm snapshot date, since tile content is regenerated periodically
Known gotchas
Reference IDs are tied to a specific OSM planet snapshot date; matches can drift or fail to align if data is referenced against different snapshot dates
This is community-maintained infrastructure, not a commercially SLA-backed service - plan for self-hosting the matcher for production reliability
Map-matching accuracy depends on the quality of the input geometry; sparse or noisy GPS traces produce unreliable matches
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?