Ontologia

Ruisseau

Lühlingsbach (Lünsebach)

Crosses 2 administrative regions : Hochsauerlandkreis, Paderborn

ruisseau

Total length

3km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080387170407 km²

2 administrative regions crossed (GADM L2)

  • Paderborn
    Nordrhein-Westfalen · Germany
    2.9 km
    in this dpt
  • Hochsauerlandkreis
    Nordrhein-Westfalen · Germany
    1.0 km
    in this dpt

18 intersecting protected areas

9 more protected areas

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

Species present

850 distinct species · 1 493 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Lühlingsbach (Lünsebach) : 25 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 106 interactions GloBI sur 6 types (connectance 15.1%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
106
Connectance
0.151
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

3km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

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