You would need to look up the ToS/licenses of the third party geocoder as they may not allow that data to be used or displayed on other Maps.
-- Luke On Wed, Jun 29, 2011 at 8:15 PM, 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. > > 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. > > Thanks in advance. > > -- > 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/-/lbsTkAwEqDsJ. > > 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. > -- 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.
