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

Clarify OSM policy on data sources that are incompatible with OSM, in PH context #69

Closed
4 of 5 tasks
govvin opened this issue Jul 27, 2020 · 2 comments
Closed
4 of 5 tasks

Comments

@govvin
Copy link
Member

govvin commented Jul 27, 2020

This ticket documents actions taken after a query was made regarding certain edits in Mindanao , alleging derived data from an incompatible source, and questions about accuracy.

We reached out to the contributor who obliged by disclosing their workflow and sources used for said edits. We concur with Maning's takeaways, that some data is derived from the Philippine Statistical Authority geodata, without which, it would be impossible for them to determine said places and their respective locations.

Their other edits in the same changeset, those locations extrapolated from OSMaPaaralan data, where DepEd permission was granted to publish their 2013 dataset, can remain in OSM.

Under section 176 of the Republic Act 8293, Philippine government data are ineligible for copyright - are considered "public domain" -- but prior permission is required for commercial use. This explicitly opposes the OSM license, that offers unrestricted use, and only requiring OSM attribution. Hence, they should not be added in OpenStreetMap unless informed consent has been granted by the data owners, and they agree to publish the data in OSM under the terms of the ODbL, explicitly waiving off the government's terms on commercial use under said act.

After #67, and #69 incident, there's a pressing need to create clearer guidelines for volunteers who are interested in contributing data (or derived data) from sources other than themselves (e.g. proprietary data, data from government, data from work/projects, etc.)

Actions

  • ascertain sources and workflow with contributor
  • consult with Licensing Working Group for their position regarding R.A. 8293
  • reiterate OSM policies and add a local wiki page / FAQ to document best practices for contributors, when adding data they don't own themselves
  • write to talk-ph mailing list
  • ask the contributor to voluntarily remove said place nodes, with changeset comment referring to this ticket for future reference
@govvin
Copy link
Member Author

govvin commented Jul 27, 2020

The contributor agreed to voluntarily delete the affected place nodes. The operation was done in this changeset: 88541453

@govvin
Copy link
Member Author

govvin commented Jul 31, 2020

A draft FAQ - data sources for OSM contributors in PH is now available for community inputs.

@govvin govvin closed this as completed Feb 15, 2021
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

1 participant