tracktrain - track trains on their traintracks

	Commit message (Collapse)	Author	Files	Lines
2024-05-15	Server.GtfsRealtime: bugfix	stuebinm	1	-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-03	fix: tripupdates should not contain old trips	stuebinm	1	-2/+2
	apparently i forgot an if here?
2024-05-02	restructure: get the tracker to work again	stuebinm	1	-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-24	restructure: save a ticket's stop in the database	stuebinm	1	-53/+62
	now mostly independent of the gtfs, but still no live-reloading of it.
2024-04-20	restructure: have "tickets" independent of gtfs	stuebinm	1	-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-17	general housekeeping	stuebinm	1	-2/+1
	jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
2024-04-17	replace protocol-buffers with proto-lens	stuebinm	1	-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-23	gtfs-rt: discard old trips from tripupdates feed	stuebinm	1	-7/+12
	google maps complains about it otherwise
2023-05-20	expose the gtfs.zip used in the API	stuebinm	1	-1/+2

2023-01-28	better web interface & css	stuebinm	1	-8/+8

2022-12-12	stylish-haskell run	stuebinm	1	-4/+5

2022-12-03	gtfs-rt: set trip_descriptor.schedule_relationship	stuebinm	1	-1/+2
	(hardcoded for now, since we don't have new trips)
2022-12-03	unreasonably stupid and probably unnecessary code	stuebinm	1	-5/+12
	(but maybe google will like it)
2022-12-03	set uncertainty in gtfs-rt	stuebinm	1	-2/+2

2022-12-03	this is almost certainly bullshit	stuebinm	1	-6/+6

2022-12-03	let's try something else as well	stuebinm	1	-1/+2

2022-12-03	another gtfs rt thingie?	stuebinm	1	-1/+2

2022-12-03	fix google warning	stuebinm	1	-1/+1

2022-10-16	fix gtfs tripupdates	stuebinm	1	-83/+92

2022-09-14	remove some extrapolation bugs	stuebinm	1	-3/+3

2022-09-10	gtfs realtime: add tripUpdate feed	stuebinm	1	-9/+71

2022-08-27	controlroom: lots of pretty little knobs	stuebinm	1	-10/+10
	(also some database schema changes, for good measure)
2022-07-11	somewhat functioning control room	stuebinm	1	-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-03	remove some unused imports	stuebinm	1	-49/+42

2022-07-03	add service monad (with built-in logging)	stuebinm	1	-1/+2

2022-07-02	better module names	stuebinm	1	-1/+2

2022-07-02	rudimentary admin api implementation	stuebinm	1	-0/+1

2022-07-02	gtfs realtime: add vehicle positions	stuebinm	1	-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-02	more or less functional servicealerts for gtfs rt	stuebinm	1	-0/+155
	(kinda barebones, but the important things should be there)