Add trip metadata to Agency #722
Labels
Agency
Specific to the Agency API
Unification
Work to unify MDS APIs like Agency, Provider with push/pull and data models
Milestone
Is your feature request related to a problem? Please describe.
Agency does not have access to trip metadata available in Provider, including
trip_distance
,standard_cost
,actual_cost
, andcurrency
. Most of the other trip data fields such asstart_time
andend_time
are available from the/event
stream.Describe the solution you'd like
One possibility is to add a
/trips
endpoint to Agency that is fully symmetrical with Provider's/trips
. To remove redundant route data, telemetry would not be sent during trips. This might make MDS more palatable to those with privacy concerns about in-trip tracking.Another is to add a /trips endpoint that has only the otherwise-unavailable metadata, and continue to use
/telemetry
to provide route data (define as all telemetry occurring betweenstart_time
andend_time
).A third is to add event-specific fields to the trip_end event, but this has significant drawbacks such as making events non-uniform, as well as putting tension on timely trip-end-event-reporting vs. accurate trip-metadata-reporting. The trip distance may need to be calculated in a data pipeline, for example.
Is this a breaking change
Impacted Spec
For which spec is this feature being requested?
agency
Describe alternatives you've considered
One possibility is to just use Provider and Agency side-by-side, but that's not on the table for LADOT.
Additional context
Nothing at the moment.
The text was updated successfully, but these errors were encountered: