Web Conference 2023.05.30 Curb - openmobilityfoundation/curb-data-specification GitHub Wiki
- Every other week 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)
Main Topics
- Working Towards the Next CDS Release
- Hosts: Jacob Larson, City of Omaha, Parking and Mobility
- Note Taker: Elias Khoury, San Jose DOT
- Facilitator: Jacob Larson, City of Omaha, Parking and Mobility
- Outreach: Michael Schnuerle, OMF
- 33 Attendees
- Slide Presentation
-
Recording: password
^usq1TBM
OMF – Curb Working Group, 5/30/2023, 9 AM PST, 12 PM EDT
9:02 Meeting started with Jacob Larson, CDS Steering Committee Chair, City of Omaha, welcoming everyone to the Curb Working Group meeting. First, Jacob went over some meeting related housekeeping items. He then expanded to explain that Curb Data Specification (CDS) was introduced to help with curb digitization and data standardization. He talked about CDS membership make-up of public agencies/cities and private companies. He mentioned the release of the first version of the standards CDS 1.0. He explained that CDS is an open-source effort that is available for anyone to use. CDS standards focus in their first version on issuing 3 API’s:
- Curb API’s
- Event API’s
- Metrics API’s
He then showed a list of agencies/cities and vendors using CDS. Jacob then introduced Michael Schnuerle, OMF, Director of Open Source Operations to briefly talk about the US DOT Smart Grant. Michael mentioned the collaborative effort for a group of CDS member cities who are all applicants of the Grant. Michael then offered the floor to Angela Giachetti, member Engagement Manager at OMF, to highlight the fact that OMF is actively recruiting staff so they can assist member cities in their collaborative SMART grant application.
After Angela’s update, Jacob Larsen introduced Ahmed Darrat with INRIX who was going to present to the meeting attendees about INRIX’s services and their work related to the curb.
Ahmed started the presentation by describing INRIX’s work related to the curb prior to CDS and how they embraced CDS and converted their already existing data to CDS. INRIX had collected curb data and currently working on collection of curb data in over 125 cities across North America and Europe. He then provided a full presentation about INRIX’s curb data collection process. It is a 4 steps process:
- Initial Data Collection
- On-going Data Integration
- Ground Truth Testing
- Customer Delivery
Initial Data Collection: involves mapping the curb with all its restrictions and uses. Data is collected from public sources, street level and aerial imagery, and in-field data collection.
On-going Data Collection: through proactive partnerships, reactive public data monitoring, and street level and aerial imagery.
Ground Truth Testing: utilizes over 100 testers in 125 cities. Periodic testing is performed depending on service level agreements. Test coverage and data attribution and prediction accuracy. Utilize occupancy measurements to feed predictive models.
Customer Delivery: manual data input is written to the database. Data science models delivering availability and occupancy for the next 7 days in 15-minute bins. Scripts to export to CDS.
Ahmed opened it up for questions, but there were no questions asked.
Michael Schnuerle highlighted the work that Ahmed put into curb data collection and standardization with CDS.
Ahmed mentioned that they have already collected over 3 million curb sections and this helping identifying challenges. INRIX has developed a CDS API.
Michael then addressed the attendees by indicating that he is going to explain how CDS plans their releases. The goal from the presentation is to understand CDS release process so the attendees can relate any of the challenges they have to the release process and be able to contribute to the effort. He talked about OMF release guidelines including technical info on how it is used on GitHub. He talked about Contributor guidelines and Code of Conduct, release plan, and meeting schedule.
Expanded on Release Guidelines and Goals: seeking regular releases through consensus and encourages involvement from all stakeholders both public and private.
Release Schedule focuses on setting goals, feature proposals, implementation and coding, decision and consensus, and release finalization. All done on a flexible timeline.
All in all, anyone can contribute, maintainers will take care of implementation and coding, feedback is provided on GitHub, collaborative effort with all contributors, as well as the Steering Committee role of pushing forward proposals, and release documentation.
Then Michael talked about the Checkpoints during the Release Process:
- Plan
- Midpoint
- Consensus
- Review
He also presented the Feature Rubric that is utilized during each Checkpoint:
- Utility
- Adoption
- Simplicity
- Consensus
- Work
Each feature is given a rating to help decide whether to move with the feature.
Michael then proceeded with explaining the Governance Process: public forum, curb working group steering committee, Technology/Strategy/Privacy Security committees, then to the Board of Directors.
Related timeline: Working Group (anytime), Technology Council (1 – 4 weeks), Board of Directors (2 weeks or more).
Michael then presented the current Open Ideas to be categorized into 3 types of releases: Major (make breaking/incompatible), Minor (add functionality in backwards compatible manner), or Patch (make backwards compatible bug fixes/doesn’t require BOD approval).
Michael then showed the attendees how to navigate the Open Ideas on GitHub. Michael encouraged everyone to add their NEEDS on GitHub. He then gave a rough estimate of the timeline for each release:
Patches few weeks
Minor release approximately 6 months
Major release approximately 18 months
Open it up for questioning. No questions were raised. Meeting ended 9:59 AM PST.
