Ontologia

Ruisseau· 7 segments

Río Negro

Crosses 4 administrative regions : Abangares, Bagaces, Tilarán, Upala

ruisseau

Total length

7 781km

Max discharge

2,3m³/s

Max Strahler

2

Segments matched

7

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080882950243 km²

4 administrative regions crossed (GADM L2)

  • Upala
    Alajuela · Costa Rica
    12.4 km
    in this dpt
  • Tilarán
    Guanacaste · Costa Rica
    10.5 km
    in this dpt
  • Bagaces
    Guanacaste · Costa Rica
    1.5 km
    in this dpt
  • Abangares
    Guanacaste · Costa Rica
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

778 distinct species · 3 723 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
33
Interactions affichées
37
Connectance
0.070
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

7 781km

Max discharge

2,3m³/s

Max Strahler

2

Segments matched

7

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