Web Conference 2021.11.02 Curb
- Every other week Tuesday call at 9am PT / 12pm ET / 6pm CET
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)
Main Topics
- Welcome and process (5 min) - Brian Hamlin, SDOT
- CDS Spec Review Discussion (45 min) - Michael Schnuerle
- Hosts: Brian Hamlin (SDOT), Michael Schnuerle (OMF)
- Note Taker: Brian Hamlin (SDOT)
- Facilitator: Michael Schnuerle (OMF)
- Outreach: Brian Hamlin
- 36 Attendees
-
Recording and chat log - Password:
YL=tr9z$ - Main Presentation Slide Deck
Action Items
- The working group needs to review the main branches for Curb Zones, Events and Metrics
- The Metrics endpoint names need review.
- Open discussion questions need more feedback
- Pilot projects guide needs to be updated to include a section on how to reference CDS if you want to use it as an agency. Reference policy language guidance document
- WGSC schedule base line info session with vendors and consultants (before end of year)
- Populus to share library of permits and data sharing agreements and best practices
- Work is no longer happening in the Spec Draft Google Doc. Instead you can use discussions, issues, or pull requests
- Consolidated work is happening on the 'feature-release-work-1' in this Pull Request.
- For your own pull request, you can make your own spec suggestions in a PR and point to the 'dev' or 'feature-release-work-1' branch
CDS Spec Review Discussion
- Walk-through on what is in the CDS GitHub page
- Main and dev are the most important branches
- Dev is development, the work is done here
- Issues and pull requests
- If you have issues, it is best to use the issues page because the working draft google doc will no longer be the editing document going forward
- Issues will be addressed in bulk and then pushed to dev branch. Use issues instead of pull requests if you are not comfortable with markdown
- Specification's walk-through
- Main page provides all of the summary information
- Curbs
- 4 endpoints – Curb Zone, Curb Space, Curb Area, Curb Policy
- The curb zones branch is the most fleshed out of all of the APIs
- The work working group needs to review the main branch
- Events
- 2 endpoints - Curb Event, Status
- More work needs to be done
- Metrics
- 2 endpoints – Activities, Aggregates (the names are placeholders, and we would like recommendations on naming conventions)
- Least defined from CDS perspective. Needs the most work
- You get a CSV instead of hierarchical JSON
- Productivity index is left off, if Metrics is defined more, we can maybe add it
- General information area – includes definitions and background information
- We still have open discussions that need to be answered. Architectural decisions document will be updated once the discussion questions are finalized
- Need feedback in an asynchronous way.
Questions
- Akshay Malik (Philly) - How do we ask a vendor to go about using CDS (even when it is in BETA) what is the lag?
- MS: If you point this to them and let them know it is in flux. Stress that the beta is coming and available for reference.
- Pilot project guide should have a section on how to reference CDS if you want to use it as an agency
- Different version numbers in MDS but CDS is not there yet. Reference policy language guidance document
- There is reference permit language. SLA language is included as well
- Also includes email language for when a release is coming
- Angela G: How do we get vendors involved and up to speed?
- Looking to do a baseline info session with vendors and consultants where we talk about the spec, where it's at, where it's going (high level information)
- Looking to do either before thanksgiving or before xmas
- MS: If you point this to them and let them know it is in flux. Stress that the beta is coming and available for reference.
- MS: Examples from cities or companies to include CDS in contract language
- Brian (SDOT): Nothing formal yet but the vendors we have talked to are very up front about including language that states they will be using CDS
- Jacob (COORD): Seeing how CDS works into their plans. Writing into SOW documents. Will help the steering committee to include generic language examples (nothing pulled directly from existing contracts)
- Regina (Populus): Language from curb cohort documentation for how they are working with cities to include CDS
- Agreements with cities to harmonize the data
- Populus is willing to share examples of language
- Data sharing guidelines, library of permits and data sharing language of best practices
- Supporting policies to make CDS more effective
- MS - OMF is working with a designer to develop a logo and images to help describe what is going on. Not sure on schedule.
- Voting on steering committee in mid-November
- MS - Feedback on something in spec
- Akshay: How are payments included into this framework, especially with third party provider?
- MS: V1 is not at all. Scope of first version was to leave payments out but could be include in the future. Rules and fees about curb usage. Digitally specify “every ride is an extra quarter”. Would not include transaction side.
- What’s the total that gets netted at the end?
- MS: As long as you get the data, you can get that information.
- Third party would be storing those events in CDS format. You would work to develop processes with third party to calculate outside of CDS
- Many things in events are optional, you can chose which field you want to us to answer your questions. Designed to be flexible
- MS: As long as you get the data, you can get that information.
- Akshay: Another layer that needs to be added that matches output to regulation operational side of things. How do we define what a vendor should do in the contract.
- Jacob:
- Mapping to have a regulations specified in the API and whatever operational things there are?
- Produce a spreadsheet that has left side with space id zones of CDS curbs API, 2nd column has IPS meter ID. (or whatever system it is) Spreadsheet shows mapping. Putting it into. Show that the ID’s are long lived. You need the ID to hook other data to it.
- Jacob:
- Matt Davis (Populus): Maybe a future version of CDS will have an equivalent of MDS policy for storing that fee information?
- MS: rates are included within rates section of Curbs API
- MS: You should star the repository that you want to follow to start getting emails when updates happen
- Akshay: How are payments included into this framework, especially with third party provider?
