model cds curbs api zones and policies distinct from mds policy geofencing

Steps

1. Use the CDS Curbs API to publish the physical definition of curb locations, parking regulations, zones, spaces within zones, and objects near the curb — this is the foundation that CDS Events and Metrics build on.
2. Note the direct conceptual mapping OMF documents: CDS Curbs corresponds to MDS Policy rules plus geofencing (which itself uses MDS Geography and Jurisdiction), while CDS Events maps to MDS Agency/Provider event data and CDS Metrics maps to MDS Metrics.
3. Where a city already runs MDS Geography/Jurisdiction for vehicle regulation, reference those objects by ID from your CDS Curbs zones rather than re-defining the same boundaries twice, since the specs are built to interconnect by reference.
4. Treat CDS as a data exchange/publishing format, not necessarily your internal storage schema — convert from your internal curb-management system into CDS on publish rather than storing regulations natively in CDS shape.
5. Confirm which of the three CDS APIs (Curbs/Events/Metrics) a given city or vendor actually implements before assuming full-stack support, since agencies may adopt only a subset.