05.forest fires 2012_epsilon

Fuel Types modellingfor INSPIRE

3rd International Conference on Modelling, Monitoring and Management of Forest Fires22 – 24 May, 2012, New Forest, UK

1

Forest Fires 2012 ConferenceSession ArcFUEL:

Advancing Forest Fuel Mapping Techniques in Europe

Giacomo MartiranoEpsilon Italia srl | Mendicino CS, IT

T: +390984631949 | [email protected]

Giacomo Martirano; EPSILON Italia; T:+39 0984 631949; [email protected]

Introduction

Description of the steps to be applied to any Fuel Type Classification Map in order to make it INSPIRE compliant.

Application to the Fuel Classification Map (FCM) datasets generated within the ArcFUEL project.

2


INSPIRE for FCM

A preliminary fit-for-purpose analysis has been conducted in order to identify the most applicable INSPIRE data theme within the ArcFUEL context.

Among the 34 INSPIRE data themes, the following three have been identified as candidate and the relevant Data Specification (DS) analyzed: (ι) Natural Risk Zones, (ιι) Land Cover and (ιιι) Land Use.

The Land Cover (LC) data theme has been selected as the most applicable and the relevant DS has been deeply analyzed.

3


INSPIRE Land Cover Data Specification

• Directive (2007/2/EC) defines Land Cover (LC) as the Physical and biological cover of the earth's surface including artificial surfaces, agricultural areas, forests, (semi-)natural areas, wetlands, water bodies.

• The LC data specification does not prescribe or recommendany particular land cover nomenclature for use in INSPIRE.

• There is a multitude of different ways to describe land cover.

• There is only one "real world" but many different descriptions of this world depending on the aims, methodology and terminology of the observer.

• The approach taken by LC DS is instead to allow many different land cover nomenclatures to coexist in the context of INSPIRE.

4


INSPIRE Land Cover (LC) Data Specification (DS)

• The data specification for land cover is separated into (i) two core models and (ii) an extended model. The two core models are conceptually similar, but for technical reasons separated into one core model for vector data and one core model for raster data.

• The LC DS defines the following application schemas:LandCover CoreVector application schema;LandCover CoreRaster application schema;LandCover Extended application schema.

• LC data shall be modelled trough one of the two core applications schemas:LandCover CoreVector defines a vector representation (i.e. points or surfaces) to support Land Cover data.LandCover CoreRaster defines a raster representation to support Land Cover data.

5



6

Land cover conceptual core model



7

The selection of the application schema to be applied within theArcFUEL context was made taking into consideration the end-user requirements of the final ArcFUEL output (i.e. the FCM - Fuel Classification Map).

This requirements consists in using the final ArcFUEL output as input for Fire Simulators processes, for this reason the CoreRaster application schema has been selected.

The LandCoverCoreRaster application schema defines how Land Cover data can be

supported by a raster representation.


LandCoverCoreRaster application schema

8

LandCoverGridCoverage defines how a grid coverage can support Land Cover information.

LandCoverNomenclature defines the references to understand and interpret the classification values.


Name of the Land Cover coverage.

9

LandCoverGridCoverage


External object identifier of the spatial object.

The extent of the dataset, in space, time or space-time.

Information about the nomenclature used in the coverage.

All the elements of the selected application schema will be

structured into a database, for further creation of the INSPIRE compliant gml using a proper

transformation tool.


For the encoding of the FCM values the use of the external file option

has been investigated, as also recommended by the

Recommendation 4 of Section 9.2.1.2 of the DS_v2.9.2.

10



In order to physically implement this option have been followed the indications contained in point 4 of the Annex C of “D2.7: Guidelines for the encoding of spatial data,

Version 3.2”.

The attribute rangeSet will be encoded as xlink to the external file.




The attribute used for documenting the FCM nomenclature has a complex dataType, LandCoverNomenclature

A LandCoverNomenclature defines what information shall be provided to

right undertand and interpret the classifcation codes contained in the

dataset.


This attribute defines which organization (or entity) defines or is responsible for the nomenclature.

12

LandCoverNomenclature


External object identifier of the spatial object.

This attribute references the code list attached to the nomenclature.It will be used to document the 44-classes Fuel Types classification, through its encoding as an URI.

This attribute allows to provide an URL pointing to the documentation (specification or other document) describing the classification system used and the nomenclature used.


13

FCM data modelling

Group No

Group name

FT No Fuel type name

1 Peat bogs 2 Wooded peatbogs

3 Pastures 4 Sparse grasslands5 Mediterranean grasslands and steppes6 Temperate, Alpine and Northern grasslands7 Mediterranean moors and heathlands8 Temperate, Alpine and Northern moors and heathlands9 Mediterranean open shrublands (sclerophylous)10 Mediterranean shrublands (sclerophylous)11 Deciduous broadleaved shrublands (thermophilous)12 Alpine open shrublands (conifers)

13 Shrublands in Mediterranean conifer forests14 Shrublands in Mediterranean sclerophylous forests15 Shrublands in Mediterranean montane conifer forests16 Shrublands in thermophilous broadleaved forests17 Shrublands in beech and mesophytic broadleaved forests18 Northern open shrublands in broadleaved forests19 Shrublands in Alpine and Northern conifer forests

20 Mediterranean long needled conifer forest (mediterranean pines)21 Mediterranean scale‐needled open woodlands (juniperus, cupressus)22 Mediterranean montane long needled conifer forest (black and scots pines)23 Mediterranean montane short needled conifer forest (firs, cedar)25 Alpine long needled conifer forest (pines)26 Alpine short needled conifer forest (fir, alp. spruce)27 Northern long needled conifer forest (scots pine)28 Northern short needled conifer forest (spruce)

29 Mediterranean evergreen broadleaved forest30 Thermophilous broadleaved forest31 Mesophytic broadleaved forest32 Beech forest33 Montane beech forest 34 White birch boreal forest

35 Mixed mediterranean evergreen broadleaved with conifers forest36 Mixed thermophylous broadleaved with conifers forest37 Mixed mesophytic broadleaved with conifers forest38 Mixed beech with conifers forest

39 Riparian vegetation40 Coastal and inland halophytic vegetation and dunes41 Aquatic Marshes42 Agroforestry areas

5 24 Central conifer forests (conifer plantations of central Europe)

GROUND FUELS

PLANTATIONS

3B

1

2

TRANSITI

ONAL

FORESTS

SURFACE

FUELS

3A

OTHER FUELS4

CONIFEROUS

FORESTS

BROAD

LEAVED

FORESTS

MIXED

FORES

TS

FUELS POTENTIALLY INVOLVING

CANOPY

Link

Link


14

FCM Metadata profile

A FCM metadata profile will be created and will comprise two groups of metadata elements, as required in the section 8 of the LC DS.

The common metadata elements, as required by Regulation 1205/2008/EC (implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata) for spatial datasets and spatial dataset series.

The theme-specific metadata elements.

An FCM xml metadata profile will be created for use within any metadata editor to create the metadata for each FCM dataset.

Thank you on behalf

Giacomo Martirano

15

05.forest fires 2012_epsilon

Documents

landcovercoreraster

land cover

lc ds

spatial object

data specification

core model

martiranoepsilon

thearcfuel