Skip to content

Web Conference 2024.10.29 Curb

Jump to bottom
Michael Schnuerle edited this page Nov 6, 2024 · 13 revisions

CDS Working Group

Agenda

Review Curb Objects

  • Welcome (5 mins)
  • Announcements (5 mins)
  • Presentation: Modeled Curbside Data in Seattle (15 mins) w/ Turnstone
  • Review current state and finish work on Curb Objects - Curb IQ (30 mins)
    • Issue #123
    • PR #126
    • Related: Define devices (like Computer-Vision cameras) #147, Zone relation (1-to-1 or 1-to-many) #152

Organizers

  • Hosts: Jacob Larson, Omaha
  • Note Taker: Michael Schnuerle, OMF
  • Facilitator: Michael Schnuerle, OMF
  • Outreach: Michael Schnuerle, OMF

Action Items and Decisions

  1. Remove proposed custom Object Type Attributes from Curb Objects (could come later in 1.2 if it's needed)
  2. Update curb object ids description in Zones to specify it is about the object's area of influence
  3. Update curb zone id description in Objects to specify it is closest location of the object at the zone
  4. Keep curb events object id in Events as is so each object get its own event and details when needed
  5. Leave your feedback on the Curb Object proposal ASAP before we merge it to the 'dev' branch: #126
  6. Get your OMF Summit tickets

Minutes

Notes

Seattle and Turnstone Presentation

  • CDS helping advance the system of parking, hardware, predictive models.
  • 30K transactions a day
  • Not just parking. Curbside Management Team
  • Rates set within range based on blockface performance using Events and Metrics. 1-2 spaces open throughout the day on each blockface. 3 adjustments annually
  • Seattle sources go into Data lake, normalized, web frontend, out to APIs
  • Models must remain precision over time, behavior changes slowly.
  • Count of transactions over number of spaces predictions match reality.
  • Hardware based sensing, not always practical, manage hardware, cost, staff time. Instead USDOT SMART grant data driven approach
  • Future - SDOT record of truth, SMART is helping what's possible

Curb Objects

  • Goal: Consensus on how curb objects are added to CDS 1.1
  • Are there custom object fields for each type of object?
  • List of object types well known values

Related Issues:

  • Curb Object, Curb Zone, and Curb Policy (1-to-1 or 1-to-many) #152

  • Define devices (like Computer-Vision cameras) used in CDS. #147

  • Adding objects, new endpoint, curb_object_ids, new object, well known object types, custom attributes

  • 36:00 min mark - starting in depth conversation with cities and vendors on the call

Object Type Attributes

  • CurbIQ - important to decide this
  • Turnstone - Free for all object type attributes could be a problem
  • INRIX - otherwise needs standardization, like EV charging
  • Umojo - Key pair approach is flexible, but moves us too far from a standard
  • 3 options
    • Allow anyone to determine their own key value pairs - Later if we define them, everyone's made up values will break
    • If we require and define each attribute, then make a change later, that's a breaking change. And it's going to complex to define each of these
    • Do an MVP and don't include attributes in 1.1
  • A bit of scope creep for OMF/CDS
  • CurbIQ, Umojo, Turnstone - eliminate the custom attributes table, there are other priorities for CDS than the time involved for this, MVP here
  • 1.1 could not include custom attributes, then we can add them in 1.2 and it would not be breaking.
  • However if we add them now, then any change to 1.1 would be breaking and then a 2.0 release, since they exist in 1.1.
  • Cities and vendors want object types, but don't need attributes yet
  • orgs can point to the dev branch once we resolve this one PR/issue. We can make tweaks in next few weeks before release 1.1 is approved.
  • Patch release 1.0.1 needs to finish soon, then push objects to dev
  • No objections to removing custom attributes for now

1 to 1 and 1 to Many for Curbs

  • SFMTA issue
  • Umojo cameras in multiple zones/spaces
  • CurbIQ, SFMTA reps - commercial loading zone then open zone
  • Defining a camera is linked to a zone in Curbs
  • Curb zones can have multiple object IDS associated with it (monitoring) - need clearer definitions here! what's its area of influence is - each zone gets a locker ID for example
  • Curb object can have 1 zone associated with it based on physical location (location) - need clearer definitions here! it's where it's located, the zone the locker is closest too for example
  • Curb zone ID affected field... - but then it's hard to cross maintain. Maybe this is a camera specific attribute, which we aren't doing now.

1 to 1 and 1 to Many for Events

  • Vehicle arriving in a zone/space that has a meter, charging, locker, etc
  • Would make a new
  • Each object would get its own event. 1 camera records 3 events for 3 cars. 2 cameras see the same event, that's 2 events, but might be duplicate, need to be careful in implementation
  • all these events are with this data source operator
  • 147 is resolved with this conversation

Recommended changes and action items are going to be added to the PR, and emailed to the group for feedback

Relevant Chat

Michael Schnuerle (OMF) 12:44 Getting Started Guide https://docs.google.com/document/d/1YfYOA38MQgMVf7f4-tE6W4UC5deRbC1GO2MFjNud0Uc/edit?usp=sharing

OMF Summit http://openmobilityfoundation.org/omf-summit-2024/

Aylene McCallum 15:19 If you are an OMF member, have not registered yet, and need a code for complimentary registration - please reach out to me directly. I can send the code to you to register for free.

Kenya Wheeler (SFMTA) 30:08 On the graph of parking compliance shown by Turnstone where occupancy is >100%, does that account for double parking?

Mary Catherine Snyder 30:22 And to clarify in Seattle we have multi-pay stations so don't have clearly designated spaces

Mary Catherine Snyder 31:48 Kenya - Parking is over 100% because we have a documented legal parking inventory in our curb data system internally that says paid spaces are 20 feet, 22 feet with clearance, except cars are various sizes and park well or poorly.

James Barr (Turnstone) 32:03 @Kenya Wheeler (SFMTA) it could be double parking, but SDOT’s space counts are length based, so it can be a larger number of smaller vehicles, or it can be higher turnover, among other things

Mary Catherine Snyder 37:32 If folks want to chat and compare notes about non-payment behavior - that would be great. It's a real problem here and realize its outside of CDS somewhat

Michael Schnuerle (OMF) 39:36 Object Pull Request https://github.com/openmobilityfoundation/curb-data-specification/pull/126

CDS logo

CDS Links

1.0.0 Release

Clone this wiki locally