Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify license and import park data from SanGIS #2

Open
cgiovando opened this issue May 18, 2015 · 6 comments
Open

Verify license and import park data from SanGIS #2

cgiovando opened this issue May 18, 2015 · 6 comments

Comments

@cgiovando
Copy link
Collaborator

Use license of SanGIS' "PARKS_ACTIVE_USE" layer as reported here references SANDAG and Rand McNally copyright:

Note: This product may contain information from the SANDAG Regional
Information System which cannot be reproduced without the written permission
of SANDAG. This product may contain information reproduced with permission
granted by Rand McNally & Company® to SanGIS. This map is copyrighted by
Rand McNally & Company®. It is unlawful to copy or reproduce all or any part
thereof, whether for personal use or resale, without the prior, written permission
of Rand McNally & Company®.

License should be verified with SanGIS to make sure it can be used within the app.

Data layers in shapefile polygon format can be downloaded from SanGIS:

@ghost
Copy link

ghost commented May 26, 2015

I am working to verify this, I have a GIS Supervisor here in our Department who works with SanGIS and hopefully should be able to provide us with the answer.

@ghost
Copy link

ghost commented May 26, 2015

From my SanGIS engineer on staff:

Hi Gary,

You have to accept the Use Agreement to download the data. Once submitted, you're good to go. The user couldn't have obtained the files otherwise. As long as you're not modifying the polygons and presenting the new data as SANDAG or SanGIS products, you're okay.

Thanks,
scott

@cgiovando
Copy link
Collaborator Author

Thanks @shaynei

Just to clarify: there is no explicit mention of a data license in the SanGIS use agreement presented when entering the Regional Data Warehouse. The Rand McNally reference is still there with a SanGIS "All Rights Reserved" statement.

From what I understand CC-BY is probably the closest license, but would be nice to confirm that it is at least compatible with ODBL since we are planning to import that data into OpenStreetMap.

CCing @MrMaksimize who may have experience with other open data licenses used within the City and County.

@jj0hns0n
Copy link

Can we get SANGIS to sign something saying its ok to import to OSM? There
is some precedent for this. http://wiki.openstreetmap.org/wiki/SanGIS

On Tue, May 26, 2015 at 6:12 PM, Cristiano Giovando <
[email protected]> wrote:

Thanks @shaynei https://github.com/Shaynei

Just to clarify: there is no explicit mention of a data license in the
SanGIS use agreement presented when entering the Regional Data Warehouse.
The Rand McNally reference is still there with a SanGIS "All Rights
Reserved" statement.

From what I understand CC-BY http://creativecommons.org/licenses/by/4.0/
is probably the closest license, but would be nice to confirm that it is at
least compatible with ODBL
http://opendatacommons.org/licenses/odbl/summary/ since we are planning
to import that data into OpenStreetMap.

CCing @MrMaksimize https://github.com/MrMaksimize who may have
experience with other open data licenses used within the City and County.


Reply to this email directly or view it on GitHub
#2 (comment)
.

@jj0hns0n
Copy link

We also use this letter on page 87 of this guide for other projects I work
on.

http://www.opencitiesproject.org/OpenCities_Book_LoRes.pdf

On Tue, May 26, 2015 at 6:19 PM, Jeffrey Johnson [email protected] wrote:

Can we get SANGIS to sign something saying its ok to import to OSM? There
is some precedent for this. http://wiki.openstreetmap.org/wiki/SanGIS

On Tue, May 26, 2015 at 6:12 PM, Cristiano Giovando <
[email protected]> wrote:

Thanks @shaynei https://github.com/Shaynei

Just to clarify: there is no explicit mention of a data license in the
SanGIS use agreement presented when entering the Regional Data Warehouse.
The Rand McNally reference is still there with a SanGIS "All Rights
Reserved" statement.

From what I understand CC-BY
http://creativecommons.org/licenses/by/4.0/ is probably the closest
license, but would be nice to confirm that it is at least compatible with
ODBL http://opendatacommons.org/licenses/odbl/summary/ since we are
planning to import that data into OpenStreetMap.

CCing @MrMaksimize https://github.com/MrMaksimize who may have
experience with other open data licenses used within the City and County.


Reply to this email directly or view it on GitHub
#2 (comment)
.

@ghost
Copy link

ghost commented Jun 3, 2015

Spoke with SanGIS and this is their reply:

Gary,

Okay, I think I see where the problem is now. I believe SanGIS needs to change their legal notice to remove the reference to Rand McNally. That reference is an appropriate notation on a map that uses the Rand McNally data (which the City and County can) but it is not data that is on the public data warehouse and therefore should not apply. I will work on getting it changed.

Scott’s initial reply is correct: If they download data from our public data warehouse they can use it anyway they want. If they use it unaltered we (SanGIS) ask that they provide a credit to SanGIS. But that is not a requirement and we can’t compel them to do that. If they use the data in any other way – add to, subtract from, “enhance”, etc. – then we specifically require them not to credit SanGIS.

The bottom line is: if they got it from our public data warehouse (www.sangis.org) then they can use it freely, including loading it into Open Street Map. In fact, I think a lot of the SanGIS data has already been loaded there.

I’ll work on changing the legal notice so that it doesn’t refer to the Rand McNally copyright.

Brad Lind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants