Ruisseau· 6 segments
Dunn Creek
Crosses 4 administrative regions : Cocke, Division No. 3, Henderson, Sevier
Total length
211km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
6
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- Division No. 3Saskatchewan · Canada32.2 kmin this dpt
- HendersonNorth Carolina · United States2.9 kmin this dpt
- SevierTennessee · United States0.7 kmin this dpt
- CockeTennessee · United States0.4 kmin this dpt
7 intersecting protected areas
Wildlife Habitat Protection
IUCN Not ApplicableWildlife Habitat Protection
Private Conservation Lands
IUCN IVPrivate Conservation Lands
Great Smoky Mountains
IUCN IINational Park
Great Smoky Mountains National Park
IUCN Not ApplicableWorld Heritage Site (natural or mixed)
Mankota
IUCN VIProvincial Pasture
Watershed Protection
Bat Fork Bog Plant
IUCN VConservation Preserve
1 page = 1 named river (aggregation of 6 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
267 distinct species · 2 197 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 42 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 Dunn Creek : 26 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 131 interactions GloBI sur 4 types (connectance 15.2%, filtre Serrano α=0.2). 16 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
211km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
6
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.