> I want Google to answer this
> question clearly.
They do, they publish their terms and conditions.
https://developers.google.com/maps/terms
Those of us that need help to fully understand these will need to hire
our own lawyer.
Those terms have been updated since this thread was last active, so
Hi, I am interested in this topic, too.
So what is the conclusion?
Is it OK to store geocoded data using Google Maps in persistent layer such
as a regular database like Oracle, Datastore in GAE, etc?
I am planning to develop a web application that lists all the registered
properties close to your
> > In the FAQs received by this person from Google, it says: "Bulk geocoding
> > and caching is allowed, with the understanding that the geocodes are for
> > use with a Google Map at some time."
Yes, see terms 10.1.3(b), that's why I said the purpose was relevant.
> > In my case, the points will
Without you having to read all the above, what I found in another thread
was someone telling how Google had sent them some FAQs indicating that it
would be OK to use the geocoding results if it was going to be used on
Google Maps again (which is what I intend to do), but this is not specified
i
Thanks Davie and Rossko for your replies.
Rossko makes a good point: The fact that you are using Google's tools for
determining the data could mean that they own the data even though a user
placed the marker on the map.
Whether they own that or not, the question then is whether and how they
al
> If the user then moves the marker to a new position the coordinates
> is not Google generated data.Otherwise Google has the copyright to all
> lat lng coordinates in the world???
But there is an argument that any coordinate taken from a Google map
is 'derived data'. If you went out and surveyed
Hi
The geocoder only places a marker on the map to the coordinates
supplied by Google
If the user then moves the marker to a new position the coordinates
is not Google generated data.Otherwise Google has the copyright to all
lat lng coordinates in the world???
As long as you dont store any data dir
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 u
> 1) Add or subtract 1.0E-10 from the long or lat so that it is not
> technically the result from the geocode.
But it is still directly derived from Google data, "derived work", not
good enough? (no lawyer)
You could display the geocode with offset to the user, so forcing/
encouraging them to dra
Thanks Andrew. So it sounds like you just need a technical loophole to
prevent you actually using the data from a geocoded result, and then you
are covered.
I have thought of the following approaches:
1) Add or subtract 1.0E-10 from the long or lat so that it is not
technically the result from
On 28 October 2011 12:05, mydoghasworms wrote:
>
> The thing is that if you geocode the location to begin with and it is
> correct, there is no incentive for the user to move the marker after that.
There is an incentive if it's the marker's moveend event which enables
the OK button to send the da
Thanks very much for the reply Davie. Seems like this is a bit of a
minefield.
So let's say that I also give the user the option to find a place with
autocomplete, then place the marker based on the location chosen by the
user from the autocomplete (without the user subsequently moving the
mar
Hi
It is generally conceded that the procedure below is within TOS
1.Geocode and place marker
2.Get user to to move marker to exact location
3 Save the new location + all the other data provided by user you
require to database
Step 2 ensures that the lat/lng data is not the data Google provides
Re
13 matches
Mail list logo
