Isochrone API issue

Question

Hi,

We are using the Isochrone to determine the drive time zone. We utilized the code available at the following link: https://samples.bingmapsportal.com/?search=drive

 We are encountering issues while retrieving the drive zone for certain addresses.

 For example, when we used the URL below, it provided the correct drive time zone. 

https://dev.virtualearth.net/REST/v1/Routes/Isochrones?&optimize=time&travelMode=driving&waypoint=51.561170,-3.035900&timeUnit=minute&maxTime=10&key={Bing map key}

 For the address below (it's just 0.2 miles different from the above address), it provides an incorrect drive time zone, and the difference is significant.

 https://dev.virtualearth.net/REST/v1/Routes/Isochrones?&optimize=time&travelMode=driving&waypoint=51.56163,-3.03896&timeUnit=minute&maxTime=10&key={Bing map key}

 Has anyone faced such an issue and found a solution for it.

Thanks

Answer 1

Taking a look at the location in question, I see a lot of one-way streets. When I test with larger drive times it still has lots off issues and doesn't get much bigger. I suspect there is something in the metadata preventing a route from being calculated out of that area. I recommend reporting this to the Bing Maps support team.