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

Allow running save_routes on historic GTFS files #626

Open
EddyIonescu opened this issue Apr 2, 2020 · 0 comments · May be fixed by #638
Open

Allow running save_routes on historic GTFS files #626

EddyIonescu opened this issue Apr 2, 2020 · 0 comments · May be fixed by #638
Assignees
Labels
Backend Python and API stuff Good First Issue Good for newcomers

Comments

@EddyIonescu
Copy link
Member

Currently we only store the latest version of route-configs, but have versioning for timetables.

save_routes.py runs daily and updates these using the recentmost GTFS that is available.

Using TransitFeeds (https://transitfeeds.com/api/swagger/) we can run save_routes.py on older versions of the GTFS based on the start/end dates of each GTFS file. Then we'll be able to show scheduled times and the proper routes for dates in the past.

For the most part, the agency config can be changed while remaining compatible with previous versions of the agency's network. However, for cases like where a branch is completely changed or the routes are redesigned, a different version would be required here too (see #127), which can be done in another issue and PR.

@EddyIonescu EddyIonescu added Good First Issue Good for newcomers Backend Python and API stuff labels Apr 2, 2020
@Brian-Lee Brian-Lee self-assigned this Apr 16, 2020
@Brian-Lee Brian-Lee linked a pull request Apr 24, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend Python and API stuff Good First Issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants