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

Web Conference - Curb Working Group

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

Conference Call Info

Meeting ID: 898 5980 7668 - Passcode 320307
https://us02web.zoom.us/meeting/register/tZ0lcuCgrjwsHNyZRagmc86b12iCmWGBHfjq

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. Welcome (5 mins) - Jacob Larson, Omaha
  2. Curb and CDS Presentation 1 (20 mins) - Omaha (w/ Coord, Populus, Automotus, Vade)
  3. Curb and CDS Presentation 2 (20 mins) - LADOT (w/ IBI Group's CurbIQ)
  4. Q&A (10 mins)

Organizers

  • Hosts: Jacob Larson, Omaha
  • Note Taker: Zane Clark, Automotus
  • Facilitator: Michael Schnuerle, OMF
  • Outreach: Angela Giacchetti, OMF

Recap

Notes

Action Items

  • None

Minutes

Who is using CDS, part 3

Overview of CDS:
  • Final review for 1.0 release is underway
Jacob Larson Presenting on behalf of Omaha:
  1. August 2020: 3 month pilot w/ Cord
    • Smart loading zones
    • QR codes on sign posts
  2. 2021: 3 month pilot w/ Populus
    • Useful to have historical data
    • Could filter by a number of useful dimensions
  3. 2022:
    • Vade Pilot
      • 1 year bike lane pilot
      • 3 month curb pilot
    • Automotus Pilot
      • 1 year commercial loading zone pilot
  4. What's next?
    • CDS Rest API
    • ESRI is the source of the data, but they don't play nice w/ CDS yet. Lot's of interest on this in the meeting
Tom Carranza (LADOT) and Jacob Malleau (CurbIQ):
  • Code the curb: digitize curb assets
  • Initiative has been around since 2014. We went through this bit pretty fast and the slide deck has very detailed information on the subject. I'll defer you to that source of information for the timeline
  • 2019: Cambridge Systematic engagement
    • completed work arrived during the pandemic
    • three volumes:
      • scoping study
      • asset management plan
      • executive summary
      • tldr: should be able to achieve objectives in 5 years if properly resourced
      • COVID resulted in some priority shifts and a lack of proper resources
  • Pursuit of Partnerships and Grants
  • Phase 1 is complete, 2 more pilots underway
  • Two grants:
    • DOE
    • Curbspace Inventory Program grant
  • CurbIQ LADOT engagement presented by Jacob Malleau
    • Available Curb Digitization Strategies:
      • Open Data Automation
      • Curb-Level Surveying
      • Augmented Mobile Mapping
    • Is there a curb digitization strategy that's scalable?
    • Experiment:
      • Use curb-level surveying on 4 neighborhoods as a control
      • Compare those results to augmented mobile mapping results
    • Results:
      • There's an inverse relationship between density and augmented mobile mapping accuracy
    • Conclusion:
      • In low-density areas, use augmented mobile mapping. That's ~90% of LA
      • In high-density areas, use curb-level surveying
      • This approach would result c 5x faster collection
    • After curb digitization, how do we make the most of that information?
      • CurbRules API converted to CDS
      • Additional value-add apis that offer value to operators
Q+A
  • Brian H.: Once you have the data on a digitized curb, how are you going to keep it up to date?
    • Tom C.: The current phase investigated the cost and accuracy of digitization methods. We're going to tackle that problem next.
    • Jacob M.: It's common for us to work with cities that only have snapshots of curb digitization data with no updates perform after the snapshot.
    • Zane: Should look at adding specific APIs or recipes to CDS for usage of data like in Curb IQ
  • Alex D.: Do you ever update and verify existing information instead of taking a brand-new inventory?
    • Jacob M.: Sure. We can update and verify or take a new snapshot.
  • Elias K.: Do you use your staff, or CurbIQs staff?
    • Jacob M.: Depends on the situation. We can collect and process, collect, or process
  • Brian H.: Will Omaha continue to use ESRI, or move away?
    • Jacob L.: Backend uses ESRI. We're likely stuck with it.
    • James DC: Approach ESRI for getting them on board collectively
  • Zane C.: Best practices for other cities?
    • Tom C.: Partnerships were critical
    • Jacob L.: Same here. Also, there's a world beyond digitizing the curb. Lane closures, construction, etc.