-
Notifications
You must be signed in to change notification settings - Fork 15
Web Conference 2021.08.24 Curb
Michael Schnuerle edited this page Aug 24, 2021
·
10 revisions
- Every other week Tuesday call at 9am PT / 12pm ET / 6pm CET
Meeting ID: 898 5980 7668 - Passcode 320307
https://us02web.zoom.us/j/89859807668?pwd=ZzJrbEpTNVB4WkNqNiszcmFYVzBwZz09
One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)
Dial by phone: +1 929 436 2866 (US) (Find your local number)
Main Topics
- Welcome and process (5 min) - Brian Hamlin, SDOT
- Regulation/Event/Metrics spec recap (5 min) - Michael Schnuerle, OMF
- Curb policy use case (8 min) - TBD
- CDS Events API Discussion (40 min) - Harris Lummis (Automotus)
- Hosts: Brian Hamlin (SDOT), Harris Lummis (Automotus), Michael Schnuerle (OMF)
- Note Taker: Tomas Carranza, LADOT
- Facilitator: Angela Giacchetti (OMF)
- Outreach: Brian Hamlin
- 41 Attendees
- Recording and chat log - Passcode: s6%k8B*B
- Main Presentation Slide Deck
Action Items
- New Discussion Areas
- event_type and vehicle_states - what to add, how to structure
- Endpoints for GET /events (list of events by recency, therefore RT and historic) and GET /status (current state of curb usage)
- How are provider IDs handled? Globally unique like MDS in a file? Locally unique and managed by each agency as fleet registration happens? Does every company get 1 ID, or could company divisions (Freight, Ground, etc) have their own IDs?
- What types of vehicle IDs are possible? License place number, unique UUID provided by provider like MDS, VINs, registration number, etc.
- Add vehicle properties - what properties need to be added? Permit number (optional and sent only in company feed)? Already have length.
- Add examples in doc for data sources (sensors, company feed, cam, etc) to show how optional fields can be used.
- Clarify that policies are not active or enforced except between the start/end times listed in the policy.
** Decisions **
May need to add this to the Architectural Decisions doc.
- Curb Areas can overlap. Add language, make array in Events
- Endpoint Push is too hard for this version, so everything needs to be Pull
- Sensor status should come through in this feed to make it easy for consumers (no cross checking needed) to know sensor operational status
Minutes
...