blob: f4285edb7227a03bd4e544edb24c0138df277e2b (
plain)
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
43
44
45
|
#+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
* 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 auth (openID? How to test?)
** TODO dynamic content via logging/monitoring etc.
* TODO find out if we need to support VDV standards
* TODO decent-ish config files (probably yaml … sigh …)
* TODO do lots and lots of testing
* IDLE tracker stuff (as website)
* IDLE monitoring stuff (at least a grafana with trains would be nice)
* 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?"
|
