Yep, as Rossko pointed out. If you straight up use the lat/lng that was provided from the geocoded data would be directly storing the information...
On Wed, Feb 16, 2011 at 12:27 PM, Rossko <[email protected]> wrote: > > For my second point, that means that we couldn't use the latitude and > > longitude to retrieve the user's timezone? ... > > And what about displaying > > the distance from the current user with displayed location? > > That would arguably be storing and using Google's data for some other > purpose than improving map display i.e. against the terms. > > The get-round would be the same ; not to store Google's data, but > instead store what the user provides via some suggest-and-drag > interface. There's nothing to stop the 'suggest' interface from > placing an arrow or marker some random distance away from the > suggested geocoded location to (a) encourage the user to fix it > properly (b) demonstrate you are not storing Google's data as-is. > > -- > 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. > > -- 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.
