Ontologia

Ruisseau· 4 segments

Kesselbach

Crosses 4 administrative regions : Ebersberg, Innsbruck Land, Rosenheim, Schwaz

ruisseau

Total length

115km

Max discharge

1,9m³/s

Max Strahler

2

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080497830599 km²

4 administrative regions crossed (GADM L2)

  • Innsbruck Land
    Tirol · Austria
    11.1 km
    in this dpt
  • Schwaz
    Tirol · Austria
    1.4 km
    in this dpt
  • Ebersberg
    Bayern · Germany
    1.3 km
    in this dpt
  • Rosenheim
    Bayern · Germany
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

1 771 distinct species · 5 456 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 Kesselbach : 26 espèces reliées par 138 interactions GloBI sur 6 types (connectance 20.7%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
138
Connectance
0.207
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

115km

Max discharge

1,9m³/s

Max Strahler

2

Segments matched

4

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