Web conference notes, 2020.10.29 (Joint Working Group City Services)

Joint Working Group - City Services

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)

Attendees

Add your own name, link, and organization during call

Jurisdiction API
- Issue: #491
- PR: #593
Release 1.1.0 Status
- 2 weeks left to finish all PRs and have agreement on code, 1 to finalize release
- Will cut features instead of extend release timeline, per the Working Group Steering Committees' Consensus Checkpoint last Fridays
- Next two meetings will be about last minute discussions around open issues and work

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

Jurisdiction

Brian Ng presentation

LA and Miami-Dade - communicate boundaries between jurisdictions
Some agencies manage overlapping jurisdictions
Not exactly Policies and more than Geographies
It's an agency’s authority to the outside world
Includes name, id, purview of physical and modal boundaries
- Eg LA taxi jurisdiction is different than micro mobility, city/county map example
Revisions need to be tracked.
Both agencies and providers can consume this
Currently doing this by email
Could tag a geography, or maybe info type in policy, but these have limitations
Clarifies overlapping authority
Miami-Dade contracts with a company to manage MDS for 34 cities in the county.
Requires a stable id, discoverability, associated geography, mobility mode, revision mechanism
This PR 1.1 version
Mobility mode is not officially part of MDS. Not part of spec but internal list.
Future: Could be part of modes in MDS, public list of jurisdictions by OMF, public list of agency ids, metadata
Scope: non public by agency. Consumers: agencies, county, transportation org, providers

Conversation

Joseph Yawn - interface across MD. Could layer on roles.
Sanjiv - benefit? Structure is important
Bill ride report - use policy instead? Possible but it's a bit limiting.
Bird - not convinced adding another layer of complexity to policy/geo right now. Could be a burden for providers.
E&A, LADOT - valid use case in LA, M-D.
Sharada - capital bike share 6 jurisdictions, state lines. Could be useful in DC.
Andrea - San Jose. Good for certain larger cities, but also San Jose could be useful for smaller cities and other modes in the future
Alex - SF Bay Area, golden gate park, presidio sub jurisdictions. Thinks good to put it out there now.
Max - optional for anyone to use. Can solve these now with API, beta, optional. Kit of parts.
Michael OMF - is it optional for cities? Yes.
Michael OMF - How do cities agree to this and who would serve file? SANDAG, regional body. Self organizing so far.
Is agency_key universal? Jurisdictions response is the list. MPO or agency maintains the list. Could be OMF maintaining it later, like with Provider IDs.
Agency key in geography? Geography is only one attribute of an agency. Want a stable id.
Could it be Public? Eventually yes, but authenticated for now
Brian - different agencies in SF area with different modes.
Alex - is it important enough to have its own API. Likely.
Ben - keeping geographies clean is a good idea. Left a comment about that in discussion

Other Points

Providers could look up who has authority.
Providers benefits: Not getting data by email, but structured by API. Would love feedback from providers.
Will get a beta designation
Could be more valuable in the future, this is a simple first step
May be beta and optional and simple and ready for 1.1.0 as long as we get some community feedback on the PR in the next 2 weeks and resolve any discussions brought up there.

Metrics

Updated with links to geography and with feature branch updates. See #594

omf-mds-github-footer