Rivière· 16 segments
Оржиця
Crosses 1 administrative regions : Orzhyts'kyi
Total length
29km
Max discharge
5,7m³/s
Max Strahler
4
Segments matched
16
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Orzhyts'kyiPoltava · Ukraine58.5 kmin this dpt
11 intersecting protected areas
Sula river valley
IUCN Not ReportedEmerald Network
Nyzhnosulskyi
IUCN Not ReportedNational nature park
Nyzhniosulskyi National Nature Park
IUCN Not ReportedEmerald Network
Orzhitsia river valley
IUCN Not ReportedEmerald Network
Velykoseletskyi
IUCN Not ReportedZakaznyk
Plekhivskyi
IUCN Not ReportedZakaznyk
Onishkivskyi
IUCN Not ReportedZakaznyk
Orzhytskyi
IUCN Not ReportedZakaznyk
Zahat
IUCN Not ReportedZapovidne urochyshche
2 more protected areassorted by area
Polovets
IUCN Not ReportedZakaznyk
Bila shapka
IUCN Not ReportedZapovidne urochyshche
1 page = 1 named river (aggregation of 16 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
90 distinct species · 90 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 23 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 Оржиця : 18 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 36 interactions GloBI sur 3 types (connectance 14.2%, 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
29km
Max discharge
5,7m³/s
Max Strahler
4
Segments matched
16
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.