Joint Working Group - Provider Services

NOTE NEW TIME TWO HOURS SOONER

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

NOTE NEW ZOOM MEETING ID/LINK/PHONE NUMBER

Meeting ID: 671 331 832 - https://zoom.us/j/671331832

One tap mobile: +19294362866,,671331832# US

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Add your own name, link, and organization during call

• Michael Schnuerle, OMF
• Jonathan Internicola, NYC TLC
• Kegan Maher
• Neil Goldader, E&A
• Josh Johnson, Spin
• Bill Dirks, Ride Report
• Mitch Vars, Mobility Data IO
• Matt Davis, Populus
• Alex Demisch, SFMTA
• Steve Brining, Blue Systems
• 30 attendees

• Issue: #480, PR #503

• Ride Report will run through part of presentation given to OMF Privacy Committee. Cover context, motivation and example use cases.

• Update on resolved comments/issues with E&A

  • Merged upstream geometry changes from dev
  • Fixed potential for stale geometries
  • New event types
    • Mini-discussion: Two events vs one
    • Suggestion: No heading/speed/accuracy data in GPS. File a new issue or building on #51.

• policy events public - #585. not necessarily required but def related. Cover how we see these two PRs working together.

• How to make this a non-breaking change? Make new events type only conditionality required

  The only aspect of this that is a breaking change is that it is implicit requirement for issuing the new events. From my view, these events should only be required for agencies/providers that opt for policy-driven events (as a beta feature and/or in lieu of full route data). Discuss ideas for how we can make this distinction explicit in the specification.

• If time, cover future work around: MDS Policy "data contract"

Notes and or transcript of the call with presentation, document, GitHub links and calls to action

William at Ride Report presentation

• Cities need real time control to adapt quickly, create pricing fees and subsidies, and look forward to modes like ride hailing
• Need realtime vehicle info, flexibility, use cases that change over time, to play nice with current implementations, to work within MDS and not make a new fork, and a way to audit data.

Policy Driven Events Proposed changes

• 2 new event types. Trip enter geography, trip leave geography. Could collapse into Cross geography instead.
• A new event geographies field listing all geo ids that apply at that moment for that vehicle
• Event_location becomes optional Other changes
• Public policy endpoints for accountability and transparency
• Data contract idea for cities - will need to create a separate issue/discussion
• Telemetry additions of speed and accuracy across MDS added for 2.0 with issue #51

Discussions

• Rename the proposal to ‘Geography Driven Events’ to reflect that for now the actions are triggered when vehicles enter or leave a geometry, and geometry IDs are returned.
• If you use GDEs, then cities are required to make policy and geography public and communicate the URLs to provide public transparency in the policy and geographic areas, and reduce authentication burden on providers.
• This is structured to be a non-breaking change for 1.1.0, and so it can be tested with minimal disruptions.
• Agreed that 2 fields (enter and leave) are better than one (cross).
• There is no order to the list of geos returned, just an unordered array of IDs
• Added note that new policies can’t be expected to be implemented until 20 minutes after publishing to prevent frequent or real time changes. 20 min delay is good for some more emergency policy situations, but most policy will be communicated days or weeks ahead of time.

Beta and testing for 1.1

• This will be labeled as beta to allow cities and providers to try it out and give feedback
• Beta designation will also also providers to see what their technical burden is to implement and run in production
• Language needed to clarify that policy driven events only apply when you opt into this and discuss with provider and city.
• Can be run in parallel with all existing MDS if desired by cities. So you can turn on GDEs and other telemetry, or turn on GDEs and turn off telemetry, or just use telemetry as it is in 1.0.0.
• Could lead to lots of geography creation if telemetry option is turned off
• Could be issues with GPS in precision float and boundary riding, returning too many events. May need smoothing of data.