search icon
TravelTime API
Developer Tools
Database Plugins
TravelTime API
TravelTime API
Isochrone API
Distance Map API
TravelTime API
Travel Time Matrix API
Travel Time Matrix API
Protocol Buffers
TravelTime API
Routes API
Geocoding API
Additional API Reference
Error Handling
TravelTime API
ArcGIS plugin
QGIS plugin
Alteryx plugin

QGIS Route Manualanchor icon

Algorithmsanchor icon

QGIS-route-simple Route (Simplified)anchor icon

This algorithm provides a simpified access to the route endpoint.


It can be used to get the best routes between two sets of points.

Parameters descriptionanchor icon


Searches: Choose a point layer from which represents input coordinates.

Search type: Whether the coordinates represent the departure or the arrival points.

Transportation type: Which transportation types to consider.

Departure/Arrival time: The departure or arrival time. Searches are time dependent, as depending on the date/time, public transport or traffic condition may be different.

Time zone: Define the time zone of the departure/arrival time.

Locations: The points layer to search from.

Load fares information: Load informations about fares in the resulting attributes.

Output style:

  • BY_ROUTE : return one linestring per route
  • BY_DURATION : return one linestring per route, broken down by travel time
  • BY_TYPE : return one linestring per route segment (allows to map mulimodal routes)

Output layer: Where to save the output layer. If you leave this empty, the result will be loaded as a temporary layer. It is still possible to save a temporary layer afterwards by right-clicking it in the legend and choosing “make permanent”.

QGIS-route-advanced Route (Advanced)anchor icon

The parameters match closely the API. They are best documented on the API documentation.

All parameters are expressions, which allow you to freely use the QGIS expression engine to define each of those parameters, which includes access to all features attributes.

Differences with the APIanchor icon

In the API, all coordinates are to be provided in the locations parameter, and then searches specify locations ids. As this doesn’t suit well GIS workflows, the algorithm separates source for searches and for location.