Releases: openmobilityfoundation/curb-data-specification
1.1.0 RC
Released Candidate created: 2025-09-03
The 1.1.0 release is the first minor release update for CDS.
CHANGES
See Release 1.1 notes for a detailed list of changes.
Full Changelog: 1.1.0...1.1.0-rc
1.1.0
Released: 2025-10-27
The 1.1.0 release is the first minor release update for CDS.
CHANGES
See the closed PRs tagged with Milestone 1.1.0 and Issues for a full list of changes. 201 commits, 14 files changed.
Updates
- Objects - defining location, properties, and usage of various objects at the curb zones
- Enforcement - define and capture time, location, and details of violations, citations, and enforcement actions at the curb, including double parking
- Payment Methods - ability to track and collect various payment methods and channels, and transaction IDs
- Real-time Events - you can now push events as they happen directly to a public agency. This optional method simplifies and speeds up the communication of event details
- External References - link CDS data fields to any other external data sources: WZDx, CWZ, GBFS, GTFS, MDS, websites, documents, etc
- Custom Attributes - custom fields can be added to align to agency and vendor needs
- Authorization - Curbs endpoints may be accessed with permission from a public agency
- Lines - curb Zones may be defined with lines, instead of polygons
- New Curb Data - curbs can have new information like description, jurisdiction, owner name, address number, available space count
- Color - Policies can be defined with colors and patterns for real world or digital representation
- Policy Uniqueness - Policies must be unique and not duplicative
- Rules Info - Rules can have names and descriptions
- Weeks of Month - Policies can define weeks of the month when applicable
- Event Authorization - recommended but not required, so events data can be made public
- Vehicle Properties - many new properties like make, model, year, color, company
- Computer Vision - confidence levels for new and existing vehicle property detection
- MDS Vehicle Alignment - align vehicle types and propulsion types with latest MDS version
- Metrics Event Tracking - new total event count tracking for various events, including enforcement
MORE DETAILS
- Website: CDS overview with links to key resources
- Intro Slide Deck: OMF & CDS overview in presentation format, with links to key resources
- One-Pager: OMF & CDS overview, ready to print and share
- GitHub Repository: Find the CDS 1.1 code release and review related discussion and contributions
- Open API: Digital schema for checking your work against CDS specifications
- Policy Language: Sample policy language and guidance for cities that wish to write CDS into their operating policy, permits, tenders, and RFPs
- Privacy Guidance: Guidance related to the collection and handling of potentially sensitive information related to CDS
- Getting Started Guide: help structure a successful curb program with key questions and recommendations during each phase of the program’s development
- Launch Meeting: Meeting of our public working group reviewing the new features and upgrade resources
- Launch Slides: See our slides from this meeting outlining the major features in more details and with helpful diagrams
- Blog Post: Overview of the release with info, features, and resources in a shareable form
ACKNOWLEDGEMENTS
Thank you to our current and past steering committee members, GitHub pull request and issue creators (CurbIQ, Populus, Umojo, INRIX, Passport, SFMTA, Omaha, Montréal, and USDOT SMART Curb Collaborative cities) for this release, and for the organizations that participated on our weekly working group calls.
What's Changed
- Release 1.0.1 by @schnuerle in #161
- Patch 1.0.1 to Dev by @schnuerle in #162
- Creating Curb Objects by @jacobmalleau in #126
- Add Additional Providers for reporting events based on Provider ID. by @rneubauer in #167
- Fix LineString GeoJSON example by @mplsmitch in #181
- Linking to External Overlapping Data Sources (WZDz, CWZ, MDS, GBFS, GTFS, Curb Objects, etc) by @schnuerle in #96
- Add event_time query parameter to events endpoint by @jiffyclub in #140
- Update README.md to note deduplication of events by @michael-danko-passport in #188
- Designated period and user class exceptions by @mplsmitch in #187
- Feature custom attributes by @jacobmalleau in #182
- Add name and description fields to policy & rule by @jiffyclub in #175
- Add linestring geometry to curb zone by @InrixParking in #171
- Push Events Endpoint by @schnuerle in #180
- 1.1 Consolidated Issues resolution by staff by @schnuerle in #192
- Added Custom Attribute to Events Data Object by @schnuerle in #193
- Staff 1.1 issues 2 by @schnuerle in #194
- Add color options to Policy in the Curbs API by @schnuerle in #195
- Add Payment Channel and Method to Curb Events by @jiffyclub in #158
- Vehicle properties and computer vision fields by @schnuerle in #196
- Incorporate Enforcement updates from WGSC discussions by @michael-danko-passport in #199
- Adding Enforcement Attributes to Demand Data by @jacobmalleau in #179
New Contributors
- @jacobmalleau made their first contribution in #126
- @InrixParking made their first contribution in #171
Full Changelog: 1.0.1...release-1.1.0
Contributors
Assets 2
1.0.1
Released: 2024-12-09
The 1.0.1 patch release cleans up and clarifies some minor issues and typos to help make the specification clearer.
CHANGES
See the closed PRs tagged with Milestone 1.0.1 and Issues for a full list of changes.
Minor updates
- OpenAPI support
- Reference to MDS
- Internal Links
- Event location description
- Street name description
- Accessibility user classes
- Rate maximum fee clarification
- New data source device name field
- New operators
ACKNOWLEDGEMENTS
Thank you to our current and past steering committee members, GitHub pull request and issue creators (Passport, CurbIQ, INRIX, Umojo, Clevercity, Lacuna, Populus, @jamesdwilson) for this release, and for the organizations that participated on our weekly working group calls.
What's Changed
- CDS 1.0.0 Final Release by @schnuerle in #71
- OpenAPI Support by @schnuerle in #100
- Correct copy/paste reference to MDS by @michael-danko-passport in #114
- Link GeoJSON type to description by @mplsmitch in #134
- Update Curb Examples by @mplsmitch in #132
- Update event examples by @mplsmitch in #133
- Add field - maximum_fee by @mplsmitch in #135
- Update data_source_operators.csv by @rneubauer in #144
- Introduced Cleverciti entry in operator list by @ArchaicDebugger in #153
- Add links to OpenAPI schema and Stoplight by @mplsmitch in #155
- Update street_name definition by @mplsmitch in #139
- Add Curb Event field for operator device name by @jiffyclub in #141
- Replace Handicapped with Accessible by @mplsmitch in #160
New Contributors
- @michael-danko-passport made their first contribution in #114
- @mplsmitch made their first contribution in #134
- @rneubauer made their first contribution in #144
- @ArchaicDebugger made their first contribution in #153
- @jiffyclub made their first contribution in #141
Full Changelog: 1.0.0...1.0.1
Contributors
Assets 2
1.0.0
The 1.0.0 major release is the first release of the Curb Data Specification (CDS) after over 17 months of community work across dozens of public meetings, with 70+ organizations and 160+ individuals participating. It includes three major APIs to define Curbs and policies, track Events at the curb and determine sensor status, and derive Metrics for sessions and aggregate curb usage with a well defined methodology. CDS is currently being used by over two dozen organizations.
LICENSE and DISCLAIMER
Use of OMF Releases are bound by the OMF License and Disclaimer.
RELEASE PLAN
Our 1.0.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with recordings, slides, and minutes.
CHANGES
See work tagged with "Milestone 1.0.0" in Pull Requests, Issues, and Discussions for a full list of changes and history.
General CDS
- Creation of spec from working group drafts and community code submissions
- See About CDS web page for high level details
Curbs
- The Curbs API is a standard way for cities to digitally publish curb locations and regulations, which can be shared with the public and with companies using curb space. It defines curb policies, curb zones, spaces in zones, and areas around curbs, and is used by Events and Metrics.
Events
- The Events API is a standard way to transmit real-time and historic commercial events happening at the curb to cities. Event data can be derived from company data feeds, on street sensors, session payments, company check-ins, in-person parking personnel, and/or other city data sources. Connected to Curbs and used by Metrics.
Metrics
- The Metrics API is a way to track curb usage session details and define common calculation methodologies to measure historic dwell time, occupancy, usage and other aggregated statistics. It defines sessions and aggregates data derived from raw Events data.
Minor Updates
- Formatting of spec, links, TOCs, headers, etc
ACKNOWLEDGEMENTS
Thank you to GitHub pull request creators (Ride Report, Automotus, Coord, City of Seattle DOT), issue/discussion creators (City of Seattle DOT, Coord, IBI Group CurbIQ, Automotus, E&A), and commenters/contributors (Ride Report, IBI Group CurbIQ, Automotus, E&A, Coord, City of Seattle DOT, Populus, Washington DC DDOT, City of San Jose, City of Omaha Parking, Passport, ITE Curbside, SANDAG, Los Angeles DOT, SFMTA, City of Philadelphia, Ford AV, Waymo) for this release, our Curb Steering Committee members, and for the 70+ organizations and 160+ individuals that participated on our weekly public working group calls.
1.0.0 Release Candidate
1.0.0
Release Candidate submitted 2022-01-25
The 1.0.0 major release is the first release of the Curb Data Specification (CDS) after over 15 months of community work across dozens of public meetings, with 70+ organizations and 160+ individuals participating. It includes three major APIs to define Curbs and policies, track Events at the curb and determine sensor status, and derive Metrics for sessions and aggregate curb usage with a well defined methodology.
CHANGES
See work tagged with "Milestone 1.0.0" in Pull Requests, Issues, and Discussions for a full list of changes and history.
General CDS
- Creation of spec from working group drafts and community code submissions
- See About CDS web page for high level details
Curbs
- The Curbs API is a standard way for cities to digitally publish curb locations and regulations, which can be shared with the public and with companies using curb space. It defines curb policies, curb zones, spaces in zones, and areas around curbs, and is used by Events and Metrics.
Events
- The Events API is a standard way to transmit real-time and historic commercial events happening at the curb to cities. Event data can be derived from company data feeds, on street sensors, session payments, company check-ins, in-person parking personnel, and/or other city data sources. Connected to Curbs and used by Metrics.
Metrics
- The Metrics API is a way to track curb usage session details and define common calculation methodologies to measure historic dwell time, occupancy, usage and other aggregated statistics. It defines sessions and aggregates data derived from raw Events data.
Minor Updates
- Formatting of spec, links, TOCs, headers, etc