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

Web Conference - Curb Working Group

  • Every other week Tuesday call at 9am PT / 12pm ET / 6pm CET

Conference Call Info

Meeting ID: 898 5980 7668 - Passcode 320307
https://us02web.zoom.us/j/89859807668?pwd=ZzJrbEpTNVB4WkNqNiszcmFYVzBwZz09

One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Agenda

Main Topics

  1. Welcome and process (5 min) - Brian Hamlin, SDOT
  2. Intro WGSC Members (10 min)
  3. CDS Open Questions (45 min) - Michael Schnuerle (OMF)

Organizers

  • Hosts: Brian Hamlin (SDOT), Michael Schnuerle (OMF)
  • Note Taker: Brian Hamlin (SDOT)
  • Facilitator: Michael Schnuerle (OMF)
  • Outreach: Brian Hamlin

Recap

Notes

Action Items

  1. Should vendor specific names be included in user class or should it be incorporated somewhere else within the spec? See discussion
  2. Need more discussion on Curb ID Stability. Use Eric’s discussion thread.
  3. New discussion for adding curb event source data descriptions
  4. Please add any source types to open discussion topic for this release
  5. Provide feedback on open discussion Are Provider ID’s global like MDS, or per city?
  6. Review and leave thoughts on feedback needed discussion items!

Minutes Welcome and Overview (Brian Hamlin, SDOT)

  • Brian provided background on the draft work products completed to date by the Curb Working Group, and gave a high-level overview of the proposed CDS structure (curbs API, events API, and Metrics API). The goal of this meeting is to address key open questions related to the specification.
  • Brian also introduced the new Steering Committee members. He mentioned that the OMF board recently voted to approve the new members and they were approved. The committee now has 7 public and 7 private members.
  • Akshay Malik (Philly) introduced Philly’s new Smart Loading Zone Pilot project RFP that was just posted. https://philawx.phila.gov/econtract/(Opportunity number 21211116142501) The RFP does not specifically include CDS language but their intention is to include CDS requirements once V1 of beta spec is released.

CDS Open Discussions (Michael S, OMF) Michael facilitated a discussion to address the following key open questions related to the CDS structure:

Discussion 1

  • User Classes in Curbs – Expanded the list of possible values about 2 dozen now. List of well know recommended values. Nothing particularly new just expanded upon.
    • Henry E (Miami) - Can you publish a policy that is vendor specific?
    • MS – Need to make a user class with vendor’s name which is not elegant
    • Action Item – Can be a discussion item in GitHub.
    • Kenya Wheeler (SFMTA) – Possibly add user class field

Discussion 2

  • Tracking “purpose” for curb events - Not really clear what level of granularity you can discern from activity. Can tell a delivery is happening but not what type. Instead of activity it will now be purpose. Well-known list. Use this first and then add your own if needed.
    • No comments

Discussion 3

  • Sessions in Metrics – Instead of activity endpoint there is now a Session endpoint which still includes everything including start and end activity wrapped up into one row of data. Allows for quick calculation of parking session or dwell time. Directly ties into Aggregate endpoint.
    • Henry (Miami) and Marcus (Passport) both agree.

Discussion 4

  • Curb ID Stability – Should curb zone ID’s remain stable or should they change? When you get a new ID what happens to the old one, how do you do historic analysis?
    • Eric (Lacuna) - If a zone’s policies change should the ID change? The ID should stay the same if the policy changes. Depends if the agency wants to keep tracking the same curb zone.
    • HE (Miami) – Wants to be able to compare before and after metrics if the policy has changed or even if the zone geom has changed. What changes do you want to report on in the future?
    • MS (OMF) – If a city considers it a new space – new ID, if city considers it’s the same, they should keep the same
    • EK (San Jose) - Modification date?
      • MS (OMF) – At minimum yes but you lose what happened before the last change
    • JF (OMF) - Need historical data in order to build long term analytics tool
      • MS (OMF) – Could add a version field? V1/V2. Allows for you to get back to a certain version
      • KW (SFMTA) – Did not include feature class for historic rate data. Have to do offline processing which makes things very challenging.
      • JM (CurbIQ) - What do you do when you add zones and create new segments? (load zone In the middle of a block of paid)
      • MS (OMF) – Change in geom leads to change in ID not really the policy

Discussion 5

  • Clarify Source – In curb event, we need to simplify and add clarity to field names and descriptions. Less fields overall. Sensor wording is going away and now everything is source. Source of data and not ownership.
    • KW (SFMTA) – Important delineate the types of sources instead of open ended category?
      • MS (OMF) – Source type is included. Defined list now but could be open ended.
      • Action Item – Discuss adding a data source description
      • JF (OMF) – what would go in there and not type?
        • Value to have enumerated types. Allows us to set rules and guideline for how to interpret data. We should add new sources to the list to formalize it. Other works as stop gap
        • KW (SFMTA) – New sources could be added in version updated
        • MS (OMF) – Add source types to discussion topics for this release
    • JF (OMF) - Data_source_organization_id and vehicle_fleet_name, should these be free text fields. Just a name field that allows a string to be passed. Or do we keep the ID option with global UUID. This will be very challenging to maintain a global ID list