On Dec 1, 4:49 pm, Andrew Leach <[email protected]> wrote:
> Can you see if this is related to Issue 1179? > http://code.google.com/p/gmaps-api-issues/issues/detail?id=1179 Thank you Andrew. I think you are correct, issue 1179 is the same problem. I can see now that the API geocode of "CA6 5TR" matches maps.google.co.uk's position for "CA6 6" and "CA65TR" matches "CA6 5". So that's the off by one issue, and the other thing I highlighted is probably caused by the use of output=embed. So am I correct in thinking that due to license restrictions Google's geocoding results are less accurate for third parties using the API? In conclusion for me I think the inconsistencies are caused by the 'off by 1' bug, which is further obsfucated by the different handling depending on whether a space is included in the request or not, and the inaccuracies are caused by reduced accuracy due to stripping off the last two characterse of the postcode for API based requests. Issue 1179 was filed about 9 months ago. It would be nice to see it fixed. I would hope that once it's fixed then the handling of the postcode with or without the space would become consistent as well, or does that merit a separate bug request? I agree that the postcode should be presented with the space, but if the resulting location differs then it becomes an issue to decide which to use. Cheers, Mark -- 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.
