Released 2025-10-27

• Release Notes
• Release Draft - all changes - browsable dev branch - leave comments
• 1.1.0 Milestone: Issues and Pull Requests
• Working Group Meetings
• Web page

According to our semantic versioning, this is a minor release.

The 1.1.0 minor release includes the following features.

Summary

• Curb Objects: Define the physical and digital assets that make up the curb — from signs and meters to EV chargers and bike corrals — for a clearer, more consistent picture of curb infrastructure and usage.
• Enforcement: Capture when and where violations or citations occur, including double parking, to help cities measure compliance and target problem areas.
• Payment Methods: Track multiple payment types, methods, and transaction IDs to support flexible, transparent pricing and easy integration across vendors.
• Real-Time Events: Share activity data with agencies as it happens, enabling more responsive, data-driven management of dynamic curb zones.
• External References: Connect CDS data fields with any related standard such as WZDx, CWZ, GBFS, GTFS, and MDS, expanding interoperability across the mobility ecosystem.
• Computer Vision & Vehicle Properties: Reflect advances in camera-based sensing and automated detection by expanding recordable vehicle attributes — from identifiers and propulsion types to size and permit details — for richer operational insight, including confidence levels for edge detection.
• Additional Features: Includes upgrades like custom attributes, policy and curb color, event tracking metrics, and more details in curb, policies, rules and events.

General

• Linking to External Overlapping Data Sources (WZDz, CWZ, etc) #96
• New data providers #167

New Features

• Curb Objects #126

Curbs API

• Name and description in Policy and Rule #175
• Add a currency field for Rates #120
• Add more Curb Zone Availability info #97
• Add linestring geometry to curb zone #171
• Define unique constraint on Policy #178
• Add color options to Policy in the Curbs API #195

Events API

• Add Payment Channel and Method #158
• Provide double parking event locations #149
• Define geometry for event_location Point #129
• Publishing events via Push mechanism #99, #180
• Add start and end time as query parameters #107
• Vehicle properties and computer vision fields #196
• Adding Enforcement Attributes to Demand Data #179

Metrics API

• New Metric Type to Handle Additional Demand Sources #174

Status Key:

• ✅ Complete
• 🟡 In Progress
• 🟥 Not Started