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

CDS Working Group

Agenda

CDS 1.1 Issue Review

  • Welcome (5 mins)
  • Announcements (10 mins)
  • CDS 1.1 Issue Review (40 mins)
    • Exception rules - link
    • EV charging events - link
    • Color - what do painting engineers use - link
    • MDS overlap, external data specs - link. PR

Organizers

  • Hosts: Michael Schnuerle, OMF
  • Note Taker: Michael Schnuerle, OMF
  • Facilitator: Michael Schnuerle, OMF
  • Outreach: Michael Schnuerle, OMF

Action Items and Decisions

  • Read summary and leave comments on:
    • Exception rules - link
    • EV charging events - link
    • External data specs - link

Minutes

Notes

Announcements

  • Event calendar
  • Steering Committee nominations open
  • CDS 1.1 Issue deadline was May 9
  • CDS 1.1 PR is May 31
  • Goodbye to OMF staff Angela Giacchetti, and consultant Mitch Vars!

Exception Rules - link

  • designated_period string field
  • Add a new designated_period_except boolean field
  • user class exception in there now for permits, in there now, non breaking
  • Followup with Laurant to see if this meets his needs - not sure how to do the two layers of exceptions, possibly for breaking
  • Can keep these names as is, and keep it non breaking, but note to change names in 2.0 later
  • Populus is already using this change, basically as laid out. "Exception schedule" field so the whole rule does not apply at this time
  • New PR made for this at #187

EV charging events - link

  • New charging start and charging end events
  • use charging_start/charging_end and fueling_start/fueling_end like in MDS.
  • Umojo would add it, use OCP as separate EV spec
  • SFMTA would use it
  • This would be in Events
  • For Metrics, need to add these events to events in spec calcs
  • Associated with a parking session ID in CDS
  • Add these events to event_session_id
  • It's Electric supports parking and changing as separate events. Could add other event like idling (plugged in but not charging)
  • INRIX - could get charge state, or charge percent. Maybe from car, maybe add to CDS?
  • New activity under Curbs API policy Activities? Yes, add to this list, Charging and Fueling. Seen in Minneapolis
  • Many companies use OCCP/OCPI spec already. Maybe add this in the external reference field. Supports this and ChargePoint. ISO 5108 can support real time charging status, but not yet, to INRIX question, so this comes from car now.
  • Many cities need active charging to allow parking to happen in a charging session. MUTCD signage 'EVs Only' and 'EV Charging Only'. SFTMA has signage like this text, but not MUTCD compliant yet, demonstration sign.
  • Can have a Curbs Object sign type with the text attached to the curb
  • This needs a PR created

Curb Color - link

  • skipped for time

MDS overlap, external data specs - link. PR

  • New object to connect a curb zone or a curb event with any external data source
  • New data_types.md file, like we have for MDS, with common objects across APIs
  • MDS: url, MDS, trip_id, ids - for that Zone. Like Blue Systems in London example parking scooters in MDS trips and CDS Zones.
  • Charging: Event happening, can reference CDS Curbs API Object by id. And you can add a OCPI external feed at the same time.
  • MDS, CWZ, EV, etc. Any external overlap can be connected
  • Seattle - very specific overlap between specs
  • CWZ: a driving lane construction area is impacting a CDS Curb zone
  • Add examples in the PR to help understanding
  • SFMTA - would you remove the reference when over? For Events, it's a moment in time, recorded. For Curbs, it's added then removed when done, if real time is supported.
  • Should reference be in Curbs Policy object (not zone?)
  • elevate this for more views and feedback, bring it to MDS WG meeting for 2.1 as well.
  • Need to specify that data feeds can be open or authenticated, or possibly have an optional field that states the feed is public or private to make it clear.

Meeting Chat