none
Inaccurate Result from Reverse Geocode RRS feed

  • Question

  • Hi,

    This rest query returns an address of 336 NW16th St which is incorrect.

    http://dev.virtualearth.net/REST/v1/Locations/26.4812836,-80.0767683?includeEntityTypes=address&o=xml&key=XXXX

    When I take the same coordinates and paste them in to Google or Bing Maps the correct location / address of 314 NW 16th St is returned.

    https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=26.4812836%2C-80.0767683

    http://www.bing.com/maps/default.aspx?q=26.4812836+-80.0767683&mkt=en&FORM=HDRSC4#Y3A9MjYuNDgxMjY0fi04MC4wNzcwNjkmbHZsPTE2JnN0eT1yJnE9MjYuNDgxMjgzNiUyMC04MC4wNzY3Njgz

    Is there any way possible to correct my rest query so it returns the correct result?

    Thanks


    Terry McCullagh www.tothecloud.com

    Wednesday, September 24, 2014 3:31 PM

Answers

  • I've tested this and found that the REST services do return 336. The Bong Maps consumer site you pointed to does not show any address. Right clicking on the map at this location returns 336, not 314 like you mentioned. If you look at the response in the Bing Maps REST service you will see that the calculation method used is Interpolation which means that the address number is approximated. As such the confidence value of this result is set as medium.

    The only way to have accurate reverse geocoding is to have parcel data for every address. This data isn't available everywhere. It appears that Google managed to track some down for this area. If you use reverse geocoding all over the US you will find many areas were Bing Maps returns much better results than Google and vice versa. No one service has perfect data.

    I've logged this with our data team so they can improve it in the future.


    http://rbrundritt.wordpress.com

    Thursday, September 25, 2014 8:47 AM