Ruisseau· 3 segments
Simbach
Crosses 3 administrative regions : Braunau am Inn, Dingolfing-Landau, Rottal-Inn
Total length
22km
Max discharge
2,2m³/s
Max Strahler
3
Segments matched
3
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- Rottal-InnBayern · Germany10.3 kmin this dpt
- Dingolfing-LandauBayern · Germany3.4 kmin this dpt
- Braunau am InnOberösterreich · Austria0.0 kmin this dpt
5 intersecting protected areas
Salzach und Unterer Inn
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Salzach und Inn
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Wetland of International Importance (Ramsar Site)
Stauseen am Unteren Inn
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Niedermoore und Quellsümpfe im Isar-Inn-Hügelland
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
578 distinct species · 3 950 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 20 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).
Indicateurs du tissu écologique
Tissu écologique de Simbach : 17 espèces reliées par 60 interactions GloBI sur 3 types (connectance 28.6%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
22km
Max discharge
2,2m³/s
Max Strahler
3
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.