Ontologia

Ruisseau· 16 segments

Río Chorcha

Crosses 4 administrative regions : Besiko, David, Gualaca, San Lorenzo

ruisseau

Total length

81km

Max discharge

8,4m³/s

Max Strahler

3

Segments matched

16

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080000860963 km²

4 administrative regions crossed (GADM L2)

  • Gualaca
    Chiriquí · Panama
    24.7 km
    in this dpt
  • David
    Chiriquí · Panama
    19.0 km
    in this dpt
  • Besiko
    Ngöbe Buglé · Panama
    18.1 km
    in this dpt
  • San Lorenzo
    Chiriquí · Panama
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

74 distinct species · 217 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

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

81km

Max discharge

8,4m³/s

Max Strahler

3

Segments matched

16

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