Hi Steve- We don't yet have documentation on the HTTP geocoding parameters as we're awaiting a few improvements to the geocoding input/output before rehauling the documentation. I suppose we were hoping an industrious developer like you would ask in the group about the parameters. :)
Here's an example query - the difference is using the &ll parameter to send in the lat/lng: http://maps.google.com/maps/geo?output=xml&oe=utf-8&ll=37,-122&key=asdad 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. - pamela On Thu, Oct 23, 2008 at 11:57 AM, Steve King <[EMAIL PROTECTED]> wrote: > > Hi Pamela, > > The blog post doesn't discuss issues about using the XML geocoder > (maps.google.com/maps/geo?) to perform reverse lookups. This still > appears to be country code only? > > Regards, > Steve. > > On Oct 23, 10:44 am, "pamela (Google Employee)" <[EMAIL PROTECTED]> > wrote: >> Hi developers- >> >> I'm super excited to tell you that we now have reverse geocoding in >> the Maps API. >> >> Read this blog post for more >> information:http://googlegeodevelopers.blogspot.com/2008/10/geocoding-in-reverse.... >> >> Note that this resolves our #4 request in the issue >> tracker:http://code.google.com/p/gmaps-api-issues/issues/detail?id=134 >> >> Enjoy, and let me know what you create! >> >> - pamela > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
