Ontologia

Ruisseau

Emkumer Bach

Crosses 3 administrative regions : Coesfeld, Recklinghausen, Unna

ruisseau

Total length

2km

Max discharge

6,2m³/s

Max Strahler

3

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080385080917 km²

3 administrative regions crossed (GADM L2)

  • Coesfeld
    Nordrhein-Westfalen · Germany
    10.7 km
    in this dpt
  • Recklinghausen
    Nordrhein-Westfalen · Germany
    8.5 km
    in this dpt
  • Unna
    Nordrhein-Westfalen · Germany
    0.5 km
    in this dpt

27 intersecting protected areas

18 more protected areas

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

Species present

370 distinct species · 997 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 47 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 Emkumer Bach : 39 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 95 interactions GloBI sur 6 types (connectance 8.8%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
47
Interactions affichées
95
Connectance
0.088
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

2km

Max discharge

6,2m³/s

Max Strahler

3

Segments matched

1

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