On Dec 1, 4:20 pm, Marky1124 <[email protected]> wrote: > > I've seen mention that geocoding in the UK isn't accurate because the > Royal Mail owns the data and licenses it, however it seems to me that > there is inconsistency in geocoding results given by the HTTP geocoder > based on whether the postcode is specified with or without a space. > E.g. "CA6 5TR" and "CA65TR". There also appears to be inconsistency > between the result location shown in maps.google.co.uk and the > geocoder's specified location.
Can you see if this is related to Issue 1179? http://code.google.com/p/gmaps-api-issues/issues/detail?id=1179 > Should all postcodes be presented to the geocoder with a space or not? Ideally, it shouldn't matter; but since the correct format is with a space, using a space should be accurate and accuracy is undefined without a space. > Shouldn't geocoder results match the maps.google.co.uk location? No, or not necessarily. The geocoders are different. Although maps.google.* and Local Search used to be accurate, recently they have been returning results which are distressingly similar to the API. Presumably the licensing has changed again. > If an inaccurate result is identified should it be reported, and if so > how? Since we know that UK postcodes are inherently inaccurate because of postcode licensing, there's probably not much to be done. BUT the district centroids are available, so CA6 should be accurately geocodable as its centroid, which is what used to happen with the API. If you know of centroids which are inaccurately geocoded, raise an issue (or add them to an existing issue). Andrew -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
