Ontologia

Rivière· 13 segments

Arroyo Pan de Azúcar

Crosses 4 administrative regions : NA, Pan de Azúcar, Piriápolis, San Carlos

rivière

Total length

63km

Max discharge

10,9m³/s

Max Strahler

4

Segments matched

13

River geography4 admin regions · 0 communes

Parent watershed

hybas-6080016210941 km²

4 administrative regions crossed (GADM L2)

  • Pan de Azúcar
    Maldonado · Uruguay
    50.3 km
    in this dpt
  • San Carlos
    Maldonado · Uruguay
    0.5 km
    in this dpt
  • NA
    Lavalleja · Uruguay
    0.0 km
    in this dpt
  • Piriápolis
    Maldonado · Uruguay
    0.0 km
    in this dpt

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

Species present

101 distinct species · 287 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Pan de Azúcar : 33 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 31 interactions GloBI sur 3 types (connectance 5.2%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
31
Connectance
0.052
Patrimoniales
2
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

63km

Max discharge

10,9m³/s

Max Strahler

4

Segments matched

13

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