Ontologia

Rivière

Мишиха

Crosses 2 administrative regions : Kabanskiy rayon, Water body

rivière

Total length

41km

Max discharge

10m³/s

Max Strahler

4

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-30806496601281 km²

2 administrative regions crossed (GADM L2)

  • Kabanskiy rayon
    Buryat · Russia
    7.1 km
    in this dpt
  • Water body
    Buryat · Russia
    2.4 km
    in this dpt

2 intersecting protected areas

  • Lake Baikal

    IUCN Not Applicable

    World Heritage Site (natural or mixed)

  • Baikalsky

    IUCN Not Applicable

    UNESCO-MAB Biosphere Reserve

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

Species present

798 distinct species · 10 702 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 20 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 Мишиха : 12 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 45 interactions GloBI sur 2 types (connectance 19.5%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
22
Interactions affichées
45
Connectance
0.195
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)

Total length

41km

Max discharge

10,0m³/s

Max Strahler

4

Segments matched

1

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