Here's a demo that uses the reverse geocoder to create a find-that-location game: http://gmaps-samples.googlecode.com/svn/trunk/geocoder/reversegame.html
It randomly reverse geocodes points within the viewport and has the user guess the location by clicking on the map. Now, what are you all making? :) - pamela On Thu, Oct 23, 2008 at 6:13 PM, pamela (Google Employee) <[EMAIL PROTECTED]> wrote: > Hi Steffen- > > The limits for reverse geocoding are exactly the same as for forward > geocoding - we consider them just different uses of the same geocoding > service. See the FAQ for more info on limits: > http://code.google.com/apis/maps/faq.html#geocoder_limit > > - pamela > > > On Thu, Oct 23, 2008 at 6:00 PM, siebert <[EMAIL PROTECTED]> wrote: >> >> On 23 Okt., 06:14, "pamela (Google Employee)" <[EMAIL PROTECTED]> >> wrote: >>> Note that GClientGeocoder should be used for any user-entered reverse >>> geocodes, due to the way our IP limit system works. The HTTP service >>> should be used for tasks like reverse geocoding points in a database. >> >> Hi Pamela, >> >> does this mean that no limits exist for the reverse geocoding request >> HTTP service? >> >> I'd like to use it to create location information tags for photos with >> GPS coordinates using a Python script. It would be sad if the script >> fails when processing too many photos at once due to limits of your >> service. So please clarify what the exact limits are for both means of >> access. >> >> Ciao, >> Steffen >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
