Asked by:
Wron calculation distancematrix

Question
-
Hello,
I do with json a call to the distancematrix.
But I get the wrong KM's back. Can someone help me?
Distance between 51.11251,3.98416 and 51.08221,4.00768 is not 21 KM. This is 7KM
Send:
{ "origins": [{ "latitude": "51.11251", "longitude": "3.98416" }], "destinations": [ { "latitude": "51.16002", "longitude": "4.81098" }, { "latitude": "51.08221", "longitude": "4.00768" } ], "travelMode": "driving" }
Response:
<?xml version="1.0"?> -<BingLocation> <authenticationResultCode>ValidCredentials</authenticationResultCode> <brandLogoUri>http://dev.virtualearth.net/Branding/logo_powered_by.png</brandLogoUri> <copyright>Copyright © 2019 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.</copyright> -<resourceSets> <estimatedTotal>1</estimatedTotal> -<resources> <__type>DistanceMatrix:http://schemas.microsoft.com/search/local/ws/rest/v1</__type> -<destinations> <latitude>51.16002</latitude> <longitude>4.81098</longitude> </destinations> -<destinations> <latitude>51.08221</latitude> <longitude>4.00768</longitude> </destinations> <errorMessage>Request accepted.</errorMessage> -<origins> <latitude>51.11251</latitude> <longitude>3.98416</longitude> </origins> -<results> <destinationIndex>0</destinationIndex> <originIndex>0</originIndex> <totalWalkDuration>0</totalWalkDuration> <travelDistance>66.375</travelDistance> <travelDuration>44.408</travelDuration> </results> -<results> <destinationIndex>1</destinationIndex> <originIndex>0</originIndex> <totalWalkDuration>0</totalWalkDuration> <travelDistance>21.225</travelDistance> <travelDuration>26.243</travelDuration> </results> </resources> </resourceSets> <statusCode>200</statusCode> <statusDescription>OK</statusDescription> <traceId>79d0dc8c92ea4be69c0f6561eb61efb9|DU00000D5D|7.7.0.0</traceId> </BingLocation>
All replies
-
-
-
-
You are very welcome! I can confirm they have received my notice of your issue and have passed it to the Engineering team. Again, I can't offer any time expectation but they do have your sample for review.
Hello,
Is there still no solution for this problem?
-
Hi Wimpel2,
The team has not resolved the issue to me so I have no update for you at this time. Note that they work on an AGILE schedule so your issue will likely be reviewed at their next sprint.
UPDATE: The Team has found the source of the issue. They will be looking into a fix on their next sprint.
Sincerely,
IoTGirl
- Edited by IoTGirlMicrosoft employee, Moderator Monday, July 8, 2019 6:42 PM
-
Hi Wimpel2,
The team has not resolved the issue to me so I have no update for you at this time. Note that they work on an AGILE schedule so your issue will likely be reviewed at their next sprint.
UPDATE: The Team has found the source of the issue. They will be looking into a fix on their next sprint.
Sincerely,
IoTGirl
Hi,
Any news?
-
-
-
Can we at least be told the nature of this issue? If they have found the source of this issue then surely they can at least describe it.
P.S. I'm not that big on Agile personally, but I don't think there's anything in there saying "only talk to customers once every few weeks."
-
Hi Zloth,
If you are an Enterprise Customer, please create a support ticket with the Bing Maps Enterprise Support Team. The forums are largely for assistance and do not offer the 1-1 connection a Support case does.
NOTE: I would expect the fix soon and my assumption is that an underlying data issue was at fault but I was not given that detail. Distance Matrix leverages a number of other APIs underneath so unwinding these can be time consuming. Also, understanding the error doesn't always mean that the fix is obvious so giving a time estimation is problematic and I would not want to give a guess and then miss that date.
UPDATE: The team has found more than one issue based on this sample. They are still working on a full fix.
Sincerely,
IoTGirl
- Edited by IoTGirlMicrosoft employee, Moderator Thursday, October 17, 2019 6:53 AM