Reporting of spatial data for the Floods Directive (Part II)

Reporting of spatial data for the Floods Directive

(Part II) Guidance on reporting for flood hazard and risk maps of spatial

information

Tools and services for reporting under WISE

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

Version 5

June 2013 Notice

This report was produced for the European Commission for the specific purpose of creating a guidance document 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 European Commission’s express permission. In any event, Atkins accepts no liability for any costs, liabilities or losses arising as a result of the use of or reliance upon the contents of this report by any person other than the European Commission.

Atkins Limited

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 EEA comments

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 States and JRC

Wolstrup 24.06.13

Revision

Purpose Description Originated Checked Reviewed Authorised Date

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 8

1. Introduction 9

1.1 Overview 9

1.2 Flood hazard and risk map content 9

1.3 Reporting arrangements 10

1.4 Other reporting under the Floods Directive 12

2. Scope 14

2.1 FD reporting schemas 14

2.2 Related documents 14

2.3 Getting help 14

3. As-is analysis and gap analysis 15

3.1 EXCIMAP analysis 15

3.2 Interactive flood map examples 16

4. User requirements 23

5. Products at the European level 24

5.1 Overview 24

5.2 Maps produced for the WISE viewer 24

5.3 Flood hazard and risk maps European overview 25

6. Data content and structure for reported floods info rmation 27

6.1 Overview 27

6.2 Information to be reported 27

6.3 How the Commission will use the information 31

7. Maintenance 33

8. Data content and structure for decentralised Flood maps 34

8.1 Overview 34

8.2 Maps 35

8.3 Map context 36

8.4 Map 1: Flood hazard map and probabilities 37

8.5 Map 2: Flood risk map and population 38

8.6 Map 3: Flood risk map and economic activity 38

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

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

8.9 Map 5: Flood risk map and other vulnerability information (optional) 40

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




6

8.11 Map 7: Other useful information (optional) 41

8.12 Map 8: Coastal protection (optional) 41

9. Data production 43

9.1 Spatial resolution 43

9.2 Spatial representation 43

9.3 Coordinate reference system 43

9.4 Trans-boundary flood mapping for reported information 44

10. Data exchange format for submitted information 45

10.1 Formats 45

10.2 Naming of files 45

10.3 Data upload 46

11. Data exchange format for decentralised information 47

11.1 Overview 47

11.2 INSPIRE 47

11.3 WMS 47

11.4 WMS profile 48

11.5 WMS service metadata 48

11.6 WMS Layer metadata 49

11.7 GetMap request parameters 51

12. Metadata 53

12.1 WISE metadata profile 53

12.2 Metadata creation 53

13. Data access and constraints 54

13.1 Data usage 54

13.2 Data Distribution 54

14. Coordination and organisation 56

14.1 Helpdesk 56

15. Reporting documents and links 57

1. Overview 77

1.1 Abstract 77

2. Publishing 77

2.1 Target publish date 77

2.2 Mapviewer 77

3. Data and pre-processing 77

3.1 Content datasets 77

3.2 Data extraction 77

3.3 Data extraction and processing steps 80

3.4 Derived datasets 80

4. Visualisation 81




7

4.1 Layer 1: Population 81

4.2 Layer 2: Economic activities9 81

4.3 Layer 3: IED installations9 82

4.4 Layer 4: Other potential consequences9 82

4.5 Background theme maps 83

4.6 Discomap services 83

4.7 Map spatial layers 83

5. Interaction 85

5.1 Layer selection 85

5.2 Pop-up windows 86

6. Specific map explanation text 88

Appendix A: Description and specification of metada ta elements for the reporting of the geographic information

Appendix B: Map layer specification for flood hazard and risk m aps

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




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 State

NMA 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

