> 1) Add or subtract 1.0E-10 from the long or lat so that it is not > technically the result from the geocode.
But it is still directly derived from Google data, "derived work", not good enough? (no lawyer) You could display the geocode with offset to the user, so forcing/ encouraging them to drag it to the correct place. A better way might be to display a map centred according to geocode but with no marker at all. Make the user click to create a new one. As a general rule, users know where they are better than any geocoder - so you should end up with better data. If the users have any incentive to get it right, of course. > 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.* I think that's sunk too, you are responsible for your service. If I write defamatory remarks on someone elses's piece of paper, I'm responsible. You do need to bear in mind *why* you are storing this content, which you haven't told us. If, say, you were going to use it to analyse your user base for mailshots or whatever - why the heck should Google permit that for free. Whereas if, say, you were storing purely for convenience in displaying another map later, that is just a caching purpose. That's okay provided you also meet the other restrictions - public, time limited etc. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
