Web Conference 2022.10.04 Curb
- 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
Standardizing Parking Event Data Citywide
- Welcome (5 mins) - Jacob Larson, City of Omaha, Parking and Mobility
- CDS Events and Metrics (10 mins) - Michael Schnuerle, OMF
- Parking Data Aggregation - Smarking w/ Miami and San Jose (10 mins)
- CDS Policy and RFP Language (10 mins) - Michael Schnuerle, OMF
- Discussion (10 mins)
- Hosts: Jacob Larson, City of Omaha, Parking and Mobility
- Note Taker: Henry Espinoza, Miami Parking Authority
- Facilitator: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle, OMF
- 38 Attendees
-
Meeting Recording - Passcode:
@GVV6@GW - OMF Slide Presentation
- Jacob kicked things off with an overview of CDS and summarized its goals and objectives.
- Links to various CDS resources were provided, and attendees were given an update of upcoming meetings and topics.
- Michael provided and Overview of CDS Curbs, Events and Metrics
- Smarking aggregates data from various sources like pay stations, mobile payment platforms, revenue control equipment into a single location for unified reporting and analysis.
- Wen described the challenges of creating and maintaining custom Extract, Transform, and Load (ETL) pipeline integrations with dozens of vendors or other data sources. He requires a dedicated team for this function only.
- Discussed the utilization patterns that can be discovered through aggregate data analysis
- Emphasized the importance of data for decision making for efficient and equitable outcomes
- Michael Danko asked about the types of data sources that can be ingested. The system integrates with mobile platforms, on-street meters, revenue control systems, LPR system, and sensor systems. Smarking adds new integrations for whatever data customers have available.
- Michael Schnuerle asked what impact CDS would impact the workflow. Wen described a world where the data sources were in CDS format as “Paradise”. He strongly supports the standard.
- Michael mentioned that even with CDS, maintenance if integrations is still an important aspect of successful integrations.
- To encourage wide CDS adoption, Cities can specify CDS as a requirement for RFP’s and other contracts.
- CDS allows data to scale across jurisdictions and encourages vendor adoption
- CDS also allows standardization across data sources
- Existing data sources can be converted to CDS format
- Showed OMF guidance on how to include CDS in policy and requested feedback on the information posted
- Used Portland RFP as an example of how it can be included in RFP’s. We would like feedback on this language as well.
- Addressed the issue of publishing and updating the data specifications and highlighted the Policy Requirements area of the CDS and MDS specifications. This flat file describes what data must flow to and from municipalities and can be updated as frequently as needed
- Wen asked how to participate. Michael described the GitHub project and OMF membership.
- Anat Capri asked about upstream and downstream tooling and data validation. Michael explained that OMF is not the custodian of the data. This function is handled between vendors and customers. An Open API spec is currently being developed that parties can use for validation.
- Anat asked if OMF manages the endpoints. OMF does not generally but allows cities can put the requirements file in the CDS GitHub.
- Brian Hamlin asked if there is a template for the policy files. Michael mentioned that this has been considered but the file is easy to fill out using the policy requirements spec. Alex Demisch (SFMTA) mentioned that developing theirs was not difficult.
- Anat asked about integrating roadway data with the curb data. Michael mentioned that CDS is best laid on top of the existing data as a layer rather than integrating the two.
