Ok, although I was happy to accept the "there's a difference between google's geocoder and the API encoder" explanation, it just kept nagging at me. And when something nags at me, i just can't let it go. So, i went exploring. I found that on just about every example of the google map API in action at code.google.com, the gclientgeocoder was being used. Practically none of the examples use an HTTP request. This of course is because most of the examples utilize javascript. Well, my site uses PHP to submit the data to a mySQL database, so i can't use gclientgeocoder. I use HTTP request to maps.google.com/maps/geo with an encoded URL containing the address.
What I found was that when i searched my fabled Fayette Mall address in one of the API examples at the google code site, the marker ended up on the PRECISE location of the actual building. Now, according to the FAQ, there should be a difference between maps.google.com and the google map API in geocoding an address. But it seems to ME that the difference in accuracy that I am experiencing is between geocoding with gclientgeocoder and an HTTP request to maps.google.com/maps/geo. Now, the question is, should I be forced to deal with an inaccurate map simply because i use an HTTP request instead of gclientgeocoder? On Sep 7, 8:52 pm, "maps.huge.info [Maps API Guru]" <[EMAIL PROTECTED]> wrote: > On Sep 7, 7:47 pm, Rossko <[EMAIL PROTECTED]> wrote: > > > > > This may not be a comfort to people looking for the potty :) > > > cheers, Ross K > > Good point... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
