Ontologia

Rivière· 2 segments

Arroyo Latorre

Crosses 5 administrative regions : Casupá, Fray Marcos, NA, San Ramón, Tala

rivière

Total length

20km

Max discharge

55m³/s

Max Strahler

5

Segments matched

2

River geography5 admin regions · 0 communes

Parent watershed

hybas-60808975702539 km²

5 administrative regions crossed (GADM L2)

  • Fray Marcos
    Florida · Uruguay
    11.7 km
    in this dpt
  • Tala
    Canelones · Uruguay
    8.5 km
    in this dpt
  • Casupá
    Florida · Uruguay
    5.6 km
    in this dpt
  • San Ramón
    Canelones · Uruguay
    4.8 km
    in this dpt
  • NA
    Florida · Uruguay
    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

246 distinct species · 511 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 43 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 Latorre : 35 espèces reliées par 51 interactions GloBI sur 4 types (connectance 5.4%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
51
Connectance
0.054
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

20km

Max discharge

55,0m³/s

Max Strahler

5

Segments matched

2

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