incorrect shapedata

1 post / 0 new
incorrect shapedata

When we make a request for an optimized route the resulted shapedata seems to be the shapedata of a normal route request without the locations being reordered.

To work around this we would have to make a request for an optimized route, look at the locationSequence, reorder our input and make second request just to get the route info.

Using the Route Shape GET request with the session id of the first request still results in the incorrect shapedata.

Is this intentional behaviour?