Thanks Rossko, you bring up an interesting point: To me, "caching" means a temporary storage (e.g. for performance) that does not live beyond the session, which is different from some persistent storage, like a database, for example, where the value is associated with other data. But maybe my understanding is wrong.
In my case, the purpose of the data would be to allow users to put up property for sale, which a prospective buyer can then locate again on a Google map. The co-ordinates that the user plots would be stored along with the property listing. (Sounds like it contravenes 10.2(b) of the ToS, but that seems to address usage of Google's Content, not one's own). The service will of course be free (though perhaps ad-sponsored, which I think is still in line with the ToS) and public. I am not sure what you mean though by "time-limited" (don't see mention of this in the ToS), though of course listings would expire, and users have complete control over their data and can delete it at any time. That said, the workarounds described in this thread (such as forcing the user to place a marker) seem to just bypass these restrictions anyway. (I mean, having the user move the marker after geocoding could be construed to result in a "derivative" work anyway - perhaps). -- 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/-/komLAehAsfwJ. 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.
