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
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.
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
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 .
The text was updated successfully, but these errors were encountered: