On 17 February 2011 16:18, Drix <[email protected]> wrote: > But in both cases we will still be storing a latitude and longitude... > Is storing the lat/lng plus the address the problem? Meaning that we > could make the link between both?
No: you can store anything you like as long as it doesn't come from Google. So, you can store an address the user has given you; and you can store some coordinates the user has given you. If you want to link those two data items, that's up to you. You can geocode the user's address, thus getting some data from Google; but then you can't store that data, because that's Google's. You can geocode the user's address and display that location on a Google Map, because if you use the geocoder then the Terms of Service require you to show the location on a map. In your use-case, the user experience is actually improved by following the rules. They give you an address (so you can be sure it's accurate); you geocode it and display a map (so you comply with the rules); then they give you some coordinates (so you can be sure they are accurate too). You get accurate data, the user controls what you are given, and you comply with the Terms. Everyone wins. -- 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.
