Ontologia

Rivière· 11 segments

Río Acarigua

Crosses 4 administrative regions : Andrés Eloy Blanco, Araure, Esteller, Ospino

rivière

Total length

49km

Max discharge

21,5m³/s

Max Strahler

4

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-60800696702071 km²

4 administrative regions crossed (GADM L2)

  • Esteller
    Portuguesa · Venezuela
    35.0 km
    in this dpt
  • Araure
    Portuguesa · Venezuela
    32.8 km
    in this dpt
  • Andrés Eloy Blanco
    Lara · Venezuela
    8.9 km
    in this dpt
  • Ospino
    Portuguesa · Venezuela
    0.0 km
    in this dpt

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

Species present

53 distinct species · 62 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 Acarigua : 19 espèces reliées par 20 interactions GloBI sur 3 types (connectance 9.5%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

49km

Max discharge

21,5m³/s

Max Strahler

4

Segments matched

11

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