Web Conference 2023.04.04 Curb
- Every other week Tuesday call at 9am PT, 12pm ET, 5/6pm CET
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)
Main Topics
- Curb related elements (EVs, parking assets, mobility hubs, etc.)
- User classes discussion
- Cross over of adjacent elements and user classes
- Open discussion
- Hosts: Jacob Larson, City of Omaha, Parking and Mobility
- Note Taker: Eric Mai, Lacuna
- Facilitator: Jacob Larson, City of Omaha, Parking and Mobility
- Outreach: Michael Schnuerle, OMF
- 36 attendees
-
Meeting Recording passcode:
@3mr.XfK - OMF Slide Presentation
- They announced 59 recipients of the first year phase 1 grants.
- 12 OMF member cities were awarded, including all 8 of our OMF Curb Collaborative group
- This is a big endorsement of CDS by the USDOT!
- There is a corresponding OMF blog post here
- ESRI products work with CDS now
- It won’t build out the full /curbs API endpoint for you but it will be a good start
- Review of last week’s discussion about linking existing curb spaces to EV charger data
- Issue 115 is the starting point
- A new class: On-street mobility hubs. Allowing scooter or bike docking. Would involve new geographies and policies
- A mobility hub could involve any combination of scooters, bikes, carshare, TNC dropoffs. Should each of those uses be categorized separately instead of being grouped into a “mobility hub”?
- CDS users can define their own terms if they’re not included in the standard lists
- Should we add a category for valet use?
- It’s generally helpful to have a standard list that can be expanded as needed
- Should we add descriptions of user classes? Yes, we should.
- How can we charge for short durations of use? We discussed an integer issue previously. Does that need to be resolved?
- We have two open rate issues: 106 and 116
- We could potentially support integer rates for short periods of use with a new field, which would not be a breaking change
- We can open a new issue in GitHub for this
- Is the current CDS definition everything you hoped and dreamed for or are there areas for improvement?
- Pierre Bouffant (Blue Systems) is still looking at implementing the first real life use cases of CDS. It’s too early to tell what they would need out of CDS in the future. The current spec covers the initial use cases pretty well.
- Everyone seems satisfied with CDS as it is currently defined and we’re just waiting for more use cases
- New issue on GitHub 116 raised by Populus - please take a look and comment. It’s simply adding a new field.
- Define when a policy does NOT apply. Not currently very well supported. They will propose a new way: take the existing
TimeRangesconcept but add a boolean indicating whether the time range is an exception (meaning that the policy does not apply at this time) or not This is a more substantial change. Has anyone run into this issue yet? Doesn’t sound like it. - Stefanny Perez (CurbIQ) thinks exception schedules could be useful for regulations around things like snow emergency zones.
- For Populus, the first place it comes up is holiday schedules.
A lot of companies and agencies are just starting down the path of implementing CDS. As we all start to work with CDS more, don’t hesitate to ask questions as they come up. You don’t have to wait for a working group meeting to share questions or comments! Just reach out to Michael or Jacob. There will be more questions and issues as we get into the meat of the work more.
