Ontologia

Rivière· 4 segments

Budi Kulo

Crosses 4 administrative regions : Bahraich, Bheri, Lakhimpur Kheri, Seti

rivière

Total length

42km

Max discharge

84,3m³/s

Max Strahler

6

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-40808209703133 km²

4 administrative regions crossed (GADM L2)

  • Bheri
    Mid-Western · Nepal
    26.3 km
    in this dpt
  • Bahraich
    Uttar Pradesh · India
    9.2 km
    in this dpt
  • Seti
    Far-Western · Nepal
    3.2 km
    in this dpt
  • Lakhimpur Kheri
    Uttar Pradesh · India
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

65 distinct species · 87 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
23
Interactions affichées
21
Connectance
0.083
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

42km

Max discharge

84,3m³/s

Max Strahler

6

Segments matched

4

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