todo.org


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

#+TITLE: Traintrack Todos


* DONE Handle service announcements
(per trip & day, nothing else needs to be supported)
* 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
** 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?)
** TODO dynamic content via logging/monitoring etc.
** 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 …)
** 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
* 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
** 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