Ontologia

Rivière· 69 segments

Spiti River

Crosses 4 administrative regions : Kinnaur, Lahul & Spiti

rivière

Total length

146km

Max discharge

234,5m³/s

Max Strahler

5

Segments matched

69

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080700090236 km²

4 administrative regions crossed (GADM L2)

  • Lahul & Spiti
    Himachal Pradesh · India
    157.7 km
    in this dpt
  • Kinnaur
    Himachal Pradesh · India
    33.6 km
    in this dpt
  • Kinnaur
    Himachal Pradesh · India
    0.0 km
    in this dpt
  • Lahul & Spiti
    Himachal Pradesh · India
    0.0 km
    in this dpt

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

Species present

61 distinct species · 302 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 15 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 Spiti River : 12 espèces reliées par 19 interactions GloBI sur 1 type (connectance 14.0%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
17
Interactions affichées
19
Connectance
0.140
Patrimoniales
0
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

146km

Max discharge

234,5m³/s

Max Strahler

5

Segments matched

69

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