​

CURB OBJECTS REVIEW

​

February 6, 2024

​

ZOOM HOUSEKEEPING

• Set your name and organization in the Participant list

​

​

• Mute yourself unless talking

​

• Use chat to let us know you want to speak, or you can speak up, or use the raise hand feature ✋�
• ⬤ This meeting is being recorded and will be published with notes

AGENDA

​

​

WGSC Roles

Hosts: Jacob Larson, Omaha

Note Taker: TBD

Facilitator: Michael Schnuerle

Outreach: Michael Schnuerle, Andrew Glass Hastings, OMF

1. Welcome (5 mins)
2. Announcements (5 mins)
3. CDS RFP Language (5 mins)
4. CDS OpenAPI and Validator (10 mins)
5. Curb Objects Discussion (20 mins)

CURB WORKING GROUP

Jacob Larson, Omaha (5 mins)

CURB DATA SPECIFICATION

​

​

​

​

​

CDS helps cities and companies pilot and scale dynamic curb zones that optimize commercial loading activities of people and goods, and measure the impact of these programs to advance policy goals.

​

The Curb Working Group Steering Committee is leading development of CDS with the help of you in the Working Group.

​

CDS 1.0 is in use by dozens of entities around the world, and we look forward to requested improvements from the community for the next CDS release.

​

​

​

​

WGSC Members

Public Sector

• Zackary Campos, LADOT
• Henry Espinosa, Miami Parking Authority
• Brian Hamlin, Seattle DOT
• Elias Khoury, City of San Jose
• Jacob Larson, City of Omaha
• Krute Singa, Metropolitan Transportation Commission (MTC)
• Kenya Wheeler, San Francisco MTA

Private Sector

• Miranda Bradshaw, Passport
• Pierre Bouffort, Blue Systems
• Dillon Cruz, Google
• Ahmed Darrat, INRIX
• Jacob Malleau, CurbIQ
• Eliot Mueting, Populus
• Christopher Perry, Umojo

CDS OVERVIEW

CDS allows cities to digitally represent their curb space, communicate with curb users in different ways, and use metrics to improve those curbs.

• Technology built through public and private sector collaboration, led by industry experts

​

• Participation from 160+ individuals from 70+ public agencies, curb users, and technology companies before & after launch

​

• More competitive markets and solutions for mobility services and software tools

​

• Built through OMF’s open model, developing free and open source tools in regular public meetings open to all

BUILDING CDS IN THE OPEN

WHO IS USING CDS?

See the “CDS Users” section of our public Working Group page.�More than 14 public agencies and 22 companies across 7 countries.

CDS in Pittsburgh w/ Automotus

Let us know if you are using CDS!

CDS in Omaha w/ ESRI

CDS in Philadelphia w/ Pebble

CDS in Seattle w/ Populus

CDS in Dublin w/ CurbIQ

CURB WORKING GROUP ROADMAP

ANNOUNCEMENTS

OMF Staff (5 mins)

CDS RFP LANGUAGE

Brian Hamlin, SDOT (5 mins)

CDS RFP LANGUAGE

Seattle (and other cities) is interested in examples of RFP language that includes any mention of CDS in the RFP requirements.

Seattle is in the early stages of putting together a new mobile payment RFP and understandably are very motivated to include CDS language in the RFP.

Additionally they are looking for RFP language around:

1. how data is stored
2. communicated (data sent to city servers in CDS format or through ecosystem vendors)
3. how much (if any detail) is included in regards to data and CDS

If you can share a link or screenshot or file of your RFPs around CDS, the OMF can compile these and share the relevant snippets anonymously for others to see, and create recommended best practice language.

Email michael@openmobilityfoundation.org or drop a link in the chat now.

CDS OPENAPI AND VALIDATOR

Michael Schnuerle, OMF (10 mins)

OPENAPI CDS

CDS 1.0 is defined using OpenAPI and that information is on GitHub and ready for you to use.

WHAT ARE APIS?

APIs are a digital interface to expose functionality or receive data between software applications.

These can be documented to establish a "handshake" on how data should be structured when it's shared between systems.

CDS APIs let government and curb users share data consistently.

APIs

WHAT IS AN OPEN API?

An openly defined industry standard way to describe HTTP/web based APIs.

Instead of using just text on GitHub, you describe them as a digital structure.

Note open does not mean “public” here, just created in the open and free to use.

The OpenAPI Specification (previously known as the Swagger Specification) is managed by the OpenAPI Initiative, much like CDS is managed by OMF.

​

​

​

The OpenAPI Specification (OAS)

BENEFITS OF OPENAPIS

1. Simplifies collaboration because there's a common understanding to explain what functionality is available within an API
2. Automated code generation & testing of API endpoints
3. Automatic generation of documentation and visualizations to assist with API adoption.
4. Online interactive tools to validate, document, and understand.

​

​

COMPLIMENTARY BENEFITS

1. OpenAPI Specifications (OAS) - Industry standard spec that outlines how Open API files are structured
2. OpenAPI Definition - Files that can be machine read and represent the specific use cases for a given API
3. API Documentation - A mechanism to display an OpenAPI Definition file in a user friendly format that simplifies navigation and readability.

