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

CDS Working Group

Agenda

  • Welcome (5 mins)
  • Announcements (5 mins)
    • Upcoming Events
  • LPR for enforcement and occupancy - SFMTA (15 mins)
  • Discussion of Current GitHub Issues/PRs - Mitch Vars (30 mins)
    • Real-time availability data in the Curbs API
    • Edge Cases for Parking Policies
    • Designating Driveways in CDS

Organizers

  • Hosts: Jacob Larson - Omaha, Kenya Wheeler - SFMTA
  • Note Taker: Mitch Vars, OMF
  • Facilitator: Mitch Vars, OMF
  • Outreach: Mitch Vars, OMF

Action Items and Decisions

  • Umojo will open GitHub issue for real time availability change suggestions
  • Need issue for capturing special regulations in parking policy
  • Need issue for driveways breaking up zones

Minutes

Notes

Curb Working Group Intro and Announcements

  • Kenya Wheeler (KW) opened the meeting and introduced CDS

  • Angela Giaccetti (AG) gave an overview of upcoming events that OMF will be attending. The calendar of upcoming events can now be found on the OMF website.

  • Michael Schnuerle noted that IPMI will be in Louisville this year and OMF will be hosting Open Mobility Mixer in the city.

Presentation: LPR for enforcement and occupancy - SFMTA

  • Presenters: Alexiy Sukenko (AS), Kenya WHeeler (KW)

  • San Francisco was initially 100% pay-by-space but has transitioned over the past few years to approximately 50% pay be licence plate technology

  • Enforcement is done with ~100 mobile LPRs

  • No longer doing physical chalking of vehicles, virtual chalking is done via LPR

  • LPR readings are sent to cloud so that enforcement can be done across shifts by any LPR vehicle.

  • LPR units are also used to measure curb occupancy by capturing GPS position of parked vehicles.

  • LPR data has been validated by comparing LPR readings with Go-Pro recording of vehicles from same LPR vehicle.

  • Each day ( Mon-Sat) is divided into 4 time bands: 9am-noon, 12-3pm,3-6pm,6-10pm

  • Each time bad requires 6 LPR vehicle passes to capture occupancy data, 24 per day, 144 passes per week Mon-Sat.

  • Occupancy rate is calculated every 3 years

  • Occupancy data is used to calculate demand responsive rate pricing.

  • When occupancy is >80%, rates are increased, <60% rates are decreased

  • Because LPR occupancy measure a point in time, it is used as a coefficient with payment rate to determine pricing.

  • Brain Hamlin (BH) Is LPR work done by enforcement vehicles or are these dedicated LPR vehicles?
    (AS) They are dedicated to LPR because enforcement vehicles would not be able to complete the required number of passes to capture data.

  • When a block face contains multiple regulations, LPR GPS is not accurate enough to determine exactly where vehicles are. GPS coordinates must be supplemented by AI to know where vehicles are and when regulation to enforce.

GitHub Issue & Pull Request Review

 Real time availability

  • Rick Neubauer (RN) from UMOJO: CDS specs lacks a good way to communicate real-time availability of parking. This is particularly true in cases where only zones are defined and not individual spaces.

  • Would like to have a lightweight solution that doesn't require querying the Curbs API which is primarily regulation data.

  • Could be push notification or webhook to make it more efficient

  • Separate endpoint from Curbs API so that it only contains occupancy data 

  • Might be better suited to Events API - would be a breaking change

  • Michael Schnuerle (MS) could be achieved with a new query string parameter that would filter for just availability data - this would be a non-breaking change 

  • Stefanny Perez (CurbIQ) suggested that a POST method could be added to the Events API for more efficient real-time data flow

  • RN will open GitHub issue for further discussion

Edge Cases for Parking Policies

  • RN - UMOJO keeps encountering edge cases where there is ancillary regulation data that cannot be expressed in CDS but needed by users to avoid tickets

  • Example one: EV chargers that are only available to users of EV car sharing service, next to public chargers

  • Example two: Diagonal parking where the city requires driver to back in.

  • Both of these are communicated to drivers via signage but there's no place in the Spec to hold these types of data.

Designating Driveways in CDS

  • RN - UMOJO captures driveways and alleys in LiDAR scans and would like to be able to communicate their locations and parking restrictions.

  • CDS Zones are not supposed to span alleys or driveways so there's no way currently to apply a rules ( no stopping) to a driveway or alleyway.

Wrap Up

  • Next meeting April 22, 2025