Management actions intended to increase growth and survival of pallid sturgeon (Scaphirhynchus albus) age-0 larvae on the Lower Missouri River require a comprehensive understanding of the geomorphic habitat template of the river. The datasets described here are intended to support decisions relating to where channel-reconfiguration projects should be located to optimize effectiveness of interception rearing complexes (IRCs). The bend-scale geomorphic classification of the Lower Missouri River is intended to help in the design of monitoring and evaluation of IRC projects. The bend-scale classification was based on geomorphic and engineering variables for 257 bends from Sioux City, Iowa to the confluence with the Mississippi River near St. Louis, Missouri. We developed 5 datasets to underlie the classification; these data were aggregated at the bend level and used in k-means clustering to identify groupings of bends that shared the same characteristics. Separate 3-, 4-, and 6-cluster classifications were developed and mapped; the final bend classification dataset is includeed in this data release.
Citation Information
Publication Year | 2017 |
---|---|
Title | Missouri River Bend Classification |
DOI | 10.5066/F7FF3R9D |
Authors | Robert B. Jacobson |
Product Type | Data Release |
Record Source | USGS Digital Object Identifier Catalog |
USGS Organization | Columbia Environmental Research Center |
Related Content
Bend-scale geomorphic classification and assessment of the Lower Missouri River from Sioux City, Iowa, to the Mississippi River for application to pallid sturgeon management
Related Content
- Publications
Bend-scale geomorphic classification and assessment of the Lower Missouri River from Sioux City, Iowa, to the Mississippi River for application to pallid sturgeon management
Management actions intended to increase growth and survival of pallid sturgeon (Scaphirhynchus albus) age-0 larvae on the Lower Missouri River require a comprehensive understanding of the geomorphic habitat template of the river. The study described here had two objectives relating to where channel-reconfiguration projects should be located to optimize effectiveness. The first objective was to dev - Connect