1. Introduction Reporting sheet (reference #2) : This document comprises text which has been extracted from the reporting sheet. In order to highlight this previously agreed text in the document, it has been given a grey background colour.

1.1 Overview Article 6 of the Floods Directive (http://ec.europa.eu/environment/water/flood_risk) requires Member States to prepare flood hazard maps and flood risk maps. The distinction between flood hazard maps and flood risk maps is (Reference #1):

- the flood hazard maps should cover the geographical area which could be flooded according to different probabilities, along with some hazard related information associated to those areas;

- the flood risk maps shall show the potential adverse consequences associated with floods under these probabilities, relating to human health, economic activity, the environment and cultural heritage.

These maps must be prepared, at the river basin level and at the most appropriate scale, for the areas of potentially significant flood risk identified under Article 5 or according to article 13.1 (a), or for the areas for which MS decide to prepare flood maps according to article 13(1)(b) (art 6.1). Member States will determine the most appropriate scale of flood hazard maps and flood risk maps, and different scales can be chosen for instance depending on the location and type of map.

Additionally, information will be reported through WISE to be shown at European level (at scale 1:250.000).

1.1.1 How to use this document

According to the Directive, Member States shall produce Flood mapping according to some minimum recommendations. This guidance focuses on these recommendations in three ways:

1. Provide guidance on the visualisation of the information to be shown on the flood maps;

2. Provide a technical framework for the setting up of Member State flood maps on national servers;

3. Describe how the information and maps will be used.

1.1.2 Timeline

The flood hazard maps and flood risk maps must be completed by the 22nd December 2013 and made available to the commission by the 22nd March 2014. Member States may also use flood hazard maps and flood risk maps which were finalised before 22.12.2010, provided these maps “provide a level of information equivalent to the requirements of Article 6” (art 13.2).

1.2 Flood hazard and risk map content As written in the reporting sheet for flood hazard and risk maps (reference #2), Flood hazard maps must show the geographical area which could be flooded under different scenarios (art. 6.3), whereas flood risk maps must show the potential adverse consequences of these flood scenarios (article 6.5). The flood maps must be prepared for the following flooding scenarios:

(a) floods with low probability, or extreme event scenarios;




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 floods can 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 four chapters:

• 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 Risk Zones, 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

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 implementing dates:

- 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 are existence (i.e does not expect pre-compliance with INSPIRE data specifications). However




12

national maps should both have implemented the INSPIRE Directive rules for metadata on both data and services and the implementing Rules for INSPIRE Network Services (Discovery, View, Download, Transform)

• In order to achieve a system where from an EU-map that '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' then Member States should deliver these maps as INSPIRE Network Services. The reporting in the first cycle, or stage 1, should as far as reasonably possible be INSPIRE compliant. Member States shall provide the INSPIRE Network Services (Discovery, View) in conformity (i.e. operating capability) with this IR no later than 9 November 2011. Chapter 11 sets out the guidance for delivery of electronic maps as View Services for Floods reporting.

• If Member States are unable to deliver their flood and risk maps as View services in Stage 1, then they should be publicly available online as PDFs or through a WebBased GIS portal.

• The hyperlink to the relevant Member State resource for the flood hazard and risk maps will be reported to the Commission with the responsibility to the Member State for maintaining this hyperlink or informing the Commission of any changes – see appendix C for more detail on how to report these hyperlinks.

Stage 2 – second reporting cycle (in accordance wit h INSPIRE)

• Chapter 6 describes the reporting to the Commission of spatial and XML data (may be revised after first reporting cycle)

• Chapter 8 details with the content of the national level maps. This is primarily driven by the Annex III data specification on Natural Risk Zones, with reporting under other Directives and other INSPIRE thematic areas – eg. the data themes Area management / restriction / regulation zones and reporting units - providing supplementary information for the maps. For the second cycle, reporting formats/schemas shall aim at being fully INSPIRE compliant, which means that apart from the implementation of the INSPIRE Directive rules for metadata on both data and services and the implementing Rules for INSPIRE Network Services (Discovery, View, Download, Transform) – that the full data content for the INSPIRE data specifications IR should be implemented

• Chapter 11 presents the implementation of the INSPIRE View services specification for the floods domain

• Chapter 12 presents the implementation of the WISE metadata profile for the floods domain

1.4 Other reporting under the Floods Directive

1.4.1 Units of Management

The Floods Directive (Article 3.2) allows Member States to identify units of management different from the river basin districts used for the Water Framework Directive. Units of management (UoM) may be individual river basins and/or certain coastal areas, and may be entirely within national borders or may be part of an international unit of management or international river basin district. The Floods Directive requires Member States to communicate to the Commission information on the identification of units of management by 26 May 2010.

Background to the context of GIS in WISE is given in the GIS Guidance document (Section 2).

Reporting sheets was developed to report the geographic information and the thematic information related to Units of Management:




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 State’s territory.

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




14

2. Scope The scope of this paper is to provide guidance to Member States in the preparation and reporting of geographic data under the Floods Directive (FD). This guidance is based on recommendations from the Guidance Document No 22 “Updated Guidance on Implementing the Geographical Information System (GIS) Elements of the EU Water policy”1.

2.1 FD reporting schemas Fundamental to the reporting process are the schemas which have been developed from the reporting sheets. All the schemas are available online from EEA’s ReportNet. The reporting schemas are not dealt with in this document. This document deals with the spatial information required for the information reported in some of those schemas. The schemas are available from this web page http://icm.eionet.europa.eu/schemas/dir200760ec/resources/ along with supporting documentation.

2.2 Related documents This is ‘Document No.4’ providing support for the FD submission workflow. There are three other documents which provide additional support to the reporting process:

• Document No.1: Floods Directive reporting - A user manual http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

• Document No.2: Schema user guidance http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

• Document No.3: Reporting of spatial data for the Fl oods Directive (Part I) - Spatial reporting of the CAUoM and PFRA/ASPFR http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

2.3 Getting help All schemas, tools and supporting documents are available from this web page:

http://icm.eionet.europa.eu/schemas/dir200760ec/resources/

If you need assistance on issues not addressed in this User Guidance please contact:

[email protected]

1 Common Implementation Strategy for the Water Framework Directive (2000/60/EC). Guidance Document No 9 “ Updated Guidance on Implementing the Geographical Information System (GIS) Elements of the EU Water policy. 17. November 2008. http://circa.europa.eu/Public/irc/env/wfd/library?l=/framework_directive/guidance_documents/guidance-no22-_nov08pdf_1/_EN_1.0_&a=d




15

3. As-is analysis and gap analysis 3.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 and floodplain 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

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

3.2.2 Switzerland

http://www.apps.be.ch/geoportal/gdp/FrontController?project=gk5&language=de

http://www.apps.be.ch/geoportal/gdp/FrontController?project=gk5&language=de


• Water hazard maps




18

3.2.3 Luxembourg

http://eau.geoportal.lu/


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

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

• Other flood related information




19

3.2.4 United Kingdom (England/Wales)

http://www.environment-agency.gov.uk/homeandleisure/floods/default.aspx


• Flood hazard maps (significant, moderate, low) – click on the map for popup

• Other flood related information




20

3.2.5 Sweden

https://www.msb.se/sv/Kunskapsbank/Kartor/Oversvamningskartering/


• Flood hazard maps (100yrs)

3.2.6 Austria (in development)

Austrian Flood risk maps are currently under development and not yet available online. Presented below are examples of how Austria may present flood hazard map and flood risk maps. Additionally to the FHM reporting, separate amps are being developed for water depth and flow velocity (where appropriate)




21


• APSFR

• Flood hazard maps (30/100/200-300 years)

• For each flood scenario:




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

4. User requirements Section 2.1.2 of the GIS Guidance document [7] provides a detailed overview of the role of GIS in reporting in WISE.




24

5. Products at the European level 5.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 available much 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 information reported 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

5.3 Flood hazard and risk maps European overview There will be a single entry point to the European flood viewer within which the user will be able to see a number of different layers. Information will be aggregated with units at appropriate scales with the aim to indicate and lead the user to areas of interest on the map. As the user zooms into the map, the information is disaggregated until detailed (reported) information used for the aggregation is visible and then beyond that the user is taken to the maps which reside on the Member State national servers.

The development of the European level maps requires reported information from Member States for at least the medium probability where applicable and for coastal and groundwater floods the low probability together with data from other European level datasets (population, landcover) and other reporting streams (EPRTR, WFD protected areas).

The details of how the maps will be displayed on European level is outlined in the draft map specificiation in Appendix B

5.3.1 Visualisation symbology

The symbology for features as suggested under the INSPIRE Directive will be used where available as the basis for the presentation of the information in available maps. The symbology should in all cases render the domain best practice.

This symbology represents how the data under the control of WISE (ie to the 1:250,000 level) will be represented, but does not aim to dictate how the Member State flood risk maps should be rendered. However, where there is an absence of established precedent then this suggested European symbology could serve as a starting point.

It is recognised presenting both the European picture along with the Member State services in the same viewer, could be confusing to the user where different symbologies are used for the same thing, or the same symbology used with different meanings. It is for this reason, map legends and metadata are critical for the development of a transparent interface to the public.

5.3.2 Map zoom-through

One of the significant features of the Flood hazard and risk maps portal at European level is the functionality utilising INSPIRE network services for more detailed maps held at Member State level to be displayed once the user zooms in beyond the WISE portal operational limit of 1:250,000.

The first requirement is Member States have set-up and notified the Commission of the INSPIRE compliant network services services. Section 11 of this document details how these services should be set up.

Secondly, the Commission will configure the flood portal to call these services when the 1:250,000 limit is reached.

It may be the Commission will index the spatial extents of these services in order to indicate to the user at the European level exactly where they are, as coverage will not be total, particularly in the first phases.

When the user does cross the 1:250,000 threshold and the Member State service will be displayed, there will be a clear, prominent and persistent notification to the user they are now seeing information which is supplied as a service. As Member States will also provide the same information within their own portals with specific context, the url to the national portal will also be clearly displayed.




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

6. Data content and structure for reported floods information

6.1 Overview The purpose of this section is to describe the information which will be reported by Member States to the Commission in the following timetable:

Floods Directive timeline

Subject Main Article Other Articles

Responsibility

To Report due date

Frequency/ Review

Flood Hazard and Flood Risk Maps

6 13.2 MS COM 22/03/14 22/12/19, every 6 years thereafter

The reporting comprises spatial information and textual/tabular information reported via an XML schema. This section is focused on the spatial information, but covers the XML reporting because of the close relationship between the two. Full support for the reporting of the XML schema is provided in other guidance documents (Guidance document 1 and 2 available on the resource page).

6.2 Information to be reported

6.2.1 Spatial information

The Flood hazard and risk map reporting sheet, Section C, describes the geographic information requirements for this reporting. Further guidance on the maps which will be prepared at the national level is given in Chapter 8. This section deals with the spatial information required for summary maps to be produced at European level. This visualisation of these maps is described in Chapter 5 and in appendix B.

The information from the schema will be displayed at UoM and APSFR level where applicable. If Member States report at APSFR level the spatial information for the APSFR is required if this has not been reported under the preliminary floods risk assessment. Member States can also choose to report the spatial information for the extents of floods under the low, medium and high probability where applicable. This data will however be aggregated at either the APSFR or UoM level for the purpose of visualization at the European level map of the FHRM.

In order to provide a long term data model, the spatial information expected corresponds to the major spatial objects defined by INSPIRE Natural Risk Zones Data specifications - e.g. Observed Event, Hazard Area, Risk Zone and Exposed Element - both vector and coverage forms.

6.2.1.1 Shapefile template for the FHRM

The template for the spatial information submitted will be a simple data model with only one attribute which will be a unique code assigned to the hazard area.

Information in the schema will allow for more detailed attribute information, such as the return period the probability represents.




28

Attribute name Obligation Type Description

EU_CD_HP (covering EU_CD_HLP, EU_CD_HMP and EU_CD_HHP )

Mandatory string (42) Unique EU code of the feature within the low probability hazard area. Codes MUST have a 1-to-1 relationship with further attribute data described in the related XML file. Please notice that multi polygons are not allowed to report and should be split into separate polygons

6.2.1.2 ID management

Two spatial objects of spatial object types cannot have the same identifier. The identifier has to be unique within all the spatial objects published in WISE. The identifier cannot be used again if an object is modified.

The same spatial object shall be reported always using the same identifier (e.g. monitoring stations reported to SoE, WFD, Nitrates Directive, etc).

ID Structure

The following structure for a unique identifier should be used for designated probabilities. The flood probability identification shall be unique within both the MS as well as on EU level and be in accordance with the INSPIRE rules for Identifier Management defined in section 14 of D2.5 Generic Conceptual Model.

At European level the following structure should be used

MS = a 2 character Member State identifier, in accordance with ISO 3166-1-Alpha-2 country codes1; and #1#2…#22 = an up to 22 character feature identifier that is unique within the Member State.

(symbol # = wildcard character (a wildcard character can be used to substitute for any other character or characters in a string)).

At MS level the ISO country code can be left out of the unique identifier.

According to these definitions the code for a coastal water body in Germany could look as follows:

Name Data type Min/max length Example

MS_code character 1-22 CW7596

EU_code character 3-24 DECW7596

Special advice given is that:

• The local identifier shall only use the following set of characters: {“A”…”Z”, “a”…”z”, “0”…”9”, “_”, “.”, “-“}, i.e. only letters from the Latin alphabet, digits, underscore, point and dash are allowed;

• The identifier should contain no spaces;

• Alphabetical characters should always be in UPPER CASE;

• Special characters must be avoided, such as ‘$’, ‘!’, ‘&’, ‘ë’, ‘á’, etc;

• Digits should be used where practical to help avoid the above problems.

1 http://www.iso.org/iso/country_codes.htm




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 text fields 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

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 (<5000 characters) on how coordination at the level of the River Basin District / Unit of Management was carried out in preparing the flood maps (art 6.1), including explaining how the prior exchange of information has been assured for RBD/UoM shared between different Member States (art 6.2).

5. Summary text (< 10.000 characters) with explanation (to be made available for the public through WISE ) on how to understand the flood maps contents, scale, purpose/use, accuracy, legends, date of publication, responsible authorities, links to further information (art 10.1). The information in this section will also be provided as part of the service metadata for the distributed services.

6. In addition to the information provided above, Member States making use of article 13.2 shall provide summary text (< 5.000 characters) with notification of use of article 13.2, which may include summary of additional relevant information to justify that the maps provided in accordance with article 13.2 provide a level of information equivalent to the requirements of article 6.

6.2.2.3 Data

The following data is also included in the XML schema for reporting.

The following data is MANDATORY:

1. Type of flood or floods, geo-referenced to the specific area identified in article 5 or article 13(1)(a) or (b) and optional for mechanisms and characteristics [Note: the reporting tool/format (e.g. XML schema for tabular/textual information) will provide an enumeration list of flood types, mechanisms and characteristics from which the relevant ones can be selected]

2. Probabilities assigned to each flood scenario: high; medium and low. [Note: the reporting tool (e.g. XML schema) will provide an enumeration list on how to express scenarios from which the relevant ones can be select, including the option of low probability or extreme event]

There should be a 1:1 relationship with the spatial information detailed in section 6.2.

The data listed below is tabular and is provided with reference to the flood scenario code delivered with the mandatory spatial information. The schema is structured to provide the linkages between the UoM/APSFR and the Flood probabilities (scenarios).

3. Geo-referenced information on potential adverse consequences associated with the particular flood scenarios expressed as in terms of indicative number of inhabitants potentially affected, [Note: the reporting tool (e.g. XML schema) will provide an enumeration types of potential adverse consequences from which the relevant options can be selected]

4. Geo-referenced information on potential adverse consequences to the different types of economic activities in the areas potentially affected in association with the particular flood




31

scenarios [Note: the reporting tool (e.g. XML schema) will provide an enumeration types of potential adverse consequences from which the relevant ones can be selected]

5. Geo-referenced information on potential adverse consequences in relation to IPPC installations and affected protected areas in association with the particular flood scenarios, [Note: the reporting tool (e.g. XML schema) will provide an enumeration types of potential adverse consequences from which the relevant ones can be selected]

The follow data is OPTIONAL:

6. (Optional) Geo-referenced information on potential adverse consequences to the other information the Member States considers useful in association with the particular flood scenarios, [Note: the reporting tool (e.g. XML schema) will provide an enumeration types of potential adverse consequences from which the relevant ones can be selected]

6.3 How the Commission will use the information

Section B of the reporting sheet (reference #2), states the reporting requirements under the reporting of Flood hazard and risk maps will allow the Commission to:

1 check the compliance of Member States Flood hazard maps, and flood risk maps with the requirements of the Directive, such as:

1.1 how relevant information has been considered and the methodologies used to prepare maps, and that flood hazard maps and flood risk maps contain the relevant scenarios (art 6.3) and data (art. 6.4 and 6.5);

1.2 how the potential adverse consequences have been identified and presented in flood risk maps (art 6.5);

1.3 the justifications for applying articles 6.6 (coastal areas) and 6.7 (groundwater floods) if applied

1.4 that flood hazard maps and flood risk maps are transparently made available to the public(art. 10.1);

1.5 that maps were prepared at the level of the unit of management (art 6.1);

1.6 that the preparation of the maps was subject to prior information exchange between Member States in the case of international RBDs or UoMs (art 6.2);

2 compare methodologies and the use of information across Member States, RBDs and UoMs and within UoM/RBD, particularly in terms of international RBDs and UoMs;

3 assess the compliance of the use of article 13.2 in comparison with the requirements of article 6.

4 prepare digital maps to be displayed in WISE at a European level of selected aspects of flood maps, in formats to be agreed.

5 identify if, and if so how, climate change has been taken into account when scenarios are identified, considering that it is not a strict requirement of the Directive at the mapping stage.

Some specific information will also be provided to the public through WISE.

The Commission will use the following criteria when checking the compliance of these aspects:

1 completeness of the coverage of the maps as regards Areas of potential significant flood risk and areas identified under article 13(1)(b), and the coverage as regards flood scenarios and potential adverse consequences, and other relevant factors set out in article 6,

2 transparency of procedures, methodologies, reports and information provided to the public and to neighbouring MS in accordance with relevant articles,




32

3 consideration of the relevant different types of floods, as relevant based on the preliminary flood risk assessment,




33

7. Maintenance In accordance with the WISE reporting arrangements1 Member States can update their data submitted to WISE at any time. Member States should ensure that the latest, correct information is available in WISE since that will be used for compliance checking and publication.

The quality, accuracy and validation of the information and data in WISE will be the responsibility of the Member States. Quality assurance and control processes will be carried out by the WISE partners. The Commission, the EEA or its contracted partners may contact the Member State in case there is an indication that any of the data may be erroneous or misleading. This could lead to a resubmission by the Member State.

1 Guidance on practical arrangement for electronic reporting to the Water Information System for Europe (WISE); “WISE REPORTING ARRANGEMENTS”; Final Document (01/03/2007)




34

8. Data content and structure for decentralised Flood maps

8.1 Overview The purpose of this section is to provide an overview of the Flood hazard and risk maps Member States will prepare according to the Reporting Sheet. This section does not aim to describe how Member States should produce the maps, but the methodologies will be reported through the XML schema (See section 7).

This section extends the requirements of the map with some visualisation suggestions. This is not a prescriptive list, but designed to stimulate the development of comprehensive maps.

In this section, minimum guidelines are provided for the production of the flood hazard and risk maps. The content of these maps is independent of the method of delivery, but they need to be publicly available.

8.1.1 Format

As described in the reporting sheet, section C: For the first cycle, Member States can report either in an INSPIRE compatible format (decentralised system), or if not fully implemented in that Member State, hyperlinks to maps available in digital format, with geo-referenced hyperlinks which enables access from a certain area identified within WISE. For the second cycle, reporting formats/schemas shall aim at being fully INSPIRE compliant (see also section 1.3.1 and 11).

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.

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. However for the first reporting cycle the Member States FHRM can also be made available through PDF, a Member State national webGIS or as national level web mapping services. Web mapping services mean the maps can be integrated into other web applications which the provider has no control over. In the context of the Floods Directive mapping, this would be a European level map hosted by the Commission which would allow the user to zoom from the European overview map to more detailed information within the same application.

In order to achieve a system where from an EU-map that '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' then Member States should deliver these maps as web services. The reporting in the first cycle, or stage 1, should as far as reasonably possible be INSPIRE compliant. The relevant INSPIRE regulation is for Network Services. Member States shall provide the Network Services in conformity with this IR no later than 9 November 2011. Chapter 11 sets out the guidance for delivery of electronic maps as INSPIRE Network Services.

If MS only present their maps as PDFs or within their own web-gis portals, then this zoom through will not be possible and only a hyperlink, supplied by the MS and indicated in the viewer for the user to switch to the MS system.




35

8.1.2 Organisation of Maps

This section lists the maps according to the Reporting Sheet, in order to provide discrete guidance for each map. However, it is not necessary the maps are published in such a manner. It is the Member States discretion on how to combine different maps into a single output.

8.1.3 INSPIRE

Under each map, an 'INSPIRE linkage' section indicates where potential data sources described under INSPIRE could be used in the map development.

It is important to establish the linkages in this section to the development of the existing Annex I specifications and to Annex II and III.

Therefore in the production of the Flood hazard and risk maps the long term view is being taken to propose the implementation of INSPIRE at a n early stage in order to streamline the transition of Floods hazard and risk maps to INSPIR E compliance.

Selected elements of INSPIRE Roadmap (reproduced in part from reference #5, see also http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44 )

The INSPIRE Directive is implemented in various sta ges, with a full implementation by 2020.

Topic Specification starts

Adoption of IR Implementation deadline for the Member States

Discovery and View services

2008 19-Oct-2009 09-Nov-2011

Download and Transformation services

2009 12-Jun-2012 28-Dec-2012

Annex I 2008 23-Nov-2010 23-Nov-20131 23-Nov-20172

Annex II and III 2010 2013 Sept-20151 Sept-20202

Table Notes:

1. For newly collected and extensively restructured spatial data sets

2. For other (not newly collected or extensively re structured) spatial data sets

8.2 Maps The reporting sheet ([2], section C) lists the following mandatory geographical information:

1. Flood hazard maps showing the extent of flooding associated with the flooding scenarios (high , medium , low probability floods ) at the appropriate scale, including water depth or water level and where appropriate the flow velocity or relevant water flow , for the areas identified under article 5 or article 13(1)(a) or (b) (art 6.3 and 6.4);

2. Flood risk maps showing the potential adverse consequences expressed in terms of the indicative number of inhabitants potentially affected under the flood scenarios (art 6.5(a));

3. Flood risk maps showing the potential adverse consequences expressed in terms of the type of economic activity of the area potentially affected under the flood scenario (art 6.5(b));




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 mandato ry).

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

This information is already defined within the repo rting sheet as a single text field (reporting data 6.2.2.2 item 5) and will made avail able through the view service metadata (see section 11).

8.3.1 Methodologies to be reported

In the preparation of these maps, the Commission expects to receive the information below which summarises the process adopted by the Member State in the production of these maps. Further details on the reporting schema can be found in section 6.2.2.2.

8.4 Map 1: Flood hazard map and probabilities

8.4.1 Rationale

Flood hazard maps must show the geographical area which could be flooded under different scenarios (art. 6.3), whereas flood risk maps must show the potential adverse consequences of these flood scenarios (article 6.5). The flood maps must be prepared for the following flooding scenarios:

(a) floods with low probability, or extreme event scenarios;

(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.

The flood depth maps show the water depth in the flooded area. They are based on the flood extent maps – after the determination of the water extent, in this boundaries is calculated the water depth. They are produced for the same return periods as the flood extent maps. The depth is given in centimetres or meters, as it is appropriate.

8.4.2 Visualisation suggestions

This map service will available this information either as multiple layers.

1. Extent of flooding will be represented with polygons. Usually in the practice flood extent is displayed with blue colour and the scale depends on the area.

2. Water depth or levels will be expressed in meters using the ranges and colours following a single flood event (e.g. 100-year)

8.4.3 INSPIRE linkage

• Natural risk zones – Observed Event, Hazard Area, Risk Zone and Exposed Element - both vector and coverage forms




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));


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


• 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

• 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 control which 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

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 location of 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 waters

3. 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


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 against flooding, 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



• Hydrography




43

9. Data production 9.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 kept as 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

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 countries where 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 the border, i.e. that at the same level of detail - no surface geometry meets a point or line geometry.




45

10. Data exchange format for submitted information

10.1 Formats • Polygon features are reported both as shapefiles and in form of XML documents. XML

documents again have their schema and the simple guidelines for shapefiles are:

� A valid shapefile is a set of 4 files: geometry (*.shp), index (*.shx), attributes (*.dbf) and projection (*.prj)

� All 4 files MUST have the same (meaningful) file name (case sensitive), plus the above-mentioned file name suffixes (the latter ones either in lower or in UPPER case, but not in MiXeD case)

� There must be 1 feature attribute in the dbf file for the unique identifier (see respective shapefile templates)

� Unique feature identifiers in the dbf file MUST have a 1-to-1 relationship with further attribute data described in the related XML file

� In order to facilitate further data processing, shapefiles shall be uncompressed inside Reportnet envelopes. If your shapefile is in ZIP format, make use of Reportnet's "Upload zipfile" function, which will uncompress your ZIP archive, before adding the files into the envelope

• When in doubt, or in case of questions please contact [email protected] or [email protected]

10.1.1 GML

GML is primarily for use in web services (INSPIRE download service). Member States may use this delivery mechanism as an alternative to submitting shape files through ReportNet. The GML application schemas can be downloaded from the INSPIRE portal http://inspire.ec.europa.eu/draft-schemas/

10.2 Naming of files When uploading files it is required that the file naming has the following structure:

[Country ID]_[UOM]_ [probability]_[Date]

• Country ID (ISO code1)

• UOM code

• Date: this should be the date of data submission (Upload date) – YYYYMMDD

Example:

AT_AT1000_probability_20121231




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

11. Data exchange format for decentralised information

11.1 Overview The previous sections have dealt with the content and appearance of the flood hazard and risk maps. This section focuses on how to make these maps available in a standard way.

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. The web-links should be set up 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.

It would be expected the Member States provide their own portal for serving the flood information in the context they wish along with any other relevant information. This will satisfy the public access requirement of the Directive.

In order for the maps to be shown through WISE, this section deals with the technical format which the flood risk maps should be made available through an url.

This is also integral to the delivery of flood maps in the second cycle and for those Member States who can do so in the first cycle.

11.2 INSPIRE This section is about the implementation of INSPIRE view services. It is therefore drawn from the technical guidance (reference #3) adding only context specific to the delivery of Flood maps, which is mainly in the service metadata.

Key points from the introduction of the technical specification:

INSPIRE Network Services allow users and computer programs to view spatial datasets.

Following the INSPIRE Technical Guidance will ensure that INSPIRE Network Services are implemented in a consistent and compatible way across Europe. It is based on European and international standards, current practices in related stakeholder communities and relevant European initiatives such as e-Government, and the EU Interoperability Framework.

INSPIRE specifies requirements and recommendations based on the European de jure standard Web Map Service (WMS) 1.3.0. It defines an INSPIRE Profile to implement the following operations:

• Get View Services Metadata: Get metadata about a specific view service;

• Get Map: Returns a map for a specified area;

• Link View Service: Allows the linking of view services together.

11.3 WMS This section describes how to deliver images of flood hazard and risk maps over the Internet as an Open Geospatial Consortium (OGC) Web Mapping Service (WMS). In the context of INSPIRE, these are known as View services.




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 one or 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-alone metadata 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

Resource Abstract (M) Flood hazard and risk maps for the purpose of the

Floods Directive. Flood hazard maps must show the geographical area which could be flooded under different probabilities (art. 6.3 of the Directive) , whereas flood risk maps must show the potential adverse consequences of these probabilities (article 6.5 of the Directive). The flood maps must be prepared for the following probabilities: a) floods with low probabi lity, or extreme event; b) flood with a medium probability ( likely return period ≥ 100 years) c) floods with a high probability, where appropriate.

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

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

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

Spatial Data Service Type (M) WMS Keyword (M) Keywords to describe the service. The INSPIRE Metadata

Regulation [INS MD] mandates that in the case of spatial data services at least one keyword from the "Classification of Spatial data Services" (Part D.4 from INS MD] shall be provided. '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 of creation. Date of last revision is preferred. The date shall be expressed YYYY-MM-DD

Spatial Resolution (C) Not required Conformity (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 a particular resource conforms.

Conditions for Access and Use (M)

no conditions apply

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

establishment, management, maintenance and distribution of the resource.

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

Metadata Date (M) The date when the INSPIRE View Service metadata was created or updated. The update date is preferred. The date shall 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

Language – as above

Theme – will be chosen from the ExposedElementCategoryValue, annex C of the INSPIRE Natural Risk Zones Data specification [11] with the below additional themes to choose (Editorial note: This enumeration will be extended over time)

probability

depthheight

velocity

velocitydepth

11.6.1 Layer title

This is the human readable format of the layer title.

The following options are available. It is possible to extend this naming using the following:

[to be further developed]

[Geographic extent] [Language] [Scale] [Theme]

11.6.2 Layer name

The layer name is based upon the layer title – it should be identical except all spaces in the tile should be substituted with an underscore ('_').

[to be further developed]

[Geographic extent]_ [Language]_[Scale]_[Theme]

11.6.3 Additional WMS layer metadata

INSPIRE Metadata elements (M-Mandatory C-Conditional)

Description or suggested text

Resource Abstract (M) Flood hazard and risk maps for the purpose of the

Floods Directive. Flood hazard maps must show the geographical area which could be flooded under different probabilities (art. 6.3 of the Directive) , whereas flood risk maps must show the potential adverse consequences of these probabilities (article 6.5 of the Directive). The flood maps must be prepared for the following probabilities: a) floods with low probabi lity, or extreme event; b) flood with a medium probability ( likely return period ≥ 100 years) c) floods with a high probability, where appropriate.

