diff options
| -rw-r--r-- | todo.org | 14 |
1 files changed, 10 insertions, 4 deletions
@@ -9,7 +9,8 @@ ** DONE do the protobuf stuff ** DONE implement vehicle positions ** DONE implement service alerts -** TODO implement trip updates +** DONE implement trip updates +** TODO test against actual real-world applications & stuff * TODO frontend stuff ("leitstelle"/controlroom) ** DONE do stuff with yesod ** TODO auth (openID? How to test?) @@ -18,19 +19,24 @@ ** TODO more cross-references (e.g. list of dates on which a trip runs) ** TODO links to osm / embed leaflet * TODO decent-ish config files (probably yaml … sigh …) -* TODO estimate delays +** DONE basic config +** TODO more options, esp. regarding extrapolation +* DONE estimate delays basically: list of known delays in a db table, either generated from trip pings & estimates or user-defined in the control room ** DONE properly handle timezones during gtfs parsing so no one else has to deal with that turns out that's impossible, but it looks to be fine the way it is now +* TODO "turn off" a specific trip (as workaround in case it's cancelled or something) * TODO do lots and lots of testing -* IDLE tracker stuff (as website) +* DONE tracker stuff (as website) * IDLE monitoring stuff (at least a grafana with trains would be nice) probably requires a fork of that grafana package * IDLE somehow handle extra data (e.g. track kilometres) without polluting the GTFS -- same for "how do we know how much we can reduce delay between stops?" +** TODO same for "how do we know how much we can reduce delay between stops?" +** DONE can use block_id for turnaround times * IDLE Handle extraordinary trips (i.e. those outside the gtfs schedule) +* IDLE handle partially cancelled trips * IDLE find out if we need to support VDV standards focus on gtfs rt first |