Ruisseau· 3 segments
Oteretni kanal Sava-Odra
Crosses 5 administrative regions : Lekenik, Martinska Ves, Orle, Velika Gorica, Zagreb
Total length
32km
Max discharge
5,4m³/s
Max Strahler
3
Segments matched
3
River geography5 admin regions · 0 communes
5 administrative regions crossed (GADM L2)
- OrleGrad Zagreb · Croatia8.3 kmin this dpt
- Velika GoricaGrad Zagreb · Croatia6.9 kmin this dpt
- ZagrebGrad Zagreb · Croatia5.7 kmin this dpt
- Martinska VesSisacko-Moslavacka · Croatia1.2 kmin this dpt
- LekenikSisacko-Moslavacka · Croatia0.0 kmin this dpt
4 intersecting protected areas
Turopolje
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Odransko polje
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Odransko polje
IUCN Not ReportedSignificant Landscape
Turopoljski lug
IUCN Not ReportedSignificant Landscape
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
132 distinct species · 607 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 47 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 Oteretni kanal Sava-Odra : 40 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 98 interactions GloBI sur 5 types (connectance 9.1%, filtre Serrano α=0.2). 7 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
32km
Max discharge
5,4m³/s
Max Strahler
3
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.