How we assess route data
Routavio joins transport options from different data sources into a single route.
Our aim is to be as clear as we can about where the prices, times and connections in a result come from, how recent they are, and what kind of figure they are.
Price information
The prices shown on Routavio are there for comparison. Flight prices in particular can be estimates, because cached data and third-party price signals may be used to produce them.
Wherever possible, the result says whether a price is live, cached or estimated. The final fare and availability are always confirmed by the provider.
Route feasibility
When a route is built, transfer times, transport points and the practicality of each connection are checked. The aim is to filter out, as far as possible, the connections that look possible on paper but cannot be made in practice.
How current the data is
Cached data is held to fixed time limits. When a source cannot be reached, the goal is that old information is never presented as if it were current.
Where it is available, a result shows when the data was last checked and whether it is live, cached or estimated.
Data sources
We draw on several different transport data sources when building a route.
A large part of the rail and public transport connections is built from timetable and stop data published in GTFS format by operators or open data sources.
On the flight side, some prices come from live data and others from cached third-party price signals. That is why flight prices in particular can be estimates, and they are no guarantee of the fare you will find at the moment of booking.
The final fare, the status of a departure and availability are always confirmed by the provider.
Handing over to third-party providers
Routavio does not handle bookings or payments. If you want to go ahead with an option, you are sent to the site of the independent third-party provider behind it.
Narrow but right beats broad but wrong.