Ontologia

Ruisseau· 13 segments

Río Culagá

Crosses 2 administrative regions : Labateca, Toledo

ruisseau

Total length

17km

Max discharge

10m³/s

Max Strahler

3

Segments matched

13

River geography2 admin regions · 0 communes

Parent watershed

hybas-6080088770232 km²

2 administrative regions crossed (GADM L2)

  • Labateca
    Norte de Santander · Colombia
    24.3 km
    in this dpt
  • Toledo
    Norte de Santander · Colombia
    16.0 km
    in this dpt

2 intersecting protected areas

  • Mejué

    IUCN VI

    Integrated Management Regional Districts

  • Civil Society Nature Reserve

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

Species present

151 distinct species · 1 020 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Culagá : 30 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 42 interactions GloBI sur 6 types (connectance 5.1%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
42
Connectance
0.051
Patrimoniales
1
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

17km

Max discharge

10,0m³/s

Max Strahler

3

Segments matched

13

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