Ontologia

Rivière· 36 segments

Beaver Dam Wash

Crosses 3 administrative regions : Lincoln, Mohave, Washington

rivière

Total length

91km

Max discharge

2,5m³/s

Max Strahler

4

Segments matched

36

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806149701521 km²

3 administrative regions crossed (GADM L2)

  • Washington
    Utah · United States
    132.6 km
    in this dpt
  • Mohave
    Arizona · United States
    19.6 km
    in this dpt
  • Lincoln
    Nevada · United States
    13.4 km
    in this dpt

5 intersecting protected areas

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

Species present

139 distinct species · 288 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 46 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 Beaver Dam Wash : 36 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 88 interactions GloBI sur 4 types (connectance 8.5%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
46
Interactions affichées
88
Connectance
0.085
Patrimoniales
1
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

91km

Max discharge

2,5m³/s

Max Strahler

4

Segments matched

36

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