aboutsummaryrefslogtreecommitdiff
path: root/lib/Server/GTFS_RT.hs (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-05-21Server.GtfsRealtime: yet another TripUpdateTooOldstuebinm1-4/+10
Google really is picky about these … and does not even seem willing to tell which thresholds it uses …
2024-05-15Server.GtfsRealtime: bugfixstuebinm1-1/+1
can't believe it was this simple … but seems to be all that was wrong. Tracktrain should now automatically remove tripUpdates for tickets whose trip has ended more than five minutes ago (taking delay into account). Nothing in the gtfs-rt spec says you should do this, but google likes to complain if one doesn't do this.
2024-05-03fix: tripupdates should not contain old tripsstuebinm1-2/+2
apparently i forgot an if here?
2024-05-02restructure: get the tracker to work againstuebinm1-7/+8
This should hopefully be the final (major) part of the restructuring: a tracker no longer has to know which trip it is on (and indeed it has no idea for now), instead the server keeps state about which trips are currently running and will insert incoming pings in a hopefully reasonable manner, based on their geoposition & time. There's lots of associated TODO items here (especially there should be manual overrides for all this logic in the web ui), but that's work for a future me. (incidentally, this also adds support for sending all log messages out via ntfy-sh)
2024-04-24restructure: save a ticket's stop in the databasestuebinm1-53/+62
now mostly independent of the gtfs, but still no live-reloading of it.
2024-04-20restructure: have "tickets" independent of gtfsstuebinm1-19/+30
this is mostly meant to guard against the gtfs changing under tracktrain, and not yet complete (e.g. a ticket does not yet save its expected stops, which it probably should).
2024-04-17general housekeepingstuebinm1-2/+1
jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
2024-04-17replace protocol-buffers with proto-lensstuebinm1-274/+172
I do not really like either option, but at least the second one seems more likely to be maintained (and a little less clunky to use, too, for what it's worth).
2023-05-23gtfs-rt: discard old trips from tripupdates feedstuebinm1-7/+12
google maps complains about it otherwise
2023-05-20expose the gtfs.zip used in the APIstuebinm1-1/+2
2023-01-28better web interface & cssstuebinm1-8/+8
2022-12-12stylish-haskell runstuebinm1-4/+5
2022-12-03gtfs-rt: set trip_descriptor.schedule_relationshipstuebinm1-1/+2
(hardcoded for now, since we don't have new trips)
2022-12-03unreasonably stupid and probably unnecessary codestuebinm1-5/+12
(but maybe google will like it)
2022-12-03set uncertainty in gtfs-rtstuebinm1-2/+2
2022-12-03this is almost certainly bullshitstuebinm1-6/+6
2022-12-03let's try something else as wellstuebinm1-1/+2
2022-12-03another gtfs rt thingie?stuebinm1-1/+2
2022-12-03fix google warningstuebinm1-1/+1
2022-10-16fix gtfs tripupdatesstuebinm1-83/+92
2022-09-14remove some extrapolation bugsstuebinm1-3/+3
2022-09-10gtfs realtime: add tripUpdate feedstuebinm1-9/+71
2022-08-27controlroom: lots of pretty little knobsstuebinm1-10/+10
(also some database schema changes, for good measure)
2022-07-11somewhat functioning control roomstuebinm1-1/+1
tbh i've kinda lost track at what has all been changed in this, but the control room form handling now works, and i can write announcements into the database. Now on to making it do useful things!
2022-07-03remove some unused importsstuebinm1-49/+42
2022-07-03add service monad (with built-in logging)stuebinm1-1/+2
2022-07-02better module namesstuebinm1-1/+2
2022-07-02rudimentary admin api implementationstuebinm1-0/+1
2022-07-02gtfs realtime: add vehicle positionsstuebinm1-16/+68
(or at least something that looks like it might be correct — though it carries very little information, and lacks things like what the next stop along the route is)
2022-07-02more or less functional servicealerts for gtfs rtstuebinm1-0/+155
(kinda barebones, but the important things should be there)