Ontologia

Rivière· 28 segments

Rio Chuviscar

Crosses 4 administrative regions : Aldama, Aquiles Serdán, Chihuahua, Riva Palacio

rivière

Total length

89km

Max discharge

2,8m³/s

Max Strahler

4

Segments matched

28

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080772240621 km²

4 administrative regions crossed (GADM L2)

  • Chihuahua
    Chihuahua · México
    67.0 km
    in this dpt
  • Aldama
    Chihuahua · México
    56.0 km
    in this dpt
  • Riva Palacio
    Chihuahua · México
    5.3 km
    in this dpt
  • Aquiles Serdán
    Chihuahua · México
    1.5 km
    in this dpt

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

Species present

145 distinct species · 420 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
50
Interactions affichées
108
Connectance
0.088
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

89km

Max discharge

2,8m³/s

Max Strahler

4

Segments matched

28

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