Ontologia

Ruisseau· 6 segments

Quebrada Golondrinas

Crosses 3 administrative regions : Argelia, El Cairo, Versalles

ruisseau

Total length

15km

Max discharge

2,5m³/s

Max Strahler

3

Segments matched

6

River geography3 admin regions · 0 communes

Parent watershed

hybas-60801290901088 km²

3 administrative regions crossed (GADM L2)

  • El Cairo
    Valle del Cauca · Colombia
    9.4 km
    in this dpt
  • Versalles
    Valle del Cauca · Colombia
    5.1 km
    in this dpt
  • Argelia
    Valle del Cauca · Colombia
    0.0 km
    in this dpt

14 intersecting protected areas

5 more protected areas

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

Species present

151 distinct species · 605 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 16 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 Quebrada Golondrinas : 14 espèces reliées par 10 interactions GloBI sur 4 types (connectance 8.3%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
16
Interactions affichées
10
Connectance
0.083
Patrimoniales
0
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

15km

Max discharge

2,5m³/s

Max Strahler

3

Segments matched

6

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