Ontologia

Rivière· 80 segments

Trisuli

Crosses 4 administrative regions : Bagmati, Gandaki, Lumbini, Narayani

rivière

Total length

114km

Max discharge

1 032,2m³/s

Max Strahler

6

Segments matched

80

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080833720285 km²

4 administrative regions crossed (GADM L2)

  • Bagmati
    Central · Nepal
    79.2 km
    in this dpt
  • Gandaki
    West · Nepal
    64.3 km
    in this dpt
  • Narayani
    Central · Nepal
    28.8 km
    in this dpt
  • Lumbini
    West · Nepal
    1.3 km
    in this dpt

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

Species present

140 distinct species · 389 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Trisuli : 29 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 34 interactions GloBI sur 4 types (connectance 6.1%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
34
Connectance
0.061
Patrimoniales
2
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

114km

Max discharge

1 032,2m³/s

Max Strahler

6

Segments matched

80

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