R D EU-HYDRO...EU-Hydro, River Net User Guide 1.0 3 Abbreviations DEM Digital Elevation Model EC European Commission ECRINS European Catchments and River Network System EEA European

COPERNICUS LAND MONITORING SERVICE

REFERENCE DATA: EU-HYDRO

RIVER NET USER GUIDE 1.1

EU-Hydro, River Net User Guide 1.0

2

Document Creation This document was created to provide specific information about the content and facilitate the use of the EU-Hydro River-Net dataset.

Title: EU-Hydro - River Net User Guide 1.1

Content: Description of the characteristics of the EU-Hydro dataset and guideline for use

Reference date: 04/06/2019 Authors: Heinz Gallaun, Kerstin Dohr, Martin Puhm,

André Stumpf, Justine Hugé

Copyright: © European Environment Agency (EEA) In parts of the figures, the COPERNICUS CORE003 image mosaic is included as background. In the figure of the cover page, Bing-Imagery from Microsoft is drawn as background.

Document Change Log

Iss./Rev. Date Section/Page Change Description

Changes by

1.0 29/03/2019 First Version JOANNEUM RESEARCH, GAF-AG, SIRS

1.1 06/11/2019 Corrected Version

Ana Carolina Cuellar (Serco)

Restrictions to Use and Resource Constraints

EEA standard re-use policy: unless otherwise indicated, re-use of content on the EEA website for commercial or non-commercial purposes is permitted free of charge, provided that the source is acknowledged (http://www.eea.europa.eu/legal/copyright).

http://www.eea.europa.eu/legal/copyright


3

Abbreviations

DEM Digital Elevation Model EC European Commission

ECRINS European Catchments and River Network System

EEA European Environment Agency ESRI Environmental Systems Research Institute Inc. ETRS89 European Terrestrial Reference System 1989 EU European Union EU-DEM European Union - Digital Elevation Model GAF GAF AG, a Service Provider

GMES Global Monitoring for Environment and Security

INSPIRE Infrastructure for Spatial Information in Europe

JR JOANNEUM RESEARCH OSM Open Street Map RDA Reference Data Access RPZ LU/LC Riparian Zones Land Use Land Cover SIRS Systèmes d’Information à Référence Spatiale WFD Water Framework Directive


4

Table of Content 1. Introduction ........................................................................................................................ 7

2. Basic specifications ............................................................................................................. 9

2.1. Geographic Coordinate System and Projection Parameters ....................................... 9

2.2. Minimum Mapping Unit (MMU) and resolution ......................................................... 9

2.3. Formats ........................................................................................................................ 9

2.4. Scale ............................................................................................................................. 9

3. Feature Description .......................................................................................................... 10

3.1. Topological relationship ............................................................................................ 10

3.2. Features ..................................................................................................................... 10

3.3. Improved functionality compared to the previous beta version of the EU-Hydro dataset .................................................................................................................................. 17

3.4. Ancillary Data Sources ............................................................................................... 18

3.5. Data Model ................................................................................................................ 19

3.6. Attributes ................................................................................................................... 20

4. FAQ ................................................................................................................................... 23

4.1. Download Data .......................................................................................................... 23

4.2. Opening a Dataset ..................................................................................................... 23

4.3. Data Management ..................................................................................................... 23

4.4. Technical Requirements ............................................................................................ 25

4.5. General Questions ..................................................................................................... 26

5. References ........................................................................................................................ 27

6. Annex ................................................................................................................................ 29

6.1. ISO Country Codes ..................................................................................................... 29

6.2. Description of the attributes ..................................................................................... 30

6.2.1. Common attributes ............................................................................................ 30

6.2.2. Feature class specific attributes ......................................................................... 30


5

List of Figures

Figure 4: Example of EU-Hydro data in the region Neusiedlersee in Austria. ........................... 7

Figure 2: EEA member states (EEA – 33) and cooperating countries (EEA 2019). ..................... 8

Figure 6: Topological relationship in EU-Hydro data model. ................................................... 10

Figure 7: Culvert, Magdebourg canal-bridge (https://www.ab-engineering.fr/pont-canal-magdebourg) ............................................................................................................................ 10

Figure 8: Example of nodes in the Danube basin. .................................................................... 11

Figure 9: Example of a Canal in the Danube basin. .................................................................. 11

Figure 10: Schema and example of ditch (https://en.wikipedia.org/wiki/Ditch). ................... 12

Figure 11: Example of ditches in an agricultural area in the Danube basin. ........................... 12

Figure 13: Example of a river network (linear feature) in the Danube basin. ......................... 13

Figure 14: Example of a canal polygon feature in the Danube basin. ..................................... 13

Figure 15: Example of a ditch polygon feature in the Danube basin ....................................... 14

Figure 16: Example of a river network (polygon feature) in Po basin ..................................... 14

Figure 17: Example of inland waters in the Danube basin....................................................... 15

Figure 18: Example of transitional areas in the Danube basin. ............................................... 15

Figure 19: Example of a coastal polygon. ................................................................................. 16

Figure 20: River basin. .............................................................................................................. 16

Figure 22: Example of the improved coastline in the Duero basin. ......................................... 17

Figure 24: Implementation of the data model into the geodatabase for the Elbe basin as example. ................................................................................................................................... 19

Figure 25: Additional information about the dataset at the Copernicus webpage (COPERNICUS 2019). ................................................................................................................ 24

Figure 26: Examples for metadata specifications of the EU-Hydro dataset at the Copernicus webpage (COPERNICUS 2019). ................................................................................................. 25

List of Tables

Table 1: Summary of feature classes ....................................................................................... 20

Table 2: Abbreviations for feature classes used in OBJECT_ID fields ...................................... 21

Table 3: Abbreviations for basins used in OBJECT_ID fields .................................................... 22

Table 4: ISO coding in EU-Hydro dataset. ............................................................................... 29

Table 5: INSPIRE attributes common to all feature classes ..................................................... 30

Table 6: Common geometry-related attributes ....................................................................... 30

Table 7: Attributes of the Canals_l feature class ..................................................................... 30

Table 8: Attributes of the Ditches_l feature class .................................................................... 32

Table 9: Attributes of the River_Net_l feature class ................................................................ 34

Table 10: Attributes of the Canals_p feature class .................................................................. 35

Table 11: Attributes of the Coastal_p feature class ................................................................. 35

Table 12: Attributes of the Ditches_p feature class ................................................................. 36

Table 13: Attributes of the InlandWater feature class ............................................................ 36

Table 14: Attributes of the RiverBasins feature class .............................................................. 37


6

Table 15: Attributes of the River_Net_p feature class............................................................. 37

Table 16: Attributes of the Transit_p feature class.................................................................. 38

Table 17: Attributes of the Culverts feature class .................................................................... 38

Table 18: Attributes of the Nodes feature class ......................... Error! Bookmark not defined.


7

1. Introduction

The European Environment Agency (EEA) coordinates the implementation of the Copernicus Land

Monitoring Service, and use of the Copernicus services is an integrated part of EEAs strategy to improve

environmental information.

The pan-European hydrographic dataset EU-Hydro was created in the frame of the Preparatory Action

for Copernicus Reference Data Access (RDA) in 2009-2012, and was upgraded in the following years.

EU-Hydro is a dataset providing a photo-interpreted river network, as well as a consistent

interpretation of surface water bodies for all EEA39 countries. It is mainly based on remote sensing

imagery from the years 2006, 2009, and 2012. An example is presented in Figure 1.

Figure 1: Example of EU-Hydro data in the region Neusiedlersee in Austria.

The dataset covers all EEA 39 countries. 33 EEA members: Austria, Belgium, Bulgaria, Croatia, Cyprus,

Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,

Latvia, Liechtenstein, Lithuania, Luxemburg, Malta, Netherlands, Norway, Poland, Portugal, Romania,

Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. 6 cooperating

countries: Albania, Bosnia and Herzegovina, the Former Yugoslav Republic of Macedonia (F.Y.R.O.M.),

Montenegro, Serbia and Kosovo.


8

Figure 2: EEA member states (EEA – 33) and cooperating countries (EEA 2019).

The dataset is mainly used by Copernicus Land Monitoring Service, and for the assessment of water

resources at the European level.


9

2. Basic specifications

2.1. Geographic Coordinate System and Projection Parameters

The data is provided in the Lambert azimuthal equal-area projection. The European Terrestrial

Reference System 1989 is an Earth-Centered / Earth-Fixed geodetic Cartesian reference frame, in

which the Eurasian Plate as a whole is static. The coordinates and maps in Europe based on

ETRS89 are not subject to change due to the continental drift.

2.2. Minimum Mapping Unit (MMU) and resolution

The minimum mapping unit is mainly in the range of 1 hectare, e.g. for Inland Waters. The feature

data extraction has been performed mainly by photo interpretation of Very High Resolution Image

from the period 2011 to 2013, with a spatial resolution of 2.5 metres.

2.3. Formats

EU-Hydro is provided in the ESRI File Geodatabase format as well as in ESRI shapefile format.

2.4. Scale

For linear objects, usage up to a scale of 1 : 30 000, and for derived polygons usage up to a scale of

1 : 50 000 is recommended.


10

3. Feature Description

This section describes in detail the content of the River Network database.

3.1. Topological relationship

The River Network is created by point, line and polygon objects (see Figure 3). In this section the

specific features are explained and examples for the geo-objects included in the data model are given.

Figure 3: Topological relationship in EU-Hydro data model.

3.2. Features

The River Network database consists of following features:

o Culverts: Culverts are crossings of river/canal/ditch with another river/canal/ditch without

having a connection i.e. without any mixing of the water.

Figure 4: Culvert, Magdebourg canal-bridge (https://www.ab-engineering.fr/pont-canal-magdebourg)

o Nodes: a point joining two segments. They are placed on headwaters and mouths of each

watercourse, on confluences and distributary of watercourses, on inlets and outlets of

watercourses into / from water polygons and at dams.


11

Figure 5: Example of nodes in the Danube basin.

o Canals_l: an artificial waterway with no flow, or a controlled flow, usable or built for navigation.

Figure 6: Example of a Canal in the Danube basin.


12

o Ditches_l: an artificial waterway with no flow, or a controlled flow, usually unlined, used

for draining or irrigating land.

Figure 7: Schema and example of ditch (https://en.wikipedia.org/wiki/Ditch).

Figure 8: Example of ditches in an agricultural area in the Danube basin.


13

o River_Net_l: a naturally flowing watercourse.

Figure 9: Example of a river network (linear feature) in the Danube basin.

Canals_p: an artificial waterway with no flow, or a controlled flow, usable or built for navigation,

wider than 50m. Canals_l segments are also digitized at Canals _p location.

Figure 10: Example of a canal polygon feature in the Danube basin.


14

Ditches_p: an artificial waterway with no flow, or a controlled flow, usually unlined, used for

draining or irrigating land, wider than 50m. Ditches_l segments are also digitized at Ditches_p

location.

Figure 11: Example of a ditch polygon feature in the Danube basin

o River_Net_p: a naturally flowing watercourse, wider than 50m. River_Net_l segments are

also digitized at River_Net _p location.

Figure 12: Example of a river network (polygon feature) in Po basin


15

InlandWater: a large body of water entirely surrounded by land.

Figure 13: Example of inland waters in the Danube basin.

Transit_p: water the level of which changes periodically due to tidal action.

Figure 14: Example of transitional areas in the Danube basin.


16

Coastal_p: coastlines and shorelines of these feature class are used as additional feature for orientation to attach inland hydrologic features.

Figure 15: Example of a coastal polygon.

o RiverBasins: is the area covered by the respective subset of the EU-Hydro. The Layout of the subsets considers geographic connectedness and the footprints of major drainage basins.

o Figure 16: River basin.


17

3.3. Improved functionality compared to the previous beta version of the EU-Hydro dataset

Compared to the previous beta version of EU-Hydro, the EU-Hydro Version 1.0 data set has been

significantly improved. This concerns in particular

a generally improved topological consistency of the database;

corrected linkages of linear features to the coast line;

more complete polygon feature classes;

a more complete representation of dams and culverts;

corrected flow directions;

and revised river network attributes.

The revision relied on numerous ancillary data bases (section 3.4), automatic checks, and manual

corrections based on the visual interpretation VHR imagery such as the VHR IMAGE 2012 and

proprietary digital globes.

Figure 17: Example of the improved coastline in the Duero basin.


18

3.4. Ancillary Data Sources

Selected geometries and attributes from the following ancillary data sources were partially included in

the EU-Hydro dataset.

o ECRINS

o RPZ LU/LC

o OSM

o WFD

o MARSgeoDB

o GRAND

The codes of the national water bodies reported through the Water Framework Directive (WFD)

aims at enabling the integration of water related information reported by the countries under the

WFD into a homogeneous European-wide context. The attributes referring to WFD, RPZ LU/LC, and

ECRINS information are transferred from the previous EU-Hydro beta version. They have not been

updated and are provided for information purposes only.


19

3.5. Data Model

The data model of the EU-Hydro River Network consists of seven polygon feature classes, three

polyline feature classes and two point feature classes.

o Point feature classes: Culverts and Nodes;

o Line feature classes: Canals_l, Ditches_l and River_Net_l;

o Polygon feature classes: Canals_p, Ditches_p, River_Net_p, InlandWater, Transit_p,

Coastal_p and RiverBasins.

Figure 18: Implementation of the data model into the geodatabase for the Elbe basin as example.


20

3.6. Attributes

A summary of the features implemented in the EU-Hydro dataset is presented in the table below. In the Annex

all attributes are discussed in detail.

Table 1: Summary of feature classes

Feature Type

Name Definition

Polygon Canals_p An artificial waterway with no flow, or a controlled flow, usable or built for navigation, wider than 50m. Canals_l segments are also digitized at Canals_p location.

Polygon Coastal_p Coastlines and shorelines of these feature classes are used as additional feature for orientation to attach inland hydrologic features.

Polygon Ditches_p An artificial waterway with controlled or no flow (usually smooth), used for draining or irrigating land, wider than 50m. Ditches_l segments are also digitized at Ditches_p location.

Polygon InlandWater A large body of water entirely surrounded by land.

Polygon RiverBasins is the area covered by the respective subset of the EU-Hydro. The Layout of the subsets considers geographic connectedness and the footprints of major drainage basins.

Polygon River_Net_p A naturally flowing watercourse, wider than 50m. River_Net_l segments are also digitized at River_Net_p location.

Polygon Transit_p Transitional areas where the water level changes periodically due to tidal movements.

Line Canals_l An artificial waterway with controlled or no flow, usable or built for navigation.

Line Ditches_l An artificial waterway with no flow, or a controlled flow (usually smooth), used for draining or irrigating land.

Line River_Net_l A naturally flowing watercourse.

Point Culverts Culverts are crossings of river/canal/ditch with another river/canal/ditch without having a connection i.e. without any mixing of the water.

Point Nodes A point joining two segments. They are placed on headwaters and mouths of each watercourse, on confluences of watercourses, on inlets and outlets of watercourses into water polygons and on dams.


21

The following tables give an overview of the feature classes and basins used in the Object_ID field for

a better orientation which features and which basins are included in the various datasets.

Table 2: Abbreviations for feature classes used in OBJECT_ID fields

Feature class 2 letters abbreviation

Canals_l CL

Canals_p CP

Coastal_p CO

Culverts CU

Ditches_l DL

Ditches_p DP

InlandWater IW

Nodes NO

River_Net_l RL

River_Net_p RP

RiverBasins RB

Transit_p TP


22

Table 3: Abbreviations for basins used in OBJECT_ID fields

Basin Code

Angerman 41

Danube 35

Duero 15

Ebro 10

Elbe 27

Fr_Guiana 46

French_Islands 47

Garonne 28

Gota 39

Guadalquivir 12

Hondo 45

Iceland 23

Jucar 14

Kemi 43

Loire 17

Mesima 13

Nemunas 38

Neva 42

Oder 36

Pinios 32

Po 24

Rhine 26

Rhone 11

Seine 25

Shannon 21

Skjern 29

Tajo 16

Tana 44

Tevere 19

Thames 20

Tirso 18

Turkey 33

Tweed 22

Vistula 37

Vorma 40


23

4. FAQ

This section includes the frequently asked questions related to the EU-Hydro dataset.

4.1. Download Data

Where can I find the dataset?

You can download the EU-Hydro datasets from https://land.copernicus.eu/imagery-in-situ/eu-

hydro/eu-hydro-public-beta/eu-hydro-river-network?tab=download

I cannot download the dataset. What can I do?

Update your web browser or try to download using a different browser.

4.2. Opening a Dataset

I cannot open the dataset. What can I do?

First of all, you must be sure that the dataset is properly downloaded. Then extract the dataset from

the zip file using one of the unzip software (WinZip, WinRAR, 7-Zip…). Finally load the dataset into the

GIS software taking into account the parameters (software parameters differ from one to another: file

format, workspace, projection…).

4.3. Data Management

Is additional to this user guide information available?

You can find access to additional information about the dataset and Metadata at:

https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-public-beta/eu-hydro-river-

network?tab=download

https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-public-beta/eu-hydro-river-network?tab=download





24

Figure 19: Additional information about the dataset at the Copernicus webpage (COPERNICUS 2019).

What kind of metadata is accessible?

The following metadata is presented at the Copernicus webpage:

1. Data identification

o Resource title

o Resource abstract

o Resource type

o Resource Locator

2. Classification of Spatial Data

o Topic category

o Keyword

3. Geographic Reference

o Bounding Box

o Coverage

o Geotags

o Coordinate Reference System

4. Temporal Reference

o Temporal extent

o Date of Publication

5. Quality and Validity

o Lineage

o Spatial resolution

6. Conformity

o Specification

o Degree

7. Constraints Related to Access and Use

o Conditions applying to access and use

o Limitations of public access

8. Responsible organisation

o Responsible party


25

o Responsible party role

See also: https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-public-beta/eu-hydro-river-

network?tab=metadata

Figure 20: Examples for metadata specifications of the EU-Hydro dataset at the Copernicus webpage (COPERNICUS 2019).

4.4. Technical Requirements

Which are the basic requirements to explore the dataset?

The user needs to know the common formats (*.mdb, *.gdb, *.shp…) as well as the common software

used to manage this kind of geospatial data. The software could be commercial (ArcGIS, Geomedia,

Global Mapper…) or free/open (QGIS, Grass, …).

System requirements

Hardware recommendations:

o Memory/RAM: 4 GB minimum

o Display properties: 24-bit color depth

o Screen resolution: 1024x768 minimum

o Swap space: determined by operating system; 500 Mb minimum

Software:

o Commercial software: ArcGIS, Geomedia, Global Mapper or other

o Free/Open software: QGIS, GRASS GIS or other.

https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-public-beta/eu-hydro-river-network?tab=metadata

https://land.copernicus.eu/imagery-in-situ/eu-hydro/eu-hydro-public-beta/eu-hydro-river-network?tab=metadata


26

o Web browser (Mozilla Firefox, Google Chrome…)

o Unzip software (WinZip, WinRAR, 7-Zip…)

4.5. General Questions

Where can I get more help?

Ask your question via EEA forum: http://community.eea.europa.eu/

http://community.eea.europa.eu/


27

5. References

COPERNICUS Land Monitoring Service, 2019: EU-Hydro. Last access: 25/02/2019

https://land.copernicus.eu/imagery-in-situ/eu-hydro

EUROPEAN ENVIRONMENT AGENCY (EEA), 2019: EEA member countries and cooperating countries.

Last access: 21/02/2010 https://www.eea.europa.eu/data-and-maps/figures/eea-member-countries-

3

https://land.copernicus.eu/imagery-in-situ/eu-hydro

https://www.eea.europa.eu/data-and-maps/figures/eea-member-countries-3

https://www.eea.europa.eu/data-and-maps/figures/eea-member-countries-3


28

European Environment Agency

Kongens Nytorv 6

1050 Copenhagen

Denmark 0045 33 36 71 17

Copernicus Land Monitoring Service –

Local Component: EU-HYDRO

http://land.copernicus.eu

http://ec.europa.eu/growth/sectors/space/copernicus

http://www.eea.europa.eu

June 2019

© European Environment Agency

http://land.copernicus.eu/

http://ec.europa.eu/growth/sectors/space/copernicus

http://www.eea.europa.eu/


29

6. Annex

6.1. ISO Country Codes

Following country codes according to ISO Standard were applied defining Language (ISO 639-2) and

country owner (ISO 3166) of the hydrological feature.

ISO 3166

Albania (AL), Andorra (AD), Austria (AT), Belgium (BE), Bosnia and Herzegovina (BA), Bulgaria (BG), Croatia (HR), Cyprus (CY), Czech Republic (CZ), Denmark (DK), Estonia (EE), Finland (FI), France (FR), Germany (DE), Greece (GR), Hungary (HU), Iceland (IS), Ireland (IE), Italy (IT), Kosovo (XK), Latvia (LV), Liechtenstein (LI), Lithuania (LT), Luxembourg (LU), Former Yugoslav Republic of Macedonia (MK), Malta (MT), Montenegro (ME), Netherlands (NL), Norway (NO), Poland (PL), Portugal (PT), Romania (RO), Serbia (RS), Slovakia (SK), Slovenia (SI), Spain (ES), Sweden (SE), Switzerland (CH), Turkey (TR), United Kingdom (GB).

ISO 639-2

Albanian (alb), Bulgarian (bul), Czech (cze), German (ger), Hungarian (hun), Italian (ita), Romanian (rum), Slovak (slo), Slavic (sla), Norwegian (nor), Swedish (sve), Swedish (swe), French (fre), Spanish (spa), Danish (dan), Icelandic (ice), Finnish (fin), Turkish (tur), Polish (pol), Modern Greek (gre), Macedonian (mac), English (eng), Chamorro (cha), French (fra), Unknown (UNK).

Table 4: ISO coding in EU-Hydro dataset.


30

6.2. Description of the attributes

6.2.1. Common attributes

Table 5: INSPIRE attributes common to all feature classes

Attribute Name Data Type Description/Comment

BEGLIFEVER Date(8) Specifies the date and time at which this version of the spatial object was inserted into the data set.

ENDLIFEVER Date(8) Specifies the date and time at which this version of the spatial object was superseded.

UPDAT_BY String(15) ID of the updater

UPDAT_WHEN Date(8) Date of update

INSPIRE_ID String(256) External identifier of the spatial object

Table 6: Common geometry-related attributes

Attribute Name Data Type Coverage Description/Comment

LENGTH_GEO Float(8) Line feature classes

Feature length (geodetic) in meters. In contrast to the internally managed SHAPE_LENGTH attribute, the value of this attribute is not influenced by the projection settings.

SHAPE_LENGTH

Float(8) Line and polygon feature classes

Feature length in meters in case of line geometries, for polygon geometries it is the length of the perimeter. Note that this attribute is created and maintained automatically by the GIS database software, thus its name exceeds the length of 10 characters.

AREA_GEO Float(8) Polygon feature classes

Feature area (geodetic) in square meters. In contrast to the internally managed SHAPE_AREA attribute, the value of this attribute is not influenced by the projection settings.

SHAPE_AREA Float(8) Polygon feature classes

Feature area in square meters. Note that this attribute is created and maintained automatically by the GIS database software.

6.2.2. Feature class specific attributes

Table 7: Attributes of the Canals_l feature class


31

Attribute Name Data Type Possible values Description/Comment

DFDD String(5) BH020 DGIWG Feature Data Dictionary

RN_I_ID String(256)

Connector between line and area data if any overlapping polygon feature exists, otherwise NULL. RN_I_ID is transferred from the OBJECT_ID of the overlapping polygon feature.

NAM String(256) UNK Name of the hydrological entity. Empty

attribute

LAN String(256) UNK ISO 639-2 language code with respect to

NAM. Empty attribute

REX String(256)

ISO 3166 code or UNK

Defines the country a hydrological feature is located in. If a feature crosses two countries, both codes separated by “/” are given (example "FI/NO").

HYP Int(2)

1 2 3 4 -9999

Hydrologic persistence: The degree of persistence of water 1: Perennial 2: Intermittent 3: Ephemeral 4: Dry

LOC Int(2)

40 44 45 -9999

Vertical position of a hydrological feature relative to the ground surface 40: Below ground surface 44: On surface 45: Above surface

FUN Int(2)

1 2 6 -9999

Condition of facility: The state of planning, construction, repair, and/or maintenance of the structures and/or equipment comprising a facility and/or located at a site, as a whole. 1: Under construction 2: Abandoned 6: Fully

NVS Int(2)

1 2 3 4 5 -9999

Navigability information 1: Navigable and operational 2: Navigable but abandoned 3: Navigable 4: Navigable with periodic restrictions 5: Not navigable

LENGTH Float(4) Length of the corresponding line segment in km

TR String(10) Segment ID transferred from the attribute TR in ECRINS if possible, NA otherwise.

STRAHLER Int(2) Strahler level of the segment

LONGPATH Float(4) Longest path from a mouth, which is not capturing all rivers from the same mouth

CUM_LEN Float(4) Cumulated length of all segments upstream. In meters

NEXTDOWNID String(256) OBJECT_ID of the next line object (Canals_l, River_Network_l or Ditches_l) in the downstream direction


32

NEXTUPID String (256)

OBJECT_ID of the previous line object (Canals_l, River_Network_l or Ditches_l) in the upstream direction. Warning: Incomplete, not updated

FNODE String(256) Upstream node OBJECT_ID

TNODE String(256) Downstream node OBJECT_ID

PENTE Float(4) Slope computed from the EU DEM according to the formula “highest z-value minus lowest z-value divided by the length of the line”

CGNELIN Int(4) NULL Empty attribute

ERM_ID String(256) UNK National Hydrological Identification Code (NHI), transferred from ERM. Empty attribute

PFAFSTETER Float(8) NULL Empty attribute, kept for future upgrades

OT_Z Int(2) 0, 1

0: z-values of the feature do not decrease monotonically along the flow direction 1: z-values of the feature decrease monotonically along the flow direction

Table 8: Attributes of the Ditches_l feature class



RN_I_ID String(256)



attribute



REX String(256)



HYP Int(2)

1 2 3 4 -9999


LOC Int(2)

40 44 45 -9999



33

FUN Int(2)

1 2 6 -9999

Condition of facility: The state of planning, construction, repair, and/or maintenance of the structures and or equipment comprising a facility and/or located at a site, as a whole. 1: Under construction 2: Abandoned 6: Fully

NVS Int(2)

1 2 3 4 5 -9999













CGNELIN Int(4) NULL Empty attribute



MONOT_Z Int(2) 0, 1



34

Table 9: Attributes of the River_Net_l feature class



RN_I_ID String(256)



attribute



REX String(256)



HYP Int(2)

1 2 3 4 -9999


LOC Int(2)

40 44 45 -9999


FUN Int(2)

1 2 6 -9999

Condition of facility: The state of planning, construction, repair, and/or maintenance of the structures and / or equipment comprising a facility and/or located at a site, as a whole. 1: Under construction 2: Abandoned 6: Fully

NVS Int(2)

1 2 3 4 5 -9999






35









CGNELIN Int(4) NULL Warning: Incomplete, not updated

ThematicID String(256) European WFD code. Transferred from the WISE WFD reference spatial dataset.


MC Int(2) 0, 1

Watercourse Channel Type 0: Braided Stream: A watercourse divided into an intricate network of interlacing channels (generally shallow, the smaller channels are continually shifting and are separated by bar deposits). 1: Normal Stream: A watercourse that has not been channelized or relocated (follows a normal meandering channel with variations in channel bed morphology).


MONOT_Z Int(2) 0, 1


Table 10: Attributes of the Canals_p feature class

Attribute Name Data Type Possible values

Description/Comment

DFDD String(5) BH020 DGIWG Feature Data

Dictionary

Table 11: Attributes of the Coastal_p feature class


DFDD String(5) SA010 DGIWG Feature Data Dictionary



36

Table 12: Attributes of the Ditches_p feature class



Table 13: Attributes of the InlandWater feature class



NAM String(256) Name of the hydrological entity. Warning:

Incomplete, not updated

LAN String(256) ISO 639-2 language code with respect to NAM.

Warning: Incomplete, not updated

REX String(256)



HYP Int(2)

1 2 3 4 -9999


LOC Int(2)

40 44 45 -9999


FUN Int(2)

1 2 6 -9999

Condition of facility: The state of planning, construction, repair, and/or maintenance of the structures and or equipment comprising a facility and/or located at a site, as a whole. 1: Under construction 2: Abandoned 6: Fully

NVS Int(2)

1 2 3 4 5 -9999


AREA Float(4) Area of water polygon in square meters.

ALTITUDE Float(4) Altitude in meters at the centroid of the polygon, from the EU_DEM.

PERIMETER Int(4) Water body perimeter in meters.

WSO_ID Int(4)

WSO (Water Shed Order). ID of the River Basin to which the lake belongs. ID is transferred from CCM and connects lakes in EU-Hydro to CCM. Warning: Incomplete, not updated

UPSTR_AREA Float(4) -9999 Empty attribute


37

SYSTEM_CD String(1)

A System Code, for distinguishing between large ocean systems as well as internal drainage basins. Transferred from ECRINS. Warning: Incomplete, not updated

SEA_CD Int(4) Domain Sea Code, for distinguishing between different seas within an ocean system. Warning: Incomplete, not updated

LKE_TYPE String(1) N R U

Code of the lake type N: Natural R: Reservoir U: Unknown

LAKID String(10) ID of the lake in ECRINS. Warning: Incomplete, not updated

LAKIN Number of inflowing lines (river, canals and/or ditch) in the InlandWater feature

LAKOUT Number of outflowing lines (river, canals and/or ditch) in the InlandWater feature


CCM_ID Int(4) Unique ID in the source CCM, transferred from ECRINS. Warning: Incomplete, not updated

ERM_ID String(256) UNK National Hydrological Identification Code (NHI). Empty attribute

WINDOW Int(4)

Source window of placement (may be inaccurate considering reallocation to processing windows) - from ECRINS. Processing data windows (Numbered from 2000 to 2018) originally in the CCM dataset. Warning: Incomplete, not updated


Table 14: Attributes of the RiverBasins feature class


This feature class has no specific attributes. For a description of common attributes please refer to Table 5 and Table 6.

Table 15: Attributes of the River_Net_p feature class




38

Table 16: Attributes of the Transit_p feature class




ELEV Float(4) 0 Elevation of the objects’ centroid in meters, based on the EU-DEM. For Transit_p, the value of this attribute is always zero.

Table 17: Attributes of the Culverts feature class


DFDD String(5) AQ065 DGIWG Feature Data Dictionary

ELEV Float(4) 0 Elevation of the objects’ centroid in meters, based on the EU-DEM. For Transit_p, the value of this attribute is always zero.

Table 18: Attributes of the Nodes feature class


DFDD String(5)

BH020 BH030 BH140 BI020

DGIWG Feature Data Dictionary BH020: Code for Canals_l and Canals_p BH030: Code for Ditches_l and Ditches_p BH140: Code for River_net_l and River_net_p BI020: Code for dams

WMT Int(4)

1 4 9 10 49 1000 1001 1004 1005 1045

Type of node 1: Mouth 4: Confluence 9: Distributary 10: Source 49: Confluence and distributary 1000: River segment 1001: Endorheic system 1004: Waterbody inlet 1005: Waterbody outlet 1045: Waterbodies inlet/outlet


39

HYDRONODCT String(256)

Junction Outlet Source flow Constriction flow Regulation NULL

Junction: Node where three or more links are coincident Outlet: Ending node of a series of interconnected links Source: Starting node of a series of interconnected links flow Constriction: A network node unrelated to the network topology per se, but associated with a hydrographic point of interest or facility, or a man-made object, that affects the network flow. flow Regulation: A network node unrelated to the network topology per se, but associated with a hydrographic point of interest or facility, or a man-made object, that regulates the network flow.

LEN_TOM Float(4) Length from the node to the river mouth at the coast, along the flow path

NUM_SEG Number of segments touching the node

ELEV Float(4) Elevation at the location of the node based on the EU-DEM

NODETYPE String(256)

Canal Dam River Ditch

This field reflects which entities from linear feature classes touch the given node. The choice of the code depends on a hierarchy between the touching line objects (Dam > River > Canal > Ditch).

EU_DAM_ID String(256) NA for ordinary nodes

European code for dams. Warning: Incomplete, not updated

NAT_DAM_ID String(256) NA for ordinary nodes

National code for dams. Warning: Incomplete, not updated

DAMX Float(4) NA for ordinary nodes

X-coordinate of the dam

DAMY Float(4) NA for ordinary nodes

Y-coordinate of the dam

DAM_NAM String(256) NA for ordinary nodes

Name of the dam.

DAM_NAMALT String(256) NA for ordinary nodes

Alternative known name of the dam

DAM_USE String(256) NA for ordinary nodes

Main use of the dam

DAM_WIDTH Float(4) NULL for ordinary nodes

Width of the dam in meters

DAM_HEIGHT Float(4) NULL for ordinary nodes

Height of the dam in meters

R D EU-HYDRO...EU-Hydro, River Net User Guide 1.0 3 Abbreviations DEM Digital Elevation Model EC European Commission ECRINS European Catchments and River Network System EEA European

Documents