Well, if I also append the postcode to the end of the address then I can retrieve the correct address as the first result: http://maps.google.co.uk/maps/api/geocode/json?address=65%20Gloucester%20Avenue,%20London,%20NW1%208JH&sensor=false
...however the lat/lng does not relate to that address - if I place that lat/lng on a map it appears to be giving me Gloucester Street again!!! For the record, Gloucester St is in a completely different postcode area (SW1V xxx vs. NW1 xxx) so it's not even an approximate match. Service seems utterly broken. On May 11, 11:26 am, anentropic <[email protected]> wrote: > Trying to geocode the following address: > 65 Gloucester Avenue, London > > I do:http://maps.google.co.uk/maps/api/geocode/json?address=65%20Glouceste... > > For some reason it is giving me back results for 65 Gloucester Street > instead. > > Performing the same search on the publichttp://maps.google.co.uk > website brings back the correct result. > > I read that searching by postcode is deliberately inaccurate due to > Royal Mail postcode data licensing restrictions... I thought searching > by address was supposed to be accurate though? > > Is there anyway to avoid the service just returning random results and > make it usable? > > -- > 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 > athttp://groups.google.com/group/google-maps-api?hl=en. -- 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.