Keyword (M) Keywords to describe the service. The INSPIRE Metadata Regulation [INS MD] mandates that in the case of spatial data services at least one keyword from the "Classification of Spatial data Services" (Part D.4 from INS MD] shall be provided. 'Floods Directive,

Geographic Bounding Box (M) The minimum bounding rectangle of the area covered by the Layer in all supported CRS shall be given.

Unique resource identifier Coordinate Reference System List of Coordinate Reference Systems in which the layer is

available: coordinate reference system as defined in Annex I of the INSPIRE Directive. It is mandatory to use




51

geographical coordinate system based on ETRS89 in continental Europe. The value of the CRS parameter depends on the coordinate reference systems catalogue being 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 style shall be composed of a title and a unique identifier. A legend shall be provided for each style.

LegendURL Location of the legend for each style. It is recommended to use "image/png" or "image/gif" mime types for a legend. If you are using the latest version of MapServer or ESRI ArcGIS server, this will be created for you automatically using 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 version REQUEST=GetMap Request name

LAYERS=name,name Comma-separated list of one or more map layers names. Names are harmonized INSPIRE 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




53

12. Metadata 12.1 WISE metadata profile

Metadata is information and documentation which describes the content, quality, origin etc. and makes data understandable and shareable between users and receivers over time.

