Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(sometimes, departure_wings contains duplicate entries)
|
|
|
|
|
|
|
|
|
|
|
|
across days
|
|
|
|
|
|
|
|
|
|
This is a preparation for a future refresh_realtime function which only
updates the realtime (fchg) part of all departures.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
selected station
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This way, if a train has so much delay that its scheduled data was not
requested in the first place, it's still possible to compared its scheduled
route with its actual route
|
|
|
|
|
|
|
|
|
|
|