QGIS Troubleshooting Guide
This is not actually related to the TravelTime plugin, but instead is part of QGIS itself. The first time you are asked for this, you can simply enter a password to set it.
More details can be found here.
You can expose your API Key by clicking on the eye icon:
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
Blank rows in an input file, or data that is corrupted (e.g with null geometry) will return an error.
If you see this error:
Open the Attribute Table of the input layer you are using, and check for Null rows:
An input file may contain blank rows if it has been generated using a Geocoder and not all the addresses were successfully geocoded.
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.
Our standard licences have a cap on the number of hits that you can send per minute. If while a tool is running, you hit your limit, the tool will fail.
To ensure that you don't hit your limits, you can set a throttle on the number of API calls that are made per minute by opening up the plugin Settings:
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 you receive an error like below:
Open up the Attribute Table of the input layer, and check for any duplicate values amongst the field being used as the ID. For example, in the layer below, we couldn't use the City field as the ID because it is contains duplicate values:
For example, on 1st June 2022, we would typically support any searches within a window from 18th May 2022 - 13th July 2022.
Running a public transport search with an arrival/departure date outside of this window will return an error like below:
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 like below: