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

Update FAQ.md with CC BY compatibility #2598

Merged
merged 1 commit into from
Jan 21, 2025
Merged

Update FAQ.md with CC BY compatibility #2598

merged 1 commit into from
Jan 21, 2025

Conversation

andrewharvey
Copy link
Collaborator

Use stronger language around CC BY requirements.

OSMF LWG require a waiver for CC BY and imagery is not compatible for tracing in OSM without one.

Further NC or SA licenses don't have a waiver and as such we can't accept their use.

Use stronger language around CC BY requirements.

OSMF LWG require a waiver for CC BY and imagery is not compatible for tracing in OSM without one.

Further NC or SA licenses don't have a waiver and as such we can't accept their use.
@grischard grischard merged commit 769680e into gh-pages Jan 21, 2025
1 check passed
@grischard grischard deleted the faq-cc-by branch January 21, 2025 05:51
@simonpoole
Copy link
Contributor

Is this based on a new position of the LWG?

Previously it was that manually tracing from imagery didn't create a derivative of the imagery. Obviously displaying -in- an editor is already covered either by an open licence or by explicit permission. That is why there are the specific request documents that essentially point that out to flush out any potential issues: https://osmfoundation.org/wiki/Licence/Waiver_and_Permission_Templates/Template_text_for_aerial_imagery_waivers

In particular and contrary to the new FAQ text, ND and NC licensed sources were consider usable.

@andrewharvey
Copy link
Collaborator Author

Sorry I mixed up the waiver template for CC BY and the template text for aerial imagery waivers (from here).

I can open a new PR to make it clear that CC BY imagery can be used with the CC BY waivers or imagery tracing waiver, CC BY/BY-NC/BY-SA can be used with the tracing waiver, and then any other licensed imagery with a general waiver.

Previously it was that manually tracing from imagery didn't create a derivative of the imagery.

Is the LWG policy document somewhere? Either OSMF requires a waiver or does not require a waiver. Given they provide 3 waivers (CC BY, imagery general, CC imagery) it would imply that we can only use with a waiver.

@andrewharvey
Copy link
Collaborator Author

https://osmfoundation.org/wiki/Licence/Waiver_and_Permission_Templates lists

  1. Cover letter and waiver template for CC BY 4.0 (ODT Format)
  2. Cover letter and waiver template for CC BY 2.0/3.0 (ODT Format)
  3. Template text for aerial imagery waivers (ODT Format)

with number 3 being further split into

  1. a) For an OSM waiver generally
  2. b) For a tracing waiver as to imagery already/to be released under CC BY/CC BY-NC/CC BY-SA

My understanding is,

  • for CC BY aerial imagery we can accept waiver 1/2, 3a or 3b.
  • for CC BY, CC BY-NC or CC BY-SA aerial imagery we can accept waiver 3a or 3b
  • for any other licensed or copyrighted imagery we can accept waiver 3a

@simonpoole
Copy link
Contributor

simonpoole commented Jan 21, 2025

Is the LWG policy document somewhere? Either OSMF requires a waiver or does not require a waiver. Given they provide 3 waivers (CC BY, imagery general, CC imagery) it would imply that we can only use with a waiver.

It is just a case of being safe instead of sorry, conceivably there are imagery providers that are the opinion that they own rights in data traced from their imagery. It should be documented somewhere in the LWG minutes but March 2017 or so.

andrewharvey added a commit that referenced this pull request Jan 21, 2025
@andrewharvey
Copy link
Collaborator Author

It is just a case of being safe instead of sorry, conceivably there are imagery providers that are the opinion that they own rights in data traced from their imagery. It should be documented somewhere in the LWG minutes but March 2017 or so.

Understood, but from the DWG point of view I believe the waivers are required to use the data and therefore we must require them to include the imagery as a reference in editors and hence this index.

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

Successfully merging this pull request may close these issues.

3 participants