Ruisseau· 31 segments
Clay Creek
Crosses 6 administrative regions : Clay, Cocke, Hutchinson, Prowers, Turner +1
Total length
277km
Max discharge
2m³/s
Max Strahler
3
Segments matched
31
River geography6 admin regions · 0 communes
6 administrative regions crossed (GADM L2)
- YanktonSouth Dakota · United States49.2 kmin this dpt
- ProwersColorado · United States44.2 kmin this dpt
- CockeTennessee · United States10.5 kmin this dpt
- HutchinsonSouth Dakota · United States10.2 kmin this dpt
- ClaySouth Dakota · United States8.3 kmin this dpt
- TurnerSouth Dakota · United States2.4 kmin this dpt
7 intersecting protected areas
Rankin Bottom
IUCN VWildlife Management Area
Reserve Program
Wetlands Reserve Program (WRP)
IUCN Not AssignedReserve Program
Yankton County
IUCN VWaterfowl Production Area
Marindahl
IUCN VLake
Volin Clay
IUCN VState Wildlife Management Area
Yankton County
IUCN VIWaterfowl Production Area
1 page = 1 named river (aggregation of 31 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
47 distinct species · 523 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 21 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 Clay Creek : 16 espèces reliées par 29 interactions GloBI sur 3 types (connectance 13.8%, filtre Serrano α=0.2). 5 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
277km
Max discharge
2,0m³/s
Max Strahler
3
Segments matched
31
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.