Web Conference 2021.05.18 Curb - openmobilityfoundation/curb-data-specification GitHub Wiki

Web Conference - Curb Working Group - 2021.05.18

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

Conference Call Info

Meeting ID: 898 5980 7668 - Passcode 320307
https://us02web.zoom.us/j/89859807668?pwd=ZzJrbEpTNVB4WkNqNiszcmFYVzBwZz09

One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)

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

Agenda

Main Topics

  1. Introduction to Curb Data Specification
    • OMF Curb Connection - Michael Schnuerle
    • History - Brian Hamlin
    • Scope of Work - Brian Hamlin
    • Timeline - Michael Schnuerle
    • Getting Involved - Angela Giacchetti

Organizers

Minutes

Presentation Notes

OMF staff, Michael Schnuerle and Angela Giacchetti, and Curb WGSC Chair, Brian Hamlin, presented CDS Implementation Phase scope overview and ways to get involved.

  • OMF connection to curb - vision for curb aligns with existing OMF objectives
  • Many diverse members that can contribute to curb work
  • Real world use cases are the focus
  • MDS - APIs that connect local cities to mobility companies
  • Involvement - Required players
    • Cities implementing loading zone pilots/programs
    • Curb users - commercial entities using curb area data from cities and sending usage data back
    • Tech companies building tools to help - publish regulations, ingest event data, analyze utilization
  • Commitment of resources to help develop and test together
  • Welcome orgs deploying current or future curb pilots to leverage the spec while informing continued development of CDS
  • Curb pilot ideas
    • Commit to producing regulation and event data
    • Use data to meet specified use cases
    • Relay feedback on success and issues
  • Two ways to participate: individual contributors + member orgs (don't need to be an OMF member to participate)

Questions and Answers

Brian, E&A - How do you see this relating to MDS especially as policies or geography may intersect?

  • Michael, OMF - TBD how it will play out. There could be some overlap between both specs. Cities can digitally express specific curb areas, for example, then use those IDs in MDS in the future. MDS Policy API connection - cities to state what's allowed vs what's not plus fees/incentives, offering some overlap potential. Same with Geography and Jurisdiction APIs. Short term overlap solution - curb ID referencing a curb regulation in CDS. Can go from MDS to refer to something in CDS (speculation but potential path).

Ellie, Waymo - how are cities socializing the work with colleagues across department as pilots will take multiple teams to implement successfully? Will everyone be aligned? Ellie works with SF AV team now; are they in the loop on this?

  • Kenya, SFMTA - He's been socializing it in the city. Larger effort to develop digitization for all sorts of assets and curb tangentially included. Hasn't yet socialized with AV team but will. Looking at OMF/CDS pilot as a part of a larger vision.

  • Elias, San Jose - not at a point to be ready to involve other depts. Maintain some level of independency from other dept like IT for now for better pilot control and flexibility.

  • Brian Hamlin, SDOT - Prelim stage of engaging teams to pursue a CDS pilot and socialize the need for this. Initial support voiced.

Regina Clewlow, Populus - how are we all getting cities engaged? Working with cities not necessarily involved in OMF now. Happy to facilitate that and rep them in this pilot process.

  • OMF is increasing outreach to cities and we hope more get involved. For the pilots we don't need everyone. What we could use more of are private company curb users who commit to working with cities and CDS.

Sarah Abel, ITE - How are you building off of tools already developed?

  • Brian Hamlin, SDOT - aim to get a collaborative approach going - perhaps cities can join forces to pilot especially if they have the same vendor in common.
  • Angela Giacchetti, OMF - potential to create a 'pilot clinic' to offer support during project.
  • Krute Singa, MTC - submitted a Caltrans planning grant to offer tech assistance via policy toolkit and online apps and tools including CDS. Bay area. Will know more in the summer
  • Michael Schnuerle - the Discovery Phase had us look at SharedStreets, CurbLR, T4A, Coord, APDS, Urban Freight Lab, Automotus and some linear referencing work, among other areas. Welcome more exosystem examples and discovery/alignment will come in the working group's efforts.
  • Sarah shared practitioner's guides and links:

Stephen Hanrahan, NYC - What would a pilot include? Any examples?

  • Jacob Baskin, Coord - smart zones bookable via app that let you see availability; work with cities to do a smart zone deployment. Check how it was regulated before v. how it's regulated once smart zone established. Communicate smart zone to users in area. Define regulations in a standard shared format that's cross-country, cross-city. Working closely with WG on this project that's a moving target. How to obtain availability information - some cities place sensors, some use cams. Ideal to have plug & play solution so it works regardless of vendor or platform. Pilot would commit to consume the data.
  • Automotus - Determining vehicle dwelling for X time or vehicles double parked and other metrics using video analytics
  • Michael, OMF - recall the scope of work outputs - regulations, events, metrics including dwell time, occupancy and usage