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
{{ message }}
This repository has been archived by the owner on Jun 20, 2020. It is now read-only.
It looks like the stops displayed after selecting a route are based on the first trip of the day. If the first trip of the day only goes to some of that route's stops, you never get to see all the stops for the route. (In Venice, for example, the first trip of route 1 only hits the last five stops on the route.)
During initialization, maybe the app should search through all the trips for each route and store every unique stop? It's a shame none of the gtfs files make this info easily accessible...
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like the stops displayed after selecting a route are based on the first trip of the day. If the first trip of the day only goes to some of that route's stops, you never get to see all the stops for the route. (In Venice, for example, the first trip of route 1 only hits the last five stops on the route.)
During initialization, maybe the app should search through all the trips for each route and store every unique stop? It's a shame none of the gtfs files make this info easily accessible...
The text was updated successfully, but these errors were encountered: