diff options
Diffstat (limited to 'todo.org')
| -rw-r--r-- | todo.org | 39 |
1 files changed, 14 insertions, 25 deletions
@@ -1,45 +1,34 @@ #+TITLE: Traintrack Todos -* TODO Handle extraordinary trips -(i.e. those outside the gtfs schedule) * DONE Handle service announcements (per trip & day, nothing else needs to be supported) -* TODO allow trip ping ingest via websockets +* DONE allow trip ping ingest via websockets * TODO implement GTFS realtime (this actually doesn't look too bad?) ** DONE do the protobuf stuff ** DONE implement vehicle positions ** DONE implement service alerts ** TODO implement trip updates -* TODO frontend stuff ("leitstelle") -** TODO write a webform API -- cancel trip -- add announcement to trip -- add trip -- add delay (only "now", not per-station?) -- edit trip metainfo -- add extra train number not in gtfs (optional) -- -** TODO static pages frontend -needed pages: - - auth (openID?) - - trips, filterable by: everything, currently running - - actions: cancel trip, add trip date - - single trip view - - actions: add announcement, cancel - - self-reload page to keep up to date? - - potentially more (e.g. accessability info for gtfs-rt) - - (optional) add extraordinary trip +* TODO frontend stuff ("leitstelle"/controlroom) +** DONE do stuff with yesod ** TODO auth (openID? How to test?) ** TODO dynamic content via logging/monitoring etc. -* TODO find out if we need to support VDV standards +** TODO nicer rendering for timestamps (e.g. "in three minutes", "5 seconds ago", etc.) +** 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 +basically: list of known delays in a db table, either generated from +trip pings & estimates or user-defined in the control room * TODO do lots and lots of testing * IDLE 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?" +* IDLE Handle extraordinary trips +(i.e. those outside the gtfs schedule) +* IDLE find out if we need to support VDV standards +focus on gtfs rt first |