Thanks Andrew. So it sounds like you just need a technical loophole to prevent you actually using the data from a geocoded result, and then you are covered.
I have thought of the following approaches: 1) Add or subtract 1.0E-10 from the long or lat so that it is not technically the result from the geocode. 2) The ToS tell me that *I* cannot store the content, so in a court of law, I could always argue that I am merely offering a public service. I myself am not storing the content; the user is using my service to store the content.* * Because, when you think about it, what stops the user from storing the lats and longs from a GMaps geocode on someone else public service in the form of a document? If the person offering the document service has also agreed to the GMaps ToS, then they are incriminated by storing the results of a geocode (even though the user provided it). The implications become totally ridiculous. Cheers, Martin -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/UM74GU72IncJ. 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-js-api-v3?hl=en.
