MDS Working Group

• Every other 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

Note: Attendees register upon entry into the Zoom meeting. An attendee count will be posted here after the meeting:

22 Attendees

Main Topics

MODES MONTH Blog Post

• SFMTA: review current data process, regulatory authority, use cases, and overview of data collected
• Passenger Services: proposal review
  • Pull Request with comments from cities
  • Planning Document
  • Active work browsable in feature branch

Part of Modes Month.

WGSC Meeting Organizers

• Host: Sebastian Berthaud, Blue Systems
• Facilitator: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF
• Note taker: Steve Brining, Blue Systems

1. ...

• Slide Presentation
• Meeting Recording - Passcode 6BC5!CLK

AD - Gave an overview of the SFMTA taxi program (insert link if available)

• Noted they are also a taxi regulator and that AD is in the Streets Division for SFMTA

• SFMTA took over the taxis role in 2009

• Noting 10 guiding principles for mobility services

• Taxi and Mobility Services Division

  • Grew to take on regulated mobility, like Google busses and private shuttles
  • Rely on data to run program

• Data Reporting Requirements

  • 2013 – developed Taxi Data Specifications and developed Electronic Taxi Access System

• Data required

  • Data collected with Trip API and Telemetry API
  • Trip API similar to MDS Trips endpoint

• Section Review: What is Trip Data?

  • Noting more fare information than MDS
  • Noted DL for driver to use for investigations

• Section Review: What is Telemetry Data?

• Telemetry API

  • Helps to investigate complaints
  • Checking out longhaul complaints
  • Has analytical purposes

• Discussion on MDS Passenger Services Mode

  • SFMTA doesn't have the authority to collect data for TNCs at this time

MS - Modes Month for Passenger Services Discussion

• review of Modes Month Schedule
• Noted that by end of September we should have a better idea of what will be included in MDS 2.0, as Modes is the bigger focus for this release

Mode: Passenger Services

• Proposal review
• Slide Presentation
• MS – reviewing work to-date on PR 763
  • https://github.com/openmobilityfoundation/mobility-data-specification/pull/763
  • Request for feedback in the pull request
• What’s in MDS now
  • Noting data that’s possible vs not possible in MDS today with respect to new modes
  • Need for updated trip structure for bots and taxis
  • Extra more specific information is missing that is used to describe trips, including fare information, including information required by law, like license plates and/or driver information
• Reviewing data Agencies receive now, noting not all will be defined in MDS 2.0
  • Trips – passenger count, cancellations, etc
  • Vehicles – license plate, vin, etc
  • Fares – fare type, trip cost, etc
  • Drivers – driver license
• Reviewing MDS 1.2 policy requirements example
  • With Requirements, cities can say which parts MDS are required to operate in a city.
  • MDS required fields allow cities to digitally describe that they need, and can also include optional fields.
    • Note: can disallow required fields if necessary, due to preference of city, or local laws/requirements.
    • Every agency can customize to their needs.

Passenger Services: Trip Types

• Review of various trip types that could be accommodated: private, shared, reservation, empty Passenger Services: Journey
• Review of a journey structure, new concept for MDS 2.0
• Can cover overlapping trips Passenger Services: Trips
• Review of modes-specific fields including hail_type, pickup_address, driver_id, passenger_count, etc Passenger Services: Vehicles
• Details about the vehicles being used Passenger Services: Accessibility
• Currently only for wheelchair, may need more

Discussion Starters:

AD- The concept of how to define a journey for passenger services still seems pretty loosely defined. Are we thinking that we just keep it flexible and let implementing agencies define how to use it more specifically? VG – Thinking people interested in mobility hubs may be interested in the modes interacting with them. MS – asking about accessibility Danny Yeung – noting assisted services DY – should we be able to add subsidy?

• MS – will operator know it’s a subsidy? Was thinking of a discount vs the trip type being subsidized by the city for mobility challenged riders
• DY – we’d know on the backend MS – any other questions on vehicles
• MD – asking about drive (ICE, hybrid, etc)
• MS – already possible in MDS today
• Noting that CDS curb spec also has a more detailed list of vehicle types