SYNOPSIS

VERSION

DESCRIPTION

efa is a command line client for EFA-based public transit routing
interfaces, e.g. http://efa.vrr.de. efa requests connections between two
points and displays the results.

By default, the EFA service at http://efa.vrr.de (operated by
Verkehrsverbund Rhein-Ruhr) is used, which supports most places in Germany.
A list of all supported EFA instances can be retrieved with -l and a custom
instance can be selected using -sservice or -uurl. It is also
possible to probe all known EFA services for a specific connection using the
-A and -D options.

OPTIONS

In all cases, if you want stop to be an address or "point of interest", you
can set it to 'addr:something' or 'poi:something'.

-a|--arrivehh:mm

Journey end time (overrides --time/--depart)

-A|--auto-url|--discover-and-print

Probe all known EFA entry points for the specified connection. Print the first
result which was not an error.

Note that this may take a while and will not necessarily return the best
result. Also, using this option by default is not recommended, as it puts
EFA services under considerable additional load.

-b|--bike

Request connections allowing the passenger to take a bike with them.
Note that this may cause efa to display no routes at all -- In that case,
the backend was unable to find such connections or didn't know about
their bike-support.

-B|--bike-info

Show information about bike support, but do not select routes based on it.
In essence, this option simply changes the --ignore-info default. It is
useful when --bike did not return any routes even though most of the
route has bike support.

-d|--datedd.mm.[yyyy]

Journey date. Also accepts the shortcut tomorrow.

-D|--discover

Probe all known EFA entry points for the specified connection. No routes are
returned in this case. Instead, efa will print the URLs and names of all
entry points which did not return an error.

-u|--efa-urlurl

URL to the EFA entry point, defaults to
http://efa.vrr.de/vrr/XSLT_TRIP_REQUEST2. Depending on your location, some
urls may contain more specific data than others. See
Travel::Routing::DE::EFA(3pm) and the -l option for alternatives.

Request connections satisfying all of the specified accessibility types
(comma-separated list, option may be repeated). Please note that this may cause
the backend to return no results at all, either because no such connection
exists or because the required lines do not have the correct accessibility
attributes set.

The following types are supported:

e / no-escalators

Transfers must be possible without taking an escalator.

E / no-elevators

Transfers must be possible without using an elevator.

i / info

Does not restrict the requested connections. However, this option causes
efa to display additional accessibility information for each route part
(where available). When -x w or -x l do not return any connections,
using -x i might be more helpful (though it cannot guarantee that any of
the results satisfy the respective type).

l / nf / low-platform

All vehicles must be low-platform ("Niederflur").

s / no-stairs

Transfers must be possible without stairs (e.g. via escalators/elevators or
ramps).

DEPENDENCIES

BUGS AND LIMITATIONS

The EFA backend is not able to calculate "two-way" routes, i.e. from -> via ->
to routes with from == to. If from and to are the same stop, it doesn't even
try to calculate a route ("we recommend walking instead"), if they are close to
each other it may or may not work. Workaround: Request from -> via using the
normal four-argument efa invocation, read the time, use efa -t time via via to
to to request via -> to.