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

https://zoom.us/j/671331832

Meeting ID: 671 331 832

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

• Henri Bourdeau, Blue Systems
• Michael Schnuerle, OMF
• Kegan Maher
• Mark Maxham, E&A / LADOT
• Jascha Franklin-Hodge
• about 25 attendees

See minutes from Provider WG meeting last week.

1. New items
   • Self driving vehicle, off trip movement, delivery bots #521
2. 1.1.0 items (Release Plan)
   • Metrics: Catalog of known city reporting requirements, street-segment metrics #556
   • Currently at end of proposal phase and starting implementation and coding according to release process
   • Geography API #498 - will be proposed soon since so much else is dependent on it.
   • Recommended rule type #557
   • Policy-driven events #480
   • Policy Schema #573
3. Still time for new ideas/proposals for your city/company in Github.

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

• Self Driving Vehicles #521
  • Example: Repositioning scooters for maintenance
  • Moving 1-2 blocks in San Jose now, could be much longer and pull cargo, delivery
  • Could apply to any vehicle moving on its own.
  • Add trip type or trip purpose as a field? (delivery, rebalance, cargo, etc).
  • Atlanta - likes the idea, good to be broad, can cover drones too
  • Blue Systems can speak to their case with Kiwi bots in San Jose.
  • Henri will create a new issue for delivery bots (keep this issue for off trip movement discussion)
  • Would need to add a new vehicle type
• Jurisdictions #492 - need to be added in as part of 1.1.0 release plan
• Metrics
  • note list of existing city use cases compiled as a comment on the issue. Add more.
  • Street segments #556
    • blue system has uses for it. E&A looked at it but it's a big discussion.
    • What is a street segment, how to work with linear referencing?
    • welcome comments and data model discussions.
• Rule Options
  • agreed to add a field at policy level to enumerate as required/recommended/optional
  • What to call that field? Enforcement, stipulation, rigor, condition, provision?
• Policy Schema #473
  • use the issue to discuss null or omit optional fields
  • Support for both in 1.1, pick one to support in 2.0