3 ms·
It has a viral license, any data you mix with OSM data becomes open source. Data sources that people commonly want to blend with mapping data have legal and re
by jandrewrogers 4y ago
It has a viral license, any data you mix with OSM data becomes open source.
Data sources that people commonly want to blend with mapping data have legal and regulatory restrictions with respect to privacy, data jurisdiction, acceptable use, statutory time limits, contract terms, etc. The OSM license terms are in conflict with legal and regulatory compliance requirements.
- tony_cannistra 4y agoThis is particularly true for governments. I know the United States Geological Survey wanted to use OSM data for portions of their cartography, but can't because it's not public domain (as their products must be).
- Doctor_Fegg 4y agoThough Overture also aren’t proposing public domain; they’re using a (newish, untested) permissive licence, CDLA.
- Bedon292 4y agoNot really. Any Derivative Data needs to be licensed under the same or compatible license IF it is Publicly Used [4.4a]. You can internally use it without issues. And you can have a Collective Database which includes it without licensing the entire database under the same license [4.5a]. See: https://opendatacommons.org/licenses/odbl/1-0/ https://opendatacommons.org/licenses/odbl/1-0/
- jandrewrogers 4y agoYou may disagree, but the legal departments of every organization I've worked for that has looked into the matter concurs with this opinion. It effectively prohibits many practical applications for which organizations want to use mapping data for more than rendering maps. Companies that do use OSM data have rigid policies that only allow it to be used in narrow contexts. The loophole that most companies seem to have landed on is using OSM data to do parallel construction of private data, which technically avoids the Derivative Database problem.