These tools calculate travel times between two layers of points and mark which journeys are possible within the travel time. Travel Time Matrix Core uses the /time-filter/fast endpoint and Travel Time Matrix Custom the /time-filter endpoint; see Core vs Custom.
| Description | Tool | |
|---|---|---|
| Departure Locations | The point layer journeys start from | Both |
| Departure Locations ID | The field identifying each departure location in the output | Both |
| Travel Mode | See Core vs Custom | Both |
| Departing / Arriving | See Departing vs arriving | Both |
| Time Period | The typical time period journeys are calculated for | Core |
| Time Zone | The time zone the departure or arrival time is in | Custom |
| Departing / Arriving Time | The departure or arrival time | Custom |
| Travel time (in minutes) | The maximum journey time (see Core vs Custom). Journeys that take longer are marked unreachable. | Both |
| Arrival Locations | The point layer journeys end at | Both |
| Arrival Locations ID | The field identifying each arrival location in the output | Both |
| Properties | What to return for each reachable pair (see Output) | Both |
| Fields To Keep [Departure Locations] / [Arrival Locations] | Fields from either layer to copy onto the output | Both |
| Output Layer | Where to save the output - must be in the project geodatabase | Both |
The optional Transportation options, Search range (Custom only) and Snapping are described on Common parameters.
A departure search runs from each departure location at the chosen time and filters the Arrival Locations: which can I reach in time?
An arrival search runs to each arrival location by the chosen time and filters the Departure Locations: where can I set off from and still arrive in time?
To make the most efficient use of your licence limits, choose the search type by which layer has fewer points. A departure search sends one one-to-many request per departure location, so use it when the Departure Locations layer is the smaller one. An arrival search sends one many-to-one request per arrival location, so use it when the Arrival Locations layer is the smaller one.
A point layer with one row per departure and arrival location pair (one per alternative when Range Results is above 1), placed at the location being filtered. Each row has Departure_locations_ID, Arrival_locations_id and reachable (1 or 0), plus a field for each selected property:
| Property | Description | Tool |
|---|---|---|
travel_time | Journey time in seconds (always included) | Both |
distance | Journey distance in metres. Core: walking+ferry, cycling+ferry and driving+ferry only. Custom: driving, walking and cycling modes only. | Both |
distance_breakdown | Distance covered by each mode, as JSON text. Driving, walking and cycling modes only. | Custom |
fares | Public transport fares, as JSON text. UK only. | Both |
Unreachable pairs have reachable 0 and a travel_time and distance of 0.