Routing Inconsistency

Hello, I am a developer, working for a company called Inlog and we are developing a software based on the TomTom solution for routing, we are evaluating the possibility of using the TomTom platform and testing it, we found an inconsistency related to routing considering the option “Best order computer” enabled. We realized that depending on the order of the points sent, we have a different result, even if we have the same points. Could you explain to us what happens? Below is an example:

First complete link sent to TomTom (32 points):

https://api.tomtom.com/routing/1/calculateRoute/-29.716094,-52.40046:-29.720141,-52.404723:-29.723684,-52.41256:-29.720507,-52.422056:-29.724787,-52.411983:-29.72567,-52.415849:-29.72741,-52.422994:-29.729521,-52.421877:-29.731836,-52.421284:-29.735472,-52.419356:-29.740237,-52.415497:-29.745094,-52.411747:-29.749054,-52.409443:-29.752056,-52.407139:-29.754423,-52.401034:-29.748137,-52.401784:-29.746056,-52.401806:-29.74349,-52.401886:-29.744556,-52.395639:-29.745429,-52.39497:-29.743631,-52.405291:-29.741737,-52.410482:-29.7437,-52.414507:-29.749617,-52.414337:-29.752297,-52.41425:-29.75475,-52.418:-29.761163,-52.41775:-29.761069,-52.415591:-29.760464,-52.411766:-29.763028,-52.411361:-29.764861,-52.411306:-29.7498266,-52.4273579/json?instructionsType=text&language=pt-BR&vehicleHeading=90&report=effectiveSettings&avoid=unpavedRoads&vehicleMaxSpeed=120&vehicleCommercial=true&vehicleEngineType=combustion&arriveAt=2021-03-29T06%3A00%3A00-03%3A00&computeBestOrder=true&routeType=fastest&travelMode=truck&traffic=true&key=“KeyHere”

In this first link, we have the dot (“lat”: -29.7205 “log”: -52.42203) returning as the 6th dot.

Second link sent to TomTom (32 points):

https://api.tomtom.com/routing/1/calculateRoute/-29.716094,-52.40046:-29.720141,-52.404723:-29.723684,-52.41256:-29.720507,-52.422056:-29.724787,-52.411983:-29.72567,-52.415849:-29.72741,-52.422994:-29.729521,-52.421877:-29.731836,-52.421284:-29.735472,-52.419356:-29.740237,-52.415497:-29.741737,-52.410482:-29.743631,-52.405291:-29.74349,-52.401886:-29.744556,-52.395639:-29.745429,-52.39497:-29.746056,-52.401806:-29.748137,-52.401784:-29.754423,-52.401034:-29.752056,-52.407139:-29.749054,-52.409443:-29.745094,-52.411747:-29.7437,-52.414507:-29.749617,-52.414337:-29.752297,-52.41425:-29.760464,-52.411766:-29.763028,-52.411361:-29.761069,-52.415591:-29.761163,-52.41775:-29.75475,-52.418:-29.764861,-52.411306:-29.7498266,-52.4273579/json?instructionsType=text&language=pt-BR&vehicleHeading=90&report=effectiveSettings&avoid=unpavedRoads&vehicleMaxSpeed=120&vehicleCommercial=true&vehicleEngineType=combustion&arriveAt=2021-03-29T06%3A00%3A00-03%3A00&computeBestOrder=true&routeType=fastest&travelMode=truck&traffic=true&key=“KeyHere”

In this second link, we have the dot (“lat”: -29.7205 “log”: -52.42203), returning as the 4th dot.

Notice that the starting and ending points are always the same, and all the others too, we only have a slight difference in the position of the intermediate points, the parameters are also the same.

Could TomTom help us with this situation?

For now this param is not working perfectly.
It is up to you if this works for your case or not.

Hi, thank you for answer me,you have any estimation when this functionality will be working?

Unfortunately I can’t promise any dates.