Ontologia

Ruisseau

Eulswaager Bach

Crosses 3 administrative regions : Remscheid, Solingen, Wuppertal

ruisseau

Total length

0km

Max discharge

4,2m³/s

Max Strahler

2

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803998102002 km²

3 administrative regions crossed (GADM L2)

  • Wuppertal
    Nordrhein-Westfalen · Germany
    18.5 km
    in this dpt
  • Solingen
    Nordrhein-Westfalen · Germany
    2.8 km
    in this dpt
  • Remscheid
    Nordrhein-Westfalen · Germany
    0.0 km
    in this dpt

23 intersecting protected areas

14 more protected areas

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

Species present

2 699 distinct species · 56 527 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 26 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 Eulswaager Bach : 21 espèces reliées par 45 interactions GloBI sur 3 types (connectance 13.8%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
26
Interactions affichées
45
Connectance
0.139
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

0km

Max discharge

4,2m³/s

Max Strahler

2

Segments matched

1

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