aboutsummaryrefslogtreecommitdiff
path: root/lib/Server/GTFS_RT.hs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Server.GtfsRealtime: yet another TripUpdateTooOldstuebinm2024-05-211-4/+10
| | | | | Google really is picky about these … and does not even seem willing to tell which thresholds it uses …
* Server.GtfsRealtime: bugfixstuebinm2024-05-151-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.
* fix: tripupdates should not contain old tripsstuebinm2024-05-031-2/+2
| | | | apparently i forgot an if here?
* restructure: get the tracker to work againstuebinm2024-05-021-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)
* restructure: save a ticket's stop in the databasestuebinm2024-04-241-53/+62
| | | | now mostly independent of the gtfs, but still no live-reloading of it.
* restructure: have "tickets" independent of gtfsstuebinm2024-04-201-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).
* general housekeepingstuebinm2024-04-171-2/+1
| | | | | jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
* replace protocol-buffers with proto-lensstuebinm2024-04-171-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).
* gtfs-rt: discard old trips from tripupdates feedstuebinm2023-05-231-7/+12
| | | | google maps complains about it otherwise
* expose the gtfs.zip used in the APIstuebinm2023-05-201-1/+2
|
* better web interface & cssstuebinm2023-01-281-8/+8
|
* stylish-haskell runstuebinm2022-12-121-4/+5
|
* gtfs-rt: set trip_descriptor.schedule_relationshipstuebinm2022-12-031-1/+2
| | | | (hardcoded for now, since we don't have new trips)
* unreasonably stupid and probably unnecessary codestuebinm2022-12-031-5/+12
| | | | (but maybe google will like it)
* set uncertainty in gtfs-rtstuebinm2022-12-031-2/+2
|
* this is almost certainly bullshitstuebinm2022-12-031-6/+6
|
* let's try something else as wellstuebinm2022-12-031-1/+2
|
* another gtfs rt thingie?stuebinm2022-12-031-1/+2
|
* fix google warningstuebinm2022-12-031-1/+1
|
* fix gtfs tripupdatesstuebinm2022-10-161-83/+92
|
* remove some extrapolation bugsstuebinm2022-09-141-3/+3
|
* gtfs realtime: add tripUpdate feedstuebinm2022-09-101-9/+71
|
* controlroom: lots of pretty little knobsstuebinm2022-08-271-10/+10
| | | | (also some database schema changes, for good measure)
* somewhat functioning control roomstuebinm2022-07-111-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!
* remove some unused importsstuebinm2022-07-031-49/+42
|
* add service monad (with built-in logging)stuebinm2022-07-031-1/+2
|
* better module namesstuebinm2022-07-021-0/+209
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 06:36:55 +0000