Ontologia

Rivière· 31 segments

Henrys Fork

Crosses 4 administrative regions : Daggett, Summit, Sweetwater, Uinta

rivière

Total length

149km

Max discharge

97,4m³/s

Max Strahler

6

Segments matched

31

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805167101506 km²

4 administrative regions crossed (GADM L2)

  • Sweetwater
    Wyoming · United States
    57.1 km
    in this dpt
  • Daggett
    Utah · United States
    47.9 km
    in this dpt
  • Uinta
    Wyoming · United States
    32.4 km
    in this dpt
  • Summit
    Utah · United States
    15.4 km
    in this dpt

1 intersecting protected areas

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

Species present

63 distinct species · 165 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 26 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 Henrys Fork : 21 espèces reliées par 49 interactions GloBI sur 3 types (connectance 13.0%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
28
Interactions affichées
49
Connectance
0.130
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

149km

Max discharge

97,4m³/s

Max Strahler

6

Segments matched

31

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