Reverse Geo-Coding Inaccuracies

[d...@touchtec.co.uk]

There are various issues with Google's Reverse Geo-coding facilities.

For instance,

Longitude: 52.5456817
latitude: -2.040153

Should be Bagnall Street, Ocker Hill, Tipton, DY4...etc

However it shows:

"address": "48-64 Bagnall St, West Bromwich, Sandwell DY4 0, UK",

Which is obviously wrong.

There are also issues with it coming up as "Wednesfield" instead of
Bilston.

This is a shame, as it means we will have to use Microsoft's
implementation instead, and therefore their mapping facilities (which
are atrocious in comparison) - but at least their reverse geo-coding
is accurate.

http://maps.google.com/maps/geo?q=52.5456817,-2.040153&output=json&oe=utf8&sensor=true_or_false&key=your_api_key

[Mauricio Scheffer]

You could just use Microsoft for reverse geocoding and Google for
mapping... with any IoC container it's easy to select one or another.

> http://maps.google.com/maps/geo?q=52.5456817,-2.040153&output=json&oe...