Ontologia

Rivière· 92 segments

Hemavati

Crosses 4 administrative regions : Chikmagalur, Hassan, Kodagu, Mandya

rivière

Total length

225km

Max discharge

49,4m³/s

Max Strahler

5

Segments matched

92

River geography4 admin regions · 0 communes

Parent watershed

hybas-40811351801224 km²

4 administrative regions crossed (GADM L2)

  • Hassan
    Karnataka · India
    184.1 km
    in this dpt
  • Mandya
    Karnataka · India
    72.9 km
    in this dpt
  • Chikmagalur
    Karnataka · India
    63.1 km
    in this dpt
  • Kodagu
    Karnataka · India
    3.3 km
    in this dpt

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

Species present

51 distinct species · 69 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 18 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 Hemavati : 17 espèces dont 3 patrimoniales (LR IUCN CR/EN/VU) reliées par 12 interactions GloBI sur 2 types (connectance 7.8%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
18
Interactions affichées
12
Connectance
0.078
Patrimoniales
3
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

225km

Max discharge

49,4m³/s

Max Strahler

5

Segments matched

92

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