Question Answer
Are there any limits regarding the number of vehicles, vehicle types, and the number of jobs for the synchronous and asynchronous request flow? Yes. Restrictions for the synchronous request flow: 250 jobs, 35 vehicle types, 350 vehicles per vehicle type. Restrictions for the asynchronous request flow: 3000 jobs, 150 vehicle types, 350 vehicles per vehicle type.
How does Tour Planning handle traffic information in routing calculations? Traffic information can be considered by HERE Tour Planning in three ways - automatically, by live or historical data, and by historical data only. Search for the traffic parameter in our API reference for more details (configuration.fleet.traffic).
Does HERE Tour Planning API have any restrictions on the geographic distribution of locations included in a problem definition, e.g. a maximum distance between vehicle or job locations? Tour Planning does not have any restrictions on the maximum distance for routing. However, when exceeding a 190 km radius (or 380 km in bounding box diameter), no live traffic will be taken into account by default (see the traffic parameter in our API reference. You can enforce having live traffic always, but then you should make sure that all the locations in the problem you specify are within an enclosing circle with a radius of 190 km or less. If they are not, you will receive a response with a status code 400, an error code E613429 and the following error message: "Region radius is too big to include traffic information". In this case, you can remove some locations (e.g. by removing jobs) from the problem until all locations are within an enclosing circle with a radius not exceeding the radius limit of 190 km mentioned above, and proceed with your problem getting live traffic information.
Does HERE Tour Planning support solving Vehicle Routing Problems (VRP)? Yes, see the Tutorials section for the detailed explanation of how to use the HERE Tour Planning for solving the most common VRPs.
Does HERE Tour Planning API support open VRP? Yes, see Open VRP for details.
Does HERE Tour Planning API support multiple shifts per vehicle? Yes, see Multiple Shifts And Breaks for details.
Can a vehicle shift stretch over several days? Yes, technically there is no limit for the shift length.
Can a 'break' stretch over more than 1 day? No, there is a limit on the duration of breaks of 24 hours.
Is HERE Tour Planning API included in the HERE Limited Plan? Tour Planning API is not included in the Limited Plan, it is included in the Base Plan. See also Plan Features and Licensing & Terms for details.
Why do I get { "error": "Forbidden", "error_description": "These credentials do not authorize access" } response when I try to make a request with the API key or the bearer token that I was able to obtain. You are probably using your Limited Plan account, which does not include access to the Tour Planning API. See Plan Features and Licensing & Terms for details.
Do I need to sign an evaluation agreement in case I want to try out HERE Tour Planning API? Yes.
How can I get evaluation access to HERE Tour Planning API? Please contact your regional HERE representative or directly request access via the platform portal.
How can I get commercial access to HERE Tour Planning API? Please contact your regional HERE representative or directly proceed to the platform portal, create an account, and choose the Base plan.
Where do I find information on how I can request a token or API key for accessing Tour Planning API? Getting Credentials, Authentication Guide
What is the transaction definition? The number of transaction charged for a request is the sum of all locations. Locations include job locations, vehicle type starting and ending locations, breaks including driver rest, charging, or other planned stops. See Tour Planning Billing for more details.
How can I find Tour Planning documentation for previous releases? Via the release picker at the top left on https://developer.here.com/documentation/tour-planning/3.7.0/release_notes/index.html
Why are there the slightly different solutions for some problems when running them several times? The algorithm used by HERE Tour Planning API is non-deterministic.
What are the rate limits for TP? 1 request per second per realm (customer) and it applies to both synchronous and asynchronous endpoints.
How are compute resources for asynchronous problem computations distributed among different users? Each user receives a fair share of the compute resources. In case your resource consumption is extremely high in comparison to other users, some of your problem computations might have to wait until a couple of your problems finish computing. This behavior merely makes sure that one or a couple of power users cannot consume all compute resources for a certain amount of time. In practice you should not notice this. Only if you have submitted an extremely large number of problems for asynchronous computation concurrently, you might see that a small number of those problem calculations remain in pending state for longer than usual. Please contact your local HERE representative, in order to discuss solutions in case you think this might be an issue.
How many pickup or delivery tasks can be added to one job? Maximum 3 pickups and 3 delivery tasks are allowed in one multi-job. If more pickup or delivery tasks are required to be added, the problem should be formulated differently. If the pickups are from a single location and there are several deliveries, the pickup location should be handled at the client side as the vehicle shift start and individual deliveries should be added as separate jobs. It makes the problem less complex and can produce more efficient tours.

Synchronous and Asynchronous Endpoints Comparison

Synchronous Asynchronous
max 250 jobs max 3000 jobs
max 35 vehicle types max 150 vehicle types
max 350 vehicles per vehicle type max 350 vehicles per vehicle type
maxTime: max - 240 sec, default - 240 sec maxTime: max - 3600 sec, default - 3600 sec
stagnationTime: max - 240, default - 10 stagnationTime: max - 3600, default - 600

results matching ""

    No results matching ""