Optimizing Route Crazy results

Hi there, we are thinking of using the TomTom RoutingAPI to find the most efficient route (Waypoints) by using the optimize route function (shortest route); however the following call gives a crazy route order:

https://api.tomtom.com/routing/1/calculateRoute/55.9610506%2C-2.9721695%3A55.9347597%2C-3.4815276%3A55.9583259%2C-3.1966415%3A55.9342655%2C-3.2305409%3A55.9609179%2C-3.1666718%3A55.9040104%2C-3.5295329%3A55.9918137%2C-3.7370107%3A56.0091955%2C-3.7307116%3A55.9610506%2C-2.9721695/xml?computeBestOrder=true&routeRepresentation=none&routeType=shortest&key=*****

Is this a bug, should we use Google Maps instead :stuck_out_tongue:?

regards,

Scott.

Hi,

Unfortunatelly waypoints optimization doesn’t work as we could expect.
There are plans to replace that with better implementation.