​

PASSPORT EXAMPLE

How is Passport using OpenAPI?

• Passport has published several APIs to our public developer portal for 3rd party applications to integrate with our systems.

Why document using OpenAPI?

• OAS files are displayed for partners to easily navigate and understand how to structure their requests and how data will be returned to their application.
• OAS files accelerate onboarding and provide partners with the ability to validate functionality throughout development.

OPENAPI VALIDATOR

OpenAPI: Single source of truth for schema definitions, with multiple uses

​

• API discovery for clients
• Validation of request and response schemas
• Automated testing

​

Leave your thoughts here on this CDS discussion area.

CURB OBJECTS

RECAP

Jacob Malleau (5 mins)

CURB OBJECTS - DISCUSSION AND PROGRESS

Where we stand. Will review new updates after this recap.

​

We have created GitHub Issue #123 and PR #126 to gather comments and feedback.

WHY CURB OBJECTS IN CDS?

​

​

• There’s a lot of stuff in the ROW!
• Including these objects in CDS will help cities and curb users
• Understand where & what those objects are
• Catalog and share to curb users
• Develop tools to better manage those spaces
• Understand object usage
• Accurately compare objects from different departments/sources

CURB OBJECTS

Include definitions/activity/events for curb area adjacent elements that facilitate or impede curb transactions:

• Trees/Planters
• Utility box
• Bench
• Ramp
• Art, sculpture, fountain
• Signage (fixed, temporary)
• Post box
• Bollard, barrier
• Surveillance camera
• Bike rack

What other objects are you interested in describing and then tracking use?

• Storage locker
• Meter pay station
• Signal cabinet
• Scooter parking
• Electric charging
• Solid waste bins
• Lighting
• Bus stop
• Drinking fountain, toilet
• Food vendor
• Fire hydrant

CURB OBJECTS

Bike Docking

Station

Space

Curb Zone

EV Charger

Planter

Planter

Street Tree

Ramp

Bench

Meter

Meter

Space

Examples of objects that can be on or off the curb.

​

Each object has location, size, and custom properties.

Storage Locker

Sign

Barrier

Trash

Bike Rack

CURB OBJECTS - BASIC PROPERTIES

How do we add this to CDS? Define in Curbs API and Events API.

​

Might need linear referencing from fixed curb point. Or maybe just lat/lon like in OpenStreetMap. These objects are not affected by GPS accuracy or drift, since their location is pre-defined by the city agency.

​

Each object would need identical basic properties in Curbs API like:

• Name
• Description
• Linear distance from fixed curb point
• Perpendicular distance from fixed curb point
• Max length
• Max depth
• Max height

• Center lat/lon
• Owner
• External ID
• External URL
• Polygon shape?

CURB OBJECTS - CUSTOM PROPERTIES

Each object could have custom properties in Curbs API.

Ramp:

• Incline
• Material

Signage:

• Purpose
• Text
• Owner

Locker:

• Total capacity
• Unit capacity
• Unit cost
• Access type

Bus stop:

• Seating
• Cover
• Signage

EV Charging:

• Plug type
• Payment Required
• Hours
• Level
• Kilowatts

Street tree:

• Species
• Trunk circumference

CURB OBJECTS - EVENTS

If an object can be used, also provide information in Events API.

​

Beyond what most current data standards (OSM, Plugshare, etc) have available because it’s based on usage that curb managers may need to know.

​

Some objects could have additional Event data sent like:

• Used (sent by operator/monitor if it was used in any way: bike rack, ramp, meter, storage locker, EV chargers)
• Total Cost (storage locker, EV chargers)
• Total Energy (EV chargers)
• Issue (could report any issue with the object)

CURB OBJECTS

UPDATES

Michael Schnuerle (15 mins)

CURB OBJECT: NEW UPDATES

​

​

• Added basic properties: owner, external id, external URL
• Any others?
• Added “Object Type Attributes” field for custom properties based on object type, with unordered key/value pairs. Similar to how we handle custom attributes in MDS.
• Added endpoints for querying the list of all objects (with a parameter for last updated), and fetching single object details using an object ID
• Other parameters needed, like all objects at a zone/space?

CURB OBJECT: DISCUSSIONS

​

​

• Is it required that a curb object be associated with a Curb Zone or Curb Space?
• If yes, that does not allow CDS to be used for complete asset management across a whole jurisdiction. Comment

​

• We have a centroid point latitude, longitude and max width/ height/ depth. Should there also be an optional polygon shape of the object?

​

GET INVOLVED

​

​

NEXT MEETING

• March 5, 2024

​

CONSIDER CDS IN YOUR WORK

• Get to know CDS and use the official v1.0 release
• Speak with your team or customers on how CDS can be used in upcoming projects
• What barriers do you have and what resources do you need?

​

PARTICIPATE IN THE WORKING GROUP

• Curb Working Group is gathering feedback for the next CDS release
• Sign up to get announcements from the Curb Management mailing list
• Attend meetings to discuss issues and hear from other contributors.
• 9am PT/Noon ET/6pm CET on Tuesdays (details on OMF public calendar).

​

JOIN THE OMF

• Get in touch with the OMF and learn how to become a member