Adopt the Open Mobility Foundation's Curb Data Specification to publish or consume curb zone and usage data
domain: github.com/openmobilityfoundation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pick the relevant CDS module: Curbs (static zone definitions), Events (real-time commercial activity at the curb), or Metrics (aggregated dwell/occupancy stats)
Reference the OpenAPI 3.1 schema in the openmobilityfoundation/cds-openapi repo for the CDS version being targeted (1.0 or 1.1)
Model curb segments and their regulations (loading zones, time restrictions) using the Curbs module's geometry and policy objects
Implement Events reporting for check-in/check-out activity if acting as a curb-use provider (e.g., delivery or TNC platform)
Use the Metrics module's defined calculation methodology so occupancy/dwell numbers are comparable across cities
Known gotchas
CDS 1.1 added capabilities not present in 1.0; confirm which version a given city has deployed before building against it
Like MDS, CDS access is typically arranged directly with a city or its vendor, not offered as an open self-serve API
The spec standardizes data structures, not the authentication mechanism, which each city or vendor sets independently
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?