You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A functionality that would parse the SIRI output files from S3 into objects that represent individual rides.
Each object should contain the route info + ride info + GPS data from siri.
These object should support later aggregation of split rides and will be upload to our future chosen database.
The text was updated successfully, but these errors were encountered:
Edited the issue swapping "trip" for "ride". We use "ride" for SIRI to avoid confusion with GTFS "trips", and since they do not designate the same thing (a ride could be a bus just standing still at the repair-shop for example or driving in some random place towards its next trip, and these should not be considered relevant trips of a route).
cjer
changed the title
Parse SIRI csv output into aggregated trips
Parse SIRI csv output into aggregated rides
Feb 18, 2020
I went over some past issues and many are related / overlapping.
This should rely on the work in #174 and is part of Epic #270 (which needs to be updated accordingly) and also Epic #197 (which also needs an update).
This also replaces parts of #243, which I think we should close and split. That one is also part of a SiriSplunkToMongo milestone which we probably want to update.
So, I think we kind of need to have a meeting around re-organizing this :)
A functionality that would parse the SIRI output files from S3 into objects that represent individual rides.
Each object should contain the route info + ride info + GPS data from siri.
These object should support later aggregation of split rides and will be upload to our future chosen database.
The text was updated successfully, but these errors were encountered: