Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

guidance on how to use telemetry data for compliance #877

Open
jean-populus opened this issue Sep 5, 2023 · 3 comments
Open

guidance on how to use telemetry data for compliance #877

jean-populus opened this issue Sep 5, 2023 · 3 comments
Labels
Agency Specific to the Agency API discussion Feedback is requested on an ongoing basis Provider Specific to the Provider API

Comments

@jean-populus
Copy link
Collaborator

jean-populus commented Sep 5, 2023

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 -

To represent trip telemetry, the data should include every observed point in the trip...

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

  • I'm not sure

Impacted Spec

  • agency
  • provider

Describe alternatives you've considered

none

Additional context

none

@jean-populus jean-populus changed the title quality of in-trip telemetry reporting for compliance guidance on how to use telemetry data for compliance Sep 6, 2023
@schnuerle
Copy link
Member

Are you thinking there should be guidance on how cities can request this, eg. "telemetry points must be sent at least every 5 seconds"? Or recommendations on how cities should rely on the pings they do get when they are infrequent or inaccurate?

@jean-populus
Copy link
Collaborator Author

There could be guidance on minimum telemetry points frequency, or acceptance of using best-guess trip trace for compliance.

Currently we've run into a situation where the provider only wants compliance verified using telemetry points but then there's a disincentive to provide good data so the city is pushing back.

It would be great if we could provide guidance on this or incentivize providers to send good data.

@schnuerle schnuerle added Provider Specific to the Provider API Agency Specific to the Agency API discussion Feedback is requested on an ongoing basis labels Sep 25, 2023
@schnuerle
Copy link
Member

With 2.1 we have a chance to add this guidance if you'd like it to be part of the spec itself. If you can propose a wording for this that might get us started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agency Specific to the Agency API discussion Feedback is requested on an ongoing basis Provider Specific to the Provider API
Projects
None yet
Development

No branches or pull requests

2 participants