On Sat, Sep 20, 2008 at 12:25 AM, vagabond <[EMAIL PROTECTED]> wrote: > > This is most unfortunate. I have encountered many strange routing > anomalies in the TeleAtlas (API) map data that did not occur in NavTeq > map data previously used in Google Maps. > > Here is an example: > > http://tinyurl.com/rim-drive > > Point A used to route directly to point B along Rim Drive when using > Google Maps. Now it takes the long way, as it does in the API. > Dragging either marker toward the other does not help. > > Yes, it is good that both now use the same map data, but I'm afraid > they went with the wrong one. >
I dont think it was as simple as picking one out of a hat ;) http://blumenthals.com/blog/2008/09/19/google-maps-now-using-teleatlas-data-exclusively/ > On Sep 19, 10:21 am, Blackpool Community Church > <[EMAIL PROTECTED]> wrote: >> That should finally put an end to all those complaints about hiw the >> imagery in the API isn't as good as what you see in maps.google.com. >> They've switched maps.google.com to use the same TeleAtlas imagery as >> the API has been using. No more Navteq in the USA or Canada. >> >> Except for Israel. It still uses GISrael in maps.google.com and >> LeadDog in the API. >> . > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
