On Jun 19, 3:02 pm, xtz <[email protected]> wrote: > When I search for this address "122-124 West St, Fareham, United > Kingdom" in Google Maps ( url > :http://maps.google.com/?q=122-124%20West%20St,%20Fareham,%20United%20... > ), its fine. > > But, in the Google Maps API it shows West Street, Portchester insead > of West Street, Fareham. (url > :http://www.elna.com/en-uk/dealers_map.php?dealer=673 > ) > > I tried to add the Postalcode, State, another spelling for West Street > (West St). Nothing seems to make it point to the right position.
This is a really good example of how not to use the geocoder -- and why you shouldn't use it this way. You *know* where the address you're asking for is. What you should be doing is getting the coordinates of that location out of your database as well as the address. Then you wouldn't need to use the geocoder: you just set the map to the location you know. Far faster and more efficient; and more accurate. However, I can get "122 West Street, po16 0, UK" to work. Or at least, it's in the right town. So that might suffice until the geocoder gets it wrong -- there have been instances of data updates making things worse rather than better. 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 -~----------~----~----~----~------~----~------~--~---
