-
Notifications
You must be signed in to change notification settings - Fork 19
Web Conference 2021.11.16 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
- City Use Case (10 min) - Prithvi Deore, Southern California Association of Governments (SCAG)
- CDS Open Questions and "Final" Decisions (45 min) - Michael Schnuerle (OMF)
- Hosts: Brian Hamlin (SDOT), Michael Schnuerle (OMF)
- Note Taker: Tomas Carranza (LADOT)
- Facilitator: Michael Schnuerle (OMF)
- Outreach: Brian Hamlin
- 34 Attendees
-
Recording and chat log - Password
ZLCt8+RA
- Main Presentation Slide Deck
Action Items
- The Working Group should continue to review the five help wanted items and any open discussion items on Github and offer comments, recommendations, or preferences.
Minutes
Welcome and Overview (Brian Hamlin, Steering Committee Chair)
Brian provided background on the draft work products completed to date by the Curb Working Group, and gave a high-level overview of the proposed CDS structure (curbs API, events API, and Metrics API). The goal of this meeting is to address key open questions related to the specification.
The Steering Committee plans to finalize the new specification (CDS Version 1.0 Beta) for launch in December 2021 / January 2022. Key upcoming meetings include a spec review on November 30, an CDS information session for firms working with cities to implement dynamic curb management solutions on December 1, and a CDS launch preparation session on December 14.
Southern California Association of Governments (Prithvi Deore, SCAG)
To address the growing issue of increasing and competing curbside demands, Prithvi presented key curb management initiatives completed or underway by SCAG - the Metropolitan Planning Organization for the Southern California region. These efforts include the following:
-
Last Mile Freight Delivery Study – to increase understanding of last mile delivery issues for SCAG’s member cities, this completed study included field data collection at curbsides within the city of Los Angeles, curbside data analysis, stakeholder engagement, and a final report that included a toolbox of potential curb management strategies. Details on the study and its findings can be found here: Last-Mile Freight Delivery Study, September 2020.
-
Curb Space Management Study – SCAG initiated this study to assess the Southern California region's readiness for dynamic curb management. Key objectives of the study are to convene representative SCAG member cities to share insights and lessons learned on curb management strategies programs and pilots underway. The study will provide various curbside management strategies and recommendations, and offer playbooks for cities to develop a work plan for pilot project concepts. While the last mile freight study focused on data collection and consolidation, this study considers specific locations for demonstration projects. In this effort, CurbIQ will be used to test the digitization of the participating cities’ curbside inventory, and to offer customizable parking, curbside, and asset management software solutions.
-
Grant Programs - SCAG offers two grant programs to assist agencies in using technology to advance their curbside management goals. One program is the Last Mile Freight Program Call for projects, and the other is the Smart Cities & Mobility Innovations (SCMI) grant program. The SCMI grant is a technical assistance program that supports local jurisdictions in using technology to improve the efficiency and performance of the transportation system through innovative policy and by implementing curb space management measures.
CDS Open Questions & Final Decisions (Michael Schnuerle, OMF)
Michael facilitated a discussion to address the following key open questions related to the CDS structure:
Discussion 1
-
Vehicle types - the Steering Committee recommended moving forward with the vehicle types included in MDS (bikes, cargo bikes, scooters, moped, trucks, vans, freight, etc.). The meeting attendees were asked if anything is missing from this list. Comments included adding motorcycles, agreed this should be added.
-
Activity types - this expresses the reason for the curb activity by a vehicle, and types include passenger transport, food delivery, parcel delivery, construction, waste management, etc. Recommendations from the attendees included adding activities related to emergency vehicles, special events, utilities, public services, and maintenance of mobility service devices. We will use the discussion area to determine what to add.
Discussion 2
- Lane types - this expresses where an activity is happening during curb events. Automotus offered the starting point for lane types and included traffic lane, turn lane, bike lane, bus lane, and unspecified. No specific comments were offered on this item but attendees were encouraged to submit comments and suggestions via Github. Discussion online about aligning to WZDx.
Discussion 3
- Metrics Endpoint Names - the draft spec currently includes 2 endpoint names under the Metric API: Activities & Aggregates. Activity provides information on the activity that occurs near, at, or within a predefined curb area, and is a subset of the Events API. Aggregates offers counts of curb events based on a formula or calculated methodology. No specific comments were offered on this item but attendees were encouraged to submit comments and suggestions via Github.
Discussion 4
- Methodology - Different methods can be used to collect data, including company data feeds, camera, and in-ground and above-ground sensors. The data collected can include vehicle characteristics, dwell times, curb activity type, & event types.
Developing a methodology to measure occupancy is a challenge. So the Steering Committee is considering a third endpoint or replacement for Activity called Session that is a conceptual level between Activity & Aggregate. This Session will use Event data to calculate a vehicle's usage of the curb, and would include start and end times (and thus duration) of a defined session. We need to develop this metric methodology to determine occupancy and dwell time at curb places for our Metrics calculations.
Jacob Malleau suggested taking events and breaking them down into 2 sessions in Events - they can be linked by a new common ID. Events would come in through CDS as a start then as an end but with a connection to the start via ID. Could add new field called session_id. So it would be great to find a way to connect these events by figuring out from the raw data if this is one connected event. If the session format does not exist to connect them, then it creates lots of work and calculations on the backend. WGSC will take these comments & discuss.
Discussion 5
Due to time limitations, the working group was not able to address the fifth discussion topic related to examples. But the staff and WGSC will work on adding these to the spec for most endpoints.
The Steering Committee will take into consideration all of the recommendations made by the attendees. However, attendees were encouraged to submit comments and suggestions via Github on any of the discussion topics in the next week.