1. Framework service contract Lot 4 Project: CDDA in conformity with INSPIRE CDDA – INSPIRE PS mapping conclusions Meeting 19.-20.02.2014 Darja Lihteneger

2. Current issues and conclusions: Mapping, Transformation and validation, geometry! 17116 INSPIRE PS Simple application schema extensionsINSPIRE PS Simple application schema extensions: -Two extensions: one for categories A,B,C and one for national designation codes -Extension to DesignationSchemeValue (INSPIRE PS): -nationalDesignationTypeCategory -nationalDesignationTypeCode -Extensions to DesignationValue (INSPIRE PS): -NationalDesignationTypeCategoryValue (current A,B,C code list) -NationalDesignationTypeCodeValue (New!) -Extending code lists – rules to follow: -INSPIRE rules for naming convention -EEA preferred use of the code lists is to use the codes as they are without any additional mapping, this would mean using: -A, B, C in NationalDesignationTypeCategoryValue -AT00, AT01, BE01, … in NationalDesignationTypeCodeValue -To check with the JRC: what are the differences between INSPIRE Annex II, III and Annex I code lists which are important in data transformation in GML! 1M M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent

3. Current issues and conclusions: Mapping, Transformation and validation, geometry! 17117 CDDA - INSPIRE PS Simple application schema matching tableCDDA - INSPIRE PS Simple application schema matching table: -Element id in the matching table: -To be moved outside of the list of INSPIRE PS attributes -To add explanation of its meaning: element is required by the GML to ensure the unique id within the GML file; it is usually generated by software; -No need to link this id with any other attribute -siteName (INSPIRE PS): -SITE_NAME (CDDA) is original local name written in Latin alphabet, sometimes provided as English name -siteName (INSPIRE PS) data type is GeographicalName; only one attribute carries the name of the site, the rest will stay voidable -Kathi provided the correct GML encoding for voidable attributes within GeographicalName data type 2M M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent

4. 18236Mapping of legal references to INSPIRE PS3M 18135 IUCN protected areas management categories To make the mapping between IUCN codes in CDDA and INSPIRE PS codes for IUCN (from numbers to descriptive code) – change in the matching table and use in transformation into GML! 3M M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent Current issues and conclusions: Mapping, Transformation and validation, geometry!

5. 17114Designation of a site and its relationship to legal basis (law)3M -YEAR (CDDA) can be mapped to legalFoundationDate (INSPIRE PS): -Both attributes have very similar meaning in CDDA and in INSPIRE PS -legalFoundationDate has type DateTime -The correct format is yyyy-mm-ddTxx:xx:xx -Agreed to transfer year into date of 1 January of that year and time as 00:00:00 (for example: 1984 > 1984-01-01T00:00:00) -Feedback to INSPIRE MIG: Date format would be enough, DateTime doesn’t have any meaning! -legalFoundationDocument (INSPIRE PS): -The meaning of LAW and LAWREFERENCE in CDDA (at designation level, not site specific) is different from the meaning of legal foundation document in INSPIRE PS (site specific); therefore we can’t map CDDA to INSPIRE PS -Is voidable in mapping/transformation to INSPIRE PS -This decision needs explanation in the guidelines M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent Current issues and conclusions: Mapping, Transformation and validation, geometry!

6. 18201Inspire identifier4M 17113Unique identifier4M Attribute localId of the data type Identifier for inspireId will use the SITE_CODE from CDDA; SITE_CODE is already an unique identifier Attribute namespace of the data type Identifier for inspireId: It is defined from the data provider point of view and EEA is a data provider for the European CDDA data sets Namespace will include also link to the country codes – providers of national CDDA data, this is done by re-using the attributes from CDDA: PARENT_ISO and ISO3 Namespace compositions is confirmed, this is: EU.EUROPA.ENVIRONMENT.PS.CDDA.. Examples from matching table: Germany: EU.EUROPA.ENVIRONMENT.PS.CDDA.DEU.DEU France – Martinique: EU.EUROPA.ENVIRONMENT.PS.CDDA.FRA.MTQ M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent Current issues and conclusions: Mapping, Transformation and validation, geometry!

