Skip to main content

ArcGIS troubleshooting guide

Tips for solving some common issues with the TravelTime add-in for ArcGIS Pro.

This guide covers the most common problems with the TravelTime add-in for ArcGIS Pro and how to fix them. If you’re still stuck, contact us through the chat on this page.

Setup

The tools won’t run, or the toolbox is greyed out. ArcGIS Pro needs your permission to run the toolbox code. Right-click the TravelTime toolbox in the Catalog pane, click Refresh Python Toolbox Access Permission, then click Yes. See Why does ArcGIS Pro ask permission to run the TravelTime toolbox?

The tools fail straight away on a locked-down computer. Each run writes temporary files to the add-in’s own folder (the iGeolise folder next to TravelTime.pyt). If that folder is read-only, the tools fail. Ask your IT team for write access to it.

None of the tools work. Your organisation may be blocking calls to the TravelTime API. Ask your IT team to allow both of these:

  • https://api.traveltimeapp.com, used by every tool

  • https://data.traveltimeapp.com, used by Data from H3 Cells, Data from Locations and Quick Data

If you connect through a proxy, the add-in uses your computer’s proxy settings, including proxies that need a user name and password.

Your data

Rows are being skipped. Features without a geometry, and rows with a blank ID, are skipped with a warning in the tool messages. Blank rows often come from a geocoding run where some addresses didn’t match. The Location Analytics tools and Isochrone with INTERSECTION aggregation stop instead, before sending any requests, so remove those rows first.

Some locations fail. Locations need to be on land that can be reached. Points in water or in very remote areas fail, which often happens when postcode or ZIP code polygons are turned into centroids. With Robust Mode on (the default), failed locations are skipped and listed in a warning, and the rest of the results are written. See What do Robust Mode and the Hits Per Minute limit do?

Duplicate IDs. Every tool with an ID field needs each ID to be unique. A duplicate stops the run with an error that names the duplicated value.

Where can my input layers be? Anywhere ArcGIS Pro can read: file, shared, enterprise or read-only geodatabases, shapefiles, or layers in another project. The tools only read your inputs and never change them. A few things to know:

  • Any coordinate system works. The tools convert to WGS84 as they read the data.

  • If you’ve selected features in a layer, only the selected features are used.

  • Location inputs must be point layers. The H3 cells input for Data from H3 Cells must be a polygon layer.

  • Geocoding can also read CSV and Excel files directly.

Tool settings

Arrival and departure dates (Custom tools). For public transport, use a date within 2 weeks either side of today. Dates outside that window can return a 422 error or patchy public transport results. Core tools don’t take a date, so this doesn’t apply to them.

Parameter values. Apart from Search Range Width, no transport parameter can be longer than the travel time. For example, a 30-minute walking time with a 15-minute travel time returns an error.

Environment settings. Only set the Parameters tab in the Geoprocessing pane. The tools handle coordinate systems themselves, and changing settings in the Environments tab can cause errors.

Saving outputs

Where outputs can go. Save outputs to a file geodatabase that you can write to. It doesn’t have to be the project’s default geodatabase.

  • Avoid saving to a shapefile or a folder, because field names are cut to 10 characters.

  • The Data tools add styled layers that only load from a file geodatabase.

  • Enterprise geodatabases haven’t been tested.

Output names. Names can’t contain spaces or special characters (underscores are fine) and can’t start with a number or an underscore. Two outputs from the same tool also can’t share a name, even if one is a table and the other a layer.

Licence limits

Errors part-way through a large run (429 errors). Most plans have a hits-per-minute limit. Turn on Hits Per Minute in Settings and enter your plan’s limit, and the tools will pause before they go over. See What do Robust Mode and the Hits Per Minute limit do?

A run stopped early. Results fetched before the run stopped are kept. Re-running the tool starts again from the beginning.

Did this answer your question?