Hi Barry, Its a bit hidden - which makes me even more suspicious. You ave to goto the standard api terms page: http://code.google.com/apis/maps/terms.html
Then in the top corner use the Google Terms of Service - which takes you to: http://www.google.com/accounts/TOS And its data that you "submit, post or display on or through, the Services" - so that definitely includes anything you add on it - even if its client side points and lines (though it could be harder for google to get it) <<Its not quite as 'far reaching' as that. A point plotted on their map (particully with the OpenSpace API) they may consider derived information, not every point displayed. >> The OS definitely conside any data that is even checked against their maps is derived. The only totally clean way is to use GPS data that is not plotted on and potentially checked against OS data. This will have signifcant implications for many organisations in the UK who are considering using google maps - the vast majority of data in the UK is OS derived in some shape or form. I'm not suggesting the OS stance is reasonable - but it is one thye have held for a long time. But there again I don't think googles terms are very reasonable either for an organisation that generally likes to be considered the "good guys" - I just hope that they can move as swiftly with thsi as they did with Chrome --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
