diff options
Diffstat (limited to '')
| -rw-r--r-- | todo.org | 23 |
1 files changed, 18 insertions, 5 deletions
@@ -1,18 +1,20 @@ #+TITLE: Traintrack Todos * Bugs found 2024-05-01 -** TODO auto-reconnect of /tracker websocket fails after android has gone to sleep -** DONE /tracker should remember its token, not constantly open a new one -either via a cookie or url parameter & redirect -** TODO train anchors are sorted wrong +** PROGRESS train anchors are sorted wrong probably based on sequence number, not based on time. results in "stuck" nonsensical delay information if we had a mistaken geolocation in the middle of the route too early + +changed to creation date, check in production +** TODO auto-reconnect of /tracker websocket fails after android has gone to sleep ** TODO stations with longer stopovers than ~2 minutes break delay extrapolation ** TODO head-turn at Passau (Gr) breaks delay extrapolation here the train has to stop & change direction, but is not in a station. Stefan says this usually takes ~5 minutes. Breaks delay predictions during that time, since we assume linear movement. +** DONE /tracker should remember its token, not constantly open a new one +either via a cookie or url parameter & redirect ** DONE do not give tripupdates after tickets are completed or outdated ** TODO tickets are not reliably marked completed ** TODO any kind of check against unrealistically fast travel? @@ -33,21 +35,32 @@ it easy to import single trips & <range of time>. should either error or (optionally) update the existing trip (perhaps change the completed-field of tickets int a status: scheduled (can still be changed by imports), in-progress (currently underway), done, archived) -* TODO built a better onboard unit +* TODO build a better onboard unit Friedrich still likes the idea of dedicated hardware (so people won't have to remember turning it on). I kinda like the idea of an android app for the onboard tablet. If it always displays current information, people might even remember to turn it on (at least people were interested today – 2024-05-01) +** IDEA display a warning on it if there's another tracker for the same trip +** IDEA display a warning on it if it's > 100m away from tracks +(possibly also make the server discard data in such cases) * TODO re-do configuration, replace conferer, possibly write own config library conferer is okay-ish, but it cannot (?) give warnings for config items that were e.g. misspelled in a yaml file. There's also no easy way to figure out where a config value came from afterwards. +* TODO replace the gtfs-based sequence with my own index during import +this should enforce that the difference between stations is always exactly 1 +(& possibly also that the first station is 0) * TODO somehow handle extra data without polluting the GTFS ** TODO gtfs blocks for handling trips done by the same vehicle ** TODO everything else goes into the database & can be inserted via the web frontend * TODO "cronjobs" that check for odd things things like: trip is scheduled to run, but has no tracker, trip has unreasonable delay values (< -5, > 40 or so) +* IDLE look at hasql-th for database things +https://hackage.haskell.org/package/hasql-th + +this would be another major rework, but persistent really is a little annoying +to use … * IDLE UI for entering custom / ad-hoc trips (i.e. those outside the gtfs schedule) * IDLE handle partially cancelled trips |