Ontologia

Fleuve· 8 segments

Butler Wash

Crosses 5 administrative regions : Emery, Garfield, Grand, San Juan, Wayne

fleuve

Total length

104km

Max discharge

207,8m³/s

Max Strahler

7

Segments matched

8

River geography5 admin regions · 0 communes

Parent watershed

hybas-70805920801893 km²

5 administrative regions crossed (GADM L2)

  • San Juan
    Utah · United States
    58.6 km
    in this dpt
  • Garfield
    Utah · United States
    13.3 km
    in this dpt
  • Grand
    Utah · United States
    7.6 km
    in this dpt
  • Emery
    Utah · United States
    2.4 km
    in this dpt
  • Wayne
    Utah · United States
    0.0 km
    in this dpt

6 intersecting protected areas

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

Species present

18 distinct species · 37 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 5 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 Butler Wash : 5 espèces reliées par 3 interactions GloBI sur 2 types (connectance 30.0%, filtre Serrano α=0.2).

Espèces affichées
5
Interactions affichées
3
Connectance
0.300
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

104km

Max discharge

207,8m³/s

Max Strahler

7

Segments matched

8

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