Here is some information regarding your questions. Reverse geocoding is fine, but storing the information in the manner you describe would be against the TOS. You are limited to 2,500 requests per day for your site, so if you are planning on being within that limit then you should be fine.
Use of the Google Geocoding API is subject to a query limit of 2,500 geolocation requests per day. (User of Google Maps API Premier may perform up to 100,000 requests per day.) This limit is enforced to prevent abuse and/or repurposing of the Geocoding API, and this limit may be changed in the future without notice. Additionally, we enforce a request rate limit to prevent abuse of the service. If you exceed the 24-hour limit or otherwise abuse the service, the Geocoding API may stop working for you temporarily. If you continue to exceed this limit, your access to the Geocoding API may be blocked. Note: the Geocoding API 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> . Also take note of these: 10.1 access or use the Service or any Content through any technology or means other than those provided in the Service, or through other explicitly authorized means Google may designate; 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; On Wed, Feb 16, 2011 at 10:25 AM, Drix <[email protected]> wrote: > We are planning to develop a website displaying locally based information > and using geolocation to identify user's geographical position. In order to > do so, we would like to use the Google Maps API. We are currently > investigating to double-check if our concept fits with the Google Maps API > Terms of Service. After reading those terms we still have a few > interrogations, which we would like to ask you directly, in order to get the > confirmation that our application matches those terms. Could you please > confirm that the following points are complying with the Google Maps API > Terms of Service? > > - We want to use a Google Map as an easy way for users to give us > addresses by pointing a location on the map. That means that we would like > to use on our website the addresses retrieved by reverse geocoding from > Google Maps and display them on pages as plain text without the Google Maps > included. > - We would like to cache the coordinates of those addresses in our > database in order to display them faster on our maps as suggested in the > FAQ. We would also like to use those coordinates to retrieve the user > timezone or to display the distance between two different points through > the > website possibly on pages having no Google Maps included. Any display of > the > positions themselves will be done with Google Maps API on several maps on > the website. > > Could you please confirm that those developments would meet the Google Maps > API Terms of Service standards? > > -- > 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.
