124
Framework Service. Lot 4: technical support for INSPIRE implementation EEA/SES/12/003/Lot 4 Conceptual data model design based on the INSPIRE specifications for the reporting of the Common Database on Designated Areas (CDDA) Description of Processes, Tools, and Deliverables Prepared by / compiled by:

WISE Technical Report - file · Web viewWISE Technical Report -

  • Upload
    leanh

  • View
    240

  • Download
    0

Embed Size (px)

Citation preview

Page 1: WISE Technical Report -    file · Web viewWISE Technical Report -

Framework Service. Lot 4: technical support for INSPIRE implementation

EEA/SES/12/003/Lot 4

Conceptual data model design based on the INSPIRE specifications for the reporting of the

Common Database on Designated Areas (CDDA)

Description of Processes, Tools, and Deliverables

Prepared by / compiled by: Organisation:

Tracasa

EEA project manager: Darja Lihteneger

Page 2: WISE Technical Report -    file · Web viewWISE Technical Report -

Identification

Project short title CDDA Reporting in conformity with INSPIRE

Project step Task 1-2-3-4 – Data Model creation and Data Transformation

Specific topic Description of Processes, Tools, and Deliverables

Deliverable number D4.1-TechnicalReport

Version/Status Final

Version history

Version

Date Author Status and description Distribution

0.1 12/01/2016 Tracasa TOC To EEA

0.2 25/01/2016 Tracasa Includes the comments from EEA and additional descriptions

To EEA and project team

1.0 24/02/2016 Tracasa Final Deliverable To EEA

2 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 3: WISE Technical Report -    file · Web viewWISE Technical Report -

Table of contents1 Executive Summary.................................................................................................6

2 Overview...................................................................................................................72.1 Normative references.................................................................................................72.2 Reference material.....................................................................................................72.3 General definitions.....................................................................................................72.4 Symbols and abbreviations........................................................................................8

3 Scope......................................................................................................................103.1 Informative view on a broader scope of the proposed activities..............................103.2 Specific project 2015 - 2016.....................................................................................113.3 Expected outcomes..................................................................................................12

4 Description of the processes................................................................................134.1 Developing the new conceptual data model for CDDA............................................13

4.1.1 CDDA Reporting.........................................................................................144.1.2 Designation types.......................................................................................17

4.2 Developing the new CDDA GML schemas..............................................................174.3 Developing the matching tables and descriptive mapping rules for the data

transformation..........................................................................................................184.3.1 Matching Tables adaptation.......................................................................184.3.2 Mapping Rules preparation........................................................................19

4.4 Transformation and validation of the selected data.................................................194.4.1 Transformation...........................................................................................204.4.2 Validation proof...........................................................................................21

5 Description of the Tools........................................................................................225.1 Enterprise Architect..................................................................................................225.2 ShapeChange..........................................................................................................265.3 MS Excel File...........................................................................................................275.4 HALE........................................................................................................................275.5 Oxygen.....................................................................................................................285.6 Other tools................................................................................................................29

5.6.1 QGIS...........................................................................................................295.6.2 Schematron................................................................................................30

6 Description of the Deliverables............................................................................316.1 UML data model.......................................................................................................316.2 Feature Catalogue...................................................................................................316.3 GML Schema...........................................................................................................326.4 Configuration file: ShapeChange.............................................................................336.5 Constraints in UML data model and Schematron rules...........................................336.6 Matching Table and Mapping Rules.........................................................................34

Page 4: WISE Technical Report -    file · Web viewWISE Technical Report -

6.7 Input source data for data transformation................................................................346.7.1 CDDA reporting information using shapefile + Access database...............346.7.2 CDDA information from EEA database using SpatiaLite............................366.7.3 Designations information from CDDA database using Excel file as input

data............................................................................................................366.8 Configuration file: HALE alignment project..............................................................376.9 GML Files.................................................................................................................38

6.9.1 CDDA reporting..........................................................................................386.9.2 Designation Type........................................................................................39

6.10 Validation proof........................................................................................................40

Annexes................................................................................................................................41ANNEX 1. UML data model.........................................................................................42ANNEX 2. Feature Catalogue.....................................................................................45ANNEX 3. GML schema..............................................................................................56ANNEX 4. Configuration file: ShapeChange...............................................................60ANNEX 5. Constraints and Schematron rules.............................................................61ANNEX 6. Matching Tables.........................................................................................68ANNEX 7. Input source data.......................................................................................71ANNEX 8. HALE alignment project.............................................................................74ANNEX 9. GML file......................................................................................................88ANNEX 10. Validation of GML file.................................................................................90

4 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 5: WISE Technical Report -    file · Web viewWISE Technical Report -

List of FiguresFigure 4.1 Summary of the process followed, deliverables produced and tools used...........................13Figure 4.2 Mandatory attributes for CddaReporting.............................................................................15Figure 4.3 Extension of INSPIRE DesignationValue code list.............................................................16Figure 4.4 Schema Input-Output Shape change....................................................................................18Figure 4.5 Example: Protected Sites GML in a GIS viewer..................................................................21Figure 5.1 Connection with the EEA Subversion repository................................................................22Figure 5.2 Project configuration in EA..................................................................................................23Figure 5.3 Importing and sharing INSPIRE data models......................................................................24Figure 5.4 Version Control configuration.............................................................................................24Figure 5.5 Importing UML profile in EA..............................................................................................25Figure 5.6 Search Type option in EA....................................................................................................25Figure 5.7 Adding classes from other packages....................................................................................26Figure 5.8 HALE alignment..................................................................................................................28Figure 5.9 Example using Oxygen........................................................................................................29Figure 5.10 Example of visualization in QGIS.....................................................................................29Figure 6.1 CDDA reporting data...........................................................................................................35Figure 6.2 CDDA reporting data for designation boundaries................................................................35Figure 6.3 EEA-CDDA spatiaLite database..........................................................................................36Figure 6.4 Designation information from CDDA reported information...............................................37Figure 6.5 Example: HALE alignment file............................................................................................37

List of TablesTable 3.1 Proposed activities related to e-Reporting and INSPIRE......................................................11Table 3.2 Project phases, processes, tools and deliverables..................................................................12Table 4.1 Example: encoding designation for CddaReporting..............................................................20Table 6.1 Proof of validation.................................................................................................................40

Page 6: WISE Technical Report -    file · Web viewWISE Technical Report -

1 Executive SummaryInside the Framework Service Contract EEA/SES/12/003/Lot 4: technical support for INSPIRE implementation, the general project focuses on “Conceptual data model based on the INSPIRE specifications for the reporting of the CDDA” and more specifically the current work evaluates the current data model of the CDDA and how to individuate in two separate models: one for the sites (following INSPIRE principles) and one for designations (following ISO concepts).

This document is intended to be a guide that demonstrates how it is possible to integrate an own data model with the INSPIRE specifications so that the specific objectives of the source data could be reached while data comply with the INSPIRE Directive.

The document describes the processes and the tools used for the generation of the extended data models according to INSPIRE Protected Sites data specifications following INSPIRE principles and adapted to the requirements of CDDA reporting; and the new designations’ data model. The deliverables produced are also described in the present report.

6 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 7: WISE Technical Report -    file · Web viewWISE Technical Report -

2 Overview

2.1 Normative references

Directive 2007/2/EC of the European Parliament and of the Council of 14 March 20071

Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services2 and the amendmentsINSPIRE DS-D2.5, Generic Conceptual Model, v3.43

D2.8.II/III.7 Data Specification on Environmental Monitoring Facilities – Technical Guidelines4

INSPIRE DS-D2.7, Guidelines for the encoding of spatial data, v3.35

ISO/TS 19103 Geographic information - Conceptual schema languageISO 19109 Geographic information - Rules for application schema

2.2 Reference material

Common Database on Designated Areas reportinghttp://rod.eionet.europa.eu/obligations/32

Central Data Repository http://cdr.eionet.europa.eu/

Data Dictionary http://dd.eionet.europa.eu/

Reportnet http://www.eionet.europa.eu/reportnet

ROD – Reporting obligations databasehttp://rod.eionet.europa.eu/

2.3 General definitions

Terms and definitions necessary for understanding this document are defined in the INSPIRE Glossary http://inspire.ec.europa.eu/glossary. In addition, the following terms and definitions are used:

Protected Site: The INSPIRE Directive defines a Protected Site as an area designated or managed within a framework of international, Community and Member States' legislation to achieve specific conservation objectives. Protected Sites and Protected Areas are synonymous. According to the International Union for the Conservation of Nature (IUCN), a Protected Site is an area of land and/or sea especially dedicated to the protection and maintenance of biological diversity, and of natural and associated cultural resources, and managed through legal or other effective means.

1 http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2007:108:0001:0014:EN:PDF2 http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CONSLEG:2010R1089:20110225:EN:PDF3 http://inspire.ec.europa.eu/documents/Data_Specifications/D2.5_v3.4.pdf4 http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_EF_v3.0.pdf5 http://inspire.ec.europa.eu/documents/Data_Specifications/D2.7_v3.3.pdf

CDDA-INSPIRE reporting data model. 7Description of Processes, Tools, and Deliverables

Page 8: WISE Technical Report -    file · Web viewWISE Technical Report -

Protected Area: A clearly defined geographical space is recognised, dedicated and managed through legal or other effective means in order to achieve the long-term conservation of nature with associated ecosystem services and cultural values. Definitions and details are basing on IUCN publication: “Guidelines for applying Protected Area Management Categories6”.

Designated Areas: The definition of a "designated area" within the Common Database on Designated Areas (CDDA) is very similar to the protected area definition by IUCN. The "designation types" are grouped according to 3 categories, which clearly reflect the IUCN note above by also identifying designation types in other sectors "or other effective means". As some of the designation types do not refer to the creation of individual site networks, the definition of the CDDA also includes "area covering" designations such as the protection of the complete distribution of certain habitats. This is an addition to the IUCN "protected area" definition.

CDDA: Database about nationally designated areas including nature protection sites such as national parks and nature reserves. The definition is based on EEA publications7.

Eionet: European Environment Information and Observation Network. Definition based on Eionet website8.

Harmonisation: This means the ability of data to be compatible and implies the adoption of common rules in application schemas, coordinate reference systems, classification systems, identifier management, etc. from different points of view. Definition based on NatureSDIplus project publications9.

Interoperability: It gives the possibility for spatial data sets to be combined, and for services to interact, without repetitive manual intervention; in such a way that the result is coherent and the added value of the data sets and services is enhanced [INSPIRE Directive]. Definition based on the INSPIRE Glossary 10.

2.4 Symbols and abbreviations

Acronym DescriptionAQD Air Quality DirectiveATS Abstract Test SuiteCDDA Common Database on Designated Areas

DG ENV The Directorate-General for the Environment, European Commission

DM Data modelDQ Data QualityEA Enterprise Architect softwareEC European CommissionEEA European Environmental AgencyEIONET European environment information and observation networkETC/BD European Topic Centre on Biological DiversityETL Extract - Transform – LoadGIS Geographical Information Systems

6 http://data.iucn.org/dbtw-wpd/edocs/PAPS-016.pdf7 http://dd.eionet.europa.eu/datasets/latest/CDDA8 http://www.eionet.europa.eu/9 http://www.nature-sdi.eu/10 http://inspire.ec.europa.eu/glossary/Interoperability

8 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 9: WISE Technical Report -    file · Web viewWISE Technical Report -

Acronym DescriptionGML Geography Markup LanguageGN Geographical NamesHALE Humboldt ALignment EditorINSPIRE Infrastructure for Spatial Information in EuropeINSPIRE PS INSPIRE Protected sites themeIR Implementing Rules (a.k.a Commission Regulation)ISDSS Interoperability of spatial data sets and servicesJRC Joint Research CentreMD MetadataMIF Maintenance and Implementation Framework (INSPIRE)MIG Maintenance and Implementation Group (INSPIRE)NFP National Focal Point (Eionet)NRC National Reference Centre (Eionet)PS Protected SitesTG Technical guidelines (a.k.a Data/interoperability specification)UML Unified Modelling Language

UNEP-WCMC United Nations Environment Programme – World Conservation Monitoring Centre United

WDPA World Database on Protected Areas

CDDA-INSPIRE reporting data model. 9Description of Processes, Tools, and Deliverables

Page 10: WISE Technical Report -    file · Web viewWISE Technical Report -

3 Scope3.1 Informative view on a broader scope of the proposed activities

The EEA, as a guardian of the CDDA priority data flow, coordinates the CDDA reporting to keep the harmonised data compliant with the thematic requirements and introduces the pilot projects to evaluate the inclusion of the INSPIRE data specifications. Therefore, the EEA has proposed a three years activity to harmonise the CDDA data specifications with the INSPIRE specifications and to prepare the reporting workflow which will rely on the INSPIRE infrastructure, including metadata, data and services.

The purpose of the multiannual activities is to establish the reporting data flow for the Common Database on Designated Areas (CDDA) based on the INSPIRE specifications for metadata, data and services. With this implementation, the data providers (Eionet members) will fulfil two reporting obligations: first on CDDA under EEA/Eionet Annual Work Programme and secondly, under INSPIRE Directive11. Successful implementation will provide better interoperability between the reported data and other more up-to-date information that can be exchanged between the international, European and national or sub-national levels. The first INSPIRE-based reporting for CDDA is foreseen in March 2018.

The established reporting workflow and the reporting system architecture will serve as the guidelines for other similar thematic reporting data flows compliant with the INSPIRE specifications.

The proposed multiannual activities related to e-Reporting and INSPIRE include: Develop the concept of e-Reporting which is based on the INSPIRE services and which is

harmonised with the INSPIRE data specifications (this concept is of general nature and relevant to several/all reporting data flows);

Design of the CDDA data model as a thematic extension of the related INSPIRE Protected sites data model;

Setting-up the reporting of CDDA data through the INSPIRE services;

