Ontologia

Ruisseau· 19 segments

Río Torreni Mayu

Crosses 3 administrative regions : Ayopaya, Chapare, Quillacollo

ruisseau

Total length

44km

Max discharge

11,2m³/s

Max Strahler

3

Segments matched

19

River geography3 admin regions · 0 communes

Parent watershed

hybas-6080644330634 km²

3 administrative regions crossed (GADM L2)

  • Chapare
    Cochabamba · Bolivia
    65.2 km
    in this dpt
  • Ayopaya
    Cochabamba · Bolivia
    3.3 km
    in this dpt
  • Quillacollo
    Cochabamba · Bolivia
    0.2 km
    in this dpt

1 intersecting protected areas

  • Tunari

    IUCN Not Reported

    National Park

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

Species present

166 distinct species · 393 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 Río Torreni Mayu : 19 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 17 interactions GloBI sur 2 types (connectance 8.1%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

44km

Max discharge

11,2m³/s

Max Strahler

3

Segments matched

19

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