search

nakijun / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Provide analysis of the Bing and Google Terms of Service #208

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
MassGIS has become aware of the need to harmonize our use of Bing basemaps and 
Bing Geocoding with the Bing Terms of Service and any changes that have 
occurred in the Terms of Service since OLIVER was originally launched.  This 
enhancement will provide technical answers to some relevant questions 
surrounding MassGIS’s use of the Bing basemaps and Geocoding services.

This enhancement is to provide a non-legal analysis of the relationship of Bing 
usage and Google usage to the current OLIVER implementation.  MassGIS is not 
soliciting an answer to the question “are we compliant with the Terms of 
Service.”  Rather, MassGIS is looking for technical guidance based on the 
technical elements included in the respective Terms of Service for Google and 
Bing.

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 22 Apr 2013 at 1:05

GoogleCodeExporter commented 9 years ago 
This corresponds to Task Order 5 enhancement 6

Original comment by Aleda.Fr...@state.ma.us on 22 Apr 2013 at 1:06

GoogleCodeExporter commented 9 years ago

Original comment by Aleda.Fr...@state.ma.us on 22 Apr 2013 at 1:09

GoogleCodeExporter commented 9 years ago 
Google
  * Since MORIS is a no-fee, no-password site, this frees us from many restrictions.  The way OpenLayers interacts w/ the Google API is in compliance w/ their TOS.
  * Printing.  It looks like this could be an option as long as on the final print page we provide proper attribution and link it back to the Google TOS.  From http://support.google.com/maps/bin/static.py?hl=en&ts=1342531&page=ts.cs see the google_attr.png attachment for details.

Bing
  * It seems that their TOS (TOU they call it) are more flexible than Google's.  Bing allows for direct tile access while Google requires you to go through their API.  To the end user this is transparent since OpenLayers does the heavy lifting.
  * http://www.microsoft.com/maps/product/terms.html Since MORIS is Non-Profit Organization Use, it, too, can be printed.

Original comment by cpl...@gmail.com on 8 May 2013 at 4:22

GoogleCodeExporter commented 9 years ago 
forgot google attachment

Original comment by cpl...@gmail.com on 8 May 2013 at 4:23

Attachments:

GoogleCodeExporter commented 9 years ago 
New Bing account and key

I got them and put them on map_ol_to5 oliver as a test.  Geocoding and tiles 
work and I'll find out tomorrow if the usage report shows my usage (it can take 
24 hours for usage to show up in the report).  I had to get a new Microsoft 
account and Bing key because I was simply not able to log in with the 2010 
Microsoft account and tech support was not helpful.

Original comment by Aleda.Fr...@state.ma.us on 23 May 2013 at 3:28

GoogleCodeExporter commented 9 years ago 
In http://maps.massgis.state.ma.us/map_ol_to5/oliver.php I do see Google and 
Bing attribution clearly on the bottom right of the map for all the types of 
Google and Bing basemaps.  The attribution includes third parties and changes 
by zoom level, as expected.  Terms of use links work.  Nothing is obscured.

One small issue - "Report a map error" showing for the 3 Google basemaps is not 
a link.  We should fix the link or remove it if it not required.

Original comment by Aleda.Fr...@state.ma.us on 23 May 2013 at 3:40

GoogleCodeExporter commented 9 years ago 
I know what you're talking about, and it looks like it was addressed and fixed 
by the OL people, https://github.com/openlayers/openlayers/pull/484.

But since I rolled our own custom OL version to fix the IE tile issue w/o fully 
upgrading to OL 2.13, I would have to incorporate those changes by hand.  
That's tedious and I believe deserves its own issue that we would need to 
address separately.

Original comment by cpl...@gmail.com on 23 May 2013 at 3:51

GoogleCodeExporter commented 9 years ago 
OK, I'll make it a separate issue and we'll just remember to Verify it when it 
gets fixed by the next OpenLayers upgrade.  I don't think it's important enough 
to go through the tedious process right now.

Original comment by Aleda.Fr...@state.ma.us on 23 May 2013 at 3:54

GoogleCodeExporter commented 9 years ago 
Your thoughts in #3 about printing Google and Bing are a nice surprise to come 
out of this TOS review.  However, I don't understand why things have changed?  
We aren't printing now b/c that would require download of tiles right? 

I did read 
http://support.google.com/maps/bin/static.py?hl=en&ts=1342531&page=ts.cs which 
is a handy tool. Although when they say refer to 10.3.1 they mean 10.1.3 in 
this doc: https://developers.google.com/maps/terms?hl=en

If we think printing is an option I would create two more Issues - one for 
Google and one for Bing for possible future work.

Original comment by Aleda.Fr...@state.ma.us on 23 May 2013 at 4:11

GoogleCodeExporter commented 9 years ago 
I don't remember why we prohibited bing / google basemaps for printing.  It 
sounds like if we get the attribution right, it will be the same as including 
one of their maps in a normal publication.

Original comment by cpl...@gmail.com on 23 May 2013 at 4:44

GoogleCodeExporter commented 9 years ago

Original comment by Aleda.Fr...@state.ma.us on 19 Jun 2013 at 8:09