1 inspire conference, edinburgh1 theme natural risk zones facilitator: matt harrison, uk editor:...

1INSPIRE Conference, Edinburgh 1

Theme Natural Risk Zones

Facilitator:

Matt Harrison, UK

Editor: Florian Thomas, France

JRC Contact Point: Robert Tomas

2

Surname Name Landslides Floods Forest Fires

Volcanic activity Earthquakes Droughts Storms IT

Bojilov Venco xCerba Otakar x x x x

Canet Castella Raquel x x x

Exadaktylos George x x xBarredo José x

Harrison Matthew x x x xPfeiffer Manuela x

Thomas Florian x xTomas Robert x x

Team

3

Presentation of the theme

• D2.3 Definition:

«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.»

4

Input documents

• 32 reference documents – The Floods Directive– Work carried out by « Plan4All »

• Annex I : Hydrography TWG has defined an « InundatedLand » feature class

5

Scope

• Analysis of input documents• Production of use cases

– « Flood » (Cross Thematic)– « Landslide »– « Forest fire»– « Earthquake »

• Codelist of 6 high level natural hazard categories– 82 hazards (so far)

• Meeting with Floods Directive working group

6


• Risk is defined as:

Risk = hazard x exposure x vulnerability.

• Natural risk:– Not technological risk

7


• Overall philosophy:

« A risk zone is the spatial intersection of a hazard area with Exposed elements some of which may have increased or lowered vulnerability to

this hazard »

Exposed

elements

Risk zoneHazard area

Vulnerability A

8

Model v2.0

• 3 packages : – 1 core package– 1 coverage package– 1 package dedicated to flood risk

• Objective : – Design a generic core model to all natural risks– Apply it to all types of data (vector and coverage)– As an example, apply this core model to flood risk

9

class 1_Core Mo...

«featureType»HazardArea

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfHazard: NaturalRiskOrHazardClassification

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

«voidable»+ levelOfHazard: LevelOfHazard+ likelihoodOfOccurence: LikelihoodOfOccurence

tagsbyValuePropertyType = falseisCollection = falsenoPropertyType = falsexsdEncodingRule = iso19136_2007_INSPIRE_Extensions

«featureType»RiskZone

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfRisk: NaturalRiskOrHazardClassification

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

«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: bool+ levelOfRisk: LevelOfRisk

constraints{A riskzone must be linked to 1 (or more) exposed elements}{legallyBindingZone - legalBasis}


«featureType»ExposedElements

+ geometry: GM_Object+ inspireId: Identifier+ typeOfElement: TypeOfExposedElementValue



VulnerabilityOfElement

«voidable»+ qualitativeVulnerability: CharacterString+ qualitativeVulnerabilityAssessmentMethod: DocumentReference+ quantitativeVulnerability: Number+ quantitativeVulnerabilityAssessmentMethod: DocumentReference

constraints{either the quantitative vulnerability or the quantitative vulnerability must be fi l led.}{If the qualitative vulnerability iscompleted, then the qualitative vulnerability assessment method must be fi l led.}{If the quantitative vulnerability is completed, then the quantitative vulnerability assessment method must be fil led.}

«featureType»Observ edHazard

«voidable»+ nameOfEvent: CharacterString

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

constraints{The likelihood of occurence is mandatory}


«featureType»ModelledOrDeterminedHazard

«voidable»+ determinationMethod: DeterminationMethodValue



Legal basis is to be harmonised with AM TWG

NOTE : An exposed element is typically any spatial object representing a real-world object or administrative/statistical unit, management are.

Therefore, it is impossible to explicitly define which INSPIRE spatial objects should be encoded as a Exposed Element.

This feature class therefore aims at including any spatial data which is considered as an exposed element, and for which a link to a risk zone is made, and vulnerability is calculated.

+sourcehazards0..*

affects

+resultHazard0..*

+riskZone«voidable»

0..*

isExposedTo

+exposedElement«voidable»

1..*

+result«voidable»

0..*+source«voidable»1

0..* 0..*

Model v2.0: Core package

Hazard area

Risk zone

Exposed element

Vulnerability

10