7. 17535 Voidable - properties with no data in INSPIRE -Voidable in INSPIRE requires to provide voidable reason from the code list -To use the voidable reason Unpopulated for all cases of voidable in mapping between CDDA to INSPIRE PS -Specific example of voidable is for attribute legalFoundationDocument (INSPIRE PS): -if the complete attribute legalFoundationDocument is voidable, then voidable follows INSPIRE voidable rules; -If the attributes of data type CI_Citation (ISO) are voidable then those attributes should follow ISO rules for nil elements! -Question for JRC: which interpretation and GML encoding of voidable elements is correct: -Voidable at the top element of legalFoundationDocument -Voidable attributes of CI_Citation data type (for example date) 5M M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent Current issues and conclusions: Mapping, Transformation and validation, geometry!

8. 18423GML transformation and validation EEA test6T&V 18249GML validation6T&V -Transformation into GML: -Agreed to transform in GML per country -Oversea territories which will require other coordinate reference system will be in separate GMLs -Rules for transformation will be the same for all! -Validation: -The discussion will continue, Tracasa and Kathi will cooperate to find the way what to use for validation M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent Current issues and conclusions: Mapping, Transformation and validation, geometry!

9. Current issues and conclusions: Mapping, Transformation and validation, geometry! 17375Converting CDDA data into GML format and file size6T&V -Agreed to split GML file into GML files per country -Countries with oversea territories: the overseas territories will be in separate GML file -To follow INSPIRE for coordinate reference systems (CRS): -ETRS89 for the “European geographic extent” -ITRS for the territories outside of the geographic scope of ETRS89 -Coordinate references systems used in Copernicus land services will be checked if they can be used -Countries CDDA deliveries will be checked if they provide the original CRS -To make a table which territories fall outside of geographic scope of ETRS89 and which countries are in this scope -GML file might include geometry with different coordinate reference systems (CRS is linked to geometry); question is how the client software can read such files? No need to explore this in our prototype! -Further discussion needed: -How to write the correct GML file? -Different software might write GML in different ways, especially INSPIRE voidable elements and void reasons -Geoconverter might no provide correct GML file?! M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent

10. Current issues and conclusions: Mapping, Transformation and validation, geometry! 18493 Creating buffers around centroids for some protected sites in CDDA 7G 18492Geometry of CDDA in the project: polygons or points or both?7G 17115Relationship between graphics and alphanumeric information7G 16794Polygons are overlapping in the CDDA7G -Geometry in CDDA: everything should be polygon -In the case the countries have points only, the EEA creates small buffers around points and includes such polygons into the common database -Centroids of polygons are created or provided by the countries, those are used for validation, display, etc. -The points geometry in the Shape file used for this project will not be included in the prototype -All CDDA polygons (all territories) are included in the prototype M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent

11. New issue and conclusions: Mapping, Transformation and validation, geometry! Percentage of site under designationNewM INSPIRE PS attribute percentageUnderDesignation (in DesignationType) Information is not explicitly in the CDDA data set but it is implicit based on the CDDA definition that only the sites with 100% area under designation are included in the CDDA; this is correct for National designation type category (A, B, C) and National designation type code For IUCN categories we cannot be sure that the site is 100% covered by the IUCN category, therefore it is proposed: Not to map to this INSPIRE PS attribute for IUCN designation; not to include attribute in GML, there is no need to provide nil reason (cardinality is 0..1)! This proposal is in conflict with INSPIRE PS definition which says: “If a value is not provided for this attribute, it is assumed to be 100%” Questions for JRC / INSPIRE MIG: how to encode no value (which has different meaning from explicitly saying 0%)? percentageUnderDesignation has a data type Percentage which is not defined in INSPIRE PS technical guidelines; where is it defined? Percentage has stereotype >; is this correct? Application schema includes information that this is URI? M – mapping T&V – transformation and validation (GML) G – geometry, CRS, extent