Skip to content

Releases: openmobilityfoundation/curb-data-specification

1.0.0

29 Apr 19:49
d0de87b
Compare
Choose a tag to compare

The 1.0.0 major release is the first release of the Curb Data Specification (CDS) after over 17 months of community work across dozens of public meetings, with 70+ organizations and 160+ individuals participating. It includes three major APIs to define Curbs and policies, track Events at the curb and determine sensor status, and derive Metrics for sessions and aggregate curb usage with a well defined methodology. CDS is currently being used by over two dozen organizations.

LICENSE and DISCLAIMER

Use of OMF Releases are bound by the OMF License and Disclaimer.

RELEASE PLAN

Our 1.0.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with recordings, slides, and minutes.

CHANGES

See work tagged with "Milestone 1.0.0" in Pull Requests, Issues, and Discussions for a full list of changes and history.

General CDS

  • Creation of spec from working group drafts and community code submissions
    • See About CDS web page for high level details

Curbs

  • The Curbs API is a standard way for cities to digitally publish curb locations and regulations, which can be shared with the public and with companies using curb space. It defines curb policies, curb zones, spaces in zones, and areas around curbs, and is used by Events and Metrics.

Events

  • The Events API is a standard way to transmit real-time and historic commercial events happening at the curb to cities. Event data can be derived from company data feeds, on street sensors, session payments, company check-ins, in-person parking personnel, and/or other city data sources. Connected to Curbs and used by Metrics.

Metrics

  • The Metrics API is a way to track curb usage session details and define common calculation methodologies to measure historic dwell time, occupancy, usage and other aggregated statistics. It defines sessions and aggregates data derived from raw Events data.

Minor Updates

  • Formatting of spec, links, TOCs, headers, etc

ACKNOWLEDGEMENTS

Thank you to GitHub pull request creators (Ride Report, Automotus, Coord, City of Seattle DOT), issue/discussion creators (City of Seattle DOT, Coord, IBI Group CurbIQ, Automotus, E&A), and commenters/contributors (Ride Report, IBI Group CurbIQ, Automotus, E&A, Coord, City of Seattle DOT, Populus, Washington DC DDOT, City of San Jose, City of Omaha Parking, Passport, ITE Curbside, SANDAG, Los Angeles DOT, SFMTA, City of Philadelphia, Ford AV, Waymo) for this release, our Curb Steering Committee members, and for the 70+ organizations and 160+ individuals that participated on our weekly public working group calls.

1.0.0 Release Candidate

25 Jan 14:51
1cab312
Compare
Choose a tag to compare
Pre-release

1.0.0

Release Candidate submitted 2022-01-25

Release Plan

The 1.0.0 major release is the first release of the Curb Data Specification (CDS) after over 15 months of community work across dozens of public meetings, with 70+ organizations and 160+ individuals participating. It includes three major APIs to define Curbs and policies, track Events at the curb and determine sensor status, and derive Metrics for sessions and aggregate curb usage with a well defined methodology.

CHANGES

See work tagged with "Milestone 1.0.0" in Pull Requests, Issues, and Discussions for a full list of changes and history.

General CDS

  • Creation of spec from working group drafts and community code submissions
    • See About CDS web page for high level details

Curbs

  • The Curbs API is a standard way for cities to digitally publish curb locations and regulations, which can be shared with the public and with companies using curb space. It defines curb policies, curb zones, spaces in zones, and areas around curbs, and is used by Events and Metrics.

Events

  • The Events API is a standard way to transmit real-time and historic commercial events happening at the curb to cities. Event data can be derived from company data feeds, on street sensors, session payments, company check-ins, in-person parking personnel, and/or other city data sources. Connected to Curbs and used by Metrics.

Metrics

  • The Metrics API is a way to track curb usage session details and define common calculation methodologies to measure historic dwell time, occupancy, usage and other aggregated statistics. It defines sessions and aggregates data derived from raw Events data.

Minor Updates

  • Formatting of spec, links, TOCs, headers, etc