The metadata for both data sets and services should follow the Commission Regulation (EC) No 1205/2008 of 3 December 2008.

The information which should be provided for all spatial data sets reported in relation to the Floods Directive and additional updates to previous spatial data sets are to be found in the table in Appendix A .

Further information on both mandatory and optional metadata elements of the WISE profile – which is an extension of the INSPIRE regulation - can be found in both Chapter 5.5 and Appendix 11 in the GIS Guidance1. Metadata should be reported using the WISE profile.

Appendix 11 of the GIS Guidance provides guidance on the implementation of the profile in XML.

Geographic data submitted to WISE will not be accepted without the proper metadata as specified in the WISE metadata profile.

12.2 Metadata creation The authoring and editing of metadata in WISE can be done in a number of ways including the use of a metadata editor, capable of outputting metadata according to the recognised WISE metadata XML schema. This can be carried out directly (i.e. if the tool can be configured to export according to this schema), or indirectly (i.e. using XSL transformations to map from the native XML schema of the specific tool to the WISE XML schema). A dedicated WISE metadata web-based entry page, with basic client-side validation does not exist at present time.

Until a metadata editor is released by WISE, the suggested workaround is to make use of the XML example which can be found at this url:

http://icm.eionet.europa.eu/schemas/dir200060ec/resources/WISE%20MetadataProfile%20guidance%20example%20v1.xml

