What about licencing? Google has a certain licence to what data it can display on maps.google.com, and a different one to what data is exposed in the APIs for third party use. (in many cases its the same data esp now much data has moved to TeleAtlas, but definitly not all)
So using maps.google.com directly you could be accessing data you not licenced to use. On 20/04/2009, joediddley <[email protected]> wrote: > > Well, if people think that is the case, i'll just use the geocoder api > and static maps api w/ my map key. There is no use case here that is > inherently meant to be outside of any terms of service of what Google > normally provides. I simply saw it as a faster way in fewer server > calls and less JS library loading to obtain the same information and I > don't think there is anything inherently wrong with that. The project > i'm working on produces the same result either way. > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
