fdrdg10 6 gis guidance fhrm ver5 clean20130624

7/29/2019 Fdrdg10 6 Gis Guidance Fhrm Ver5 Clean20130624

1/93

Reporting of spatial data

for the Floods Directive

(Part II)

Guidance on reporting for flood

hazard and risk maps of spatial

information


2/93


3/93

Tools and services for reporting under

WISE

Guidance on reporting of spatial data forthe Floods Directive (part II)

Version 5

June 2013

Notice

This report was produced for the European Commission for the specific purpose of creating a guidancedocument on reporting of spatial data under the Floods Directive.

This report may not be used by any person other than the European Commission without the EuropeanCommissions express permission. In any event, Atkins accepts no liability for any costs, liabilities or lossesarising as a result of the use of or reliance upon the contents of this report by any person other than theEuropean Commission.

Atkins Limited


4/93

Document History

JOB NUMBER: DOCUMENT REF: FDRDG10-6-GIS guidance-FHRM-ver5_CLEAN20130624

0.1 First draft Maidens Wolstrup 29.04.11

0.2 Updates from Wolstrup comments Maidens Brattemark (Comm) 03.05.11

0.3 Updates with Comm comments Maidens Brattemark, Jacobsen (EEA) 05.05.11

1 Updates with further Comm and EEAcomments

Maidens 01.06.11

2 Comments from FDG Maidens 20.06.11

3 Comments from MS Maidens 8.09.11

4 Incl. pilot project Wolstrup 18.03.13

5 Incl comments from Member Statesand JRC

Wolstrup 24.06.13

Revision

Purpose Description Originated Checked Reviewed Authorised Date


5/93

Guidance Document No:22

Guidance on Implementing the Geographical Information System (GIS) Elements of the EU Water policy

Appendix 13.3: Guidance on the reporting

of geographical data

5

Contents

Section Page

Abbreviations 81. Introduction 91.1 Overview 91.2 Flood hazard and risk map content 91.3 Reporting arrangements 101.4 Other reporting under the Floods Directive 122. Scope 142.1 FD reporting schemas 142.2 Related documents 142.3 Getting help 143. As-is analysis and gap analysis 153.1 EXCIMAP analysis 153.2 Interactive flood map examples 164. User requirements 235. Products at the European level 245.1 Overview 245.2 Maps produced for the WISE viewer 245.3 Flood hazard and risk maps European overview 256. Data content and structure for reported floods information 276.1 Overview 276.2 Information to be reported 276.3 How the Commission will use the information 317. Maintenance 338. Data content and structure for decentralised Flood maps 348.1 Overview 348.2 Maps 358.3 Map context 368.4 Map 1: Flood hazard map and probabilities 378.5 Map 2: Flood risk map and population 388.6 Map 3: Flood risk map and economic activity 388.7 Map 4a: Flood risk map and environment: installations 398.8 Map 4b: Flood risk map and environment: WFD protected areas 408.9 Map 5: Flood risk map and other vulnerability information (optional) 408.10 Map 6: Other significant sources of pollution (optional) 41


6/93





6

8.11 Map 7: Other useful information (optional) 418.12 Map 8: Coastal protection (optional) 419. Data production 439.1 Spatial resolution 439.2

Spatial representation 43

9.3 Coordinate reference system 439.4 Trans-boundary flood mapping for reported information 4410. Data exchange format for submitted information 4510.1 Formats 4510.2 Naming of files 4510.3 Data upload 4611. Data exchange format for decentralised information 4711.1 Overview 4711.2 INSPIRE 4711.3 WMS 4711.4 WMS profile 4811.5 WMS service metadata 4811.6 WMS Layer metadata 4911.7 GetMap request parameters 5112. Metadata 5312.1 WISE metadata profile 5312.2 Metadata creation 5313. Data access and constraints 5413.1 Data usage 5413.2 Data Distribution 5414. Coordination and organisation 5614.1 Helpdesk 5615. Reporting documents and links 571. Overview 771.1 Abstract 772. Publishing 772.1 Target publish date 772.2 Mapviewer 773. Data and pre-processing 773.1 Content datasets 773.2 Data extraction 773.3 Data extraction and processing steps 803.4 Derived datasets 804. Visualisation 81


7/93





7

4.1 Layer 1: Population 814.2 Layer 2: Economic activities9 814.3 Layer 3: IED installations9 824.4 Layer 4: Other potential consequences9 824.5 Background theme maps 834.6 Discomap services 834.7 Map spatial layers 835. Interaction 855.1 Layer selection 855.2 Pop-up windows 866. Specific map explanation text 88Appendix A: Description and specification of metadata elements for the reporting of the geographic

information

Appendix B:Map layer specification for flood hazard and risk maps

Appendix C:Procedure on how to link to national maps from EU portal


8/93





8

Abbreviations

Term Meaning / Definition

EC European Commission

EEA European Environmental Agency

ETC-W European Topic Centre Water

FD Floods Directive

FHRM Flood Hazard and Risk Map

FHM Flood Hazard Map

FRM Flood Risk Map

GIS Geographic Information System

GML Geographic Markup Language

GWB Groundwater body

GWD Groundwater Directive

ID Identifier

IR Implementation Rule

INSPIRE Infrastructure for Spatial Information in Europe

MS Member StateNMA National Mapping Agency

POM Programme Of Measures

RBD River Basin District

RBMP River Basin Management Plan

Scenario Probability

SWB Surface Water Body

UOM Unit Of Management

WB Water Body

WFD Water Framework Directive

WISE Water Information System for Europe

XML Extensible Markup Language


9/93


10/93





10

(b) flood with a medium probability (likely return period 100 years);

(c) floods with a high probability, where appropriate.

Members States have flexibility to assign specific flood probabilities to these scenarios.

For each scenario, Members State must prepare information of flood extents and water depth or

levels (art 6.4). Where appropriate, Members States could also prepare information on flow

velocities or the relevant water flow.

For each flooding scenario, the flood risk maps shall show:

1. the indicative number of inhabitants potentially affected;

2. type of economic activity of the area potentially affected;

3. installations as referred to in Annex I to Council Directive 2008/1/EC (codified version of

Directive 96/61/EC of 24 September 1996) concerning integrated pollution prevention and

control which might cause accidental pollution in case of flooding and potentially affected

WFD protected areas identified in Annex IV(1)(i), (iii) and (v) to Directive 2000/60/EC;

The maps may show other information which the Member State considers useful such as the

indication of areas where floods with a high content of transported sediments and debris floodscan occur and information on other significant sources of pollution.

For coastal flooding where there is an adequate level of protection in place, and for groundwater

flooding, Member States can decide to limit the preparation of flood hazard maps to low probability

or extreme events (art 6.6 and 6.7).

1.2.1 Guidance structure

This guidance document is the continuation of the agreed reporting sheet with the goal of defining

the reporting needs

Chapters 1, 2, 3, 4, 7 and 10 are background or 'supporting' chapters

The backbone of the document is the reporting arrangements which are distributed between fourchapters:

Chapter 5 describes what will be shown at European level through WISE

Chapter 6 describes the information the Member States are expected to report which will be

used in the visualisation at European level (chapter 5)

Chapter 8 deals with the content of the national level maps, Member States are expected to

