[pmwiki-users] GoogleMap question

Ben Wilson dausha at gmail.com
Wed Jun 21 18:12:17 CDT 2006


On 6/21/06, Chris Cox <ccox at airmail.net> wrote:

[snip prior]

> >> I use something like this... (using the includeSite recipe)
> >> You can use just the address in the q= or you can do a hybrid
> >> after you have the ll codes... like

[snip include site example]

> > Except, that may be construed as a site scrape by Google. I'm not sure
> > if they have a policy about that, but other major web companies have
> > policies against. They prefer you link. Google provided the API as a
> > way of providing the functionality without having to include its site.
>
> Actually, they can't prevent it... in fact, it's less intrusive
> than their API google-wise.  Granted, Google can change their
> GET parameters.  Trust me... Google has OTHER reasons for why
> they want you to use their API... remember, they are an information
> gathering source.  Has nothing to do with anything "nice",
> I can assure you.
>
> > The advantage of the Google Map API is that you can set multiple
> > points and can provide message bubbles and a short form to generate
> > directions to a location.
>
> The disadvantage is you have to register (by Google policy) and
> it's not nearly as simple an interface.  Just my opinion.  The
> above is easily added as a PmWiki Intermap as well.

"For individual users, Google Maps, including local search results,
maps, and photographic imagery, is made available for your personal,
non-commercial use only. For business users, Google Maps is made
available for your internal use only and may not be commercially
redistributed, except that map data may be accessed and displayed by
using the Google Maps API pursuant to the API terms and conditions."
[1]

Translation: business sites must use the API. Therefore, the
IncludeSite recipe and PmWiki's Intermap capability are both a
violation of Google's terms of service when used by a business.

"By using Google Maps and any data or information accessed from Google
Maps, you agree to be bound by our Google Terms of Service as well as
these additional terms and conditions." [1] The Google Terms of
Service state: "You may not take the results from a Google search and
reformat and display them, or mirror the Google home page or results
pages on your Web site."[2]

Accessing the Google map via GET and redisplaying on your web site is
the same as mirroring search content, as you are using the address as
a query string to search Google's database for satellite imagery.
Therefore, by using the Intermap attribute or IncludeSite recipe is a
violation of Google's TOS, even when doing so as a personal user. As a
consequence, the only way to legally display Google map content on a
web site is to use the Google Map API.

> Actually, they can't prevent it... in fact, it's less intrusive
> than their API google-wise.

Based on my argument above, Google can enforce its rights via
injunction under the Terms of Service and the Map Terms of Service.
While it may be less intrusive, to interface Google's map service in
contravention of its Terms is a violation of its rights and it may
enforce.

> The disadvantage is you have to register (by Google policy) and
> it's not nearly as simple an interface.

Google owns the database, it owns the images, and it owns the
interface. Therefore, it is entitled to name its terms for access. "He
who pays the piper names the tune." The registration process is
simple: give them the URL to your site, and agree to comply with its
terms.[3] Google does not even require a site POC. Therefore, the
disadvantage you offer is a trivial consideration for what Google
provides in return--which is a legal right to display its content on a
web site.

[1]: http://maps.google.com/help/terms_maps.html
[2]: http://www.google.com/terms_of_service.html
[3]: http://www.google.com/apis/maps/signup.html

-- 
Ben Wilson
"Democracy: two wolves and a sheep voting on what's for dinner."




More information about the pmwiki-users mailing list