Routing changes? Cannot route to a off-road lat-lng

5 posts / 0 new
Last post
jpero
Routing changes? Cannot route to a off-road lat-lng

Did something change recently with the Directions API (routing) service?

We are noticing that we are now unable to route to points that are "off-the-grid".

We have several locations that are "off-road", where we need to know a rough travel distance and drivetime.

 

For comparison, Bing Maps is able to resolve a route to the specified lat/long:  http://binged.it/1Oml0q2

Assuming the classic MapQuest site is using the same routing provider:    http://mapq.st/1XEoxr1

 

 

 


MQBrianCoakley
The dirt path beyond Sellwood
The dirt path beyond Sellwood, ON is not in the MapQuest data and the lat/lng destination is not routable since there is no connected road network nearby.

jpero
Ok, is there a way we can use

Ok, is there a way we can use the Route matrix to determine which points (lat/lng) are not routable?


MQBrianCoakley
You may be able to reverse
You may be able to reverse geocode the lat/lng and if there is no road quality code returned then it's probably not routable. Otherwise, the only way is to try the route whether it's a full route or a single route matrix.

tarouma
I am having a similar problem

I am having a similar problem here. I would love a way to determine which address is the problem. It took me several hours to figure out since I first looked at every lat/lng and everything seemed fine. I had already run into the 602 problem sending lat/lng earlier, so if I get that the first time then I try the route using reversegeocoding. But in the problem with the link above, there is no apparent reason why it is unable to route.