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

Trips and Timings missing stop name #145

Open
lightsprint09 opened this issue May 27, 2019 · 3 comments
Open

Trips and Timings missing stop name #145

lightsprint09 opened this issue May 27, 2019 · 3 comments

Comments

@lightsprint09
Copy link

When editing trips/timings it would be really helpful to have stop name to have a readable reference

@answerquest
Copy link
Collaborator

answerquest commented May 28, 2019

@lightsprint09 the GTFS format doesn't keep stop names anywhere except in the stops table; everywhere else the stop_id is referenced only. But I understand the convenience that would be if names could be seen.

Please check out our Payanam tool also. Static-gtfs-manager is made to adhere closely to gtfs format. In Payanam we flipped things around, and there you can build each route organically and at the end make gtfs. So that tool is recommended for situations where you're making things from scratch. Presently it's in beta stage equivalent : some improvements happening but the main stuff is made and working.

@lightsprint09
Copy link
Author

Makes totals sense. Thanks

@answerquest
Copy link
Collaborator

Keeping this open as it might be possible to do this. For example, in Default Route Sequence page I'm having the full stops data load up as a lookup json - that's what makes it possible to get the stop's name and location. In Trips/Timings page we may be possible to do something on display side.

@answerquest answerquest reopened this May 30, 2019
@mvanlaar mvanlaar mentioned this issue Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants