diff options
| author | stuebinm | 2024-05-15 01:12:09 +0200 |
|---|---|---|
| committer | stuebinm | 2024-05-15 01:12:09 +0200 |
| commit | 0c9b3a6dba6850ce526d1d397f35aa6ad76beb50 (patch) | |
| tree | f7b307548904ed0c0bb1459b9d09da63ed0a4243 /todo.org | |
| parent | 59670bdb6f0a3bba898274eadf47707e93bea195 (diff) | |
Server.Ingest: new handling of unassigned trackers
now takes all potential stops along each trip into account when guessing
tickets; also checks if a ticket is still likely in case the tracker
switched its direction. This should solve many cases where a tracker is
accidentally turned off or falls asleep halfway before the last station
of one trip, then wakes up in the middle of the next.
Diffstat (limited to '')
| -rw-r--r-- | todo.org | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -4,8 +4,6 @@ ** 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 matching of tokens to trip ought not to assume trips are at their start position -this produces horrible results if the tracker is started towards a trip's end ** TODO 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 @@ -18,6 +16,8 @@ that time, since we assume linear movement. ** 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? +** DONE matching of tokens to trip ought not to assume trips are at their start position +this produces horrible results if the tracker is started towards a trip's end * TODO implement GTFS realtime ** TODO get google to accept trip updates ** DONE get google to accept service alerts |