Skip to content

Conversation

schnuerle
Copy link
Member

@schnuerle schnuerle commented Aug 11, 2025

Note: See #200 for the latest official release candidate, and leave comments there.

Starting a pull request so the working group can see all proposed changes in CDS 1.1 in one place, as they get pushed to the dev branch.

We will be reviewing this at tomorrow's public Curb Working Group meeting.

However we won't have much time to discuss, so leave your comments and suggestions here as general or inline comments to spark changes before the CDS 1.1 release is made.

schnuerle and others added 30 commits June 14, 2022 08:21
First commit / defining Curb Object
- Note centroid of object
- Note positive and negative distances
- Start to populate type specific attributes
Updated language around Object Type Attributes based on latest discussions.

It omits details on specific attributes for future versions of the spec.
The events/events endpoint currently has no documented way to indicate
the time range for which data is being requested. This adds an
event_time query parameter to the API endpoint that takes the form
of an ISO 8601 UTC hour YYYY-MM-DDTHH so that the user can request
all events that occurred within that specific hour. This is the same
format used for MDS events [1].

[1]: https://github.com/openmobilityfoundation/mobility-data-specification/tree/2.0.1/provider#historical-events---query-parameters
See meeting notes for additional context.
schnuerle and others added 27 commits August 20, 2025 15:16
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Reduces need to enumerate event types.

Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
Documentation updates:
- Clarifies distinction between vehicle detection and enter/exit event types.
- Text formatting changes
Applies changes discussed via Slack with members from WGSC.
- Documentation updates to the descriptions of vehicle_detected (new) and enter_area (existing) events to distinguish between these.
- Adds a new `enforcement.is_warning` field
- Adds a new `enforcement.violations` array
- Defines a new `Violations` object
- Moves violation specific fields to the new violations array
- Previously was an array of Enforcement objects
- Change aligns with a single enforcement object for each event, with the Enforcement object now containing an array of violations
…nt-object-changes

Incorporate Enforcement updates from WGSC discussions
…rcementimprovements

Adding Enforcement Attributes to Demand Data
@schnuerle
Copy link
Member Author

See #200 for the latest official release candidate, and leave comments there.

@schnuerle schnuerle removed this from the 1.1 milestone Sep 4, 2025
@schnuerle schnuerle changed the title Draft of CDS 1.1 Release Preview of CDS 1.1 Release Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin Administrative work, chores, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants