Service Contract based on the restricted procedure No EEA/MDI/14/009 following a call for expression of interest EEA/SES/13/005-CEI

Transcription

1 Service Contract based on the restricted procedure No EEA/MDI/14/009 following a call for expression of interest EEA/SES/13/005-CEI Final Report Assistance to the EEA in the production of the new CORINE Land Cover (CLC) inventory, including the support to the harmonisation of national monitoring for integration at pan-european level Task 3 - Data model description Prepared by: Gebhard Banko 30. December 2014 Version 1.0

2 Restricted procedure No EEA/MDI/14/009 following a call for expression of interest EEA/SES/13/005-CEI Legal notice The contents of this publication were created by the contractor under EEA service contract No. 3436/B2014/R0-GIO/EEA and do not necessarily reflect the official opinions of the European Commission or other institutions of the European Union. Neither the European Environment Agency nor any person or company acting on behalf of the Agency is responsible for the use that may be made of the information contained in this report. Copyright notice EEA, Copenhagen, 2014 Reproduction is authorised, provided the source is acknowledged, save where otherwise stated.

3 EAGLE DATA MODEL DESCRIPTION BASIC ELEMENTS The central classes of the EAGLE data model are the LandCoverUnit (LCU) and the LandCoverComponent (LCC). The LCU can be considered the most elementary mapped area, as it is the element used to store the geometry, representing a homogeneous piece of land able to be delineated from the neighbor scopes. The LCU can then be composed of several LCC to describe the landscape. This description can be done as pure land cover components (e.g. bare rock, building, trees, etc.) or compositions of these pure components. The LCCs may specify their quantitative relevance within the LCU (e.g. percentage of covered area), but the geometries of the constituent LCCs do not belong to EAGLE model and thus are not stored (usually because the area of the components is below the threshold of the specified minimum mapping unit or their geometries as isolated components are considered irrelevant or unknown). GML EAGLELandCoverVector_Base 0..1 LandCov erdataset + levelofdetail: LevelOfDetailType + metadata: EAGLEMetadataType element 1..* LandCov erunit + cultivationpractice: CultivationPracticeValue [0..1] + ecosystem: EcosystemType [0..1] + environmentalzone: EnvironmentalZoneType [0..1] + heightzone: HeightZoneValue [0..1] + spatialcontext: SpatialContextValue [0..1] + tidalinfluence: boolean [0..1] «ExistingLandUse» + existinglanduse: LandUseType [0..1] 1 0..* + occurence: OccurenceType + overlaying: boolean [0..1] AbstractLandCoverComponent «lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] «ExistingLandUse» + existinglanduse: LandUseType [0..1] «time» + timedimension: TimeDimensionType [0..1] 1..* 1 SpatialComposition + built-uppattern: Built-upPatternValue [0..1] + linearpattern: LinearPatternValue [0..1] + lineartechnicalnetwork: LinearTechnicalNetworkValue [0..1] + spatialpattern: SpatialPatternValue [0..1] LandCoverComponent + status: StatusType [0..*] + surfacemodification: SurfaceModificationValue [0..1] constraints {urbanpatternonlyforsealedlandcovercomponents}

