Ontologia

Ruisseau· 13 segments

Río Ayampe

Crosses 4 administrative regions : Jipijapa, Paján, Puerto López, Santa Elena

ruisseau

Total length

81km

Max discharge

5,5m³/s

Max Strahler

3

Segments matched

13

River geography4 admin regions · 0 communes

Parent watershed

hybas-6080032840548 km²

4 administrative regions crossed (GADM L2)

  • Jipijapa
    Manabi · Ecuador
    33.3 km
    in this dpt
  • Santa Elena
    Santa Elena · Ecuador
    18.0 km
    in this dpt
  • Puerto López
    Manabi · Ecuador
    16.6 km
    in this dpt
  • Paján
    Manabi · Ecuador
    0.9 km
    in this dpt

1 intersecting protected areas

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

Species present

147 distinct species · 394 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 22 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 Ayampe : 18 espèces reliées par 24 interactions GloBI sur 3 types (connectance 10.4%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
22
Interactions affichées
24
Connectance
0.104
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

81km

Max discharge

5,5m³/s

Max Strahler

3

Segments matched

13

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