documentation

git HEAD

    * IRIS->new: Add optional argument lookbehind

    * db-iris: Remove a useless HTTP request, resulting in slightly faster

               responses

    * db-iris -V / --track-via: Improve support for faraway stations

Travel::Status::DE::IRIS 1.13 - Thu Jan 26 2017

Note that here, I<viastation> must be a regular station name or DS100 code.

Caveat: Some trains change their identity along the route. For instance, the

line RE11 line in NRW has two identifiers, one for ME<ouml>nchengladbach

<-> Duisburg and one for Duisburg <-> Hamm. B<track-via> is not able to handle

those and will miss trains changing their identifier between I<station> and

I<viastation>

Caveat: Some trains may change their identity along the route. B<track-via> is

not able to handle those and will miss trains changing their identifier between

I<station> and I<viastation>

=item B<-x>, B<--exact>, B<--no-related>

=item B<lookahead> => I<int>

Compute only those results which are less than I<int> minutes in the future.

Default: 240 (4 hours).

Note that the DeutscheBahn IRIS backend only provides schedules up to four

to five hours into the future, and this module only requests data for up to

three hours. So in most cases, setting this to a value above 180 minutes will

have no effect. However, as the IRIS occasionally contains unscheduled

departures or qos messages known far in advance (e.g. 12 hours from now), any

non-negative integer is accepted.

Compute only results which are less than I<int> minutes in the future.

Default: 180 (3 hours).

Note that the DeutscheBahn IRIS backend only provides schedules up to four to

five hours into the future. So in most cases, setting this to a value above 240

minutes will have little effect. However, as the IRIS occasionally contains

unscheduled departures or qos messages known far in advance (e.g. 12 hours from

now), any non-negative integer is accepted.

=item B<lookbehind> => I<int>

Also check trains whose scheduled departure lies up to I<int> minutes in the

past. Default: 0.

This is useful when requesting departures shortly after a full hour. If,

for example, a train was scheduled to depart on 11:59 and has 5 minutes delay,

it will not be shown when requesting departures on or after 12:00 unless

B<lookbehind> is set to a value greater than zero.

Note that trains with significant delay (e.g. +30) may still be shown in this

case regardless of the setting of B<lookbehind>, since these receive special

treatment by the IRIS backend.

=item B<lwp_options> => I<\%hashref>