Ontologia

Rivière· 11 segments

Río Cocorná

Crosses 4 administrative regions : Cocorná, El Carmen de Viboral, Granada, San Luís

rivière

Total length

43km

Max discharge

16,6m³/s

Max Strahler

4

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-60801023901939 km²

4 administrative regions crossed (GADM L2)

  • Cocorná
    Antioquia · Colombia
    20.2 km
    in this dpt
  • El Carmen de Viboral
    Antioquia · Colombia
    14.7 km
    in this dpt
  • Granada
    Antioquia · Colombia
    1.7 km
    in this dpt
  • San Luís
    Antioquia · Colombia
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

529 distinct species · 8 328 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 23 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 Cocorná : 16 espèces reliées par 29 interactions GloBI sur 5 types (connectance 10.5%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
24
Interactions affichées
29
Connectance
0.105
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

43km

Max discharge

16,6m³/s

Max Strahler

4

Segments matched

11

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