inspire and flood directive reporting: important issues to raise manuela pfeiffer wise...

INSPIRE and

flood directive reporting:

important issues to raise

Manuela Pfeiffer

WISE GIS/IT-Workshop 7.5./8.5.2012 Copenhagen

Scope “Natural Risk Zones” (NZ)• INSPIRE Directive (2007/2/EC) defines Natural Risk Zones theme

as: “Vulnerable areas characterised according to natural hazards (all atmospheric, hydrologic, seismic, volcanic and wildfire phenomena that, because of their location, severity, and frequency, have the potential to seriously affect society), e.g. floods, landslides and subsidence, avalanches, forest fires, earthquakes, volcanic eruptions.”

• Overall approach taken: "Natural risk zones" are zones where natural hazards areas intersect with highly populated areas and/or areas of particular environmental/ cultural/ economic value.

Risk in this context is defined as:

• Risk = Hazard x Vulnerability x Exposure with regards to the social, environmental, cultural and economic assets

in the zone respectively area of interest.

4 kinds of spatial object types that are derivated both in vectors and in coverages:

• Observed event• Hazard area• Risk zone • Exposed element

For each of them, the following feature types have been created:

• abstract feature type that contains the properties (attributes, or constraints) of the spatial object that are common both to its vector representation and to its coverage representation.

• vector feature type and a coverage feature type generated from the abstract feature, and with the properties that are specific to vector or coverage representation.

It is therefore not required to provide data both in coverages and in vector, but either in vector or in coverages.

class 1_temporal_merged_cov erage_v ec...

«featureType»AbstractRiskZone

+ inspireId: identifier+ sourceOfRisk:

NaturalHazardClassification

«voidable, l ifeCycleInfo»+ beginLifeSpanVersion: DateTime+ endLifeSpanVersion: DateTime [0..1]

«voidable»+ validityPeriod: TM_Period [0..*]

«featureType»AbstractExposedElement

+ inspireId: identifier+ typeOfElement:

ExposedElementCategoryValue [1..*]


«voidable»+ validFrom: DateTime+ validTo: DateTime [0..1]

«featureType»AbstractHazardArea

+ inspireId: identifier+ determinationMethod:

DeterminationMethodValue+ typeOfHazard:



«voidable»+ validityPeriod: TM_Period [0..1]

«featureType»AbstractObservedEvent

+ inspireId: Identifier+ typeOfHazard:


«voidable, l ifeCycleInfo»+ beginLifeSpanVersion: DateTime+ endLifeSpanVersion: DateTime

[0..1]

«voidable»+ validFrom: DateTime+ validTo: DateTime [0..1]

«featureType»NaturalRiskZonesCov erage::

RiskCov erage

constraints{RangeSet is LevelofRisk}

CoverageByDomainAndRange

«featureType»NaturalRiskZonesCoverage::

RiskHazardOrExposedElementCoverage

constraints{Domain is RectifiedGrid or ReferenceableGrid}

CoverageByDomainAndRange

«featureType»NaturalRiskZonesCoverage::ExposedElementCoverage

constraints{Range Set is LevelofVulnerabil ity}

«featureType»NaturalRiskZonesCov erage::

Observ edEv entCov erage

constraints{RangeSet is magnitudeOrIntensity or LikelihoodOfOccurence}

«featureType»NaturalRiskZonesCov erage::HazardCov erage

constraints{RangeSet is magnitudeOrIntensity or LikelihoodOfOccurence}

«featureType»NaturalRiskZonesVector::ExposedElementVector

+ geometry: GM_Object+ assessmentOfVulnerabil ity:

Vulnerabil ityAssessment [1..*]

«featureType»NaturalRiskZonesVector::RiskZoneVector

+ geometry: GM_Surface

«voidable»+ levelOfRisk: LevelOrIntensity

«featureType»NaturalRiskZonesVector::

HazardAreaVector

+ geometry: GM_Surface

«voidable»+ likelihoodOfOccurence:

LikelihoodOfOccurrence+ magnitudeOrIntensity: LevelOrIntensity

«featureType»NaturalRiskZonesVector::

ObservedEventVector

+ geometry: GM_Object

«voidable»+ likelihoodOfOccurence:

LikelihoodOfOccurrence+ magnitudeOrIntensity: LevelOrIntensity

[1..*]

+source«voidable»1

+result«voidable»

0..*

+riskZone«voidable»0..*

+exposedElement«voidable»

1..*

Merged NZ Core Model Draft proposal V

ecto

rs

Covera

ges

class 2_Data_types

LikelihoodOfOccurrence

+ + +

constraints

Quantitativ eLikelihood

+ probabilityOfOccurrence: Probability+ returnPeriod: Number

Lev elOrIntensity

+

+ +

constraints

DocumentReference

+ + + +

constraints

contactInformation

+ + + + +

constraints

This is our view of document referencing. We will adapt this to the feedback from the JRC for version 3.0.

RiskOrHazardCategoryValue

ExposedElementCategoryValue

DeterminationMethodValue

modelling indirectDetermination

«dataType»NaturalHazardClassification

+ hazardCategory: RiskOrHazardCategoryValue

«voidable»+ specificHazardType: CharacterString+ specificHazardTypeReference: URI

«dataType»ExposedElementClassification

+ exposedElementCategory: ExposedElementCategoryValue

«voidable»+ specificExposedElementType:

characterString+ specificExposedElementTypeReference: URI

Key NZ code lists:

• facilitate semantic interoperability;• more detailed terms are extensible by MS/Data providers,

(narrower concept);• data provider can add specific classifications of

type of hazards or exposed elements

(regional, local, more detailed etc.)

e.g. lists of flood types and adverse consequences

• Categories of Natural hazards (1st level)

• Geological/hydrogeological (FD: “Tsunami”)• Meteorological/climatological (FD: all other “flood

types”)• Fires• Biological• Cosmic

• Categories of Exposed elements (1st level)• FD: “Types of adverse consequences”

• Human Health (FD: “Human Health”)• Economic assets (FD: “Economic Activities”)• Environmental assets (FD: “Environment”)• Cultural assets (FD: “Cultural heritage”)

Key NZ code lists:

Elements vulnerable to floods:

PropertyPeople…

AgricultureIndustry…

Elements non vuleranble to floods

Natural floodplains and river-side ecosystems

Elements non vuleranble to floodsElements non vuleranble to floods

Natural floodplains and river-side ecosystems

Estimated, thus hypothetical100 yr flood-prone area (Hazard)

Estimated, thus hypothetical100 yr flood-prone area (Hazard)

RiverRiver

Natural Risk zonesNatural Risk zones

Exposed elements(vulnerability > 0)

Vulnerable elements not exposed to a given hazard

Exposed elements(vulnerability = 0)

Legend

DIAGRAM EXPLANATIONDIAGRAM EXPLANATION

Roads

Relationship between risk, hazard, vulnerability and exposure

Relevant reporting obligations:Floods Directive (2007/60/EC) – FD

• NZ considered FD in Annex B Use Case “Flood Risk

Maps” and provides a ”Floods Model” as an example

only (no premature fixation in terms of FD reporting)

• Demonstration of the extensibility of the core NZ

model for a specific hazard (can be re-used or

modified = flexibility for Data providers)

• Collaboration with the Floods Directive Reporting

Drafting Group (joint meetings, comments on the

drafts etc.)

• Full harmonisation for the Second Reporting cycle

(after 2015, utilisation of implementing experience)

class Floods

«codeList»InundationValue

+ controlled+ natural

HydroObject

«featureType»InundatedLand

+ dateOfObservation: DateTime+ observedConsequences:

ObservedConsequences [1..*]

«dataType»FD_PreliminaryFRAssessment

+ inspireId: Identifier

«voidable, l ifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

«voidable»+ reference: DocumentCitation

«dataType»FD_FloodHazardMap



«voidable»+ reference: DocumentReference

«dataType»FD_FloodRiskMap



«voidable»+ reference: DocumentReference

«featureType»PotentialFloodedArea

«featureType»PotentialFloodedAreaElement

«dataType»Observ edConsequences

+ typeOfConsequence: ExposedElementCategoryValue

+ assessmentOfConsequence: CharacterString

«featureType»NaturalRiskZonesCore::

AbstractRiskZone

+ inspireId: identifier+ sourceOfRisk:



«voidable»+ validityPeriod: TM_Period [0..*]

«featureType»NaturalRiskZonesCore::

AbstractExposedElement

+ inspireId: identifier

«voidable, l ifeCycleInfo»+ beginLifeSpanVersion: DateTime+ endLifeSpanVersion: DateTime [0..1]+ validFrom: DateTime+ validTo: DateTime [0..1]

«featureType»NaturalRiskZonesCore::AbstractHazardArea

+ inspireId: identifier+ determinationMethod:

DeterminationMethodValue+ typeOfHazard: NaturalHazardClassification


«voidable»+ validityPeriod: TM_Period [0..1]

«featureType»NaturalRiskZonesCore::AbstractObservedEvent

+ inspireId: Identifier+ typeOfHazard:


«voidable, l ifeCycleInfo»+ beginLifeSpanVersion: DateTime+ endLifeSpanVersion: DateTime

[0..1]

«voidable»+ validFrom: DateTime+ validTo: DateTime [0..1]+ nameOfEvent: CharacterString

NOTE : Those constraints are only for the purpose of Floods Directive

/*At least water heights or water levels must be completed.*/Inv : self.magnitudeOrIntensity.quantitativeValue.oclIsKindOf(Length)