Testing of the CDDA data, services and tools (e.g. test platform for e-Reporting);

Adaptations of the EEA systems for reporting, if needed;

Developing the guidelines for the new CDDA reporting workflow.

The proposed activities are enumerated in the table below.

11 http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN

10 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 11: WISE Technical Report -    file · Web viewWISE Technical Report -

Table 3.1 Proposed activities related to e-Reporting and INSPIRE

Proposed activity Proposed deliverablesA. Concept and design of the reporting workflow based on INSPIRE infrastructure (metadata, data, services)

- Concept of e-Reporting- Reporting system architecture

B. Development of new CDDA data model as extension of the INSPIRE Protected sites data model, related XML schemas and data examples

- UML data model- Feature catalogue- XML schemas- Code lists

C. Preparing and testing the exchange of CDDA data through web services (including INSPIRE network services) with pilot Eionet countries:- Countries participation in developing metadata,

data and services- EEA testing scenarios for data delivery and data

consumption

- Testing INSPIRE based reported data, metadata and services, prepared by the countries

- Testing the use of services, basic data quality

D. Testing the reporting workflow and evaluating the use of tools and systems (e.g. Reportnet, Common Workspace, etc.) for harvesting, verification, resubmission, confirmation, archiving, etc. of the reported data (e.g. test platform)Specific operational testing case: CDDA

- Adaptation of EEA tools and systems, where needed

- Developing quality control checks (QA/QC)

- Documentation of the reporting workflow

- Operational reporting testing and updates

- Test reportsE. Developing the guidelines for the CDDA reporting - Guidelines for reporting

3.2 Specific project 2015 - 2016

The scope of the specific project is only related to the activity B (“Development of new CDDA data model as an extension of the INSPIRE Protected sites data model, related XML schemas and data examples”) from the set of the multiannual activities, described in Table 3.1.

The project uses the INSPIRE legal documents and specifications together with the existing CDDA specifications and reporting requirements and designs the CDDA data model as a thematic extension of the related INSPIRE Protected sites data model. It provides the GML/XML schemas and the examples of compliant data.

The project is organised into several phases. Each phase requires specific expertise and provides the deliverables which are important milestones for project progress and development. The present report essentially describes the processes, tools, and deliverables produced under the specific contract as presented in the table below.

CDDA-INSPIRE reporting data model. 11Description of Processes, Tools, and Deliverables

Page 12: WISE Technical Report -    file · Web viewWISE Technical Report -

Table 3.2 Project phases, processes, tools and deliverables

Tasks - Processes Tools Deliverables1. Developing the new CDDA data model as extension of the INSPIRE Protected sites data model, including all available updates of the CDDA content

- Enterprise Architect (EA)- ShapeChange

- UML data model- Code lists- Feature catalogue

2. Developing of the XML schemas and validation with the INSPIRE XML schemas

- ShapeChange- Oxygen

- GML/XML schemas- Validation report

3. Testing how to provide data according to the new XML schemas with examples of test data or services

- HALE- Oxygen- MS Excel

- Matching tables and mapping rules

- Test data (GML): samples generated from the European CDDA or/and from the national databases (participation of the Eionet members)

- Testing results’ documentation4. Final updates and report - MS Word - Final updates of all deliverables

- Report

3.3 Expected outcomes

Plain input data models are transformed into an object-oriented and extended INSPIRE data model. The methodology for the production of the new data model is based on existing solutions, and profit the knowledge gained in the previous project CDDA ran in 2014.

The following chapter 4 describes the processes followed during the project explaining the basic methodology and indicating the tools used and deliverables produced.

In chapter 5, a description of the different tools used in the project is provided. Those tools are used for the development of the new UML data models, for the creation of the GML/XSD schema and feature catalogue, for the transformation from the original information into the new data specifications and for the validation against XSD schemas.

Finally, chapter 6 describes the final deliverables, as well as other additional deliverables produced and required during the project.

12 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 13: WISE Technical Report -    file · Web viewWISE Technical Report -

4 Description of the processesThis chapter describes the different approaches followed during the project for the right achievements of the main objectives. The project relies on the outcomes of the pilot project “CDDA in conformity with INSPIRE”12, concluded in 2014. The figure summarise all the information described in the report.

Figure 4.1 Summary of the process followed, deliverables produced and tools used

4.1 Developing the new conceptual data model for CDDA

Following the general rules13 for the extension of the INSPIRE application schemas, the extension would imply at a minimum that:

the extension does not change anything in the INSPIRE data specification but normatively references it with all its requirements

the extension does not add a requirement that breaks any requirement of the INSPIRE data specification

It is allowed

to add new application schemas importing INSPIRE or other schemas

to add new types and new constraints in the application schemas

12 http://forum.eionet.europa.eu/nrc-nature-and-biodiversity-interest-group/library/bdc/cdda-and-inspire-implementation/project-deliverables-final 13 http://inspire.ec.europa.eu/documents/Data_Specifications/D2.5_v3_3.pdf

CDDA-INSPIRE reporting data model. 13Description of Processes, Tools, and Deliverables

Page 14: WISE Technical Report -    file · Web viewWISE Technical Report -

The development of the new data models has entailed:

Splitting the existing (old) CDDA into two different packages and reporting process, one for sites and one for designation types (based on the new reporting requirements)

Adding new feature types and data types

Extending existing code lists / creating new ones

Renaming the elements following INSPIRE principles

Modifying the multiplicity of some attributes to improve or reduce the flexibility of the data model

Adding constraints to the application schemas.

The two data models have been developed using Sparx System Enterprise Architect for the management of the UML.

The extension or creation of new code list depends on the extensibility value: a) not extensible b) extensible using narrower values c) extensible using additional values at any level d) any values allowed

The restriction is that the extended values and their definitions shall be made available in a register, referenceable through a persistent http URI. The recommendation is to include additional human-readable label.

In this project, the extension of existing code list and new code list have been published by the EEA under the vocabularies of the EIONET data dictionary14.

At the end of this process, two data models have been produced, one for CddaReporting (sites and designation boundaries) and one for DesignationTypes (national designations). The deliverables are described in Chapter 6.

4.1.1 CDDA Reporting

Extension of the data model

As mentioned above, the CddaReporting will collect the information about the CDDA sites and also the designation boundaries. This data model is based on INSPIRE Protected Sites simple schema, that has been extended following INSPIRE recommendations and according Generic Conceptual Model principles.The extension includes elements from the old CDDA modelled following INSPIRE approach, what make possible to collect some additional information not existing in original CDDA data model.

The attributes in the new data model are differentiated as mandatory and no mandatory. The designation boundaries information defines the line to distinguish the status of mandatory. The voidability concept has been not used.

14 http://dd.eionet.europa.eu/vocabularies

14 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 15: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 4.2 Mandatory attributes for CddaReporting

The INSPIRE Protected Sites Simple schema has been extended for the CddaReporting by including additional elements from several schemas:

INSPIRE Generic Conceptual Model: base types: «featureType», «codeList»

ISO19103:2005 basic types

ISO 19107:2003 Spatial Schema. «Leaf» Geometry: GM_Point

.Extension and creation of new code lists

The CddaReporting requires the extension of one INSPIRE code list:

DesignationSchemaValue has been extended with a new code value “cdda” that links to the National Designations code list values: ProtectedAreaDesignationValue

CDDA-INSPIRE reporting data model. 15Description of Processes, Tools, and Deliverables

Page 16: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 4.3 Extension of INSPIRE DesignationValue code list

