On Wed, Jun 29, 2011 at 3:15 AM, Eric Dooley <[email protected]> wrote:
> Mike. This is good news, thanks for the reply. Not to question your > authority, but how do you know this to be true? Is it buried in Google's TOS > somewhere because I couldn't find anything that explicitly says this. I'm > definitely inclined to agree with you, but I just wanted the peace of mind > before I go any further on my project. > I don't have any authority! :-) I'm just a long-time Maps API developer with a good practical understanding of the TOS. Any other maps developer will give you the same answer, though. There must be thousands upon thousands of sites that do exactly what you're talking about - saving locations that are generated by user input. It's not a problem at all. > Also, do you (or anyone else) know if I could use Google's geocoder just as > a lookup, but not to store its results. For example, a user types his > address and clicks "Check it on the map". If it's the one they want, they > simply submit (and I store) the address they originally typed. They only > used the geocoder as a verification method to *their* data, not Google's. > Sure, why not? You're using the geocoding as part of a Maps API application. You're not storing the geocoded data. Nothing wrong with that either. (But don't take my word for any of this...) -Mike -- 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.
