Ontologia

Fleuve

Ожузиво

⚠ Partial coverage : only 1 named segment matched so far. The real fleuve extends much further (Strahler order 7 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 2 administrative regions : Ozerskiy rayon, Ozery

fleuve

Max discharge

397,3m³/s

Max Strahler

7

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080312570184 km²

2 administrative regions crossed (GADM L2)

  • Ozerskiy rayon
    Moskva · Russia
    8.6 km
    in this dpt
  • Ozery
    Moskva · Russia
    1.2 km
    in this dpt

1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.

Species present

982 distinct species · 2 910 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Ожузиво : 23 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 86 interactions GloBI sur 5 types (connectance 17.3%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
86
Connectance
0.173
Patrimoniales
1
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Matched len.

3,4km

Max discharge

397,3m³/s

Max Strahler

7

Segments matched

1

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.