-
Notifications
You must be signed in to change notification settings - Fork 260
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
Conversation
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.
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. |
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.
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. |
https://osmfoundation.org/wiki/Licence/Waiver_and_Permission_Templates lists
with number 3 being further split into
My understanding is,
|
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. |
This reverts commit 769680e.
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. |
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.