> 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... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
