Ontologia

Ruisseau· 5 segments

Río Quero

Crosses 4 administrative regions : Cevallos, Mocha, Quero, Tisaleo

ruisseau

Total length

13km

Max discharge

8,2m³/s

Max Strahler

3

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-60802337601319 km²

4 administrative regions crossed (GADM L2)

  • Quero
    Tungurahua · Ecuador
    8.8 km
    in this dpt
  • Mocha
    Tungurahua · Ecuador
    3.6 km
    in this dpt
  • Cevallos
    Tungurahua · Ecuador
    0.9 km
    in this dpt
  • Tisaleo
    Tungurahua · Ecuador
    0.0 km
    in this dpt

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

Species present

112 distinct species · 395 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Quero : 38 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 64 interactions GloBI sur 5 types (connectance 6.8%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
64
Connectance
0.068
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

13km

Max discharge

8,2m³/s

Max Strahler

3

Segments matched

5

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