Ontologia

Ruisseau

Río Uriangato

Crosses 4 administrative regions : Huandacareo, Moroleón, Uriangato, Yuriria

ruisseau

Total length

0km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography4 admin regions · 0 communes

Parent watershed

hybas-70808333801185 km²

4 administrative regions crossed (GADM L2)

  • Moroleón
    Guanajuato · México
    17.0 km
    in this dpt
  • Uriangato
    Guanajuato · México
    3.1 km
    in this dpt
  • Yuriria
    Guanajuato · México
    0.0 km
    in this dpt
  • Huandacareo
    Michoacán · México
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

89 distinct species · 151 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Uriangato : 35 espèces reliées par 49 interactions GloBI sur 3 types (connectance 6.3%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
49
Connectance
0.063
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

0km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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