Doesn't this violate the terms of use? Geocoding and saving that in a fixed list/database?
I do agree that geocoding items from a fixed list more than once IS a waste of google's resources. Especially if you are going to use the geocoded result to put a marker on a google map. What do people do to get around it? If I have 150,000 possible addresses, it does not make sense to try to geocode them in real time. It would seem to be better to do it once up front and then use the geocode results as you need them. It would allow me to do server side things like calculate which of those addresses would even BE on the map that I'm creating. On Mar 24, 2:46 pm, Rossko <[email protected]> wrote: > > Hi there. I have looked around and decided that it isn't feasible to > > try andgeocodemultiple addresses... > > Go back a step first. Most often multiple geocoding is just a bad > idea, usually because the list-of-things togeocodeis a selection > from a fixed list (or database). The thing to do isgeocodeeach > 'thing' as it gets added to the list, which also allows sensible > corrective action to be taken on unknown or incorrect locations. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
