You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a train has a new terminus, this stopover is also incorrectly marked as cancelled: true, because in HAFAS the departure (but not the arrival) was marked as cancelled.
Expected behaviour: The parameter cancelled should only be true if both arrival and departure have been cancelled.
Example train today: ICE 316 with new final stop Aachen Hbf, which is returned as cancelled according to API.
The text was updated successfully, but these errors were encountered:
Little bit late to the party, but this is what we're getting from the HAFAS API. I'll look into it, wether we can make the cancellation consistent and a bit more... logical.
When a train has a new terminus, this
stopover
is also incorrectly marked ascancelled: true
, because in HAFAS the departure (but not the arrival) was marked as cancelled.Expected behaviour: The parameter
cancelled
should only be true if both arrival and departure have been cancelled.Example train today: ICE 316 with new final stop Aachen Hbf, which is returned as cancelled according to API.
The text was updated successfully, but these errors were encountered: