Web conference notes, 2020.05.07 (Provider Services wg)
Web conference notes, 2020.05.07 (Provider Services wg) - Docked Micromobility Session
- biweekly call at 11am PST / 2pm EST
- Join Zoom Meeting https://zoom.us/j/627957166
Meeting ID: 627 957 166
One tap mobile:
- +16699006833,,627957166# US (San Jose)
- +19294362866,,627957166# US (New York)
Dial by your location:
- +1 669 900 6833 US (San Jose)
- +1 929 436 2866 US (New York)
Find your local number: https://zoom.us/u/aeJWJsuC2b
- Brady Law (Lyft Software Engineering)
- Heidi Guenin (MobilityData IO)
- Tim Millet (MobilityData IO)
- Jascha Franklin-Hodge (OMF)
- Neil Goldader (E&A)
- Eric Mai (E&A)
- Michael Schnuerle (OMF)
- Bill Dirks (Ride Report)
-
Michael Schnuerle - Intro Director of Open Source Operations role
-
Discuss Working Group Steering Committee structure: 5 contributors voted in by WGSC members. Fill in membership per the charter.
-
Issue #374 - Docked Bike Share Systems
-
Issue #428 - Modify /trips to represent docked start/end locations
-
Issue #438 - Modify /status_changes to represent docked event locations
-
GBFS approved approach to dockless /stops PR #219
-
Proposed Approach #1: New /stops endpoint
- PR #427 - MDS-Provider Stops Specification
-
Proposed Approach #2: New /stations and /station_status_changes endpoints
- PR #441 - Add Docked Bikeshare Systems to MDS
-
How do we align our approach with the work being done by MobilityData on virtual stations and geofencing in GBFS? (see NABSA/gbfs#219) How does GBFS approach to geospatial references align with MDS Geographies?
-
Does our approach to adding per-vehicle-type capacity/availability information make sense and align with direction of GBFS?
-
Do we need an historical view of station status available via MDS? If so, should it have its own endpoint or be supported through an existing endpoint?
-
How to best share common data types (like stops) across multiple MDS APIs?
