Web conference notes, 2021.01.14 (Joint Working Group)
Joint Working Group - Provider Services
NOTE NEW TIME TWO HOURS SOONER
- Every other week call at 9am PT / 12pm ET / 6pm CET
NOTE NEW ZOOM MEETING ID/LINK/PHONE! (as of Jan 1, 2021)
Meeting ID: 841 7098 9462 - Passcode 612987
https://us02web.zoom.us/j/84170989462?pwd=WTRlY25wOVhNeS8wQk1iM2QzYkQvUT09
One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)
Dial by phone: +1 929 436 2866 (US) (Find your local number)
Add your own name, link, and organization during call
- Steve Brining, BlueSystems
- Michael Schnuerle, OMF
- Kegan Maher
- Marie Maxham
- Jascha Franklin-Hodge
- William Henderson, Ride Report
- Seth Herr, Tranzito
- 26 attendees
Goal setting for next release. Continuation of last meeting
Main Topics
- City Requirements API - Proposal #608
- Authorization Consistency #584
- Extend Metrics: street segments #556
- Discussion of any unresolved issues that are a priority
Notes and or transcript of the call with presentation, document, GitHub links and calls to action.
City Requirements
- Meg Baltimore - would be great for clarity for what cities need
- Steve, auto catalog these feeds? Maybe if need but manual collection could work too.
- Version settings - each supported version would be in the file
- Good idea to collect options in the Issue, leave thoughts
Authorization consistency
- Not complex to fix, but a bit tedious
- Max can volunteer to do PR at some point
- Docs and organizing, not breaking or not, not changing
- May identify areas for improvements
Metrics street segments
- Sharada - streets segments identified with shared streets
- Burden on providers?
- DC can do this if the GPS accuracy is good enough
- 2 things - disaggregated data with street segments and /trips, and in Metrics to aggregate to street segments (useful for providers offering to cities, not how it is now).
- Shared streets only ID used? City IDs. Question of analytic tools cities are using.
- Combine multiple provider data into Metrics
- Instead of geographies, talk in segments
- Use case - MPO wanting to make use of this for members
- OSM, Coord, CurbLR street segment systems, cities have their own segment ids in Open data.
- Curb WG will decide how to define linear space, could be used here, needs to be consistent with rest of MDS
Rich Telemetry data #589
- Providers, is this possible? Speed, heading, accuracy
- Some could be captured without GPS accuracy
- Spin doesn’t save this currently
- Useful to cities to get speed with breadcrumbs from an operator compliance perspective, but also for infrastructure planning to see where speed is too low/high. DC compare corridor speed to bus speed. Baltimore uses radar gun for speed due to being unreliable.
- Is this possible to capture and save this, is it possible? Can be an optional field for cities to request.
- London wanted max speed reached per trip.
- What is real value for cities?
- Needs more exploring about what is possible, how accurate, who’s doing it. Then use cases for cities. Then how to implement in MDS.
- Spin will look, OMF can reach out to other operators.
- Utility from other operators (Ride Report created this discussion)
- Note PR #73brings this up and adds altitude, vertical/horizontal accuracy.
Self driving option #521
- Rebalance, charging, navigate to customer, empty back to new delivery, improve cellular reception
- Sidewalk delivery robots, last mile delivery
- Productive trip movement, or other type of travel
- SPIN: Tele operated using cameras to reposition for obstruction removal. Short distance. Maybe not entire fleet, but a portion of fleet.
- Are trips included in all cases, eg obstructions
- maybe just state machine options are added for now with no trip/location data added
- This needs a provider to deploy at scale, or city needing this to be known. Start with sidewalk delivery which is happening now, and update MDS to support this. Ensure to align that to rebalancing and tele operation. Not currently part of OMF scope but when it is ensure this is brought up
