Maps API, data storage, how without breaking the conditions?

Question

In the Google APIs and Yahoo Maps, I read the following terms of service:

YOU SHOULD NOT: "store or allow end users to save map images, map data or geocoded location information from the Yahoo! Maps API for any future use;

My problem and the scope of my project is to create a real estate site. A user who places an advertisement for the sale of his home will be able to write a home address or point it directly to the map. Then I would save the latitude / longitude data in the mysql database, so I can get it later when a new user searches for a house for sale.

Is this the right procedure? How does this compare with the above conditions? I mean, how can I use a geocoding system if I can't store simple latitude / longitude?

Answer 1

Google has no such restriction that you are talking about. The Google Geocoding API website actually offers to cache or store content to reduce the number of hits to its servers and improve performance.

As for addresses, your users enter them , so you can store addresses. These latitudes / longitudes can be obtained from the Google Maps API service using these addresses.

Caching results is good, so you will need to really look for them during your first search.

Answer 2

As far as I can tell, you should not store geocoded data from Google in a database. I have the same problem on the Drupal website. A module in which I use latitude and longitude data in a database. If you look at the terms of service indicated on the jmort253 page indicated in his answer, you will find the following:

(from https://developers.google.com/maps/terms#section_10_1_3 )

10.1.3 Restrictions on the export or copying of data.

(a) No unauthorized copying, modification, creation of a derivative Work or display of contents. You must not copy, translate, modify or create derivative works (including creating or contributing to the database) or publicly display any Content or any part of it, except as expressly permitted by these Terms. For example, the following are prohibited: (i) the creation of the server side modification of the cartographic tile; (ii) stitching multiple static map images together to display a map that is larger than that allowed in the Maps API Documentation; (iii) the creation of mailing lists or telemarketing lists based on Content; or (iv) exporting, writing, or storing Content on a third-party platform or service based on location.

(b) No prefetching, caching, or storage of content. You should not prefetch, cache, or save any Content, except that you can store: (i) a limited amount of Content in order to improve the performance of the implementation of the API Maps if you do it temporarily, safely and in a way that does not allow the use of Content outside the Service; and (ii) any identifier or content key that the Maps API Documentation specifically allows you to store. For example, you should not use Content to create an independent database of "places" or other information about local listings.

(c) There are no bulk downloads or bulk content channels. You should not use the Service in such a way as to provide you or any other person with access to bulk downloads or bulk channels of any Content, including, but not limited to, numerical latitude or longitude coordinates, images, visible map data or location data (including company listings) . For example, you are not permitted to offer a batch geocoding service that uses the content contained in the Maps API (s).

Parts b and c really make it sound like you and I are trying to do it, no no. Am I reading this wrong?

Answer 3

Geocoding refers to changing the address from Lat / Long coordinates. You can indicate that the person entering the address, provide it, and save lat / long coords in the database for future use (returned from Google or the Yahoo Maps API).

Or you could just violate these seemingly absurd terms and store irrelevant data anyway :)