Web Conference, 2020.06.04 (Provider Services WG)
- Every other week call at 11am PT / 2pm ET
Meeting ID: 627 957 166
One tap mobile:
- +16699006833,,627957166# US (San Jose)
- +19294362866,,627957166# US (New York)
Dial by your location:
- +1 669 900 6833 US (San Jose)
- +1 929 436 2866 US (New York)
Find your local number: https://zoom.us/u/aeJWJsuC2b
Add your own name, link, and organization during call
- Michael Schnuerle, OMF
- Bill Dirks, Ride Report
- Heidi Guenin, MobilityData
- Kegan Maher
- Josée Sabourin, MobilityData
- Michael Durling, E&A
- Neil Goldader, E&A
- ...
-
Reconciliation Naming Options
- Opinions on the two open naming questions in the Reconciliation / ensure everyone has seen the #506 PR
- on_trip (vs trip) and non_operational (vs unavailable) are the consensus
-
Docked
- See if we can decide on a direction for docked micromobility for 1.0.
- PR #427
- Issues #374 #427 #438
-
Optional API Fields
- Discussion of ideas around optional (geolocation) info and proposal for dynamic field exclusion #507.
-
Release 1.0.0 timing and feature inclusion
- Move from June 15 to June 29
- Proposed for 1.0.0
- Proposed for next release (1.1.0) after discussions
Notes and or transcript of the call with presentation, document, GitHub links and calls to action
Audit
- would like to get it in 1.0.0. In production in LA as it is now in the PR
- E&A will clean up the PR to get it ready
Reconciliation
- Max making updates, the marking it not draft after agreed name (on_trip, non_operational) changes made
- Max clarify state machine docs w/ regards to phantom states and transient events.
- #509 - state machine updates
- Sharada DC - emergencies, need something for this and weather events, etc. service_closure and service_resume could work.
- PRs need to be linked
Docked
- GBFS alignment is agreed upon where possible
- #508 mention vehicles endpoint
- link to guidance doc
- authenticated GBFS not likely in short term
- What's left in PR #427? OMF to leave comments and summarize.
- If it's defined enough to use it can be beta, otherwise push to next release (no alpha states)
Policy: Fees
- OMF in Github summarize and everyone comment
Exclude fields
- Dirk points out it breaks pre-calculated data, comment in Github
- Would make schemas hard to validate
- Maybe if only trips is optional that could work since that is just double the pre-calculated data
- William maybe Policy API could be used as cities/providers agree on list of fields to provide?
