Web conference notes, 2021.02.18 (Joint Working Group)
Joint Working Group - City Services
- 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
- Henri Bourdeau, BlueSystems
- Michael Schnuerle, OMF
- Matt Davis, Populus
- Steve Brining, Blue Systems
- Marie Maxham, E&A/LADOT
- 21 attendees
Main Topic : 1.0 and BETA use
- What is your current or planned use for the BETA features? (follow up on this email thread)
- How far are you with implementing 1.0? Is there a need for more guidance?
- Does the MDS specifications need more examples? If yes, where and which?
Who on the call is using which beta features?
Provider Vehicles (0.4) use:
- Superpedestrian is serving this to cities and ingesting from providers now. Will followup with more details.
- Spin - Baltimore required it, uses it for distribution discrepancies
- San Francisco - intents to use it soon, for investigations, maybe to do counts of scooter
- Washington DC - created a bespoke GBFS with unavailable devices, allows some extra knowledge. Bike providers only are required now.
- Baltimore - vehicles tracking vandalism. Required from spin and lime.
- Ride report - GBFS private is being used now
Stops (0.4) use:
- Too early to tell. Not much use yet.
Rates (1.0) use:
- Ride Report - several cities are using it. No one is consuming the Policy API even though it's built and ready and has this rule type.
- DC likes the idea of using it but hasn't yet.
Who on the call is using or plans to use 1.0.0 release?
- Blue systems - will be ready in a couple of weeks, accepts from both providers or agencies, events and transitions are useful
- San Francisco - upgrade later this year. state transitions docs are useful
- Los Angeles - planning on it
- Superpedestrian - provider to be live soon, and agency under development.
- Vianova - has policy 1.0 on near term roadmap
Should MDS have more examples and if so where?
- Policy could use more specific use cases
- Geography is well done
- Instead of examples, a validator may be more useful in the long run
- Maybe some examples for non technical folks and for technical solutions too
Idea of a validation tool that providers, agencies, third parties could use to validate their data feed.
- Official validator for MDS would be useful, downloaded and run locally
- MDS Schemas that exist now are good for a first step, but don't have enough detailed checking for issues
- Example, status change endpoint start after and end, provider sending events too recent after end, etc
- Start and end time check.
- Produce scripts that providers and run locally, and point to APIs.
- Blue systems has an open source agency validator: https://github.com/Polyconseil/mds-agency-validator (adding to OMF state of practice and community projects). Python.
- Collectively contribute to a tool that could help everyone.
- Jack from Vianova - has to build a custom patching system to fix issues with provider feeds
- OMF will make a call for interest to participate in a temporary working group and see what the momentum is like.
- Ride Report has a tool for providers to validate their feeds, is also willing to help
