Hello,
When using the azure maps route api with compute best order enabled I've found that the lines and routes output are different to the optimized order summaries that come in the same response. This leads to a mismatch between the two and after manually looking at the lines produced they create the logical order expected while the summary doesn't which means the result then can't be used without examining where the lines start and end.
Example using some generated coordinates in the UK:
URL used to generate rest api call -
https://atlas.microsoft.com/route/directions/json?api-version=1.0&query=53.79913,-1.547699:53.773066,-1.568298:53.820922,-1.601944:53.813626,-1.456375:53.73734,-1.493454:53.734497,-1.586151:53.788889,-1.655502:53.882083,-1.51886:53.871559,-1.675415:53.86832,-1.419296:53.764949,-1.358185:53.694267,-1.472168:53.657661,-1.583405:53.730842,-1.728973:53.849286,-1.770172:53.801665,-1.538043&subscription-key=subscription-key&computeBestOrder=True&routeType=fastest

I would have expected the two to align and I've factored in the n-1 due to the start and end being removed, some of the differences are much larger than that for me to think that is the issue, happy to know if I've configured something incorrectly though.
Thanks,
Alex
