European catchments and Rivers network system (ECRINS) - version 1, Jun. 2012

River segments mimic the surface rivers on a simplified way, allowing simple journeying. As for FECs but completed because of the process, any segment may have 0, 1, or 2 upstream and single downstream. The reason for single upstream is because spurious branching segments have been removed (roughly 160,000) from CCM source during the Ecrins making.

<br><div>The segments mimic rivers that are cultural, not simply defined objects. The 'dummy rivers' (ID is CGENELIN) branches together all the segments which spring is most distant to the se, then second most distant and connecting to this first set of segments, etc; the 'true rivers' are those sets of segments having the same name, disregarding translation (segments on the Rheine, Rhin, etc have same river ID). Name of true rivers is hosted in the EcrGaz database.

<br></div><div>Dummy rivers maybe sorted out as “main drains” that either connect FECs together (continental FECs) or are the most important in a coastal FEC. Main drains are hence the potential population of “WFD large rivers”, since the FEC average size is ~1/10 of the threshold catchment size of main rivers.

The geodatabases contains two feature classes: C_Tr where all segments lines are. This table links to FECs, since a FEC may contain several segments. Feature class C_node contains all nodes, making implicit the flow direction that is identified in C_tr by FNode (from node) and TNode (to node).</div>

Default

IdentificationAbout this resource

Alternate Identifier

b5c56aea-133e-4ef5-9c37-f87d1cf886f2

Publication Date
2010-12-08
Title

European catchments and Rivers network system (ECRINS) - version 1, Jun. 2012

Short Name

ECRINS

Abstract

River segments mimic the surface rivers on a simplified way, allowing simple journeying. As for FECs but completed because of the process, any segment may have 0, 1, or 2 upstream and single downstream. The reason for single upstream is because spurious branching segments have been removed (roughly 160,000) from CCM source during the Ecrins making.

<br><div>The segments mimic rivers that are cultural, not simply defined objects. The 'dummy rivers' (ID is CGENELIN) branches together all the segments which spring is most distant to the se, then second most distant and connecting to this first set of segments, etc; the 'true rivers' are those sets of segments having the same name, disregarding translation (segments on the Rheine, Rhin, etc have same river ID). Name of true rivers is hosted in the EcrGaz database.

<br></div><div>Dummy rivers maybe sorted out as “main drains” that either connect FECs together (continental FECs) or are the most important in a coastal FEC. Main drains are hence the potential population of “WFD large rivers”, since the FEC average size is ~1/10 of the threshold catchment size of main rivers.

The geodatabases contains two feature classes: C_Tr where all segments lines are. This table links to FECs, since a FEC may contain several segments. Feature class C_node contains all nodes, making implicit the flow direction that is identified in C_tr by FNode (from node) and TNode (to node).</div>

Dataset Language

English

 
Dataset Creator
Metadata Provider
Dataset Contact
Keywords (Categories)

  • Inland waters

Keywords (GEMET - INSPIRE themes, version 1.0)

  • Hydrography

Keywords (EEA topics)

  • Water

Geographic Coverage

Geographic Description

Europe

Bounding Box

West Bounding Coordinate

-18.70

East Bounding Coordinate

53.80

North Bounding Coordinate

73.50

South Bounding Coordinate

26.50

Bounding Altitudes

Minimum
Maximum
Unit

Temporal Coverage

Range of Dates

Begin Date

1990-01-01

End Date

2006-12-31

resourceLicensesLicense Information

Intellectual Rights

Copyright holder: European Environment Agency (EEA).

 

Distribution

Online

A brief description of the the content of online URL.

European catchments and rivers network system (Ecrins), rivers - version 1, Jun. 2012

URL
https://sdi.eea.europa.eu/webdav/datastore/public/eea_v_3035_250_k_ecrins-rivers_p_1990-2006_v01_r00/
 
 

Project

• Project

Title
Abstract

This dataset is derived from the segments and nodes data sets produced by CCM. Significant reprocessing has been carried out to clean the data sets, create hierarchy, populate incomplete fields (e.g. distance to the sea), create dummy rivers and, last but most important, give names to rivers. A systematic check of branching errors is currently being carried out to identify topological errors based on discharge computation and name matching.

Personnel

Organization Name

European Environment Agency (EEA)

Individual Name

Given Name
Surname
Position Name

Custodian | Point of contact

 
 

Methods

• Method

Method Step

Description

The aggregation of European catchments and Rivers network system (Ecrins) id a geographical information system of the European hydrographical systems with a full topological information. It is organised from a layer of 181,071 “functional elementary catchments (FECs)” which average size is ~62 km2, fully connected with explicit identifier (ID) relationships and upstream area. Catchments are grouped as sub-basins, river basin districts (actual and functional to meet hydrographical continuity). The catchments are as well organised according to their sea shore of emptying to meet Marine Strategy delineations. Catchments are drained by 1,348,163 river segments, sorted as “main drains” (connecting together the FECs) and secondary drains (internal to a FEC). river segments mimic the natural drainage, however fulfilling the topological constraint of “0,1 or 2 upstreams, single or 0 downstream”. Each segment is populated with distance to the sea, to ease further processing. They are connected to elementary catchments and nodes documented with altitude data. The current layer comprises 70,847 lake objects. The database comprises the following tables: feature class C_Lak with all information related to all still waterbodies which area is more than the Corine Land cover threshold, plus those identified because a reservoir or any other relevant source. This table is completed by the centroids of lakes, V_lak_Centro. The complex relationships between lakes and river segments are documented by table lakInOut where the inlet and the outlet(s) segments are reported. Complementary tables, needed by the water accounts, v_lakperadmin et v_linterfec respectively document the lake to administrative entities, with shared area and same with FECs. Lake naming comes from fours sources: ERM, Eldred2, Art 13 reporting and Wikipedia. Hydrographical information (volume, Zaverage, Zmax) and is permanently updated from three source: Eldred2, the dams database, and Wikipedia.

Software

Title
Version

1.0

 
 

Data Tables

• Data Table

Name

EcrRiv.mdb

Physical

Data Format

Externally Defined Format

Format Name

Microsoft Access

• Data Table

Name

EcrRiv.sqlite

Physical

Data Format

Externally Defined Format

Format Name

Spatialite