/* the intensity is either a measure (for the expression of the flow), or more specifically a Velocity (for the velocity of flow) or a length (for the water height and for the water level*/inv: self.magnitudeOrIntensity.quantitativeValue.oclIsKindOf(Measure) or self.magnitudeOrIntensity.quantitativeValue.oclIsKindOf(Length) or inv.magnitudeOrIntensity.quantitativeValue.oclIsKindOf(Velocity)

NOTE : Those constraints are only for the purpose of Floods Directive

/*A flood hazard map must contain one high probability potential flooded area, one medium probability potential flooded area and one low probability potential flooded area.*/inv : self.pFArea.typeOfHazard.specificRiskOrHazardType = 'groundwater' or self.pFArea.typeOfHazard.specificRiskOrHazardType = 'seawater' implies self.pFArea.likelihoodOfOccurence.qualitativeLikelihood = 'low' and self.componentOf.likelihoodOfOccurence.qualitativeLikelihood = 'medium' and self.componentOf.likelihoodOfOccurence.qualitativeLikelihood = 'high'

/*The potential flooded area element that are displayed on the flood hazard map must compose the potential flooded areas that are also on the same flood hazard map*/inv : self.pFAElement = self.pFArea.componentOf

/*For groundwater or seawater floods, then it is possible for a FloodHazardMap to fi l l in only one low probability potential flooded area.*/inv : self.pFArea.typeOfHazard.specificRiskOrHazardType = 'groundwater' or self.pFArea.typeOfHazard.specificRiskOrHazardType = 'seawater' implies self.pFArea.likelihoodOfOccurence.qualitativeLikelihood = 'low'

NOTE : /*The generic risk or hazard category is "Flood" for all inundated lands*/inv : self.typeOfHazard.hazardCategory = 'flood'

NOTE :/*The exposed elements that are on the flood risk Map are those linked to the risk zones that are on the same flood risk Map */Inv:self.exposedElement = self.componentOf.riskZone.exposedElement

NOTE : this link is set only for the purpose of the Floods Directive

HydroObject

«featureType»WaterBody not Management Unit but links to

RBD::WFDWaterBody


«lifeCycleInfo, voidable»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

NOTE : /*The generic risk or hazard category is "Flood" for all potential flooded areas*/inv : self.typeOfHazard.hazardCategory = 'flood'

NOTE : potential flooded area is either generalised from "HazardAreaVector" or "HazardAreaCoverage" The magnitude or intensity and likelihood of occurrence are properties of this spatial object, but as they are modeled either as attributes (when generalizedfrom "HazardAreaVector") or as constraints (when generalized from "HazardAreaCoverage"), it does not appear in the model.

NOTE : /*The generic risk or hazard category is "Flood" for all potential flooded areas elements*/inv : self.typeOfHazard.hazardCategory = 'flood'

NOTE : potential flooded area elements is either generalised from "HazardAreaVector" or "HazardAreaCoverage" The magnitude or intensity and likelihood of occurrence are properties of this spatial object, but as they are modeled either as attributes (when generalized from "HazardAreaVector") or as constraints (when generalized from "HazardAreaCoverage"), it does not appear in the model.

+FD_componentOf

+FD_contains

«voidable» 0..1

«voidable»0..1

+inundatedLand«voidable»

1..*

+contains«voidable»

0..*

+source«voidable»

1

+exposedElement«voidable»

1..*

1

+FD_riskZone

1..*

+pFAElement

1..*

+showsPFAElement

1

+pFArea1

+showsPFArea 1

+result 1..*

+origin 0..*

+FD_ExposedElement1..*

+source«voidable»

0..*

WFD-Waterbody

FD – Extension

FD-PFRA

FD-APSFR

FD-FRM

FD-FHM

Annex I HY object:

Inundated land FD-past events

scenarios

“Type of consequences” – tb specified

… there are some other FD-relevant INSPIRE themes:

e. g. Area Management for UoM / RBD,

Hydrography (WFD-Waterbodies, man-made objects)

Protected areas

….

Outlook

• 26 March – 20 April 2012 Preparation of Data Specifications v3.0

• 23 April – 11 May 2012 Preparation of draft Implementing Rule v1.0 (comments by TWG‘s 4 May until 9 May)

• 14 May – 8 June 2012 Review of draft Implementing Rule v1.0 by Member States

• 11 June 2012 – 29 June2012 Preparation of draft Implementing Rule v2.0

• 2 July – 27 July 2012 Interservice Consultation on draft

Implementing Rule v2.0

• 21 September 2012 Final draft Implementing Rule v3.0

• October/November 2012 (to be confirmed) INSPIRE COMMITTEE Meeting

√

Thank you for your attention !

Scope AM

covered by “Area Management Restriction and Regulation Zones” application schema

covered by requirements on reporting data

Example: River basin district

Middle Appenines

inspire and flood directive reporting: important issues to raise manuela pfeiffer wise...

Documents