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

Bring rich telemetry data to Provider Status Endpoint #616

Closed
quicklywilliam opened this issue Jan 21, 2021 · 5 comments · Fixed by #653
Closed

Bring rich telemetry data to Provider Status Endpoint #616

quicklywilliam opened this issue Jan 21, 2021 · 5 comments · Fixed by #653
Labels
Provider Specific to the Provider API
Milestone

Comments

@quicklywilliam
Copy link
Contributor

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

A remaining inconsistency between Agency and Provider is that the Status endpoint's location data does not include Speed data. This data could be useful in assessing regulatory compliance with speed rules. This data is currently present in Agency, so adding it to Provider would also create greater parity.

Describe the solution you'd like

Add the speed field to status events in Provider.

Is this a breaking change

No

Impacted Spec

  • provider

Additional context

This issue was broken out from #589, which originally requested these data for both Provider endpoints.

@quicklywilliam
Copy link
Contributor Author

I've filed this issue based on the possible use case of wanting to assess compliance with speed-related rules. There may be other regulatory use cases I am overlooking, please chime in if so!

@schnuerle
Copy link
Member

For some more context, here is what is currently supported in Agency. Note the requirements are all listed as "Required if Available" from the provider.

https://github.com/openmobilityfoundation/mobility-data-specification/tree/release-1.1.0/agency#telemetry-data

Name Type Required? Description
gps.lat Double Required Latitude of the location
gps.lng Double Required Longitude of the location
gps.altitude Double Required if Available Altitude above mean sea level in meters
gps.heading Double Required if Available Degrees - clockwise starting at 0 degrees at true North
gps.speed Float Required if Available Speed in meters / sec
gps.accuracy Float Required if Available Accuracy in meters
gps.hdop Float Required if Available Horizontal GPS or GNSS accuracy value (see hdop)
gps.satellites Integer Required if Available Number of GPS or GNSS satellites

@schnuerle schnuerle added the Provider Specific to the Provider API label Jan 25, 2021
@schnuerle schnuerle added this to the Next Release milestone Jan 25, 2021
@schnuerle schnuerle modified the milestones: Next Release, 1.2.0 Feb 12, 2021
@schnuerle
Copy link
Member

We'll be talking about this at today's Working Group meeting.

@schnuerle
Copy link
Member

schnuerle commented Jun 25, 2021

Similar to #589, does anyone feel comfortable making a pull request for this, adding the Required if Available fields and others discussed to Provider Status Changes? There is a PR #73 but I think it's out of date (and the CLA needs to be signed). Could be the same PR.

@quicklywilliam
Copy link
Contributor Author

Addressed by #653.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Provider Specific to the Provider API
Projects
None yet
2 participants