guidance on how to use telemetry data for compliance #877
Labels
Agency
Specific to the Agency API
discussion
Feedback is requested on an ongoing basis
Provider
Specific to the Provider API
Is your feature request related to a problem? Please describe.
Telemetry is used to calculate compliance for No Ride and Slow Ride policies but there's no standard for reporting this information. The description -
Allows for a lot of variability in how this information is reported which can affect compliance with these policies.
Cities need guidance on how to use these "pings" for compliance when there might not be enough represent the possible route traveled. For example, we receive telemetry with "ping" on either side of a No Ride zone but none in the middle even though the zone encompasses a large area. Has the scooter gone in a straight line through the No Ride zone? Or has it taken the long way around it?
Describe the solution you'd like
I don't have a proposed solution though we can consider how to increase the frequency (quality) of telemetry when in-trip or formally allowing for the use of generated trip traces for compliance.
Is this a breaking change
Impacted Spec
agency
provider
Describe alternatives you've considered
none
Additional context
none
The text was updated successfully, but these errors were encountered: