Web conference notes, 2025.05.15 (MDS Working Group)
- Monthly on Thursday at 9am PT, 12pm ET, 5/6pm CET - open to the public
-
Zoom Registration and Join Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4
- One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)
- Signup to the Mailing List for emails and calendar invites
MDS 2.0.2 Patch Release w/ Blue Systems MDS/CDS Curb Parking in London
- Intro and announcements (5 min)
- Presentation (15 mins)
- MDS/CDS Curb Parking in London - Blue Systems
- MDS 2.1 Review and Feedback (10 mins)
- MDS 2.0.2 Patch Release Review (20 mins)
WGSC Meeting Organizers
- Host: Pierre Bouffort, Blue Systems
- Facilitator: Michael Schnuerle, OMF
- Preparation: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle, OMF
- Note taker: Michael Schnuerle, OMF
- Feedback needed: Policy real-time updates in PR #928.
- Policies must be unique. Is the current wording adequate to capture this and remain consistent with the rest of MDS?
- Feedback needed: #899, PR #931.
- Vehicle property changes. How to implement this in MDS?
- Vehicle lifecycle. Clarification of language for 2.1 so it’s not breaking. Could add new event type ‘start_of_service’ for future 3.0.
- Feedback needed: MDS 2.0.2 Patch Release 16 Issues and PRs.
- Comment on any concerns or issues by end of May
- 27 Attendees
- OMF Slides
-
Recording - Password
Ad?5mDm.
MDS/CDS Curb Parking in London
Voi and Lime are ingesting CDS Curbs API data to know about parking areas for scooters.
Sending MDS Agency API data back to cities about parking pay
Operators know more than GPS around scooter locations and which bay devices are parked in.
Designated Parking Only system. Must send ID of the bay you have parked the device in.
Blue Systems cross references info with GPS.
Optional event_geographies field made required in Events. Using UUID of the Parking Bay via CDS API.
Using the CDS Curb Zone UUID to send via MDS now, instead could be a new field in proposed 2.1 changes #731.
https://github.com/openmobilityfoundation/mobility-data-specification/blob/main/data-types.md#events
Status of entire city of London live for each bay. Also know overcapacity, low, good, empty, high, full.
Bridging the gap between MDS and CDS for the first time.
https://github.com/openmobilityfoundation/mobility-data-specification/issues/731 MDS and CDS alignment
Seattle looking to do this. How to pre reserve parking spaces in corrals? In Japan riders preselect destination to reserve space ahead of time - one operator https://luup.sc/en/ . Technically doable, some tweaks in MDS to make it right. Issue with multiple operators would be more complex.
Next step in London is share real-time availablity with operators. Currently it’s a burden/request for operators, but this is giving something back. Can display info to operators. Could send occupancy via CDS Curbs spaces.
LADOT Vlad is calling these ideas mobility hubs. CDS and MDS will start to merge and be one thing for operators. Manage real estate using the specs. Scooters, robot charging, AVs, carshare Blue LA - 200 parking locations, etc.
SFMTA Alex overlaps in concepts. Mobility hubs, on street or sidewalk. How to rep this location in specs.
How to reconcile Zone vs Stops. CDS can do it with a polygon on sidewalk with great accuracy, so Blue Systems went with that.
Stops could have also worked for showing capacity: can specify availability in MDS Stops and counts of vehicles occupying spaces and operational vs non operational.
MDS 2.1 Review and Feedback
Feedback on Policy real-time updates in PR #928
Feedback needed:
Policies must be unique. Is the current wording adequate to capture this and remain consistent with the rest of MDS?
Tracking Property changes in Vehicles
Opened in February, discussed in April #899, PR #931 from SFMTA.
Feedback needed:
Vehicle property changes. How to implement this in MDS?
Vehicle lifecycle. Clarification of language for 2.1 so it’s not breaking. Could add new event type ‘start_of_service’ for future 3.0.
MDS 2.0.2 Patch Release Review
Create a small patch release for MDS to collect easy and needed clarifications. 16 Issues and PRs
-
Update mailing list link
-
Update GBFS recommendation to 3.0
-
Multiple new provider IDs
-
Fix trip_stop event for two modes
-
Include stop_id in Events as intended
-
Conditionally Require three fields in Stops, if part of SLA
-
Ease some of the burden when creating 2.1
-
Finishing patch release after May 30, so leave feedback now
_Feedback needed: _
Comment on any concerns or issues by end of May
