Ok, so you're saying that even though it's an example of the google maps API, that since the geocode request is coming from a google site, it's hitting one particular database, and then when i put the exact same code on MY site, it would be hitting a completely different database? That seems to be pretty misleading on google's part. Sort of like, "hey, see how accurate our maps API can be?" and then you put it on your own site and it's a quarter mile off what it was when you previewed it on google's site. Or like going to a used car lot and buying a car with an engine that sounded really smooth on the lot, only to get it home and having it sputter and die because the mechanic at the lot had filled the crankcase with grease.
If they are going to show examples of the maps API in action, then it should be shown FULLY in action, in my opinion. I mean, how are my users going to find safe haven potties when they are in dire need?? :P On Sep 9, 10:47 pm, "maps.huge.info [Maps API Guru]" <[EMAIL PROTECTED]> wrote: > The difference you're seeing is due to the source of the site being a > Google domain. Non-google domains use the TeleAtlas database, Google > domains use the Navteq database. The http and Javascript forms of the > API use the exact same database. > > -John Coryat > > http://maps.huge.info > > http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
