Ruisseau· 2 segments
Kanaal door Voorne
Crosses 4 administrative regions : Brielle, Hellevoetsluis, Nissewaard, Zuid Hollandse Meren
Total length
9km
Max discharge
1,1m³/s
Max Strahler
2
Segments matched
2
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- HellevoetsluisZuid-Holland · Netherlands5.3 kmin this dpt
- BrielleZuid-Holland · Netherlands2.5 kmin this dpt
- NissewaardZuid-Holland · Netherlands0.1 kmin this dpt
- Zuid Hollandse MerenZuid Hollandse Meren · Netherlands0.0 kmin this dpt
5 intersecting protected areas
NNN-ZH
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Haringvliet
IUCN IVNature Conservation Act
Haringvliet
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Haringvliet
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Haringvliet
IUCN IVWetland of International Importance (Ramsar Site)
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
2 870 distinct species · 80 467 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 36 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 Kanaal door Voorne : 25 espèces reliées par 140 interactions GloBI sur 6 types (connectance 18.9%, filtre Serrano α=0.2). 14 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
9km
Max discharge
1,1m³/s
Max Strahler
2
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.