On Jan 21, 10:37 am, Andy Pearson <[email protected]> wrote: > The page in question is showing an incorrect map: > http://www.welovecamden.co.uk/go/4752-kieser-training-ltd/
I don't get any map at all on that page (using Firefox). In fact it's completely blank. > In order to try and improve results I pass in 3 address formats and > use the first one that returns a valid point, in this case the 3 > addresses are: > > 1. Greater London House, Hampstead Road, Camden, London, NW1 7DF, UK > 2. Hampstead Road, Camden, London, NW1 7DF, UK > 3. NW1 7DF, UK You shouldn't be using the geocoder for addresses *you* know about. You should geocode them yourself and pass the location to the client browser. There's no point in getting every visitor to your site geocode the same locations. > This is where the discrepancy between my maps and maps.google.co.uk is > really confusing. I am guessing the maps site is using a newer version > of the API (or some private API). http://code.google.com/apis/maps/faq.html#geocoder_differences There's also an issue with UK postcodes. NW1 7DF will be geocoded as "NW1 7" and the centroid of that sector probably won't be in the same place as the centroid of NW1 7DF. Although since Greater London House is a former cigarette factory and has a large number of postcodes, that may well suffice. I guess that the geocoder will work best with a street number, if that's possible for such a large number. "180 Hampstead Road, London NW1" should work fine. But you shouldn't be geocoding known addresses, and you could run into problems if you attempt to geocode more than one at once. 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 -~----------~----~----~----~------~----~------~--~---
