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

Updated GTFS (stop changed) updates the Schedule Report but doesn't update Maps #246

Open
wkulesza opened this issue Sep 18, 2021 · 0 comments

Comments

@wkulesza
Copy link

Expected functionality
Loading a new, updated GTFS that replaces a previously wrong stop in the stop sequence should draw the shape correctly.

Describe the bug
Eventhough the GTFS is updated, and reports/schedule shows the correct stop, the maps in the transitclock still show the old, wrong stop.

To Reproduce
Using Transitclock docker to start the docker, then update GTFS (changing the stop in the stop sequence, rebuild shapes) and re-run go.sh script (comment all lines in go.sh that delete and remove database commands to keep the old database.

Screenshots
http://prntscr.com/1sqjfv8 - Maps are showing Sedzinko, wies stop which is incorrect.
http://prntscr.com/1sqjj8p - Schedule reports are showing Sątopy, wies stop which is correct

Version:
TransitClock Docker MPK branch, modified to use Traccar module for AVL data.

Configuration:
Please provide relevant configuration information.

Additional context
Add any other context about the problem here.

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

1 participant