| Commit message (Collapse) | Author | Files | Lines |
|---|
|
these used to go wrong in case there was no real-time info on departure
times. Instead traveltext now falls back on scheduled departure times if
no real-time info is available.
These still fail sometimes (at exit-only stops both appear to be unset
on the oebb hafas), but it's a lot better than what was before.
Also I've observed travelynx returning actual null values for missing
time stamps now, so the old hack of checking if timestamp = unix epoch
and considering that "unknown" might no longer be necessary, but I'm
keeping it around just in case.
|
|
these are not present when other hafas backends than the DB one were
used for the trip's checkin.
|
|
(travelynx sends these as the literal epoch value, which led
to really confusing results, printing exactly the time zone offset
as arrival time)
|
|
… lots and lots of traits …
|
