On Feb 3, 7:18 pm, Jason <[email protected]> wrote: > How does one parallelise requests to reverse geocode lat/longs via > GClientGeocoder? I believe 5 queries per second are allowed per browser IP > address when reverse geocoding (or geocoding). How can we send 5 concurrent > requests from the browser? We have an application that displays 50-100 > lat/longs on the browser (the lat/longs are shown in a table); and the user > has to choice to reverse geocode some or all the lat/longs. Each reverse > geocode request via GClientGeocoder takes between 1-2 seconds; so if each of > the lat/longs is reverse geocoded in a sequential manner; it could take > about 100 seconds for the entire request to complete -- not exactly a > pleasant experience for the user. > > Any tricks/suggestions/workarounds??
Don't do that. That is the reason there is a quota on the free service. You should either re-think your application to avoid such intense use of the geocoding service (you should really only need to geocode user input; known points you can store in your database), create your own or find a paid service. -- Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
