Web Conference 2022.07.12 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
- Welcome (5 mins) - Jacob Larson, Omaha
- City Presentation - Philadelphia (10 mins)
- Open API work (40 mins)
- GitHub Issue #87
- GitHub Pull Request #100
- Stoplight CDS Curbs Draft
- OpenAPI website
- Integration with GitHub
- Feature Branch: feature-openapi for development on GitHub
- Working Document with details
- Hosts: Jacob Larson, Omaha
- Note Taker: Tomas Carranza, LADOT
- Facilitator: Michael Schnuerle, OMF
- Outreach: Angela Giacchetti, OMF
- 37 Attendees
-
Meeting Recording - Passcode:
5C%12P@^ - OMF Slide Presentation
- Refine existing Curbs definitions
- Add Events and Metrics OpenAPI definitions
- Possibly create new GitHub repo to store schema so 1) bi-directional changes can be made 2) improvements can be made between releases
- Jacob provided 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.
- Eric and Michael described the initiation of the OpenAPI work and the integration of GitHub and Spotlight.
- While GitHub offers a public and collaborative way to use wikis, to hold open discussions on key issues, and to develop the spec, Spotlight offers a visualization tool. In this case, OpenAPI can be visualized and can provide sample code to help with development.
- Eric initiated the discussion on OpenAPI and walked the attendees through a live GitHub demo.
- Eric presented a sample pull request, and provided this link to illustrate a pull request.
- The specification can act as a single source of truth, can be viewed to learn which endpoints are available, can validate requests to clients, and is helpful to see what data is exchanged in this API.
- An OpenAPI validator used to validate requests and responses. Eric walked the group through a demonstration of requests and responses
- Michael offered more insight on the bidirectional integration of Stoplight and Github, and how content can be kept in sync.
- GitHub provides the source of the content and Stoplight helps to visualize that content.
- Michael walked the attendees through a demonstration of how changes are made on GitHub.
- He stressed that Stoplight is helpful in presenting information to an audience that is easier to digest and follow, and can be a useful tool to increase the adoption of CDS.
- In response to questions, Michael and Eric noted that Stoplight recognizes when GitHub has been edited, and that GitHub includes the history of user changes. Any issues that come up with this integration can also be fixed in Stoplight – there is flexibility in this pairing thanks to the validation process in Stoplight.
- Moving forward, YAML files will have to be manually updated regularly. Updates would need to be made as the specification is updated. However, with Stoplight, it is easier than writing technical code.
- Attendees liked the idea that the validation process can ensure that all users are on a level playing field when trying to communicate data, so there is less potential for misinterpretations.
- Akshay presented the Philadelphia Smart Loading Zones pilot project - a three agency collaboration. Philadelphia does not currently maintain a digital inventory of their parking and regulations, so this will be their first effort to digitize these assets.
- The main goals of this pilot are to match demand-supply for loading activity, to improve user experience, and to test digital management of the curb space.
- Key components of the project include physical assets, regulations, reservations, management, & enforcement.
- Google is a partner in this effort and the key software components will include a parking app, enforcement app, driver’s app for reservations & payments, and a dashboard to track all of the data.
- The hardware components include on-pavement sensors (“parking puck”), and wireless gateways (solar-powered hubs that gather information from nearby on-pavement sensors and relay the data to the cloud using cellular data).
- The project is currently in the planning phase and implementation is expected to start in September 2022 and be operational for 6 months.
- 20 zones will be part of the pilot (all in downtown Philadelphia) and there will be a warning period before the locations are enforced. The pilot will include a reservation and payment process for curbside deliveries.
- The pilot, which will be evaluated to assess what aspects worked and which can be improved, will offer an opportunity to educate stakeholders on the purpose and benefits of CDS, so that it can eventually be integrated into the agencies’ operations.
- In response to questions, Akshay indicated that the pilot will hopefully demonstrate the value of CDS and other curb management strategies like a reservation system. He also stressed the importance of collaboration between key agencies and stakeholders to demonstrate how these tools are available and effective, and can help them graduate from paper-based systems like writing work orders.
