Ontologia

Rivière· 9 segments

Lenne

Crosses 3 administrative regions : Hochsauerlandkreis, Märkischer Kreis, Olpe

rivière

Total length

159km

Max discharge

14,6m³/s

Max Strahler

4

Segments matched

9

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803938201351 km²

3 administrative regions crossed (GADM L2)

  • Hochsauerlandkreis
    Nordrhein-Westfalen · Germany
    16.5 km
    in this dpt
  • Olpe
    Nordrhein-Westfalen · Germany
    9.8 km
    in this dpt
  • Märkischer Kreis
    Nordrhein-Westfalen · Germany
    0.8 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

630 distinct species · 1 104 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 Lenne : 32 espèces reliées par 132 interactions GloBI sur 5 types (connectance 16.1%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
132
Connectance
0.161
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

159km

Max discharge

14,6m³/s

Max Strahler

4

Segments matched

9

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