Further work on professional services page

langs/en.json

@@ -376,6 +376,16 @@
         "intro": "<p>Once the data is in OpenStreetMap, you'll probably want to use the data as well. Your MapComplete theme can have a convenient <i>export</i>-button, offering to download the data in many open formats usable in QGis, ArcGis, Excel, LibreOffice-calc, ...</p><p>Someone with basic spreadsheet-skills can thus easily create graphs and insights about the data, whereas the GIS-experts within your organisation can easily work with this data in their preferred application.</p><p>If an automated setup is needed, a free-to-use, community-run API is available.</p>"
       }
     },
+    "services": {
+      "title": "MapComplete services",
+      "intro": "The developer of MapComplete can help you with the following services:",
+      "li0": "Setting up a theme tailored for your need",
+      "li1": "Help with setting up the internal data flow to integrate OpenStreetMap",
+      "li2": "Training on how to contribute data with MapComplete",
+      "li3": "Advanced training (e.g. for the GIS-team) on how to add advanced data to OpenStreetMap",
+      "li4": "Training on how to download filtered data from OpenStreetMap",
+      "outro": "These services are offered at competitive prices. A simple theme without extra support can be setup for as little €2000, and a small additional yearly hosting cost."
+    },
     "drawbacks": {
       "title": "A few drawbacks to keep in mind",
       "intro": "While joining this community has tremendous benefits, there are a few topics to carefully consider.",
@@ -392,9 +402,19 @@
         "li0": "All data can be reused for any purpose - including commercial purposes",
         "li1": "Applications or products using OpenStreetMap should give a clear copyright notice",
         "li2": "Any dataset or product which contains OpenStreetMap-data must be republished under ODbL too, including modifications to this dataset and in a usable format.",
-        "outro": "This has a few implications which should be considered for some usecases, as explained below"
+        "outro": "This has a few implications which should be considered for some usecases, as explained below",
+        "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.",
+          "outro": "As a result, this kind of mixing is not allowed"
+        },
+        "usecaseGatheringOpenData": {
+          "title": "Gathering open data",
+          "intro": "MapComplete is an excellent way to create Open Data, also for governments. By default, this data will be freely redistributable under the ODbL. However, if there is a requirement to publish the gathered data under a <i>public domain</i>-license (where <b>all</b> rights are granted to the public and no attribution is required), the ODbL is too restrictive. In this case, one can ask the contributors to add data as Public Domain (e.g. by informing them in the mapcomplete theme).  "
+        }
       }
-      
     }
   }
 }