Thanks for the additional info. When a user adds a shop, the Geocoder results are stored on your backend. Will these stored locations ever be displayed again on the map? If so, this is okay since it only temporarily stores them on your server under the assumption they'll be displayed again at some point in the future on a map. Overall, I don't see any problems with your use-case.
Hope this helps, Dann On Thu, Apr 15, 2010 at 12:02 PM, babbos <[email protected]> wrote: > Hello Dann, > > Thank you for the reply! > > I understand the use of pre-fetch and cache. For that case i have made > the client application, request and process geocoding results directly > with the client so i have nothing todo with what / how user uses the > service... In that i am not intervening. > > The kind of application i am developing allows users to keep bookmarks > of favorite places. > > They search for a specific shop by address, using geocoding services, > or by using a draggable marker to pin point the exact location, in > that case the client also performs a reverse geocode query. > > When the user chooses to add this shop, he /she has to complete a form > and submit the data. > > The data submitted to my server have the complete json of the geocoder > result object. From this data object i choose to store some basic > information like address, street number, town, country etc... > > ... > So, am i allowed to do that? > > Should i request from the user to input the address data by hand so as > to avoid storing geocoding results? > > An advice on the matter would be greatly appreciated > > > > On Apr 15, 3:08 am, Daniel Lee <[email protected]> wrote: > > An example of storing *limited* amounts of Content temporarily is to > > pre-fetch and cache Geocoding results to avoid having to geocode > addresses > > at runtime. If this is your use-case, it's perfectly fine to do so as > long > > as the geocoded locations are displayed using the Google Maps API. > > > > More on this in the second paragraph here: > http://code.google.com/apis/maps/documentation/geocoding/#Geocoding > > > > Note: the geocoding service may only be used in conjunction with a Google > > map; geocoding results without displaying them on a map is prohibited. > For > > complete details on allowed usage, consult the Maps API Terms of Service > > License Restrictions: > http://code.google.com/apis/maps/terms.html#section_10_12 > > > > It may be more helpful to know specifically what your prospective > use-case > > and evaluate whether it abides by our ToC. > > > > Thanks, > > > > Dann > > > > > > > > > > > > On Fri, Apr 9, 2010 at 7:34 PM, babbos <[email protected]> wrote: > > > Hello, > > > i am not sure if this is the correct group to post these questions but > > > i am developing a project using the google's Maps API... so here > > > goes... > > > > > In the project, users query via google's geocode API and get results > > > on the map. > > > > > The user then may choose to save one of the results for later use... > > > > > According to the terms of the google Maps API service found in: > > >http://code.google.com/apis/maps/terms.html, Article 10 is about > > > restrictions. Users of the API may NOT [quote]: > > > "<i>10.3 pre-fetch, cache, or store any Content, except that you may > > > store limited amounts of Content for the purpose of improving the > > > performance of your Maps API Implementation if you do so temporarily, > > > securely, and in a manner that does not permit use of the Content > > > outside of the Service;</I>" > > > > > Where Content is defined as: > > > "<i>7.1 Definitions. (b) "Content" means any content provided through > > > the Service (whether created by Google or its third party licensors), > > > including map and terrain data, photographic imagery, traffic data, or > > > any other content.</i>" > > > > > If i am reading correctly i am not allowed to store permanently *any* > > > information produced by the Maps API? > > > > > I see hundreds of sites storing information from google's Maps API... > > > > > My apologies if i am totally off topic > > > > > -- > > > 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]<google-maps-js-api-v3%[email protected]><google-maps-js-api-v3%2B > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > > -- > > Daniel Lee > > Developer Programs Engineer > > Google, Inc. > > 345 Spear Street > > San Francisco, CA 94105 > > 650 253 0967 > > -- > 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]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- Daniels Lee Developer Programs Engineer Google, Inc. 345 Spear Street San Francisco, CA 94105 650 253 0967 -- 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.
