Azure Maps failing with NO_ROUTE_FOUND

Question

Azure Maps failing with NO_ROUTE_FOUND

Landon Sulick 20

Hello, I am trying to get the distance between two coordinates and Azure Maps is failing and returning a NO_ROUTE_FOUND error. Here is API request that I am using that is failing:
https://atlas.microsoft.com/route/directions/json?subscription-key=<redacted>&api-version=1.0&query=37.3901399,-121.9443419:37.3606615,-121.8470229&routeType=fastest&traffic=false

Would you be able to update the database the Azure Maps uses to get these addresses working? Both locations seem to be legitimate buildings.

thank you!

Landon

VSawhney 320 Reputation points Microsoft External Staff

2025-04-15T09:37:49.1233333+00:00

Hello Landon Sulick,

The most common reasons for these types of errors are:

A route point that is more than 150 meters from a road segment.

One way streets sometimes can create issues

I recommend moving these points to the nearest road for the meantime so you can get the route. Ref thread: azure-maps-api-no-routes-found-sometimes-work-in-o

Hope this helps. In case of further queries please feel free to reach us.

Thank you!
Landon Sulick 20 Reputation points

2025-04-15T15:00:19.2333333+00:00

VSawhney, thank you for getting back to me so quickly. I checked and it looks like both coordinates are well within 150 meters. I attached two screenshots of the locations that shows they are within 150 meters. I can't move these points to the nearest road because we are getting these coordinates from an API. Would you be able to submit a ticket to Microsoft to fix the incorrect map data?

thank you again for your help on this issue,
Landon
Landon Sulick 20 Reputation points

2025-04-15T15:04:40.61+00:00

I could only put one attachment in per post. Here's a screenshot of the other location.
VSawhney 320 Reputation points Microsoft External Staff

2025-04-16T06:21:08.77+00:00

Hello Landon Sulick,

I hope you had the chance to review the answer provided by rbrundritt and found it effective in addressing your concern.

Thank you!
VSawhney 320 Reputation points Microsoft External Staff

2025-04-17T06:52:51.72+00:00

Hello Bayu Damar Jati,

Following up to see if had an opportunity to review the response provided by rbrundritt and found it useful in resolving your concern.

Thank you!

Accepted answer

0 additional answers

Your answer

VSawhney 320 Reputation points Microsoft External Staff

2025-04-15T09:37:49.1233333+00:00

Hello Landon Sulick,

The most common reasons for these types of errors are:

A route point that is more than 150 meters from a road segment.

One way streets sometimes can create issues

I recommend moving these points to the nearest road for the meantime so you can get the route. Ref thread: azure-maps-api-no-routes-found-sometimes-work-in-o

Hope this helps. In case of further queries please feel free to reach us.

Thank you!
Landon Sulick 20 Reputation points

2025-04-15T15:00:19.2333333+00:00

VSawhney, thank you for getting back to me so quickly. I checked and it looks like both coordinates are well within 150 meters. I attached two screenshots of the locations that shows they are within 150 meters. I can't move these points to the nearest road because we are getting these coordinates from an API. Would you be able to submit a ticket to Microsoft to fix the incorrect map data?

thank you again for your help on this issue,
Landon
Landon Sulick 20 Reputation points

2025-04-15T15:04:40.61+00:00

I could only put one attachment in per post. Here's a screenshot of the other location.
VSawhney 320 Reputation points Microsoft External Staff

2025-04-16T06:21:08.77+00:00

Hello Landon Sulick,

I hope you had the chance to review the answer provided by rbrundritt and found it effective in addressing your concern.

Thank you!
VSawhney 320 Reputation points Microsoft External Staff

2025-04-17T06:52:51.72+00:00

Hello Bayu Damar Jati,

Following up to see if had an opportunity to review the response provided by rbrundritt and found it useful in resolving your concern.

Thank you!

Answer 1

rbrundritt 20,201 Microsoft Employee

Looks like you are using the old v1 routing service. Try the newer service: https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-2025-01-01

The older service used TomTom data and services directly behind the scenes, and there where the odd location where a route couldn't be calculated.

The newer service uses the same data and backend as Bing Maps (bing.com/maps) which has a lot more data and improved logic.

Note that the API interface and response format of the new version is very different from the v1 service. Also, the new service only accepts post requests. The main reason for this is that there are a lot more options available and it is not possible to use half the options before a GET URL would be too long and cause issues in some system.

IoTGirl 3,616 Reputation points Microsoft Employee

2025-04-17T15:02:40.8966667+00:00

Also, if you are using the Azure Maps V2 Geocoder Search, also powered by Bing Maps, there are two co-ordinates given one for viewing and the other for routing. Sometimes folks will use the viewing one and that can cause this issue even with the V2 routing. For example, if you are routing to a hospital, warehouse of shopping mall, the co-ordinate you would show visually on a map is very far from the street. The screen shots show geocoordinates in the middle of buildings so my assumption is you are using the visual co-ordinates, not the routing ones.
Landon Sulick 20 Reputation points

2025-04-17T15:08:53.43+00:00

Thank you for the response rbrundritt. Unfortunately I'm working on a legacy app and it looks like we will not have the time to switch to this newer service. If it worked similarly to the old one we could make the switch, but it does look quite different.
Landon Sulick 20 Reputation points

2025-04-17T15:10:17.7833333+00:00

And thank you IoTGirl. I wouldn't have thought of this.

Share via

Azure Maps failing with NO_ROUTE_FOUND

0 additional answers

Your answer