Using Googlemaps and saving data

I create an Events site in which the address of this event will be saved for use in the map on the page. When viewing a page of individual events, I would like to provide a list of similar events on the page side. I would also like to rank this list by distance and display a small map with a marker on it for each item in the list.

I thought about geocoding the address of the events when I entered the content, and then saved this data in the site database. This will allow me to calculate the distance from the event on the server, and then provide an ordered list for display.

My question is: Will this violate the Googlemaps Terms of Service?

These terms:

"A geocoder for any purpose other than obtaining locations that will be displayed using the Google Maps API is a violation of the Terms of Service. You can use an HTTP geocoder to geocode addresses outside of your Google Maps API application so that they can be cached and later displayed using one of the Google Maps APIs, but locations obtained using the geocoding web service cannot be used by any other application, distributed in other ways, or resold. "

Suggest that data storage was not a problem, but I'm not sure that the process of sorting the list with a long lats will not lead to a violation.

Any advice is appreciated.

+4
source share
1 answer

As long as the map you refer to in your question is Google Map, and you use geocoded data to display features on a Google map, you're fine. The client side google.maps.Geocoder dev-guide is designed for dynamic queries based on real-time interaction with the user, which leads to the need to perform geocoding on the fly. But Google recommends that you consider using the Geocoding Web Service dev-guide on the server side if you want static addresses or coordinates before the geocode before using response values ​​on the Google map. The preservation of these values ​​is supposed.

Usually, to complete these steps, as well as the ordering by distance that you describe, they usually do some form of processing after the response / post-store to fit any case used to fill your map with relevant data. I understand that you want to be careful to stay in TOS, but what you describe sounds pretty standard.

0
source

All Articles