Ontologia

Rivière· 65 segments

Tawa

Crosses 4 administrative regions : Betul, Chhindwara, Hoshangabad, Sehore

rivière

Total length

201km

Max discharge

151,5m³/s

Max Strahler

6

Segments matched

65

River geography4 admin regions · 0 communes

Parent watershed

hybas-4080996000333 km²

4 administrative regions crossed (GADM L2)

  • Hoshangabad
    Madhya Pradesh · India
    129.2 km
    in this dpt
  • Betul
    Madhya Pradesh · India
    79.4 km
    in this dpt
  • Chhindwara
    Madhya Pradesh · India
    39.1 km
    in this dpt
  • Sehore
    Madhya Pradesh · India
    0.0 km
    in this dpt

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

Species present

56 distinct species · 177 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 Tawa : 16 espèces dont 3 patrimoniales (LR IUCN CR/EN/VU) reliées par 16 interactions GloBI sur 2 types (connectance 10.5%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
18
Interactions affichées
16
Connectance
0.105
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

201km

Max discharge

151,5m³/s

Max Strahler

6

Segments matched

65

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