Ontologia

Ruisseau· 3 segments

Wiesbach

Crosses 4 administrative regions : Landsberg am Lech, Mühldorf am Inn, Ostallgäu, Reutte

ruisseau

Total length

154km

Max discharge

22,7m³/s

Max Strahler

3

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-20804706001294 km²

4 administrative regions crossed (GADM L2)

  • Landsberg am Lech
    Bayern · Germany
    12.4 km
    in this dpt
  • Mühldorf am Inn
    Bayern · Germany
    4.7 km
    in this dpt
  • Reutte
    Tirol · Austria
    3.2 km
    in this dpt
  • Ostallgäu
    Bayern · Germany
    1.2 km
    in this dpt

8 intersecting protected areas

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

Species present

1 938 distinct species · 41 542 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 22 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 Wiesbach : 18 espèces reliées par 49 interactions GloBI sur 4 types (connectance 21.2%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
22
Interactions affichées
49
Connectance
0.212
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

154km

Max discharge

22,7m³/s

Max Strahler

3

Segments matched

3

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