Ontologia

Ruisseau· 2 segments

Arroyo Yukyry

Crosses 4 administrative regions : Caacupé, Eusebio Ayala, Piribebuy, Tobatí

ruisseau

Total length

4km

Max discharge

3,4m³/s

Max Strahler

3

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-60807875601533 km²

4 administrative regions crossed (GADM L2)

  • Eusebio Ayala
    Cordillera · Paraguay
    22.8 km
    in this dpt
  • Piribebuy
    Cordillera · Paraguay
    7.7 km
    in this dpt
  • Caacupé
    Cordillera · Paraguay
    0.0 km
    in this dpt
  • Tobatí
    Cordillera · Paraguay
    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

82 distinct species · 200 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 18 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 Arroyo Yukyry : 17 espèces + 1 bulle famille, 15 interactions GloBI documentées sur 3 types (connectance 9.8%, filtre Serrano α=0.2). Les 1 bulle regroupe des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
18
Interactions affichées
15
Connectance
0.098
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

4km

Max discharge

3,4m³/s

Max Strahler

3

Segments matched

2

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