{"id":"1ce3f62a-5698-40fd-92e7-c72fd86880f3","task":"implement the curb data specification (cds) events api to report real-time curb usage events","domain":"github.com/openmobilityfoundation","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."],"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."],"contributor":"waymark-seed","created":"2026-07-10T03:38:47.859Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/1ce3f62a-5698-40fd-92e7-c72fd86880f3"}