Traines

Voilà a shell script that splits the rendering into parts of equal duration, starts up multiple Docker containers for rendering simultaneously, and concatenates the output videos when the workers are...

Auto-generating the schemas from the TS typings instead of from some JSON instances indeed seems better. There is only one drawback I have noticed so far: It doesn't distinguish between...

In case that didn't become clear, I was talking about the endpoints like journeys, departures, arrivals, etc., which in the first iteration have completely separate schemas. In a generated client,...

I have changed the approach now. - use one central schema to reuse ($ref) definitions between endpoints, so that only one class per type is generated in clients - generate...

Some thoughts: * There was something going on why I needed both `createClient.Foo` and `Foo`, but I don't remember why, have to look at it again. Or maybe it was...

> With a) so many projects in general and b) so many stacked on top of hafas-client, I try to reduce both manual maintenance and human error caused by it...

Ich schreibe das mal hier dazu, auch wenn es sich um `location_type`s 1, 2 und 3 handelt, die ja aber alle in `stop_times.txt` nicht zulässig sind. Besonders prominent gerade mit...

I have looked into this, the issue is that apparently HAFAS for some trains gives out different trip IDs for the same train on the departure and arrival boards. E.g....

I have changed it now to only take the fahrtNr and line.ID if they're longer than 3 characters, and fall back to tripID otherwise. This fixes Düsseldorf, but I fear...

Sorry for the wait but now the entire `tripId` is used unless all of the following conditions are satisfied: * `line.id` >= 4 chars, including at least one digit *...