Below are some of the common issues that can arise when using the ArcGIS add-in, and how to solve them.
Data Issues
1. Blank or corrupted data
Blank rows in an input file, or data that is corrupted (e.g with null geometry) will return an error.
An input file may contain blank rows if it has been generated using a Geocoder and not all the addresses were successfully geocoded.
2. Unreachable areas
All lat-long coordinates being used for any of the tools must be in a physically reachable area. Locations on water (e.g a river) or in very remote locations will return an error.
This may happen when the input layer has been created by converting polygon areas into points, e.g when using the centroid of zip codes / postcodes.
3. Read/Write access (Time Map Advanced only)
When using the Time Map Advanced tool, you must have Read/Write access to the input layer. This may not be the case if trying to pull the input layer from a shared database - if this is the case, simply save the layer into the project database and try again.
Licence Restrictions
1. Hitting the 'Hits per Minute' limit
Our standard licences have a cap on the number of hits that can be used per minute, depending on the licence tier. If while a tool is running, you hit your hits per minute limit, the tool will fail.
Not sure what a hit is? 1 hit is either:
1 Isochrone
1 Route
1 Time Filter request of a maximum size of 1 x 2,000 (for more details on how best to configure the Time Filter tools to stay within this limit, see here)
To ensure that you don't hit your limits, you can break up layers of points into smaller layers and run each layer separately. Alternatively, the Model Builder in Pro can be used to automate this process.
Tool Configuration
1. Non-unique IDs
When running any of the Advanced Tools, where the ID fields are configurable, the field selected as the ID must be unique amongst all points. If this ID is not unique, an error will be returned.
2. Arrival/departure date
We typically support public transport data for two weeks back from today's date, and six weeks forwards.
For example, on 1st June 2022, we would typically support any searches within a window from 18th May 2022 - 13th July 2022.
Running a tool with an arrival/departure date outside of this window will return an error.
3. Advanced parameter values
None of the Advanced Parameters (except for Search Range Width) can be greater than the Travel time field value. For example, a Walking Time of 30 minutes and a Travel time of 15 minutes will return an error.
4. Geodatabase saving
The Output layer for any of the Simple or Advanced tools must be saved into the project Geodatabase.
5. File naming
Files saved into the Geodatabase have to follow the Esri naming convention:
1. No spaces or special characters (except for underscores _)
2. Name cannot start with a number of an underscore
If the file name you are trying to save an Output layer as does not follow these rules, an error will be returned.
6. Environment configuration
When running any of the Simple or Advanced tools, only the Parameters tab in the Geoprocessing pane should be configured
Changing values in the Environments tab can cause errors - for example, if the Output Coordinate System is changed.
Other
1. API whitelisting
All of the TravelTime tools in ArcGIS Pro involve making an API call to the TravelTime API. If you are unable to get any of the tools to work, it may be that your company does not allow API calls to be made unless the API has been whitelisted first.
If you do use whitelisting, the URL that needs adding is - https://api.traveltimeapp.com