The model has been also extended by the creation of specific code list for the CDDA reporting that have been published as vocabularies in the Eionet data dictionary (http://dd.eionet.europa.eu/vocabularies). The majority of them, were already included in the old CDDA, and has only required some redesign and update:

CddaCoordinatesCodeValue: http://dd.eionet.europa.eu/vocabulary/cdda/CddaCoordinatesCodeValue

CddaDisseminationCodeValue: http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue

EionetChangeTypeValue: http://dd.eionet.europa.eu/vocabulary/cdda/EIONETChangeTypeValue

Iso3CountryEntityValue: http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue

IucnCatValue: http://dd.eionet.europa.eu/vocabulary/cdda/IucnCatValue

MajorEcosystemTypeValue: http://dd.eionet.europa.eu/vocabulary/cdda/MajorEcosystemTypeValue

CddaResolutionCodeValue: http://dd.eionet.europa.eu/vocabulary/cdda/CddaResolutionCodeValue

CddaAvailabilityCodeValue: http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue

CddaDisseminationCodeValue: http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue

ProtectedAreaDesignationValue: http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue

16 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 17: WISE Technical Report -    file · Web viewWISE Technical Report -

The new code list created specifically for the new data model is:

ProtectedAreaTypeValue: http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaTypeValue

4.1.2 Designation types

The new data model for designation types is out of the INSPIRE scope, and it is not based in any specific INSPIRE data models. The data model created uses the required elements to collect information from MS about designations, underlining that this information is basically alphanumeric.

Some elements are close to INSPIRE, and they include additional information to be reported by member states.

The DesignationType application schema includes elements from several foundation schemas:

INSPIRE Generic Conceptual Model: base types: «featureType», «codeList», LegislationCitation, RelatedParty

ISO19103:2005 basic types

ISO 19108:2006 Temporal Schema. «Leaf» Temporal Objects: TM_Period

The elements, attributes, data types or code list created keep the existing relationships with the previous CDDA sites. A new code List has been created specifically for DesignationType

CategoryValue: http://dd.eionet.europa.eu/vocabulary/cdda/CategoryValue

Additionally it uses the same code list that CddaReporting for:

Iso3CountryEntityValue

ProtectedAreaDesignationValue

The ProtectedAreaDesignationValue is an example of element that is used in both data models. Some concepts that are new for the designation type comparing to old version of CDDA are those related to life cycle of the designations.

4.2 Developing the new CDDA GML schemas

The new GML schemas have been prepared using the tool ShapeChange described in section 5.2. The process includes the preparation of a configuration file that include the specific arguments for the GML schema preparation. As it is described in the Figure 4.4 Schema Input-Output Shape change the input information is the EA project, producing not only the GML schema but also the Feature catalogue which include the description of the different elements in the data model as well as the code list and the specific constraints.

CDDA-INSPIRE reporting data model. 17Description of Processes, Tools, and Deliverables

Page 18: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 4.4 Schema Input-Output Shape change

Additional information about the configuration file is presented in section 6.4

4.3 Developing the matching tables and descriptive mapping rules for the data transformation

The matching table allows mapping the input or source data model with the output data model (CddaReporting). The specifications are reflected in the matching table in the way that helps to carry out the process of matching the source with the target attributes. To this end, clear description and explanations should be provided.

Working with the matching table reveal the level of quality of the information contained in the source data model, the needs for improvement or the preliminary processes that need to be carried out in order to achieve the final objective. The matching table itself serves additionally, as a quality control document and reflect the methodology to be followed in the process of transformation between the models (mapping rules).

Matching tables are available from INSPIRE web site15. For this project the INSPIRE Protected Sites theme, Simple schema16 has been used as a basic template.

4.3.1 Matching Tables adaptation

The original matching table has been slightly modified in two different ways: by the addition of new lines to describe the new elements from the extended data model that

provides specific CDDA thematic content.

by the addition of two new columns. The first column describes the scope and the mapping rules; the second includes real examples for a better understanding on how to apply the transformation rules.

In the Matching tables of CddaReporting, the elements required for mapping are highlighted in light blue colour.

The matching tables prepared includes the input data description, identifying the required attributes for the new data model. Three separated matching tables are provided:

15 http://inspire.ec.europa.eu/data-model/approved/r4618-ir/mapping/16http://inspire.ec.europa.eu/data-model/approved/r4618-ir/mapping/Protected Sites Simple Mapping Table.xml

18 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 19: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA sites from Croatia using reported information: Input SHP +Access

CDDA sites + designation boundaries from The Netherlands using reported information: Input SHP + Access + Excel (Designation boundaries)

Representative data from the different countries reporting to EEA from EEA CDDA database: Input SpatiaLite database

The process has been the same in all source data, and examples are included in the ANNEX 6

4.3.2 Mapping Rules preparation

This section describe the mapping rules required for the transformation of the original data model into the new CDDA data model adopted, extending the INSPIRE Protected Sites simple schema data model. It should contain the maximum information that will allow the data provider to know the right process to follow in order to achieve the proper information for every attribute.

The left part of the sheet includes the attributes of the target data model, the application schema 'Protected Sites' (version 3.0) and CDDA extended (version 3.0). The attributes, characteristics, values, multiplicity, stereotypes and descriptions are described in the matching table. The information from the previous activity in the Project (described in section 4.1) is directly used.

In the following right part of the sheet, the original CDDA data model is represented providing detailed information in the same way that in the target data model. The mapping of the attributes (output/input), the process, operations and values used are included in the right part of the sheet.

For mandatory attributes a link to an existing mapping rule must be provided.

For voidable attributes a mapping rule or a value assigned to the nilReason should be provided. The value should be agreed previously. In the specific case of this Project, an agreement with technical team has been reached.

For optional attributes, the mapping rule is not needed.

4.4 Transformation and validation of the selected data

This is the process where the operations move from the conceptual and logical levels to the physical level, and this is how the digital file compliant with the new CDDA data specifications is obtained. The input data that conform to a geographic information model will modify their content to continue complying not only with the inherent characteristics of the digital geographic information but also with the specifications of a final model. When developing new models, the rules of transformation between previous and subsequent models are defined. In this case, INSPIRE and CDDA reporting define the rules that are described in the mapping rules, as mentioned above. The next step will consider applying the mapping rules precisely specified, in the tool or engine that may execute them and store the remodelled data in a common database.

The experiences acquired with data harmonisation processes have shown that the transformation of the data model must be followed with a validation process of the data obtained in order to ensure the final interoperability of the system. The INSPIRE data specifications and the organisations working in this field consider this to be fundamental and provide documentation to help carry out this process.

CDDA-INSPIRE reporting data model. 19Description of Processes, Tools, and Deliverables

Page 20: WISE Technical Report -    file · Web viewWISE Technical Report -

4.4.1 Transformation

The main goal of this activity is to obtain a physical file known as GML instance document that will comply with the mapping rules detailed in the matching table. It is the process to transform the original data to the new data model.

The transformation itself has been carried out using the open source tool HALE (described in chapter 6). Using this application (or other transformation tools) the data model edition can be done easily and a GML instance file produced.

Each element can be configured according to the INSPIRE data specifications and following the specific GML encoding requirements. An example of this configuration is presented below on how a designated area is encoded for the attribute designation.

Table 4.3 Example: encoding designation for CddaReporting

Attribute designation

Input data IUCNCATDESIG_ABBR

Transformation rule

To provide at least information about two designation schemas : IUCN and cdda (CDDA extended part)

Value Code Listhttp://dd.eionet.europa.eu/vocabulary/cdda/IucnCatValuehttp://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue

Remarks for code list the elements href and title are provided

Encoding <ps:siteDesignation> <ps:DesignationType> <ps:designationScheme xlink:href="http://inspire.ec.europa.eu/codelist/DesignationSchemeValue/IUCN" xlink:title="IUCN"></ps:designationScheme> <ps:designation xlink:href="http://inspire.ec.europa.eu/codelist/IUCNDesignationValue/ProtectedLandscapeOrSeascape" xlink:title="protected landscape or seascape"></ps:designation> <ps:percentageUnderDesignation>100</ps:percentageUnderDesignation> </ps:DesignationType> </ps:siteDesignation> </ps:siteDesignation> <ps:DesignationType> <ps:designationScheme xlink:href="http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda" xlink:title="Cdda"></ps:designationScheme> <ps:designation xlink:href="http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue/HR07" xlink:title="Significant Landscape"></ps:designation> <ps:percentageUnderDesignation>100</ps:percentageUnderDesignation> </ps:DesignationType> </ps:siteDesignation>

4.4.2 Validation proof

The full validation following abstract test suite of INSPIRE is out of the scope of this project; however, some validation criteria have been applied to check the final results of the transformation.General validation aspects can be enumerated:

20 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 21: WISE Technical Report -    file · Web viewWISE Technical Report -

Validation of the structure of a GML file.

Semantic validation: check that the attributes are correct and that the names are correctly spelt.

Syntax validation: check that the information contained in the fields is correct. This requires taking into account the characteristics of the attributes (numeric, string, date, date-time, etc.) and the ISO standards.

Spatial validation: check that the results (GML files) may be displayed in a viewer and are geographically correct by comparing their coordinate system with that of other data layers.

The GML instance document obtained from the transformation has been validated in different ways and using several tools.

The first validation is carried out using HALE, which integrates a module for validation. It validates the GML structure, and also accomplish semantic and syntax validation. The tool facilitates the analysis and resolution of the errors that appear during the transformation process. This validation is against the proper target schema (INSPIRE PS simple + CDDA extension). The tool offers the possibility to pass an additional validation at the end of the transformation when the GML is created to ensure the proper encoding against the schema.

Further validation has been carried out using Oxygen XML Editor 17.1 that analyse the conformity of the results. This process of validation compares GML instance document against the CddaReporting.XSD schema, and against the original INSPIRE PS simple schema. The results have been totally satisfactory in both cases, fulfilling with the specific data model agreed upon. The use of a second tool external and different from the transformation is highly recommended to assure the conformity of the data.

Finally, spatial validation as another way to control the quality of the results and the validity of the data has been applied by open the GML in a GIS viewer. This QC has been done using QGIS, and it has been possible to view the CDDA sites used in the example.

5 Description of the ToolsThe objective pursued is to indicate the different tools that have been used during the project, how they have been used and configured to produce the required deliverables.

CDDA-INSPIRE reporting data model. 21Description of Processes, Tools, and Deliverables

Figure 4.5 Example: Protected Sites GML in a GIS viewer

Page 22: WISE Technical Report -    file · Web viewWISE Technical Report -

5.1 Enterprise Architect

Tool used for modelling the WISE extended data modelhttp://www.sparxsystems.com /products/ea/index.html

This tool allows working with existing models linked through the Subversion repository. In this specific project information from four different projects: INSPIRE, ISO, Sites and Designations have been used.

Before modelling with Enterprise Architect, it is required to connect to the subversion repository for the project WISE data model and INSPIRE, created by EEA.The repository is at https://svn.eionet.europa.eu/repositories/INSPIREDataModels/cdda-data-model/

The access to the SVN repository requires authentication using Eionet credentials. Additionally, it requires installing a subversion client TortoiseSVN on the local computer. It can be downloaded at https://tortoisesvn.net/downloads.html

After the installation, a new folder on the local PC must be created, eg.: Project-CDDA-data-model. Select the new folder and click on the mouse right button to active the menu and choose checkout SVN function:

URL of the repository: https://svn.eionet.europa.eu/repositories/INSPIREDataModels/cdda-data-model/

Checkout directory: select directory on local PC, e.g.: C:\ Project-CDDA-data-model

Figure 5.6 Connection with the EEA Subversion repository

Enterprise Architect needs additional configuration to set-up the versioning system. It applies version control to Packages within a model. A Package is the primary organizational construct for UML models.

The first step requires creating in Sites or Designations projects the different packages to be modelled and configure the versioning in EA. Several properties must be configured for every package:

Unique ID: All different users shall use the same ID. In the project: o Cdda

22 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 23: WISE Technical Report -    file · Web viewWISE Technical Report -

o Inspire-modelo Isotc211

Type: Subversion Working Copy Path: the path where the projects are copied. Some examples may be:

o Cdda: c:\Project-CDDA-data-modelo INSPIRE: C:\Project-CDDA-data-model\INSPIRE-modelo ISO: C:\Project-CDDA-data-model\ISO

Subversion Exe Path: path where the executable svn.exe is copied

Figure 5.7 Project configuration in EA

The projects from INSPIRE have to be imported after the package creation and once the configuration of the version control settings are established. To import the projects, on the INSPIRE package in Package Control -> Get Package:

- Select a Version Control Configuration: select option inspire-model

- Select shared file for inclusion: select TEMPLATE - INSPIRE Consolidated UML Model - ANNEX I-II-III - complete.xml

CDDA-INSPIRE reporting data model. 23Description of Processes, Tools, and Deliverables

Page 24: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 5.8 Importing and sharing INSPIRE data models

The version control in EA must be associated with an XML file. In this project, the Sites and the DesignationDescription have their own and specific XML. It is configured in the Package Control -> Configure.

Figure 5.9 Version Control configuration

The parameters configured are:

Version Control: It must be selected the path previously defined as cdda for both sites and DesignationDescription.

24 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 25: WISE Technical Report -    file · Web viewWISE Technical Report -

XMI Filename: name and path of the XML file

Sites: %cdda%\CDDA\CDDAExtended_Vx.x.xx.xml

DesignationDescription: %cdda%\CDDA\DesignationDescription_Vx.x.xx.xml

The next step requires to import the different UML profiles from INSPIRE, by indicating the path of the XML file (e.g. C:\Project-CDDA-data-model\ INSPIRE_UMLProfile_20130122.xml)

Figure 5.10 Importing UML profile in EA

Once all the configurations are completed, the process of modelling can start. Different examples are included to better illustrate the modelling of the two data models.

One of the possible modifications is to add a new class. It requires: Add the name of the new class

Specify the stereotype: featureType, dataType, codeList, etc.

Version of the project

Details defining the class properties (type, multiplicity, stereotype).

When the attribute comes from INSPIRE or ISO (as it is the case of representativePoint in DesignatedArea) the option Select Type can be used to search the type (GM_Point).

Figure 5.11 Search Type option in EA

When an existing class need to be linked, then, it must be done through the project browser, by linking with the project. This is the case for DesignatedArea class, linked to ProtectedSite class from

CDDA-INSPIRE reporting data model. 25Description of Processes, Tools, and Deliverables

Page 26: WISE Technical Report -    file · Web viewWISE Technical Report -

the INSPIRE Consolidated UML Model, subpackage Protected Sites Simple, INSPIRE Consolidated UML Model.

Figure 5.12 Adding classes from other packages

By adding the class from INSPIRE, the new class DesignatedArea have now the same characteristics than ProtectedSite from INSPIRE and are linked. Those relationships have to be reflected in the application schema.

In this project the following relationships has been established and used: Protected Sites Simple schema

type ISO TC211::ISO 19103:2005 Conceptual schema language::Basic Types::Primitive

type ISO TC211::ISO 19103:2005 Conceptual schema language::Basic Types::Derived

type ISO TC211::ISO 19107:2003 Spatial Schema

type ISO TC211::ISO 19108:2006 Temporal Schema

Generic Conceptual Model::Base Types

The procedure to display all those linked elements is the same as if it were a class defined in another model. The element can be dragged and dropped from the original package to the project package, and proceed to set up the links.

The final results is the UML data model provided as deliverable in the project, and included in .

5.2 ShapeChange

This tool has been used for generating the GML schema and Feature Catalogue. The Feature Catalogue describes all the elements of the new data models.http://shapechange.net/

Shape Change is a Free Tool (GPL) that allows automatic creation of GML application Schemas using the XML created in Enterprise architect during the phase described in Section 4.2 Developingthe new CDDA GML schemas

The primary mechanism for providing arguments to ShapeChange is the configuration file. More information about this file is presented in section

26 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 27: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 5.13 HALE alignment

5.3 MS Excel File

Matching tables have been created using spreadsheet files (MS Excel xls). The Mapping rules have been also included in the correspondent matching describing the rule how to transform the data structure from the original data source into the new developed GML schema.

Open software to manage spreadsheet files can be found at:https://www.openoffice.org/; https://www.libreoffice.org/;

The original matching tables for the different INSPIRE Themes can be downloaded athttp:// inspire.ec.europa.eu/data-model/approved/r4618-ir/mapping/Protected%20Sites%20Simple %20Mapping%20Table.xml

5.4 HALE

The Humboldt ALignment Editor is the tool used for transformation and validation of the CDDA sample data against GML schemas. The version used in this project has been the last published version V2.9.4 http://www.esdi-community.eu/projects/hale

This tool fulfil the main three aspects required for this type of conversion tools: It allows to edit the data models

It transform between formats: in this transformation is required from Shape to GML

It transform coordinates systems.

Additionally it includes Inspire Data models and the last version of the application also includes the new recommendations of the INSPIRE Directive as well as data encoding updates.

The tool allows to define and include all the mapping rules for the proper transformation. One of the main advantages is the possibility to save and reuse the mapping rules in further transformations.

The mapping can be reviewed in an easy and graphical way.

CDDA-INSPIRE reporting data model. 27Description of Processes, Tools, and Deliverables

Page 28: WISE Technical Report -    file · Web viewWISE Technical Report -

5.5 Oxygen

Specific tool used for validation Oxygen XML Editor17.1https://www.oxygenxml.com/

The tool is used as external tool for validation, in addition to the validation carried out during the transformation with HALE tool. The process is similar to the previous one, it requires one GML file to be validated and the original schema to validate against.

5.6 Other tools

5.6.1 QGIS

The tool has been used only for

visualization purposes. QGIS is a free and open source Geographic Information System very powerful and widely used in the GI community. It allows to create, edit, visualise, analyse and publish geospatial information.http://www.qgis.org/en/site/forusers/download.html

28 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Figure 5.14 Example using Oxygen

Page 29: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 5.15 Example of visualization in QGIS

5.6.2 Schematron

It is a structural schema language expressed in XML that is used for stablishing some rules during the validation process. In this project, the creation of schematron rules was out of the scope, however, some automatically generated schematron (using shapechange) have been used to validate the constraints.

Additionally additional schematron rules have been prepared by ETC Biodiversity team member and are included in ANNEX 5, or can be downloaded at

CDDA-INSPIRE reporting data model. 29Description of Processes, Tools, and Deliverables

Page 30: WISE Technical Report -    file · Web viewWISE Technical Report -

6 Description of the DeliverablesThis chapter includes the list and the overview of the deliverables that were developed in the project, including the configuration files required for some of the tools.

6.1 UML data model

This deliverable includes all the information related to the new CDDA data model, split in two separated designated areas and designation types. The process has included the extension of the INSPIRE Protected Sites data model following the INSPIRE principles for designated areas and the creation of a new data model for designation types.

The UML data model is the conceptual data model for the new CDDA reporting. It is provided in different formats:

- Enterprise Architect format: CDDA_V3.0.eap

- HTML view: accessible through the subversion repository

https://svn.eionet.europa.eu/repositories/INSPIREDataModels/cdda-data-model/Cdda_V3.0-view/

- HTML view of the final UML data model: https://taskman.eionet.europa.eu/issues/69410

6.2 Feature Catalogue

The data specifications for Sites and Designations have been documented in a feature catalogue according to the ISO 19110 methodology for feature cataloguing.

The tool ShapeChange, described in section 5.2 has been used for the documentation of the Feature Catalogue.

The feature catalogue for sites includes not only the new elements from the extended data model but also those elements inherited from INSPIRE data models.

The feature catalogue is composed by different parts:1. General Information:

Version

Date

Scope

Responsible Organization

2. Elements description: For every element (feature type, attribute) the following information is provided: Name: following INSPIRE naming principles

Definition

Description: It includes additional information about the element

Voidable: Condition of voidability (true or false)

30 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 31: WISE Technical Report -    file · Web viewWISE Technical Report -

Multiplicity

Value type

3. Constraints:

Name:

Description

Expression: OCL type

The feature catalogues ‘CddaReporting_FC_V3.0’ and ‘DesignationTypes_FC_V3.0’ can be downloaded from the following links: https://taskman.eionet.europa.eu/issues/69410 and https://taskman.eionet.europa.eu/issues/69413

An illustrative copy has been included in ANNEX 2

6.3 GML Schema

Two GML schemas are generated with ShapeChange, for CddaReporting and DesignationTypes.The GML schema includes general information, imports the INSPIRE and other GML schemas and includes the new extended elements.

The general information contains the encoding, the targetNamespace where the GML schema is published.

In the project, the imported schemas are:

Protected Sites Simple – INSPIRE PS

type ISO TC211::ISO 19103:2005 Conceptual schema language::Basic Types::Primitive,

type ISO TC211::ISO 19103:2005 Conceptual schema language::Basic Types::Derived,

type ISO TC211::ISO 19108:2006 Temporal Schema

Generic Conceptual Model::Base Types

The GML schema for CddaReporting defines new extended elements (name, type and other characteristics depending on the type of element). An illustrative copy of the two GML schemas is provided in ANNEX 3

The GML schemas ‘CddaReporting_V3.0.xsd’ and ‘DesignationTypes_V3.0.xsd’ are published in:http://dd.eionet.europa.eu/schemaset/cdda

The schema and other additional documentation as an additional Schematron Schema file are provided for validation purposes at the following links: https://taskman.eionet.europa.eu/issues/69411 and https://taskman.eionet.europa.eu/issues/69414

CDDA-INSPIRE reporting data model. 31Description of Processes, Tools, and Deliverables

Page 32: WISE Technical Report -    file · Web viewWISE Technical Report -

6.4 Configuration file: ShapeChange

A ShapeChange configuration file is an XML file which conforms to a customized XML Schema. The configuration files CddaReporting_SC.xml and DesignationTypes_SC.xml and the Enterprise Architect Cdda_V3.0.eap file must be copied to the same folder to obtain the proper result.

The root element of the configuration file is the <ShapeChangeConfiguration> element. The file is divided into various “functional elements”:

The <input> element defines the source of the data model and some parameters controlling its interpretation.

The parameter inputFile specify the name of the project (Cdda_V3.0.eap). In this way, ShapeChange, can read the content of the EA file, obtaining the necessary information to create the Feature Catalogues and the GML schemas (XSD).

Another important parameter is checkingConstraints, which analyses the existing OCL constraints in the UML data models and made possible to include them in the Feature Catalogue.

The <log> element defines logging parameters, and facilitate the detection of some modelling errors.

The <targets> element has the required information to create the Feature Catalogue and the XSD.

The most important parameters to define for the Feature Catalogue are:

outputDirectory: folder where the Feature Catalogue is going to be created

outputFilename: name of the Feature Catalogue file

outputFormat: format in which the Feature Catalogue is created

inheritedProperties: to indicate whether the properties of inherited models must be presented or not.

In the configuration of the XSD, apart from the outputDirectory parameter, the defaultEncodingRule state the type of encoding to follow. This Project follows the ISO19136_2007_INSPIRE_Extensions encoding.

Once everything is configured, the shapechange xml file can be executed and all the specified files are created.

6.5 Constraints in UML data model and Schematron rules

The constraints that limits somehow the UML elements, requires specific rules for the validation against the schema. The objective is to translate the OCL constraints language to the XML language. The tool Shapechange performs this transformation automatically for code lists and allows to add some further rule that is not included in the above mentioning encoding rule by using a schematron.

For a tailored rule the parameter defaultEncodingRule must refer to the name of the rule:

<targetParameter name="defaultEncodingRule" value="CDDA" />

32 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 33: WISE Technical Report -    file · Web viewWISE Technical Report -

Then, the rule is defined extending the iso19136_2007_INSPIRE_Extensions:

<rules><EncodingRule name="WISE" extends="iso19136_2007_INSPIRE_Extensions">

<rule name="rule-xsd-pkg-schematron"/><rule name="rule-xsd-cls-codelist-constraints"/>

</EncodingRule></rules>

The rule rule-xsd-pkg-schematron creates the schematron while the rule rule-xsd-cls-codelist-constraints adds constraints on code list values to a schematron schema.

The creation of new schematron rules is out of the scope of this project, therefore, only rules created automatically by the tool shapechange and their equivalence in OCL constraints in UML can be visualized in ANNEX 5

6.6 Matching Table and Mapping Rules

The deliverable includes four excel sheets, prepared following the process described in section 4.3, which include the matching table with target and source data model, the structure of the original data and the example used for the purpose of the transformation.

CddaReporting_HRV_V3.0.xlsx

CddaReporting_NLD_V3.0.xlsx

CddaReporting_CDDA_V3.0.xlsx

DesignationType_V3.0.xls

The final version of the matching tables together with their corresponding mapping rules can be downloaded from the following links:

CddaReporting: https://taskman.eionet.europa.eu/issues/69412

DesignationType: https://taskman.eionet.europa.eu/issues/69415

A visual copy of the matching tables is provided in ANNEX 6.

6.7 Input source data for data transformation

For the purpose of the data transformation, three different source data types have been used containing information from the CDDA v13, reporting 2015:

6.7.1 CDDA reporting information using shapefile + Access database

Information from the CDDA annual reporting of Member States has been selected in the first example. The source information is composed by a graphical part in Shapefile format and an alphanumeric part in Access database format.

The selected countries have been Croatia and The Netherlands. The first one includes graphical information reported as polygons and points. The second one includes designation boundaries that will be reported in the new CDDA as designated areas.

CDDA-INSPIRE reporting data model. 33Description of Processes, Tools, and Deliverables

Page 34: WISE Technical Report -    file · Web viewWISE Technical Report -

The data preparation has been common to all of them, consisting in joining the required information from the Site table (all the attributes) and Site_Boundaries table (CDDA_Availability_code and CDDA_Dissemination_code) with their corresponding graphical information

The input information prepared contains all the necessary information to carry out the transformation process using the tool HALE and produce the final GML file fulfilling the specifications of the new CDDA INSPIRE reporting.

The Netherlands includes additional information for designation boundaries that has been also used. In this particular case, graphical information has been created as multipolygon. The associated information from the site_boundaries table has been previously analysed to complete the transformation process. The attribute SITE_CODE was missing for designation boundaries. Fort he only purpose of the transformation example, a unique identifier has been created in graphic and alphanumeric, to joining unequivocally.

34 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Figure 6.16 CDDA reporting data

Figure 6.17 CDDA reporting data for designation boundaries

Page 35: WISE Technical Report -    file · Web viewWISE Technical Report -

6.7.2 CDDA information from EEA database using SpatiaLite

The second example includes information from the reporting countries, previously transformed and centralised in a common data base prepared by the EEA in spatiaLite database format.

Starting from the EEA spatiaLite data base, 10 rows have been selected for every country to perform the transformation. The extracted information has not required any additional preprocessing and has been directly used as source data in HALE Tool.

Figure 6.18 EEA-CDDA spatiaLite database

6.7.3 Designations information from CDDA database using Excel file as input data

The third example is related to Designation Types. In this case, the source information is the CDDA database, where the representative information for designation types has been selected.

The difference with the previous examples is that only requires alphanumeric information. The Access database information has been exported to and Excel format that is fully compatible and readable from HALE. The only required modifications have been the fictitious creation of the life cycle of the designations data to cover the attribute designationPeriod that for the purpose of the project is considered as mandatory.

CDDA-INSPIRE reporting data model. 35Description of Processes, Tools, and Deliverables

Page 36: WISE Technical Report -    file · Web viewWISE Technical Report -

Figure 6.19 Designation information from CDDA reported information

The input data information prepared for the transformation is accessible at https://taskman.eionet.europa.eu/issues/69412

6.8 Configuration file: HALE alignment project

A HALE configuration file is an XML file which conforms to a customized XML Schema. It includes the transformation rules with required information on how the source information is transformed into the target data model.

Figure 6.20 Example: HALE alignment file

Three configuration files (“CddaReporting_AL _XXX_ V3.0.align”) have been prepared according to the three different input data models for CDDA sites, CDDA sites and designation Boundaries and

36 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 37: WISE Technical Report -    file · Web viewWISE Technical Report -

EEA-CDDA database. They can be downloaded from the following link: https://taskman.eionet.europa.eu/issues/69412

An additional alignment has been prepared for the designation types ‘DesignationType_AL_V3.0.align’ that can be downloaded from https://taskman.eionet.europa.eu/issues/69415

The alignment files are reusable, and are provided for further transformations that use the same source data models.

6.9 GML Files

Several GML instance files are provided, but can be grouped in the two different data models for Cdda Reporting and Designation Types.

Some specific encoding are presented below, some of them are common for the two data models and some other are specific

Code lists and code valuesIn the scope of the current reporting process, the title of the code list is not encoded. In other words, recommendation related to including not only the xlink:href attributes with the link to the code list value, but also xlink:title in code list values is out of the scope of the GML files.

Voidable attributes The INSPIRE PS Simple schema use the voidable stereotype. However, in the extension of CddaReporting the voidability has not been used. Instead of that, the attributes have been considered as mandatory or optional. In the same way the voidability has not been used for DesignationType.

For those cases where the stereotype is permitted, the INSPIRE «voidable» stereotype implies the necessity of a nilReason when data could not be provided. NilReasonType defines a content model that lets recording an explanation for a void value or other exception. In the scope of the present data transformation, the nilReason assigned should be:http://inspire.ec.europa.eu/codelist/VoidReasonValue/Unpopulated.

6.9.1 CDDA reporting

Coordinate Reference SystemThe CRS used is ETRS89 geographic: srsName=http://www.opengis.net/def/crs/EPSG/0/3035.The geometry of spatial objects may also be encoded in the ETRS89-LAEA projected coordinate system (urn:ogc:def:crs:EPSG::3035).

siteDesignationThis attribute come from the INSPIRE PS Simple data model and its definition, it allows to report different designations indicating the designation schema followed. In this way, the project agreed to include at least two designation types: one for IUCN and other for Cdda.Both designations are included in the CDDA database and are easily transferable to the new CddaReporting.

The GML encoding in this case is:

<ps:siteDesignation> <ps:DesignationType> <ps:designationScheme xlink:href="http://inspire.ec.europa.eu/codelist/DesignationSchemeValue/IUCN" xlink:title="IUCN"></ps:designationScheme>

CDDA-INSPIRE reporting data model. 37Description of Processes, Tools, and Deliverables

Page 38: WISE Technical Report -    file · Web viewWISE Technical Report -

<ps:designation xlink:href="http://inspire.ec.europa.eu/codelist/IUCNDesignationValue/ProtectedLandscapeOrSeascape" xlink:title="protected landscape or seascape"></ps:designation> <ps:percentageUnderDesignation>100</ps:percentageUnderDesignation> </ps:DesignationType> </ps:siteDesignation> <ps:siteDesignation> <ps:DesignationType> <ps:designationScheme xlink:href="http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda" xlink:title="Cdda"></ps:designationScheme> <ps:designation xlink:href="http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue/HR07" xlink:title="Significant Landscape"></ps:designation> <ps:percentageUnderDesignation>100</ps:percentageUnderDesignation> </ps:DesignationType></ps:siteDesignation>

representativePointThe CDDA collects centroid coordinates for sites in Lat/Lon format. The new data model CddaReporting includes a new attribute where this information will be reported. The encoding includes the CRS and the coordinates as follow

<cdda:representativePoint> <gml:Point gml:id="_48207589-4788-4c15-aa6c-95df900fa7b1" srsName="http://www.opengis.net/def/crs/EPSG/0/3035" srsDimension="2"> <gml:pos>2306022.7161039324 4867920.524390843</gml:pos> </gml:Point></cdda:representativePoint>

geometryWhile formally all protected sites should provide geometry, there are cases where the MS refuse to provide it, mainly due to the sensitive nature of the information. For those specific cases, the MS will provide the dummy coordinates 0,0 in order to validate the information conform INSPIRE

6.9.2 Designation Type

designationPeriodThe new attribute has been created to record information about the life cycle of the designation types. In the new Designation Type data model the date of creation or the end date of designation validity (if available) will be collected. Some examples on how this information will be encoded are included to illustrate with non-real data the two situations that could exist:

Designation with creation date and currently applicable:

<gml:TimePeriod gml:id="TP_ HR03.HRV"> <gml:beginPosition>1982-01-01</gml:beginPosition> <gml:endPosition indeterminatePosition="unknown"></gml:endPosition></gml:TimePeriod>

Designation with creation date and end date

<gml:TimePeriod gml:id="TP_GR23.GRC"> <gml:beginPosition>2014-01-01</gml:beginPosition> <gml:endPosition>2015-12-31</gml:endPosition></gml:TimePeriod>

38 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 39: WISE Technical Report -    file · Web viewWISE Technical Report -

LegislationCitationThe attributes to use in mapping to INSPIRE LegislationCitation are:

name

journalCitation

legislationLevel: It will be national for all entries, however in the countries with federal and regional political administration this might change to lower level

URL: It is not mandatory and will be only included when available. The possibility to use ECOLEX has been analysed, but will not be finally used. Nevertheless an example on how to include this information using ECOLEX is also provided.

<base2:LegislationCitation gml:id="LC_HR04.HRV"> <base2:name>Zakon o zaštiti prirode/Nature protection Act/art. 115.</base2:name> <base2:date nilReason="http://inspire.ec.europa.eu/codelist/VoidReasonValue/Unpopulated" xsi:nil="true"></base2:date> <base2:link nilReason="http://inspire.ec.europa.eu/codelist/VoidReasonValue/Unpopulated">http://www.ecolex.org/ecolex/ledge/view/RecordDetails;DIDPFDSIjsessionid=CAFF670658D09660A365A6D6CC9B934F?id=LEX-FAOC138448&amp;index=documents</base2:link> <base2:level xlink:href="http://dd.eionet.europa.eu/vocabularyconcept/inspire/LegislationLevelValue/national" xlink:title="National level"></base2:level> <base2:journalCitation> <base2:OfficialJournalInformation> <base2:officialJournalIdentification>"Narodne novine" 80/13</base2:officialJournalIdentification> </base2:OfficialJournalInformation> </base2:journalCitation> </base2:LegislationCitation>

The final GML files can be downloaded from the following links: CddaReporting https://taskman.eionet.europa.eu/issues/69412DesignationType https://taskman.eionet.europa.eu/issues/69415

An illustrative example is provided in ANNEX 9

6.10 Validation proof

The validation has been reproduced for the different GML created for CddaReporting. The proof about how the gml files have passed the validation process is provided below.

Table 6.4 Proof of validation

Oxygen XML Editor 17.1

CddaReporting schema

INSPIRE EF schema

CddaReporting_HRV_V3.0.gml Is valid Is valid

CddaReporting_NLD_V3.0.gml Is valid Is valid

CddaReporting_CDDA_V3.0.gml Is valid Is valid

CDDA-INSPIRE reporting data model. 39Description of Processes, Tools, and Deliverables

Page 40: WISE Technical Report -    file · Web viewWISE Technical Report -

Annexes

40 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 41: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 1. UML data model

CddaReporting

CDDA-INSPIRE reporting data model. 41Description of Processes, Tools, and Deliverables

Page 42: WISE Technical Report -    file · Web viewWISE Technical Report -

42 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 43: WISE Technical Report -    file · Web viewWISE Technical Report -

DesignationType

CDDA-INSPIRE reporting data model. 43Description of Processes, Tools, and Deliverables

Page 44: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 2. Feature Catalogue

Feature Catalogue CddaReporting_V3.0Version:

3.0Date:

18/02/2016Scope:

This feature catalogue compiles CDDA-PS extension informationResponsible organisation:

European Environment AgencyApplication schema: CDDA Designated AreaDefinition:

The CDDA Nationally Designated Area is an extension of INSPIRE Protected Sites simple schema.Version:

3.0DesignatedAreaDesignatedArea

Title: Designated area

Definition: Records for nationally designated areas.

Description: The table contains information about nationally designated areas in European countries, members of the Eionet network.

Subtype of: ProtectedSite

Type: Feature type

Attribute:

Name: area

Title: Area

Definition: The measure of the physical extent of any topologically 2-D geometric object. Usually measured in "square" units of length.

Description: NOTE 1 Surface area in hectares (ha).

NOTE 2 Former SITE_AREA in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: Area

Attribute:

Name: cddaId

Title: Cdda id

Definition: The CDDA ID is the unique identifier within the CDDA data base for nationally

44 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 45: WISE Technical Report -    file · Web viewWISE Technical Report -

designated areas.

Description: NOTE 1 The CDDA ID is identical to the WDPA ID and reused in the World Data base on Protected Areas.

NOTE 2 Former SITE_CODE in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: Integer

Attribute:

Name: coordinatesCode

Title: Coordinates code

Definition: Code for derivation of tabular coordinates of sites.

Description: NOTE Former CDDA_Coordinates_code in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: CddaCoordinatesCodeValue (code list)

Values eeaCalculation EEA to calculate from reported boundary data

nationalCalculation National calculation

unknown Unknown

Attribute:

Name: dataDissemination

Title: Data dissemination

Definition: Code for instructions to EEA regarding the further dissemination of information provided in the Sites table (tabular data) to partners (WDPA) or the public.

Description: NOTE Former CDDA_Dissemination_code in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: CddaDisseminationCodeValue (code list)

Values eeaOnlyInternal No dissemination, only for EEA internal use

eeaPartnersInternal No dissemination, except to UNEP-WCMC for internal use

CDDA-INSPIRE reporting data model. 45Description of Processes, Tools, and Deliverables

Page 46: WISE Technical Report -    file · Web viewWISE Technical Report -

public Yes, public dissemination by EEA allowed

Attribute:

Name: eionetChangeDate

Title: Eionet Change Date

Definition: The date the site record was edited.

Description: NOTE Former EIONET_CHNG_DATE in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: Date

Attribute:

Name: eionetChangeType

Title: Eionet Change Type

Definition: The type of change to the site record.

Description: NOTE Former EIONET_CHNG_TYPE in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: EionetChangeTypeValue (code list)

Values errorCorrection Correction or a real error. Not an update.

newRecord Additional new record added to Sites table

updatedField A field was updated to a more recent value or text

Attribute:

Name: eionetEditedBy

Title: Eionet Edited By

Definition: The name of the person who did the actual editing of the data.

Description: NOTE Former EIONET_EDITED_BY in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: CharacterString

46 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 47: WISE Technical Report -    file · Web viewWISE Technical Report -

Attribute:

Name: eionetInstitute

Title: Eionet Institute

Definition: The abbreviation of the institution responsible for editing of the record.

Description: NOTE Former EIONET_INSTITUTE in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: CharacterString

Attribute:

Name: geometry

Definition: The geometry defining the boundary of the Protected Site.

Description: The geometry may be determined by a wide range of methods, including surveying, digitisation or visual reference to natural features or cadastral boundaries and may be defined by the legal document that creates the protected area. The geometry included in a data set that uses this data model is stored as a fixed geometry by coordinates, not by reference to natural, cadastral or administrative boundaries, although it may originally have been defined from these.

Voidable: false

Multiplicity: 1

Value type: GM_Object

Attribute:

Name: inspireID

Definition: External object identifier of the protected site.

Description: NOTE An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.

Voidable: false

Multiplicity: 1

Value type: Identifier (data type)

Attribute:

CDDA-INSPIRE reporting data model. 47Description of Processes, Tools, and Deliverables

Page 48: WISE Technical Report -    file · Web viewWISE Technical Report -

Name: isoCountryCode

Title: Iso country code

Definition: ISO 3 character code for the reporting country.

Description: NOTE Former PARENT_ISO in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: Iso3CountryEntityValue (code list)

Values ABW Aruba

AFG Afghanistan

...

ZWE Zimbabwe

Attribute:

Name: isoEntityCode

Title: Iso entity code

Definition: ISO 3 character code for the reporting entity, being country, autonomous or overseas region or community, or other territory (e.g. overseas entities as Outermost Regions or Overseas Countries and Territories).

Description: NOTE Former ISO3 in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: Iso3CountryEntityValue (code list)

Values ABW Aruba

AFG Afghanistan

...

ZWE Zimbabwe

Attribute:

Name: iucnCat

Title: IucnCat

Definition: IUCN protected area management categories (2008) classify protected areas

48 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 49: WISE Technical Report -    file · Web viewWISE Technical Report -

according to their management objectives. The categories are recognized by international bodies such as the United Nations and by many national governments as the global standard for defining and recording protected areas and as such are increasingly being incorporated into government legislation.

Description: NOTE 1 IucnCat is the same as IUCNDesignation.

NOTE 2 Former IUCNCAT in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: IucnCatValue (code list)

Values II Large natural or near natural areas set aside to protect large-scale ecological processes, along with the complement of species and ecosystems characteristic of the area, which also provide a foundation for environmentally and culturally compatible, spiritual, scientific, educational, recreational, and visitor opportunities.

III Protected areas set aside to protect a specific natural monument, which can be a landform, sea mount, submarine cavern, geological feature such as a cave, or even a living feature such as an ancient grove. They are generally quite small protected areas and often have high visitor value.

IV Protected areas aiming to protect particular species or habitats, their management reflects this priority. Many Category IV protected areas will need regular, active interventions to address the requirements of particular species or to maintain habitats, but this is not a requirement of the category.

Ia Strictly protected areas set aside to protect biodiversity and also possibly geological/geomorphologic features, where human visitation, use and impacts are strictly controlled and limited to ensure protection of the conservation values. Such protected areas can serve as indispensable reference areas for scientific research and monitoring.

Ib Usually large unmodified or slightly modified areas, retaining their natural character and influence without permanent or significant human habitation, which are protected and managed so as to preserve their natural condition.

V A protected area where the interaction of people and nature over time has produced an area of distinct character with significant, ecological, biological, cultural and scenic value: and where safeguarding the integrity of this interaction is vital to protecting and sustaining the area and its associated nature conservation and other values.

VI Protected areas that conserve ecosystems and habitats together with associated cultural values and traditional natural resource management systems. They are generally large, with most of the area in a natural condition, where a proportion is under

CDDA-INSPIRE reporting data model. 49Description of Processes, Tools, and Deliverables

Page 50: WISE Technical Report -    file · Web viewWISE Technical Report -

sustainable natural resource management and where low-level non-industrial use of natural resources compatible with nature conservation is seen as one of the main aims of the area.

notApplicable

The IUCN management categories are not applicable to a specific designation type (e.g. Natura 2000 sites, World Heritage Sites).

notAssigned A protected area whereby the data provider has chosen not to use the IUCN management categories.

notReported The IUCN management category has not been reported.

Attribute:

Name: legalFoundationDate

Definition: The date that the protected site was legally created. This is the date that the real world object was created, not the date that its representation in an information system was created.

Description: NOTE In the case of Natura2000 sites, a protected site may go through several different stages (for example, proposed as SCI, confirmed as SCI, designated as SAC). A new version of the site is created for each of these different stages (because there is a change in the designation), and the new version should have the date on which the new stage was legally assigned as the legalFoundationDate (for example, when designated as a SAC, the version for the SAC would have the designation date as the legalFoundationDate).

Voidable: true

Multiplicity: 1

Value type: DateTime

Attribute:

Name: legalFoundationDocument

Definition: A URL or text citation referencing the legal act that created the Protected Site.

Voidable: true

Multiplicity: 1

Value type: CI_Citation (data type)

Attribute:

Name: majorEcosystemType

Title: Major ecosystem type

Definition: The type of the major ecosystem.

Description: NOTE 1 The major ecosystem type can be: marine, marine and terrestrial (incl.

50 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 51: WISE Technical Report -    file · Web viewWISE Technical Report -

freshwater) or terrestrial (incl. freshwater).

NOTE 2 Former Major_ecosystem_type in CDDA Reporting

Voidable: false

Multiplicity: 1

Value type: MajorEcosystemTypeValue (code list)

Values marine Marine

marineAndTerrestrial Marine and terrestrial (incl. freshwater)

terrestrial Terrestrial (incl. freshwater)

Attribute:

Name: marineAreaPercentage

Title: Marine area percentage

Definition: Percentage of the total area of marine ecosystems in the site.

Description: NOTE Former Marine_area_perc in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: Decimal

Attribute:

Name: nationalId

Title: National id

Definition: The National ID is the unique identifier for the site in the national database on designated areas.

Description: NOTE 1 The National code is mandatory when the field protectedAreaType = protectedSite. When the field protectedAreaType = protectedBoundary, the National code is optional.

NOTE 2 Former SITE_CODE_NAT in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: CharacterString

Attribute:

Name: protectedAreaType

CDDA-INSPIRE reporting data model. 51Description of Processes, Tools, and Deliverables

Page 52: WISE Technical Report -    file · Web viewWISE Technical Report -

Title: Protected area type

Definition: Indicate whether the spatial object is a protected site or a protected area. The protected area could be e.g. sets of areas are under general protection because of the occurrence of a specific habitat type (this could be raised bogs, specific meadow types, etc). Another example for protected area could be when sets of areas are designated by the type of organisation managing the sites (this could e.g. be sites managed for nature purposes by NGOs).

Voidable: false

Multiplicity: 1

Value type: ProtectedAreaTypeValue (code list)

Values protectedSite Protected sites are designated by national legislation with the intent to protect fauna, flora and habitats.

protectedBoundary Protected boundaries are designated areas (often sets of areas) which provides adequate and durable protection for fauna, flora and habitats through national, sectorial or private statutes.

Attribute:

Name: remark

Title: Remark

Definition: Remarks about the site record.

Description: NOTE Former NOTES in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: CharacterString

Attribute:

Name: representativePoint

Title: Representative point

Definition: Geographical Co-ordinate in decimal degrees.

Description: NOTE Former LAT and LON in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: GM_Point

Attribute:

52 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 53: WISE Technical Report -    file · Web viewWISE Technical Report -

Name: resolutionCode

Title: Resolution code

Definition: Codes for spatial resolution of dataset from which geographical data for this feature (boundaries, coordinates) has been derived.

Description: NOTE Former CDDA_Resolution_code in CDDA Reporting.

Voidable: false

Multiplicity: 0..1

Value type: CddaResolutionCodeValue (code list)

Values metadataResolution Use resolution information provided in metadata for the spatial dataset

scale100K-250K Between 1:100 000 and 1:250 000

scale250K-1M Between 1:250 000 and 1:1 000 000

scaleLarger100K More than 1:100 000

scaleSmaller1M Smaller than 1:1 000 000

unknown Unknown

Attribute:

Name: siteDesignation

Definition: The designation (type) of Protected Site.

Description: At least one designation is required, but designations may be available using a number of different designation schemes, all of which can be accommodated in the DesignationSchemeValue codelist.

Voidable: true

Multiplicity: 1..*

Value type: DesignationType (data type)

Attribute:

Name: siteEnded

Title: Site ended

Definition: To be able to maintain the central data base, sites which are not valid any more can be marked for deletion in this field.

Description: NOTE 1 Former To_be_deleted in CDDA Reporting.

CDDA-INSPIRE reporting data model. 53Description of Processes, Tools, and Deliverables

Page 54: WISE Technical Report -    file · Web viewWISE Technical Report -

NOTE 2 When a site has been marked for deletion, the Remarks field in the Sites table should be used to indicate the reason for doing so.

Voidable: false

Multiplicity: 0..1

Value type: Boolean

Attribute:

Name: siteName

Definition: The name of the Protected Site.

Description: NOTE 1 Several names in different languages may be expressed.

NOTE 2 It is recommended that the language of the name (part of the GeographicalName data type) be filled where ever possible. This is an important identifying attribute of a Protected Site.

Voidable: true

Multiplicity: 0..*

Value type: GeographicalName (data type)

Attribute:

Name: siteProtectionClassification

Definition: The classification of the protected site based on the purpose for protection.

Description: The site may have more than one classification.

Voidable: true

Multiplicity: 1..*

Value type: ProtectionClassificationValue (enumeration)

Values natureConservation

The Protected Site is protected for the maintenance of biological diversity.

archaeological The Protected Site is protected for the maintenance of archaeological heritage.

cultural The Protected Site is protected for the maintenance of cultural heritage.

ecological The Protected Site is protected for the maintenance of ecological stability.

landscape The Protected Site is protected for the maintenance of

54 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 55: WISE Technical Report -    file · Web viewWISE Technical Report -

landscape characteristics.

environment The Protected Site is protected for the maintenance of environmental stability.

geological The Protected Site is protected for the maintenance of geological characteristics.

Attribute:

Name: spatialDataAvailability

Title: Spatial data availability

Definition: Provides information if boundaries for designated areas are available in the countries for their reporting to the CDDA.

Description: NOTE Former CDDA_Availability_code in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: CddaAvailabilityCodeValue (code list)

Values notAvailable Boundaries not available

notRelevant Boundaries not relevant for analysis at European scale. Point or line feature.

reportedToEEA Boundaries reported to EEA

underPreparation Boundaries under preparation

Attribute:

Name: spatialDataDissemination

Title: Spatial data dissemination

Definition: Code for instructions to EEA regarding further dissemination of geographical data (boundaries) to partners (WDPA) or the public.

Description: NOTE Former CDDA_Dissemination_code in CDDA Reporting.

Voidable: false

Multiplicity: 1

Value type: CddaDisseminationCodeValue (code list)

Values eeaOnlyInternal No dissemination, only for EEA internal use

eeaPartnersInternal No dissemination, except to UNEP-WCMC for internal use

public Yes, public dissemination by EEA allowed

CDDA-INSPIRE reporting data model. 55Description of Processes, Tools, and Deliverables

Page 56: WISE Technical Report -    file · Web viewWISE Technical Report -

Constraint:

Name: NationalIdForSites

Description: National id is mandatory for protected sites

Expression: inv: self.protectedAreaType = ProtectedAreaTypeValue::protectedSite implies self.nationalId->notEmpty()

Constraint:

Name: noGeometry

Description: spatialDataAvailability != spatialDataAvailabilityValue::reportedToEEA implies self.geometry = (0,0)

Expression: inv: self.spatialDataAvailability <> CddaAvailabilityCodeValue::reportedToEEA implies self.geometry -> size() = 0

56 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 57: WISE Technical Report -    file · Web viewWISE Technical Report -

Feature Catalogue DesignationType_V3.0Version:

3.0Date:

18/02/2016Scope:

This feature catalogue compiles designation description informationResponsible organisation:

European Environment AgencyApplication schema: Designation Type DescriptionDefinition:

Description of national and international designation types relevant to the European region.Version:

3.0DesignationTypeDescriptionDesignationTypeDescription

Title: Designation type descriptionDefinition: List of national and international designations types relevant to the

European region.Type: Feature type

Attribute:Name: categoryTitle: CategoryDefinition: The designation type category (A, B or C) is a categorisation of national

designation types deriving from CDDA reporting.

The categories are also mentioned in the Natura 2000 Standard Data Form Explanatory notes and in the Emerald Standard Data Form Explanatory notes.

Voidable: falseMultiplicity: 1Value type: CategoryValue (code list)Values A Designation types used with the intention to

protect fauna, flora, habitats and landscapes (the latter as far as relevant for fauna, flora and for habitat protection)

B Statutes under sectorial, particularly forestry, legislative and administrative acts providing an adequate protection relevant for fauna, flora and habitat conservation

C Private statute providing durable protection for fauna, flora or habitats

Attribute:Name: competentAuthorityTitle: Competent AuthorityDefinition: CompetentAuthority for the designation.Description: NOTE Former Agency in CDDA Reporting is included.Voidable: falseMultiplicity: 0..*Value type: RelatedParty (data type)

Attribute:Name: creatingSitesTitle: Creating sitesDefinition: Flag to indicate whether the designation type does or does not create sites.Description: NOTE A "True" in this field indicates that the relevant data flow

(CDDA/Natura 2000/Emerald) should contain sites data for this designation.

Voidable: falseMultiplicity: 1

CDDA-INSPIRE reporting data model. 57Description of Processes, Tools, and Deliverables

Page 58: WISE Technical Report -    file · Web viewWISE Technical Report -

Value type: BooleanAttribute:

Name: designationCodeTitle: Designation codeDefinition: The designation type code list is a sequential list of the relevant nature

conservation designation types which have statutory protection with their definition from the national/regional level.

The codes are used in the Natura 2000 Standard Data Form, in the Emerald Standard Data Form and in the CDDA reporting.

Description: NOTE 1 designationCode is the identifier of DesignationDescription feature type.

NOTE 2 Former DESIGN_ABBR in CDDA Reporting.Voidable: falseMultiplicity: 1Value type: ProtectedAreaDesignationValue (code list)Values AL00 No Protection Status

AL01 National Park (category II)...XK08 Elements of agricultural landscape

Attribute:Name: designationNameTitle: Designation nameDefinition: Title in original language and English translation of the official title of the

designation type.Description: NOTE Former ODESIGNATE and DESIGNATE in CDDA Reporting.Voidable: falseMultiplicity: 1..*Value type: LocalisedCharacterString

Attribute:Name: designationPeriodTitle: Designation periodDefinition: Time period defining when the designation type was legally established

or became effective in the real world.Voidable: falseMultiplicity: 1Value type: TM_Period

Attribute:Name: isoCountryCodeTitle: Iso country codeDefinition: ISO 3 character code for the reporting countryDescription: NOTE Former PARENT_ISO in CDDA Reporting.Voidable: falseMultiplicity: 0..1Value type: Iso3CountryEntityValue (code list)Values ABW Aruba

AFG Afghanistan...ZWE Zimbabwe

Attribute:Name: isoEntityCodeTitle: Iso entity codeDefinition: ISO 3 character code for the reporting entity, being country, autonomous

or overseas region or community, or other territory (e.g. overseas entities as Outermost Regions or Overseas Countries and Territories).

Description: NOTE Former ISO3 in CDDA Reporting.Voidable: false

58 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 59: WISE Technical Report -    file · Web viewWISE Technical Report -

Multiplicity: 0..1Value type: Iso3CountryEntityValue (code list)Values ABW Aruba

AFG Afghanistan...ZWE Zimbabwe

Attribute:Name: legalReferenceTitle: Legal referenceDefinition: The legal context, in which the management and regulation of the

designation is defined.Description: NOTE Former Law and Law reference in CDDA Reporting.Voidable: falseMultiplicity: 0..*Value type: LegislationCitation

Attribute:Name: remarkTitle: RemarkDefinition: Remarks concerning the designation.Voidable: falseMultiplicity: 0..1Value type: CharacterString

Attribute:Name: remarkSourceTitle: Remark sourceDefinition: Reference to source of information for the remarks.Voidable: falseMultiplicity: 0..1Value type: CharacterString

Association roleName: supersededByTitle: supersededByDefinition: In a genealogy, the newly active NationalDesignations(s) that

replaces(replace) the superseded one.Voidable: trueMultiplicity: 0..*Value type: Error: Reference source not found (feature type)

Association roleName: supersedesTitle: supersedesDefinition: In a genealogy, the NationalDesignations(s) that has(have) been

deactivated/replaced by another one.Voidable: trueMultiplicity: 0..*Value type: Error: Reference source not found (feature type)

Constraint:Name: DesignationDescriptionIsoCountryCodeRequiredDescription: If legalReference.level is national or sub-national, then isoCountryCode is

required for Designation DescriptionExpression: inv: if self.legalReference.level = 'national' or self.legalReference.level =

'sub-national' then self.isoCountryCode -> notEmpty() else null endif

CDDA-INSPIRE reporting data model. 59Description of Processes, Tools, and Deliverables

Page 60: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 3. GML schema

60 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 61: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA-INSPIRE reporting data model. 61Description of Processes, Tools, and Deliverables

Page 62: WISE Technical Report -    file · Web viewWISE Technical Report -

62 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 63: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA-INSPIRE reporting data model. 63Description of Processes, Tools, and Deliverables

Page 64: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 4. Configuration file: ShapeChange

64 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 65: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 5. Constraints and Schematron rules

CddaReporting

Constraint:Name: NationalIdForSitesDescription: National id is mandatory for protected sitesExpression: inv: self.protectedAreaType =

ProtectedAreaTypeValue::protectedSite implies self.nationalId->notEmpty()

Schematron Rule:<assert test="cdda:protectedAreaType/@xlink:href != 'protectedSite' or cdda:nationalId">NationalIdForSites: National id is mandatory for protected sites </assert>Constraint:

Name: noGeometryDescription: spatialDataAvailability !=

spatialDataAvailabilityValue::reportedToEEA implies self.geometry = (0,0)

Expression: inv: self.spatialDataAvailability <> CddaAvailabilityCodeValue::reportedToEEA implies self.geometry -> size() = 0

Schematron Rule:<assert test="cdda:spatialDataAvailability/@xlink:href = 'reportedToEEA' or count(ps:geometry/*) = 0">noGeometry: spatialDataAvailability != spatialDataAvailabilityValue::reportedToEEA implies self.geometry = (0,0)</assert>

DesignationType

Constraint:Name: DesignationDescriptionIsoCountryCodeRequiredDescription: If legalReference.level is national or sub-national, then

isoCountryCode is required for Designation DescriptionExpression: inv: if self.legalReference.level = 'national' or

self.legalReference.level = 'sub-national' then self.isoCountryCode -> notEmpty() else null endif

Schematron Rule:<assert test="designationType:isoCountryCode/@xlink:href[$A] | /*[false()][not($A)]">DesignationDescriptionIsoCountryCodeRequired: If legalReference.level is national or sub-national, then isoCountryCode is required for Designation Description</assert>

CDDA-INSPIRE reporting data model. 65Description of Processes, Tools, and Deliverables

Page 66: WISE Technical Report -    file · Web viewWISE Technical Report -

Additional Schematron Rules

?xml version="1.0" encoding="UTF-8"?><sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" xml:lang="en">

<sch:title>Schematron constraints for AQD e-Reporting Zones</sch:title><sch:ns prefix="sch" uri="http://purl.oclc.org/dsdl/schematron"/><sch:ns prefix="gml" uri="http://www.opengis.net/gml/3.2"/><sch:ns prefix="xlink" uri="http://www.w3.org/1999/xlink"/><sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/><sch:ns prefix="skos" uri="http://www.w3.org/2004/02/skos/core#"/><sch:ns prefix="rdf" uri="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/><sch:ns prefix="cdda" uri="http://dd.eionet.europa.eu/schemaset/cdda"/><sch:ns prefix="ps" uri="http://inspire.ec.europa.eu/schemas/ps/4.0"/>

<!--<skos:Concept rdf:about="http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/IUCN">http://inspire.ec.europa.eu/codelist/DesignationSchemeValue/IUCN/rdf:RDF/skos:Concept[2]/skos:exactMatch/@rdf:resource

/gml:FeatureCollection/gml:featureMember[3]/cdda:DesignatedArea/ps:siteDesignation[2]/ps:DesignationType/ps:designationScheme/@xlink:href-->

<sch:pattern><sch:title>Designation Scheme from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="designationScheme"

value="./ps:siteDesignation/ps:DesignationType/ps:designationScheme/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$designationScheme]" /><sch:let name="dictMatch" value="$codelist/rdf:RDF/skos:Concept/skos:exactMatch[@rdf:resource =

$designationScheme]" /><sch:assert test=" $inDictionary or $dictMatch" >

