-
Notifications
You must be signed in to change notification settings - Fork 243
Web conference notes, 2024.08.29 (MDS Working Group)
Michael Schnuerle edited this page Aug 29, 2024
·
8 revisions
MDS Working Group
- Monthly on Thursday at 9am PT, 12pm ET, 5/6pm CET
Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4
One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom
MDS 2.0 for Taxis in LADOT
- Intro and announcements (5 min)
- MDS 2.0 for Taxis in LADOT
- MDS for Passenger Services (5 mins) - Michael Schnuerle, OMF
- History and Taxi Companies (10 mins) - Pierre Bouffort, Blue Systems
- Vision and Integration (20 min) - Jarvis Murray, LADOT
- IATR - Matthew Daus
- SFMTA and CPUC - Julia Friedlander
- Discussion and questions (20 min)
WGSC Meeting Organizers
- Host: Pierre Bouffort, Blue Systems
- Facilitator: Michael Schnuerle, OMF
- Preparation: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle, OMF
- Note taker: Craig Dittman, San Jose
- ...
- 65 Attendees
- OMF Slides
-
Recording - Password
wK6UA6*W
Overview of MDS 2.0 for Passenger Services:
- Development of MDS 2.0 took over a year, focusing on standardizing data fields already collected by cities for taxis and rideshare services.
- MDS 2.0 simplifies the data collection process by providing a standardized format, reducing the need for cities to request similar data in different formats.
- The release includes guidance on how to use MDS for passenger services, with recommended language for requiring the latest version of MDS for publishing digital policies and collecting vehicle information.
- Operators and public agencies can use MDS to meet permit requirements and manage data collection. This can be done internally or by hiring vendors, aligned with defined use cases.
Integration of the Taxi Industry with MDS:
- Collaboration with LADOT and Blue Systems focused on integrating the taxi industry with MDS 2.0.
- The integration process was designed to be as seamless as possible, minimizing the effort required from taxi companies while meeting LADOT’s needs.
- The main challenge was acquiring basic data, such as vehicle registration and trip details. LADOT now requires taxi companies to comply with MDS, specifically MDS 2.0.
- Future plans include developing a fee structure to cover the costs associated with submitting data in near-real-time, ensuring sustainability for taxi companies.
Technical Aspects of Integration:
- Initial integration efforts focused on minimizing the burden on taxi companies by leaving out certain features, such as fare rates and trip types beyond passenger trips.
- Vehicle registration data was simplified, and some optional features, like accessibility and propulsion information, were not fully implemented.
- These decisions allowed for a quicker integration process, though they limited some use cases. Lessons learned from this integration have informed future versions of MDS.
Current Status and Future Directions:
- The current integration provides the same level of information as more mature MDS integrations, like those for micromobility.
- By using the same data visualization tools across different modes, LADOT can better compare and analyze data from various mobility programs, including taxis.
- Efforts are ongoing to integrate TNCs (Uber, Lyft, Flywheel) into MDS. Initial progress includes data sharing through partnerships with companies like Curb.
- There are signs that the TNC industry is becoming more open to data sharing, which could lead to further collaboration in the future.
Closing Remarks:
- LADOT emphasized the importance of this work, particularly as taxis remain a significant part of the transportation ecosystem despite the rise of TNCs.
- The integration with MDS will help LADOT manage transportation more effectively, with the potential for expanded use cases as more data becomes available.
MDS Links
Working Groups
2.1.0 Release
0.4.1 Release Planning Meetings
