Web Conference 2025.02.25 Curb - openmobilityfoundation/curb-data-specification GitHub Wiki

Monthly on Tuesday at 9am PT, 12pm ET, 5/6pm CET - open to the public
Zoom Registration and Join Link: https://us02web.zoom.us/meeting/register/tZ0lcuCgrjwsHNyZRagmc86b12iCmWGBHfjq
- One tap mobile: +13126266799,,89859807668#,,,,*320307# US (New York)
Signup to the Mailing List for emails and calendar invites

Agenda

APIs, Webmaps and GitHub Pull Request Review

Jacob Larson (JL) opened the meeting and introduced CDS
Angela Giaccetti (AG) gave an overview of upcoming events that OMF will be attending. The calendar of upcoming events can now be found on the OMF website.
Em Burnett -- Shared latest document on Curb Technology Guidance

Presentation: Web Maps and APIs

Presentation by Michael Schnuerle (MS) OMF, Brain Hamlin (BH) SDOT, Jacob Malleau (JM) CurbIQ
MS - APIs are a digital way to send information between systems or organizations. APIs are very common, numbering in the thousands or hundreds of thousands. A restaurant is a good analogy of how an API works with the waiter serving as the API between the customer and the kitchen.
Seattle has web map developed with CurbIQ
BH - Seattle web map meets users where they are and allows access to curb data without the need to query an API.
BH - Seattle has developed both public and private maps. Public for curb users and private for internal use. Internal map contains CDS usage metrics
BH - Seattle survey found many curb users lacked technical capacity to use API so web map is a better fit.
JM - Internal map aggregates demand data from meters and sensors to calculate CDS metrics.
JM showed an example of raw CDS zones and policy data that powers the web maps using Postman to query APIs. JM demonstrated how to limit query results to a radius around a point.
MS - Shared pros/cons of web maps vs APIs and their relative strengths & weaknesses in different contexts.
BH suggested a future workshop on working with APIs and queries
JM made comparison between GTFS and CDS. GTFS standardization of transit data across many cities allowed scaling of use.

GitHub Issues and Pull Requests

Mitch Vars (MV) gave an overview of GitHub Issues and Pull requests and how they are used in the specification development process.

Michael Schwartz (MSZ) of INRIX - proposal to allow linestring data in place of polygons in the geometry field. Many cities have existing linestring data that they would likeot be able to use in CDS
MS - described how polygon requirement was developed. Polygon was aspirational and enabled support for things like parking lots etc and would allow for using GPS coordinates to determine if a vehicle was within the curb zone. Should this be options polygon or linestring or should polygon still be required
Matt Davis (MD) - is anyone combing linestring with event enforcement?
MSZ - yes, INRIX is using linestring for enforcement.
MV - any concerns with using linestring if we map travel lanes and other parts of ROW?
MSZ - how accurate do geometries need to be? INRIX has found that linestring provides enough accuracy for most use cases.
Elliot Meuting ( EM) Would using two different geometry types make it more difficult for data consumers to consume data?
MV - should it be two separate fields?
MS - could be in separate fields where requirement was for either.

Matt Davis (MD) of Populus - suggestion to split the way user interacted vs how they paid for curb. PR adds payment method and payment channel with method being things like credit card or cash and channel being things like meter or mobile app.
MV - everyone go and look at PR and add any enumerables that are missing from the two fields.
MV- are there other things we are not covering, connected vehicles bluetooth, RFID etc?

MD Events API lacks time range filter for events. Proposal borrows method from MDS using ISO 8601 UTC hour
MV - please visit the GitHub and comment on the 6 open PRs so we can keep them moving forward.
MV - Next meeting is March 25th, put it on your calendar

...