4 The LCCs are modelled as a hierarchy of classes taking as root AbstractLandCoverComponent, abstract concept that involves those all common characteristics for pure LCC and sets of them. The hierarchy can be divided on pure land cover components (LandCoverComponent class) and SpatialComposition components set. The pure components are divided further into more specific classes (Abiotic/Non-vegetated, Biotic/Vegetation and Water), which in turn are divided into even more specific classes (e.g. Artificial and NaturalMaterial are specializations of Abiotic/Nonvegetated). A SpatialComposition component can be composed of pure land cover components or nested spatial compositions that are grouped following a specific spatial pattern (mosaic, homogeneous, scattered, etc.). To map a specific landscape feature, the most specific land cover component class should be applied according to the available information (e.g. we should use RegularGraminaceous class if we have enough information to know this is the best-fitting class, but we could use just Graminaceous or Herbaceous if not enough information is available to use the most specific class). The LCCs can specify their presence and weight within the LCU or the enclosing SpatialCompsition by using the occurrence attribute. This attribute can be applied in different ways to either express the relative area of the LCC compared with the LCU (PercentageOccurrence), the presence or absence of the LCC (PressenceOccurrence) or the number of elements (CountableOccurrence). Both LCC and LCU have several attributes to further define the landscape. The attributes available on LCUs tend to be more generic as they apply to the whole unit (e.g. heightzone, tidalinfluence, environmentalzone, etc), while most LCC attributes only apply to a single component so they are more specific (e.g. leaftype is only available on Woody components and its descendant classes). Another important class of the EAGLE model is the LandCoverDataset, which is composed of one or more LCUs mapped at the same spatial detail level (mapping scale). The datasets can have a hierarchical relationship with other datasets, meaning that a given dataset is a generalization (coarser mapping scale) of another dataset. In this way it is possible to store land cover information at several generalization levels within the same database and keep the relationship between these levels. EAGLE AND INSPIRE The EAGLE data model is grounded in the INSPIRE data specifications. As the model is targeted to describe both land use and land cover aspects of land monitoring, the EAGLE model extends the INSPIRE data model for Land Cover and includes the most relevant aspects of Land Use data specifications.

5 In particular, EAGLE LandCoverDataset and LandCoverUnit extend INSPIRE LandCoverDataset and LandCoverUnit from Land Cover data specification (LandCoverExtension model). This implies that the geometry is bound to the LandCoverUnit which has at least one LandCoverObservation. While EAGLE proposes the use of an object oriented description (the land cover components) of the observed land cover, the INSPIRE LandCoverObservation (based on a traditional set of categories encoded as a code list) is still convenient for storing a backwards-compatible land cover value (e.g. a CORINE Land Cover class or a category from a national methodology). The EAGLE data model integrates descriptors related to other INSPIRE data specifications (e.g. biogeographical regions, ecosystems, buildings, etc). Whenever possible, these descriptors are encoded using the same code list included in the related data specification (e.g. EUNIS for ecosystems, HILUCS for land use, etc.) [expand this description]. In this way, the EAGLE data model fulfills all the requirement of the INSPIRE Land Cover data model and adds additional objects and attributes to allow a richer and more flexible set of descriptors for land cover, land use and other observed characteristics. GML EAGLELandCoverVector_Base INSPIRE Land Cover LandCov ernomenclature::landcov ernomenclature + inspireid: Identifier + nomenclaturecodelist: URI + responsibleparty: RelatedParty «voidable» + embeddeddescription: LC_LandCoverClassificationSystem [0..1] + externaldescription: DocumentCitation [0..*] LandCov ervector::landcov erdataset + extent: EX_Extent + inspireid: Identifier + name: CharacterString + nomenclaturedocumentation: LandCoverNomenclature «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] «voidable» + validfrom: Date + validto: Date LandCov erextension::landcov erdataset LandCov erdataset + nomenclaturedocumentationextended: LandCoverNomenclature [0..*] {ordered} + levelofdetail: LevelOfDetailType + metadata: EAGLEMetadataType element 1..* +member 1..* LandCov ervector::landcov erunit + geometry: GM_Object + inspireid: Identifier + landcoverobservation: LandCoverObservation [1..*] «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] LandCov erextension::landcov erunit + landcoverobservationextended: LandCoverObservation [0..*] {ordered} + parametricobservation [0..*] ::LandCoverUnit + geometry: GM_Object + inspireid: Identifier + landcoverobservation: LandCoverObservation [1..*] «voidable, lifecycleinfo» ::LandCoverUnit + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] constraints ::LandCoverUnit { geometryiskindofgm_pointorgm_surface } +element 1..* LandCov erunit + cultivationpractice: CultivationPracticeValue [0..1] + ecosystem: EcosystemType [0..1] + environmentalzone: EnvironmentalZoneType [0..1] + heightzone: HeightZoneValue [0..1] + spatialcontext: SpatialContextValue [0..1] + tidalinfluence: boolean [0..1] «ExistingLandUse» + existinglanduse: LandUseType [0..1] LandCov ervector:: LandCov erobserv ation + class: LandCoverClassValue «voidable» + mosaic: LandCoverValue [1..*] + observationdate: DateTime «codelist» ParameterTypeValue + crowcoverdensity + soilsealingdegree LandCoverExtension:: ParameterType + name: ParameterTypeValue «voidable» + observationdate: Date Data value of 'name' has been changed from characterstring to a extensible codelist. Benefits: only controled values allowed. LandCov ervector:: LandCov ervalue + class: LandCoverClassValue «voidable» + coveredpercentage: Integer LandCov erextension:: PercentageParameter LandCov erextension:: CountableParameter LandCov erextension:: PresenceParameter + coveredpercentage: Number + count: Number + present: Boolean The modelling of land use is integrated on EAGLE at the LCU level and also at the LCC level. The purpose of first one is to define the land use applicable to the whole unit, while the second one is