set up in accordance with the Directive in a distributed manner.

Chapter 11 describes the delivery mechanism for distributed maps

Development of reporting/data exchange formats and visualisation shall furthermore be in line with

relevant requirements of INSPIRE, in particular as regards the Annex III theme Natural RiskZones, but also in relation to other relevant themes e.g. area management / restriction / regulation

zones and reporting units.

1.3 Reporting arrangements

As written in the reporting sheet for flood hazard and risk maps (reference #2, pg 3), All reporting

under the Directive should be done electronically via WISE (Water Information Systems for

Europe). The reporting of Flood hazard maps and flood risk maps however presents two main

challenges in this context.

Firstly, the current scale of visualisation of maps in the current WISE map viewer (scale 1:250000)might not be the appropriate scale for such maps, as mentioned in the Directive.


11/93





11

Secondly, the INSPIRE Directive rules for metadata on relevant topics may not be fully operational

until after 2014, that is most likely after the reporting deadline for the flood hazard maps and flood

risk maps.

The road map for implementation of the Commission Regulation (EC) No 1205/2008 of 3

December 2008 as regard Metadata (for both data sets and services) are:

- Data sets and services of Annex I and II - Implementation by the 03.12.2010

- Data sets and Services of Annex III - Implementation by the 03.12. 2013

The implementation of the INSPIRE Directive rules for metadata on both data and services should

be operational by the end of 2013 and therefore fully implemented when the reporting deadline for

the flood hazard and risk map are due on the 22nd

of December 2013.

This leads to a two pronged approach on reporting and visualisation of flood maps via WISE.

To address these challenges, a decentralised and staged approach to reporting flood maps will be

implemented. The detailed and reference data for the flood hazard maps and flood risk maps shall

rest in the national repositories for these maps (the decentralised approach), with web-links to

these maps provided through geographical information as set out in section C (of the reporting

sheet) (and through textual information on methodologies) provided to the public through WISE.

Under the staged approach, it is proposed that in the short term (until 2014) the reporting of flood

maps should be based on textual information on methodologies used, and reporting of

geographical information as set out in section C (of the reporting sheet), with web-links to detailed

maps held in the Member States. This should be visualised in a way which allows the user to

select an area from the EU-wide WISE background map, and then via hyperlink established in

WISE, to switch and to zoom into the correct area at MS level. This will also take into

consideration the reporting of existing maps according to article 13.2.

The technical solution (web services) for providing national floods maps should in addition also be

in line with the Implementing Rules for INSPIRE Network Services (Discovery, View, Download,

Transform) Commission Regulation (EC) No 976/2009 which have the following implementingdates:

- Discovery and View - Implementation by the 09.11.2011

- Download and Transformation - Implementation by the 28.12.2012

Data, as set out in section C (of the reporting sheet), shall be reported which are required to

enable compliance checking by Commission and production of certain maps and reference data

sets to be produced at the European level (WISE scale). The content of reporting as described in

the Reporting Sheet reflect what is needed for the compliance checking or for the production of

complete reference datasets across EU27 for other uses by the Commission, including JRC and

EEA. However, some data can be labelled conditional (only applies for certain conditions) or

optional for additional reporting where this information is available and can provide added value. .

In the longer term as INSPIRE is being implemented, notably to be in place for the second cycle of

flood maps (deadline for establishing maps: 22.12.2019), the format for reporting/data and

information exchange and visualisation/displayed of flood maps should be in a decentralised

mode foreseen by that Directive, and in line with a Shared Environmental Information System

(SEIS) initiative and made available via WISE.

1.3.1 Reporting arrangements stages applied to this document

Stage 1 first reporting cycle

Chapter 6 describes the reporting to the Commission of spatial and XML data

Chapter 8 describes the content of the national level maps, but only where datasets areexistence (i.e does not expect pre-compliance with INSPIRE data specifications). However


12/93


13/93





13

http://circa.europa.eu/Members/irc/env/wfd/library?l=/floods_programme_1/d-

drafting_groups/reporting_grafting/reporting_sheets&vm=detailed&sb=Title

1.4.2 Preliminary Flood Risk Assessment

Article 4 of the Floods Directive requires Member States to undertake a Preliminary Flood Risk

Assessment (PFRA) for each river basin district, unit of management or the portion of an

international river basin district or unit of management lying within their territory. The identification

of areas with a potential significant flood risk (art. 5) will be based on available or readily derivable

information including the requirements specified in the directive (art. 4).

Available or readily derivable information should, where possible, include details of:

Significant floods that have occurred in the past and their location, extent, conveyance routes

and adverse consequences, and other floods that occurred in the past which would have

significant adverse consequences if they occurred again;

Potential adverse consequences of future floods;

Impacts of climate change and long-term developments on the occurrence of floods; and,

Other available or readily derivable information, as relevant to the Member State, on issues

such as topography, the position of water courses and their general hydrological and geo-

morphological characteristics, including flood plains as natural retention areas, the

effectiveness of existing flood defence infrastructure, and the position of populated areas and

areas of economic activity.

Article 5 requires that the PFRA shall be used as the basis for the identification of areas for which

Member States conclude that potential significant flood risk (APSFR) exist or might be considered

likely to occur in the future for each river basin district, unit of management or the portion of an

international river basin district or unit of management lying within a Member States territory.

Member States shall complete the preliminary flood risk assessment by 22 December 2011.


14/93


15/93





15

3. As-is analysis and gap analysis3.1 EXCIMAP analysis

The following is extracted from Excimap:

http://ec.europa.eu/environment/water/flood_risk/flood_atlas/pdf/flood_maps_ch8.pdf

It is intended to post this information in the guidance from the EXCIMAP and Member

States can update this information during the review period as it dates from 2007.

Most countries have flood extent maps. This flood extent should be related to a specified flood

frequency.

Frequencies used in the maps vary from 1/30 to 1/10.000. Most countries use only 2 or 3 different

frequencies (e.g. 1/100 and 1/1000, or the less accurate frequent and exceptional), Flanders

seventeen (2, 5, 10, 15, 20, 25, 30, 40, 50, 75, 100, 150, 200, 250, 300, 500 and 1000 years).

England & Wales distinguish between floods originating from the sea (1/200) and flood from rivers

(1/100), while Ireland gives an indication of the uncertainty of the flood extent. Maps become

difficult to read when flood extent is presented in iso-lines (instead of coloured surfaces) or when

current velocities are presented is arrows (that may merge together with parallel current lines).

Often flood extent for different frequencies is presented in one map. Increasing intensities of blue,

suggesting increasing flood depth, represent the most frequent flooded (deeper) areas (like

England & Wales, Finland, Germany). Flood depth maps may be presented for one representative

flood frequency, e.g. 1/100. An interesting example is from Japan, in which the flood depth

intervals are such that it contains danger/how to act information for individuals. In France maps

exist that also present flood duration.

Information on historic floods is shown on maps from France, Finland and Ireland. With this type

of information one should be aware that since this flood event floodwave characteristics andfloodplain topography may have changed considerably and that therefore this historic flood may

not representative for present conditions. However, this information is valuable to increase flood

awareness.

Flood hazard maps, indicating where the combination of current velocity and waterdepth may be

dangerous, are published in England & Wales. Austria uses the more or less comparable drag

force parameter. In Rheinland-Pfalz (Germany) and Switzerland this velocity-depth information is

related to frequency, expressing this hazard information in a more sophisticated way for

professional users. The dominant colours for this type of hazard information are red, orange and

yellow.

In terms of flood risk maps, official maps indicating potential damage are rare. The only examples

are from Germany (Rheinland-Pfalz, Sachsen). Italy, Spain and Switzerland have official risk zone

maps. These maps are based on the probability of flooding in combination with the land use

sensitivity /vulnerability to flooding. In Italy and Switzerland this risk zonation relates to spatial

planning regulations and construction requirements. Specific vulnerability maps are available in

England & Wales (social vulnerability of the population) and Sachsen (Germany) (vulnerable

services, like hospitals).


16/93





16

3.2 Interactive flood map examples

Editorial remark: It is intended to include a complete survey here of currently available interactive

flood map services, please provide other to the Commission if available.

3.2.1 Spain

http://sig.marm.es/snczi/visor.html?herramienta=DPHZI

3.2.1.1 Flood layers available

Areas of significant flood risk (partial coverage)

Flood scenarios (10, 50,100,500 years)


17/93


18/93





18

3.2.3 Luxembourg

http://eau.geoportal.lu/

3.2.3.1 Flood layers available

Flood hazard maps (10yrs, 100yrs , extreme)

Flood risk maps (10yrs, 100yrs , extreme)

Other flood related information


19/93


20/93


21/93


22/93





22

o Flooded areas and use

o Residents in flood-prone area per municipality

o Specific hazards

o Infrastructure

o Road/rail network

o Rivers


23/93


24/93





24

5. Products at the European level5.1 Overview

The aim of this section is to describe the output map products which will be produced at the

European level. This section is intended to expose the approach which will be taken in order for

these maps to be developed.

It is important to convey these maps will not necessarily provide the exact same message as the

national level maps. The goal of these maps is not the same as the national level maps. These

maps are intended to draw the attention of the user or citizen to areas of interest. This section is

showing what will be done at European level in order to build up a picture, drawing attention to

where the information has been reported and where national FHRM are available and the user

can zoom in to see.

Where possible information will be used from the Member State reporting, other Directives and

other European data sets. This is phase 1, as it is envisaged that INSPIRE will make availablemuch more information from Member States which will be used to underpin the Flood hazard and

risk maps.

5.2 Maps produced for the WISE viewer

The intention is to disseminate certain aspects of the reported FD data and information via WISE,

and where necessary, appropriate and possible, provide links to data and information from other

sources such as national flood maps which can provide a higher resolution than WISE which will

be more appropriate for flood mapping purposes (larger scale than 1:250.000).

This chapter describes the proposed European level map. This will be derived from informationreported by the Member States (further details in the next chapter) and other European level

datasets available, for example from other reporting streams and INSPIRE.

Within this European level viewer, the user will also be able to access Member State flood maps

available as INSPIRE Network Services or links at larger zoom scales.

5.2.1 Data to be used in the maps

Section 6 details the reporting needs under this Directive. The reporting to the Commission is a

combination of spatial information (GIS layers) and tabular information (xml). The European level

view of the Floods hazard and risk maps will be derived from a combination of Member State

submissions and other datasets available at European level, primarily from other reporting

streams. To summarize though, it would be expected Member States are reporting the following:

APSFR/UoM

Information under the medium probability where applicable and for coastal and groundwater

floods under the low probability

Summary data for exposed elements (e.g. population) for relevant probability (see reporting

sheet section C Data point 1-6.)


25/93


26/93





26

With the services it is expected a legend will also be provided and metadata, both of which will be

made available to the user to ensure the context of the maps are correctly interpreted. This is

critical when it is likely there will be no consistent implementation of map presentation.

The Member State services should only provide the hazard and risk maps. The background maps

.e.g streets, aerial etc will be provided by the European service even at large scales beyond

1:250,000.


27/93


28/93


29/93





29

6.2.1.3 GML application schema.

Data conformant to the application schema Natural Risk Zones shall be encoded using the

encoding specified and distributed with the INSPIRE data specification.

6.2.2 XML schema

The XML schema will be used for the reporting of certain summary information and data. The XML

schema is used to provide structure for the reporting. The reporting schema, guidance and

provided tools can be found at http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

6.2.2.1 Schema structure overview

The XML schema is available at the above link with a separate reporting guidance. The broad

structure is provided here to aid in the understanding of the reporting and linkages to the other

sections in this document:

6.2.2.2 Summary text

The following list provides broad groupings of the information to be reported. However, in

execution the schema developed has a more structured approach, breaking down the free textfields into more discrete and targeted items. This facilitates the definition of the requirement and

the use of the information after reporting.

1. Summary (< 10.000 characters) on methods used to identify, assess or calculate: flooding

extent (including resolution of digital terrain models); flooding probabilities (including

information as to why particular probabilities have been selected) or return periods; depths

or water levels; velocities or flows (where appropriate); models used, datasets, uncertainties,

if and if so how, climate change has been taking into account in the mapping(article 6);

2. Where particular flood scenarios have been omitted , a summary (< 5000 characters)

information on the exclusion of particular groundwater or coastal flooding scenarios, and a

justification for these decisions, including information on the justification that adequate level

of protection is in place in coastal areas and where articles 6.6 and 6.7 has been applied.

6-1 Principles of the structure of the XML reporting schema (simplified)


30/93





30

3. Summary (< 5000 characters) of methods (including criteria) used to determine, for each

flood scenario,

i. the indicative number of inhabitants affected (art 6.5.a),

ii. the type of economic activity affected(art 6.5.b,

iii. location of IPPC installations(art 6.5.c),

iv. the impact on WFD protected areas (art 6.5.c);

v. other information considered relevant by Member States (art 6.5.d)

4. Summary text (


31/93


32/93


33/93


34/93


35/93


36/93





36

4. Flood risk maps showing the potential adverse consequences expressed in terms of the

location of installations which might cause accidental pollution in case of flooding and

potentially affected areas identified in WFD Annex IV(1)(i) (iii) and (v) the flooding scenarios

(art 6.5(c));

Optional geographic information

The reporting sheet lists the following optional geographical information:

1. Areas vulnerable to floods with a high content of transported sediment and debris flows for

each flood scenario (art 6.5(d)).

2. The location of other significant sources of pollution, including the areas potentially affected

where possible (art 6.5(d)).

3. Maps with other information that Member States may consider useful (art 6.5 (d) (examples

may be , flood event maps, flood damage maps, maps or areas benefiting from protection

against flooding, evacuation maps, maps relating to other potential natural or manmade

hazards, etc

4. Maps showing coastal areas where adequate level of protection is in place, and where

article 6.6 will be applied (NB: IF article 6.6 is applied, this map is mandatory).

8.3 Map context

According to the recommendations from the Excimap (reference #1), these maps are to be made

available at the national level and it is important to note for interpretation they should all be

accompanied by the following in some capacity. Information that is important for use and that

explain the content of the map includes:

Title: brief description of the map, including its content and / or purpose (for flood maps

particularly important are the considered probabilities or recurrence intervals

Responsible authority (organisation responsible for the development and publishing of the

maps, with contact details)

Date of preparation / publication

Legend (textual description of symbols, colours, line features, etc.)

Purpose of development and intended use

Method of development

Limitations of map and / or assessment of uncertainty (if available)

Disclaimer (to enforce explanatory information and limitations, and provide legal protection to

the responsible authority against adverse consequences of misuse)

North and scale: preferably using scale bar as this allows for changes in page size

The scope and detail of the explanatory information should be appropriate to the intended

audience.

Maps intended for public use should be simple and self-explanatory and include a clear

legend, such that as little supporting or explanatory information as possible is required for

correct interpretation.


37/93


38/93





38

8.5 Map 2: Flood risk map and population

8.5.1 Rationale

Flood risk maps showing the potential adverse consequences expressed in terms of the indicative

number of inhabitants potentially affected under the probability (art 6.5(a));

8.5.2 Visualisation suggestions

For this map it would be expected a layer would be provided which classifies the probabilities

according to the population.

Probabilities classified according to type of consequence human health (reference #4):

Human Health: Adverse consequences to human health, either as immediate or

consequential impacts, such as might arise from pollution or interruption of services related to

water supply and treatment, and would include fatalities.

Community: Adverse consequences to the community, such as detrimental impacts on local

governance and public administration, emergency response, education, health and social

work facilities (such as hospitals). Other

8.5.3 INSPIRE linkage

Natural risk zones Observed Event, Hazard Area, Risk Zone and Exposed Element

Population distribution - demography

Human health and safety

8.6 Map 3: Flood risk map and economic activity

8.6.1 Rationale

Flood risk maps showing the potential adverse consequences expressed in terms of the type of

economic activity of the area potentially affected under the probability (art 6.5(b));


Land use classification. Point locations for storage of chemicals, vital networks and services

(highways, railways, airport, lifeline services like electricity, sewerage and drinking water,

hospitals, etc). Critical infrastructure, unless classified information. Probability classified according

to type of consequence - economic (reference #4):

Property: Adverse consequences to property, which could include homes

Infrastructure: Adverse consequences to infrastructural assets such as utilities, power

generation, transport, storage and communication.

Economic Activity: Adverse consequences to sectors of economic activity, such as

manufacturing, construction, retail, services and other sources of employment. (see reference

#4, note v)

Other

Probabilities classified according to type of consequence cultural heritage (reference #4):


39/93





39

Cultural Assets: Adverse permanent or long-term consequences to cultural heritage, which

could include archaeological sites / monuments, architectural sites, museums, spiritual sites,

and buildings.

Landscape

Other



Hydrography such as hydro facilities

Land use

Industrial and production facilities

Agricultural and Aqua-cultural facilities

Utility and government services

Transport networks

Buildings

8.7 Map 4a: Flood risk map and environment: installations

8.7.1 Rationale

Flood risk maps showing the potential adverse consequences expressed in terms of the location

of installations as referred to in Annex I to Council Directive 2008/1/EC (codified version of

Directive 96/61/EC of 24 September 1996) concerning integrated pollution prevention and controlwhich might cause accidental pollution in case of flooding.


For this map it would be expected the minimum the Member State will show is what has been

reported under the EPRTR, but it is expected they have more detailed information.

This layer will show point locations of installations (for a specific industrial activity or NACE code)

as they are reported under the E-PRTR Directive

Point locations of UWWT plants

Probabilities classified according to type of consequence - environment (reference #4):

Pollution Sources: Sources of potential pollution in the event of a flood, such as IED and

Seveso installations, or point or diffuse sources.



Industrial and production facilities

Hydrography


40/93





40

8.8 Map 4b: Flood risk map and environment: WFD protected areas

8.8.1 Rationale

Flood risk maps showing the potential adverse consequences expressed in terms of the locationof potentially affected WFD protected areas identified in Annex IV(1)(i), (iii) and (v) to Directive

2000/60/EC.


For this map it would be expected the minimum the Member State will show is what has been

reported under the WFD, but it is expected they have more detailed information.

The WFD information referred to is the following:

1. Areas designated for the abstraction of water intended for human consumption under Article 7

of the WFD;

2. Recreational waters and Bathing waters3. Areas designated for the protection of habitats or species.

Probabilities classified according to type of consequence - environment (reference #4):

Waterbody Status: Adverse permanent or long-term consequences ecological or chemical

status of surface water bodies or chemical status of ground water bodies affected, as of

concern under the WFD. Such consequences may arise from pollution from various sources

(point and diffuse) or due to hydromorphological impacts of flooding.

Protected Areas: Adverse permanent or long-term consequences to protected areas or

waterbodies such as those designated under the Birds and Habitats Directives, bathing

waters or drinking water abstraction points.

Other: Other potential permanent or long-term adverse environmental impacts, such as those

on soil, biodiversity, flora and fauna, etc.



Protected Sites

8.9 Map 5: Flood risk map and other vulnerability information

(optional)

8.9.1 Rationale

Areas vulnerable to floods with a high content of transported sediment and debris flows for each

probability (art 6.5(d))

This map would be derived from firstly an analysis of flow velocity, a map product in itself.

Therefore the flood hazard is represented by the the velocity at a particular location. .

(Flow velocity is highly localized information which can be represented at a detailed scale)


41/93





41


Vulnerable areas delineated

Probability classified by vulnerable areas



8.10 Map 6: Other significant sources of pollution (optional)

8.10.1 Rationale

The location of other significant sources of pollution, including the areas potentially affected where

possible (art 6.5(d)).


Other significant sources as points or polygons on the map.

Probabilities classified according to other significant sources of pollution.



8.11 Map 7: Other useful information (optional)

8.11.1 Rationale

Maps with other information that Member States may consider useful (art 6.5 (d) (examples may

be , flood event maps, flood damage maps, maps or areas benefiting from protection againstflooding, evacuation maps, maps relating to other potential natural or manmade hazards, etc


In any interpretation


MS dependant

8.12 Map 8: Coastal protection (optional)

8.12.1 Rationale

Maps showing coastal areas where adequate level of protection is in place, and where article 6.6

will be applied. This map should only be developed for the extreme flood extents.


Polygons or lines marking the coastal areas where protection is in place. These can be polygons

or lines which demark the protection.

Mark the protection with a point or line on the map and the area that is protected with a hatched

area. The area protected would be the flood extent for the most extreme event which the defence

is built against (protection grade).


42/93


43/93





43

9. Data production9.1 Spatial resolution

9.1.1 Scale

Member States are recommended not to simplify spatial data before submitting to WISE for

reporting. The accuracy of the data should however be documented in the metadata so the

simplification process performed in WISE during e.g. reference data production can respect the

original accuracy.

Considering both the WISE needs and the practical constraints of data availability, the GIS

Working Group recommends that the required positional accuracy for reported data should be

better than 125 metres (1:250 000). The positional accuracy should always be kept as high as

possible and ideally be similar to the national operational datasets.

9.1.2 Positional accuracy

This quality sub-element shows the closeness of reported coordinate values to values accepted

as or being true. All spatial objects should be provided at the source accuracy where possible.

Where more than one geometry is available at the source, the provided geometry should be the

one with the highest spatial detail; i.e. a surface geometry is provided where both surface and

point geometry is available or where both surface and linear geometry is available.

Considering both the WISE needs and the practical constraints of data availability, it is

recommended that the required positional accuracy for reported data is set to a minimum of

125 metres (corresponding to a scale of 1:250.000) and a maximum of 500 meters

(corresponding to a scale of 1:1.000.000). The positional accuracy should however always be keptas high as possible and ideally be to the same as the national operational datasets.

For more information see Chapter 5.1, WISE GIS guidance document, second edition.

9.2 Spatial representation

Please refer to section 7 for the spatial representation of the different information.

9.3 Coordinate reference system

Data should be delivered in the spheroid coordinates (decimal degrees) in the geodetic datum

ETRS-89 (EPGS code 3035) http://www.epsg-registry.org/) and follow the INSPIRE requirements

for coordinate reference systems (see section 6 of the INSPIRE data specifications).

At national level, a series of different coordinate reference systems is used. It is essential that

conversion from a national coordinate reference system is done with care. If conversion is not

done correctly data will lose positional accuracy. Proper transformation routines have to be

observed.

The National Mapping Agencies (NMA) (or comparable institutions and organisations) have

provided the information for the descriptions of the national Coordinate Reference Systems and

for the transformation parameters between the national Coordinate Reference Systems and the

European Coordinate Reference System ETRS89. Formulae can be requested from the NMAs or

are directly accessible at http://crs.bkg.bund.de/crs-eu/


44/93





44

The transformation between national systems and the European coordinate reference system is

done using the agreed transformation parameters for different countries (see the link above).

9.4 Trans-boundary flood mapping for reported information

Transboundary flood objects should be harmonised with the respective neighbouring countrieswhere applicable. Appendix B of the INSPIRE document D2.6 Methodology for the development

of Data specifications provides recommendation regarding the geometric harmonisation of linear

and polygon features across borders (edge matching).

The hydrographic network data should be edge-matched, reconciled and maintained across state

borders by the respective authorities.

In considering reconciliation across state borders, the respective authorities should seek to fully

resolve the positional alignment that minimises positional deficiencies. Positional deficiencies

require repeated manual interval in updates and/or detract from the use of the data in applications.

Wherever a feature crosses a border it is recommended that the parties holding the source data

for this feature across the border make arrangements for the geometry to be the same across theborder, i.e. that at the same level of detail - no surface geometry meets a point or line geometry.


45/93


46/93





46

10.3 Data upload

Data submission is through the ReportNet Central Data Repository (CDR)

http://cdr.eea.europa.eu. Full submission instructions are detailed in Section 5 of the Floods

Directive reporting - A user manual [5]. An eionet login is required.

Data shall be uploaded into CDR no later than 2014-03-22.


47/93


48/93





48

This guidance does not detail how to set up a WMS using software, but to provide the standard

requirements for a Floods Directive conformant WMS.

11.4 WMS profile

The intention is that there will be several services per Member State. Each service will serve oneor more layers, which may be of different scale and/or of different geographical extent. The WMS

profile sets out a naming mechanism to ensure uniqueness across service names and layer

names, whilst maintaining human readability.

The profile is essentially two parts. The first is the service-level elements and the second part is

the elements which describe the layers.

The following describes the metadata which is required for the service to be compliant with

INSPIRE. The elements would be returned in XML format with a GetCapabilities request on the

service.

It could also be the service is described in a metadata document which is independent of the

service. This metadata structure is described in section 10 of this document. This stand-alonemetadata would be developed for the purposes of Discovery.

11.5 WMS service metadata

11.5.1 WMS service name

For WMS 1.3.0 fixed as 'WMS'

11.5.2 WMS service title

The title is a composite in order to be informative and unique

[ISO country code] [ISO 639 language code]* [Floods hazard maps]

[ISO country code] [ISO 639 language code]* [Floods risk maps]

*the language code is not required if the service is provided in the default language, English.

e.g. DK Flood hazard risk maps

11.5.3 WMS service URL

[ISO country code]_[ISO 639 language code]*_[Floods_hazard_maps]

[ISO country code]_[ISO 639 language code]*_[Floods_risk_maps]

The web service url is based upon the web service title it should be identical except all spaces in

the tile should be substituted with an underscore ('_').

e.g.if ArcGIS Server is providing the service:

http://www.someurl.dk//ArcGIS/services/DK_Flood_hazard_risk_maps/MapServer/WMSServer?

11.5.4 Additional WMS service metadata

INSPIRE Metadata elements(M-Mandatory C-Conditional)

Description or suggested text


49/93





49

Resource Abstract (M) Flood hazard and risk maps for the purpose of theFloods Directive. Flood hazard maps must show thegeographical area which could be flooded underdifferent probabilities (art. 6.3 of the Directive), whereasflood risk maps must show the potential adverseconsequences of these probabilities (article 6.5 of theDirective). The flood maps must be prepared for thefollowing probabilities: a) floods with low probability, orextreme event; b) flood with a medium probability (likelyreturn period 100 years) c) floods with a highprobability, where appropriate.

Resource Type (M) serviceResource Locator (C) Uniform Resource Locator(s) (URL) to the service as

described in section 9.4.3Coupled Resource (C) If the underlying datasets used in the service are also

publicly available, then this element provides for the input ofthe URL to the resource.

Spatial Data Service Type (M) WMS

Keyword (M) Keywords to describe the service. The INSPIRE MetadataRegulation [INS MD] mandates that in the case of spatialdata services at least one keyword from the "Classification ofSpatial data Services" (Part D.4 from INS MD] shall beprovided. 'Floods Directive,

Geographic Bounding Box (M) Bounding box for the full service probably country level.Note: each layer also has a bounding box.

Temporal Reference (M) Date of publication, date of last revision, or the date ofcreation. Date of last revision is preferred. The date shall beexpressed YYYY-MM-DD

Spatial Resolution (C) Not requiredConformity (M) conformant or not conformant or not evaluated. Citation

of the implementing rules adopted under Article 7(1) of

Directive 2007/2/EC or other specification to which aparticular resource conforms.

Conditions for Access and Use(M)

no conditions apply

Limitations on Public Access (M) NoneResponsible Organisation (M) Description of the organisation responsible for the

establishment, management, maintenance and distribution ofthe resource.

Metadata Point of Contact (M) The organisation responsible for the creation andmaintenance of the metadata.

Metadata Date (M) The date when the INSPIRE View Service metadata wascreated or updated. The update date is preferred. The dateshall be expressed YYYY-MM-DD.

Metadata Language (M) Codelist ISO 639-2

11.6 WMS Layer metadata

Floods Directive reporting is layer-level based, rather than service-level based. It is therefore

important to add as much metadata as possible to each of the layers. Even if most of your

metadata is the same for your layers and for your service, you should replicate that data in the

layer metadata.

The layer name and title are composites of certain information

Geographic extent in this context will be the country code or the UoM code


50/93


51/93





51

geographical coordinate system based on ETRS89 incontinental Europe. The value of the CRS parameterdepends on the coordinate reference systems cataloguebeing used, for example, using EPSG repository(http://www.epsg.org/), the relevant code would be:EPSG:4258

Styles List of the rendering styles available for the layer. A styleshall be composed of a title and a unique identifier. A legendshall be provided for each style.

LegendURL Location of the legend for each style. It is recommended touse "image/png" or "image/gif" mime types for a legend. Ifyou are using the latest version of MapServer or ESRIArcGIS server, this will be created for you automaticallyusing the inbuilt SLD capability.

11.7 GetMap request parameters

The GetMap operation returns a map. Upon receiving a GetMap request, a WMS shall either

satisfy the request or issue a service exception.

The GetMap request is georeferencing the returned image at least by the use of the layers,

Bounding box and Coordinate Reference

Request parameter Description

VERSION=1.3.0 Request versionREQUEST=GetMap Request name

LAYERS=name,name Comma-separated list of one or more map

layers names. Names are harmonizedINSPIRE layers names.

STYLES=name,name Comma-separated list of one rendering

style per layer requested. When the

STYLES parameter is left blank in the

GetMap request, the INSPIRE default

styling applies in the GetMap response to

all layers

CRS=namespace:identifier Coordinate reference system

Transparency=TRUE In order to have overlapping services

BBOX=minx,miny,maxx,maxx Bounding box corners (lower left, upper

right) in CRS units and in the axis order of

the CRS

WIDTH=output_width Width in pixels of map picture

HEIGHT=output_height Height in pixels of map picture

FORMAT=output_format Output format of map. At least supported :

Portable Network Graphics format (PNG;

MIME type"image/png") or the GIF

(Graphics Interchange Format) without

LZW compression (MIME type "image/gif")


52/93





52


53/93


54/93


55/93





55

Furthermore it is specified in this paper that the metadata related to the geographic data and the

derived geographic data will be distributed via a data catalogue service within the Commission,

the EEA and to the public without any restrictions.


56/93





56

14. Coordination and organisation

14.1 Helpdesk

The EEA will provide a content related helpdesk for questions related to these reporting rules and

procedures which will be informed related to the WISE data flow concerned. EEA will provide a

central helpdesk for all technical questions. The EEA may delegate these tasks to contracted

partners. The contact details of the WISE technical help desk are:

Phone: +32 2714 87 87 from Monday through Friday 9:00 to 17:00 CET

Email: [email protected]

Web page: http://nmc.eionet.europa.eu/


57/93


58/93





58


59/93





59

Appendix A


60/93





60

A.1 Description and specification of metadata elements for the

reporting of the geographic information.

For further information about metadata element description and definition see Appendix 11 of

Guidance Document No. 22: Updated Guidance on Implementing the Geographical InformationSystem (GIS) Elements of the EU Water policy and Technical Guidelines (V1.2) for INSPIRE

Metadata. In addition 5 metadata elements are introduced in the EC Regulation (1089/2010) for

interoperability of spatial data sets and services (Annex I).


61/93


Updated Guidance on Implementing the Geographical Information System (GIS) Elements of the EU Water policy

Appendix 13.3: Guidance on the reporting of

geographical data

Element Name Description Condition Value Domain Recommended input Exam

IDENTIFICATION

1.1 Resource

title

This is a

characteristic, and

often-unique, name

by which theresource is known.

Mandatory Free text

See section 8.1of this

guidance document

for a list of featuretypes

Derived from the type of

information being reported and

the place [Feature type] [Country]

1.2 Resource

abstract

This is a brief

narrative summary of

the content of the

resource

Mandatory Free text

1.3 Resource

type

This is the type of

resource described

by the metadata

Mandatory MD_ScopeCode

CodeList (see Annex B

of ISO 19115 for full

list)

DatasetSeries (if reporting

multiple files e.g by

Protected Area type)

1.4 Resource

locator

The resource locator

defines the link(s) to

the resource and/or

the link to additional

information about

the resource

Mandatory if a

URL is available

to obtain more

information on

the resource,

and/or access

related services

Character string

expressed by a URL

1.5 Unique

resource

identifier

A value uniquely

identifying the

resource

Mandatory MD_identifier (ISO

19115)

Character string +

character string

namespace

Identification of the authority

providing the resource +

identification of the dataset = name

of the dataset

[ISO 3166 country


62/93




geographical data

code]_[RiverBasinDistrict

(MS_CD)]_GWB_[date of

submission/upload date]

1.6 Coupled

resource

Identification of the

target spatial data

set(s) of the services

through their UniqueResources Identifiers

(URI)

Mandatory if

linkage to the

service is

available

MD_DataIdentification

(ISO 19115)

Character string code +

character string

namespace

Not applicable to dataset and

dataset series.

1.7 Resource

language

The language(s) used

within the resource

Mandatory if

the resource

includes textual

information

Codelist ISO 639-2

The list of codes for

the 23 official EU

languages is:

Bulgarian bul

Czech cze

Danish dan

Dutch dut

English eng

Estonian est

Finnish fin

French fre

German ger

Greek gre

Hungarian hun

Irish gle

Italian ita

Latvian lav

Lithuanian lit

Maltese mlt

Polish pol

Portuguese por

Romanian rum

Slovak slo

Slovenian slv

Spanish spa

Swedish swe

dan


63/93


64/93




geographical data

4.1 Geographic

bounding box

Extent of the

resource in the

geographic space

Spatial data set

or spatial data

set series:

Mandatory

Decimal degrees with

at least two decimals -

180.00

westBoundLongitude

180.00

-180.00

eastBoundLongitude

180.00

-90.00

southBoundLatitude

northBoundLatitude

southBoundLatitude

northBoundLatitude

90.00

-81.8

93.20

71.92

-29.8

Spatial data

service:

Mandatory forservices with an

explicit

geographic

extent

Decimal degrees with

at least two decimals

Not applicable to dataset and

dataset series.

TEMPORAL REFERENCE

5.1 Temporal

extent

Time period covered

by the resource as an

individual date, an

interval of dates or a

mix of both

At least one of

the metadata

elements

referred to

points 5.1 to

5.4

Date

ISO 8601

Provide the period covered by the

spatial data reported. The period

should be defined by the planning

period the groundwater bodies are

valid, e.g. RBMP period 2009-2015.

The input of this element isrequired

From

5.2 Date of

publication

Date of publication

or entry into force of

the resource

At least one of

the metadata

elements

referred to

Date

ISO 8601

Provide the date of the reporting

deadline of the period specified

with Metadata element 5.1.

2010


65/93




geographical data

points 5.1 to

5.4

The input of this element is

required

5.3 Date of last

revision

Date of last revision

of the resource

At least one of

the metadata

elements

referred to

points 5.1 to

5.4

Date

ISO 8601

Provide the date of the revision of

the dataset; in case of the first data

upload for the period specified with

Metadata element 5.1 the Date of

last revision = Date of publication.

[(1) example below].

The input of this element is

required.

2010

5.4 Date of

creation

Date of creation of

the resource

At least one of

the metadata

elements

referred to

points 5.1 to

5.4

Date

ISO 8601

Optional element

QUALITY & VALIDITY

6.1 Lineage Statement on

process history

and/or overall quality

of the spatial data set

Mandatory Free text The required input for the element

Lineage is described below

6.2 Spatial

resolution

Level of detail of the

dataset: it shall be

expressed as a set of

zero to many

resolution distances

or equivalent scales

Mandatory Equivalent scale

expressed as an

integer; resolution

distance expressed as

a numerical value.

A distance is a Number

expressing the

distance value and a

unit of measure of the

distance value.

Exam

scale

Exam

CONFORMITY

7.1 Citation of the Mandatory Free text + date Title:


66/93




geographical data

Specification implementing rules

adopted under

Article 7(1) of

Directive 2007/2/EC

or other specification

to which a particular

resource conforms

down

inter

admi

Date:

D

D

7.2 Degree Degree of conformity

of the resource to

the implementing

rules adopted under

Article 7(1) of

Directive 2007/2/EC

or other specification

Mandatory Part D.5 of the MD IR

- True if conformant

- False if not

conformant

true

CONSTRAINTS RELATED TO ACCESS AND USE

8.1 Conditions

applying toaccess and use

Conditions for access

and use of spatialdata sets and

services, and where

applicable,

corresponding fees

Mandatory Free text + URL if

applicable forinformation on any

fees

If data should be used only for a

certain purpose, this should benamed here

Exam

large

8.2 Limitations

on public

access

Limitations on public

access and the

reasons for them

Mandatory Free text (3) the limitations to public access

are described in section 11.2

The codelist for the input is as

follows:

WISE category 1

WISE category 2

WISE category 3

WISE

RESPONSIBLE ORGANISATIONS

9.1 Responsible

party

Description of the

organisation

responsible for the

Mandatory Free text + e-mail

address as a character

string

The following properties are

expected:

organisationName:

orga

G


67/93




geographical data

establishment,

management,

maintenance and

distribution of the

resource

ISO19115

CI_ResponsibleParty

CharacterString

contactInfo:

oaddress:

electronicMailAddress [1..*]:

CharacterString

conta

ad

9.2 Responsible

party role

Role of the

responsibleorganisation

Mandatory Part D.6 of the MD IR

CodeList (see B.5.5

of ISO 10115)

ISO19115

CI_RoleCode

001 (

METADATA

10.1 Metadata

point of contact

Description of the

organisation

responsible for the

creation and

maintenance of the

metadata

Mandatory Free text + e-mail

address as a character

string

ISO19115

CI_ResponsibleParty


expected:

organisationName:

CharacterString

contactInfo:

o address:electronicMailAddress [1..*]:

CharacterString

role: CI_RoleCode

organ

En

conta

o

role:

10.2 Metadata

date

Date the metadata

record was created

or updated

Mandatory ISO 8601 2008

10.3 Metadata

language

Language in which

the metadata are

expressed

Mandatory Codelist ISO 639-2

The list of codes for

the 23 official EU

languages is:

Bulgarian bulCzech cze

Danish dan

Dutch dut

English eng

Estonian est

eng


68/93




geographical data

Finnish fin

French fre

German ger

Greek gre

Hungarian hun

Irish gle

Italian itaLatvian lav

Lithuanian lit

Maltese mlt

Polish pol

Portuguese por

Romanian rum

Slovak slo

Slovenian slv

Spanish spa

Swedish swe

11.1 Metadata

character set

Full name of the

character codingstandard used for the

dataset

Optional http://www.isotc211.o

rg/2005/resources/Codelist/gmxCodelists.xm

l#

MD_SpatialRepresenta

tionTypeCode

utf8 utf8

11.2 Reference

system

Description of the

spatial and temporal

reference systems

used in the dataset

Optional MD_ReferenceSystem

(B.2.7)

referenceSystemIdentifier:

code: ETRS_89

codeSpace: INSPIRE RS registry

ETRS

11.3 Spatial

representation

type

Method used to

spatially represent

geographicinformation

Conditional: if

the resource is

a dataset ordataset series

http://www.isotc211.o

rg/2005/resources/Co

delist/gmxCodelists.xml#


tionTypeCode

Vector Vecto


69/93




geographical data

WISE METADATA (additional WISE Metadata, not INSPIRE)

11.1

Distribution

format

Provides a

description of the

distributor, format

and version of the

data to be

distributed and the

digital transfer

options

Mandatory Free text

ISO19115:

MD_Format (B.2.10.4)

MD_Distributor

(B.2.10.3)

MD_DigitalTransferOp

tions (B.2.10.2)

Provide at least the Format

information

Format: provide information on the

format:

Format name

Format version

Distributor: provide information on

the distributor


expected:

organisationName:

CharacterString

contactInfo:

oaddress:

electronicMailAddress [1..*]:

CharacterString

Digital transfer option: provide

information, if the data can be

provided online or offline

Online: provide the URL

Offline: provide the name

of the medium on which

the resource can bereceived

Form

Name

Versi

forma

softw

the s

ArcG

Distri

Orga

G

conta

ad

elect

Digita

Onlin

http:

dex.j

Offlin

11.2 Metadata

standard name

Name of the

metadata standard

(including profile

name) used

Mandatory Free text ISO 19115 Geographic information

Metadata; WISE Metadata profile

ISO 1

Meta


70/93




geographical data

11.3 Metadata

standard

version

Version (profile) of

the metadata

standard used

Mandatory Free text ISO 19115:2003 ISO 1

11.4 Metadata

file identifier

Unique identifier for

this metadata file

Optional Free text Globally unique identifier GUID

http://www.guidgenerator.com/

e88fb

11.5 Metadatacharacter set

Full name of thecharacter coding

standard used for the

dataset

Optional http://www.isotc211.org/2005/resources/Co

delist/gmxCodelists.xm

l#


tionTypeCode

utf8 utf8

11.6 Reference

system7

Description of the

spatial and temporal

reference systems

used in the dataset

Optional MD_ReferenceSystem

(B.2.7)

referenceSystemIdentifier:

code: ETRS_89

codeSpace: INSPIRE RS registry

ETRS

11.7 Spatial

representationtype7

Method used to

spatially representgeographic

information

Conditional: if

the resource isa dataset or

dataset series

http://www.isotc211.o

rg/2005/resources/Codelist/gmxCodelists.xm

l#


tionTypeCode

Vector Vecto

11.8 Credit8

Recognition of those

who contributed to

the resource(s)

Optional Free text Orga

11.9

Presentation

form

Mode in which the

resource is

represented

Optional http://www.isotc211.o

rg/2005/resources/Co

deList/gmxCodelists.x

ml#CI_PresentationFor

mCode

documentDigital docu

7Is part of the INPIRE metadata profile

8Proposed to be part of the INSPIRE metadata profile


71/93




geographical data

11.10 Purpose Summary of the

intentions with which

the resource(s) was

developed

Optional Free text

11.11 Specific

usage

Brief description of

the resource and/or

resource series usage

Optional Free text The following information is

required

description of the use of the

resource including the reporting

period or planning period the

dataset is valid/should be used

description of the relationship to

referenced datasets

11.12 Vertical

extent

Provides vertical

component of the

extent of the

referring object

Optional EX_VerticalExtent The vertical extent is provided as

attribute to the dataset; no input

required for this element

C.1.1 Element 6.1 WISE lineage: Further information

Under category QUALITY & VALIDITY the following information should be given by the data provider. If applicab

specified:

Description of the process history, covering the total life cycle of the dataset from initial collection to its current fo

Source information: describing the origin of the dataset;

Process steps: record the events of transformation in the lifetime of the dataset (including information on ge

Intervals to maintain the dataset.

If a previous reported dataset will be updated with the current dataset, the following information should be given

Providing the name of the data which will be updated with the current dataset;

Short description of the amendments done to the previous reported dataset (change of geometry and/or att


72/93




geographical data

Providing a reference to a source that gives information on life cycle rules of features.

Describe the data quality in line with ISO/DIS 19157. Provide statements on:

Completeness

Topological consistency

Positional accuracy

Temporal consistency

Thematic accuracy


73/93




geographical data


74/93


75/93

75

Appendix BB.1 Map layer specification for flood hazard and risk maps

Map layer specification

FD_FHRM: Floods Directive - Flood Hazard and Risk Map

Title* Floods Directive Flood Hazard Risk Maps EU level

Subject* Specification for online interactive map service for Water InformationSystem for Europe (WISE)

Date* 15/11/12

Publisher* European Commission DG Environment (DG ENV)

Contributor* Atkins Wolstrup/Maidens/Simonsen-Gjedde

Format* DOC

Language* En

Identifier* [Insert URL in circa Go4 library for EU Directive data flows]

Contact Balazs Hovarth, DG ENV

Reference N/A

Map code

Map name

FD_FHRM

*Dublin core metadata

Version history

Version Date Author Status and description1.0 11/03/13 Wolstrup-Atkins Draft

NB: Use track changes to only indicate the changes between versions


76/93

76

Contents

1. Overview 771.1 Abstract 772. Publishing 772.1 Target publish date 772.2 Mapviewer 773. Data and pre-processing 773.1 Content datasets 773.2 Data extraction 773.3 Data extraction and processing steps 803.4 Derived datasets 804. Visualisation 814.1 Layer 1: Population 814.2 Layer 2: Economic activities 814.3 Layer 3: IED installations 824.4 Layer 4: Other potential consequences 824.5 Background theme maps 834.6 Discomap services 834.7 Map spatial layers 835. Interaction 856. Specific map explanation text 88


77/93

77

1. Overview

1.1 AbstractThe intention is to disseminate certain aspects of the reported FD Flood Risk Hazard Maps data andinformation via WISE, and where necessary, appropriate and possible, provide links to data and informationfrom other sources such as national flood maps which can provide a higher resolution than WISE which willbe more appropriate for flood mapping purposes (larger scale than 1:250.000).

This chapter describes the proposed European level map. This will be derived from information reported bythe Member States and other European level datasets available, for example from other reporting streamsand INSPIRE.

2. Publishing

2.1 Target publish date2014

2.2 Mapviewer

The target viewer for this map service is:http://www.eea.europa.eu/themes/water/interactive/floods-directive-viewer

The service is also available in EyeOnEarth

3. Data and pre-processing

3.1 Content datasetsFloods Directive - Units of Management, APSFR information previously reported under the Floods Directive

Data reported under the Flood Hazard and Risk Map reporting obligation

Schema:http://icm.eionet.europa.eu/schemas/dir200760ec/resources/FRHMreview/FHRM_2p0.html

MS reported information: to be reported 2014

3.2 Data extractionThe reported information will be extracted from the XML schemas which are to be reported under the FHRMreporting. The FHRM reporting will be of three different probabilities (high, medium and low probability) with

affected population, economic activities and IED installations for each probability. Only medium (and lowprobability where groundwater and/or coastal floods are relevant) will be displayed. Options to click on/offlayers displaying land cover, population, the E-PRTR installations and the WFD protected areas will beavailable.


78/93

78


79/93

79


80/93

80

3.3 Data extraction and processing stepsData will be extracted from the schema for the medium probability (low probability for groundwater and

coastal floods) and aggregated at different levels for visualisation in the viewer i.e prepared for theclassification of UoM and country polygons. An additional layer will be added to show where detailed floodhazard and risk maps are available within MS.

Aggregation Flood risk population Flood risk economicactivities

Flood risk - IEDinstallations

Flood risk otherpotential consequences

InternationalUoM

Indication of where thereis data




CountryPercentage of populationwithin flood extent at riskon Country level

Aggregation of type ofeconomic activitiesimpacted for flood extentswithin the Country (piechart)

Percentage of IEDinstallation wherepollution risk exists forflood extents within theCountry

Aggregation of type ofother potentialconsequences for floodextents within the Country(pie chart)

UoMPercentage of populationwithin flood extent at riskon UoM level

Aggregation of type ofeconomic activitiesimpacted for flood extentswithin the UoM (pie chart)

Percentage of IEDinstallation wherepollution risk exists forflood extents within theUoM

Aggregation of type ofother potentialconsequences for floodextents within the UoM(pie chart)

APSFR*Number of inhabitantspotentially affected withincertain thresholds

Indication of type ofeconomic activityimpacted (pillar)

IED installation wherepollution risk exists forflood extents withincertain thresholds

Indication of otherpotential consequences(pillar or list**)

Backgroundtheme map

Population dataset(gridded)

Landcover datasetE-PRTR installations andWFD protected areas

NA

* This level will only be displayed where reported**Depends on data reported through the xml schema - if other consequences can be grouped or a list needs to be added

3.4 Derived datasets

Dataset name Intended use

IntUOM Internationalunits ofmanagement

UOM Units ofmanagement

APSFR Areas ofpotentialsignificant floodrisk


81/93

81

4. Visualisation

4.1 Layer 1: Population9

4.2 Layer 2: Economic activities9

9Please note that data used in all 4 layers are fictive and does not reflect any Member State reporting


82/93

82

4.3 Layer 3: IED installations9

4.4 Layer 4: Other potential consequences9


83/93

83

4.5 Background theme maps Population (available in 100x100m cells)

Land cover E-PRTR (http://prtr.ec.europa.eu/MapSearch.aspx)

WFD Protected areas (not yet developed)

4.6 Discomap servicesTo be developed

4.7 Map spatial layers

4.7.1 Zoom levels

Step Geographicscope

Scale Aggregation at Symbology Defaultvisibility

Notes

1 Pan-Europeanto National

Default to1:10,000,001

InternationalUoM

Classifiedpolygon

Visible Derived fromMS reported

2 Cross-borderto National

1:10,000,000to 1:5,000,001

Country Classifiedpolygon


3 National toRegional

1:5,000,000 to1,000,000

UoM Classifiedpolygon


4 Local 1:2,000,000 to250,000

UoM Classifiedpolygon


5 Local 1:2,000,000 to

250,000

APSFR (where

reported)

Classified

polygon/line/point

Visible Derived from

MS reported,generalized at1:250,000

6 Local 1:250,000 to2,000

Probabilities Classifiedpolygon

Visible(throughINSPIRENetworkservices/WMS servicewhereavailable)

Greater detailcan be shownthan at the1:250,000 forEuropeanlevel map

4.7.2 Symbology

Default symbology for features and layers as defined under the INSPIRE Directive will be used as the basisfor the presentation of the information in available maps.

For each layer referenced in the table above there should be a further table which details the values for eachclassification and the corresponding RBG colours to be used.

4.7.2.1 Population affected

Categorisation

affected

fdrdg10 6 gis guidance fhrm ver5 clean20130624

Documents