From a4f855c7f7d6fba7b6c249ecb174cb79acd55fad Mon Sep 17 00:00:00 2001 From: Daniel Friesel Date: Sun, 12 Jan 2014 15:41:33 +0100 Subject: Improve unparsable route data error message, and two-way trips to limitations --- bin/efa | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'bin') diff --git a/bin/efa b/bin/efa index 2eb8624..287ef18 100755 --- a/bin/efa +++ b/bin/efa @@ -65,7 +65,7 @@ sub handle_efa_exception { exit 2; } if ( $e->isa('Travel::Routing::DE::VRR::Exception::NoData') ) { - printf STDERR ( 'Error: %s', $e->description ); + printf STDERR ( "Error: %s\n", $e->description ); exit 3; } if ( $e->isa('Travel::Routing::DE::VRR::Exception::Ambiguous') ) { @@ -432,6 +432,13 @@ This script requires perl 5.10 (or higher) with the following modules: =head1 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. + None known. =head1 AUTHOR -- cgit v1.2.3