6 provided to encode the specific land use on each LCC. In both cases, the land use has been modelled using the LandUseType, which is a flexible type which can combine the HILUCS classification (mandatory) with an optional or custom classification, in term of EAGLE scope it has been defined a EAGLELandUseClassificationSystem that enhances HILUCS classes for some specific land uses. Each EAGLE land use class is included in one HILUCS class, and this relation is expressed by the hierarchical code in the class label. class EAGLELandCoverVector_DataTypesAndLists LandUseType + hilucslanduse: HILUCSValue + hilucspresence: HILUCSPresence [0..1] + specificlanduse: LandUseClassificationValue [0..1] + specificlandusepresence: SpecificPercentage [0..1] INSPIRE Land Use «union» Land Use Nomenclature::SpecificPresence + orderedlist: LandUseClassificationValue [1..*] {ordered} + percentagelist: SpecificPercentage [1..*] «union» Land Use Nomenclature::HILUCSPresence + orderedlist: HILUCSValue [1..*] {ordered} + percentagelist: HILUCSPercentage [1..*] Land Use Nomenclature::SpecificPercentage + percentage: Integer + specificvalue: LandUseClassificationValue Land Use Nomenclature::HILUCSPercentage + hilucsvalue: HILUCSValue + percentage: Integer «codelist» Land Use Nomenclature::LandUseClassificationValue tags asdictionary = true extensibility = any vocabulary = xsdencodingrule = iso19136_2007_inspire_extensions «codelist» Land Use Nomenclature::HILUCSValue tags asdictionary = true extensibility = none vocabulary = xsdencodingrule = iso19136_2007_inspire_extensions «codelist» EAGLELandUseClassificationSystem + 1_3_3_1_Salines + 1_3_X_SurfaceMining + 3_3_5_1_CementeryServices + 3_4_1_1_IndoorCulturalServices + 3_4_1_2_OutdoorCulturalServices + 3_4_3_1_GolfCourse + 3_4_3_2_SkiPistes + 3_4_3_3_OutDoorRacingCourses + 3_4_3_4_SportHalls + 3_4_3_5_Stadiums - 3_4_3_6_SwimmingPools + 3_4_4_1_UrbanGreeneryAndParks + 3_4_5_1_2_Allotment Gardens + 4_3_2_1_FreshWaterFacilities + 4_3_2_2_SewageWaterAndTreatmentFacilities According INSPIRE Data Specification on Land Use, it is possible to create or use an alternative land use classification system together HILUCS. This classification system will be a sub-codelist of LandUseClassificationSystem that will be defined and maintained by the responsible organization, not by INSPRIE. Also it is required to supply a mapping between classes on HILUCS and the alternative classification system. EAGLE proposes a codelist that contains specialized land use classes not represented in HILUCS that will be used to describe in a more detailed aspect. Each EAGLE land use is included in one HILUCS class, and this relation is expressed by the hierarchical code in the class label. EAGLE land use classes have to be used always together with original parent HILUCS classes. The simplest usage of the LandUseType (attributing a single land use class to the LCU or the LCC) involves filling the hilucslanduse attribute, which is a direct reference to a HILUCS class using HILUCS code. When the HILUCS classification is not specific enough for the modelling exercise, then the specificlanduse attribute can be used (in addition to hilucslanduse) to encode this specific land use using an alternative classification system. EAGLE land use classes have to be used always together with original parent HILUCS classes.

