On 19 juin, 16:16, Andrew Leach <[email protected]> wrote:
> 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
Hi Andrew,
Thanks for your quick answer. The problem is, I have a lot of
addresses that are entered by >20 people for >20 countries.
They are really a lot of them. This is the only one reported to be
wrong at the moment. I just checked the few in Switzerland, and these
seems to be correct.
I don't think it's a good idea to ask the users to enter their
resellers coordinates (Lat/Lng) as they will surely not understand the
process.
Or maybe do you know a way to do it ?
They can just edit a list of names/addresses from the admin panel.
I could add Lat/Lng fields without any problem.
But it will be a lot of work (>700 addresses at the moment).
Thanks.
Philippe / xtz
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
