National datasets transformation to INSPIRE specifications with FME

Transcription

1 Instituto Geográfico Nacional National datasets transformation to INSPIRE specifications with FME Land Cover, Land Use and Orthoimageries Julián Delgado Hernández INSPIRE Clusters

2 Presentation Introduction: Scope and FME INSPIRE GML writer Datasets transformation and examples Conclusions INSPIRE Clusters 2

3 Objetive To test FME 2015 as tool to generate GMLs compliant to INSPIRE specifications To work directly with published INSPIRE XML (downloaded XSDs or on-line connection), no consideration on XSDs particular editions Results delivered for : FME World tour, Madrid venue, April 21th 2015 INSPIRE thematic clusters, INSPIRE Conference 2015? European Environment Agency - EAGLE group Spanish Council for INSPIRE implementation (CODIIGE - Consejo Directivo de la Infraestructura de Información Geográfica en España) INSPIRE Clusters 3

4 INSPIRE themes Related with land monitoring Land Cover (LC) Land Use (LU) In parallel with Orthoimagery in order to reflect the use of raster data for LC/LU INSPIRE Clusters 4

5 Transformation strategy Steps Selection of example national datasets ( 250 km2) Own part: national dataset adaptation to facilitate posterior INSPIRE features >> done with FME Generic part: Obtaining of INSPIRE feature types >> done with FME GML writing and validation >> done with FME INSPIRE Clusters 5

6 WorkwithINSPIREGMLinFME Since FME 2014 there are reader/writer INSPIRE GML INSPIRE Clusters 6

7 WorkwithINSPIREGMLinFME Since FME 2014 there are reader/writer INSPIRE GML Selection of INSPIRE theme and application schema package INSPIRE Clusters 7

8 WorkwithINSPIREGMLinFME Since FME 2014 there are reader/writer INSPIRE GML Aspect of a well defined INSPIRE GML writer INSPIRE Clusters 8

9 Work with INSPIRE GML writer Allowed data types in a FME INSPIRE GML writer Booleano: xml_boolean (true/false) Texto: xml_buffer, xml_char Numérico: xml_byte, xml_ubyte, xml_decimal, xml_int, xml_uint, xml_real Fecha: xml_date, xml_datetime, xml_time Geometría: xml_geometry Fragmento xml: xml_xml Default attributes from GML standard gml_id mandatory attribute, should be always present INSPIRE Clusters 9

10 Presentation First example is for LU, because its simple profile is easier than LC Datasets transformation and examples Land Use INSPIRE Clusters 10

11 Land Use INSPIRE features types to obtain ExistingLandUseDataSet ExistingLandUseObject (at least on value of HILUCS class per geometry, mandatory attribute to be present) Not considered PlannedLandUse feature types ELU Dataset ELU Object INSPIRE Clusters 11

12 Land Use National dataset SIOSE - National Land Cover and Land Use system of Spain (previously classified with HILUCS nomenclature) INSPIRE Clusters 12

13 Land Use FME Workbench SHP reader (SIOSE) ELU Dataset (general atts.) ELU Dataset(geometry and GML writer) ELU Object (geometryand GML writer) General data integrity and CRS change LU Object (general atts.) RelationshipbetweenELU Dataset and ELU Object ELU Object (HILUCS codelist) INSPIRE Clusters 13

14 General INSPIRE attributes Direct creation or renaming according GML writer INSPIRE Clusters 14

15 General INSPIRE attributes Direct creation or renaming according GML writer INSPIRE Clusters 15

16 INSPIRE CodeLists Using an attribute with GML label xlink:href There are other alternatives and ideas on it, but this one works INSPIRE Clusters 16

17 INSPIRE CodeLists Using an attribute with GML label xlink:href INSPIRE Clusters 17

18 Attributes values with multiplicity 0..* Using FME lists Attributes needed by INSPIRE GML writer INSPIRE Clusters 18

19 Relationships between INSPIRE features types with multiplicity 0..*, required in the GML Not always these relationships are required to be expressed in the GML. ELU demands it, other themes no. The relationships is defined by gml_id of the set and the components, using a attribute label xlink:href ExistingLandUseObject demands the link to the ExistingLandUseDataset. Using a FeatureMerger it is posible to transmit gml_id from one feature type to other. INSPIRE Clusters 19

20 Relationships between INSPIRE features types with multiplicity 0..*, required in the GML ELU Dataset gml_id, inside the ELU Object label INSPIRE Clusters 20

