Ontologia

Ruisseau· 7 segments

Milk Creek

Crosses 5 administrative regions : Coconino, Delta, Duchesne, Garfield, Grand

ruisseau

Total length

235km

Max discharge

0,1m³/s

Max Strahler

2

Segments matched

7

River geography5 admin regions · 0 communes

Parent watershed

hybas-70806009002346 km²

5 administrative regions crossed (GADM L2)

  • Duchesne
    Utah · United States
    6.5 km
    in this dpt
  • Garfield
    Utah · United States
    5.9 km
    in this dpt
  • Coconino
    Arizona · United States
    5.7 km
    in this dpt
  • Grand
    Colorado · United States
    3.5 km
    in this dpt
  • Delta
    Colorado · United States
    0.9 km
    in this dpt

7 intersecting protected areas

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

Species present

13 distinct species · 15 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 2 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 Milk Creek : 2 espèces reliées par 1 interaction GloBI sur 1 type (connectance 100.0%, filtre Serrano α=0.2).

Espèces affichées
2
Interactions affichées
1
Connectance
1.000
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

235km

Max discharge

0,1m³/s

Max Strahler

2

Segments matched

7

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