View source for Licence/Community Guidelines

As publisher of the OpenStreetMap geodata database under the ODbL, the OpenStreetMap Foundation, OSMF, gets asked to clarify how data can/should be used in certain situations. The OSMF's mission is to support but not control OpenStreetMap. OSMF's role as Licensor and publisher of the database should not involve dictating policy. To that end, [https://wiki.openstreetmap.org/wiki/Open_Data_License/Community_Guidelines/How_We_Create_Community_Guidelines we have evolved a process] called Community Guidelines. On legal advice, what a Licensor says carries weight with users of our data and, potentially, to a judge. A court would make a final decision on the issue, however we hope these guidelines are helpful to avoid disputes arising in the first place and can be considered by the courts in coming to their verdict. 

Here are guidelines that have gone through the full process and have been endorsed by the OSMF board. You can also find a full list of new and evolving guidelines [https://wiki.openstreetmap.org/wiki/Open_Data_License/Community_Guidelines here].

Making maps where you want to mix OpenStreetMap with other sources:

* '''[[Licence/Community_Guidelines/Regional Cuts - Guideline|Regional Cuts]]''' - The principle that a map provider can use maps from OpenStreetMap in one part of the world and not be obliged to share data from another supplier used elsewhere in the world has been established for several years. Here we formalise and state what we are happy with and give examples that we hope will help potential OpenStreetMap users with incompatible sources.

* '''[[Licence/Community_Guidelines/Horizontal Map Layers - Guideline|Horizontal Layers]]''' - The principle that a map maker can make and publish a map made from several distinct horizontal layers without being obliged to share data from the non-OpenStreetMap layers has been established for several years and is much clearer with the switch to the ODbL. Here we formalise and state what we are happy with and give examples that we hope will help potential OpenStreetMap users with incompatible sources.

* '''[[Licence/Community_Guidelines/Collective Database Guideline Guideline|Collective Database]]''' - A Collective Database is defined by the ODbL as a database consisting of a collection of “independent” databases. This Guideline clarifies that so long as a particular data type within a database consists entirely of non-OSM data within a regional cut, the OSM and non-OSM datasets will be considered “independent” and thus, the combination will be considered a Collective Database rather than a Derivative Database. 

Other guidelines:

* '''[[Licence/Community_Guidelines/Trivial Transformations - Guideline|Trivial Transformations]]''' - where a change is made purely algorythmically without using externally collected (non-OSM) metadata. When is it so trivial that there should be no obligation to share the changes or how they were made?

* '''[[Licence/Community_Guidelines/Geocoding - Guideline|Geocoding]]''' - when addresses or geographic locations from user input or third party databases are geocoded with OpenStreetMap data, what obligations apply?

* '''[[Licence/Community_Guidelines/Produced Work - Guideline|Produced Work]]''' - "Produced Work" is a term used by ODbL to broadly separate something created from a database but not a database itself.  For OpenStreetMap, this often means a map, but could be something else (a mug, a data visualisation...).  Usually the distinction is clear, but if you are having trouble in deciding, we hope that this guideline will help you.

* '''[[Licence/Community_Guidelines/Substantial - Guideline|Substantial]]''' - ODbL uses the term "Substantial". "Substantial" is a term which comes from the European Database Directive. This is OpenStreetMap's view of what is substantial in our own context.

* '''[[Licence/Attribution_Guidelines|Attribution Guidelines]]''' - Guidelines for OSMF's recommended forms of attribution to OpenStreetMap