Model v2.0: Core package class 2_Enumerations and codelists

«enumeration»DeterminationMethodValue

modelling indirectDetermination

«dataType»NaturalRiskOrHazardClassification

+ riskOrHazardCategory: HazardCategoryValue

«voidable»+ specificRiskOrHazardType: SpecificRiskOrHazardTypeValue

«codeList»SpecificRiskOrHazardTypeValue

This code list is empty in the INSPIRE context and must be extended by each data provider in their own codeList register. In this register also mapping to the centralized list genericRiskOrHazardType must be provided

«codeList»HazardCategoryValue

+ 1_biological+ 1_1_Epidemic+ 1_2_InsectInfestation+ 1_3_AnimalStampede+ 2_geophysical+ 2_1_Earthquake+ 2_2_Volcano+ 2_3_DryMassMovement+ 3_hydrological+ 3_1_Flood+ 3_2_WetMassMovement+ 4_meteorological+ 4_1_Storm+ 5_climatological+ 5_1_ExtremeTemperature+ 5_2_Drought+ 5_3_Wildfire+ 6_extraterrestrial+ 6_1_Meteorite_Asteroid

This codelist is empty, and is to be extended by any data data provider

«codeList»TypeOfExposedElementValue

«codeList»Example_TypeOfExposedElement

+ existingLandUse+ openAirPublicArea+ publicAssemblyBuilding+ publicInterestEquipment+ transportInfrastructure+ numberOfInhabitants+ employment+ plannedLandUse

This codelist is provided as an example only. It is assumed that it is incomplete.

This codelist comes from the MünichRe - CRED. [Disaster Category Classification and peril. Terminology for for Operational Purposes. ].

We believe that this l ist has gaps. If data providers have a more specific classification, this should be completed inspecificRiskOrHazardTypeValue

11

Model v2.0: Coverage package class 3_Generic_cov erag...

«featureType»HazardCoverage

+ typeOfHazard: NaturalRiskOrHazardClassification+ inspireId: Identifier

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

«voidable»+ likelihoodOfOccurence: LikelihoodOfOccurence+ levelOfHazard: LevelOfHazard

«featureType»RiskCov erage

+ typeOfRisk: NaturalRiskOrHazardClassification+ inspireId: Identifier

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

«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: Boolean+ levelOfRisk: LevelOfRisk

