• Monthly on Tuesday at 9am PT, 12pm ET, 5/6pm CET - open to the public
• Zoom Registration and Join Link: https://us02web.zoom.us/meeting/register/tZ0lcuCgrjwsHNyZRagmc86b12iCmWGBHfjq
  • One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)
• Signup to the Mailing List for emails and calendar invites

CDS 1.1 Released - Live on GitHub - Release Notes

The new version of CDS is approved and live. Adds curb objects, enforcement data and metrics, payment method details, real-time activity tracking, connecting to external data sources, more vehicle properties, computer vision fields, curb color schemes, and lots of other new details and features.

• Welcome (5 mins)
• Announcements (5 mins)
• CDS 1.1 Released (45 mins) - Resources and Upgrading

• Hosts: Michael Schnuerle, OMF
• Note Taker: Michael Schnuerle, OMF
• Facilitator: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF

• Get to know CDS 1.1 and explore the release and notes
• Share the resources as needed
• Speak with your team or partners on how the new features in CDS 1.1 might be useful in upcoming projects and/or how to prepare to upgrade
• Invite OMF for a deep-dive with your team on CDS 1.1, including more detailed information on use cases and impactful technical changes

1. Website: CDS overview with links to key resources
2. Intro Slide Deck: OMF & CDS overview in presentation format, with links to key resources
3. One-Pager: OMF & CDS overview, ready to print and share
4. GitHub Repository: Find the CDS 1.1 code release and review related discussion and contributions
5. Open API: digital schema for checking your work against CDS specifications. In development.
6. Policy Language: Sample policy language and guidance for cities that wish to write CDS into their operating policy, permits, tenders, and RFPs
7. Privacy Guidance: Guidance related to the collection and handling of potentially sensitive information related to CDS
8. Getting Started Guide: help structure a successful curb program with key questions and recommendations during each phase of the program’s development
9. Launch Meeting: Meeting of public working group reviewing the new features, upgrade resources
10. Launch Slides: See our slides from this meeting outlining the major features in more details and with helpful diagrams
11. Blog Post: Overview of the release with info, features, and resources in a shareable form

• 38 Attendees
• OMF Slides
• Recording - Password tEC7h@s7

Implementing CDS doesn’t require planners, engineers, or policymakers to be coding experts. The key is setting clear goals, working with the right technical partners, and aligning data needs with mobility, parking, and curb management objectives. Often, someone in the agency already has experience with or working knowledge of other specifications and can guide the process with help from an existing ecosystem of vendors.

In practice, planners, engineers, and policymakers define the “what” and “why,” while vendors or IT teams manage the technical “how.”

• Yes CDS 1.1 is live on the main GitHub page now
  • Other branches will be cleaned up soon, and dev and release branches will remain
• In early 2026 we will start gathering your ideas for the next release, and the Curb Collaborative 2.0 will help drive changes
  • See the CDS Releases page to keep up to date, and subscribe to our mailing list
• OpenAPI work for CDS 1.1 will start soon in the 1.1 branch, and we welcome your help along with OMF and Passport
• Going from v1.0 to v1.1 does not include any breaking changes

This provides resources that guide cities in writing CDS into their operating policy, permits, tenders, or RFPs. The Open Mobility Foundation has created sample language for cities to use based on existing policy documents and feedback from its members. The sample language offers a starting point while creating flexibility for cities to customize the language based on their local requirements.

RFP Guidance

For public agencies using an RFP, RFI, RFQ, tender, etc. to procure vendors for a project, consider specifying CDS as part of the evaluation process. [LINK].

Policy Guidance

Cities can ask mobility providers to stay up to date with the latest CDS releases by incorporating language into the city’s operating, policy, tender, or RFP [LINK].

Contract Renewal

For public agencies preparing for an upcoming annual contract renewal, specify MDS as part of a requirement for renewal [LINK].

Service Level Agreement Guidance

Cities should specify a Service Level Agreement (SLA) to establish technical performance expectations. This should include, a minimum, data availability and response time (e.g., how long it takes to return data) [LINK].

• 00:07:18 Daniel Patterson: Daniel Patterson - returning. Congratulations for the 1.1 release!
• I’ve been freelancing (data engineering) for the past year with transportation and land development firms. I’ll be joining Parametrix as a Senior Geospatial Engineer alongside David VS. Happy to be here.
• 00:07:32 Michael Schnuerle: Project Showcase https://docs.google.com/document/d/1YfYOA38MQgMVf7f4-tE6W4UC5deRbC1GO2MFjNud0Uc/edit#heading=h.fxlnztjxsmgo
• 00:21:57 Brian Hamlin | Seattle DOT: I think having Objects now is going to be a game changer
• 00:25:06 Elias Khoury - San Jose DOT: i see us converting our curb regulation signage inventory to CDS
• 00:25:24 John Lundstrom (Minneapolis PW): Objects are a vital component of our approach to an evergreen curb map, but Minneapolis is going to try and utilize nearly every new feature of 1.1 to both recommend changes moving forward and to test their limits.
• 00:25:45 Brian Hamlin | Seattle DOT: Can confirm that I am not a very technical person but I know enough now to be able to work with the people that actually are when it comes to curb data
• 00:27:31 Loan Nguyen, ParkClear: Hi Everyone, we're a mobile parking app that converts confusing street sign rules into simple yes/no answers. We are piloting Los Angeles to help people save time and money, while promoting responsible parking.
• https://parkclear.co demo below
• https://youtu.be/he5S1xkU1vk
• 00:29:09 John Lundstrom (Minneapolis PW): Replying to "Hi Everyone, we're a..."
• This looks quite close to features I have been wanting to advance in Minneapolis. I'd be happy to setup a conversation.
• 00:31:03 Michael Schnuerle: Blog announcement https://www.openmobilityfoundation.org/announcing-cds-1-1-a-smarter-more-connected-future-for-the-curb/
• 00:33:13 Loan Nguyen, ParkClear: Replying to "Hi Everyone, we're a..."
• We’d love to connect! Please kindly share contact
• 00:34:40 Michael Danko (Passport): Going from v1.0 to v1.1 does not include any breaking changes.
• 00:37:10 John Lundstrom (Minneapolis PW): Replying to "Hi Everyone, we're a..."
• John.lundstrom@minneapolismn.gov is the best way to reach me!
• 00:47:22 Brian Hamlin | Seattle DOT: That sounds like something Philly is cooking up
• 00:49:43 John Lundstrom (Minneapolis PW): Thank you!