Ontologia

Ruisseau· 2 segments

Quebrada Cajón

Crosses 3 administrative regions : Buenos Aires, Osa, Pérez Zeledón

ruisseau

Total length

24km

Max discharge

1m³/s

Max Strahler

1

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-70808848101057 km²

3 administrative regions crossed (GADM L2)

  • Pérez Zeledón
    San José · Costa Rica
    7.0 km
    in this dpt
  • Osa
    Puntarenas · Costa Rica
    2.3 km
    in this dpt
  • Buenos Aires
    Puntarenas · Costa Rica
    0.0 km
    in this dpt

1 intersecting protected areas

  • La Amistad

    IUCN Not Applicable

    UNESCO-MAB Biosphere Reserve

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

Species present

132 distinct species · 221 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 Quebrada Cajón : 21 espèces reliées par 26 interactions GloBI sur 4 types (connectance 7.4%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

24km

Max discharge

1,0m³/s

Max Strahler

1

Segments matched

2

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