What of data sources should our curb Events specification support?

[jfh01]

We have discussed the need for the events specification to accommodate data from a variety of sources. Some of the ones that have been mentioned are:

• In-ground / meter-mounted sensors
• Computer vision / fixed cameras
• ALPRs (fixed or mobile)
• Fleet-reported data
• Meter data (e.g. parking sessions)
• Bluetooth / RFID (need to define in more detail)

What other kinds of data sources should we accommodate? Please also share specific companies and technologies you are familiar with so that we can research/reach out as part of the design process.

[jiffyclub]

Maybe GPS coordinates/duration or GPS trip routes and timing?

[ITE-Curbside]

Street centerline data in the SharedStreets linear reference format.

[ITE-Curbside]

CurbLR data standard for describing curb regulations.

[ITE-Curbside]

CurbIQ: https://curbiq.io/

[ITE-Curbside]

Mapillary physical feature data.

[ITE-Curbside]

Coord app for curb uses, TOD, and revenue data as well as Coord Collector to geocode physical features.

[ITE-Curbside]

INRIX Road Rules platform.

[jacobmalleau]

You mentioned meter data for payment sessions, but we should also accommodate payment session data from parking payment apps.

[schnuerle]

Many of the geographic/road suggestions here seem to apply to the Curbs API, not Events API.

For payment session data in Events, actual_cost and currency has been added to the event object as optional, aligning with MDS:

https://github.com/openmobilityfoundation/curb-data-specification/blob/feature-release-work-1/events/README.md#curb-event