Closed timaschew closed 4 years ago
[...] Transportr was only showing the canceled flag for the next two hours/journeys [...]. So I checked what data the hafas client will give me and it gives me the same output unfortunately:
This is actually a good sign, because it at least it returns the same data.
The fact that the different HAFAS endpoints have different delay data, as well as different sets of human-written warnings, is unfortunately nothing that this project can change. From what I've heard, it's because of bureaucratic and complex technical reasons (which mostly sound unreasonable from an outside perspective) that won't disappear soon, so we can only work around it.
I've started doing that with ~two projects find-db-hafas-leg-in-another-hafas
and augment-vbb-hafas
that I've forgot to publish (will do that as soon as I have time)~ find-hafas-leg-in-another-hafas
, but merging data from two HAFAS (or even non-HAFAS) endpoints is a complex problem. With pan-european-public-transport
, I'm trying to take this approach as far as possible.
[...] only VBB is showing the 2 hours as canceled, but at least they show warnings for later journeys. [...] Can we bring the warning somehow into the response of the journey?
Yes. Please find a future connection (ideally >2 days in the future, so we can debug properly) and query with the vbb
and/or bvg
profiles, with remarks: true
. Hopefully it will give you some results.
If it doesn't: Parsing the semi-structured messages is hard, and currently hafas-client
parses only some of them (here and here. AFAIK public-transport-enabler
and TripKit
als only parse some.
I recently talked to @opyh though, and they have a lot of recorded messages or a better parsing logic. See also #5, #90 and #131 for tracking Issues.
Closing this because we can't really do something about the low-quality upstream data, just work around it (by putting layers of abstraction on top, like in pan-european-public-transport
).
Today my regional train was canceled, it was already announced yesterday and I've realized that my Android app Transportr was only showing the canceled flag for the next two hours/journeys but not on the subsequent journeys even if it's already known that they will be canceled.
So I checked what data the hafas client will give me and it gives me the same output unfortunately:
Then I checked the websites of Deutsche Bahn, BVG and VBB and I've realized that only VBB is showing the 2 hours as canceled, but at least they show warnings for later journeys. But DB and BVG are showing cancelations for all journeys (the planned outage is only until 2pm).
Can we bring the warning somehow into the response of the journey?
Here are some screenshots and the warning message: