Ontologia

Rivière· 37 segments

Diphupani river

Crosses 4 administrative regions : Dimapur, Golaghat, Karbi Anglong, Kohima

rivière

Total length

46km

Max discharge

36,7m³/s

Max Strahler

5

Segments matched

37

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080894370599 km²

4 administrative regions crossed (GADM L2)

  • Dimapur
    Nagaland · India
    56.4 km
    in this dpt
  • Kohima
    Nagaland · India
    16.8 km
    in this dpt
  • Golaghat
    Assam · India
    6.4 km
    in this dpt
  • Karbi Anglong
    Assam · India
    0.0 km
    in this dpt

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

Species present

108 distinct species · 217 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Diphupani river : 37 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 37 interactions GloBI sur 4 types (connectance 4.5%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
37
Connectance
0.045
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

46km

Max discharge

36,7m³/s

Max Strahler

5

Segments matched

37

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