CDDA Rule 1: Designation Scheme from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Designation Scheme [<sch:value-of select="$designationScheme"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/

</sch:assert></sch:rule>

</sch:pattern>

<!--/gml:FeatureCollection/gml:featureMember/cdda:DesignatedArea/ps:siteDesignation[1]/ps:DesignationType/ps:designationScheme/@xlink:href-->

<!-- CDDA Designation Type from Codelist --><sch:pattern>

<sch:title>CDDA Designation from Codelist</sch:title><sch:rule context="//cdda:DesignatedArea/ps:siteDesignation/ps:DesignationType">

<sch:let name="gmlid" value="./../../@gml:id"/><sch:let name="designationScheme" value="./ps:designationScheme/@xlink:href"/><sch:let name="designation" value="./ps:designation/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $designation]" /><sch:assert test="(($designationScheme and (compare($designationScheme,

'http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda') = 0) and $inDictionary) or ($designationScheme and (compare($designationScheme, 'http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda') != 0 )))" >

CDDA Rule 2: Designation Type from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Designation [<sch:value-of select="$designation"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue although designationScheme set to cdda

</sch:assert></sch:rule>

</sch:pattern>

<!-- CDDA Designation provided --><sch:pattern>

<sch:title>CDDA Designation provided</sch:title>

66 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 67: WISE Technical Report -    file · Web viewWISE Technical Report -

<sch:rule context="//cdda:DesignatedArea"><sch:let name="gmlid" value="./@gml:id"/><sch:let name="siteInfo" value="./."/><sch:let name="designationAvailable"

value="$siteInfo/ps:siteDesignation/ps:DesignationType/ps:designationScheme[@xlink:href='http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda']"/>

<sch:assert test="$designationAvailable" >CDDA Rule 3: CDDA Designation provided - DesignatedArea [<sch:value-of

select="$gmlid"/>]: No Designation from designation scheme CDDA http://dd.eionet.europa.eu/vocabulary/inspire/DesignationSchemeValue/cdda

</sch:assert></sch:rule>

</sch:pattern><!--http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaTypeValue//gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:protectedAreaType/@xlink:href-->

<!-- Protected Area Type from Codelist --><sch:pattern>

<sch:title>Protected Area Type from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="protectedAreaType" value="./cdda:protectedAreaType/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaTypeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$protectedAreaType]" /><sch:assert test=" $inDictionary" >

CDDA Rule 4: Protected Area Type from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Protected Area Type [<sch:value-of select="$protectedAreaType"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaTypeValue

</sch:assert></sch:rule>

</sch:pattern>

<!--/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:majorEcosystemType/@xlink:hrefhttp://dd.eionet.europa.eu/vocabulary/cdda/MajorEcosystemTypeValue-->

<!-- Major Ecosystem Type from Codelist --><sch:pattern>

<sch:title>Major Ecosystem Type from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="majorEcosystemType" value="./cdda:majorEcosystemType/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/MajorEcosystemTypeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$majorEcosystemType]" /><sch:assert test=" $inDictionary" >

CDDA Rule 5: Major Ecosystem Type from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Major Ecosystem Type [<sch:value-of select="$majorEcosystemType"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/MajorEcosystemTypeValue

</sch:assert></sch:rule>

</sch:pattern>

<!--http://dd.eionet.europa.eu/vocabulary/cdda/IucnCatValue/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:iucnCat/@xlink:href-->

<!-- IUCN Category from Codelist --><sch:pattern>

<sch:title>IUCN Category from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="iucnCat" value="./cdda:iucnCat/@xlink:href"/><sch:let name="codelist" value="document('http://dd.eionet.europa.eu/vocabulary/cdda/IucnCatValue/

rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $iucnCat]" /><sch:assert test=" $inDictionary" >

CDDA Rule 6: IUCN Category from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: IUCN Category [<sch:value-of select="$iucnCat"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/IucnCatValue

</sch:assert>

CDDA-INSPIRE reporting data model. 67Description of Processes, Tools, and Deliverables

Page 68: WISE Technical Report -    file · Web viewWISE Technical Report -

</sch:rule></sch:pattern>

<!--http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue/HRV/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:isoCountryCode/@xlink:href-->

<!-- ISO 3 Country Code from Codelist --><sch:pattern>

<sch:title>ISO 3 Country Code from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="isoCode" value="./cdda:isoCountryCode/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $isoCode]" /><sch:assert test=" $inDictionary" >

CDDA Rule 7: ISO 3 Country Code from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: ISO 3 Country Code [<sch:value-of select="$isoCode"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue

</sch:assert></sch:rule>

</sch:pattern>

<!-- ISO 3 Entity Code from Codelist --><sch:pattern>

<sch:title>ISO 3 Entity Code from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="isoCode" value="./cdda:isoEntityCode/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $isoCode]" /><sch:assert test="(string-length($isoCode)= 0) or $inDictionary" >

CDDA Rule 8: ISO 3 Entity Code from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: ISO 3 Entity Code [<sch:value-of select="$isoCode"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue

</sch:assert></sch:rule>

</sch:pattern>

<!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaCoordinatesCodeValue/eeaCalculation/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:coordinatesCode/@xlink:href-->

<!-- Coordinates Code Value from Codelist --><sch:pattern>

<sch:title>Coordinates Code Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="coordinatesCode" value="./cdda:coordinatesCode/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/CddaCoordinatesCodeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$coordinatesCode]" /><sch:assert test=" $inDictionary" >

CDDA Rule 9: Coordinates Code Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Coordinates Code Value [<sch:value-of select="$coordinatesCode"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/CddaCoordinatesCodeValue

</sch:assert></sch:rule>

</sch:pattern>

<!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:spatialDataAvailability/@xlink:href-->

<!-- Spatial Data Availability Value from Codelist --><sch:pattern>

68 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 69: WISE Technical Report -    file · Web viewWISE Technical Report -

<sch:title>Spatial Data Availability Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="spatialDataAvailability" value="./cdda:spatialDataAvailability/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$spatialDataAvailability]" /><sch:assert test=" $inDictionary" >

CDDA Rule 10: Spatial Data Availability Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Spatial Data Availability Value [<sch:value-of select="$spatialDataAvailability"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue

</sch:assert></sch:rule>

</sch:pattern><!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:spatialDataDissemination-->

<!-- Spatial Data Dissemination Value from Codelist --><sch:pattern>

<sch:title>Spatial Data Dissemination Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="spatialDataDissemination" value="./cdda:spatialDataDissemination/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$spatialDataDissemination]" /><sch:assert test=" $inDictionary" >

CDDA Rule 11: Spatial Data Dissemination Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Spatial Data Dissemination Value [<sch:value-of select="$spatialDataDissemination"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue

</sch:assert></sch:rule>

</sch:pattern><!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:dataDissemination-->

<!-- Data Dissemination Value from Codelist --><sch:pattern>

<sch:title>Data Dissemination Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="dataDissemination" value="./cdda:dataDissemination/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $dataDissemination]"

/><sch:assert test=" $inDictionary" >

CDDA Rule 12: Data Dissemination Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Data Dissemination Value [<sch:value-of select="$dataDissemination"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/CddaDisseminationCodeValue

</sch:assert></sch:rule>

</sch:pattern><!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaResolutionCodeValue//gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:resolutionCode/@xlink:href-->

<!-- Resolution Code Value from Codelist --><sch:pattern>

<sch:title>Resolution Code Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="resolutionCode" value="./cdda:resolutionCode/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/CddaResolutionCodeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about = $resolutionCode]" /><sch:assert test=" $inDictionary" >

CDDA-INSPIRE reporting data model. 69Description of Processes, Tools, and Deliverables

Page 70: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA Rule 13: Resolution Code Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: Spatial Data Dissemination Value [<sch:value-of select="$resolutionCode"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/CddaResolutionCodeValue/

</sch:assert></sch:rule>

</sch:pattern><!--http://dd.eionet.europa.eu/vocabulary/cdda/EIONETChangeTypeValue/errorCorrection/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:eionetChangeType/@xlink:href-->

<!-- EIONET Change Type Value from Codelist --><sch:pattern>

<sch:title>EIONET Change Type Value from Codelist </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="eionetChangeType" value="./cdda:eionetChangeType/@xlink:href"/><sch:let name="codelist"

value="document('http://dd.eionet.europa.eu/vocabulary/cdda/EIONETChangeTypeValue/rdf')" /><sch:let name="inDictionary" value="$codelist/rdf:RDF/skos:Concept[@rdf:about =

$eionetChangeType]" /><sch:assert test=" $inDictionary" >

CDDA Rule 14: EIONET Change Type Value from Codelist - DesignatedArea [<sch:value-of select="$gmlid"/>]: EIONET Change Type Value [<sch:value-of select="$eionetChangeType"/>] not valid according to codelist http://dd.eionet.europa.eu/vocabulary/cdda/EIONETChangeTypeValue/

</sch:assert></sch:rule>

</sch:pattern>

<!-- Nilreason valid --><sch:pattern>

<sch:title>Nilreason valid</sch:title><sch:rule context="@xsi:nil">

<sch:let name="gmlid" value="//cdda:DesignatedArea/@gml:id"/><sch:let name="nil" value="./."/><sch:let name="nilReason" value="../@nilReason"/><sch:let name="codelist" value="document('http://inspire.ec.europa.eu/codelist/VoidReasonValue/

VoidReasonValue.en.rdf')" /><sch:let name="inDictionary"

value="$codelist/rdf:RDF/rdf:Description/skos:hasTopConcept[@rdf:resource = $nilReason]" /><sch:assert test="($nil = 'false') or $inDictionary" >

CDDA Rule 15: Nilreason valid - DesignatedArea [<sch:value-of select="$gmlid"/>]: nilreason [<sch:value-of select="$nilReason"/>] although nil is [<sch:value-of select="$nil"/>]

</sch:assert></sch:rule>

</sch:pattern>

<!--http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue/gml:FeatureCollection/gml:featureMember[1]/cdda:DesignatedArea/cdda:spatialDataAvailability/@xlink:href-->

<!-- Geometry provided if CddaAvailabilityCodeValue = reportedToEEA --><sch:pattern>

<sch:title>Geometry provided if CddaAvailabilityCodeValue = reportedToEEA </sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="spatialDataAvailability" value="./cdda:spatialDataAvailability/@xlink:href"/><sch:let name="pos" value="./ps:geometry//gml:pos"/><sch:let name="posList" value="./ps:geometry//gml:posList"/>

<sch:let name="testCase" value="( (($spatialDataAvailability and (compare($spatialDataAvailability, 'http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue/reportedToEEA') != 0) ))

or (($spatialDataAvailability and (compare($spatialDataAvailability,

'http://dd.eionet.europa.eu/vocabulary/cdda/CddaAvailabilityCodeValue/reportedToEEA') = 0 )) and ((string-length($pos) > 0) or (string-length($posList) > 0) or (count(ps:geometry/*) = 0))) )"/><sch:assert test="$testCase" >

CDDA Rule 16: Geometry provided if CddaAvailabilityCodeValue = reportedToEEA - DesignatedArea [<sch:value-of select="$gmlid"/>]: Spatial Data Availability Value = reportedToEEA [<sch:value-of select="$spatialDataAvailability"/>] but no spatial information available for either Point [<sch:value-of select="$pos"/>] or Polygon [<sch:value-of select="$posList"/>]

</sch:assert>

70 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 71: WISE Technical Report -    file · Web viewWISE Technical Report -

</sch:rule></sch:pattern>

<!-- National ID provided if Protected Area Type protectedSite --><sch:pattern>

<sch:title>National ID provided if Protected Area Type protectedSite</sch:title><sch:rule context="//cdda:DesignatedArea">

<sch:let name="gmlid" value="./@gml:id"/><sch:let name="protectedAreaType" value="./cdda:protectedAreaType/@xlink:href"/><sch:let name="nationalId" value="./cdda:nationalId" /><sch:let name="testCase" value="($nationalId or (compare($protectedAreaType,

'http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaTypeValue/protectedSite') != 0))"/><sch:assert test="$testCase" >

CDDA Rule 17: National ID provided if Protected Area Type protectedSite - DesignatedArea [<sch:value-of select="$gmlid"/>]: Protected Area Type [<sch:value-of select="$protectedAreaType"/>] National ID [<sch:value-of select="$nationalId"/>]

</sch:assert></sch:rule>

</sch:pattern></sch:schema>

CDDA-INSPIRE reporting data model. 71Description of Processes, Tools, and Deliverables

Page 72: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 6. Matching Tables

Example of matching table for Designated Areas: The complete matching table can be found at https://taskman.eionet.europa.eu/issues/69412

72 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 73: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA-INSPIRE reporting data model. 73Description of Processes, Tools, and Deliverables

Page 74: WISE Technical Report -    file · Web viewWISE Technical Report -

Example of matching table for Designation Types: The matching table can be found at https://taskman.eionet.europa.eu/issues/69415

74 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 75: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 7. Input source data

The source data model correspond to the CDDA data model V13

CDDA-INSPIRE reporting data model. 75Description of Processes, Tools, and Deliverables

Page 76: WISE Technical Report -    file · Web viewWISE Technical Report -

Example of Designated Area data

76 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 77: WISE Technical Report -    file · Web viewWISE Technical Report -

Example of Designation Type data

CDDA-INSPIRE reporting data model. 77Description of Processes, Tools, and Deliverables

Page 78: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 8. HALE alignment project

Example of DesignationType alignment

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><alignment xmlns="http://www.esdi-humboldt.eu/hale/alignment"> <cell relation="eu.esdihumboldt.hale.align.retype" id="C14c93002-a629-49b6-983c-6a422fe7da9f" priority="normal"> <source> <class> <type name="_cdda_designations"/> </class> </source> <target> <class> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> </class> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign" id="C83560c95-372b-4fc6-9ec3-8e294e4d1bfc" priority="normal"> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationName" ns="http://dd.eionet.europa.eu/schemaset/cdda"> <context>0</context> </child> <child name="lang" ns="http://www.w3.org/XML/1998/namespace"/> </property> </target> <parameter value="eng" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="C71ef5036-2b95-4b13-9c21-e78d189829a4" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Lawreference"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="journalCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="OfficialJournalInformation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="officialJournalIdentification" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign" id="C3a1dcc3e-5cba-45e1-890a-8b78ef5877af" priority="normal"> <target>

78 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 79: WISE Technical Report -    file · Web viewWISE Technical Report -

<property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="level" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="href" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="http://dd.eionet.europa.eu/vocabularyconcept/inspire/LegislationLevelValue/national" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign" id="Cf9eb50d0-ceea-4ec5-a7e4-30606b2c4ecb" priority="normal"> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="level" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="title" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="National level" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="Cca6d1c1a-348e-4aff-a552-2c4bc8c4fb48" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="From"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationPeriod" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="TimePeriod" ns="http://www.opengis.net/gml/3.2"/> <child name="choice_1" ns="http://www.opengis.net/gml/3.2/TimePeriodType"/> <child name="beginPosition" ns="http://www.opengis.net/gml/3.2"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="C10ef8775-8a64-42e6-8971-ae3071485b31" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Ecolex"> <condition lang="CQL">value &lt;&gt; ''</condition> </child> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="link" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/>

CDDA-INSPIRE reporting data model. 79Description of Processes, Tools, and Deliverables

Page 80: WISE Technical Report -    file · Web viewWISE Technical Report -

</property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign.bound" id="Ca668f7e3-952d-4915-a8b8-b25b223ee455" priority="normal"> <source name="anchor"> <property> <type name="_cdda_designations"/> <child name="Ecolex"> <condition lang="CQL">value &lt;&gt; ''</condition> </child> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="link" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="nilReason"/> </property> </target> <parameter value="http://inspire.ec.europa.eu/codelist/VoidReasonValue/Unpopulated" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign" id="C46460ddb-668f-4fd9-9911-ce20ca6d98dc" priority="normal"> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="date" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="nilReason"/> </property> </target> <parameter value="http://inspire.ec.europa.eu/codelist/VoidReasonValue/Unpopulated" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.assign" id="C9d350514-ce4c-4f13-9883-cc086bcf841f" priority="normal"> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationPeriod" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="TimePeriod" ns="http://www.opengis.net/gml/3.2"/> <child name="choice_2" ns="http://www.opengis.net/gml/3.2/TimePeriodType"/> <child name="endPosition" ns="http://www.opengis.net/gml/3.2"/> </property> </target> <parameter value="2015-12-31" name="value"/> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="Cc77d0a23-f013-4968-a5ff-84846ffb8975" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="DESIG_ABBR"/>

80 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 81: WISE Technical Report -    file · Web viewWISE Technical Report -

</property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="title" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="HR01"/> <value value="&#x9;Strict Reserve"/> </entry> <entry> <key value="HR02"/> <value value="Special Reserve"/> </entry> <entry> <key value="HR03"/> <value value="National Park"/> </entry> <entry> <key value="HR04"/> <value value="&#x9;Nature Park"/> </entry> <entry> <key value="HR05"/> <value value="&#x9;Regional Park"/> </entry> <entry> <key value="HR06"/> <value value="Natural Monument"/> </entry> <entry> <key value="HR07"/> <value value="Significant Landscape"/> </entry> <entry> <key value="HR08"/> <value value="Forest Park"/> </entry> <entry> <key value="HR09"/> <value value="Horticultural Monument"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="C24f76289-5455-426f-919a-50b18f420ccf" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Odesignate"/> </property> </source> <target>

CDDA-INSPIRE reporting data model. 81Description of Processes, Tools, and Deliverables

Page 82: WISE Technical Report -    file · Web viewWISE Technical Report -

<property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationName" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="Cc95b73f8-e75e-4419-9af2-1d51a8559e8c" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Remark"> <condition lang="CQL">value &lt;&gt; ''</condition> </child> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="remark" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="C8641177d-c3f5-4e3d-85ae-e5316db87501" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Remark_source"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="remarkSource" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="C711b692d-d527-4af5-b49a-8785d5f8353f" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Category"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="category" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="href" ns="http://www.w3.org/1999/xlink"/> </property>

82 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 83: WISE Technical Report -    file · Web viewWISE Technical Report -

</target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="A"/> <value value="http://dd.eionet.europa.eu/vocabulary/cdda/CategoryValue/A"/> </entry> <entry> <key value="B"/> <value value="http://dd.eionet.europa.eu/vocabulary/cdda/CategoryValue/B"/> </entry> <entry> <key value="C"/> <value value="http://dd.eionet.europa.eu/vocabulary/cdda/CategoryValue/C"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="C76444f50-926d-4f6c-94f8-9616d763d226" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Category"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="category" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="title" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="A"/> <value value="Category A"/> </entry> <entry> <key value="B"/> <value value="Category B"/> </entry> <entry> <key value="C"/> <value value="Category B"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="C78c8ce73-75a5-4cb3-a013-4edcd521c9f7" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Agency"/> </property> </source>

CDDA-INSPIRE reporting data model. 83Description of Processes, Tools, and Deliverables

Page 84: WISE Technical Report -    file · Web viewWISE Technical Report -

<target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="competentAuthority" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="RelatedParty" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="organisationName" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="choice" ns="http://www.isotc211.org/2005/gco/CharacterString"/> <child name="CharacterString" ns="http://www.isotc211.org/2005/gco"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="Cba872a7a-35a7-40d6-a7c6-402ecea7e869" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="CDDA_sites"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="creatingSites" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> </property> </target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="true"/> <value value="true"/> </entry> <entry> <key value="false"/> <value value="false"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C76d21038-f474-455d-99d0-7a63d0213b4a" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="DESIG_ABBR"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="href" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="http://dd.eionet.europa.eu/vocabulary/cdda/ProtectedAreaDesignationValue/{DESIG_ABBR}" name="pattern"/>

84 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 85: WISE Technical Report -    file · Web viewWISE Technical Report -

</cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="Cf70401b8-baae-4d43-a84b-d4c2c9c351ad" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Designate"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationName" ns="http://dd.eionet.europa.eu/schemaset/cdda"> <context>0</context> </child> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C19347380-0dca-4d23-a522-43875f0849a6" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="DESIG_ABBR"/> </property> </source> <source name="var"> <property> <type name="_cdda_designations"/> <child name="ISO3"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="designationPeriod" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="TimePeriod" ns="http://www.opengis.net/gml/3.2"/> <child name="id" ns="http://www.opengis.net/gml/3.2"/> </property> </target> <parameter value="TP_{DESIG_ABBR}.{ISO3}" name="pattern"/> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C78407fec-a591-4a35-965e-31975f299486" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="DESIG_ABBR"/> </property> </source> <source name="var"> <property> <type name="_cdda_designations"/> <child name="ISO3"/> </property> </source> <target> <property>

CDDA-INSPIRE reporting data model. 85Description of Processes, Tools, and Deliverables

Page 86: WISE Technical Report -    file · Web viewWISE Technical Report -

<type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="id" ns="http://www.opengis.net/gml/3.2"/> </property> </target> <parameter value="DD_{DESIG_ABBR}.{ISO3}" name="pattern"/> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C19b0cb11-2be8-428b-ac86-33956fa8d9c5" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="PARENT_ISO"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="isoCountryCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="href" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue/{PARENT_ISO}" name="pattern"/> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="Cd9043096-209b-4e08-94ee-70fc52da20b9" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="PARENT_ISO"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="isoCountryCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="title" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="HRV"/> <value value="Croatia"/> </entry> <entry> <key value="ALB"/> <value value="Albania"/> </entry> <entry> <key value="AUT"/> <value value="Austria"/> </entry> <entry> <key value="BEL"/> <value value="Belgium"/> </entry>

86 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 87: WISE Technical Report -    file · Web viewWISE Technical Report -

<entry> <key value="BGR"/> <value value="Bulgaria"/> </entry> <entry> <key value="BIH"/> <value value="Bosnia and Herzegovina"/> </entry> <entry> <key value="CHE"/> <value value="Switzerland"/> </entry> <entry> <key value="CYP"/> <value value="Cyprus"/> </entry> <entry> <key value="CZE"/> <value value="Czech Republic"/> </entry> <entry> <key value="DEU"/> <value value="Germany"/> </entry> <entry> <key value="DNK"/> <value value="Denmark"/> </entry> <entry> <key value="ESP"/> <value value="Spain"/> </entry> <entry> <key value="EST"/> <value value="Estonia"/> </entry> <entry> <key value="FIN"/> <value value="Finland"/> </entry> <entry> <key value="FRA"/> <value value="France"/> </entry> <entry> <key value="GBR"/> <value value="United Kingdom of Great Britain and Northern Ireland"/> </entry> <entry> <key value="GRC"/> <value value="Greece"/> </entry> <entry> <key value="HUN"/> <value value="Hungary"/> </entry> <entry> <key value="IRL"/> <value value="Ireland"/> </entry>

CDDA-INSPIRE reporting data model. 87Description of Processes, Tools, and Deliverables

Page 88: WISE Technical Report -    file · Web viewWISE Technical Report -

<entry> <key value="ISL"/> <value value="Iceland"/> </entry> <entry> <key value="ITA"/> <value value="Italy"/> </entry> <entry> <key value="LIE"/> <value value="Liechtenstein"/> </entry> <entry> <key value="LTU"/> <value value="Lithuania"/> </entry> <entry> <key value="LUX"/> <value value="Luxembourg"/> </entry> <entry> <key value="LVA"/> <value value="Latvia"/> </entry> <entry> <key value="MKD"/> <value value="The former Yugoslav Republic of Macedonia"/> </entry> <entry> <key value="MLT"/> <value value="Malta"/> </entry> <entry> <key value="MNE"/> <value value="Montenegro"/> </entry> <entry> <key value="NLD"/> <value value="Netherlands"/> </entry> <entry> <key value="NOR"/> <value value="Norway"/> </entry> <entry> <key value="POL"/> <value value="Poland"/> </entry> <entry> <key value="PRT"/> <value value="Portugal"/> </entry> <entry> <key value="ROU"/> <value value="Romania"/> </entry> <entry> <key value="SRB"/>

88 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 89: WISE Technical Report -    file · Web viewWISE Technical Report -

<value value="Serbia"/> </entry> <entry> <key value="SVK"/> <value value="Slovakia"/> </entry> <entry> <key value="SVN"/> <value value="Slovenia"/> </entry> <entry> <key value="SWE"/> <value value="Sweden"/> </entry> <entry> <key value="TUR"/> <value value="Turkey"/> </entry> <entry> <key value="XKX"/> <value value="Kosovo (UNSCR 1244/99)"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C059d2e87-99fa-48a0-9f6c-c44d3348b003" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="ISO3"> <condition lang="CQL">parent.ISO3 &lt;&gt; parent.PARENT_ISO</condition> </child> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="isoEntityCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="href" ns="http://www.w3.org/1999/xlink"/> </property> </target> <parameter value="http://dd.eionet.europa.eu/vocabulary/cdda/Iso3CountryEntityValue/{ISO3}" name="pattern"/> </cell> <cell relation="eu.esdihumboldt.hale.align.classification" id="Ca31bedb2-2cb9-486f-a1bf-63d6a4ffcd1b" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="ISO3"> <condition lang="CQL">parent.ISO3 &lt;&gt; parent.PARENT_ISO</condition> </child> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="isoEntityCode" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="title" ns="http://www.w3.org/1999/xlink"/>

CDDA-INSPIRE reporting data model. 89Description of Processes, Tools, and Deliverables

Page 90: WISE Technical Report -    file · Web viewWISE Technical Report -

</property> </target> <parameter value="null" name="notClassifiedAction"/> <complexParameter name="lookupTable"> <lookup-table xmlns:ns2="http://www.esdi-humboldt.eu/hale/alignment" xmlns=""> <entry> <key value="ATF"/> <value value="French Southern Territories"/> </entry> <entry> <key value="BLM"/> <value value="Saint Barthélemy"/> </entry> <entry> <key value="GLP"/> <value value="Guadeloupe"/> </entry> <entry> <key value="GRL"/> <value value="Greenland"/> </entry> <entry> <key value="GUF"/> <value value="French Guiana"/> </entry> <entry> <key value="MAF"/> <value value="Saint Martin (French part)"/> </entry> <entry> <key value="MTQ"/> <value value="Martinique"/> </entry> <entry> <key value="MYT"/> <value value="Mayotte"/> </entry> <entry> <key value="REU"/> <value value="Réunion"/> </entry> <entry> <key value="SPM"/> <value value="Saint Pierre and Miquelon"/> </entry> </lookup-table> </complexParameter> </cell> <cell relation="eu.esdihumboldt.hale.align.formattedstring" id="C888e6d41-b627-4bee-9677-12b473b5ab08" priority="normal"> <source name="var"> <property> <type name="_cdda_designations"/> <child name="DESIG_ABBR"/> </property> </source> <source name="var"> <property>

90 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 91: WISE Technical Report -    file · Web viewWISE Technical Report -

<type name="_cdda_designations"/> <child name="ISO3"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="id" ns="http://www.opengis.net/gml/3.2"/> </property> </target> <parameter value="LC_{DESIG_ABBR}.{ISO3}" name="pattern"/> </cell> <cell relation="eu.esdihumboldt.hale.align.rename" id="Cbe8a6801-def3-4a97-b548-ca82cacb1baa" priority="normal"> <source> <property> <type name="_cdda_designations"/> <child name="Law"/> </property> </source> <target> <property> <type name="DesignationTypeDescriptionType" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="legalReference" ns="http://dd.eionet.europa.eu/schemaset/cdda"/> <child name="LegislationCitation" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> <child name="name" ns="http://inspire.ec.europa.eu/schemas/base2/2.0"/> </property> </target> <parameter value="false" name="ignoreNamespaces"/> <parameter value="false" name="structuralRename"/> </cell></alignment>

CDDA-INSPIRE reporting data model. 91Description of Processes, Tools, and Deliverables

Page 92: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 9. GML file

92 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 93: WISE Technical Report -    file · Web viewWISE Technical Report -

CDDA-INSPIRE reporting data model. 93Description of Processes, Tools, and Deliverables

Page 94: WISE Technical Report -    file · Web viewWISE Technical Report -

94 CDDA-INSPIRE reporting data modelDescription of Processes, Tools, and Deliverables

Page 95: WISE Technical Report -    file · Web viewWISE Technical Report -

ANNEX 10. Validation of GML file

Example: simulation of the potential errors in GML and validation outcomesA summary of possible (hypothetic) validation errors that could occur and have been fixed in the transformation process are presented below:

Example of mandatory attribute not collected:

Description: cvc-complex-type.2.4.b: The content of element 'gml:TimePeriod' is not complete. One of '{"http://www.opengis.net/gml/3.2":endPosition, "http://www.opengis.net/gml/3.2":end}' is expected.Start location: 50:14End location: 50:28 

Example of GML element identifier not collected:

Description: cvc-attribute.3: The value '' of attribute 'gml:id' on element ‘cdda:DesignatedArea’ is not valid with respect to its type, 'ID'.Start location: 4:37End location: 4:39 

Example of INSPIRE application schema target namespace not collected:

Severity: fatalDescription: The prefix "ps" for element "ps:inspireId" is not bound.Start location: 5:8End location: 5:20 

Example of CDDA application schema target namespace not collected:

Severity: fatalDescription: The prefix "cdda" for element "cdda:DesignatedArea" is not bound.Start location: 4:6End location: 4:29

CDDA-INSPIRE reporting data model. 95Description of Processes, Tools, and Deliverables