Translated using Weblate (English)
Currently translated at 100.0% (409 of 409 strings) Translation: MapComplete/Core Translate-URL: https://hosted.weblate.org/projects/mapcomplete/core/en/
This commit is contained in:
parent
65a1d0e016
commit
3bc1f836ab
1 changed files with 4 additions and 4 deletions
|
@ -432,8 +432,8 @@
|
|||
"usecaseMapDifferentSources": {
|
||||
"title": "Creating a map from different sources",
|
||||
"intro": "<p>For example, one could make a map with all benches in some city, based on the benches known by OpenStreetMap. This printed map needs a clear statement that the map data is based on OpenStreetMap. Selling these maps is permitted.If the mapmaker notices that the benches are missing in some area and adds them on the printed map, the data on the missing benches are automatically open data too. This means that an OpenStreetMap-contributor is allowed to take the paper map and use it to add the missing benches back into OpenStreetMap.</p><p>This contributor also has the right to ask for the dataset of the missing benches, which should be provided too.</p><p>If the mapmaker notices that the benches are missing in some area and adds them on the printed map, the data on the missing benches are automatically open data too. This means that an OpenStreetMap-contributor is allowed to take the paper map and use it to add the missing benches back into OpenStreetMap. This contributor also has the right to ask for the dataset of the missing benches, which should be provided too.</p><p>Of course, a map with only benches can be boring. The mapmaker might also decide to add in a layer with shops, possibly sourced from another geodata provider under another license. This is permitted to, if the map clearly states that the benches are sourced from OSM (under ODBL) and the shops have a different source (eventually with an all rights reserved).</p><p>However, mixing two datasets into one undistinguishible layer might not be permitted. For example, the mapmaker migth find that OSM has excellent data on benches in one part of the city and the closed-source provider might have excellent data on benches in another part of the city, merging these datasets into one could be problematic: </p>",
|
||||
"li0": "the open license would require the modifications to be openly republished...",
|
||||
"li1": "...whereas the all-rights-reserved license would prohibit this.",
|
||||
"li0": "the open license would require the modifications to be openly republished…",
|
||||
"li1": "…whereas the all-rights-reserved license would prohibit this.",
|
||||
"outro": "As a result, this kind of mixing is not allowed"
|
||||
},
|
||||
"usecaseGatheringOpenData": {
|
||||
|
|
Loading…
Reference in a new issue