Wasn't it borzoi who wrote: > >> Best not to geocode at all - or rather, do it once when you load the >> data in your database, and allow checks and correction of failed/ >> inaccurate geocodes. > >From a point of view, I completely agree with you. >From another, geocoded addresses are highly variables: new ones are >added, others removed, others change, at an high rate. >At time, I just have and manage addresses; should I manage geocoded >coordinates also, it can rapidly become a maintainance nightmare. >Still searching a solution...
If you don't mind a modest percentage of your points being incorrectly located, then you can write code to automatically geocode any that don't already have coordinates stored in your database, and write the coordinates back to your database. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
