Web Conference 2024.02.06 Curb
- Monthly on a 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)
Curb Objects Review
- Welcome (5 mins)
- Announcements (5 mins)
- CDS RFP Language (5 mins)
- CDS OpenAPI and Validator (10 mins)
- Curb Objects Discussion (20 mins)
- Hosts: Jacob Larson, Omaha
- Note Taker: Elias Khoury, City of San Jose
- Facilitator: Em Burnett, OMF
- Outreach: Michael Schnuerle, Andrew Glass Hastings, OMF
- Email staff or steering committee and RFP language you have that mentions CDS
- Start using the CDS OpenAPI definitions, and leave your thoughts on a validator
- Add an optional polygon definition to the Objects draft (done)
- Add operator field in addition to owner (done)
- Add query parameters for "Query Curb Objects" to only return objects associated with a specified zone/space (done)
- Merge object type and attribute sections into one to simplify (done)
- Leave comments about what should be the scope of the objects and their level of detail, what is the tech debt, what is required or optional, which object types should be included and are relevant, etc.
- 39 Attendees
- OMF Slides
-
Recording - Password
+xC=VTC4
Michael Schnuerle (Michael S.), OMF’s Director of Open Source Operations, kicked off the meeting by providing an overview of Curb Data Specifications (CDS) and the its membership make up of public and private organizations that adopted CDS.
Michael then moved to allow for two Announcements:
- He introduced Eric Raamot of USDOT. Eric shared with the group that his role in USDOT is to act as a liaison between USDOT and awardees of the SMART Grant. He offered his help for any related SMART Grant questions and shared his email with the group: [email protected]
- Michael S. then mentioned Seattle’s request for the group to help provide any RFP language related to CDS that public or private organizations can share with them as they are putting an RFP related to curb parking and payment and such language would help them develop their scope of work. Anyone with samples of such language can share with Seattle and OMF.
Michael S. then started talking about OpenAPI and how related work is being used on GitHub to facilitate the coding of curb API’s mainly the Curb API, the Events API, and the Metrics API. He also discussed the benefits of using OpenAPI and CDS and the work that Passport, a private company and OMF member, did related to it. Michael S. then turned the floor to Michael Danko (Michael D.) of Passport, who is the main developer/contributor to CDS.
Michael D. talked about the API’s structure as it relates to CDS and encouraged everyone to contribute to the specs.
Michael S. talked about the OpenAPI Validator. It is a CDS feed validator using the OPEN API’ and encouraged attendants to contribute. A related question was posed by Jacob Malleau (Jacob M.) of CurbIQ related to the OpenAPI and if the link to the platform can be shared. Michael S. responded and Michael D. followed.
Michael D. provided some technical information to clarify the unique uses of Stop Light and GitHub and how they are being concurrently used. He offered his help to anyone who is interested in learning more.
A follow-up conversation ensued between Michael S., Michael D., and Jacob M.
The floor was handed to Jacob Malleau of CurbIQ who was presenting about Curb Objects. Jacob M. provided a recap of the discussions and the work that has been already completed related to Curb Objects that are adjacent to curb zones. He also talked about Basic Properties, Custom Properties, and Events.
Michael S. of OMF, then talked about Curb objects progress and presented how issues are posted on GitHub and how can everyone contribute to the posted issues or start a new issue for discussion.
A conversation followed related to Curb objects including Michael Schnuerle (OMF), Felix Mark (INRIX), Jacob Malleau (CurbIQ), Joel Mandella (MTC/ABAG), Miranda Bradshaw (Passport), Dan Patterson (Cambridge Systems), Ahmed Darrat (INRIX), and Michael Danko (Passport). A main takeaway from the conversation were the use of shapes and points for curb objects. We already have centroid, and it was agreed that an optional polygon should be added. Polylines were discussed too, but would require a comment about use cases to include in the draft.
Also shared was the concern on whether the Curb Objects initiative is opening the scope of CDS wide open that it becomes an asset management system, something that CDS should not tackle, a point made by Ahmed Darrat of INRIX. How much detail for each object should be included? What is the tech debt to maintain these in the future? Which objects should be included (toilets and trees?!)? Priority of object types?
The meeting ended at 9:02 AM PST.
