Ontologia

Ruisseau· 5 segments

Quebrada El Oro

Crosses 4 administrative regions : Briceño, Sabanalarga, Toledo, Valdivia

ruisseau

Total length

96km

Max discharge

6,7m³/s

Max Strahler

3

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-60800852901781 km²

4 administrative regions crossed (GADM L2)

  • Valdivia
    Antioquia · Colombia
    21.7 km
    in this dpt
  • Sabanalarga
    Antioquia · Colombia
    6.5 km
    in this dpt
  • Toledo
    Antioquia · Colombia
    1.7 km
    in this dpt
  • Briceño
    Antioquia · Colombia
    0.2 km
    in this dpt

1 intersecting protected areas

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

Species present

112 distinct species · 188 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 22 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 Oro : 17 espèces reliées par 19 interactions GloBI sur 3 types (connectance 8.2%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
22
Interactions affichées
19
Connectance
0.082
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

96km

Max discharge

6,7m³/s

Max Strahler

3

Segments matched

5

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