I'm working on adding a map to a website that collect's the website members' addresses in a DB, geocodes them to lat/lng, then displays a map with markers at each members' location.
Ideally I would like to make an API call when the member is saved in the DB to generate the lat/lng data once, instead on a per-request basis (or even a per-thousand request basis assuming caching or whatever.) This isn't allowed by the TOS, though, so what is the best practice in this case? Am I correct that the geocoding API must be called from the page via JS? I'm looking at having to geocode ~300 addresses at a time if this is done when rendering the page, as opposed to doing this 300 times *once* if it was just a callback when each member is saved. I understand wanting to limit the load on the web service, but it seems that (at least in this case) the load is made to be more burdensome than if I could call the api from the app and write them to the DB once. Let me know what I'm missing, as I'm sure there is a better way to do this. This is my first stab at the Google Maps API and have probably missed some details that I should've read in the docs. Stu -- 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.
