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

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)

Welcome - Brian Hamlin, SDOT (5 mins)
Announcements - Brian Hamlin, SDOT (10 mins)
- SMART Grants
- OMF Summit
- OpenAPI Progress
- EV Charging Decisions
Smart Dublin presentation - Smart Dublin and CurbIQ (10 mins)
Curb Objects - Brian Hamlin, SDOT (30 mins)
- Issue #123

WHEN: Wed, Nov 14th, 2023
WHERE: CoMotion LA'23
- Japanese American National Museum
- 100 N Central Ave, Los Angeles, CA 90012
Tickets are free for OMF members and are on sale for non-members
Register early to save your spot – tickets are selling fast and space is limited!

Currently have a draft version of the Curbs API in Open API under a feature branch
Work is in progress to finalize the Events and Metrics APIs
Should be able to present these in a future monthly meeting for public consumption

"Kicking Chaos from the Kerb"

Presenters:
- Payal Pandya - Dublin City Council
- Jacob Malleau - Product Manager, CurbIQ
Kerb Management
- Where is everything?
- Inventory mapping
- What should we use the kerb for?
- How do we keep data updated?
Dublin's Problem: There was no asset management system in place
Pilot area:
- Area covered: ~2.5 sq. Km
- Roads covered: 60+ Kerb Km
- Data points: ~4000 data points
Challenges & Learnings
- Biggest challenge is to keep the data updated on the maps. There could be three approaches to it
1. Update internally - Respective teams update their own assets on the map (Ideal)
2. Update externally - Survey the area on a regular basis (Quarterly or Half-Yearly)
3. Combined approach - Provide traffic order documentation to the service provider and they update the maps

CurbIQ is a SaaS solution to create, manage, and share curbside regulations in a visual and easy-to-navigate way.
Comprehensive solution
- Curb converter: Digitizes and standardizes city's regulations to align with an industry standard format (CDS) and to create open regulation data
- Curb viewer: Helps municipalities, businesses, and residents better understand their curbside regulations in an easy-to-navigate platform
- Curb manager: Helps municipal staff update regulations in a user-friendly interface and convey these changes effectively
- Curb analyzer: Lets users analyze the supply, usage, and revenues of curbside space to make more informed planning decisions
- Curb rules API: Disseminate curbside regulations to 3rd parties
Data collection
- Open data automation: Convert existing, geo-referenced data to digitized curb segments
- Curb-level surveying: Manual surveying of curb regulations through open-source tools
- Augmented mobile mapping: vehicle based to generate curb regulations

A direction that is being considered by the CDS Working Group Steering Committee
- Something that has been talked from the initial talks about CDS
- Resurfaced in response of the recent EV survey
Curb objects are a re-framing of "curb adjacent" to be considered "curb objects"
Curb object examples
- Utility box
- Bench
- Ramp
- Post box
- Bike rack
- Storage locker
- Electric charging
- Lighting
- Bus stop
- Food vendor
- Fire hydrant
Curb object properties
- Each object would have both basic and custom properties in the CDS Curbs API
- Standard would include properties such as name, description, and location to the curb
- Custom properties would support object specific attributes. Examples for signage may be purpose, text, owner.
Curb Objects - Discussion
- Thoughts on approach?
- Linear referencing vs. lat/long?
- Other objects you would like to see?
- What are some use cases for having objects standardized?
- Join the discussion in GitHub issue #123