Ontologia

Ruisseau· 20 segments

Sweetwater Creek

Crosses 4 administrative regions : Eagle, Garfield, Wayne

ruisseau

Total length

772km

Max discharge

1,1m³/s

Max Strahler

3

Segments matched

20

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080580860496 km²

4 administrative regions crossed (GADM L2)

  • Garfield
    Utah · United States
    44.5 km
    in this dpt
  • Wayne
    Utah · United States
    31.7 km
    in this dpt
  • Garfield
    Colorado · United States
    16.2 km
    in this dpt
  • Eagle
    Colorado · United States
    10.4 km
    in this dpt

6 intersecting protected areas

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

Species present

134 distinct species · 495 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Sweetwater Creek : 24 espèces reliées par 78 interactions GloBI sur 3 types (connectance 13.1%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
78
Connectance
0.131
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

772km

Max discharge

1,1m³/s

Max Strahler

3

Segments matched

20

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