-
Notifications
You must be signed in to change notification settings - Fork 22
Preview of CDS 1.1 Release #197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
schnuerle
wants to merge
157
commits into
main
Choose a base branch
from
dev
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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
See #200 for the latest official release candidate, and leave comments there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.