Ontologia

Ruisseau· 2 segments

Río Araute

Crosses 4 administrative regions : El Rosario, Jocoaitique, San Isidro, Torola

ruisseau

Total length

9km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-70808765601475 km²

4 administrative regions crossed (GADM L2)

  • Jocoaitique
    Morazán · El Salvador
    4.1 km
    in this dpt
  • El Rosario
    Morazán · El Salvador
    2.0 km
    in this dpt
  • Torola
    Morazán · El Salvador
    0.8 km
    in this dpt
  • San Isidro
    Morazán · El Salvador
    0.0 km
    in this dpt

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

Species present

161 distinct species · 461 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 Araute : 24 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 38 interactions GloBI sur 4 types (connectance 6.4%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
38
Connectance
0.064
Patrimoniales
1
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

9km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

2

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