7 If a more complex and flexible description of land use is required, then the LandUseType provides the hilucspresence and specificlandusepresence attributes. These attributes can be used to attach to LCU or LCC, an ordered list of land uses (by order of importance), or a list of presence percentage of land uses. The INSPIRE data specification for land use defines two different types of land use: existing land use ( which objectively depicts the use and functions of a territory as it has been and effectively still is in real life ) and planned land use ( which corresponds to spatial plans, defined by spatial planning authorities, depicting the possible utilization of the land in the future ). The EAGLE data model focuses only on existing land use, as the planned land use is beyond the scope of a land cover/land use monitoring methodology. TEMPORAL ASPECTS The EAGLE data model has been designed for modelling temporal aspects of land monitoring, such as land cover changes or recurring phaenomena (e.g. flooding, snow fall, etc.). The timedimension attribute of the LCC is used to specify these temporal aspects by using the TimeDimensionType, which is a flexible type that allows specifying: Seasonal frequency for the number of changes per year (for recurring events or status), using the recurringfrequency attribute Seasonal duration for the length of a time interval of an event or status (measured in years, months, days, hours, etc.), using the duration attribute Period of an event or status which is limited by two definite positions in time (temporal validity of the LCC), using the period attribute The TimeDimensionType is built on the top of ISO s temporal schema (ISO 19108:2002), so TM_Duration is used to encode the seasonal duration and TM_Period is used to encode the temporal validity. Note that the LCU is considered to be constant for a given dataset, so it has no associated time dimension. OVERLAYING LCCs The land cover description is an abstraction of the reality and it becomes quite natural to flatten reality in order to model it on a land cover database. The EAGLE data model has chosen this approach, so (generally speaking) no vertical strata information is stored. However, there are some temporary phaenomena (snow cover, flooding, etc.) that are likely to be captured on the database while we still want to record the permanent cover underneath. For these specific cases, the LCCs have an overlay attribute which indicates whether they lay on the standard EAGLE plane or on an overlaying plane. This attribute is reserved for these specific temporary uses and it is not recommended to abuse it for modelling more complex vertical strata (rivers under bridges, etc.). Leaving alone these overlaying components, all the rest of the reality is considered to be on a single plane (from the land cover modeling point of view) and therefore the sum of all nonoverlaying LCCs must be equal or lower than 100% of the related LCU (for any specific temporal instant).

8 RASTER DATASETS One of the requirements for EAGLE data model is to make possible the representation of raster data. There are fundamental datasets in this format (i.e. Copernicus High Resolution Layers, Global Land Cover, etc.) and the proposed EAGLE data model should facilitate and help dealing with this issue. EAGLE data model is aligned with INSPIRE specifications on land cover and land use and ISO standards, for this reason the raster development in EAGLE must follow the INSPIRE proposed features and attributes, established from ISO standard about coverages. As it can be seen in the following application schema for raster data, EAGLE only adds some attribution at level of land cover coverage to describe it in the same way that vector datasets: metadata, level of detail and possibility of reflexive relationships between coverages. In order to reproduce adequately the main coverage attributes defined by ISO 19123, EAGLE documentation offers some description of them and key guidelines about their implementation

