Ontologia

Ruisseau· 5 segments

Río Coco

Crosses 1 administrative regions : San Carlos

ruisseau

Total length

871km

Max discharge

9,9m³/s

Max Strahler

3

Segments matched

5

River geography1 admin regions · 0 communes

Parent watershed

hybas-6080101520210 km²

1 administrative regions crossed (GADM L2)

  • San Carlos
    Antioquia · Colombia
    13.3 km
    in this dpt

4 intersecting protected areas

  • Camelias

    IUCN VI

    Integrated Management Regional Districts

  • Playas

    IUCN VI

    Regional Protective Forest Reserves

  • Punchiná

    IUCN VI

    Regional Protective Forest Reserves

  • Civil Society Nature Reserve

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

Species present

554 distinct species · 6 380 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Coco : 27 espèces reliées par 30 interactions GloBI sur 2 types (connectance 6.9%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
30
Connectance
0.069
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

871km

Max discharge

9,9m³/s

Max Strahler

3

Segments matched

5

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