-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bug: zero trips showing up in fct_scheduled_trips for select agencies #3383
Comments
This query seems okay: But... By this query: Maybe we are still using the previous gtfs and haven't properly ingested the new one? |
So there are a decent number of stop_times that didn't get processed, while the stops did get processed. If you compare the count of the unique feeds used for stops vs the unique feeds used for stop times, there is an incongruity.
There is a slight pattern that makes me think the error is cause by this issue: |
So i've thought of two potential fixes for this issues:
Another option:
and manually re-reun the processing / zipping. And do the same for the shapes that might be missing. Pro: potentially easier. faster. |
I reran all the failed jobs (slowly, painfully, manually) , I got all to work but 2 (which consistently fail). I did a query to see if this fixed things but I think I need to wait for a Sunday Full Refresh for that data to populate. Not sure if it's worth it to fix those last two. |
I spoke with @vevetron and I think this one can be marked as closed as we should have all needed data now. |
Both B-Line and Long Beach are resolved for this issue, Sacramento is not. Sacramento's issue is likely because they publish their GTFS a head of schedule without merging in the previous GTFS, and we don't handle that scenario. |
Describe the bug
There are zero trips in the fct_scheduled_trips table for:
To Reproduce
Expected behavior
There should be scheduled trips appearing in this table for all active dates.
Additional context
B-Line and Long Beach use calendar-dates-only style for publishing their schedule. However, I'm not sure if this is the cause of the problem.
The text was updated successfully, but these errors were encountered: