implement the curb data specification (cds) events api to report real-time curb usage events
domain: github.com/openmobilityfoundation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Model each occurrence at a curb zone as a Curb Event with a globally unique event_id, an event_type describing what happened, and a curb_use field capturing the general purpose of the activity (required when your source can determine it).
Include a geographic point location for the event whenever possible, even if only approximately known.
Source events from whichever channels your deployment supports — company data feeds, on-street sensors, session payments, check-ins, or manual entry by parking personnel — CDS Events is designed to accept any of these.
Reference the relevant Curbs API zone/policy objects by ID so agencies can join event activity back to the regulation in effect at that location.
Treat CDS Events as the input layer for CDS Metrics — don't independently compute dwell time/occupancy if you're also implementing Metrics; let Metrics derive those from the raw Events stream.
Known gotchas
CDS is modular — an agency may adopt only the Curbs API, so don't assume every CDS deployment you integrate with also runs Events or Metrics.
CDS Events overlaps conceptually with MDS Agency/Provider event data; the specs are designed to be interoperable but are not automatically the same payload shape, so don't assume a single event object satisfies both.
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?