Web Conference 2024.09.24 Curb

Web Conference - Curb Working Group

• Monthly on a 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

Meeting Agenda

SMART: CDS First Learnings

• Welcome (5 mins)
• Announcements (5 mins)
• First CDS Learnings from SMART - Mitch Vars, OMF
  • SMART Status and Implementation Reports - Em Burnett, OMF
  • Capturing SMART Learnings in GitHub - Mitch Vars, OMF
  • Minneapolis, Umojo
  • San Jose, Umojo
  • SFMTA

Organizers

• Hosts: Jacob Larson, Omaha
• Note Taker: TBD
• Facilitator: Mitch Vars, OMF
• Outreach: Mitch Vars, OMF

Action Items and Decisions

1. Get your OMF Summit tickets

Minutes

• 53 Attendees
• OMF Slides
• Recording - Password 3bDD??!#

Notes

• SMART Status and Implementation Reports - Em Burnett, OMF

  • Some SMART projects are starting to collect data from cameras and sensors.
  • Most have signed vendor agreements.
  • Challenges include integrating existing data into CDS and validating or determining data accuracy.
  • See the OMF SMART Resource Hub for more information on SMART funded projects
  • Mid grant summary report has been published with information on policy & regulations, procurement, technology suitability, data analysis, governance and more. Download available here.

• First CDS Learnings from SMART - Mitch Vars, OMF

  • Capturing SMART Learnings in GitHub - Mitch Vars, OMF
  • Overview of the importance of public input into the CDS development process.
  • OMF uses GitHub to develop and document OMF specifications. OMF’s development process is intended to emphasize openness, transparency, collaboration and consensus.
  • GitHub Issues are the first step in the CDS change process. Creating or commenting on GitHub issues is free and open to all. All interested parties are encouraged to open issues and participate in discussions. No technical expertise is required to do this. See a list of current Issues on the CDS GitHub repository for more information.

• Minneapolis, Umojo

  • Interested in creation of naming schema for automatic generation of human readable names for name field in Curbs API as opposed to UUID. Covered by Issue #148
  • Cites are interested in data on double parking events but current spec does not support the level of detail needed to track these events when they occur outside the curb lane. Issue #149 describes the need and potential short and longer term solutions.
  • Minneapolis is in the early stages of developing a “meta asset” tool within Cartegraph to automatically generate and update curb zones, using CDS, when changes to street signage are implemented.

• San Jose, Umojo

  • Umojo has proposed a number of changes on behalf of SanJose and other cities.
  • Camera computer vision data in Events API lacks meta-data, e.g camera ID, vehicle characteristics like color, make, model etc. Covered in Issue #146
  • Need a way to define cameras and sensors in Curbs API. Covered in Issue #147
  • Future API Plans: Add a lot more definition to the Metrics API - More definition of key metrics, standardized calculations, and optimal reporting definitions that we have found that customers like.

• SFMTA

  • Recommendation for flexible geometry type to allow linear reference (LR) in addition to polygons. Covered in Issue #151
  • Need for flexible classification of curb objects geometry allowing point, line or polygon
  • Curb policy priorities can be set using 10,20,30 as opposed to 1,2,3 to enable insertion of future policy priorities without changing existing priority.
  • Working on building a history of curb regulation based on historical INRIX data to inform before and after analysis of regulation changes. ...