none
Bing Maps API return wrong longitude and latitude RRS feed

  • Question

  • When entering this address "2500 Rochelle Rd, Rockwall, TX 75032" on bing maps website and google maps website, I get identical longitude and latitude returns. Which are "Longitude = -96.4016472" and "Lattitude = 32.8806335". But when using he API with the below code I am getting "Longitude = -96.4421310425" and "Lattitude = 32.8109893799". Slightly off.  Does anyone have an idea why it is so?

    My Code :

    <cfhttp url="https://dev.virtualearth.net/REST/v1/Locations?query=#address#&key=#ATTRIBUTES.bingkey#"  method="GET" result="rsJSON"></cfhttp>

    <cfset result = DeserializeJSON(rsJSON.Filecontent)>
    <cfif result.resourceSets[1].resources[1].bbox[1] NEQ "">
    <cfset ret.latitude = result.resourceSets[1].resources[1].point.coordinates[1]>
    <cfset ret.longitude = result.resourceSets[1].resources[1].point.coordinates[2]>
    </cfif>

    Friday, May 5, 2017 6:04 PM

Answers

  • The Bing Maps website is using a new geocoder which has newer data. This is why it is able to correctly find the address you specified. The Bing Maps REST services haven't yet been updated to use this new geocoder (work in progress and expected to be done in a couple of months). Currently the REST services does not find this address and is resolving to the zip code level, thus the different coordinate.

    [Blog] [twitter] [LinkedIn]

    Friday, May 5, 2017 6:56 PM

All replies

  • The Bing Maps website is using a new geocoder which has newer data. This is why it is able to correctly find the address you specified. The Bing Maps REST services haven't yet been updated to use this new geocoder (work in progress and expected to be done in a couple of months). Currently the REST services does not find this address and is resolving to the zip code level, thus the different coordinate.

    [Blog] [twitter] [LinkedIn]

    Friday, May 5, 2017 6:56 PM
  • Any specific time frame for the update? We have clients depended on this. It is important for us to provide this service accurately. 

    How and where do we follow up with the fix?

    Wednesday, June 14, 2017 11:03 PM