Skip to content

Web conference notes, 2021.02.18 (Joint Working Group)

Michael Schnuerle edited this page Feb 19, 2021 · 14 revisions

Web Conference, 2021.02.18

Joint Working Group - City Services

  • Every other week call at 9am PT / 12pm ET / 6pm CET

Conference Call Info

#red 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)

Attendees

Add your own name, link, and organization during call

Agenda

Main Topic : 1.0 and BETA use

  1. What is your current or planned use for the BETA features? (follow up on this email thread)
  2. How far are you with implementing 1.0? Is there a need for more guidance?
  3. Does the MDS specifications need more examples? If yes, where and which?

Minutes

Beta features

Provider use:

  • Super pedestrian is serving to cities
  • Spin - Baltimore required, distribution discrepancies
  • SF intents to use it for investigations, maybe counts of scooters
  • Sharada DC - bespoke GBFS with unavailability, extra knowledge, don’t know how live GBFS is. Bike providers only.
  • Meg Baltimore, vehicles tracking vandalism. Required from spin and lime
  • Ride report - GBFS private

Stops use:

  • Too early to tell. It’s added 1.0.0.

Rates use:

  • Ride Report - several cities are using it. No one is consuming the Policy API and this rule type.
  • DC likes the idea

1.0 Implementation

  • Blue systems, Ready in a couple of weeks, accept from providers or agencies
  • SF upgrade later this year
  • LA planning on it
  • Superpedestrian - provider, and agency soon. People consuming it
  • Vianova has policy 1.0 on roadmap
  • Blue systems - events and transitions
  • Alex SF - state transitions docs are useful

Examples

  • Policy could use more
  • Geography is well done
  • Instead of examples, a validator may be more useful in the long run

Validation Tool

  • Official validator for MDS would be useful, locally
  • Schemas are good in for first step
  • Ex, status change endpoint start and end, provider sending events too recent after endgame
  • Start and end time check.
  • Examples for non technical folks and for technical solutions too
  • Produce scripts that providers and run locally, and point to APIs. Python. Providers are using it.
  • Blue systems agency validator: https://github.com/Polyconseil/mds-agency-validator
  • Contribute to a tool that could help.
  • Jack from Vianova - patching system to fix providers
  • WG call for interest and momentum.
  • Ride Report tool for providers to validate, willing to help
Clone this wiki locally