Ontologia

Rivière· 60 segments

Río Margua

Crosses 4 administrative regions : Cubará, Labateca, Pamplona, Toledo

rivière

Total length

69km

Max discharge

140,5m³/s

Max Strahler

5

Segments matched

60

River geography4 admin regions · 0 communes

Parent watershed

hybas-6080091420696 km²

4 administrative regions crossed (GADM L2)

  • Toledo
    Norte de Santander · Colombia
    105.7 km
    in this dpt
  • Labateca
    Norte de Santander · Colombia
    20.9 km
    in this dpt
  • Pamplona
    Norte de Santander · Colombia
    0.5 km
    in this dpt
  • Cubará
    Boyacá · Colombia
    0.0 km
    in this dpt

1 intersecting protected areas

  • Tamá

    IUCN II

    National Natural Park

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

Species present

83 distinct species · 201 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 13 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 Margua : 13 espèces reliées par 9 interactions GloBI sur 2 types (connectance 11.5%, filtre Serrano α=0.2).

Espèces affichées
13
Interactions affichées
9
Connectance
0.115
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

69km

Max discharge

140,5m³/s

Max Strahler

5

Segments matched

60

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