Ontologia

Ruisseau· 8 segments

Ellerbach

Crosses 3 administrative regions : Bad Kreuznach, Cochem-Zell, Paderborn

ruisseau

Total length

140km

Max discharge

1,6m³/s

Max Strahler

2

Segments matched

8

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080387180335 km²

3 administrative regions crossed (GADM L2)

  • Paderborn
    Nordrhein-Westfalen · Germany
    25.3 km
    in this dpt
  • Cochem-Zell
    Rheinland-Pfalz · Germany
    7.6 km
    in this dpt
  • Bad Kreuznach
    Rheinland-Pfalz · Germany
    2.0 km
    in this dpt

23 intersecting protected areas

14 more protected areas

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

Species present

717 distinct species · 2 015 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 33 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 Ellerbach : 22 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 96 interactions GloBI sur 5 types (connectance 16.1%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
96
Connectance
0.161
Patrimoniales
1
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

140km

Max discharge

1,6m³/s

Max Strahler

2

Segments matched

8

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