This example was produced using the INSPIRE metadata editor and then the WISE specific elements added manually afterwards. The WISE elements are marked in the document with comments. The XML uses the example elements from the metadata table in Appendix A.1

No XML Schema for developing WISE metadata will be released.




54

13. Data access and constraints The MS have in the Guidance on practical arrangements for electronic reporting to WISE1 agreed on the access rights for data submitted to WISE.

The access rights to data submitted to WISE are already agreed with Member States and appear in the WISE reporting arrangements2. Annex 1 of the Paper specifies the “WISE spatial data policy” – data use and data distribution.

13.1 Data usage The Commission and the EEA are authorised to use the geographic data in the context of environmental policy definition, implementation, assessment and analysis

• as geographic reference, i.e. creating a geographical context for other data;

• for the production of maps, publications, posters, presentations, web sites and any other electronic publication on the Internet. Electronic publication will be in the form of image maps;

• for spatial and statistical analysis;

• for deriving new geographic datasets by applying data manipulation procedures, e.g. combining different geographic datasets, generalisation procedures including smoothing and dropping of spatial features and adding new attribute information3.

• for inclusion of the geographic data in other applications provided that it will not be possible to extract the original geographic data.

13.2 Data Distribution The Commission and the EEA are authorised to distribute geographic data, if

