<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Thomas R. Batt</dc:contributor>
  <dc:creator>James R. Hatten</dc:creator>
  <dc:date>2010</dc:date>
  <dc:description>&lt;p&gt;&lt;span&gt;We used a two-dimensional (2D) hydrodynamic model to simulate and compare the hydraulic characteristics in a 74-km reach of the Columbia River (the Bonneville Reach) before and after construction of Bonneville Dam. For hydrodynamic modeling, we created a bathymetric layer of the Bonneville Reach from single-beam and multi-beam echo-sounder surveys, digital elevation models, and navigation surveys. We calibrated the hydrodynamic model at 100 and 300 kcfs with a user-defined roughness layer, a variable-sized mesh, and a U.S. Army Corps of Engineers backwater curve. We verified the 2D model with acoustic Doppler current profiler (ADCP) data at 14 transects and three flows. The 2D model was 88% accurate for water depths, and 77% accurate for velocities. We verified a pre-dam 2D model run at 126 kcfs using pre-dam aerial photos from September 1935. Hydraulic simulations indicated that mean water depths in the Bonneville Reach increased by 34% following dam construction, while mean velocities decreased by 58%. There are numerous activities that would benefit from data output from the 2D model, including biological sampling, bioenergetics, and spatially explicit habitat modeling.&lt;/span&gt;&lt;/p&gt;</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:identifier>10.3955/046.084.0301</dc:identifier>
  <dc:language>en</dc:language>
  <dc:publisher>Northwest Scientific Association</dc:publisher>
  <dc:title>Hydraulic alterations resulting from hydropower development in the Bonneville Reach of the Columbia River</dc:title>
  <dc:type>article</dc:type>
</oai_dc:dc>