21 Geometry FME geometry must be renamed according INSPIRE specifications, using GeometryPropertySetter Attribute needed by INSPIRE GML writer (the little triangle doesn t turn green, but the writer recognizes the geometry na me) In the special case of Land Use, INSPIRE specifies that the geometry type must be gml:multisurface. To get this type in FME it is required to use the following sequence of transformers: Aggregator, MultipleGeometrySetter (value=no) and GeometryPropertySetter INSPIRE Clusters 21

22 Geometry FME geometry must be renamed according INSPIRE specifications, using GeometryPropertySetter INSPIRE Clusters 22

23 Result in FME Data Inspector 1 ExistingLandUseDataset 1043 ExistingLandUseObject How to see results on QGIS, please go to: /oi-result-in-qgis INSPIRE, GML and FME attributes 2 table views INSPIRE Clusters 23

24 Presentation Datasets transformation and examples Land Cover INSPIRE Clusters 24

25 Land Cover INSPIRE features types to obtain LandCoverDataset LandCoverUnit (INSPIRE doesn t define a class nomenclature, each provider can use the own nomenclature) LandCoverObservation (way to offer more than one class value per unit) LC Dataset LC Unit LC Observation INSPIRE Clusters 25

26 Land Cover National dataset SIOSE - National Land Cover and Land Use system of Spain (with Iberpix nomenclature Each SIOSE polygon has assigned 1 o more classes of LC measured by percentages INSPIRE Clusters 26

27 Land Cover FME Workbench SHP reader (SIOSE) LC Unit(general atts.) LC Observation LC Dataset (general atts. and GML writer) CSV reader (SIOSE) where are stored the multiple classes per polygon Mosaics. Way to express more that 1 LC class per polygon LC Unit(geometry and GML writer) INSPIRE Clusters 27

28 INSPIRE attributes with XML-fragment type It is needed to build manually the XML-fragment structure with XMLTemplater The labels values should be present in the data attributes, or obtained by operations INSPIRE Clusters 28

29 INSPIRE attributes with XML-fragment type It is needed to build manually the XML-fragment structure with XMLTemplater In case that the XML-fragment needs an XML-namespace, it is needed to include the definition of the XMLnamespace in the transformer INSPIRE Clusters 29

30 INSPIRE attributes with XML-fragment type It is needed to build manually the XML-fragment structure with XMLTemplater INSPIRE Clusters 30

31 Validation It is possible to use the default validation implemented in the INSPIRE GML writer Validation needs a reference application schema to compare. It will be the downloaded XSD file from INSPIRE web. If this parameter is in blank, FME looks for directly in the INSPIRE web. The validation only can be carried out over elements defined in the XSD file. XML-fragments attributes are omitted INSPIRE Clusters 31

32 Open issues What happen with LC nomenclatures? As they are not centralized by INSPIRE there is not a INSPIRE published CodeList for them. Proposed solutions: And maybe other more Each data provider should publish their class nomenclature value at web by a on-line register, and use xlink:href label to create the GMLs INSPIRE Clusters 32

33 Result 1 LandCoverUseDataset 1036 LandCoverUnit INSPIRE, GML and FME attributes, xmlfragments are showed by [ ] 2 table views INSPIRE Clusters 33

34 Presentation Datasets transformation and examples Orthoimagery (OI) In order to reflect the use of raster data for LC/LU. Next slides well be closer to OI theme, by special notes to raster LC/LU INSPIRE Clusters 34

35 Orthoimageries INSPIRE features types to obtain LC OrthoimageCoverage (OI) AggregatedMosaicElement (OI) LandCoverGridCoverage (LC) ExistingLandUseGrid (LU) LU OI Thematic attributes from LC or LU theme in their respective grid dataset are simple to be obta ined. The complicate ones are those attributes inherited from RectifiedGridCoverage. OrthoimageCoveragefrom OI theme has the same attributes INSPIRE Clusters 35

36 Orthoimageries National dataset The example is done for OI data, but LC-LU would follow the same process, only changing the values PNOA National Plan of Aerial Orthophotography It is needed the metadata files from the raster data, because there is where the coverage definition is. INSPIRE Clusters 36

37 Orthoimageries ISO Coverages RangeType: RecordType Data values description (type of phenomenon described by the coverage, nº bits, etc.) CoverageFunction Description of grid function (ordering of file, origin point, etc.) DomainSet Description of grid nature (images coordinates, axis, resolution, etc.) RangeSet Data values (pixels values) INSPIRE OI, LC, LU raster data follows the ISO standard about Coverages. Their fundamental attributes are: INSPIRE Clusters 37

38 Orthoimageries ISO Coverages RangeSet Alternatives to encode data values: Multipart representation (OGC GML for coverages OGC r2) GML (except rangeset) + rangeset in binary format Reference to a external file GML with rangeset as gml:fileelement that points to an external file in format *.tiff, *.geotiff, etc Encoding the range inline GML with range set as gml:datablock element (all pixel values inside GML file) WCS service, where rangeset is obtained through a GetCoverage operation localized in DomainSet defined Alterative in this example INSPIRE Clusters 38

39 Orthoimageries SHP reader (PNOA) Aggregated Mosaic Element (general att.) Coverage (rangetype) needs a csvfile to define the grid bands Aggregated Mosaic Element (geometryand GML writer) XML metadata file (PNOA). To read it FME needs a reader configuration file xfmap Coverage(general att. from the INSPIRE them) and domain extent Coverage(rangeSet, gridfunction, domainset and footprint) Coverage (geometryand GML writer) INSPIRE Clusters 39

40 Orthoimageries Domain extent INSPIRE Clusters 40

41 Orthoimageries Domain extent INSPIRE Clusters 41

42 Orthoimageries Range type INSPIRE Clusters 42

43 Orthoimageries Range type INSPIRE Clusters 43

44 Orthoimageries Range type Example of values for LC/LU grid raster datasets. HRL=Copernicus High Resolution Layer, CLC=CORINE Land Cover. [ref.: EAGLE group] INSPIRE Clusters 44

45 Orthoimageries Coverage Function & metadata INSPIRE Clusters 45

46 Orthoimageries Coverage Function & metadata Example of values for LC/LU grid raster datasets. HRL=Copernicus High Resolution Layer, CLC=CORINE Land Cover. [ref.: EAGLE group] INSPIRE Clusters 46

47 Orthoimageries Domain Set INSPIRE Clusters 47

48 Orthoimageries Domain Set INSPIRE Clusters 48

49 Orthoimageries Domain Set Example of values for LC/LU grid raster datasets. HRL=Copernicus High Resolution Layer, CLC=CORINE Land Cover. [ref.: EAGLE group] INSPIRE Clusters 49

50 Orthoimageries Range Set INSPIRE Clusters 50

51 Orthoimageries Range Set INSPIRE Clusters 51

52 Orthoimageries Range Set Example of values for LC/LU grid raster datasets. HRL=Copernicus High Resolution Layer, CLC=CORINE Land Cover. [ref.: EAGLE group] INSPIRE Clusters 52

53 Open issues RangeSet by external file does not seem the best solution because is pointed to a local resource, better through a WCS Allowed file formats (tiff, geotiff, jpeg200, etc.) are not optimal for dealing with big volume grid datasets Transform grid data into INSPIRE coordinate reference system implies re-sampling the original image values Geographical grid systems are different between countries, homogenization into INSPIRE implies re-sampling the original image values INSPIRE DomainExtent for coverages generates diverse interpretation by data providers. Redundancy between GML and ISO- OGC Coverages extent attributes. INSPIRE Clusters 53

54 Result 3 OrthoimageryCoverages 7 AggregatedMosaicElements INSPIRE, GML and FME attributes, xmlfragments are showed by [ ] 2 table views INSPIRE Clusters 54

55 Presentation Conclusions INSPIRE Clusters 55

56 Conclusions FME is able to create INSPIRE GML, but needs advanced experience with XML INSPIRE themes are more distinct that expected at XSD level (possible proposal to homogenize data types, extent, geometry, dates) Open issues Mistakes in the INSPIRE XSD for Land Cover Codelists do not defined by INSPIRE implies that each data provider should publish their LC class nomenclature values at web by a on-line registry Example: European Environment Agency CORINE Land Cover Complete INSPIRE validation ISO Coverage encoding (is it sufficient pointing to a external file?) What happen if INSPIRE XSD will be changed? Will FME INSPIRE GML writer work as now? INSPIRE Clusters 56

57 Instituto Geográfico Nacional Thanks for your attention Julián Delgado Hernández Land Cover and Land Use department INSPIRE Clusters