This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 4%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAF%3C/text%3E%3C/svg%3E)
I can route in one direction, but the reverse fails. This is consistent across Bing web site and REST services.
{X = -111.958817 Y = 33.48164} to {X = -111.766396 Y = 33.44712}
One direction works perfectly and I get a completed route, the other direction says there's no possible route, which makes no sense. Please advise.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 11%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Document? Not sure what you mean.
Just go to maps.bing.com, search for 33.48164, -111.958817 and then request directions FROM 33.44712, -111.766396. Works fine. Then swap the locations and try to get directions. Fails with "We can't find directions for this journey. Check your waypoints and route options and try again." Which is clearly not the right outcome. This happens in web site and REST services, so there's likely a data issue or routing logic issue behind the scenes. REST Locations API says these are routable points (which they are at least in one direction).
Hi Andy,
Sorry I did not see this sooner but the issue you are seeing is that not all points are "Routable". What the website does behind the scene is to "Move" your Lat/Lon to a routable address. You will see this conversion happen right in the UI. When you call the API, it does not do this for you as it assumes you really want a route to that point and it is telling you that there really isn't one available. Basically a very different use case.
If you do want the bing experience then you would find the location first, choose the routable lat/lon and then call the route API with the already validated routable coordinate.
Sincerely,
IoTGirl
I did find the offending location first, it's a country club, I have the address, it translates to a working geocode, but the geocode won't route FROM it. The routing with that point only appears to work in one direction (TO it; trying to route FROM the same country club fails).
And per ramr-msft, I opened a ticket. still waiting to hear back from that all these months later.
If I follow the steps I gave you, I am unable to reproduce the issue. Both directions work when address is given rather than the unroutable co-ordinate.
Correct, but I'm starting from the geocode, which I got from Bing for 5668 E. Orange Blossom Ln.
Phoenix 85018...
Or at least the geocode I got back in April, data changes over time and where it's showing it on the map now is not what it was showing back in April (in April, the address resolved to the main building off Orange Blossom, not a weird hop from Valencia). Back in April, the geocode request came back with two X/Ys, one that it said was "routable", one that was not. I used the routable one, but it wouldn't route in both directions.
@Andy F Thanks for the details. we would recommend to raise a Azure support desk ticket from Help+Support blade from Azure portal for your resource. This will help you to share the details securely and work with an engineer who can provide more insights about the issue that if it can be replicated.