Bing Map Distance Matrix - Index order

Miles Taylor (UK) 1

Hello,

We are using the Bing Distance Matrix REST API to retrieve transit times.

Please can you confirm the correct usage of the originIndex and destinationIndex distance matrix cell fields.

Does this index refer to the order of origins/destinations listed in the API request, or in the API response?

We've noticed that the order of origins/destinations is different in the response to those we send when making the request, so it is not clear which list the index refers to.

Thanks

QuantumCache 20,026 Reputation points

2021-05-06T17:17:54.603+00:00

Hello @Miles Taylor (UK) Welcome to Microsoft Q&A Platform and thanks for your query. Community SME's on this topic or our team will review your scenario and circle back at the possible earliest time. Cc: @RickyBrundritt-9609
QuantumCache 20,026 Reputation points

2021-05-07T21:25:07.173+00:00

Hello @Miles Taylor (UK) Just checking in if you have had a chance to see the previous response from the Microsoft Product team.
Please enable your preferred alert types on your Profile's Settings to get instant notifications on this thread's discussions. Here is how to subscribe to a notification.

2 answers

Ashley Song 6 Reputation points

2021-05-07T19:28:52.227+00:00

Hello, thanks for the inquiry.

I tested using the example request from: https://learn.microsoft.com/en-us/bingmaps/rest-services/routes/calculate-a-distance-matrix , and the results look correct.

Please share you request if you still find the index order incorrect.

Here is the request URL:
https://dev.virtualearth.net/REST/v1/Routes/DistanceMatrixAsync?origins=47.6044,-122.3345;47.6731,-122.1185;47.6149,-122.1936&destinations=45.5347,-122.6231;47.4747,-122.2057&travelMode=driving&startTime=2017-06-15T13:00:00-07:00&key={BingMapsAPIKey}
Please sign in to rate this answer.

1 person found this answer helpful.
Ashley Song 6 Reputation points

2021-05-07T19:29:12.277+00:00

And below is the response. "originIndex": 0 referes to 47.6044,-122.3345, and "destinationIndex": 0 refers to 45.5347,-122.6231. "destinationIndex": 1 refers to 47.4747,-122.2057. The index order looks correct.

...
"results": [
{
"originIndex": 0,
"destinationIndex": 0,
"travelDistance": 281.389,
"travelDuration": 177,
"departureTime": "2017-06-15T20:00:00.0000000+00:00"
},
{
"originIndex": 0,
"destinationIndex": 1,
"travelDistance": 23.579,
"travelDuration": 24.6833,
"departureTime": "2017-06-15T20:00:00.0000000+00:00"
},
...

Miles Taylor (UK) 1 Reputation point

2021-05-10T09:01:14.74+00:00

Hello yasong,
Thank you for looking into this. I see that you have tried with driving travelMode, however the issue is occuring with transit travelMode. Pls try this request, which has a single origin and destinations with increasing distance:

https://dev.virtualearth.net/REST/v1/Routes/DistanceMatrix?travelMode=transit&timeUnit=second&key=xxx&origins=
51.525136%2c-0.111183&
destinations=
51.516595%2c-0.129279%3b
51.658838%2c-0.401468%3b
51.750231%2c-1.267367%3b
52.479029%2c-1.903098%3b
53.483282%2c-2.231454%3b
54.96746%2c-1.615383%3b
55.948894%2c-3.19259%3b
57.149606%2c-2.096916

I can't post much of the response on this forum due to the character limitation, but will try to post a snippet to show how the results don't align.

Miles Taylor (UK) 1 Reputation point

2021-05-10T09:06:41.737+00:00

95232-distance-matrix-response.txt

Please see response attached as a file
Also please be aware that I have raised a support ticket for this issue
Sign in to comment
rbrundritt 15,126 Reputation points Microsoft Employee

2021-05-07T16:18:36.327+00:00

Odd, not sure when that order changed in the response vs the input, but looking into this, it looks like the indicies align with the order defined in the response, which makes sense.
Please sign in to rate this answer.
Miles Taylor (UK) 1 Reputation point

2021-05-10T09:09:40.257+00:00

Hello rbrundritt,
Thanks for looking into this. I can't see that they align with the response, please see the attachment I added to yasong's reply below, showing how they mis-align.
Sign in to comment