Rivière· 12 segments
Hazel Creek
Crosses 5 administrative regions : Chippewa, Graham, Swain, Washington, Yellow Medicine
Total length
250km
Max discharge
120,7m³/s
Max Strahler
5
Segments matched
12
River geography5 admin regions · 0 communes
5 administrative regions crossed (GADM L2)
- Yellow MedicineMinnesota · United States43.2 kmin this dpt
- SwainNorth Carolina · United States20.7 kmin this dpt
- WashingtonMissouri · United States14.7 kmin this dpt
- ChippewaMinnesota · United States0.2 kmin this dpt
- GrahamNorth Carolina · United States0.0 kmin this dpt
10 intersecting protected areas
Great Smoky Mountains
IUCN IINational Park
Great Smoky Mountains National Park
IUCN Not ApplicableWorld Heritage Site (natural or mixed)
Martin County
IUCN VWaterfowl Production Area
Reserve Program
Reserve Program
Tyro
IUCN VState Wildlife Management Area
Natural Area
Reserve Program
Stokke
IUCN VState Wildlife Management Area
1 more protected areassorted by area
Flowage
IUCN VEasement
1 page = 1 named river (aggregation of 12 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
5 distinct species · 5 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 3 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).
Indicateurs du tissu écologique
Tissu écologique de Hazel Creek : 3 espèces reliées par 2 interactions GloBI sur 1 type (connectance 66.7%, filtre Serrano α=0.2).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
250km
Max discharge
120,7m³/s
Max Strahler
5
Segments matched
12
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.