Saving vehicle locations should never error out when GTFS-RT feed is valid #14
Description
There's currently no data saved for Brampton in orion-vehicles from 4/29 to 5/04. This was because Orion was erroring out due to the GTFS endpoint in transify-api (staging-api.transify.ca at the time) was unavailable - this was because there was no valid GTFS available as the new one started on April 29 and the previous one didn't extend past that.
Orion should not be dependent on having a valid GTFS to save vehicle locations. It’s okay for the real-time map to fail in this instance, but not saving vehicles to S3 - that needs to be robust since its failure results in data loss.
The issue was addressed by:
- Receiving a valid GTFS URL from Brampton (as they'd changed the endpoint without notifying Transify)
- Using api.transify.ca as deployment issues on staging-api.transify.ca caused the real-time map on orion-api to break
The scope of this issue includes:
- Allow saving vehicle locations from GTFS-RT to S3 without relying on the GTFS - ideally without the need for a backfill/running a script once a valid GTFS is received.
Potential scope additions could include:
- Making the real-time map work when there is no GTFS that corresponds to the GTFS-RT feed at that instant in time
- Adding a staging environment to orion