@Marcelo The idea with using the Client to geocode and retrieve the results for later use via Ajax is pretty appealing to me. I will try to implement it, if the other options fail.
On 22 Jun., 16:53, Marcelo <[email protected]> wrote: > On Jun 22, 4:39 pm, "johan.uhIe" <[email protected]> wrote: > > > I want to avoid client-side geocoding for the reason of speed. I have > > about 100 markers on the map and it would take a lot of time for the > > map to finally load on the client side. Also this can't be in the > > interested of Google, since it would increase the API load by very > > high times. > > You mentioned 1000 per day. > My suggestion was to let a client geocode them **once** and then save > by AJAX to your database. That's the same load on Google (once per > address), but distributed from several different IP addresses (from > your visitors). > > > It is no option to geocode "at home", because I have to constantly > > geocode every 3 minutes. I could run the geocoding on another server, > > but that's pretty stupid because it increases complexity without any > > gain. > > The gain is that you don't hit the quota limit because others are also > doing the same from the same IP. > > > My workarounds are: > > - use another geocoding engine, like yahoo > > Doesn't Yahoo have a quota too? > > -- > Marcelo -http://maps.forum.nu > -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
