Skip to content

Adding Enforcement Attributes to Demand Data #179

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 34 commits into from
Sep 4, 2025
Merged

Adding Enforcement Attributes to Demand Data #179

merged 34 commits into from
Sep 4, 2025

Conversation

jacobmalleau
Copy link
Collaborator

@jacobmalleau jacobmalleau commented Apr 21, 2025 •
edited by schnuerle
Loading

Adding the ability to handle enforcement related events in the CDS Curb Events and Metrics data. Based on work with LADOT in the SMART Grant Collab.
Resolves #173
Resolves #174

@jacobmalleau
Adding Enforcement Attributes to Demand Data
1e7013c 
Adding the ability to handle enforcement related events in the CDS Curb Events and Metrics data. 
Based on work with LADOT in the SMART Grant Collab
@jacobmalleau jacobmalleau requested a review from a team as a code owner April 21, 2025 17:18
@jacobmalleau
Enforcement Metric - Total Events
dfc0cc8 
Addition of metric to handle summation of events
@schnuerle schnuerle added this to the 1.1 milestone Apr 22, 2025
@schnuerle
Copy link
Member

We will be talking about this at today's public Curb Working Group meeting.

@schnuerle schnuerle changed the base branch from main to dev April 24, 2025 14:23
@mplsmitch mplsmitch added the SMART Collaborative Idea coming from the OMF USDOT SMART grant collaborative. label May 1, 2025
@jacobmalleau
Updates
d147254 
Slight edits to enforcement type names
@schnuerle schnuerle added the Los Angeles OMF and USDOT SMART Curb Collaborative Member label Jun 12, 2025
@schnuerle
Copy link
Member

schnuerle commented Jun 17, 2025 •
edited
Loading

From our Curb Working Group meeting today:

  • Could add an 'enforcement' array key value object that can be part of Events to be captured: muni code, violation name, enforcement action taken, fee/cost, ticket id
  • Also applies to curb objects, how to connect to these objects?
  • Minneapolis and San Joes support this

SFMTA pushes our parking citation data to a public open data feed, and it would be great to have this information available in CDS events.
Current feed: https://data.sfgov.org/Transportation/SFMTA-Parking-Citations-Fines/ab4h-6ztd/about_data

LADOT does as well: https://data.lacity.org/Transportation/Parking-Citations/4f5p-udkv/about_data

@jacobmalleau
Add connecting events to Curb Objects
e97e7a9 
Also slight edits to language.
@jacobmalleau
Copy link
Collaborator Author

Added a commit to connect Events to Objects, but held off on adding the key-value pairs as I want to see if anyone else has thoughts on attributes to add:

  • muni code
  • violation name
  • enforcement action taken
  • fee/cost
  • ticket id
  • Others?

@schnuerle
Copy link
Member

... held off on adding the key-value pairs as I want to see if anyone else has thoughts on attributes to add:

Where would these key value pairs be added?

@schnuerle
Copy link
Member

@jacobmalleau I think go ahead and add a new Enforcement data type with these fields, like we created for External References. Then we can talk about what enforcement fields to add/remove/edit beyond your short list.

You can then add the new enforcement data object as a field in Events, like with External References in Events (bottom of table) and Curbs.

jacobmalleau and others added 5 commits August 6, 2025 14:30
@schnuerle
Copy link
Member

Thanks, looks good, I made some formatting updates, and changed it to just 'Enforcement'. The 'External Reference' name was really just because it was a reference to an external thing.

@schnuerle schnuerle mentioned this pull request Aug 8, 2025
Closed
@schnuerle schnuerle linked an issue Aug 8, 2025 that may be closed by this pull request
Provide double parking event locations #149
Closed
@schnuerle
Copy link
Member

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.

@michael-danko-passport
Copy link
Collaborator

michael-danko-passport commented Aug 12, 2025 •
edited
Loading

There are a few places where we are using citation, ticket, and violation and I think we should be consistent throughout the spec. I would propose the following:

  • citation -> Replaces the usage of ticket and represents a single instance of a broken infraction.
  • violation -> The city or municipal code that was violated

If we can get consensus in one direction or another there are some additional changes that will need to be made.

schnuerle and others added 8 commits August 20, 2025 15:16
@schnuerle @michael-danko-passport
Note original cost
aa600cb 
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle @michael-danko-passport
Clarified field with violation_name renaming
48f6628 
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle @michael-danko-passport
Noted that zones and areas can use any event type
fdd6903 
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle @michael-danko-passport
Allows use of any event type if known and used
74cc38a 
Reduces need to enumerate event types.

Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle @michael-danko-passport
Renaming enforcement fields for consistency
5927b86 
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle @michael-danko-passport
Enforcement fields edits for consistency, clarity
914943f 
Co-authored-by: michael-danko-passport <99669313+michael-danko-passport@users.noreply.github.com>
@schnuerle
Minor formatting
74de5df
@schnuerle
Minor description updates for event types
83cabb9
@schnuerle
Copy link
Member

