Handle changing schedule data; match trips to appropriate schedule
Nate-Wessel opened this issue · 3 comments
Nate-Wessel commented
Currently there is no way of handling changes to the schedule. We keep randomly checking the schedule data from the NextBus API to see if anything has changed, and we store any changes. But nothing is done to link the most recent data to an ending trip. This has worked because nothing has changed during script execution yet.
When the set of stops is selected, it needs to be the most recent set of stops only.
Nate-Wessel commented
we are currently selecting the latest 'direction' but not checking the dates on the stop records.
Nate-Wessel commented
Given the retroactive processing which is possible, this may be quite complicated. We may need to check for nearest rather than most recent.
Nate-Wessel commented
This is now taken care of :-)