Ontologia

Ruisseau· 2 segments

Deilbach

Crosses 3 administrative regions : Ennepe-Ruhr-Kreis, Essen, Mettmann

ruisseau

Total length

21km

Max discharge

1,1m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080392760601 km²

3 administrative regions crossed (GADM L2)

  • Mettmann
    Nordrhein-Westfalen · Germany
    5.3 km
    in this dpt
  • Essen
    Nordrhein-Westfalen · Germany
    3.9 km
    in this dpt
  • Ennepe-Ruhr-Kreis
    Nordrhein-Westfalen · Germany
    1.6 km
    in this dpt

28 intersecting protected areas

19 more protected areas

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

Species present

2 251 distinct species · 11 247 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Deilbach : 29 espèces reliées par 91 interactions GloBI sur 6 types (connectance 11.7%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
91
Connectance
0.117
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

21km

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.