• the source is acknowledged and,

• the data is not used for commercial purpose – unless approved by the provider - and,

• the data provider has not explicitly restricted their dissemination beyond what specified at point 2

Category 1: Internal use within Commission and EEA, publication as maps on paper or in electronic format as image maps.

Category 2: Distribution of derived data and products under predefined conditions with the aim of decreasing the spatial accuracy or resolution of the geographic data.

Category 3: Distribution of original data electronically as feature service or on physical support.

1 Guidance on practical arrangement for electronic reporting to the Water Information System for Europe (WISE). WISE reporting arrangements. Final document (01.03.2007). http://eea.eionet.europa.eu/Public/irc/eionet-circle/eionet-telematics/library?l=/technical_developments/various_items/reporting_arrangements/_EN_1.0_&a=d 2 Guidance on practical arrangement for electronic reporting to the Water Information System for Europe (WISE); “WISE REPORTING ARRANGEMENTS ”; Final Document (01/03/2007) 3 Examples of derived geographic data are the Main Rivers map




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

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

15. Reporting documents and links

[1] Atlas of Flood Maps, EXCIMAP, 2007 http://ec.europa.eu/environment/water/flood_risk/flood_atlas/

[2] Reporting sheets for the Flood hazard maps and flood risk maps, European Commission 2010

[3] Technical guidance for the implementation for INSPIRE View services http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf

[4] Draft List of flood types and list of consequences, v5 https://circabc.europa.eu/faces/jsp/extension/wai/navigation/container.jsp?FormPrincipal:_idcl=FormPrincipal:_id3&FormPrincipal_SUBMIT=1&id=e42d1331-4f07-4c45-8a6f-af19279c4404&javax.faces.ViewState=rO0ABXVyABNbTGphdmEubGFuZy5PYmplY3Q7kM5YnxBzKWwCAAB4cAAAAAN0AAIxM3B0ACsvanNwL2V4dGVuc2lvbi93YWkvbmF2aWdhdGlvbi9jb250YWluZXIuanNw

[5] Relationships between EU water policies and INSPIRE activities and implementation: Background information note CIS Strategic coordination group, NERI (Michael Stjernholm), 2009,

[6] Common Implementation Strategy for the Water Framework Directive (2000/60/EC). Guidance Document No 22 “Updated Guidance on Implementing the Geographical Information System (GIS) Elements of the EU Water policy. 17. November 2008.

https://circabc.europa.eu/sd/d/d5a9cbcd-e693-483f-a76d-5b64b8f80311/WISE%20GIS%20guidance-No22-%202nd%20edition%20Nov__08.pdf

[7] Guidance on practical arrangement for electronic reporting to the Water Information System for Europe (WISE). WISE reporting arrangements. Final document (01.03.2007).

http://eea.eionet.europa.eu/Public/irc/eionet-circle/eionet-telematics/library?l=/technical_developments/various_items/reporting_arrangements/_EN_1.0_&a=d

[8] INSPIRE. http://inspire.jrc.ec.europa.eu/

[9] INSPIRE Data Specification on Hydrography – Guidelines. http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_HY_v3.0.pdf

[10] "INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119 (Version 1.2)

[11] INSPIRE Natural Risk Zones: http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_NZ_v3.0rc3.pdf

[12] INSPIRE Area management / restriction / regulation zones and reporting units: http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_AM_v3.0rc3.pdf




58




59

Appendix A




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 Information System (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).


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


61

Element Name Description Condition Value Domain Recommended input Example

IDENTIFICATION

1.1 Resource

title

This is a

characteristic, and

often-unique, name

by which the

resource is known.

Mandatory Free text

See section 8.1of this

guidance document

for a list of feature

types

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)

Dataset

Series (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

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 Unique

Resources 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

CLASSIFICATION OF SPATIAL DATASETS & SERIES

2.1 Topic

category

High-level

classification scheme

Mandatory MD_TopicCategoryCod

e (ISO 19115)

Enumeration (see

B.5.2.27 of ISO 19115)

012 (inlandWaters) 012 (inlandWaters)

2.2 Spatial data

service type

This is a classification

to assist in the search

of available spatial

data services

Mandatory Part D.3 of the MD IR Not applicable to dataset and

dataset series.

KEYWORDS

3.1 Keyword

value

A commonly used

word, formalized

word or phrase used

to describe the

subject

Spatial data set

or spatial data

set series: at

least one

keyword from

GEMET

Free text

WISE recommendations:

http://converters.eionet.europa.eu

/xmlfile/WISE_metadata_keywords

_1.xml

GEMET:

http://www.eionet.europa.eu/gem

et

Spatial data

service: at least

one keyword

from Part D.4 of

the MD IR

Part D.4 of the MD IR Not applicable to dataset and

dataset series.

3.2 Originating

controlled

vocabulary

The citation of the

originating controlled

vocabulary shall

include at least its

title and a reference

date (publication, last

revision or creation)

Mandatory if

the keyword

originates from

a Controlled

vocabulary

Free text + date GEMET - Concepts, version 2.1, 2008-06-13 http://www.eionet.europa.eu/ge

met

GEMET - Concepts, version 2.1, 2008 -06-13 http://www.eionet.europa.eu/gemet

GEOGRAPHIC LOCATION




64

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.80

93.20

71.92

-29.86

Spatial data

service:

Mandatory for

services 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 is

required

From 2006-03-22 to 2010-03-22

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-03-22




65

points 5.1 to

5.4


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].


required.

2010-03-22

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.

Example scale: 250000 (e.g. 1:250,000

scale map)

Example distance: 3 metres

CONFORMITY

7.1 Citation of the Mandatory Free text + date Title: “INSPIRE Implementing rules laying




66

Specification implementing rules

adopted under

