Ontologia

Ruisseau· 17 segments

Río Machuca

Crosses 4 administrative regions : Esparza, Orotina, San Mateo, San Ramón

ruisseau

Total length

74km

Max discharge

7,3m³/s

Max Strahler

3

Segments matched

17

River geography4 admin regions · 0 communes

Parent watershed

hybas-70800014302294 km²

4 administrative regions crossed (GADM L2)

  • San Mateo
    Alajuela · Costa Rica
    21.5 km
    in this dpt
  • Orotina
    Alajuela · Costa Rica
    8.1 km
    in this dpt
  • San Ramón
    Alajuela · Costa Rica
    5.0 km
    in this dpt
  • Esparza
    Puntarenas · Costa Rica
    0.2 km
    in this dpt

2 intersecting protected areas

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

Species present

645 distinct species · 30 482 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 14 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 Machuca : 8 espèces reliées par 14 interactions GloBI sur 2 types (connectance 15.4%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
14
Interactions affichées
14
Connectance
0.154
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

74km

Max discharge

7,3m³/s

Max Strahler

3

Segments matched

17

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