Ontologia

Ruisseau· 5 segments

Quebrada El Venado

Crosses 4 administrative regions : Angostura, Neiva, San Francisco, Valdivia

ruisseau

Total length

169km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-60801501601568 km²

4 administrative regions crossed (GADM L2)

  • Neiva
    Huila · Colombia
    10.4 km
    in this dpt
  • San Francisco
    Antioquia · Colombia
    3.7 km
    in this dpt
  • Valdivia
    Antioquia · Colombia
    2.1 km
    in this dpt
  • Angostura
    Antioquia · Colombia
    1.2 km
    in this dpt

3 intersecting protected areas

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

Species present

294 distinct species · 3 339 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 Quebrada El Venado : 19 espèces reliées par 18 interactions GloBI sur 3 types (connectance 8.6%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

169km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

5

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