-
Notifications
You must be signed in to change notification settings - Fork 232
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
Support batch telemetry #196
Conversation
The submission of telemetry data is now provided on `POST /vehicles/telemetry` to allow for batch telemetry data upload. It will still support single telemetry point submission, but also across an entire fleet of active vehicles or data for an entire trip. The goal is to make it easier and more flexible for Providers to submit data and to design to support larger scale datasets. Telemetry data no longer requires a trip_id and will be automatically associated with trips based on timestamps. The telemetry data for this endpoint is now structured as a simple JSON object and not GeoJSON. GeoJSON will remain for the GET (retrieval) endpoints.
Unsure why this is targeting the |
@toddapetersen can you have this PR target |
has conflicts with dev branch |
Conflicts resolved. Review and approve merge. |
} | ||
] } | ||
``` | ||
400 Failure Response: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably not be part of a specific section but rather be defined globally for the agency API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The responses are specific to each endpoint. The codes are global.
The submission of telemetry data is now provided on
POST /vehicles/telemetry
to allow for batch telemetry data upload. It will still support single telemetry point submission, but also across an entire fleet of active vehicles or data for an entire trip. The goal is to make it easier and more flexible for Providers to submit data and to design to support larger scale datasets. Telemetry data no longer requires a trip_id and will be automatically associated with trips based on timestamps.The telemetry data for this endpoint is now structured as a simple JSON object and not GeoJSON. GeoJSON will remain for the GET (retrieval) endpoints.