This tool calculates the fastest route, with turn-by-turn directions, from every departure location to every arrival location, using the /routes endpoint.
| Description | |
|---|---|
| Departure Locations | The point layer routes start from |
| Departure Locations ID | The field identifying each departure location in the output |
| Travel Mode | Any of the 13 transport modes the Custom tools offer |
| Departing / Arriving | Whether routes leave the Departure Locations at the chosen time, or reach the Arrival Locations by it |
| Time Zone | The time zone the departure or arrival time is in |
| Departing / Arriving Time | The departure or arrival time |
| Arrival Locations | The point layer routes end at |
| Arrival Locations ID | The field identifying each arrival location in the output |
| Output Style | How the routes are drawn and tabled (see below). Defaults to By journey. |
| Properties | travel_time (seconds) and distance (metres) are always included. fares adds public transport fares as JSON text (UK only). |
| Fields To Keep [Departure Locations] / [Arrival Locations] | Fields from either layer to copy onto the output |
| Output Layer | Where to save the output - must be in the project geodatabase |
The optional Transportation options, Search range and Snapping are described on Common parameters. With a search range and Range Results above 1, each alternative route is a row of its own, numbered by an alternative field (0 = fastest).
By journey- one line per route, each coloured separatelyBy travel time- one line per route, coloured by bands of total journey timeBy transport type- one line per leg of each route, coloured by the transport used, with turn-by-turn directions in the attribute table
A line layer. Each row has location_id (the departure location), search_id (the arrival location), travel_time and distance. With By transport type, each row is one leg and also has its mode and directions.