«Invariant»{//the record must be a qualitativeValue (from LevelOfHazard) or quantitativeValue type (from LevelOfHazard), or riskOrHazardCategory (from NaturalRiskOrHazardClassification).}

«invariant»{////the record must be a qualitativeValue (from LevelOfRisk)or quantitativeValue type (from LevelOfRisk), or riskOrHazardCategory (from NaturalRiskOrHazardClassification).}

«featureType»ExposedElementsCov erage

+ inspireId: Identifier


The Record must express the type of exposed element. For a land-cover coverage, the record must be the land cover value according to a specific classification

«featureType»Coverage (Base)::Coverage

+ metadata: Any [0..*]+ rangeType: RecordType

«featureType»ModelledHazardCov erage

«voidable»+ determinationMethod: DeterminationMethodValue


«featureType»Observ edHazardCov erage


«voidable»+ nameOfEvent: CharacterString

NOTE : An exposed element is typically any spatial object representing a real-world object or administrative/statistical unit, management are.

Therefore, it is impossible to explicitly define which INSPIRE spatial objects should be encoded as a Exposed Element. T

his feature class therefore aims at including any spatial data which is considered as an exposed element, and for which a link to a risk zone is made, and vulnerability is calculated.

VulnerabilityOfElement

«voidable»+ qualitativeVulnerability: CharacterString+ qualitativeVulnerabilityAssessmentMethod: DocumentReference+ quantitativeVulnerability: Number+ quantitativeVulnerabilityAssessmentMethod: DocumentReference

+source«voidable»1

+result«voidable»

0..*

+sourceHazard0..*

+resultHazard0..*

+exposedElement 1..*

+riskZone 1..*

0..* 0..*

12

Exposed Element modellingHazard modelling

Model v2.0 Links

Natural risk zones

Land use

Hydrology

Geology Elevation

Stat. Units / Pop. distribution

Buildings

Administrative boundaries

Utilities / public services

Environmental monitoring facilities

Parallel

Consequences on land use planning

Land useArea management

13

Model v2.0: Core package class 4_xTWG_links

«featureType»RiskZone

+ geometry: RiskHazardGeometry+ inspireId: Identifier+ typeOfRisk: NaturalRiskOrHazardClassification


«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: bool+ levelOfRisk: LevelOfRisk

«featureType»EF_Model_V2.0RC::Env ironmentalMonitoringFacility

+ inspireId: Identifier+ geometry: GM_Object [0..1]+ representativePoint: GM_Point [0..1]+ name: CharacterString [0..*]+ additionalDescription: CharacterString [0..1]+ mediaMonitored: Media [0..*]+ typeOfMonitoring: MonitoringType [0..*]+ measurementRegime: MeasurementRegime+ gemetReference: ThemeValue [1..*]+ responsibleParty: CI_ResponsibleParty [0..*]+ responsiblePartyRole: RoleListType [0..*]+ legalBackground: LegislationReference [0..*]+ mobile: MobileValue+ resultAcquisitionSource: ResultAcquisitionSourceValue [0..1]

«voidable»+ beginLifespan: DateTime+ endLifespan: DateTime [0..1]+ beginOperationalActivityPeriod: DateTime+ endOperationalActivityPeriod: DateTime [0..1]

Coverage

«featureType»2_Generic_coverages::RiskCoverage

+ typeOfRisk: NaturalRiskOrHazardClassification+ inspireId: Identifier

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

«voidable»+ determinationMethod: DeterminationMethodValue+ legalBasis: LegislationReference [0..*]+ legallyBindingZone: Boolean+ levelOfRisk: LevelOfRisk

Recommandation : If a risk zone or a risk coverage is legally binding, then it should be linked to a feature of Land-Use "CoreLandUseObject" or to a Area Management Restriction Regulation Zoes and Reporting Units "ManagementRestrictionOrRegulationZone"

«featureType»Area Management Restriction and Regulation Zones::

ManagementRestrictionOrRegulationZone

+ inspireID: Identifier+ thematicID: AlternateIdentifier [0..*]+ name: GeographicalName [0..*]+ geometry: GM_Object

«voidable»+ zoneType: ZoneTypeCode+ specialisedZoneType: SpecialisedZoneTypeCode [0..1]+ validTime: TM_Period+ competentAuthority: CI_ResponsibleParty+ legalBasis: LegislationReference [0..1]

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

constraints{legalBasis mandatory if not provided on SpatialDataSet level}{Geometry shall be surface or multi-surface}{Either managementInformation or controlledActivity is mandatory}

«featureType»Land Use Core Model::

CoreLandUseObject

0..*

+monitors 0..*

+areaManagement

0..*

+zoningElement 0..*

anyThematicLink

+broader0..* hierarchy

+narrower0..*

+supersede0..* genealogy

+supersedeby 0..*

+zoningElement 0..*

0..*

+monitors

0..*

+areaManagement 0..*

+relatedZone0..*

fthomas

Added a new slide to complete description of the core model

fthomas

added this one also

14

Model v2.0 : Flood Package

• « Why floods and no other hazard? »– Flood Directive 2007/60/CE

• Overall idea: – Take the core model, eventually specialize it, to

make it meet Flood Directive’s requirements– Use the navigability of the links to avoid

redundances, and the constraints to ensure the coherence of the model

15

class Floods

«codeList»InundationValue

+ controlled+ natural

HydroObject

«featureType»InundatedLand

+ dateOfObservation: DateTime+ geometry: GM_Surface+ inspireId: Identifier


«voidable»+ inundationReturnPeriod: Number+ inundationType: InundationValue

constraints{Inundated land is observed}

«featureType»NaturalRiskZones::HazardArea

+ geometry: GM_MultiSurface+ inspireId: Identifier+ typeOfHazard: HazardType


«voidable»+ classificationMethod: URI+ determinationMethod: DeterminationMethod+ levelAssessmentMethod: URI+ levelOfHazard: LevelOfHazard+ momentOfHazard: MomentOfHazard

constraints{Only observed hazards can be linked to vulnerable features and vulnerable zones}

«dataType»PreliminaryFRAssessment



«voidable»+ reference: CL_citation

constraints{Vulnerable feature that are linked must be the ones linked to the Inundated Lands}

«featureType»NaturalRiskZones::RiskZone

+ geometry: GM_Surface+ inspireId: Identifier


«voidable»+ classificationMethod: URI+ determinationMethod: DeterminationMethod+ levelAssessmentMethod: URI+ levelOfRisk: LevelOfRisk

constraints{A risk cannot be observed}{A riskzone must be linked to 1 (or more) vulnerable feature or to 1 vulnerable zone}

«dataType»FloodHazardMap



«voidable»+ Reference: CL_citation

constraints{A flood hazard map must contain one high probability prospective flooded area, one medium probability and one low probability prospective flooded area. For groundwater or seawater floods, then it is possible to fi l l in only one low probability potential}{For groundwater or seawater floods, then it is possible for a FloodHazardMap to fi l l in only one low probability potential flooded area}

«dataType»FloodRiskMap



«voidable»+ reference: CL_Citation

constraints{The risk zones composing the Flood Risk Map are those derived from the potential flooded areas that are in the Flood Hazard Map which is l inked to the Flood Risk Map}{The vulnerable features that are on the flood risk Map are those linked to the risk zones that are on the same flood risk Map}

«featureType»PotentialFloodedArea

+ floodProbability: ProbabilityOfFlood+ geometry: GM_MultiSurface+ inspireId: Identifier


constraints{Potential flooded areas are modelled.}

«enumeration»ProbabilityOfFlood

low medium high

«featureType»PotentialFloodedAreaElement


«voidable»+ floodFlow: int+ velocityOfFlow: int+ waterHeight: int+ waterlevel: int

constraints{Either water heights or water levels must be fi l led}{Either velocity of flow or flood flow must be fi l led}

«featureType»NaturalRiskZones::VulnerableFeature

+ geometry: Any+ inspireId: Identifier


«voidable»+ classificationMethod: URI+ exposure: float+ exposureMethod: URI+ levelAssessmentMethod: URI+ levelOfVulnerability: LevelOfVulnerability

+involvedFeature 0..*

+observedHazard 0..*

+riskZone

0..*

+hazardArea

1..*

+sourcehazards0..* results

from

+resultHazard0..*

+componentOf

1..*

+contains 0..*

+result 1..*

+origin 0..*

+inundatedLandVulnFeature

0..*+pFRA

0..*

+involvedFeature 0..*

+riskZone 0..*

+componentOf

1..3

+contains 1

+vulnFeature

+frMap

+componentOf

1..3

+contains

0..1

+fhMap

+frMap

+componentOf

+contains


Risk zone

Exposed element

Flood hazard map

Flood risk map

Preliminary flood risk assessment

Potential flooded area

Hazard area

Inundated Land(Annex I Hydrography)

16


• New classes compared to the generic package : • « Potential flooded area » : specialized from

« hazard area »• Flood hazard map• Flood risk map• Preliminary flood risk assessment• « inundated land » : specialized from « hazard

area »• Some concepts :

• The « potential adverse consequences » are « exposed elements »

• The « flood hazard maps » must contain 3 flood scenarios they contain 3 features from the « Potential flooded area » feat. class

17

Open Questions

• Generic Core model- useful/ useable?• More specific hazardTypes codelist?• exposedElements codelist?• Floods Schema

– Doesn’t address detailed requirements?– Can you identify how you could extend it further?– Does it demonstrate harmony between FD and INSPIRE?

• More application schemas as examples?• Example implementation e.g. in major GIS software?• Geometry of risk zones / coverages Currently model vector

data model and coverage separately• Portrayal rules/ guidelines• DQ & MD Chapters still require work

1 inspire conference, edinburgh1 theme natural risk zones facilitator: matt harrison, uk editor:...

Documents

model slide

core package slide

technological risk slide

coverage package slide

flood risk objective

flood hazard maps

theme risk

group slide