Rivière· 3 segments
Büdös-gáti-víz
Crosses 3 administrative regions : Balatonföldvári, Fonyód, Tab
Total length
16km
Max discharge
19,2m³/s
Max Strahler
4
Segments matched
3
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- BalatonföldváriSomogy · Hungary10.0 kmin this dpt
- FonyódSomogy · Hungary0.0 kmin this dpt
- TabSomogy · Hungary0.0 kmin this dpt
6 intersecting protected areas
Lake Balaton
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Balaton
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Balaton
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Fishponds and Marshlands south of Lake Balaton
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Kopasz-dombi erdő
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Dél-balatoni berkek
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
266 distinct species · 366 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 40 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 Büdös-gáti-víz : 35 espèces reliées par 57 interactions GloBI sur 5 types (connectance 7.3%, filtre Serrano α=0.2). 5 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
16km
Max discharge
19,2m³/s
Max Strahler
4
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.