There is no way to provide double parking event locations in the Events API with exact location

[rneubauer]

Is your feature request related to a problem? Please describe.

After implementing cameras at scale across customer cities, the first thing that our customers asked for were double-parking events and locations. After looking into the events API, there is currently only a way to provide a double-parking event in a defined travel lane, but there is currently no way to provide the cross section of where that event happened for an entire block. Other events like unauthorized parking or stopping in the non-travel (parking) lane are mapped to the lane adjacent to the curb and can be provided via the current events API.

Describe the solution you'd like

As a simple short-term solution, we are proposing to add a double parking event tied to a camera ID in https://github.com/openmobilityfoundation/curb-data-specification/issues/147. This will allow us to map the event on maps based on the camera, which will also allow us to report on the affected zones related to that camera. The reason this is a short term solution is because it would not require any breaking changes to the current CDS schema.

Long-Term Solution - We would want to provide the exact lat/long of the double parking events.

Is this a breaking change

No, not breaking - This would not break the current schema and would just be an addition to the existing version.

Impacted Spec

For which spec is this feature being requested?

Events

Describe alternatives you've considered

We have thought about storing this data in our backend databases, but then it will not allow us to provide events via CDS API to other systems to locate where issue are occurring.

[jiffyclub]

The Curb Event model does have an event_location field that allows reporting an exact lat/lon for an event. It seems like the issue might be more that there is no way to indicate that the event is a double-parking event? Available event types are listed here.

[rneubauer]

That is correct, but unless the exact lat/long can be detected from the CV model there needs to be another reference point to show where it happened in the travel lane along the block. Tying it to an adjacent loading, ADA, or parking zone won't really work for a few reasons:

1. If the car parks halfway between two zones, we don't want to get into fractional measurements between two zones.
2. We don't really care about the adjacent zone. The drive that is parking is more likely double parking because of a business on the curb that they are picking up food or a delivery form ,etc. which definitely cant be defined in the Curbs API at this point.

This is why we are currently mapping the events to the camera that captured the event and then providing the pixel coordinates in our backed.