Ontologia

Ruisseau· 4 segments

Grosse Entle

Crosses 3 administrative regions : Entlebuch, Obwalden, Sursee

ruisseau

Total length

12km

Max discharge

8,9m³/s

Max Strahler

3

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080506610473 km²

3 administrative regions crossed (GADM L2)

  • Entlebuch
    Lucerne · Switzerland
    16.8 km
    in this dpt
  • Sursee
    Lucerne · Switzerland
    0.0 km
    in this dpt
  • Obwalden
    Obwalden · Switzerland
    0.0 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

3 266 distinct species · 25 352 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 33 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 Grosse Entle : 20 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 105 interactions GloBI sur 6 types (connectance 16.7%, filtre Serrano α=0.2). 16 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
105
Connectance
0.167
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

12km

Max discharge

8,9m³/s

Max Strahler

3

Segments matched

4

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