Ruisseau· 2 segments
Beneden-Merwede
Crosses 3 administrative regions : Dordrecht, Hardinxveld-Giessendam, Sliedrecht
Total length
16km
Max discharge
16,6m³/s
Max Strahler
3
Segments matched
2
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- SliedrechtZuid-Holland · Netherlands1.9 kmin this dpt
- DordrechtZuid-Holland · Netherlands1.6 kmin this dpt
- Hardinxveld-GiessendamZuid-Holland · Netherlands0.1 kmin this dpt
6 intersecting protected areas
NNN-ZH
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Biesbosch
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Biesbosch
IUCN IVNature Conservation Act
Biesbosch
IUCN IIWetland of International Importance (Ramsar Site)
Biesbosch
IUCN Not ReportedSpecial Protection Area (Birds Directive)
De Biesbosch
IUCN IINational Park
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
3 346 distinct species · 151 677 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 42 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Beneden-Merwede : 22 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 163 interactions GloBI sur 6 types (connectance 18.9%, filtre Serrano α=0.2). 20 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
16km
Max discharge
16,6m³/s
Max Strahler
3
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.