Ontologia

Ruisseau· 3 segments

Oranjekanaal

Crosses 3 administrative regions : Emmen, Midden-Drenthe, Westerveld

ruisseau

Total length

54km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803607801108 km²

3 administrative regions crossed (GADM L2)

  • Midden-Drenthe
    Drenthe · Netherlands
    9.9 km
    in this dpt
  • Emmen
    Drenthe · Netherlands
    4.4 km
    in this dpt
  • Westerveld
    Drenthe · Netherlands
    3.5 km
    in this dpt

6 intersecting protected areas

1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

2 877 distinct species · 37 622 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Oranjekanaal : 29 espèces + 7 bulles famille, 91 interactions GloBI documentées sur 5 types (connectance 14.4%, filtre Serrano α=0.2). Les 7 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
36
Interactions affichées
91
Connectance
0.144
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

54km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

3

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.