Article 7(1) of

Directive 2007/2/EC

or other specification

to which a particular

resource conforms

down technical arrangements for the

interoperability and harmonisation of

administrative boundaries”

Date:

Date type: publication

Date: 2009-05-15

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 to

access and use

Conditions for access

and use of spatial

data sets and

services, and where

applicable,

corresponding fees

Mandatory Free text + URL if

applicable for

information on any

fees

If data should be used only for a

certain purpose, this should be

named here

Example: not to be displayed at a scale

larger than 1:250,000

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 category 3

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:

organisationName: Institut

Géographique National




67

establishment,

management,

maintenance and

distribution of the

resource

ISO19115

CI_ResponsibleParty

CharacterString

• contactInfo:

o address:

electronicMailAddress [1..*]:

CharacterString

contactInfo:

address:

electronicMailAddress:

[email protected]

9.2 Responsible

party role

Role of the

responsible

organisation

Mandatory Part D.6 of the MD IR

CodeList (see B.5.5

of ISO 10115)

ISO19115

CI_RoleCode

001 (resourceProvider)

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:


CharacterString

• contactInfo:

o address:

� electronicMailAddress [1..*]:

CharacterString

• role: CI_RoleCode

organisationName: European

Environment Agency

contactInfo:

o address:

� electronicMailAddress:

[email protected]

role: 007 (pointOfContact)

10.2 Metadata

date

Date the metadata

record was created

or updated

Mandatory ISO 8601 2008-08-27

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 – bul

Czech – cze

Danish – dan

Dutch – dut

English – eng

Estonian – est

eng




68

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

11.1 Metadata

character set

Full name of the

character coding

standard used for the

dataset

Optional http://www.isotc211.o

rg/2005/resources/Co

delist/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_89

11.3 Spatial

representation

type

Method used to

spatially represent

geographic

information

Conditional: if

the resource is

a dataset or

dataset series

http://www.isotc211.o



l#

MD_SpatialRepresenta

tionTypeCode

Vector Vector




69

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:


CharacterString

• contactInfo:

o address:

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 be

received

Format:

Name: shape file

Version: [not necessary to provide if the

format is shape file; if wished, the GIS

software, which has been used to export

the shape file, can be named; e.g.

ArcGIS9.2]

Distributor:

OrganisationName: Institut

Géographique National

contactInfo:

address:

electronicMailAddress: [email protected]

Digital transfer option:

Online:

http://gis.umweltbundesamt.at/shop/in

dex.jsp

Offline: cdROM

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 19115 Geographic information –

Metadata; WISE Metadata profile




70

11.3 Metadata

standard

version

Version (profile) of

the metadata

standard used

Mandatory Free text ISO 19115:2003 ISO 19115:2003

11.4 Metadata

file identifier

Unique identifier for

this metadata file

Optional Free text Globally unique identifier – GUID

http://www.guidgenerator.com/

e88fbdf4-c70b-4a3d-9dae-1595d8fe27ad

11.5 Metadata

character set

Full name of the

character coding

standard used for the

dataset




l# MD_SpatialRepresenta

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_89

11.7 Spatial

representation

type7

Method used to

spatially represent

geographic

information

Conditional: if

the resource is

a dataset or

dataset series

http://www.isotc211.o



l#

MD_SpatialRepresenta

tionTypeCode

Vector Vector

11.8 Credit8 Recognition of those

who contributed to

the resource(s)

Optional Free text Organisation X

11.9

Presentation

form

Mode in which the

resource is

represented



deList/gmxCodelists.x

ml#CI_PresentationFor

mCode

documentDigital documentDigital

7 Is part of the INPIRE metadata profile 8 Proposed to be part of the INSPIRE metadata profile




71

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 informatio n Under category “QUALITY & VALIDITY “ the following information should be given by the data provider. If applicable, further needs for information can be specified:

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

• Source information: describing the origin of the dataset;

• Process steps: record the events of transformation in the lifetime of the dataset (including information on generalisation and harmonisation)

• 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 attributes);




72

• 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

75

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

Map layer specification

FD_FHRM: Floods Directive - Flood Hazard and Risk M ap

Title* Floods Directive Flood Hazard Risk Maps EU level

Subject* Specification for online interactive map service for Water Information System 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 description 1.0 11/03/13 Wolstrup-Atkins Draft NB: Use track changes to only indicate the changes between versions

76

Contents

1. Overview 77

1.1 Abstract 77

2. Publishing 77


2.2 Mapviewer 77

3. Data and pre-processing 77

3.1 Content datasets 77

3.2 Data extraction 77

3.3 Data extraction and processing steps 80

3.4 Derived datasets 80

4. Visualisation 81

4.1 Layer 1: Population 81

4.2 Layer 2: Economic activities 81

4.3 Layer 3: IED installations 82

4.4 Layer 4: Other potential consequences 82

4.5 Background theme maps 83

4.6 Discomap services 83

4.7 Map spatial layers 83

5. Interaction 85

6. Specific map explanation text 88

77

1. Overview

1.1 Abstract The intention is to disseminate certain aspects of the reported FD Flood Risk Hazard Maps 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 information reported by the Member States and other European level datasets available, for example from other reporting streams and INSPIRE.

2. Publishing


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 datasets Floods 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 extraction The reported information will be extracted from the XML schemas which are to be reported under the FHRM reporting. 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 low probability where groundwater and/or coastal floods are relevant) will be displayed. Options to click on/off layers displaying land cover, population, the E-PRTR installations and the WFD protected areas will be available.

80

3.3 Data extraction and processing steps Data 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 the classification of UoM and country polygons. An additional layer will be added to show where detailed flood hazard and risk maps are available within MS.

Aggregation Flood risk population Flood ris k economic activities

Flood ris k - IED installations

Flood risk – other potential consequences

International UoM

Indication of where there is data




Country Percentage of population within flood extent at risk on Country level

Aggregation of type of economic activities impacted for flood extents within the Country (pie chart)

Percentage of IED installation where pollution risk exists for flood extents within the Country

Aggregation of type of other potential consequences for flood extents within the Country (pie chart)

UoM Percentage of population within flood extent at risk on UoM level

Aggregation of type of economic activities impacted for flood extents within the UoM (pie chart)

Percentage of IED installation where pollution risk exists for flood extents within the UoM

Aggregation of type of other potential consequences for flood extents within the UoM (pie chart)

APSFR* Number of inhabitants potentially affected within certain thresholds

Indication of type of economic activity impacted (pillar)

IED installation where pollution risk exists for flood extents within certain thresholds

Indication of other potential consequences (pillar or list**)

Background theme map

Population dataset (gridded) Landcover dataset E-PRTR installations and

WFD 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 International units of management

UOM Units of management

APSFR Areas of potential significant flood risk

81

4. Visualisation

4.1 Layer 1: Population9

4.2 Layer 2: Economic activities9

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

82

4.3 Layer 3: IED installations9

4.4 Layer 4: Other potential consequences9

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 services To be developed

4.7 Map spatial layers 4.7.1 Zoom levels

Step Geographic

scope Scale Aggregation at Symbol ogy Default

visibility Notes

1 Pan-European to National

Default to 1:10,000,001

International UoM

Classified polygon

Visible Derived from MS reported

2 Cross-border to National

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

Country Classified polygon


3 National to Regional

1:5,000,000 to 1,000,000

