Ontologia

Ruisseau

Asmecker Siepen

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

ruisseau

Total length

1km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803938201351 km²

3 administrative regions crossed (GADM L2)

  • Olpe
    Nordrhein-Westfalen · Germany
    3.0 km
    in this dpt
  • Hochsauerlandkreis
    Nordrhein-Westfalen · Germany
    0.0 km
    in this dpt
  • Märkischer Kreis
    Nordrhein-Westfalen · Germany
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

1 138 distinct species · 1 890 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Asmecker Siepen : 21 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 102 interactions GloBI sur 6 types (connectance 17.1%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
102
Connectance
0.171
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

1km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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