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.
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.