Ontologia

Rivière· 11 segments

Alme

Crosses 3 administrative regions : Hochsauerlandkreis, Paderborn, Soest

rivière

Total length

81km

Max discharge

13,3m³/s

Max Strahler

4

Segments matched

11

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080387170407 km²

3 administrative regions crossed (GADM L2)

  • Paderborn
    Nordrhein-Westfalen · Germany
    46.1 km
    in this dpt
  • Hochsauerlandkreis
    Nordrhein-Westfalen · Germany
    9.2 km
    in this dpt
  • Soest
    Nordrhein-Westfalen · Germany
    0.0 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

676 distinct species · 1 392 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Alme : 17 espèces reliées par 99 interactions GloBI sur 6 types (connectance 21.3%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
99
Connectance
0.213
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

81km

Max discharge

13,3m³/s

Max Strahler

4

Segments matched

11

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