UoM Classified polygon


4 Local 1:2,000,000 to 250,000

UoM Classified polygon


5 Local 1:2,000,000 to 250,000

APSFR (where reported)

Classified polygon/line/point

Visible Derived from MS reported, generalized at 1:250,000

6 Local 1:250,000 to 2,000

Probabilities Classified polygon

Visible (through INSPIRE Network services/WMS service where available)

Greater detail can be shown than at the 1:250,000 for European level map

4.7.2 Symbology

Default symbology for features and layers as defined under the INSPIRE Directive will be used as the basis for 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 each classification and the corresponding RBG colours to be used.

4.7.2.1 Population affected

Categorisation – affected population

count Symbology Colour RGB

0-5 Polygon Yellow xx-xx-xx

5-10 Polygon Orange xx-xx-xx

84

10-50 Polygon Red xx-xx-xx

50-100 Polygon Dark red xx-xx-xx

4.7.2.2 Economic activities at risk

Economic activities Symbology Colour RGB

Property (B41) Pie chart Yellow xx-xx-xx

Infrastructure (B42) Pie chart Orange xx-xx-xx

Rural Land Use (B43) Pie chart Green xx-xx-xx

Economic Activity (B44) Pie chart Bordeaux xx-xx-xx

Other (B45) Pie chart Grey xx-xx-xx

Zoom level 1:2,000,000 to 250,000

Pillar – economic activities

Symbology Colour RGB

Property (B41) Pillar Yellow xx-xx-xx

Infrastructure (B42) Pillar Orange xx-xx-xx

Rural Land Use (B43) Pillar Green xx-xx-xx

Economic Activity (B44) Pillar Bordeaux xx-xx-xx

Other (B45) Pillar Grey xx-xx-xx

4.7.2.3 IED installations where pollution risk exists

Categorisation –installations where pollution risk exist -

percentage


1-20 Polygon Light purple xx-xx-xx

20-40 Polygon xx-xx-xx



80-100 Polygon Dark purple xx-xx-xx

4.7.2.4 Other potential consequences

Other potential consequences


Cultural heritage Pie chart Dark brown xx-xx-xx

Other Pie chart Light brown xx-xx-xx

Zoom level 1:2,000,000 to 250,000

Other potential Symbology Colour RGB

85

consequences

Cultural heritage Pillar Dark brown xx-xx-xx

Other Pillar Light brown xx-xx-xx

4.7.3 Layer names

Layer 0: Indication (UoM/APSFR/Other) of where detailed flood hazard and risk maps are available within MS Layer 1: Population affected Layer 2: Economic activities at risk Layer 3: IED installations where pollution risk exists Layer 4: Other potential consequences

5. Interaction

5.1 Layer selection A user in the default map is presented with the Flood hazard/risk maps. In order for the user to select the Flood hazard/risk maps for population or environment or economic activity or other consequences, then the user must select this map through the map selector (buttons). This can be seen in the example below.

The user also has the ability to exert greater control over the layers which are shown in the map and their visibility or transparency from the layer view. The user can also select different kinds of background maps.

86

5.2 Pop-up windows For each zoom step this section details the information which will be available to the user when they click on a visible feature.

87

When a user clicks on the following layers, they will see the following information in the pop-up:

88

Layer Pop-up information to be displayed

Population Economic activities IED installations Other potential consequences

International UoM

• Features of the International UoM (list of country, UoM name/Code, size)

Country • Features of the Country (Country, UoM name/Code, International UoM, size) • Reporting status

UoM

• Features of the UoM (Country, UoM name/Code, size) • Competent authorities • Count/Area of covered APSFR • Links: to websites of CA with more information or/and risk/hazard maps • International UoM

Methods for determination of population affected

Methods for determination of economic activities affected

Methods for determination of IED installations affected and method for determinate the impact on WFD protected areas

Methods for determination of other potential consequences

APSFR • APSFR code, name • Type of flood (list) • Competent authorities • Links: to websites of CA with more information or/and risk/hazard maps • Features of the UoM (Country, UoM name/Code, size • Indication if articles 4 or 13.1(a) or (b) have been applied and the conclusions of these

articles in terms of identification of APSFR or the decision made to proceed to mapping and the production of flood risk management plans

Methods for determination of population affected

Methods for determination of economic activities affected

Methods for determination of IED installations affected and method for determinate the impact on WFD protected areas

Methods for determination of other potential consequences

6. Specific map explanation text To be developed

89

Appendix C

90

C.1 Procedure on how to link to national maps from EU portal This appendix outline the procedure for Member States to register their national level Flood Hazard and Risk Maps (FHRM) under the reporting obligation for flood hazard maps and flood risk maps. This registration follows its own reporting process where MS are responsible for maintaining the links to their national maps, hence shall the most updated FHRM_links xml be available at a source location within the member state to be harvested by the EEA. A guide on how to register the source location of the xml can be found in section C2. The links to national portals should be provided through INSPIRE Network services – however for the first reporting cycle of the FHRM the links can be provided through either a list of PDF's, portal or through WMS. The links to national FHRM shall be done at the APSFR level where applicable. If a MS has used a different level for the identification of the APSFR (eg. UoM) then the links should be reported at this level. In cases where the MS has not used either UoM or APSFR the MS needs to report a 'bounding box' of where they have available national FHRM and report the link at this level. A separate xml file has been developed to support the link to national maps reporting process and has the following structure:

And a translation of the xml schema to a database table

MapCategories to be reported in a separate database table.

The conversion tool will also be able to translate the FHRM_links table to xml in order to upload this.

The AreaUniqueCode (eg. APSFRCode) shall have a one-to-one relationship with reported spatial data.

The file should be named using the following structure and updated when links change within national portal.

91

[Country ID]_[UOM]_[FHRM_links]_ [Date]

• Country ID (ISO code)

• UOM code


Example:

AT_AT1000_FHRM_Links_20140331

If MS are reporting bounding boxes or another spatial identification of an area to which a link to national FHRM then these shall follow the same requirements as set out in section 10.1 named with the following structure

[Country ID]_[UOM]_ [BoundingBox]_[Date]

• Country ID (ISO code1)

• UOM code


Example:

AT_AT1000_BoundingBox_20121231

When a user is presented for the European FHRM one layer will be an overview of where more detailed information can be accessed through national maps. All UoM/APSFR/bounding boxes where a link has been reported to a national (INSPIRE Network service, portal, PDF or WMS) will be highlighted in order for the user quickly to get an overview of where more detailed information can be found. When the user zoom in to more than the threshold value of 1:250.000 the user will be presented to the national map through INSPIRE Network service/WMS. A notification when the user is entering a national map will be given a long with a link to the national portal to seek further information. If the provided link is to a portal of a PDF a pop-up notification will appear with links to the national maps.

It has not been tested how the European map will perform when pulling on several WMS and some modifications to this set-up might be needed in order to keep the performance of the map at an acceptable level.

C.2 Reportnet registration of link (URL) In order to register the URL (HTTP or FTP) to where the FHRM_links.xml is located go to the Reportnet and choose Content Registry from the drop down list – please remember to be logged in to be able to register the source.

92

Then click on Harvesting Sources and 'Add new source'

And add source of xml file(s)

Reporting of spatial data for the Floods Directive (Part II)

Documents

Transcript of Reporting of spatial data for the Floods Directive (Part II)