Rivière· 38 segments
Уводь
Crosses 9 administrative regions : Furmanovskiy rayon, Ivanovo, Ivanovskiy rayon, Kameshkovskiy rayon, Komsomol’skiy rayon +4
Total length
367km
Max discharge
18,9m³/s
Max Strahler
5
Segments matched
38
River geography9 admin regions · 0 communes
9 administrative regions crossed (GADM L2)
- Ivanovskiy rayonIvanovo · Russia59.9 kmin this dpt
- Kovrovskiy rayonVladimir · Russia26.5 kmin this dpt
- Komsomol’skiy rayonIvanovo · Russia23.6 kmin this dpt
- Savinskiy rayonIvanovo · Russia19.6 kmin this dpt
- Shuyskiy rayonIvanovo · Russia19.0 kmin this dpt
- Furmanovskiy rayonIvanovo · Russia9.9 kmin this dpt
- Lezhnevskiy rayonIvanovo · Russia6.8 kmin this dpt
- IvanovoIvanovo · Russia5.0 kmin this dpt
- Kameshkovskiy rayonVladimir · Russia1.1 kmin this dpt
3 intersecting protected areas
Klyaz`minskij
IUCN IVState Natural Zakaznik
Uvod`skoe vodohranilishhe
IUCN Not ReportedNatural Monument
Sad im. 1-e Maya
IUCN Not ReportedPark of Culture and Rest
1 page = 1 named river (aggregation of 38 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
19 distinct species · 25 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 9 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 Уводь : 9 espèces reliées par 7 interactions GloBI sur 4 types (connectance 19.4%, 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
367km
Max discharge
18,9m³/s
Max Strahler
5
Segments matched
38
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.