get_connecting_trains: departure delay is relevant for connecting trains
This commit is contained in:
parent
9f06b52a00
commit
6f107754fb
1 changed files with 4 additions and 3 deletions
|
@ -295,14 +295,15 @@ sub get_connecting_trains_p {
|
|||
$iris_train->[2] = $strp->parse_datetime(
|
||||
$stop->{arrival} );
|
||||
if ( $iris_train->[2]
|
||||
and $iris_train->[0]->arrival_delay
|
||||
and $iris_train->[0]->departure_delay
|
||||
and $stop->{arrival} eq
|
||||
$stop->{plannedArrival} )
|
||||
{
|
||||
# If the departure is delayed, but the arrival supposedly on time, we assume that this is an API issue and manually compute the expected arrival time.
|
||||
# This avoids cases where a connection is shown as arriving at its destination before having departed at a previous stop.
|
||||
$iris_train->[2]->add( minutes =>
|
||||
$iris_train->[0]->arrival_delay );
|
||||
$iris_train->[2]
|
||||
->add( minutes => $iris_train->[0]
|
||||
->departure_delay );
|
||||
}
|
||||
last;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue