Rivière· 329 segments
Омь
Crosses 12 administrative regions : Barabinskiy rayon, Chanovskiy rayon, Kalachinsk, Kalachinskiy rayon, Kormilovskiy rayon +7
Total length
1 126km
Max discharge
114m³/s
Max Strahler
6
Segments matched
329
River geography12 admin regions · 0 communes
12 administrative regions crossed (GADM L2)
- Kuybyshevskiy rayonNovosibirsk · Russia341.7 kmin this dpt
- Ubinskiy rayonNovosibirsk · Russia330.3 kmin this dpt
- Kalachinskiy rayonOmsk · Russia190.1 kmin this dpt
- Nizhneomskiy rayonOmsk · Russia137.6 kmin this dpt
- Kormilovskiy rayonOmsk · Russia125.2 kmin this dpt
- Ust'-Tarkskiy rayonNovosibirsk · Russia118.5 kmin this dpt
- Vengerovskiy rayonNovosibirsk · Russia108.3 kmin this dpt
- Omskiy rayonOmsk · Russia91.6 kmin this dpt
- Chanovskiy rayonNovosibirsk · Russia84.9 kmin this dpt
- Tatarskiy rayonNovosibirsk · Russia67.5 kmin this dpt
- Barabinskiy rayonNovosibirsk · Russia0.4 kmin this dpt
- KalachinskOmsk · Russia0.1 kmin this dpt
1 page = 1 named river (aggregation of 329 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
11 distinct species · 12 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 2 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 Омь : 2 espèces reliées par 1 interaction GloBI sur 1 type (connectance 100.0%, filtre Serrano α=0.2).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
1 126km
Max discharge
114,0m³/s
Max Strahler
6
Segments matched
329
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.