There are a few places where we are using citation, ticket, and violation and I think we should be consistent throughout the spec. I would propose the following:

  • citation -> Replaces the usage of ticket and represents a single instance of a broken infraction.
  • violation -> The city or municipal code that was violated

If we can get consensus in one direction or another there are some additional changes that will need to be made.

Are you thinking here, for ticket_id and ticket_cost?

https://github.com/openmobilityfoundation/curb-data-specification/blob/jacobmalleau-enforcementimprovements/data-types.md#enforcement

Is a ticket different than a citation? Can there be a ticket ID and a citation ID too, or are those really always the same thing?

@schnuerle
Copy link
Member

@JohnLundstrom-Minneapolis and @bhamlinSDOT can you propose a definition of a status field?

It should be an open ended 'string' type, so you can use two letter abbreviations if needed, or other cities can use what they need.

@kenyaw
Copy link

kenyaw commented Aug 20, 2025 •
edited
Loading

There are a few places where we are using citation, ticket, and violation and I think we should be consistent throughout the spec. I would propose the following:

  • citation -> Replaces the usage of ticket and represents a single instance of a broken infraction.
  • violation -> The city or municipal code that was violated

If we can get consensus in one direction or another there are some additional changes that will need to be made.

Are you thinking here, for ticket_id and ticket_cost?

https://github.com/openmobilityfoundation/curb-data-specification/blob/jacobmalleau-enforcementimprovements/data-types.md#enforcement

Is a ticket different than a citation? Can there be a ticket ID and a citation ID too, or are those really always the same thing?

@schnuerle In San Francisco, we utilize citation for parking violations, so the change from ticket seems fine.

Regarding the definition for violation, cities enforce infractions from various levels of government. A more descriptive definition statement could be "The city/municipal, county, state, or provincial code that was violated."

@schnuerle
Copy link
Member

Based on @kenyaw's comments, I think you can align things to citation, and away from ticket @michael-danko-passport. And update the violation description to "The city/municipal, county, state, provincial, or federal code that was violated." Note I added federal to that list.

@JohnLundstrom-Minneapolis
Copy link

@JohnLundstrom-Minneapolis and @bhamlinSDOT can you propose a definition of a status field?

It should be an open ended 'string' type, so you can use two letter abbreviations if needed, or other cities can use what they need.

I'm realizing that we wouldn't be capturing changes to the status over time (such as when a citation is cancelled on some future date), as those wouldn't be distinct curb events, but we still have some options at the time the citation is issued, mainly delineating between a warning and an active citation. My first attempt is:

"Describes the disposition of the citation at the time it was issued which can be used to identify alternate use cases such as warnings."

schnuerle and others added 10 commits August 26, 2025 11:26
@schnuerle
Update field name in Metrics to citation_issued
0066470
@michael-danko-passport
Update README.md
2d70f00 
Documentation updates:
- Clarifies distinction between vehicle detection and enter/exit event types.
- Text formatting changes
@michael-danko-passport
Incorporates changes from Slack discussion.
5c0700e 
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
@michael-danko-passport
Change citation_id from UUID to String
e311113
@michael-danko-passport
Changes enforcement key in CDS Event to be an object
1bfd51b 
- 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
@schnuerle
Violations TOC and hierarchy
c836c25
@michael-danko-passport
Adds Enforcement and Violations data objects to TOC
559e367
@schnuerle
Removed data type links from TOC
951aa89
@schnuerle
Minor cleanup
98d7fed
@schnuerle
Merge pull request #199 from openmobilityfoundation/feature-enforceme…
156c3f0 
…nt-object-changes

Incorporate Enforcement updates from WGSC discussions
schnuerle
schnuerle approved these changes Sep 4, 2025
View reviewed changes
Copy link
Member

@schnuerle schnuerle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks to the OMF member WGSC and public WG participants for the work and clarity on this feature!

@schnuerle schnuerle merged commit 6ebc72d into dev Sep 4, 2025
1 check passed
This was referenced Sep 4, 2025
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michael-danko-passport michael-danko-passport michael-danko-passport left review comments

@schnuerle schnuerle schnuerle approved these changes

Assignees
No one assigned
Labels
Events API Los Angeles OMF and USDOT SMART Curb Collaborative Member Metrics API SMART Collaborative Idea coming from the OMF USDOT SMART grant collaborative.
Projects
None yet
Milestone
1.1
7 participants
@jacobmalleau @schnuerle @JohnLundstrom-Minneapolis @bhamlinSDOT @michael-danko-passport @kenyaw @mplsmitch