Ontologia

Rivière· 9 segments

Rio Potosí

Crosses 5 administrative regions : Galeana, Iturbide, Linares, Montemorelos, Rayones

rivière

Total length

20km

Max discharge

1m³/s

Max Strahler

4

Segments matched

9

River geography5 admin regions · 0 communes

Parent watershed

hybas-70808050501522 km²

5 administrative regions crossed (GADM L2)

  • Galeana
    Nuevo León · México
    14.4 km
    in this dpt
  • Rayones
    Nuevo León · México
    6.1 km
    in this dpt
  • Iturbide
    Nuevo León · México
    5.8 km
    in this dpt
  • Linares
    Nuevo León · México
    5.0 km
    in this dpt
  • Montemorelos
    Nuevo León · México
    3.6 km
    in this dpt

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

Species present

108 distinct species · 146 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 20 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 Rio Potosí : 17 espèces reliées par 16 interactions GloBI sur 2 types (connectance 8.4%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
20
Interactions affichées
16
Connectance
0.084
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

1,0m³/s

Max Strahler

4

Segments matched

9

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