I'm referring to the Lat Long Blog here http://google-latlong.blogspot.com/2009/06/how-to-find-out-whats-here.html
where the author notes that the 'What's here' functionality in Google Maps is based on "reverse geocoding" and "has been available in the Google Maps API for a couple of months now, so you can also put it to use if you're a developer." Sounds like a good promise to approve. So I made a comparison of this official API example http://code.google.com/apis/maps/documentation/examples/geocoding-reverse.html with the 'What's here' functionality in Google Maps, i.e. here http://maps.google.com/maps?q=40.75897,-74.005501&sll=40.757522,-74.000006&sspn=0.00154,0.002811&ie=UTF8&ll=40.759448,-74.003649&spn=0.00616,0.011244&z=16 The result was that in nearly every case the returned points are different. The API example seems to return the closest available address whereas the 'Whats here' request seems to return the nearest point of interest. (I certainly mean the red marker, not the green arrow). My questions are: Does anyone know if my guess is right? And if so: Does anyone know if - and how - something like the 'Whats here' functionality is also available in the API ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
