diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image1.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image1.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image1.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image1.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image9.jpg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image9.jpg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image9.jpg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image9.jpg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd similarity index 95% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd index 3111dd79..4d334e4a 100644 --- a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd +++ b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1.qmd @@ -113,7 +113,7 @@ As an **Admin User** your account has certain authorizations, i.e. you are able Search function, to **search for an organisation** within the system. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png){width="6.925in" height="2.222916666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image6.png){width="6.925in" height="2.222916666666667in"} []{#_Ref153959302 .anchor}**Figure 6‑1: Menu item -- Organisations** @@ -127,7 +127,7 @@ As an Admin User your account has certain authorizations, i.e. you are able to a Further, you have the possibility to **search for a User.** -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png){width="6.925in" height="2.7680555555555557in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image7.png){width="6.925in" height="2.7680555555555557in"} []{#_Ref153959323 .anchor}**Figure 6‑2: Menu item -- Users.** @@ -135,7 +135,7 @@ Further, you have the possibility to **search for a User.** To open the **User Profile** you can either click on the User Profile Icon in the Header, which opens a context menu with the actions 'My Profile' and 'Logout' ([Figure 6‑3](#_Ref153959344)) or in the Users tab by clicking on your name ([Figure 6‑3](#_Ref153959344)). You will then be forwarded to the Profile view. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png){width="6.925in" height="1.1444444444444444in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image8.png){width="6.925in" height="1.1444444444444444in"} []{#_Ref153959344 .anchor}**Figure 6‑3: User Profile -- Actions.** @@ -149,7 +149,7 @@ When you click on the context menu action 'My Profile' of the User Profile Icon As an Admin User can deactivated by a person with the role 'User Administration / support'. "Inactive" Users do not have access to the application. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png){width="6.925in" height="3.827777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image10.png){width="6.925in" height="3.827777777777778in"} []{#_Ref153959381 .anchor}**Figure 6‑4: View User Profile (User Administrator).** @@ -161,7 +161,7 @@ Editing your profile will only affect / edit the user profile in the CLC+ Core s By clicking on 'Save' your entered information will be saved. If you do not want to save the changed information, then you have the possibility to click on 'Cancel' (see [Figure 6‑5](#_Ref153959405)). -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png){width="6.925in" height="2.23125in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image11.png){width="6.925in" height="2.23125in"} []{#_Ref153959405 .anchor}**Figure 6‑5: Edit User Profile.** @@ -171,11 +171,11 @@ In the "**Add new version**" dialog a call is made to the EIONET data dictionary By clicking on the **EIONET Data Dictionary** link you will be redirected to the EIONET data dictionary. Data Dictionary[^1] holds definitions of datasets, tables and data elements (see [Figure 6‑7](#_Ref153959430)). Each of these three levels is defined by a set of attributes, the core set of which corresponds to ISO 11179 standard for describing data elements. The whole attribute set is flexible, and attributes can be added / removed from/to the system. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png){width="6.925in" height="1.7979166666666666in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image12.png){width="6.925in" height="1.7979166666666666in"} []{#_Ref99095063 .anchor}**Figure 6‑6: Add new EAGLE Ontology Version.** -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png){width="6.0178619860017495in" height="2.9841885389326333in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image13.png){width="6.0178619860017495in" height="2.9841885389326333in"} []{#_Ref153959430 .anchor}**Figure 6‑7: EIONET data dictionary.** @@ -189,7 +189,7 @@ Once a new EAGLE ontology version is published all users get a notification (see The EAGLE barcoding of an Ingestion can be approved for being **EAGLE compliant** by any user with the additional role of being an "EAGLE Maintainer/Approver". When opening an Ingestion, the button "Approve EAGLE Compliance" can only by seen by users with that role (see [Figure 6‑8](#_Ref153959461)). The User gets notified once the EAGLE barcoding for the Ingestion is approved by an EAGLE Maintainer. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png){width="6.925in" height="3.8361111111111112in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image14.png){width="6.925in" height="3.8361111111111112in"} []{#_Ref153959461 .anchor}**Figure 6‑8:Approval of EAGLE compliance for an Ingestion.** @@ -197,7 +197,7 @@ The Ingestion gets than a quality stamp in the Data Catalogue (first column) and The **EAGLE approval** for an Ingestion can also be revoked again by the EAGLE Maintainer (see [Figure 6‑9](#_Ref153959479)). Each approval change is saved and displayed in the history of an Ingestion. -![](./CLC+Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png){width="6.925in" height="3.1902777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_Annex_Admin_User_v1-media/image15.png){width="6.925in" height="3.1902777777777778in"} []{#_Ref153959479 .anchor}**Figure 6‑9:Approval and possibility to revoke the EAGLE approval again.** diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image1.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image1.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image1.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image1.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image10.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image10.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image10.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image10.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image100.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image100.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image100.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image100.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image101.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image101.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image101.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image101.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image102.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image102.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image102.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image102.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image103.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image103.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image103.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image103.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image104.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image104.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image104.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image104.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image105.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image105.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image105.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image105.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image106.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image106.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image106.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image106.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image107.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image107.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image107.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image107.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image108.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image108.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image108.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image108.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image109.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image109.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image109.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image109.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image11.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image11.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image11.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image11.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image110.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image110.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image110.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image110.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image111.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image111.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image111.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image111.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image112.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image112.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image112.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image112.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image113.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image113.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image113.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image113.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image114.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image114.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image114.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image114.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image115.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image115.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image115.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image115.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image116.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image116.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image116.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image116.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image117.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image117.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image117.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image117.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image118.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image118.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image118.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image118.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image119.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image119.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image119.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image119.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image12.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image12.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image12.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image12.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image120.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image120.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image120.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image120.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image121.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image121.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image121.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image121.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image122.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image122.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image122.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image122.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image123.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image123.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image123.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image123.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image124.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image124.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image124.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image124.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image125.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image125.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image125.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image125.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image126.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image126.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image126.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image126.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image127.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image127.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image127.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image127.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image128.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image128.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image128.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image128.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image129.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image129.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image129.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image129.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image13.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image13.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image13.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image13.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image130.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image130.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image130.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image130.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image132.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image132.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image132.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image132.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image133.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image133.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image133.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image133.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image134.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image134.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image134.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image134.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image135.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image135.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image135.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image135.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image136.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image136.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image136.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image136.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image137.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image137.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image137icon.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137icon.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image137icon.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137icon.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image138.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image138.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image138.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image138.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image139.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image139.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image139.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image139.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image14.jpg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image14.jpg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image14.jpg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image14.jpg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image140.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image140.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image140.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image140.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image141.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image141.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image141.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image141.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image142.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image142.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image142.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image142.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image143.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image143.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image143.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image143.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image144.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image144.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image144.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image144.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image145.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image145.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image145.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image145.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image146.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image146.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image146.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image146.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image147.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image147.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image147.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image147.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image148.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image148.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image148.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image148.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image149.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image149.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image149.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image149.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image15.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image15.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image15.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image15.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image150.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image150.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image150.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image150.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image151.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image151.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image151.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image151.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image152.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image152.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image152.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image152.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image153.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image153.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image153.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image153.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image154.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image154.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image154.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image154.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image155.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image155.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image155.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image155.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image156.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image156.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image156.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image156.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image157.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image157.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image157.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image157.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image158.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image158.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image158.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image158.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image159.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image159.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image159.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image159.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image16.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image16.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image16.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image16.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image160.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image160.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image160.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image160.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image161.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image161.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image161.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image161.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image162.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image162.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image162.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image162.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image163.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image163.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image163.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image163.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image164.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image164.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image164.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image164.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image165.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image165.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image165.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image165.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image166.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image166.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image166.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image166.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image167.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image167.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image167.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image167.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image168.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image168.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image168.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image168.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image169.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image169.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image169.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image169.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image17.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image17.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image17.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image17.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image18.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image18.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image18.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image18.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image19.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image19.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image19.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image19.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image2.jpg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image2.jpg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image2.jpg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image2.jpg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image20.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image20.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image20.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image20.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image21.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image21.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image21.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image21.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image23.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image23.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image23.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image23.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image24.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image24.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image24.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image24.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image25.jpeg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image25.jpeg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image25.jpeg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image25.jpeg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image26.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image26.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image26.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image26.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image27.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image27.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image27.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image27.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image28.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image28.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image28.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image28.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image29.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image29.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image29.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image29.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image3.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image3.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image3.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image3.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image30.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image30.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image30.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image30.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image32.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image32.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image32.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image32.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image34.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image34.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image34.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image34.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image35.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image35.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image35.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image35.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image36.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image36.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image36.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image36.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image37.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image37.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image37.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image37.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image38.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image38.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image38.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image38.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image39.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image39.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image39.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image39.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image4.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image4.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image4.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image4.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image40.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image40.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image40.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image40.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image41.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image41.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image41.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image41.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image42.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image42.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image42.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image42.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image43.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image43.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image43.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image43.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image44.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image44.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image44.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image44.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image45.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image45.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image45.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image45.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image46.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image46.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image46.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image46.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image47.jpg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image47.jpg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image47.jpg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image47.jpg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image48.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image48.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image48.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image48.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image49.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image49.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image49.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image49.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image5.jpg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image5.jpg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image5.jpg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image5.jpg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image50.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image50.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image50.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image50.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image51.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image51.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image51.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image51.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image52.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image52.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image52.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image52.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image53.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image53.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image53.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image53.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image54.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image54.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image54.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image54.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image55.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image55.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image55.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image55.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image56.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image56.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image56.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image56.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image57.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image57.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image57.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image57.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image58.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image58.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image58.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image58.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image59.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image59.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image59.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image59.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image6.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image6.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image6.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image6.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image60.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image60.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image60.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image60.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image61.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image61.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image61.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image61.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image62.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image62.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image62.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image62.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image63.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image63.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image63.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image63.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image64.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image64.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image64.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image64.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image65.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image65.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image65.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image65.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image66.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image66.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image66.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image66.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image67.JPG b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image67.JPG similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image67.JPG rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image67.JPG diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image68.JPG b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image68.JPG similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image68.JPG rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image68.JPG diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image69.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image69.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image69.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image69.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image7.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image7.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image7.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image7.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image70.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image70.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image70.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image70.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image71.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image71.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image71.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image71.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image72.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image72.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image72.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image72.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image73.JPG b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image73.JPG similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image73.JPG rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image73.JPG diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image74.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image74.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image74.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image74.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image75.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image75.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image75.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image75.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image76.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image76.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image76.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image76.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image77.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image77.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image77.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image77.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image78.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image78.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image78.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image78.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image79.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image79.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image79.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image79.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image8.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image8.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image8.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image8.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image80.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image80.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image80.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image80.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image81.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image81.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image81.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image81.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image82.jpeg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image82.jpeg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image82.jpeg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image82.jpeg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image83.jpeg b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image83.jpeg similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image83.jpeg rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image83.jpeg diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image84.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image84.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image84.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image84.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image85.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image85.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image85.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image85.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image86.JPG b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image86.JPG similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image86.JPG rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image86.JPG diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image87.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image87.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image87.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image87.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image88.JPG b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image88.JPG similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image88.JPG rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image88.JPG diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image89.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image89.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image89.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image89.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image9.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image9.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image9.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image9.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image90.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image90.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image90.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image90.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image91.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image91.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image91.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image91.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image92.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image92.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image92.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image92.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image93.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image93.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image93.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image93.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image94.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image94.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image94.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image94.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image95.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image95.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image95.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image95.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image96.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image96.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image96.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image96.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image97.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image97.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image97.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image97.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image98.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image98.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image98.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image98.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image99.png b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image99.png similarity index 100% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1-media/image99.png rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1-media/image99.png diff --git a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1.qmd b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1.qmd similarity index 93% rename from DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1.qmd rename to DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1.qmd index 66f42316..1a891711 100644 --- a/DOCS/clcplus-core/CLC+Core_User_Manual_Issue_4.0_v1.qmd +++ b/DOCS/CLCplus_Core/CLCplus_Core_User_Manual_Issue_4.0_v1.qmd @@ -112,7 +112,7 @@ In addition, in section [5](#faq-frequently-asked-questions) frequently asked qu With CLC+ Core, the European Environment Agency (EEA) offers you a consistent multi-use grid-based, web-based Land Cover/Land Use (LC/LU) hybrid data repository. Following up on the CLC+ Backbone, the CLC+ Core constitutes the second stage of the CLC+ Product Suite (see [Figure 1‑1](#_Ref151465617)). The CLC+ Core provides a flexible database approach to incorporate existing and future European Copernicus Land Monitoring Service (CLMS) products as well as various national land cover (LC) and land use (LU) datasets, by standardised integration along the EAGLE language, which further enables the Extraction of various CLC+ Instances. CLC+ Core will thus be able to provide unprecedented information to strengthen Europe's leading role in climate change impact mitigation and the management of environmental monitoring in support of programmes and policies such as Land Use, Land-Use Change and Forestry (LULUCF) and the European Green Deal. The goal of the CLC+ suite is to become the new European standard in land monitoring, within the CLMS. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image3.png){width="6.419444444444444in" height="2.6032841207349082in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image3.png){width="6.419444444444444in" height="2.6032841207349082in"} []{#_Ref151465617 .anchor}**Figure 1‑1: CLC+ Product suite overview (from left to right) with the CLC+ Core database solution (middle) hosting integrated CLMS, and potentially ancillary and national LC/LU data.** @@ -132,7 +132,7 @@ The European Environment Information and Observation Network (EIONET) is a partn Eionet user accounts are created for those who need access to Eionet websites, tools and services that require Eionet login. **New user accounts can only be created by the Eionet Helpdesk and the National Focal Points.** The Eionet helpdesk is manned throughout the opening hours of EEA and generally responds to the ticket within 24 hours. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image4.png){width="6.093470034995626in" height="3.9828751093613297in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image4.png){width="6.093470034995626in" height="3.9828751093613297in"} []{#_Ref151465691 .anchor}**Figure 1‑2: CLC+ Core login page** @@ -163,7 +163,7 @@ The **Header** section contains the Navigation Menu (see [Figure 1‑3](#_Ref151 The **Content** represents the section between the Header and the Footer area and varies depending on which tab is opened (see [Figure 1‑3](#_Ref151621809)). The Data Catalogue (section [1.6](#data-catalogue)) is the landing page / starting point of CLC+ Core. To navigate through the system, simply click on the relevant navigation tabs or entries. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image7.png){width="6.925in" height="3.8055555555555554in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image7.png){width="6.925in" height="3.8055555555555554in"} []{#_Ref151621809 .anchor}**Figure 1‑3: Content example - Data Catalogue** @@ -175,7 +175,7 @@ Organisations are taken over by default from EIONET with your first login to CLC **Search function**, to search for an organisation within the system (see [Figure 1‑4](#_Ref151465792)). If you are an Admin User, please refer to section 6.1 in separate Annex. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image8.png){width="6.925in" height="3.8201388888888888in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image8.png){width="6.925in" height="3.8201388888888888in"} []{#_Ref151465792 .anchor}**Figure 1‑4: Menu item -- Organisations** @@ -187,7 +187,7 @@ Users are taken over by default from EIONET with your first login to CLC+ Core. You have the possibility to search for a **User** (see [Figure 1‑5](#_Ref100263548)). If you are an Admin User, please refer to section 6.2 in separate Annex. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image9.png){width="6.925in" height="3.832638888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image9.png){width="6.925in" height="3.832638888888889in"} []{#_Ref100263548 .anchor}**Figure 1‑5: Menu item -- Users** @@ -195,7 +195,7 @@ You have the possibility to search for a **User** (see [Figure 1‑5](#_Ref10026 To open the **User Profile** View you can either click on the User Profile Icon in the Header, which opens a context menu with the actions 'My Profile' and 'Logout' ([Figure 1‑6](#_Ref100263532)) or in the Users tab by clicking on your name. You will then be forwarded to the Profile view. By clicking on Logout your session will be terminated. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image11.png){width="6.925in" height="1.1444444444444444in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image11.png){width="6.925in" height="1.1444444444444444in"} []{#_Ref100263532 .anchor}**Figure 1‑6: User Profile -- Actions** @@ -207,7 +207,7 @@ When you click on the context menu action 'My Profile' of the User Profile Icon **Roles:** In this area it is displayed what roles are assigned to you. Roles define what you as a user are allowed to do within the CLC+ Core system from a functional point of view. You are perfectly able to use the system if there are no roles assigned to you. If you are an Admin User, please refer to section 6.2 in separate Annex. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image12.png){width="6.925in" height="3.8125in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image12.png){width="6.925in" height="3.8125in"} []{#_Ref151622278 .anchor}**Figure 1‑7: View User Profile (User without special roles)** @@ -243,9 +243,9 @@ In addition to the functionalities mentioned above, the data catalogue is the st or to start an Extraction configuration (**Add Extractions**) (see [Figure 1‑8](#_Ref151467230) [Figure 1‑9](#_Ref151467380)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image16.png){width="6.925196850393701in" height="3.811023622047244in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image16.png){width="6.925196850393701in" height="3.811023622047244in"} -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image17.png){width="6.925in" height="2.086956474190726in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image17.png){width="6.925in" height="2.086956474190726in"} []{#_Ref151467230 .anchor}**Figure 1‑8: Data Catalogue (Ingestions upper image, lower image Extractions view)** @@ -255,7 +255,7 @@ The Data Catalogue lists all Ingestions and Extractions available in the CLC+ Co Further there are '**Quick Filters**" available. The user can quickly filter by "Ingestion", "Extraction", "My Organisation" or "My Data" (see [Figure 1‑9](#_Ref151467380)). By clicking on e.g. "My Data" symbol the filter for the table blow gets activated (check mark appears) and only shows then the Ingestions/Extractions = data the user added. Same applies for "My Organisation" only data shown ingested or extracted by the user's organisation are shown. By activating (clicking on the symbol) for example "Ingestions" only Ingestions are shown in the table. Each of these quick filter options can easily be deactivated again by clicking on it again (check mark will disappear) and no filters will be applied to the table below anymore. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image18.png){width="6.925in" height="1.6416666666666666in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image18.png){width="6.925in" height="1.6416666666666666in"} []{#_Ref151467380 .anchor}**Figure 1‑9: Data Catalogue -- Main functionalities** @@ -263,7 +263,7 @@ Further there are '**Quick Filters**" available. The user can quickly filter by **Breadcrumbs** appear on sub-pages to show their parent pages. This helps you to identify how you got to the page you are currently working on (see [Figure 1‑10](#_Ref151467456)). In addition, it provides you more information about the context. Breadcrumbs are not clickable. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image19.png){width="6.925in" height="3.828472222222222in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image19.png){width="6.925in" height="3.828472222222222in"} []{#_Ref151467456 .anchor}**Figure 1‑10: Breadcrumbs** @@ -271,7 +271,7 @@ Further there are '**Quick Filters**" available. The user can quickly filter by **Help function** by clicking on the "?" icon on the bottom right corner (see Figure 1‑11) a separate Help window opens in which the use can report any issues or questions. The support contact form can be found here: . -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image21.png){width="6.925in" height="3.828472222222222in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image20.png) +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image21.png){width="6.925in" height="3.828472222222222in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image20.png) **Figure 1‑11: Pagination and Help function** @@ -285,7 +285,7 @@ By default, all archived data is not shown. By activating 'Show ARCHIVED data' a **Filtered results** will be shown then on the right. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image23.png){width="6.925in" height="3.7830194663167105in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image23.png){width="6.925in" height="3.7830194663167105in"} []{#_Ref151467805 .anchor}**Figure 1‑12: Search and Filter function in the Data Catalogue** @@ -297,25 +297,25 @@ The search function can be found in several tabs in the CLC+ Core system. In the In the example in [Figure 1‑13](#_Ref98847093), the EAGLE barcoding is missing and the Country / Region field has not been filled out -- therefore these fields are highlighted in red, and you get the hint with the notification to fill out all required fields. If not all required fields are filled the action/process cannot start. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image24.png){width="6.929391951006124in" height="6.158339895013123in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image24.png){width="6.929391951006124in" height="6.158339895013123in"} []{#_Ref98847093 .anchor}**Figure 1‑13: Add Ingestion -- Notification of a failed preview due to missing EAGLE barcoding and the Country/region field has not been filled out -- therefore these fields are highlighted in red, and you get the hint with the notification to fill out all required fields.** **Pop-up notifications** are messages shown on your desktop to grab your attention. The following figures show some examples for pop-up notifications (see [Figure 1‑14](#_Ref98938457), [Figure 1‑15](#_Ref98938435) and [Figure 1‑16](#_Ref98938437)). Pop-up notifications are also shown in case there is an invalid entry in the uploaded EAGLE barcoding file (see [Figure 1-17](#_Ref152831048)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image25.jpeg){width="6.925in" height="2.794145888013998in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image25.jpeg){width="6.925in" height="2.794145888013998in"} []{#_Ref98938457 .anchor}**Figure 1‑14: Pop-up Notification about deleting Ingestion. If an Ingestion upload was not successful, you can either delete the Ingestion or retry with different datasets or input parameters.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image26.png){width="6.925in" height="3.0034722222222223in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image26.png){width="6.925in" height="3.0034722222222223in"} []{#_Ref98938435 .anchor}**Figure 1‑15: Pop-up Notification about deleting Ingestion** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image27.png){width="6.925in" height="3.3541666666666665in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image27.png){width="6.925in" height="3.3541666666666665in"} []{#_Ref98938437 .anchor}**Figure 1‑16: Pop-up Notification about uploading documents** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image28.png){width="6.3in" height="3.747916666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image28.png){width="6.3in" height="3.747916666666667in"} []{#_Ref152831048 .anchor}**Figure 1-17: Pop-up Notification about errors in the uploaded EAGLE barcoding file and the hint in which columns in the Excel file there are some potential errors.** @@ -359,19 +359,19 @@ The following events/status changes trigger a **notification message** (examples By clicking on the **notification's icon**, a more detailed view of the notifications opens which includes all notifications (see Figure 1‑18). By clicking on the notification or by clicking "Mark all as read" (all) notifications get read and the blue dot disappears. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image30.png) +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image30.png) -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image29.png){width="6.925196850393701in" height="1.330708661417323in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image29.png){width="6.925196850393701in" height="1.330708661417323in"} []{#_Toc154044680 .anchor}**Figure 1‑18: Notifications at the header (blue dot if new/unread notifications is available), by clicking on the clock the notifications open up on the right.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image34.png){width="3.039200568678915in" height="1.3968996062992125in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image35.png){width="2.766547462817148in" height="1.4241305774278215in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image34.png){width="3.039200568678915in" height="1.3968996062992125in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image35.png){width="2.766547462817148in" height="1.4241305774278215in"} []{#_Ref151471608 .anchor}**Figure 1‑19: Examples for notification of status changes.** Further if the users email address is added in the user profile an email with the notification will be send automatically if the notification is not read within 15 min (see below [Figure 1‑20](#_Ref151472379)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image36.png){width="5.388442694663167in" height="3.1378543307086613in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image36.png){width="5.388442694663167in" height="3.1378543307086613in"} []{#_Ref151472379 .anchor}**Figure 1‑20: Notification email in case of an unread notification** @@ -383,7 +383,7 @@ In general, datasets in national projections can be ingested into the CLC+ Core. Within the Navigation Menu you can find the entry "**About EAGLE**" which brings you directly to the [homepage of the EAGLE group](https://land.copernicus.eu/en/eagle?tab=main) (see [Figure 1‑21](#_Ref151986403)) when clicking on it. On this page you can find additional information about EAGLE, documentations and tools and the context and background of the Pan-European Implementation of CLC+ based on the EAGLE concept. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image37.png){width="6.925in" height="3.823611111111111in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image37.png){width="6.925in" height="3.823611111111111in"} []{#_Ref151986403 .anchor}**Figure 1‑21: Homepage of the EAGLE group on land.copernicus.eu** @@ -415,7 +415,7 @@ In the CLMS products, such as the HRLs, each class in the nomenclature is coded [Figure 2‑1](#_Ref98942013) shows HRL IMD as example: Barcode of value 5 means that the input class directly relates to the EAGLE element (*LCC_1_1_1* *Sealed Artificial Surfaces and Constructions*) and therefore the spatial coverage of the class can be considered the spatial coverage of the EAGLE element. A pure exclusive solitary element and nothing else besides the 5-coded element is contained. Additionally, a factor defines the coverage of the EAGLE element for the Input Class. Value range is from 0.0 to 1.0. Together with the percentage coverage of the Input Class for each cell it defines the coverage of the EAGLE element for each cell. For example, if an Input Class has got a percentage coverage of 80% for the specific cell and a factor of 0.5 is applied to the specific EAGLE element, the coverage of the EAGLE element for this cell is 40%. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image38.png){width="3.9963746719160107in" height="2.9793580489938756in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image38.png){width="3.9963746719160107in" height="2.9793580489938756in"} []{#_Ref98942013 .anchor}**Figure 2‑1: The EAGLE matrix for HRL Imperviousness degree (excerpt).** @@ -435,7 +435,7 @@ b. **Reduce complexity** - Limit the complexity and simplify the barcoding (example see [Figure 2‑2](#_Ref151986473)). Focus on the most useful codes and highest possible hierarchy levels, considering the future Extractions. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image39.png){width="6.268055555555556in" height="2.5555555555555554in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image39.png){width="6.268055555555556in" height="2.5555555555555554in"} []{#_Ref151986473 .anchor}**Figure 2‑2: Comparison simplified or more explicit barcoding** @@ -445,11 +445,11 @@ c. **Try to not interpret** - On the other hand, sometimes the Land Use is absolutely clear from the nomenclature. The Netherlands BBG dataset describes on class: \"Inland water for mineral extraction", which can be mapped as displayed in [Figure 2‑4](#_Ref100052208). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image40.png){width="6.268055555555556in" height="5.131944444444445in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image40.png){width="6.268055555555556in" height="5.131944444444445in"} []{#_Ref100052219 .anchor}**Figure 2‑3: Coastal Zones - \"Open Sea\" land cover components, land use attributes** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image41.png){width="6.268055555555556in" height="4.072916666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image41.png){width="6.268055555555556in" height="4.072916666666667in"} []{#_Ref100052208 .anchor}**Figure 2‑4: NL BBG - \"Inland water for mineral extraction\"** @@ -458,7 +458,7 @@ d. **Interpretation might be necessary for differentiation** - Even if we stated under d. that interpretation should be avoided, sometimes the barcoding will need a little "interpretation" to differentiate classes or their use. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image42.png){width="6.268055555555556in" height="4.33125in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image42.png){width="6.268055555555556in" height="4.33125in"} []{#_Toc137576632 .anchor}**Figure 2‑5: Natura 2000 - \"(Semi-)Natural Forest\" vs \"Plantations\" land use attribute mapping** @@ -466,11 +466,11 @@ e. **Consider Land Cover and Land Use separately** - Not always both land cover and land use will be useful for Extractions. Sometimes we have a very heterogeneous land cover setting but clear land use, and vice-versa. Some classes will not offer much insight due to a (potential) combination of abiotic, biotic and water land cover components. For such classes, the land use section might be more useful. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image43.png){width="6.268055555555556in" height="6.988194444444445in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image43.png){width="6.268055555555556in" height="6.988194444444445in"} []{#_Toc137576633 .anchor}**Figure 2‑6: NL BBG - \"Sports Area\" which includes land cover component ice rinks** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image44.png){width="6.268055555555556in" height="3.713888888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image44.png){width="6.268055555555556in" height="3.713888888888889in"} []{#_Toc137576634 .anchor}**Figure 2‑7: NL BBG - \"Sports Area\" has a clear land use barcoding** @@ -498,13 +498,13 @@ Users are also able to **download the EAGLE barcoding template using this button - **Now, that you have everything reclassified, you can start the EAGLE barcoding** -> ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image45.png){width="3.620683508311461in" height="3.2496117672790903in"} ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image46.png){width="2.416116579177603in" height="3.2214873140857394in"} +> ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image45.png){width="3.620683508311461in" height="3.2496117672790903in"} ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image46.png){width="2.416116579177603in" height="3.2214873140857394in"} []{#_Ref99878072 .anchor}**Figure 2‑8: The original 337 classes (GEWASCODE) from the Dutch LPIS dataset were reduced /aggregated to 16 classes (LGN).** You are also able to have a look at the details of each EAGLE Ontology version by clicking on "open" within the context menu of each EAGLE Ontology version from the table. The detail page is described in section [2.4](#view-details-of-eagle-ontology). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image51.png){width="6.925in" height="1.7451388888888888in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image51.png){width="6.925in" height="1.7451388888888888in"} []{#_Ref151986517 .anchor}**Figure 2‑9: EAGLE Ontology overview** @@ -520,17 +520,17 @@ Additionally, you can open the details of each EAGLE element by a right-click an After you clicked on "show details" a dialog will pop up to show you all relevant information for the specific EAGLE element (see [Figure 2‑11](#_Ref151986570)). You can see in which version (Version), when (created at) and by whom (created by) it was created, since (since version) and until (to version) which version it was active in the ontology, when (changed at) and by whom it has been changed (changed by) and a description. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image53.png){width="6.925in" height="3.8180555555555555in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image53.png){width="6.925in" height="3.8180555555555555in"} []{#_Ref151986549 .anchor}**Figure 2‑10: View details of EAGLE Ontology** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image54.png){width="6.925in" height="3.817361111111111in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image54.png){width="6.925in" height="3.817361111111111in"} []{#_Ref151986570 .anchor}**Figure 2‑11: View details of EAGLE element** In addition, the EAGLE mapping barcoding file of a published Ingestion can be downloaded on the detail view page of the Ingestion. Either at the bottom left of the page under "Additional Documents" by clicking on the file or by using the "Download EAGLE Barcoding" button below the map view (see [Figure 2-12](#_Ref152831592)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image55.png){width="6.925in" height="3.81875in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image56.png){width="6.925in" height="1.073611111111111in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image55.png){width="6.925in" height="3.81875in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image56.png){width="6.925in" height="1.073611111111111in"} []{#_Ref152831592 .anchor}**Figure 2-12: Options for downloading the EAGLE barcoding file of a published Ingestion.** @@ -540,9 +540,9 @@ The EAGLE barcoding of an Ingestion can be approved for being EAGLE compliant by The Ingestions gets then a quality stamp/icon in the Data Catalogue (first column 'EAGLE approved'). By hovering over it with the mouse an explanation appears in the grey box: "The EAGLE mapping was reviewed and approved by the EAGLE Group". Further when opening the Ingestion itself the approval appears next to the status (see [Figure 2‑13](#_Ref151645180)). Moreover, when selecting Input classes for an Extraction (see section [4.4](#add-input-classes-to-extraction)) there is also the possibility in the 'add input class' view to filter by 'show only EAGLE approved Input classes'. The EAGLE approval for an Ingestion can also be revoked again by the EAGLE Maintainer. Each approval change is saved and displayed in the history of an Ingestion. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image57.png){width="6.925in" height="1.4673611111111111in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image57.png){width="6.925in" height="1.4673611111111111in"} -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image58.png){width="6.925in" height="3.2222222222222223in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image58.png){width="6.925in" height="3.2222222222222223in"} []{#_Ref151645180 .anchor}**Figure 2‑13: EAGLE Approval stamp in the Data Catalogue (upper image) and Ingestion view (lower image).** @@ -572,7 +572,7 @@ In the meanwhile, the consortium gained valuable experience about the EAGLE barc As mentioned in the introduction, users are able to add already existing datasets to the CLC+ Core, such as products of the Copernicus CLMS portfolio as well as national datasets by performing an **Ingestion**. Ingestion means to upload datasets to the system and make it available and usable for all users, a selected user group or only for the organization of the ingesting user. [Figure 3‑1](#_Ref100264360) provides a simplified overview of the Ingestion process. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image59.png){width="5.909722222222222in" height="5.972541557305337in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image59.png){width="5.909722222222222in" height="5.972541557305337in"} []{#_Ref100264360 .anchor}**Figure 3‑1: Simplified Ingestion workflow** @@ -628,7 +628,7 @@ The key steps required in the development of an Ingestion and Extraction are (se 11. Publish Extraction +------------------+-------------------------------------------------------------------------------------+ -| > **Ingestion** | ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image60.png){width="6.607769028871391in" height="3.0520833333333335in"} | +| > **Ingestion** | ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image60.png){width="6.607769028871391in" height="3.0520833333333335in"} | +------------------+ | | > **Extraction** | | +==================+=====================================================================================+ @@ -641,13 +641,13 @@ The key steps required in the development of an Ingestion and Extraction are (se Clicking the '**Add Ingestion**' button (section [1.6](#data-catalogue) [Figure 1‑9](#_Ref151467380)) opens the 'Add Ingestion' dialog (see [Figure 3‑3](#_Ref151987176)) where you can define the data format of your dataset (step 1). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image61.png){width="6.925in" height="3.852777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image61.png){width="6.925in" height="3.852777777777778in"} []{#_Ref151987176 .anchor}**Figure 3‑3: Add Ingestion - Step 1 (Data format) - here raster file** In a second step, further information, such as name and country / region that describe the data can be entered (step 2 see [Figure 3‑4](#_Ref151987203)). All **mandatory fields** are marked with a \*. In this example, we will upload the HRL Imperviousness (IMD) for Albania. Since we want to ingest the whole country, we do not specify a region. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image62.png){width="4.93673665791776in" height="3.1693733595800526in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image62.png){width="4.93673665791776in" height="3.1693733595800526in"} []{#_Ref151987203 .anchor}**Figure 3‑4: Add Ingestion - Step 2 (Parameter)** @@ -659,7 +659,7 @@ The data can be uploaded directly from a computer (file upload or per \`drag and In this example below, we chose the file upload from a local computer. By doing this, an attachment is added to the dialog. **In case the file size is larger than 5 GB, a warning appears recommending using an URL upload as the file upload might take a long time.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image64.png){width="4.338582677165355in" height="4.519685039370079in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image63.png){width="3.5188681102362205in" height="2.1646161417322833in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image64.png){width="4.338582677165355in" height="4.519685039370079in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image63.png){width="3.5188681102362205in" height="2.1646161417322833in"} []{#_Ref151987252 .anchor}**Figure 3‑5: Add Ingestion - Step 3 (Data upload via local computer)** @@ -667,15 +667,15 @@ In another example below (see [Figure 3‑7](#_Ref151987383)), we chose the URL **Note: please use a direct download URL (a link that automatically starts the download immediately). Consider that the system can only process links which do not require a user login.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image65.png){width="5.291666666666667in" height="5.9375in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image65.png){width="5.291666666666667in" height="5.9375in"} []{#_Ref151987332 .anchor}**Figure 3‑6: Add Ingestion - Step 3 (Data upload via URL)** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image66.png){width="5.926814304461942in" height="4.801718066491689in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image66.png){width="5.926814304461942in" height="4.801718066491689in"} []{#_Ref151987383 .anchor}**Figure 3‑7: Add Ingestion -Step 3 (Get download link via CLMS portal)** -> ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image67.JPG){width="4.811321084864392in" height="3.5814720034995626in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image68.JPG){width="4.792452974628172in" height="2.9253576115485562in"} +> ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image67.JPG){width="4.811321084864392in" height="3.5814720034995626in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image68.JPG){width="4.792452974628172in" height="2.9253576115485562in"} []{#_Ref151987407 .anchor}**Figure 3‑8: Add Ingestion - Step 3 (Get download link via the portal and via email)** @@ -693,7 +693,7 @@ Additionally, you can **enter a layer name** which shall be used to generate inp **Please make sure to avoid special characters, otherwise an error will occur.** Please also refer to section 3.3 to learn about the **limitations of data uploads**. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image69.png){width="4.147503280839895in" height="2.177729658792651in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image70.png){width="3.9302241907261593in" height="2.6924595363079615in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image69.png){width="4.147503280839895in" height="2.177729658792651in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image70.png){width="3.9302241907261593in" height="2.6924595363079615in"} []{#_Ref151987363 .anchor}**Figure 3‑9: Add Ingestion - Step 4 (exclude values and enter layer name)** @@ -707,11 +707,11 @@ The fifth step is optional and provides you with the possibility to upload **add Files can be uploaded via the explorer or per "drag and drop". These additional files will be used to prefill the data descriptions and define the EAGLE barcodes as well as the style for the Ingestion Classes (step 5). The upload of these documents can also be performed at a later stage (section [3.7](#edit-ingestion)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image73.JPG){width="3.2547167541557305in" height="3.5280533683289588in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image72.png){width="3.7945319335083116in" height="1.746836176727909in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image73.JPG){width="3.2547167541557305in" height="3.5280533683289588in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image72.png){width="3.7945319335083116in" height="1.746836176727909in"} []{#_Ref151987450 .anchor}**Figure 3‑10: Add Ingestion - Step 5 (upload additional datasets (i.e. EAGLE barcoding file))** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image73.JPG){width="3.6037740594925634in" height="3.906424978127734in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image74.png){width="2.991311242344707in" height="1.537652012248469in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image73.JPG){width="3.6037740594925634in" height="3.906424978127734in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image74.png){width="2.991311242344707in" height="1.537652012248469in"} []{#_Toc137576649 .anchor}**Figure 3‑11: Add Ingestion - Step 5 (upload additional datasets (i.e. Metadata file))** @@ -719,11 +719,11 @@ The last option allows you to specify whether the **raw data** (original/initial As soon as the processing step is finished, the raw data cannot be downloaded or reused anymore by anyone. Finally, if you have defined all upload parameters, the dataset can be added by pressing the 'ADD' button (see [Figure 3‑12](#_Ref151987498)). While the upload is performed, please do not leave the page (see [Figure 3‑13](#_Ref151987519)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image76.png){width="4.0806277340332455in" height="4.182929790026247in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image76.png){width="4.0806277340332455in" height="4.182929790026247in"} []{#_Ref151987519 .anchor}**Figure 3‑12: Add Ingestion - Step 6 (start the upload)** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image77.png){ width="3.573008530183727in" height="2.584806430446194in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image77.png){ width="3.573008530183727in" height="2.584806430446194in"} []{#_Ref151987498 .anchor}**Figure 3‑13: Add Ingestion - Step 6 (stay on page)** @@ -731,13 +731,13 @@ As soon as the processing step is finished, the raw data cannot be downloaded or Clicking the '**Add Ingestion**' button (see section [1.6](#data-catalogue) [Figure 1‑9](#_Ref151467380)) opens the 'Add Ingestion' dialog (see [Figure 3‑14](#_Ref151987694)) where you can define the data format of your dataset (step 1). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image78.png){width="6.925in" height="3.8180555555555555in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image78.png){width="6.925in" height="3.8180555555555555in"} []{#_Ref151987694 .anchor}**Figure 3‑14: Add Ingestion - Step 1 (Data format) - here vector file** In a second step, further information, such as name and country / region that describes the data can be entered (step 2 see [Figure 3‑15](#_Ref151987707)). All **mandatory fields** are marked with a \*. In this example, we will upload the Urban Atlas 2018 for Innsbruck. As we want to ingest the area of Innsbruck only in this example, we do specify Tyrol as region. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image79.png){width="4.013493000874891in" height="3.144948600174978in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image79.png){width="4.013493000874891in" height="3.144948600174978in"} []{#_Ref151987707 .anchor}**Figure 3‑15: Add Ingestion - Step 2 (Parameter)** @@ -753,7 +753,7 @@ The data can be uploaded directly from your computer (file upload or per \`drag In this example below (see [Figure 3‑16](#_Ref151987739)), we chose the file upload from a local computer. If successfully defined, an attachment is added to the dialog. **If the file size is larger than 5 GB, a warning appears recommending using an URL upload as the file upload might take a long time.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image80.png){width="4.726548556430446in" height="3.3500721784776903in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image80.png){width="4.726548556430446in" height="3.3500721784776903in"} []{#_Ref151987739 .anchor}**Figure 3‑16: Add Ingestion - Step 3 (Data upload via local computer)** @@ -761,17 +761,17 @@ In this example below (see [Figure 3‑17](#_Ref151987899)), we chose the URL up **Note: please use a direct download URL (link that automatically starts the download immediately). Consider that the system can only process links which do not require a user login.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image81.png){width="5.412512029746281in" height="3.109834864391951in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image81.png){width="5.412512029746281in" height="3.109834864391951in"} []{#_Ref151987899 .anchor}**Figure 3‑17: Add Ingestion - Step 3 (Data upload via URL)** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image82.jpeg){width="5.6799289151356085in" height="3.3181813210848645in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image83.jpeg){width="4.80394028871391in" height="4.340909886264217in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image82.jpeg){width="5.6799289151356085in" height="3.3181813210848645in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image83.jpeg){width="4.80394028871391in" height="4.340909886264217in"} []{#_Ref151987915 .anchor}**Figure 3‑18: Add Ingestion - Step 3 (Get download link via the portal and via email)** For the vector file, the Attribute Name from the dataset (column from the attribute table) which shall be used as Input Parameter for the Class Code needs to be entered (see [Figure 3‑16](#_Ref151987739) and [Figure 3‑17](#_Ref151987899)), for the raster dataset this is not required as raster dataset usually consists of one band only. Please select an integer field (the code and not its description). In general, strings also work as long as they do not have any special characters. Allowed: digits, upper-lower case, hyphen, underscore. In this case (see [Figure 3‑19](#_Ref151987951)), we chose 'code_2018'. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image84.png){ width="5.619794400699912in" height="3.06462489063867in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image84.png){ width="5.619794400699912in" height="3.06462489063867in"} []{#_Ref151987951 .anchor}**Figure 3‑19: Add Ingestion - Step 3 (Enter Attribute Name from the dataset (column from the attribute table) which shall be used as Input Parameter for the Class Code needs to be entered). Here: code_2018** @@ -785,22 +785,22 @@ Additionally, you can **enter a layer name** (see [Figure 3‑20](#_Ref151988050 **Please make sure to avoid special characters, otherwise an error will occur.** Please also refer to section 3.3 to learn about the **limitations of data uploads**. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image86.JPG){width="3.486956474190726in" height="3.637884951881015in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image85.png){width="3.513888888888889in" height="1.1036406386701663in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image86.JPG){width="3.486956474190726in" height="3.637884951881015in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image85.png){width="3.513888888888889in" height="1.1036406386701663in"} []{#_Ref151988050 .anchor}**Figure 3‑20: Add Ingestion - Step 4 (exclude values and enter layer name)** The fifth step provides the possibility to upload **additional, supporting files** that help to understand the content, such as the metadata files (see [Figure 3‑22](#_Ref151988218)), legend files (see [Figure 3‑21](#_Ref151988076)) QGIS layer style file (.qml) or SLD (Styled Layer Descriptor) file (.sld); ArcGIS Layer Files (.lyr) are not supported), EAGLE Barcoding files (see [Figure 3‑23](#_Ref151988308)). These additional files will be used prefill the data descriptions and define the EAGLE barcodes and the style to the Ingestion Classes (step 5). The upload of these documents can also be performed at a later stage (section [3.7](#edit-ingestion)) and is possible via the explorer or per "drag and drop". -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="3.991304680664917in" height="4.169222440944882in"} -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image87.png){width="3.777292213473316in" height="1.6791666666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="3.991304680664917in" height="4.169222440944882in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image87.png){width="3.777292213473316in" height="1.6791666666666667in"} []{#_Ref151988076 .anchor}**Figure 3‑21: Add Ingestion - Step 5 (upload additional datasets (i.e. legend / style file))** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="3.965217629046369in" height="4.141973972003499in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image89.png){width="3.2582983377077865in" height="1.4520833333333334in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="3.965217629046369in" height="4.141973972003499in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image89.png){width="3.2582983377077865in" height="1.4520833333333334in"} []{#_Ref151988218 .anchor}**Figure 3‑22: Add Ingestion - Step 5 (upload additional datasets (i.e. Metadata file))** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="4.311319991251094in" height="4.503503937007874in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image90.png){width="3.2121391076115486in" height="1.4in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image88.JPG){width="4.311319991251094in" height="4.503503937007874in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image90.png){width="3.2121391076115486in" height="1.4in"} []{#_Ref151988308 .anchor}**Figure 3‑23: Add Ingestion - Step 5 (upload additional datasets (i.e. EAGLE barcoding file))** @@ -808,7 +808,7 @@ The last option allows you to specify whether the **raw data** (original uploade As soon as the processing step is finished, the raw data cannot be downloaded or reused anymore by anyone. Finally, if you have everything defined, the dataset can be added by pressing the 'ADD' button (see [Figure 3‑24](#_Ref151988324)). While the upload is performed, please do not leave the page. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image91.png){width="4.204266185476816in" height="3.214753937007874in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image91.png){width="4.204266185476816in" height="3.214753937007874in"} []{#_Ref151988324 .anchor}**Figure 3‑24: Add Ingestion - Step 6 (start the upload)** @@ -826,11 +826,11 @@ In case your data is split into several sub-tiles, such as Urban Atlas or Ripari For datasets (i.e. gdb, gpkg) that consist of more than one layer (per file), you need to specify the layer name which shall be used to generate input classes in the field 'layer name'. If no specific file is defined, the first layer will be selected. In the example below we have three layers in the dataset we want to ingest. For selecting the first one, we can define 'AT005L3_INNSBRUCK_UA2018' under 'layer name' or we skip it as the first layer would be selected by default anyways. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image85.png){width="3.513888888888889in" height="1.1034722222222222in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image85.png){width="3.513888888888889in" height="1.1034722222222222in"} If your required layer is not on the first position of your folder/gdb/gpkg and in addition the layers of different regions are named differently (SAR_13_T_USOS vs. SAR_15_T_USOS), you have 2 possibilities to upload your data in the system: -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image92.png){width="2.9251498250218724in" height="1.568176946631671in"} ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image93.png){width="2.801619641294838in" height="1.5401607611548556in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image92.png){width="2.9251498250218724in" height="1.568176946631671in"} ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image93.png){width="2.801619641294838in" height="1.5401607611548556in"} - Extract the required layer from GDB / GPKG and merge data into one dataset in a GIS software **outside the system** (might be not possible due to the size) @@ -844,13 +844,13 @@ If you have tried to upload the dataset by mistake, you can delete the entry. Both options can be initiated by right clicking on the Ingestion for which the upload failed (see [Figure 3‑25](#_Ref151988719)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image95.png){width="6.925in" height="3.245138888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image95.png){width="6.925in" height="3.245138888888889in"} []{#_Ref151988719 .anchor}**Figure 3‑25: Add Ingestion -- Retry or delete dataset** Further there is also the possibility to 'cancel' and Ingestion while its uploading or processing (right click on the processing Ingestion see [Figure 3‑26](#_Ref151988796)), it will then run into an 'Uploading Error' or 'Processing Error' (see section [3.5](#status-of-an-ingestion)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image96.png){width="6.925in" height="3.251388888888889in"}[]{#_Ref151988796 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image96.png){width="6.925in" height="3.251388888888889in"}[]{#_Ref151988796 .anchor} **Figure 3‑26:Cancel Ingestion while uploading or processing** @@ -860,7 +860,7 @@ The **status** indicates the current process of the Ingestion or Extraction in t In the example below, you can see the different states of Ingestions in the Data Catalogue view (see [Figure 3‑27](#_Ref151989171)). Several are Used, one Published, one Draft, one Processing and four Ingestions are in status Ingested_Preview. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image97.png){width="6.925in" height="2.9854166666666666in"}[]{#_Ref151989171 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image97.png){width="6.925in" height="2.9854166666666666in"}[]{#_Ref151989171 .anchor} **Figure 3‑27: Example of different status of datasets in the CLC+ system** @@ -873,7 +873,7 @@ In the example below, you can see the different states of Ingestions in the Data +-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Uploading_Error | An error occurred while uploading the dataset. By clicking on the data catalogue entry, a pop-up window will help indicating the error. | | | | -| | ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image98.png){width="5.570138888888889in" height="2.6083333333333334in"} | +| | ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image98.png){width="5.570138888888889in" height="2.6083333333333334in"} | | | | | | - When ingesting a vector file, please check if the correct attribute value is selected | | | | @@ -887,7 +887,7 @@ In the example below, you can see the different states of Ingestions in the Data +-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Processing_Error | An error occurred while processing the dataset. By clicking on the data catalogue entry, a pop-up window will help indicating the error. | | | | -| | ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image99.png){width="5.570138888888889in" height="2.6625in"} | +| | ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image99.png){width="5.570138888888889in" height="2.6625in"} | | | | | | - Check if the provided upload link is valid. In case the link is valid, a download should start by clicking on it. If not, the download link might be expired (i.e. CLMS links expire after 24h) | | | | @@ -911,7 +911,7 @@ In the example below, you can see the different states of Ingestions in the Data | | | | | **Note: Once the Ingestion is published, other users can perform Extractions with the Ingestion, which changes the status to \"used\". In status USED, you can no longer make changes to the Ingestion.** | | | | -| | ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image100.png){width="2.5629604111986in" height="1.423902012248469in"} | +| | ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image100.png){width="2.5629604111986in" height="1.423902012248469in"} | +-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Used | The dataset is already used in an Extraction. **Now it is no longer possible to delete the dataset. The only further option is to archive the dataset.** | +-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -922,7 +922,7 @@ In the example below, you can see the different states of Ingestions in the Data The status of an Ingestion is also displayed in the detail view next to the Ingestion Name in the upper left corner (see [Figure 3‑28](#_Ref151989420)). The status of an Ingestion can be changed by triggering some actions. E.g. by adding the EAGLE barcodes and pressing preview for a small area, the status converts from 'draft' (see [Figure 3‑28](#_Ref151989420)) to 'ingested_preview'. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image101.png){width="6.925in" height="3.8201388888888888in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image101.png){width="6.925in" height="3.8201388888888888in"} []{#_Ref151989420 .anchor}**Figure 3‑28: From draft to ingested_preview (by adding EAGLE barcodes, Region and general information like reference year, time range and INSPIRE theme)** @@ -930,7 +930,7 @@ The status of an Ingestion is also displayed in the detail view next to the Inge **Input Classes** are representing detailed information about the Ingestion and originating from the uploaded dataset for each Ingestion. This also means that every Input Class is connected to an Ingestion. Input Classes contain the information on how to interpret the class code within the raster file and how they are mapped to the specific EAGLE barcodes (compliance to EAGLE, factor of EAGLE barcode value). Input Classes from the dataset layers are generated when adding a new Ingestion to the system (see section[3.23.2](#add-ingestion)). Furthermore, they are used when adding a new Extraction to the system in case they are selected (see section [4.2](#add-extraction)). In the example below (see [Figure 3‑29](#_Ref151640298)[Figure 3‑29](#_Ref151640298)) the Ingestion 'HRL Forest Type' has three input classes. Besides the class code the class name and the EAGLE barcodes per class are shown, as well as the colour code per class. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image2.jpg){width="0.27165354330708663in" height="0.27165354330708663in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image102.png){width="6.925in" height="3.801388888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image2.jpg){width="0.27165354330708663in" height="0.27165354330708663in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image102.png){width="6.925in" height="3.801388888888889in"} []{#_Ref151640298 .anchor}**Figure 3‑29: Example of Input Classes of the HRL Forest Type Ingestion** @@ -946,9 +946,9 @@ You can **edit your Ingestion** as often as you like, also after the status has In the left section (**General Information**), you can review all Ingestion information and edit them by clicking on the "**Edit**" button. Reference year, time range and [INSPIRE Themes](https://inspire.ec.europa.eu/Themes/Data-Specifications/2892) are mandatory fields. In case a metadata file has been uploaded during the Ingestion and the necessary data is available, this section will be prefilled already. Save the changes by clicking on the "Save" button. Before leaving the page without saving your edits the user will be reminded to save the edits, otherwise all edits will not be saved when returning to the page. Below the General Information the user can add **additional documents** like the EAGLE barcoding file per drag and drop or via uploading. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image103.png){width="3.4196456692913384in" height="6.002495625546807in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image103.png){width="3.4196456692913384in" height="6.002495625546807in"} -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image104.png){width="4.19990157480315in" height="2.5390004374453192in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image104.png){width="4.19990157480315in" height="2.5390004374453192in"} []{#_Toc137576666 .anchor}**Figure 3‑30: Edit Ingestion -- Ingestion settings and possibility to add additional documents** @@ -956,13 +956,13 @@ In the left section (**General Information**), you can review all Ingestion info It is obligatory to map all ingested classes as **EAGLE elements** in order to publish an Ingestion. It is recommended to upload the EAGLE barcoding file (a detailed description is provided in section 2.3) together with the data. You can do this already when defining the settings for the Ingestion (see section [3.2](#add-ingestion)) or by clicking on the EAGLE element picker. In case you use the picker, continue with step 3 below, otherwise you can skip this and continue with step 4. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image106.png){width="6.925in" height="3.8125in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image106.png){width="6.925in" height="3.8125in"} []{#_Ref98941497 .anchor}**Figure 3‑31: Edit Ingestion (step 3 is in [**Figure 3‑33**](#_Ref98941415))** Further if the EAGLE barcoding was already uploaded or done manually the number of used EAGLE elements per Input class is shown in the EAGLE elements column. For example, + 10 for class 11100 in the example below (see [Figure 3‑32](#_Ref152070629)) indicated that overall 11 EAGLE elements are barcoded for this Input class (first element is written in the column, the other 10 EAGLE elements are summarized as '+10'). By hovering over the EAGLE element column for an input class all EAGLE elements of this class including the applied barcoding is shown in the dark grey box (see [Figure 3‑32](#_Ref152070629)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image107.png){width="6.925in" height="5.73125in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image107.png){width="6.925in" height="5.73125in"} []{#_Ref152070629 .anchor}**Figure 3‑32: Summary of EAGLE elements per Input class** @@ -970,23 +970,23 @@ Even if it is recommended to upload the EAGLE barcoding file, the CLC+ Core syst Concerning the Help function, in the "Help- EAGLE Barcoding Manual" there is also a direct link (see [Figure 3‑34](#_Ref98941416)) to the [EAGLE homepage](https://land.copernicus.eu/en/eagle?tab=bar_coding), which opens then in a separate tab. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image108.png){width="6.925in" height="3.797222222222222in"}[]{#_Ref98941415 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image108.png){width="6.925in" height="3.797222222222222in"}[]{#_Ref98941415 .anchor} **Figure 3‑33: Mapping Input Classes to EAGLE elements - Select EAGLE elements** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image109.png){width="3.876061898512686in" height="2.059691601049869in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image110.png){width="3.1216032370953632in" height="1.6599825021872265in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image109.png){width="3.876061898512686in" height="2.059691601049869in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image110.png){width="3.1216032370953632in" height="1.6599825021872265in"} []{#_Ref98941416 .anchor}**Figure 3‑34: Mapping Input Classes to EAGLE elements -- Help windows for barcoding and factor** Classes that have been already excluded from the dataset (e.g. NoData) in the relevant steps before, will not be shown in the Input Classes section anymore (see section [3.2](#add-ingestion) "exclude class codes"). In case this has not been done yet, there is still the opportunity to hide (not exclude!!!) specified/single classes before finally ingesting the data. Therefore, just uncheck the 'eye' symbol at the end of the row of the respective class ([Figure 3‑35](#_Ref100162670)). Note that the hidden classes will appear as "0" in the Ingestion and not as NoData pixels. Hidden classes can be shown again even after publishing the Ingestion by unpublishing the Ingestion but only if the Ingestion is not in status "Used" yet. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image111.png){width="3.987040682414698in" height="2.0510750218722658in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image111.png){width="3.987040682414698in" height="2.0510750218722658in"} []{#_Ref100162670 .anchor}**Figure 3‑35: Uncheck 'eye' to prevent values / classes to be ingested.** Once all settings and Input Classes have been reviewed, you can start the Ingestion for a small area / region that lies within the boundary of the processed dataset by clicking on '**preview**' (see [Figure 3‑36](#_Ref152070767)). If the preview was successful, you can now inspect your Ingestion in the map and continue with step 6. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image112.png){ width="4.84594706911636in" height="1.9885094050743657in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image112.png){ width="4.84594706911636in" height="1.9885094050743657in"} []{#_Ref152070767 .anchor}**Figure 3‑36: Map preview** @@ -994,13 +994,13 @@ Now, you can '**Start the Ingestion**' for the full extent of your Ingestion (se The clock symbol allows to view the **Ingestion history** (see [Figure 3‑37](#_Ref98877006)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image115.png){width="6.925in" height="3.183333333333333in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image115.png){width="6.925in" height="3.183333333333333in"} []{#_Ref98877006 .anchor}**Figure 3‑37: History of Ingestion for one layer** Once an Ingestion is published (see next chapter) Input classes can either be shown all in the map preview by activating the "Show in Map" or be toggled on and off individually by selectin on Input class. Only the selected Input class will then be shown in the map preview like for example class "11210" in the example below (see [Figure 3‑38](#_Ref152248025)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image116.png){width="6.925in" height="5.055555555555555in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image116.png){width="6.925in" height="5.055555555555555in"} []{#_Ref152248025 .anchor}**Figure 3‑38: Show selected Input classes in the map of published Ingestions.** @@ -1010,7 +1010,7 @@ You can **publish an Ingestion** by clicking on the button 'publish' in the Inge **Note: Depending on what kind of visibility (private, public or national) you have chosen, the ingested data will then be available to either all users (public), to the country of the selected organisation (national), or only to users within your organisation (private). Consider, that other users might use your data for Extractions. As mentioned before, once your data has been used, it can no longer be deleted or edited while in use by either you or other users.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image117.png){width="6.925in" height="3.1277777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image117.png){width="6.925in" height="3.1277777777777778in"} []{#_Ref151639942 .anchor}Figure 3‑39: Publish Ingestion -- Select visibility (public or limited) @@ -1018,13 +1018,13 @@ You can **publish an Ingestion** by clicking on the button 'publish' in the Inge Further, you can **reuse** an Ingestion by right clicking on the Ingestion in the Data Catalogue a small windowsdialog with several options opens (see [Figure 3‑40](#_Ref151639877)). Here, the Add Ingestion dialog opens again (see [Figure 3‑41](#_Ref151639902)), with all the fields containing the previous information entered such as name, region, excluded values (section[3.2](#add-ingestion)). Please note that by reusing an Ingestion the original raw data will not be available anymore. Also, in case the "delete raw data" was not ticked for the reused Ingestion the raw data is not accessible and reusable anymore. The data needs to be uploaded as a file or via ULR again. Only the information entered to the Ingestion before will be already filled in when reusing an Ingestion. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image118.png){width="0.4618055555555556in" height="0.5277777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image118.png){width="0.4618055555555556in" height="0.5277777777777778in"} -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image119.png){width="6.925in" height="3.1083333333333334in"}[]{#_Ref151639877 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image119.png){width="6.925in" height="3.1083333333333334in"}[]{#_Ref151639877 .anchor} **Figure 3‑40: Reuse Ingestion** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image120.png){width="6.925in" height="3.379166666666667in"}[]{#_Ref151639902 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image120.png){width="6.925in" height="3.379166666666667in"}[]{#_Ref151639902 .anchor} **Figure 3‑41: Reuse Ingestion -- detailed view** @@ -1032,7 +1032,7 @@ Further, you can **reuse** an Ingestion by right clicking on the Ingestion in th An **Extraction** will create new and independent data products that can be used to generate Extractions for future CLC+ instances by selecting Input Classes from available Ingestions in the CLC+ Core (section [3.6](#input-classes)), define Class Conditions (section [4.5.1](#some-definitions-for-a-better-understanding-also-see-glossary)) extracting the required information and thus, create new Output Classes (section [4.5](#output-classes)), reuse an already available Extraction (section [4.9](#reuse-extraction)) or delete an Extraction (section [4.10](#delete-extraction)). To make the new Extraction available for all or selected users in CLC+ Core, execute the Extraction, review and validate the Extraction results and publish it (section [4.8](#publish-extraction-and-download-result)). [Figure 4‑1](#_Ref100264486) provides a simplified overview of the Extraction process. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image121.png){width="5.734752843394576in" height="4.506944444444445in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image121.png){width="5.734752843394576in" height="4.506944444444445in"} []{#_Ref100264486 .anchor}**Figure 4‑1: Simplified Extraction workflow.** @@ -1057,9 +1057,9 @@ The **status** indicates the current process of the Ingestion or Extraction in t : []{#_Ref153954038 .anchor}Table 4‑1: Status of Extraction datasets -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image122.png){width="4.576922572178478in" height="1.0229855643044619in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image122.png){width="4.576922572178478in" height="1.0229855643044619in"} -![Graphical user interface, website Description automatically generated](./CLC+Core_User_Manual_Issue_4.0_v1-media/image123.png){width="5.554351487314086in" height="2.6134186351706035in"} +![Graphical user interface, website Description automatically generated](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image123.png){width="5.554351487314086in" height="2.6134186351706035in"} ## Add Extraction @@ -1067,15 +1067,15 @@ Clicking the '**Add Extraction'** button (section [4.2](#add-extraction)) opens By clicking on 'ADD', you will be forwarded to the 'Edit Extraction' view ([Figure 4‑3](#_Ref153438205), section [4.3](#edit-extraction)). Further, a new entry in the Data Catalogue table was created with status 'Draft' ([Figure 4‑4](#_Ref100140139)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image124.png){width="6.925in" height="3.3465277777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image124.png){width="6.925in" height="3.3465277777777778in"} []{#_Ref153438205 .anchor}**Figure 4‑2: Add Extraction -- Add Extraction Dialog.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image125.png){width="6.925in" height="3.2958333333333334in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image125.png){width="6.925in" height="3.2958333333333334in"} []{#_Ref100140157 .anchor}**Figure 4‑3: Add Extraction -- Edit Extraction View.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image126.png){width="6.925in" height="1.4375in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image126.png){width="6.925in" height="1.4375in"} []{#_Ref100140139 .anchor}**Figure 4‑4: Add Extraction -- A new entry in the table was created with status 'draft'.** @@ -1084,31 +1084,31 @@ By clicking on 'ADD', you will be forwarded to the 'Edit Extraction' view ([Figu Before an Extraction can be published you need to set the Extraction settings, select the specific Input Classes and create Output Classes with the help of Extraction rules. To prevent mistakes, you can preview your results within a specific NUTS region in a Map Viewer. This view is very similar to the Edit Ingestion (section [3.7](#edit-ingestion)) one. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image127.png){width="6.925in" height="3.2715277777777776in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image127.png){width="6.925in" height="3.2715277777777776in"} []{#_Ref153953950 .anchor}**Figure 4‑5: Edit Extraction.** In the left section (**General Information**) (see [Figure 4‑5](#_Ref153953950) and [Figure 4‑6](#_Ref153953951)) you can review all Extraction settings and update them if necessary. Reference year, Time range and [INSPIRE Themes](https://inspire.ec.europa.eu/Themes/Data-Specifications/2892) are mandatory. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image128.png){width="2.9580260279965005in" height="4.066681977252843in"} ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image129.png){width="2.9644499125109363in" height="4.034543963254593in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image128.png){width="2.9580260279965005in" height="4.066681977252843in"} ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image129.png){width="2.9644499125109363in" height="4.034543963254593in"} []{#_Ref153953951 .anchor}**Figure 4‑6: Edit Extraction - Review all Extraction settings and update them if necessary. Reference year, Time range and INSPIRE Themes are mandatory.** Further, users are able to upload additional (already existing) datasets such as EAGLE matrix or style files (CLR, QML) or metadata information (txt, xml) ([Figure 4‑7](#_Ref153644917)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image130.png){width="3.4574409448818897in" height="1.8518011811023622in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image130.png){width="3.4574409448818897in" height="1.8518011811023622in"} []{#_Ref153644917 .anchor}**Figure 4‑7: Upload of additional datasets such as EAGLE matrix or style files.** -In the next step, you need to **define the Input Classes** you want to use for your Extraction. By clicking on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon, in the area "**Input Classes**" you can **add Input Classes** which are already ingested into CLC+ Core (see [Figure 4‑8](#_Ref153954099)). The **"Select Input Classes"** menu opens and the dataset can be selected by checking the tick box. By clicking on the **"Confirm Selection"** button, the data will be taken into the Extraction view. Details about this step can be found at section [4.4 Add Input Classes to Extraction](#add-input-classes-to-extraction). +In the next step, you need to **define the Input Classes** you want to use for your Extraction. By clicking on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon, in the area "**Input Classes**" you can **add Input Classes** which are already ingested into CLC+ Core (see [Figure 4‑8](#_Ref153954099)). The **"Select Input Classes"** menu opens and the dataset can be selected by checking the tick box. By clicking on the **"Confirm Selection"** button, the data will be taken into the Extraction view. Details about this step can be found at section [4.4 Add Input Classes to Extraction](#add-input-classes-to-extraction). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image132.png){width="6.1026388888888885in" height="1.69875in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image132.png){width="6.1026388888888885in" height="1.69875in"} []{#_Ref153954099 .anchor}**Figure 4‑8: Add or delete Input Classes.** -As a next step you need to create Output Classes and define Class Conditions for them. Creating new Output Classes is possible by clicking on in the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon in the area "**Output Classes**" (see [Figure 4‑9](#_Ref105168124)). Once you have triggered this action, a new and Output Class will be added and you have to define the specific attributes such as the class code, name and the Class Condition (ruleset) ([Figure 4‑9](#_Ref105168124)). Further, you can specify a class colour and if you want to have this Extraction displayed in the Map preview or not. The class code is the value you assign to an Output Class, the name should be class descriptive (i.e. class 1 -- woodland stands, 2 -- unmanaged woodland, etc.). +As a next step you need to create Output Classes and define Class Conditions for them. Creating new Output Classes is possible by clicking on in the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon in the area "**Output Classes**" (see [Figure 4‑9](#_Ref105168124)). Once you have triggered this action, a new and Output Class will be added and you have to define the specific attributes such as the class code, name and the Class Condition (ruleset) ([Figure 4‑9](#_Ref105168124)). Further, you can specify a class colour and if you want to have this Extraction displayed in the Map preview or not. The class code is the value you assign to an Output Class, the name should be class descriptive (i.e. class 1 -- woodland stands, 2 -- unmanaged woodland, etc.). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image133.png){width="6.355581802274716in" height="1.7584284776902888in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image133.png){width="6.355581802274716in" height="1.7584284776902888in"} []{#_Ref105168124 .anchor}**Figure 4‑9: Add or delete Output Classes.** @@ -1120,49 +1120,49 @@ Once all settings and the test result have been reviewed you can start the Extra **After starting the Extraction, a pop-up window will appear asking if you really want to proceed as the Extraction may take a while. Further, it is indicating that EAGLE elements are used within the rules that are not corresponding to the available Input Classes. Please check if the correct EAGLE element and the correct barcode value is applied! The warning can be ignored but may affect the result!** (see [Figure 4‑10](#_Ref153954681)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image134.png){width="6.565197944006999in" height="3.266139545056868in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image134.png){width="6.565197944006999in" height="3.266139545056868in"} []{#_Ref153954681 .anchor}**Figure 4‑10: Pop up window asking to proceed. Indicating that EAGLE elements are used within the rules that are not corresponding to the available Input Classes.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image135.png){ width="6.925in" height="3.286111111111111in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image135.png){ width="6.925in" height="3.286111111111111in"} []{#_Ref153651792 .anchor}**Figure 4‑11: After starting the Extraction process.** ## Add Input Classes to Extraction -After you clicked on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon within the area "**Input Classes**" the **"Select Input Classes"** menu opens. You can select which are already ingested into CLC+ Core and that you want to use for your Extraction by checking the tick box. You can multi-select (more than one possible) Input Classes and also see information about them within the table. Use the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image136.png){width="0.4027777777777778in" height="0.17844597550306213in"} icon to add or remove columns for data information such as Name, Created at/by, Reference Year, EAGLE comliance, etc ([Figure 4‑12](#_Ref153650700)). +After you clicked on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon within the area "**Input Classes**" the **"Select Input Classes"** menu opens. You can select which are already ingested into CLC+ Core and that you want to use for your Extraction by checking the tick box. You can multi-select (more than one possible) Input Classes and also see information about them within the table. Use the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image136.png){width="0.4027777777777778in" height="0.17844597550306213in"} icon to add or remove columns for data information such as Name, Created at/by, Reference Year, EAGLE comliance, etc ([Figure 4‑12](#_Ref153650700)). Additionally, you have the possibility to **search** for specific Input Classes using the search field and the filter panel. In the filter panel ([Figure 4‑13](#_Ref153649503)) you can sear for data matching your criteria. Further, there is an option to toggle on/off "100 EAGLE compliant" or "EAGLE approved". The list on the right is updated accordingly. Further, you can reduce the list of data to data, ingested only by your or your organisation ([Figure 4‑12](#_Ref153650700)). -By hovering the mouse over the EAGLE elements column, a tooltip dialog opens, displaying all barcoded EAGLE elements for this Input Class ([Figure 4‑14](#_Ref153650770)). The EAGLE barcoding can be opened in a new tab to be inspected in more detail by clicking on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image137icon.png){width="0.1736111111111111in" height="0.1736111111111111in"} icon ([Figure 4‑15](#_Ref153650763)). +By hovering the mouse over the EAGLE elements column, a tooltip dialog opens, displaying all barcoded EAGLE elements for this Input Class ([Figure 4‑14](#_Ref153650770)). The EAGLE barcoding can be opened in a new tab to be inspected in more detail by clicking on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137icon.png){width="0.1736111111111111in" height="0.1736111111111111in"} icon ([Figure 4‑15](#_Ref153650763)). In the last step you click on the **"Confirm Selection"** button in order to apply them. The data will be taken into the Extraction view ([Figure 4‑12](#_Ref153650700)). -Back in the Extraction view, the selected data can be seen ([Figure 4‑16](#_Ref105172435)). By clicking on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon at the end of the Input Classes, you are able to add more classes and of course you can delete classes from your current selection by clicking on the delete symbol ([Figure 4‑17](#_Ref105172428)). Same as in the "Select Input Classes" View, hovering your mouse over the EAGLE elements column, a tooltip dialog opens, displaying all barcoded EAGLE elements for this Input Class ([Figure 4‑17](#_Ref105172428)). The EAGLE barcoding can be opened in a new tab to be inspected in more detail by clicking on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image137icon.png){width="0.1736111111111111in" height="0.1736111111111111in"} icon. +Back in the Extraction view, the selected data can be seen ([Figure 4‑16](#_Ref105172435)). By clicking on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon at the end of the Input Classes, you are able to add more classes and of course you can delete classes from your current selection by clicking on the delete symbol ([Figure 4‑17](#_Ref105172428)). Same as in the "Select Input Classes" View, hovering your mouse over the EAGLE elements column, a tooltip dialog opens, displaying all barcoded EAGLE elements for this Input Class ([Figure 4‑17](#_Ref105172428)). The EAGLE barcoding can be opened in a new tab to be inspected in more detail by clicking on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137icon.png){width="0.1736111111111111in" height="0.1736111111111111in"} icon. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image138.png){width="6.925in" height="3.285416666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image138.png){width="6.925in" height="3.285416666666667in"} []{#_Ref153650700 .anchor}**Figure 4‑12: Add Input Classes to Extraction -- selection of classes.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image139.png){width="6.925in" height="3.451388888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image139.png){width="6.925in" height="3.451388888888889in"} []{#_Ref153649503 .anchor}**Figure 4‑13: Add Input Classes to Extraction -- filter panel.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image137.png){width="6.729166666666667in" height="3.2083333333333335in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image137.png){width="6.729166666666667in" height="3.2083333333333335in"} []{#_Ref153650770 .anchor}**Figure 4‑14: Add Input Classes to Extraction - EAGLE elements with tooltip dialog.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image140.png){ width="6.925in" height="3.327777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image140.png){ width="6.925in" height="3.327777777777778in"} []{#_Ref153650763 .anchor}**Figure 4‑15: Add Input Classes to Extraction - EAGLE barcoding opened in new window (here for Input Class "dry pulses").** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image141.png){ width="6.925in" height="2.9402777777777778in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image141.png){ width="6.925in" height="2.9402777777777778in"} []{#_Ref105172435 .anchor}**Figure 4‑16: Add Input Classes to Extraction -- back in Edit Extraction view with the newly added Input Classes.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image142.png){width="6.715277777777778in" height="3.2222222222222223in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image142.png){width="6.715277777777778in" height="3.2222222222222223in"} []{#_Ref105172428 .anchor}**Figure 4‑17: Add or delete Input Classes in the Extraction view and the EAGLE elements shown in the tooltip dialog.** @@ -1190,7 +1190,7 @@ The **Class Condition** specifies whether the Extraction Output Class to which i ### Create Output Classes -After you clicked on the ![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon within the area "**Output Classes**" a new entry will be added. First, you have to define a name (here: FL Transitional woodland) and Rule Class Code (here: 1) for the new Output Class. The Class Code is automatically filled by the system, starting at 1, but could be adapted to your needs ([Figure 4‑18](#_Ref153806764)). +After you clicked on the ![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image131.png){width="0.16875in" height="0.16875in"} icon within the area "**Output Classes**" a new entry will be added. First, you have to define a name (here: FL Transitional woodland) and Rule Class Code (here: 1) for the new Output Class. The Class Code is automatically filled by the system, starting at 1, but could be adapted to your needs ([Figure 4‑18](#_Ref153806764)). The Output Classes are ranked according to their order. So, it is following hierarchical processing (from first to last). That means that the CLC+ Core System always favours the classes with a smaller order number. If a pixel is then assigned to an Output Class, it cannot be assigned to another class even if the coverage for this other class is higher. There is also the possibility to change the order of the Output Classes by Drag & Drop. @@ -1200,7 +1200,7 @@ Same as for the Input Classes, you are able to add further Output Classes or del After you have clicked on the Class Condition of a specific Output Class ([Figure 4‑18](#_Ref153806764)), a new window opens (Query Builder, [Figure 4‑19](#_Ref153808348)) and you can start creating or editing it (see section [4.5.3 Create Class Conditions/Rulesets](#create-class-conditionsrulesets)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image143.png){width="6.228293963254593in" height="1.449423665791776in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image143.png){width="6.228293963254593in" height="1.449423665791776in"} []{#_Ref153806764 .anchor}**Figure 4‑18: Create new Output Class and other options.** @@ -1208,7 +1208,7 @@ After you have clicked on the Class Condition of a specific Output Class ([Figur [Figure 4‑19](#_Ref153808348) shows an overview of the Query Builder with all its options and functions which are explained in more details in this section. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image147.png){width="6.925in" height="3.3368055555555554in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image147.png){width="6.925in" height="3.3368055555555554in"} []{#_Ref153808348 .anchor}**Figure 4‑19: Query Builder with all its options and functions.** @@ -1220,21 +1220,21 @@ Example: For the Extraction of the deciduous forest class, I add two Rulesets, o Of course, there is the possibility to delete Rules or Rulesets. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image148.png){width="6.484667541557306in" height="3.1480424321959757in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image148.png){width="6.484667541557306in" height="3.1480424321959757in"} []{#_Ref153873991 .anchor}**Figure 4‑20: Create new Rule for an Output Class -- Query Builder** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image149.png){width="6.562167541557305in" height="3.1435487751531057in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image149.png){width="6.562167541557305in" height="3.1435487751531057in"} []{#_Ref153875245 .anchor}**Figure 4‑21: Create new Class Condition for Output Class "Deciduous Forest".** In the next steps, select the required EAGLE elements from the Query Builder ([Figure 4‑22](#_Ref153876094)). The prefered option is to select elements from the drop down menu but you can also write in the text box. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image150.png){width="6.533227252843394in" height="3.158512685914261in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image150.png){width="6.533227252843394in" height="3.158512685914261in"} []{#_Ref153876094 .anchor}**Figure 4‑22: Select EAGLE elements in the Query Builder.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image151.png){width="6.580074365704287in" height="3.1653248031496064in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image151.png){width="6.580074365704287in" height="3.1653248031496064in"} []{#_Ref153881096 .anchor}**Figure 4‑23: Select EAGLE elements in the Query Builder. Information that LCH-8_1_3 is in the list of EAGLE elements but does not occur in one of the Input Classes.** @@ -1242,13 +1242,13 @@ Next, select the barcode value from a drop-down list. There is also the option t **Multi-selected barcodes are OR-connected. That means, that a rule with multiple barcodes can be written as well as an OR-connected ruleset containing an individual rule for each of the barcodes. The multi-selection is only possible if an EAGLE Element is compared to a value but not if two EAGLE Elements are compared (icon-toggle on the right).** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image152.png){width="6.580279965004374in" height="3.1680621172353454in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image152.png){width="6.580279965004374in" height="3.1680621172353454in"} []{#_Ref153876076 .anchor}**Figure 4‑24: Select the barcode value from a drop-down list in the Query Builder.** Then the comparison operators need to be selected from a drop-down list ([Figure 4‑25](#_Ref153876064)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image153.png){width="6.5305369641294835in" height="3.1611417322834647in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image153.png){width="6.5305369641294835in" height="3.1611417322834647in"} []{#_Ref153876064 .anchor}**Figure 4‑25: Select the comparison operators in the Query Builder.** @@ -1258,19 +1258,19 @@ The last step is setting the percentage coverage of the aggregated value. Subsequently, add other EAGLE elements to complete the Ruleset. Clicking on "**ADD**" will save the Class Condition (see [Figure 4‑26](#_Ref153876041)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image155.png){width="6.5090485564304466in" height="3.1657524059492563in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image155.png){width="6.5090485564304466in" height="3.1657524059492563in"} []{#_Ref153876041 .anchor}**Figure 4‑26: Class Condition for Output Class "Deciduous Forest" set up in the Query Builder.** You also have the option to add comments to your Class Conditions (see [Figure 4‑27](#_Ref153958528)). Especially, if the Rulesets are getting more complex, the commenting function might be very helpful. You can use it to document your intentions because due to the usage of the EAGLE elements, the connection to the Ingestions and/or Input Classes gets lost or difficult to keep track. There is of course also the possibility to delete the comments. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image156.png){width="6.506107830271216in" height="3.1349628171478567in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image156.png){width="6.506107830271216in" height="3.1349628171478567in"} []{#_Ref153958528 .anchor}**Figure 4‑27: Add comments to the Rulesets.** If you are familiar with query language, you are also able to use the "Text field". In [Figure 4‑28](#_Ref105174879), you can see the Class Condition and its rules in an **expression language** in the Text tab. If you have added a comment, this is also shown here. If you want to reuse a created Class Condition or parts of it in a different class, copy the respective text and paste it in a different Output Classes Class Condition text editor. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image157.png){width="6.461420603674541in" height="1.7926017060367454in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image157.png){width="6.461420603674541in" height="1.7926017060367454in"} []{#_Ref105174879 .anchor}**Figure 4‑28: Class Condition in expression language.** @@ -1278,7 +1278,7 @@ Further, there are two information boxes at the top right. By clicking on "Compu You need to select either of the three options which might fit best to your requirements. Highest Coverage is the default and is recommended. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image158.png){width="6.565692257217847in" height="3.150505249343832in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image158.png){width="6.565692257217847in" height="3.150505249343832in"} []{#_Ref153880313 .anchor}**Figure 4‑29: Computational Manual.** @@ -1348,7 +1348,7 @@ Using the EAGLE elements information box will list all the relevant EAGLE elemen This will help users to avoid errors and get a better overview and understanding of the used EAGLE elements. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image159.png){width="6.520193569553806in" height="3.1430577427821524in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image159.png){width="6.520193569553806in" height="3.1430577427821524in"} []{#_Ref153880277 .anchor}**Figure 4‑30: EAGLE elements.** @@ -1364,15 +1364,15 @@ The used Input Classes in the section below ([Figure 4‑31](#_Ref153652241)). F Further, you can **download** the dataset (geotiff) and the metadata (geojson) to be able to inspect and validate your data in more detail in a GIS program on your local computer ([Figure 4‑31](#_Ref153652241)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image160.png){width="6.504597550306212in" height="3.1074912510936135in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image160.png){width="6.504597550306212in" height="3.1074912510936135in"} []{#_Ref153652241 .anchor}**Figure 4‑31: Preview Extraction and download result.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image161.png){width="6.247557961504812in" height="2.868162729658793in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image162.png){width="6.318649387576553in" height="2.8615146544181975in"}![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image163.png){width="6.576442475940508in" height="3.0006824146981628in"}[]{#_Ref153972958 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image161.png){width="6.247557961504812in" height="2.868162729658793in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image162.png){width="6.318649387576553in" height="2.8615146544181975in"}![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image163.png){width="6.576442475940508in" height="3.0006824146981628in"}[]{#_Ref153972958 .anchor} **Figure 4‑32: Output Class extraction information.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image164.png){width="6.636077209098863in" height="3.007263779527559in"}[]{#_Ref153972533 .anchor} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image164.png){width="6.636077209098863in" height="3.007263779527559in"}[]{#_Ref153972533 .anchor} **Figure 4‑33: Input Class extraction information.** @@ -1382,7 +1382,7 @@ You can publish an Extraction by clicking on the '**publish**' button in the det Further, you can download the dataset (geotiff) and the metadata (geojson) to be able to inspect your data in more detail in a GIS program on your local computer ([Figure 4‑34](#_Ref153652068)). -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image166.png){width="6.779166666666667in" height="3.2291666666666665in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image166.png){width="6.779166666666667in" height="3.2291666666666665in"} []{#_Ref153652068 .anchor}**Figure 4‑34: Publish Extraction and download result.** @@ -1390,11 +1390,11 @@ Further, you can download the dataset (geotiff) and the metadata (geojson) to be Further, you can **reuse** an Extraction. By right clicking on the Extraction in the Data Catalogue, a small window with several options opens (see [Figure 4‑35](#_Ref153652480)). Here, the Add Extraction dialog opens again, with all the fields containing the previous information entered such as name, country, region (see [Figure 4‑36](#_Ref153652678)). This is only true, if the user does share the same organisation with the entry or is a USER_ADMIN. Otherwise, the entry will either way is not visible to the user. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image167.png){width="6.729166666666667in" height="3.201388888888889in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image167.png){width="6.729166666666667in" height="3.201388888888889in"} []{#_Ref153652480 .anchor}**Figure 4‑35: Reuse Extraction.** -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image168.png){width="6.925in" height="3.872916666666667in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image168.png){width="6.925in" height="3.872916666666667in"} []{#_Ref153652678 .anchor}**Figure 4‑36: Reuse Extraction -- detailed view.** @@ -1402,7 +1402,7 @@ Further, you can **reuse** an Extraction. By right clicking on the Extraction in Further, you can **delete** an Extraction. By right clicking on the Extraction in the Data Catalogue, a small window with several options opens (see [Figure 4‑35](#_Ref153652480)). By clicking on "**Delete**", a pop-up window prevents you from accidentally deleting a dataset (see [Figure 4‑37](#_Ref153956701)). By clicking Delete in the window, the dataset will be ultimately removed from the data catalogue. This is only true, if the user does share the same organisation with the entry or is a USER_ADMIN. Otherwise, the entry will either way is not visible to the user. -![](./CLC+Core_User_Manual_Issue_4.0_v1-media/image169.png){width="2.9652777777777777in" height="1.4246533245844268in"} +![](./CLCplus_Core_User_Manual_Issue_4.0_v1-media/image169.png){width="2.9652777777777777in" height="1.4246533245844268in"} []{#_Ref153956701 .anchor}**Figure 4‑37: Delete Extraction** diff --git a/DOCS/clcplus-core/LICENSE.md b/DOCS/CLCplus_Core/LICENSE.md similarity index 100% rename from DOCS/clcplus-core/LICENSE.md rename to DOCS/CLCplus_Core/LICENSE.md