Ontologia

Ruisseau· 5 segments

Río Changuinola Sur

Crosses 3 administrative regions : Boquete, Changuinola, Kankintú

ruisseau

Total length

16km

Max discharge

4,7m³/s

Max Strahler

3

Segments matched

5

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080884960340 km²

3 administrative regions crossed (GADM L2)

  • Changuinola
    Bocas del Toro · Panama
    13.6 km
    in this dpt
  • Boquete
    Chiriquí · Panama
    0.0 km
    in this dpt
  • Kankintú
    Ngöbe Buglé · Panama
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

306 distinct species · 529 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 Changuinola Sur : 16 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 23 interactions GloBI sur 4 types (connectance 11.0%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
21
Interactions affichées
23
Connectance
0.110
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

16km

Max discharge

4,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.