9 for the most common raster datasets examples. Particular aspects of ISO coverages encoding are not dealt in the present document. - coveragefunction: Describe the main aspects of coverage function itself, such as ordering of values, main description, documentation reference or staring point. Dataset coveragefunction.coveragema ppingrule.ruledefinition coveragefunction. CoverageMappingRule. rulereference.xlink_href coveragefunction.gridfunctio n.sequencerule (in most of raster data, the values are stored in linear way) coveragefunction.gridfunctio n.startpoint (in most of raster data, the origin for storing is the top telf corner) Imperviousness degree Degree of imperviousness on land surface us.eu/ Forest type Type of forest depending on leaf type icus.eu/ Water Presence of water on land icus.eu/ Linear linear linear linear Rasterized CLC CORINE Land Cover in rater format Top left corner Top left corner Top left corner Top left corner - rangetype: Describe the range of values that the coverage can represent. It is used a complex type to document the possibility of values, called RecordType. Each information dimension stored in the dataset needs the use of a one recordtype instance. If only land cover data is represented, there will be only one information dimension. If land use data is also stored inside the coverage, there will be other recordtype. The main attributes to be filled for each recordtype are shown below, together with some examples: Dataset Imperviousness degree Forest type Water Rasterized CLC

10 rangetype.datarecord.quantit y.description rangetype.datarecord.quantit y.uom rangetype.datarecord.quantit y.constraint.allowedvalues rangetype.datarecord.quantit y.nilvalues Degree Type Presence Type Percentage Classes of forest Boolean Classes Broadleaved, coniferous, mixed, no-forest <0 and >100 Distinct values of previous ones Water, no-water Distinct values of previous ones CORINE Land Cover nomenclature Distinct values of previous ones - domainset: Describe the scope where the coverage is reproduced, such as geographic limits, Cartesian definition, etc. Dataset domainset.rectifiedgrid.limits. GridEnvelope.low domainset.rectifiedgrid.limits. GridEnvelope.high (together low parameter, offers the number of pixels) domainset.rectifiedgrid. axislabels domainset.rectifiedgrid.origin.point.pos (geographic starting point) domainset.rectifiedgrid.offset Vector{} (possible offset form the origin) Imperviousness degree Forest type Water (0,0) (0,0) (0,0) (0,0) Rasterized CLC (1000,1000) (1000,1000) (1000,1000) (1000,1000) (x,y) (x,y) (x,y) (x,y) , ) , ) , ) (0,0) (0,0) (0,0) (0,0) , ) - rangeset: Set of pixel values. In terms of ISO encoding, the pixel values can be stored in 3 different ways. o 1) Multipart representation. This is composed of: 1st Part: GML Part (gmlcov:rectifiedgridcoverage) - This is the structure of the coverage in GML, without the values. 2nd Part: The Range Set of the coverage (the values), encoded using a well-known binary format e.g. TIFF / GeoTIFF (*) - but embedded in the 1st Part. o 2) External file encoding. This is composed of: 1st Part: GML Part (gmlcov:rectifiedgridcoverage) - This is the structure of the coverage in GML, without the values. 2nd Part: The Range Set of the coverage (the values), encoded using an external well-known binary format (linking it using gml:file) e.g. TIFF / GeoTIFF (*). This is the example that is shown below. o 3) Inline encoding. The Range Set of the coverage is encoded within the XML inline (using the "DataBlock" element). Type of encoding no applicable for big volumes of data because would generate much bigger GML files.

11 Dataset rangeset.file.filereference (it should be allow attached image, webservice, FTP or ATOM) rangeset.file.filestructure (it depends on file format) rangeset.file.mimetype Imperviousness degree hrl_imp_2012) Forest type hrl_ft_2012) Water hrl_w_2012) Rasterized CLC clc_2012) linear) linear) linear) linear) image/tiff) image/tiff) image/tiff) image/tiff)