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

S3 per-route timetable files are empty for date key 2020-02-03 #595

Open
exxonvaldez opened this issue Feb 29, 2020 · 0 comments
Open

S3 per-route timetable files are empty for date key 2020-02-03 #595

exxonvaldez opened this issue Feb 29, 2020 · 0 comments
Labels
Backend Python and API stuff Bug Something isn't working

Comments

@exxonvaldez
Copy link
Contributor

exxonvaldez commented Feb 29, 2020

The timetable files for date key 2020-02-03 contain no arrivals. For example, the contents of http://opentransit-data.s3.amazonaws.com/timetables/v1/muni/2020-02-03/timetables_v1_muni_2020-02-03_1.json.gz are:

{"version":"v1","agency":"muni","route_id":"1","date_key":"2020-02-03","timezone_id":"America/Los_Angeles","service_ids":["1_merged_9191495"],"arrivals":{}}

Edit: this affects production and my dev build. I cannot get schedule adherence stats at the stop to stop level for dates from Feb 3 to Feb 21. Route summary does work.

Not sure if this is a known issue to @youngj .

@exxonvaldez exxonvaldez added Backend Python and API stuff Bug Something isn't working labels Feb 29, 2020
@exxonvaldez exxonvaldez changed the title S3 timetable files are empty for date key 2020-02-03 S3 per-route timetable files are empty for date key 2020-02-03 Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend Python and API stuff Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant