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
• Wiliam Henderson, Ride Report
• Mark Maxham, E&A / LADOT
• Neil Goldader, E&A
• Jack Reilly, Vianova
• Steve Brining, Blue Systems
• 18 attendees

Main Topics

1. Stops in Policy

2. Making Policy/Geo public

3. Geography 'Type'

4. Jurisdiction followup

5. Other Items

   • Adding retire date to geography
   • The idea of requirement/necessity to rule types in policy
   • Discussing 1) modifying the state machine and 2) describing non-trip movement.

Next Week

• Geography Driven Events
• Metrics

In Two Weeks

• Release 1.1.0 Finalization Review

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

View full detailed minutes and screenshots here

Stops in Policy

• Jack from Vianova, wants to allow parking in spray painted areas only in a city. Could be done with Rule Layering with ordering. 1st permits in regions, then 2nd not permitted. Need example of how it could be done now.
• Action: Jack added example here.
• Discussion:
  • Could add Stops row in location.
  • Where are stops defined? Stop Id in rules for policy? Jurisdictions. Remove geography info from stop, reference a geography instead?
  • Rule has stop id as well. Geographies can be omitted. List of stop ids.
  • Layered ruling is required to forbid, else stops can be optional.
  • Define stops, add rules.
• Action: Add optional stops to rules (like geographies). Need a PR. Michael can start. If stops then geography ID required.

Geography

• What is geography (a point, a polygon)?
• Action: Need to clarify no points or specify in spec a buffer around any points. Geographic data in general info - polygon. Point in route for stop. Connect to geography for stop as a feature collection. Change example from point to polygons for stops in Geography. Change location field to describe polygon or point (just point now).
• Kegan and Neil - points are what some cities make by default, could be changed polygons though. Buffer - if you encounter a point in the data (eg, 30ft)

Beta

• Action: Update beta general language to include breaking changes. Michael

Recommended rule type

• Willam at Ride Report. Preferred parking. New rule type? Recommended, necessity, requirement?
• Informational benefit.
• Action: Need to define use cases. Please add to issue #557.
• Not sure of consensus.

Geography type

• Stops are in there and defined. Stops are fine here, not really a policy.
• Will operators understand it? Confusing? Will operators use it?
• Can use name and description, need a way to make it easy to filter.
• Sherie Tan, San Jose - sees value in types - wants them in policy. (Andrea moving to new position)
• William look at use cases, give me all the geo or policy that is relevant.
• Address querying in Metrics.
• Maybe query Geographies by type could be added later. List of types in geography possible later.
• Worry is that cities may just run with this Geography and not do Policy and try to make it work like policy.
• Action: roll policy types into new geo type (geofence/policy_zone)

Policy/Geo Public

• William would like to see making it public required. Michael says that would be breaking, but can be in the next release. Current wording says it may be required in next major release. Leave your thoughts if you have an opinion.

Did not discuss

Leave thoughts on issues directly, as we may not get to these next week.

• Jurisdiction follow up
• Adding retire date to geography
• The idea of requirement/necessity to rule types in policy
• Discussing 1) modifying the state machine and 2) describing non-trip movement