<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book SYSTEM "BITS-book2.dtd">
<book xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" dtd-version="2.0" xml:lang="EN">
<collection-meta collection-type="series"><title-group>
<title>U.S. Geological Survey Scientific Investigations Report</title>
<alt-title alt-title-type="pub-short-title">Scientific Investigations Report</alt-title>
<alt-title alt-title-type="pub-acronym-title">SIR</alt-title>
</title-group><contrib-group content-type="secretary-director"><contrib><string-name><given-names>DAVID</given-names><surname>BERNHARDT</surname></string-name><aff><institution>U.S. Department of the Interior</institution></aff><role>Secretary</role></contrib><contrib><string-name><given-names>James F.</given-names><surname>Reilly</surname><suffix>II</suffix></string-name><aff><institution>U.S. Geological Survey</institution></aff><role>Director</role></contrib></contrib-group><issn publication-format="print">2328-031X</issn><issn publication-format="online">2328-0328</issn></collection-meta>
<book-meta><book-id book-id-type="publisher-id">2021-5098</book-id><book-id book-id-type="doi">10.3133/sir20215098</book-id><book-title-group>
<book-title>Bathymetric and Velocimetric Surveys at Highway Bridges Crossing the Missouri River near Kansas City, Missouri, August 2019, August 2020, and October 2020</book-title>
<alt-title alt-title-type="sentence-case">Bathymetric and velocimetric surveys at highway bridges crossing the Missouri River near Kansas City, Missouri, August 2019, August 2020, and October 2020</alt-title>
<alt-title alt-title-type="running-head">Bathymetric and Velocimetric Surveys at Highway Bridges, Missouri River near Kansas City</alt-title>
</book-title-group><contrib-group content-type="collaborator">
<contrib>
<collab>Prepared in cooperation with the Missouri Department of Transportation and Clarkson Construction</collab>
</contrib>
</contrib-group><contrib-group content-type="authors">
<contrib contrib-type="author"><string-name><x>By</x><x> </x><given-names>Richard J.</given-names><x> </x><surname>Huizinga</surname></string-name></contrib>
</contrib-group><pub-date date-type="pub"><year>2021</year></pub-date><book-volume-number/><publisher>
<publisher-name>U.S. Geological Survey</publisher-name>
<publisher-loc>Reston, Virginia</publisher-loc>
</publisher><edition/><abstract>
<title>Abstract</title>
<p>Bathymetric and velocimetric data were collected by the U.S.&#x00A0;Geological Survey, in cooperation with the Missouri Department of Transportation, near 9&#x00A0;bridges at 8&#x00A0;highway crossings of the Missouri River near Kansas City, Missouri, on August 13&#x2013;14, 2019. A multibeam echosounder mapping system was used to obtain channel-bed elevations for river reaches about 1,550 to 1,660&#x00A0;feet longitudinally and generally extending laterally across the active channel from bank to bank during moderate flood-flow conditions. These surveys indicated the channel conditions at the time of the surveys and provided characteristics of scour holes that may be useful in developing predictive guidelines or equations for scour holes. These data also may be useful to the Missouri Department of Transportation as a low to moderate flood-flow assessment of the bridges for stability and integrity issues with respect to bridge scour during floods.</p>
<p>Bathymetric data were collected around every pier that was in water, except around the nose of one pier that was surrounded by a persistent debris raft. Scour holes were present at most piers for which bathymetry could be obtained, except those on banks or surrounded by riprap. The observed scour holes at the surveyed bridges generally were examined with respect to shape and depth.</p>
<p>Comparisons between bathymetric surfaces from previous surveys and this study do not indicate any consistent correlation in channel-bed elevations with streamflow conditions at the times of the surveys. The predominant overall scour observed between the various surveys implies the channel bed in the 2019 surveys might have been rebounding from more substantial scour caused by the high streamflow earlier in March and June 2019, which was the highest streamflow since 1993. Pier size and nose shape had a substantial effect on the size of the scour hole observed at a given pier. Many of the piers at the Kansas City area bridges have wide or blunt noses caused by exposed footings, seal courses, or caissons, which resulted in large, deep scour holes at most piers. Several of the structures had piers that were skewed to primary approach flow; and, at most of the structures, the scour hole was deeper and longer on the side of the pier with impinging flow than the leeward side, with some amount of deposition on the leeward side, as typically has been observed at piers skewed to approach flow.</p>
<p>Limited additional bathymetric data were collected by the U.S.&#x00A0;Geological Survey, in cooperation with Clarkson Construction, near the main channel piers of the U.S.&#x00A0;Highway 169 (Broadway) and the Interstate 435 (Randolph) bridges on August 17 and October 23, 2020, to determine the channel-bed conditions before and after installation of scour countermeasures near those piers. Survey results from before and after installation of these countermeasures show these features had a substantial effect on mitigating the observed scour at these piers, particularly when compared to piers at other sites without such features.</p>
</abstract><custom-meta-group>
<custom-meta><meta-name>Online Only</meta-name><meta-value>True</meta-value></custom-meta>
</custom-meta-group><notes notes-type="further-information"><p>For more information on the USGS&#x2014;the Federal source for science about the Earth, its natural and living resources, natural hazards, and the environment&#x2014;visit <ext-link>https://www.usgs.gov</ext-link> or call 1&#x2013;888&#x2013;ASK&#x2013;USGS.</p></notes><notes notes-type="overview"><p>For an overview of USGS information products, including maps, imagery, and publications, visit <ext-link>https://store.usgs.gov/</ext-link>.</p></notes><notes notes-type="disclaimer"><p>Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</p></notes><notes notes-type="permissions"><p>Although this information product, for the most part, is in the public domain, it also may contain copyrighted materials as noted in the text. Permission to reproduce copyrighted items must be secured from the copyright owner.</p></notes></book-meta>
<front-matter>
<ack>
<title>Acknowledgments</title>
<p>The author would like to acknowledge Dennis Heckmann (retired), Bryan Hartnagel, and Jennifer Harper at the Missouri Department of Transportation for their role in funding and supporting the work of the project detailed in this report. The author also would like to acknowledge Jonathan Baker and Damon Johnson at Clarkson Construction for their role in requesting and funding the special surveys at structure A4649 on U.S.&#x00A0;Highway 169 and structure A0767 on Interstate 435 to document the installation of the scour countermeasures there.</p>
<p>The author also wishes to gratefully acknowledge the assistance of several current and former colleagues at the U.S.&#x00A0;Geological Survey Central Midwest Water Science Center for their assistance in collecting and processing the data for this project. Jarrett T. Ellis (former employee) was instrumental in collecting and initial processing of the data from the August 2019 surveys. Benjamin C. Rivers was instrumental in collecting the data from the two special surveys near the main channel piers of the Broadway and Randolph bridges in August and October 2020.</p>
</ack>
<front-matter-part book-part-type="Conversion-Factors">
<book-part-meta>
<title-group>
<title>Conversion Factors</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<table-wrap id="ta" position="float">
<caption>
<title>U.S. customary units to International System of Units</title>
</caption>
<table rules="groups">
<col width="38.91%"/>
<col width="28.67%"/>
<col width="32.42%"/>
<thead>
<tr>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">Multiply</td>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">By</td>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">To obtain</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt" scope="col">Length</th>
</tr>
<tr>
<td valign="top" align="left" scope="row">foot (ft)</td>
<td valign="top" align="char" char=".">0.3048</td>
<td valign="top" align="left">meter (m)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.75pt" scope="row">mile (mi)</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.75pt">1.609</td>
<td valign="top" align="left" style="border-bottom: solid 0.75pt">kilometer (km)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-bottom: solid 0.75pt" scope="col">Volume</th>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.75pt" scope="row">cubic yard (yd<sup>3</sup>)</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.75pt">0.7646</td>
<td valign="top" align="left" style="border-bottom: solid 0.75pt">cubic meter (m<sup>3</sup>)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt" scope="col">Flow rate</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.75pt" scope="row">foot per second (ft/s)</td>
<td valign="top" align="char" char="." style="border-top: solid 0.75pt">0.3048</td>
<td valign="top" align="left" style="border-top: solid 0.75pt">meter per second (m/s)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">cubic foot per second (ft<sup>3</sup>/s)</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.02832</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">cubic meter per second (m<sup>3</sup>/s)</td>
</tr>
</tbody></table></table-wrap>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Datum">
<book-part-meta>
<title-group>
<title>Datum</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>Vertical coordinate information is referenced to the North American Vertical Datum of 1988 (NAVD&#x00A0;88).</p>
<p>Horizontal coordinate information is referenced to the North American Datum of 1983 (NAD&#x00A0;83).</p>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Supplemental-Information">
<book-part-meta>
<title-group>
<title>Supplemental Information</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>In this report, the words &#x201C;left&#x201D; and &#x201C;right&#x201D; refer to directions that would be reported by an observer facing downstream.</p>
<p>Distance on the Missouri River is given in river miles (RMs) upstream from river mile&#x00A0;0 at the confluence with the Mississippi River at St. Louis, Missouri, at river mile&#x00A0;195.2 of the Upper Mississippi River.</p>
<p>Frequency is given in kilohertz (kHz).</p>
<p>Data were collected, processed, and output in the International System of Units, and converted to U.S.&#x00A0;customary units for presentation in the report at the request and for the convenience of the cooperator.</p>
</named-book-part-body>
</front-matter-part>
<glossary content-type="Abbreviations">
<title>Abbreviations</title>
<def-list>
<def-item><term>ADCP</term><def><p>acoustic Doppler current profiler</p></def></def-item>
<def-item><term>CUBE</term><def><p>Combined Uncertainty and Bathymetry Estimator</p></def></def-item>
<def-item><term>DEM</term><def><p>digital elevation model</p></def></def-item>
<def-item><term>DoD</term><def><p>digital elevation model of difference</p></def></def-item>
<def-item><term>GCD</term><def><p>Geomorphic Change Detection</p></def></def-item>
<def-item><term>GNSS</term><def><p>Global Navigation Satellite System</p></def></def-item>
<def-item><term>IHO</term><def><p>International Hydrographic Organization</p></def></def-item>
<def-item><term>IMU</term><def><p>inertial measurement unit</p></def></def-item>
<def-item><term>INS</term><def><p>inertial navigation system</p></def></def-item>
<def-item><term>MBES</term><def><p>multibeam echosounder</p></def></def-item>
<def-item><term>MBMS</term><def><p>multibeam echosounder mapping system</p></def></def-item>
<def-item><term>MMS</term><def><p>Mobile Mapping Suite</p></def></def-item>
<def-item><term>MoDOT</term><def><p>Missouri Department of Transportation</p></def></def-item>
<def-item><term>POS MV</term><def><p>Position Orientation Solution for Marine Vessels</p></def></def-item>
<def-item><term>RM</term><def><p>river mile</p></def></def-item>
<def-item><term>RTK</term><def><p>real-time kinematic</p></def></def-item>
<def-item><term>SBET</term><def><p>smoothed best estimate of trajectory</p></def></def-item>
<def-item><term>sonar</term><def><p>sound navigation and ranging</p></def></def-item>
<def-item><term>TIN</term><def><p>triangulated irregular network</p></def></def-item>
<def-item><term>USGS</term><def><p>U.S. Geological Survey</p></def></def-item>
</def-list>
</glossary>
</front-matter>
<book-body>
<book-part>
<body>
<sec>
<title>Introduction</title>
<p>Scour in alluvial channels is the removal of channel-bed and bank material by flowing water and is the leading cause of bridge failures in the United States (<xref ref-type="bibr" rid="r2">Arneson and others, 2012</xref>). Scour at a bridge site is caused by short- and long-term geomorphic processes and the local effects from elements of the structure in or next to the waterway (<xref ref-type="bibr" rid="r2">Arneson and others, 2012</xref>; <xref ref-type="bibr" rid="r25">Huizinga and Rydlund, 2004</xref>). Because the effects of scour can be severe and dangerous, bridges and other structures over waterways are routinely assessed and inspected. Scour processes can be exacerbated during high-flow conditions because velocity and depth typically increase with increasing streamflow.</p>
<p>The Missouri Department of Transportation (MoDOT) is responsible for most of the transportation infrastructure in the State. A part of this responsibility is fulfilled through periodic inspections of highway structures, including bridges that span waterways. At most of these structures, all or most of the structure can be fully inspected from land or from personnel lift trucks deployed from the roadway of the structure; however, for structures over primary waterways, such as the Missouri and Mississippi Rivers, inspecting the underwater part of the bridge requires a different approach.</p>
<p>The U.S.&#x00A0;Geological Survey (USGS), in cooperation with MoDOT, began assessing scour at selected waterway crossings in Missouri in 1988 (<xref ref-type="bibr" rid="r3">Becker, 1994</xref>) and at waterway crossings throughout the State in 1991 (<xref ref-type="bibr" rid="r25">Huizinga and Rydlund, 2004</xref>). In 2007, the USGS, in cooperation with MoDOT, began determining channel bathymetry and monitoring for scour at bridges using single-beam echosounders and a multibeam echosounder mapping system (MBMS; <xref ref-type="bibr" rid="r32">Rydlund, 2009</xref>; <xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r17">b</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r19">b</xref>, <xref ref-type="bibr" rid="r20">c</xref>, <xref ref-type="bibr" rid="r21">d</xref>, <xref ref-type="bibr" rid="r22">e</xref>; <xref ref-type="bibr" rid="r24">Huizinga and others, 2010</xref>). The MBMS has been a useful tool not only in determining channel bathymetry but also in providing a medium- to high-resolution representation of bridge structural elements below the water line. In March 2010, 9&#x00A0;highway bridges at 7&#x00A0;crossings over the Missouri River near Kansas City, Missouri, were assessed using the MBMS (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>). In October 2010, 12&#x00A0;highway bridges at 7&#x00A0;crossings over the Missouri and Mississippi Rivers near St. Louis, Mo., were assessed (<xref ref-type="bibr" rid="r10">Huizinga, 2011</xref>). During high-flow conditions in June&#x2013;August 2011, many of the highway bridges and several of the railroad bridges along the entirety of the Missouri River downstream from Montana were assessed (<xref ref-type="bibr" rid="r5">Densmore and others, 2013</xref>; <xref ref-type="bibr" rid="r6">Dietsch and others, 2014</xref>), including the 37&#x00A0;highway bridges (at 28&#x00A0;crossings) over the Missouri River in and into Missouri (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>). In April and May 2013, 10&#x00A0;highway bridges at 9&#x00A0;crossings over the Missouri River between Kansas City and St. Louis, Mo., were assessed as part of more routine, nonflood surveys at bridge sites in and into Missouri (<xref ref-type="bibr" rid="r13">Huizinga, 2014</xref>). In June 2014, 8&#x00A0;highway bridges at 7&#x00A0;crossings over the Missouri and Mississippi Rivers on the periphery of Missouri also were assessed as part of routine, nonflood surveys at bridge sites (<xref ref-type="bibr" rid="r14">Huizinga, 2015</xref>). A second round of routine, nonflood surveys at the highway bridges across the Missouri and Mississippi Rivers throughout Missouri began in 2015; the Kansas City area bridge surveys were completed in June 2015 (<xref ref-type="bibr" rid="r15">Huizinga, 2016</xref>, <xref ref-type="bibr" rid="r19">2020b</xref>), the St. Louis area bridge surveys were completed in May 2016 (<xref ref-type="bibr" rid="r16">Huizinga, 2017a</xref>, <xref ref-type="bibr" rid="r17">b</xref>), the bridge surveys between Kansas City and St. Louis were completed in May 2017 (<xref ref-type="bibr" rid="r18">Huizinga, 2020a</xref>, <xref ref-type="bibr" rid="r20">c</xref>), and the bridge surveys on the periphery of Missouri were completed in July&#x2013;August 2018 (<xref ref-type="bibr" rid="r21">Huizinga, 2020d, e</xref><xref ref-type="bibr" rid="r22"/>).</p>
<p>A third round of routine, nonflood surveys at the highway bridges across the Missouri and Mississippi Rivers throughout Missouri began in 2019. The study detailed in this report covers the surveys at the highway bridges across the Missouri River in the Kansas City area (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) and includes 9&#x00A0;bridges at 8&#x00A0;crossings (<xref ref-type="table" rid="t01">table&#x00A0;1</xref>). This report also provides details about two additional, limited surveys, completed in cooperation with Clarkson Construction, near the main channel pier of two sites in August and October 2020 before and after installation of scour countermeasures near these piers.</p>
<table-wrap id="t01" orientation="landscape" position="float">
<label>Table 1</label><caption><title>Highway bridges crossing the Missouri River in and into Missouri in the Kansas City area, in downstream order.</title>
<p content-type="toc"><bold>Table 1.</bold>&#x2003;Highway bridges crossing the Missouri River in and into Missouri in the Kansas City area, in downstream order.</p>
<p>[KDOT, Kansas Department of Transportation; Mo., Missouri; IS, Interstate highway; S, southbound; Kans., Kansas; N, northbound; MoDOT, Missouri Department of Transportation; --, not known/applicable; US, U.S. highway; MO, Missouri State highway]</p>
</caption>
<table rules="groups">
<col width="6.03%"/>
<col width="7.97%"/>
<col width="11.03%"/>
<col width="10.19%"/>
<col width="12.15%"/>
<col width="8.86%"/>
<col width="6.29%"/>
<col width="7.75%"/>
<col width="17.84%"/>
<col width="11.89%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Site number (<xref ref-type="fig" rid="fig01">fig. 1</xref>)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Primary agency</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Structure number</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Local name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">County, State</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Route</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">River mile<sup>a</sup></td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Surveyed as part of this study</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Remarks</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Figures</td>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt" scope="row"><sup>b</sup>5</td>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt">KDOT</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">435-105-11.97 (235)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Parkville</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Platte, Mo.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">IS 435 S</td>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt">383.4</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">No</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Dual bridge crossing with 435-105-11.98 (240)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Not shown</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">435-105-11.98 (240)</td>
<td valign="top" align="left">Parkville</td>
<td valign="top" align="left">Wyandotte, Kans.</td>
<td valign="top" align="left">IS 435 N</td>
<td valign="top" colspan="1" align="left">No</td>
<td valign="top" align="left">Dual bridge crossing with 435-105-11.97 (235)</td>
<td valign="top" align="left">Not shown</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">6</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">MoDOT</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A1800</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Riverside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Platte, Mo.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">IS 635</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">374.1</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Yes</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">1, 6&#x2013;12, 1.1</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">7</td>
<td valign="top" align="left">MoDOT</td>
<td valign="top" align="left">A8340</td>
<td valign="top" align="left">Fairfax</td>
<td valign="top" align="left">Platte, Mo.</td>
<td valign="top" align="left">US 69</td>
<td valign="top" align="left">372.6</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="left">Replaced K0456/A0450 in 2016</td>
<td valign="top" align="left">1, 13&#x2013;19, 1.2</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">8</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">MoDOT</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A4649</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Buck O&#x2019;Neil</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Clay, Mo.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">US 169</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">366.2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Yes</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">1, 20&#x2013;30, 1.3&#x2013;1.4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">9</td>
<td valign="top" align="left">MoDOT</td>
<td valign="top" align="left">A4060</td>
<td valign="top" align="left">Heart of America</td>
<td valign="top" align="left">Clay, Mo.</td>
<td valign="top" align="left">MO 9</td>
<td valign="top" align="left">365.5</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="left">--</td>
<td valign="top" align="left">1, 31&#x2013;37, 1.5</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">10</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">MoDOT</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A7650</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Christopher Bond</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Clay, Mo.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">IS 35</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">364.7</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Yes</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">1, 38&#x2013;43, 1.6</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">11</td>
<td valign="top" align="left">MoDOT</td>
<td valign="top" align="left">A5817</td>
<td valign="top" align="left">Chouteau</td>
<td valign="top" align="left">Clay, Mo.</td>
<td valign="top" align="left">MO 269</td>
<td valign="top" align="left">362.3</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="left">--</td>
<td valign="top" align="left">1, 44&#x2013;50, 1.7</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">12</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">MoDOT</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A0767</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Randolph</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Clay, Mo.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">IS 435</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">360.3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Yes</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">1, 51&#x2013;61, 1.8&#x2013;1.9</td>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">13</td>
<td rowspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">MoDOT</td>
<td valign="top" align="left">A4757</td>
<td valign="top" align="left">Courtney</td>
<td valign="top" align="left">Jackson, Mo.</td>
<td valign="top" align="left">MO 291 S</td>
<td rowspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">352.7</td>
<td valign="top" align="left">Yes</td>
<td valign="top" align="left">Dual bridge crossing with L0568</td>
<td valign="top" align="left">1, 5, 62&#x2013;69, 1.10</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="border-bottom: solid 0.50pt" scope="row">L0568</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Courtney</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Jackson, Mo.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">MO 291 N</td>
<td valign="top" colspan="1" align="left" style="border-bottom: solid 0.50pt">Yes</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Dual bridge crossing with A4757</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">1, 5, 62&#x2013;69, 1.10</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t01n1"><label><sup>a</sup></label><p>River mile is the distance upstream from the confluence of the Missouri River with the Mississippi River at St. Louis, Mo. (<xref ref-type="fig" rid="fig01">fig. 1</xref>).</p></fn>
<fn id="t01n2"><label><sup>b</sup></label><p>Shown for consistency with previous survey; not included in this study.</p></fn></table-wrap-foot>
</table-wrap>
<fig id="fig01" position="float" fig-type="figure"><?Figure Large?><label>Figure 1</label><caption><p>Location of highway bridges crossing the Missouri River in and into Missouri in the Kansas City, Missouri, area.</p><p content-type="toc"><bold>Figure 1.</bold>&#x2003;Map showing the location of highway bridges crossing the Missouri River in and into Missouri in the Kansas City, Missouri, area.</p></caption>
<long-desc>The Missouri River in Kansas City with bridge locations marked.</long-desc><graphic xlink:href="rol21-0068_fig01"/></fig>
<sec>
<title>Purpose and Scope</title>
<p>The purpose of this report is to document the results of bathymetric and velocimetric surveys completed August 13&#x2013;14, 2019, of the Missouri River channel near 9&#x00A0;highway bridges at 8&#x00A0;crossings in the Kansas City, Mo., area (<xref ref-type="fig" rid="fig01">fig. 1</xref>; <xref ref-type="table" rid="t01">table 1</xref>) using an MBMS and an acoustic Doppler current profiler (ADCP). Special bathymetric surveys before and after installation of scour countermeasures near the main channel pier of two of the sites in August and October 2020 also are documented. Equipment and methods used and results obtained are described. The results obtained from the bathymetric and velocimetric surveys of the channel document the channel-bed conditions and velocity distribution at the time of the surveys and provide characteristics of scour holes that may be useful in developing predictive guidelines or equations for scour holes. These data also may be used by MoDOT as a low to moderate flood-flow comparison to help assess the bridges for stability and integrity issues with respect to bridge scour. Comparison of results to previous surveys at the sites (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>) also are provided.</p>
</sec>
<sec>
<title>Description of Study Area</title>
<p>The study area for this report is the Missouri River in and near Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig. 1</xref>). The Missouri River flows through the Kansas City area from west to east, meandering across the floodplain. The river is highly channelized in the Kansas City area; rock revetment and spur dikes are along the banks to maintain the channel alignment, and levees and floodwalls are on the upper banks to limit flooding in the industrial, commercial, and agricultural areas on the floodplains. The site numbering sequence used in <xref ref-type="bibr" rid="r11">Huizinga (2012)</xref> is used in this report for consistency and comparability.</p>
</sec>
<sec>
<title>Description of Streamflow Conditions</title>
<p>Data from the streamflow-gaging station (hereinafter referred to as &#x201C;streamgage&#x201D;) on the Missouri River at Kansas City, Mo. (station 06893000; <xref ref-type="bibr" rid="r37">U.S.&#x00A0;Geological Survey, 2020</xref>; <xref ref-type="fig" rid="fig01">fig. 1</xref>), indicated the Missouri River was in a trough between minor flood rises when the sites were surveyed August 13&#x2013;14, 2019 (<xref ref-type="fig" rid="fig02">fig. 2<italic>A</italic></xref>); however, the trough happened during generally higher summer streamflows that lasted from mid-March to past the end of the water year in September (<xref ref-type="fig" rid="fig02">fig. 2<italic>B</italic></xref>). Moderate streamflows of more than 110,000&#x00A0;cubic feet per second (ft<sup>3</sup>/s) were observed throughout the spring and summer, compared to 45,000&#x2013;50,000&#x00A0;ft<sup>3</sup>/s observed during the late winter trough in early March. The streamflow on the Missouri River as measured at the Kansas City streamgage ranged from about 122,000&#x00A0;to 137,000&#x00A0;ft<sup>3</sup>/s during the surveys. This streamflow range has a daily exceedance range of about 5&#x00A0;to 6&#x00A0;percent (<xref ref-type="bibr" rid="r38">U.S. Geological Survey, 2021</xref>) and is slightly less than the 50-percent annual exceedance probability (2-year recurrence interval) flood of 142,000&#x00A0;ft<sup>3</sup>/s (<xref ref-type="bibr" rid="r35">U.S.&#x00A0;Army Corps of Engineers, 2004</xref>, plate E&#x2013;20). Daily exceedance probabilities were computed using daily streamflow from 1957 to 2020 (<xref ref-type="bibr" rid="r38">U.S.&#x00A0;Geological Survey, 2021</xref>).</p>
<fig id="fig02" position="float" fig-type="figure"><?Figure Large?><label>Figure 2</label><caption><p>Unit values of streamflow (15-minute interval) from the streamflow-gaging station on the Missouri River at Kansas City, Missouri (station 06893000; <xref ref-type="bibr" rid="r37">U.S.&#x00A0;Geological Survey, 2020</xref>). <italic>A</italic>,<underline underline-style="UWORD">&#x00A0;</underline>August 8&#x2013;12, 2019. <italic>B</italic>,&#x00A0;March 1 through September 30, 2019.</p><p content-type="toc"><bold>Figure 2.</bold>&#x2003;Graphs showing unit values of streamflow from the streamflow-gaging station on the Missouri River at Kansas City, Missouri.</p></caption>
<long-desc>Streamflow on the Missouri River from March 1 through September 30, 2019.</long-desc><graphic xlink:href="rol21-0068_fig02"/></fig>
<p>Streamflow conditions in these daily and annual exceedance ranges are in the low to moderate flood-flow regime. In an analysis of real-time scour monitoring data at Jefferson City, Mo., <xref ref-type="bibr" rid="r13">Huizinga (2014)</xref> noted that substantial pier scour begins soon after the onset of hydrograph rise (substantial rise of 8&#x00A0;feet [ft] or more), although the scour often does not reach maximum depth until the peak stage is reached or sometime thereafter (see fig. 35 in <xref ref-type="bibr" rid="r13">Huizinga, 2014</xref>). Although the streamflow conditions during these surveys was not at the peak streamflow for the summer season, several peaks had occurred earlier in the year (<xref ref-type="fig" rid="fig02">fig. 2</xref>), and streamflow was substantially higher than base flow based on the daily exceedance values. Furthermore, the peak streamflow of 308,000&#x00A0;ft<sup>3</sup>/s on June 2, 2019, a streamflow that is in the 2- to 5-percent annual exceedance probability (20- to 50-year recurrence interval) range (<xref ref-type="bibr" rid="r35">U.S.&#x00A0;Army Corps of Engineers, 2004</xref>, plate&#x00A0;E&#x2013;20), was the highest streamflow since 1993 and is higher than flows observed in 2011 (<xref ref-type="bibr" rid="r37">U.S.&#x00A0;Geological Survey, 2020</xref>). Although the scour scenario captured at the sites in this study likely does not represent the maximum scour potential that might have been observed immediately after the peak streamflow in early June, the cumulative information gathered at the sites during the course of multiple surveys in 2010, 2011, 2016, and 2019 remains useful for determining scour for a variety of streamflow conditions and flood durations.</p>
<p>Special surveys were conducted at two of the sites in August and October 2020. The streamflow on the Missouri River as measured at the Kansas City streamgage was about 61,000&#x00A0;ft<sup>3</sup>/s during the survey on August 17, 2020, and was about 46,200&#x00A0;ft<sup>3</sup>/s during the survey on October 23, 2020. These streamflows have a daily exceedance of about 35&#x00A0;and 55&#x00A0;percent, respectively (daily exceedance probabilities were computed using daily streamflow from 1957 to 2020; <xref ref-type="bibr" rid="r38">U.S.&#x00A0;Geological Survey, 2021</xref>), and are substantially less than the 50-percent annual exceedance probability (2-year recurrence interval) flood of 142,000&#x00A0;ft<sup>3</sup>/s (<xref ref-type="bibr" rid="r35">U.S.&#x00A0;Army Corps of Engineers, 2004</xref>, plate&#x00A0;E&#x2013;20). Streamflow conditions in these daily and annual exceedance ranges are in the nonflood regime.</p>
</sec>
<sec>
<title>Description of Equipment and Basic Processing</title>
<p>The bathymetry of the Missouri or Mississippi River at each of the bridges was determined using a high-resolution MBMS. The various components of the MBMS used for this study are as described in reports about studies on the Missouri and Mississippi Rivers in Missouri (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>; <xref ref-type="bibr" rid="r18">2020a,</xref> e; <xref ref-type="bibr" rid="r24">Huizinga and others, 2010</xref>) and on the Missouri and Yellowstone Rivers in North Dakota (<xref ref-type="bibr" rid="r5">Densmore and others, 2013</xref>). The survey methods used to obtain the data were similar to these previous studies, as were the measures used to ensure data quality. A brief description of the equipment follows; a more-complete description of the various system components and methods used in this study are available in the previous reports by <xref ref-type="bibr" rid="r9">Huizinga (2010)</xref>, <xref ref-type="bibr" rid="r24">Huizinga and others (2010)</xref>, and <xref ref-type="bibr" rid="r5">Densmore and others (2013)</xref>.</p>
<p>An MBMS is an integration of several individual components: the multibeam echosounder (MBES), an inertial navigation system (INS), and a data-collection and data-processing computer. The MBES that was used for the 2019 surveys is the Norbit iWBMSh (<xref ref-type="fig" rid="fig03">fig. 3</xref>), which operated at a frequency of 400&#x00A0;kilohertz (kHz). The iWBMSh is similar in operation to the MBES systems used in other previous studies in the Kansas City area, except that it has a curved receiver array, which enables bathymetric data to be collected throughout a sound navigation and ranging (sonar) swath range of 210&#x00A0;degrees. Optimum data usually are collected in a swath of less than 160&#x00A0;degrees (80&#x00A0;degrees on each side of nadir, or straight down below the MBES); nevertheless, the swath can be electronically rotated to either side of nadir, enabling data along sloping banks to be captured up to a depth just below the water surface. The Norbit iWBMSh has a tightly coupled INS, the Applanix Position Orientation Solution for Marine Vessels (POS MV) OceanMaster system, consisting of an inertial motion unit on the sonar head (<xref ref-type="fig" rid="fig03">fig. 3<italic>A</italic></xref>) and two Global Navigation Satellite System (GNSS) antennae. The INS provides position in three-dimensional space and measures the pitch, roll, yaw, and heading of the vessel (and, thereby, the MBES) to accurately position the data received by the MBES. Real-time kinematic (RTK) differential corrections for the INS came from cellular communication with the MoDOT GNSS real-time network for the navigation and tide solution during the 2019 surveys.</p>
<fig id="fig03" position="float" fig-type="figure"><?Figure Large?><label>Figure 3</label><caption><p>The Norbit iWBMSh multibeam echosounder. Photographs by Richard J. Huizinga, U.S.&#x00A0;Geological Survey. <italic>A</italic>,&#x00A0;Viewed from the side. <italic>B</italic>,&#x00A0;Mounted on the port side of the U.S.&#x00A0;Geological Survey boat.</p><p content-type="toc"><bold>Figure 3.</bold>&#x2003;Images showing the Norbit iWBMSh multibeam echosounder.</p></caption>
<long-desc>Photos of the multibeam sonar on the boat.</long-desc><graphic xlink:href="rol21-0068_fig03"/></fig>
<p>As in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r17">b</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r19">b</xref>, <xref ref-type="bibr" rid="r20">c</xref>, <xref ref-type="bibr" rid="r21">d</xref>, e), the navigation information from the 2019 surveys was postprocessed using the POSPac Mobile Mapping Suite (MMS) software (<xref ref-type="bibr" rid="r1">Applanix Corporation, 2017</xref>) to mitigate the effects of degraded positional accuracy of the vessel while near or under a bridge. The POSPac MMS provides tools to identify and compensate for sensor and environmental errors and computes an optimally blended navigation solution from the GNSS and inertial measurement unit (IMU) raw data. The blended navigation solution (called a &#x201C;smoothed best estimate of trajectory&#x201D; or &#x201C;SBET&#x201D; file) generated by postprocessing the navigation data was applied to the survey at a given bridge to minimize the effects of the GNSS outages while surveying under the bridges.</p>
<p>The data from the MBES and INS components were processed and integrated into a cohesive dataset for cleanup and visualization. A computer onboard the survey vessel ran the HYPACK/HYSWEEP data acquisition software (<xref ref-type="bibr" rid="r26">HYPACK, Inc., 2018</xref>) that was used to prepare for the bathymetric surveys and collect the survey data. After completing the surveys, the acquired depth data were further processed to remove data spikes and other spurious points in the multibeam swath trace, georeferenced using the navigation and position solution data from the SBET file from the POSPac MMS, and visualized in HYPACK/HYSWEEP as a gridded bathymetric surface or a point cloud.</p>
<p>Information about the velocity of the river at various points throughout each study reach were collected using an ADCP, similar to recent previous studies by <xref ref-type="bibr" rid="r11">Huizinga (2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r17">b</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r19">b</xref>, <xref ref-type="bibr" rid="r20">c</xref>, <xref ref-type="bibr" rid="r21">d</xref>, e). A Teledyne RD Instruments Rio Grande ADCP operating at 600&#x00A0;kHz was used to obtain velocities at 1.64-ft increments, or &#x201C;bins,&#x201D; throughout the water column. The Rio Grande 600-kHz ADCP operates in depths from 2.3&#x00A0;to 230&#x00A0;ft and determines the velocity of the water by measuring the Doppler shift of an acoustic signal reflected from various particles suspended in the water (<xref ref-type="bibr" rid="r28">Mueller and others, 2013</xref>). By measuring the Doppler shift in four different beam directions, the velocity of the water in each bin can be determined in three dimensions.</p>
</sec>
<sec>
<title>Basic Description of Methods</title>
<p>The methods used to acquire and ensure the collection of quality data were the same as those used in previous studies using the MBES (methods are detailed in <xref ref-type="bibr" rid="r24">Huizinga and others, 2010</xref>; <xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>). A brief summary of&#x2014;and differences from&#x2014;these methods are highlighted below.</p>
<sec>
<title>Surveying Methods</title>
<p>Generally, the surveyed area extended across the active channel from bank to bank, as in the previous studies on the Missouri River in the Kansas City area (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>). The surveyed reaches were 1,550&#x00A0;to 1,660&#x00A0;ft long in the direction of flow, positioned so that the surveyed highway bridges were about one-third to one-half of the total length from the upstream boundary, generally using about the same upstream and downstream boundaries as used in the 2011 flood study on the Missouri River (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>). The upstream and downstream boundaries of the surveyed areas were assumed to be beyond the substantial hydraulic effects (wake vortices and shear flow) of the bridge structures.</p>
<p>As in previous studies, bathymetric data were obtained along longitudinal transect lines, and each survey was designed such that there was overlap of the survey swaths to attempt to ensure complete coverage of the channel bed and minimize sonic &#x201C;shadows&#x201D; (<xref ref-type="bibr" rid="r24">Huizinga and others, 2010</xref>). Substantial overlap was achieved for many of the surveyed swaths, except in shallow areas near the channel banks or spur dikes and near in-flow structures or debris rafts. Areas near the bridge piers and along the banks also were surveyed in an upstream direction with the MBES swath electronically tilted to port or starboard to increase the acquisition of bathymetric data higher on the banks and the sides of the piers. The electronically tilted swath generally was 120&#x00A0;degrees wide, extending from 10&#x00A0;degrees above horizontal on the bank-ward or pier-ward side of the survey vessel to 20&#x00A0;degrees past nadir below the vessel.</p>
<p>After completing the bathymetric survey with the MBMS at a given site, the velocity data were obtained with the ADCP on seven lateral sections across the channel within the study area. The position and speed of the boat was determined using a differential GNSS receiver mounted on a pole directly above the ADCP. The bottom-track reference method for determining boat speed was anticipated to be unusable because of moving channel-bed material, so the boat velocity was determined using the GNSS essential fix data (the NMEA&#x2013;0183 GGA string [shorthand for the $GPGGA standard output format for GNSS essential fix data defined by the National Marine Electronics Association 0183 standard that includes information on the three-dimensional location and accuracy of the GNSS receiver; <xref ref-type="bibr" rid="r29">National Marine Electronics Association, 2002</xref>]) from the differential GNSS receiver. The distance between the velocity section lines generally was about 260&#x00A0;ft. Three sections were upstream and four sections were downstream from the bridge being surveyed. Each section line was traversed in each direction across the river. The reported velocity values are the average from the two traverses of a given section line, computed using averaging algorithms from the Velocity Mapping Toolbox (<xref ref-type="bibr" rid="r30">Parsons and others, 2013</xref>). Streamflow for a site was computed as the average of the streamflows from reciprocal pairs (two transects per section line) at the various sections in the reach. Generally, measured streamflow for an individual transect was within 5&#x00A0;percent of the average.</p>
</sec>
<sec>
<title>Survey Quality-Assurance/Quality-Control Measures</title>
<p>A quality-assurance plan has been established for streamflow measurements using ADCPs that includes several instrument diagnostic checks and calibrations. These standard operating procedures were followed when acquiring the velocity profile data for these surveys, including a moving-bed test and paired ADCP measurements at each transect to mitigate directional bias. For a detailed discussion of these procedures, see <xref ref-type="bibr" rid="r28">Mueller and others (2013)</xref>.</p>
<p>For the MBMS, the principal quality-assurance measures were assessed in real time during the survey. The MBMS operator continuously assessed the quality of the collected data during the survey by making visual observations of cross-track swath shape (such as convex, concave, or skewed bed returns in flat, smooth bottoms), noting data-quality flags and alarms from the MBES and the INS, and noting comparisons between adjacent overlapping swaths. In addition to the real-time quality-assurance assessments during the survey, beam angle checks and a suite of patch tests were executed to ensure quality data were acquired from the MBMS for the 2019 surveys. The beam angle test and patch tests were completed at Longview Lake near Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>).</p>
<sec>
<title>Beam Angle Check</title>
<p>A beam angle check is used to determine the accuracy of the depth readings obtained by the outer beams (greater than 25&#x00A0;degrees from nadir [vertical]) of the MBES (<xref ref-type="bibr" rid="r36">U.S.&#x00A0;Army Corps of Engineers, 2013</xref>), which may change with time as a result of inaccurate sound velocities, physical configuration changes, and overall depth being surveyed. The HYPACK/HYSWEEP software has a utility that develops a statistical assessment of the quality of the outer beams compared to a reference surface (<xref ref-type="bibr" rid="r26">HYPACK, Inc., 2018</xref>). On August 12, 2019, a reference surface was surveyed for a part of Longview Lake near Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), and check lines were run across the reference surface. Included with the measurement was a sound-velocity profile cast to document and quantify any stratification in the water column near the reference surface. The results of this beam angle check (<xref ref-type="table" rid="t02">table&#x00A0;2</xref>) were within the recommended performance standards used by the U.S.&#x00A0;Army Corps of Engineers for hydrographic surveys for all the representative angles less than 55&#x00A0;degrees (<xref ref-type="bibr" rid="r36">U.S.&#x00A0;Army Corps of Engineers, 2013</xref>), permitting the use of the central 110&#x00A0;degrees of the sonar swath with confidence.</p>
<table-wrap id="t02" position="float">
<label>Table 2</label><caption><title>Results of a beam angle check from two check lines over a reference surface at Longview Lake near Kansas City, Missouri, on August 12, 2019.<?Table Small?></title>
<p content-type="toc"><bold>Table 2.</bold>&#x2003;Results of a beam angle check from two check lines over a reference surface at Longview Lake near Kansas City, Missouri, on August 12, 2019.</p>
<p>[&lt;, less than; --, no data]</p>
</caption>
<table rules="groups">
<col width="17.44%"/>
<col width="20.88%"/>
<col width="20.88%"/>
<col width="18.99%"/>
<col width="21.81%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Beam angle limit, in degrees</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Maximum outlier, in feet</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Average difference, in feet</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Standard deviation, in feet</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">95-percent confidence, in feet</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="5" valign="top" align="center" style="border-top: solid 0.50pt" scope="col">Beam angle check results</th>
</tr>
<tr>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt" scope="row">0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.36</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.00</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.10</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.20</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">5</td>
<td valign="top" align="char" char=".">0.49</td>
<td valign="top" align="char" char=".">0.03</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.20</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">10</td>
<td valign="top" align="char" char=".">0.49</td>
<td valign="top" align="char" char=".">0.07</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.23</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">15</td>
<td valign="top" align="char" char=".">0.49</td>
<td valign="top" align="char" char=".">0.07</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">20</td>
<td valign="top" align="char" char=".">0.62</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">25</td>
<td valign="top" align="char" char=".">0.59</td>
<td valign="top" align="char" char=".">0.07</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">30</td>
<td valign="top" align="char" char=".">0.66</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">35</td>
<td valign="top" align="char" char=".">0.72</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">40</td>
<td valign="top" align="char" char=".">0.62</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">45</td>
<td valign="top" align="char" char=".">0.72</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">50</td>
<td valign="top" align="char" char=".">0.92</td>
<td valign="top" align="char" char=".">0.03</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.26</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">55</td>
<td valign="top" align="char" char=".">1.28</td>
<td valign="top" align="char" char=".">&#x2212;0.03</td>
<td valign="top" align="char" char=".">0.20</td>
<td valign="top" align="char" char=".">0.36</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">60</td>
<td valign="top" align="char" char=".">2.10</td>
<td valign="top" align="char" char=".">&#x2212;0.13</td>
<td valign="top" align="char" char=".">0.26</td>
<td valign="top" align="char" char=".">0.52</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">65</td>
<td valign="top" align="char" char=".">2.03</td>
<td valign="top" align="char" char=".">&#x2212;0.23</td>
<td valign="top" align="char" char=".">0.33</td>
<td valign="top" align="char" char=".">0.62</td>
</tr>
<tr>
<td valign="top" align="char" char="." scope="row">70</td>
<td valign="top" align="char" char=".">1.57</td>
<td valign="top" align="char" char=".">&#x2212;0.36</td>
<td valign="top" align="char" char=".">0.20</td>
<td valign="top" align="char" char=".">0.39</td>
</tr>
<tr>
<th valign="middle" colspan="5" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Performance standards<sup>a</sup></th>
</tr>
<tr>
<td valign="top" align="left" scope="row">--</td>
<td valign="top" align="char" char=".">1.00</td>
<td valign="top" align="char" char=".">&lt;0.20</td>
<td valign="top" align="left">--</td>
<td valign="top" align="char" char=".">&lt;0.80</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">--</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Met, angle &lt;55</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Met, angle &lt;65</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">--</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Met</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t02n1"><label><sup>a</sup></label><p>Performance standard check values are from <xref ref-type="bibr" rid="r36">U.S.&#x00A0;Army Corps of Engineers (2013</xref>, table&#x00A0;3&#x2011;1) for soft sand/silt bottoms.</p></fn></table-wrap-foot>
</table-wrap>
<p>Ideally, the average depth of the reference surface used in the beam angle check would be equal to or greater than the depth in the area being surveyed. The depth of the Missouri River in each study reach generally is unknown before each survey because of the dynamic nature of the channel bed and streamflow conditions; however, the average depth of the reference surface (about 70&#x00A0;ft) was expected to be substantially greater than the average depth observed in the 2019 surveys because the average depths observed during the 2011 flood surveys in the Kansas City area were less than 40&#x00A0;ft (the average depth is the difference between the average water-surface elevation and average channel-bed elevation in table 5 of <xref ref-type="bibr" rid="r11">Huizinga [2012]</xref>). As described in the &#x201C;Surveying Methods&#x201D; section earlier in this report, areas with depths greater than the average depths generally had substantial overlap of the surveyed swath with adjacent swaths. Data from the outer beams in these areas were either verified or removed to mitigate any detrimental effects caused by beam angle inaccuracies</p>
</sec>
<sec>
<title>Patch Tests</title>
<p>Patch tests are a series of dynamic calibration tests that are used to check for subtle variations in the orientation and timing of the MBES with respect to the INS and real-world coordinates. The patch tests are used to determine timing offsets caused by latency between the MBES and the INS, and to determine angular offsets to roll, pitch, and yaw caused by the alignment of the transducer head (<xref ref-type="fig" rid="fig04">fig.&#x00A0;4</xref>). These offsets have been observed to be essentially constant for a given survey, barring an event that causes the mount to change such as striking a floating or submerged object (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>). The offsets determined in the patch test are applied when processing the data collected during a survey.</p>
<fig id="fig04" position="float" fig-type="figure"><?Figure Large?><label>Figure 4</label><caption><p>Generalized effects on data from a multibeam echosounder. <italic>A</italic>,&#x00A0;Timing offset for latency. <italic>B</italic>,&#x00A0;Angular offset for roll. <italic>C</italic>,&#x00A0;Angular offset for pitch. <italic>D</italic>,&#x00A0;Angular offset for yaw.</p><p content-type="toc"><bold>Figure 4.</bold>&#x2003;Diagrams showing generalized effects on data from a multibeam echosounder.</p></caption>
<long-desc>Four sketches showing effects of timing and angular offsets on multibeam data.</long-desc><graphic xlink:href="rol21-0068_fig04"/></fig>
<p>Patch tests were completed before and after the 2019 surveys at three lakes in Missouri (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>). Although the MBES had several minor strikes of floating debris at various times during the 2019 surveys, there were no apparent changes to the roll, pitch, or yaw angles from the beginning to the end of the surveys.</p>
<table-wrap id="t03" position="float">
<label>Table 3</label><caption><title>Patch test results at a few locations in Missouri from July 17 to September 4, 2019.<?Table Large?></title>
<p content-type="toc"><bold>Table 3.</bold>&#x2003;Patch test results at a few locations in Missouri from July 17 to September 4, 2019.</p>
<p>[Dates are shown as month/day/year]</p>
</caption>
<table rules="groups">
<col width="9.14%"/>
<col width="9.76%"/>
<col width="13.81%"/>
<col width="13.25%"/>
<col width="14.13%"/>
<col width="39.91%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Date of test</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Timing offset, in seconds</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Angular offset for roll, in degrees</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Angular offset for pitch, in degrees</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Angular offset for yaw, in degrees</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Location (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">07/17/19</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x2212;0.30</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">King City South Lake near King City, Missouri</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">08/12/19</td>
<td valign="top" align="char" char=".">0</td>
<td valign="top" align="char" char=".">&#x2212;0.37</td>
<td valign="top" align="char" char=".">0</td>
<td valign="top" align="char" char=".">0</td>
<td valign="top" align="left">Longview Lake near Kansas City, Missouri</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">09/04/19</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x2212;0.30</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.50</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Harrison County Lake near Bethany, Missouri</td>
</tr>
</tbody></table></table-wrap>
<p>For this study, there was no measured timing offset (&#x0394;<italic>t</italic>=0; <xref ref-type="table" rid="t03">table&#x00A0;3</xref>, <xref ref-type="fig" rid="fig04">fig.&#x00A0;4</xref>), which is consistent with latency test results for this boat and similar equipment configurations used in other surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>; <xref ref-type="bibr" rid="r24">Huizinga and others, 2010</xref>). The measured angular offset for pitch was 0&#x00A0;degree (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>). The measured offset for yaw changed from 0 to 0.50&#x00A0;degree (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>), which is likely the result of a relatively major strike of a submerged tree at Harrison County Lake; therefore, the yaw of the Kansas City area surveys was not affected. The measured angular offset for roll seemed to be &#x2013;0.37&#x00A0;degree just before the Kansas City area surveys based on the results at Longview Lake (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>); however, the measured angular offset for roll was &#x2013;0.30&#x00A0;degree for the patch tests before and after the Kansas City area surveys (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>). Furthermore, using a roll angle offset of &#x2013;0.37&#x00A0;degree during processing of the Kansas City area bridge surveys indicated this offset was incorrect. Therefore, a roll angle offset of &#x2013;0.30&#x00A0;degree was used for the Kansas City area bridge surveys with better overall results. It was noted in the earliest work with the MBMS in Missouri (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>) that a sensitivity analysis of the four offsets implied that the ultimate position of surveyed points in three-dimensional space was least sensitive to the angular offset for yaw, whereas it was most sensitive to the angular offset for roll.</p>
<p>The bathymetric data were processed to apply the offsets determined from the patch tests and to remove data spikes and other spurious points in the multibeam swaths through the use of automatic filters and manual editing. The bathymetric data were then projected to a three-dimensional grid at a resolution of 1.64&#x00A0;ft using the Combined Uncertainty and Bathymetry Estimator (CUBE) method (<xref ref-type="bibr" rid="r4">Calder and Mayer, 2003</xref>), as implemented in the MBMax processing package of the HYPACK/HYSWEEP software (<xref ref-type="bibr" rid="r26">HYPACK, Inc., 2018</xref>) and used to generate a gridded raster surface of the channel bed (and associated uncertainty) near each bridge (hereinafter referred to as a &#x201C;bathymetric surface&#x201D;) using ArcGIS (<xref ref-type="bibr" rid="r7">Esri, 2020</xref>).</p>
</sec>
</sec>
<sec>
<title>Uncertainty Estimation</title>
<p>Similar to the previous studies of bathymetry in Missouri (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r17">b</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r19">b</xref>, <xref ref-type="bibr" rid="r20">c</xref>, <xref ref-type="bibr" rid="r21">d</xref>, <xref ref-type="bibr" rid="r22">e</xref>), uncertainty in the surveys was estimated by computing the uncertainty for each survey-grid cell in the bathymetric surface of each survey area using the CUBE method (<xref ref-type="bibr" rid="r4">Calder and Mayer, 2003</xref>) as implemented in the MBMax processing package of the HYPACK/HYSWEEP software (<xref ref-type="bibr" rid="r26">HYPACK, Inc., 2018</xref>). The CUBE uncertainty is a measure of the variability of the individual points in the cell used to determine the CUBE-derived elevation for the cell. Statistics of CUBE uncertainty for each of the survey areas are shown in <xref ref-type="table" rid="t04">table&#x00A0;4</xref>, and an example of the spatial distribution of CUBE uncertainty typically observed in the survey data is shown in <xref ref-type="fig" rid="fig05">figure&#x00A0;5</xref> for the bathymetric data at structures A4757 and L0568 on State Highway 291. The uncertainty data were output and combined with the three-dimensional bathymetry data and are included with metadata in the USGS data release associated with this study (<xref ref-type="bibr" rid="r23">Huizinga, 2021</xref>).</p>
<table-wrap id="t04" orientation="landscape" position="float">
<label>Table 4</label><caption><title>Uncertainty results for gridded bathymetric data at a 1.64-foot grid spacing from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</title>
<p content-type="toc"><bold>Table 4.</bold>&#x2003;Uncertainty results for gridded bathymetric data at a 1.64-foot grid spacing from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</p>
<p>[MoDOT, Missouri Department of Transportation]</p>
</caption>
<table rules="groups">
<col width="7.58%"/>
<col width="12.42%"/>
<col width="12.28%"/>
<col width="10.99%"/>
<col width="11.72%"/>
<col width="14.65%"/>
<col width="7.49%"/>
<col width="7.49%"/>
<col width="7.49%"/>
<col width="7.89%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Site number (<xref ref-type="fig" rid="fig01">fig. 1</xref>)</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">MoDOT structure number</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Maximum value of uncertainty, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Average value of uncertainty, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Median value of uncertainty, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Standard deviation of uncertainty, in feet</td>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Percentage of bathymetry points with uncertainty value less than a given threshold</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-bottom: solid 0.50pt">1.00 foot</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">0.50 foot</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">0.25 foot</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">0.10 foot</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">6</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">A1800</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">3.97</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.12</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.10</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.09</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">99.8</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">99.2</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">97.4</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">56.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">7</td>
<td valign="top" align="left">A8340</td>
<td valign="top" align="char" char=".">3.54</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.06</td>
<td valign="top" align="char" char=".">100.0</td>
<td valign="top" align="char" char=".">99.7</td>
<td valign="top" align="char" char=".">99.1</td>
<td valign="top" align="char" char=".">76.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">8</td>
<td valign="top" align="left">A4649</td>
<td valign="top" align="char" char=".">4.00</td>
<td valign="top" align="char" char=".">0.12</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.09</td>
<td valign="top" align="char" char=".">99.8</td>
<td valign="top" align="char" char=".">99.2</td>
<td valign="top" align="char" char=".">96.6</td>
<td valign="top" align="char" char=".">54.9</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">9</td>
<td valign="top" align="left">A4060</td>
<td valign="top" align="char" char=".">3.81</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.08</td>
<td valign="top" align="char" char=".">99.9</td>
<td valign="top" align="char" char=".">99.4</td>
<td valign="top" align="char" char=".">97.2</td>
<td valign="top" align="char" char=".">52.1</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10</td>
<td valign="top" align="left">A7650</td>
<td valign="top" align="char" char=".">1.57</td>
<td valign="top" align="char" char=".">0.12</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.07</td>
<td valign="top" align="char" char=".">99.9</td>
<td valign="top" align="char" char=".">99.4</td>
<td valign="top" align="char" char=".">97.0</td>
<td valign="top" align="char" char=".">50.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">11</td>
<td valign="top" align="left">A5817</td>
<td valign="top" align="char" char=".">3.38</td>
<td valign="top" align="char" char=".">0.09</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.06</td>
<td valign="top" align="char" char=".">100.0</td>
<td valign="top" align="char" char=".">99.7</td>
<td valign="top" align="char" char=".">98.8</td>
<td valign="top" align="char" char=".">75.1</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">12</td>
<td valign="top" align="left">A0767</td>
<td valign="top" align="char" char=".">2.82</td>
<td valign="top" align="char" char=".">0.12</td>
<td valign="top" align="char" char=".">0.10</td>
<td valign="top" align="char" char=".">0.08</td>
<td valign="top" align="char" char=".">99.9</td>
<td valign="top" align="char" char=".">99.5</td>
<td valign="top" align="char" char=".">97.2</td>
<td valign="top" align="char" char=".">50.8</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">13</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">A4757/L0568</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">3.87</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.13</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.10</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.09</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">99.8</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">99.2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">96.4</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">50.4</td>
</tr>
</tbody></table></table-wrap>
<fig id="fig05" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 5</label><caption><p>Uncertainty of gridded bathymetric data from the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 5.</bold>&#x2003;Map showing uncertainty of gridded bathymetric data from the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri.</p></caption>
<long-desc>Distribution of uncertainty at State Highway 291 bridges.</long-desc><graphic xlink:href="rol21-0068_fig05"/></fig>
<p>The largest uncertainty in this group of surveys was 4.00&#x00A0;ft (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>); however, as noted in previous studies, uncertainty values of this magnitude typically happened near high-relief features, such as the front or side of a pier footing (<xref ref-type="fig" rid="fig05">fig.&#x00A0;5</xref>). More than 98&#x00A0;percent of the uncertainty values at all the sites were less than 0.50&#x00A0;ft (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>), which is within the specifications for a &#x201C;Special Order&#x201D; survey, the most-stringent survey standard of the International Hydrographic Organization (IHO; <xref ref-type="bibr" rid="r27">International Hydrographic Organization, 2008</xref>). As noted in previous surveys with this type of equipment (see, for example, <xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), the uncertainty values were larger near moderate-relief features (banks, spur dikes, rock riprap and outcrops, and scour holes near piers). Occasionally, the uncertainty values also were larger (1.00&#x00A0;ft or greater) in the outermost beam extents of the multibeam swath in the overlap with an adjacent swath, particularly when the MBES head was electronically tilted for the survey lines along the banks or near the piers. Overlapping adjacent swaths in the channel thalweg (the line of maximum depth in the channel) also can display larger uncertainty values because substantial bed movement can happen between survey passes (<xref ref-type="fig" rid="fig05">fig.&#x00A0;5</xref>). More than 96&#x00A0;percent of the uncertainty values were less than 0.25&#x00A0;ft, and more than 50&#x00A0;percent of the uncertainty values were less than 0.10&#x00A0;ft (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>). The tops of bridge substructural elements (pier footings and seal courses) typically had uncertainty values of less than 0.10&#x00A0;ft.</p>
<p>The uncertainty of the gridded data computed using the CUBE method has been decreasing with time compared to previous surveys (see <xref ref-type="table" rid="t04">table&#x00A0;4</xref> in previous studies; <xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>). The decrease in uncertainty primarily is the result of improvements in data-collection equipment and methods. The Norbit iWBMSh used in these surveys has the IMU attached directly to the sonar head in what is referred to as a &#x201C;tightly coupled&#x201D; configuration, which decreases some of the uncertainty by reducing the lever arm length (and therefore the potential movement) between the sonar and IMU. The ability to electronically tilt the sonar swath substantially reduces the time between when unrotated, down-looking data and rotated, side-looking data are collected, which reduces the uncertainty of the data in the swath overlap zone that might otherwise experience more substantial bed movement.</p>
<p>The survey at structures A4757 and L0568 on State Highway 291 had the third-highest maximum value of uncertainty, as well as the lowest percentage of bathymetry points with an uncertainty of less than the various thresholds (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>). The survey was obtained with relatively smooth longitudinal swaths (<xref ref-type="fig" rid="fig05">fig.&#x00A0;5</xref>), which was the case at nearly all the sites surveyed in this study. The primary anomalies at this site were observed along the banks, where the sonar was used in an electronically tilted configuration to extend the potential coverage in these areas, resulting in high uncertainty values. Secondary anomalies at this site were in the downstream midchannel area where thalweg migration and insufficient overlap of the swath outer beams resulted in high uncertainty values. Generally, the magnitude and distribution of uncertainty observed at this site are representative of those observed at all the other surveyed sites.</p>
</sec>
</sec>
</sec>
<sec>
<title>Results of Bathymetric and Velocimetric Surveys</title>
<p>The site-specific results for each bridge are discussed in the following sections, starting with the upstream-most bridge and progressing downstream. The site-specific results are followed by a discussion of general findings that are not specific to a particular site. The range of bed elevations described as &#x201C;the channel-bed elevations&#x201D; for each survey was based on statistical analysis of the gridded raster surface of the bathymetry data at each site and covers the 5th&#x00A0;to 95th&#x00A0;percentile range of the data. Because the surveys generally were limited to the active channel from bank to bank excluding overbank areas, this percentile range generally covered the channel bed but excluded the banks and localized high or low spots, such as spur dikes or scour holes near piers. All elevation data were referenced to the North American Vertical Datum of 1988 (NAVD&#x00A0;88).</p>
<p>For consistency with earlier studies, dune sizes are described in general terms for each of the bridge sites using the categories set by <xref ref-type="bibr" rid="r11">Huizinga (2012)</xref> for the discussion of bathymetry during the 2011 flood. In this report, small dunes and ripples are those that are less than 5&#x00A0;ft high from crest to trough, medium dunes are those that are 5&#x00A0;to 10&#x00A0;ft high, large dunes are those that are 10&#x00A0;to 15&#x00A0;ft high, and very large dunes are those that are 15&#x00A0;ft or more in height.</p>
<p>All the bridge sites in this study were previously surveyed (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), and bathymetry data from earlier surveys at all eight crossings are included with metadata in <xref ref-type="bibr" rid="r19">Huizinga (2020b)</xref>. A map showing the difference in channel-bed elevation for the area common to the comparison surveys is included for each site, and data from previous surveys are included in the cross-section plot for that bridge. The difference maps were created using the Geomorphic Change Detection (GCD) add-in tool for ArcGIS available through the <xref ref-type="bibr" rid="r31">Riverscapes Consortium (2020)</xref>. GCD computes elevation difference and volumetric change in storage between two gridded raster surfaces (each as a digital elevation model, or &#x201C;DEM&#x201D; of the surface) derived from repeat topographic surveys. The GCD program provides a suite of tools to associate the uncertainties for points in the various surveys (using the uncertainty values associated with each point, or an average uncertainty of the survey when point-specific uncertainty data were not available [2010 survey data]) and propagates those uncertainties through the DEM of difference (DoD) map. The GCD program also provides a way to segregate the best estimates of change using threshold masks. A threshold mask of 95-percent confidence was used for comparisons in the current study, and summary statistics (maximum, minimum, and average) of the DoD maps were determined. Sediment volumes for cut (scour) and fill (deposition) between the 2019 survey and previous surveys in 2010, 2011 and 2015 also were determined. The surveys are broadly compared based on their timing and the streamflow at the time of the survey. Additionally, shaded triangulated irregular network (TIN) images of the channel and side of pier were prepared for each surveyed pier. These visualizations are shown in <xref ref-type="app" rid="a1">appendix&#x00A0;1</xref>, <xref ref-type="fig" rid="fig01.01">figures 1.1</xref> to <xref ref-type="fig" rid="fig01.10">1.10</xref>.</p>
<p>Although the configuration of the channel bed and the underlying sediment transport conditions at a site are associated with an instantaneous streamflow in the discussions that follow, a given bathymetric surface actually is a reflection of more than those instantaneous transport conditions. A wide variety of factors affect the channel-bed configuration of a reach for a specific streamflow, including magnitude of flow velocities and velocity distribution, the number, size, and timing of previous flood rises, whether or not the stage currently is rising or falling, and other local hydraulic conditions (<xref ref-type="bibr" rid="r8">Gilbert and Murphy, 1914</xref>; <xref ref-type="bibr" rid="r33">Simons and Richardson, 1966</xref>). Furthermore, the channel-bed configuration at a site is affected by upstream and local sediment conditions (size and spatial distribution) and contributions, as well as water temperature and other seasonal variations (<xref ref-type="bibr" rid="r34">Simon, Li and Associates, 1985</xref>). Because of the myriad number and interactions between factors affecting sediment transport conditions and the resultant bed configuration, it was assumed that the configuration and size of bed forms observed during the current (2019) surveys in the Kansas City area depended on more than the instantaneous streamflow at a given site. Although it is beyond the scope of the current (2019) study to examine all the antecedent conditions that created the observed channel-bed configuration, the comparisons with previous surveys under different streamflow conditions nevertheless contributes to understanding the many complexities of sediment transport.</p>
<p>As in recent previous studies (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r12">2013</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>), when discussing the vertically averaged velocity values obtained during the surveys in the sections that follow, neighboring vectors having random variations in direction and magnitude were taken as an indication of nonuniform flow in the section resulting from shear and wake vortices. Conversely, neighboring vectors having gradual and systematic variations were taken as an indication of uniform flow in the section. The Missouri River is highly turbulent even in the absence of structures that generate strong shear or wakes, but in the interest of conciseness, nonuniform flow is loosely described as &#x201C;turbulent&#x201D; in the following sections.</p>
<sec>
<title>Structure A1800 on Interstate 635</title>
<p>Structure A1800 (site&#x00A0;6; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on Interstate 635 crosses the Missouri River at river mile (RM) 374.1, on the northwestern side of Kansas City (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 13, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GNSS tide solution, was 731.9&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). Streamflow on the Missouri River was about 112,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<table-wrap id="t05" orientation="landscape" position="float">
<label>Table 5</label><caption><title>Bridge and survey information, and selected channel-bed elevations from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</title>
<p content-type="toc"><bold>Table 5.</bold>&#x2003;Bridge and survey information, and selected channel-bed elevations from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</p>
<p>[Dates are shown as month/day/year. All elevations are referenced to the North American Vertical Datum of 1988. MoDOT, Missouri Department of Transportation; ADCP, acoustic Doppler current profiler; IS, Interstate highway; US, U.S. highway; MO, State highway]</p>
</caption>
<table rules="groups">
<col width="6.34%"/>
<col width="10.97%"/>
<col width="8.56%"/>
<col width="7.37%"/>
<col width="6.22%"/>
<col width="11.76%"/>
<col width="10.37%"/>
<col width="10.37%"/>
<col width="9.14%"/>
<col width="9.53%"/>
<col width="9.37%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Site number (<xref ref-type="fig" rid="fig01">fig. 1</xref>)</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">MoDOT structure number</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Survey date</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Route</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">River mile<sup>a</sup></td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Streamflow from ADCP measurements,<sup>b</sup> in cubic feet per second</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Average water-surface elevation near the bridge, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Average channel-bed elevation,<sup>c</sup> in feet</td>
<td valign="middle" colspan="2" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate elevation of the indicated percentile of the bathymetric data, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate minimum channel elevation,<sup>d</sup> in feet</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-bottom: solid 0.50pt">5th percentile</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">95th percentile</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">6</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">A1800</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">08/13/19</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">IS 635</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">374.1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">112,000</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">731.9</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">708.2</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">698.0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">719.0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt"><sup>e</sup>692</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">7</td>
<td valign="top" align="left">A8340</td>
<td valign="top" align="left">08/13/19</td>
<td valign="top" align="left">US 69</td>
<td valign="top" align="char" char=".">372.6</td>
<td valign="top" align="char" char=".">114,000</td>
<td valign="top" align="char" char=".">730.6</td>
<td valign="top" align="char" char=".">707.6</td>
<td valign="top" align="char" char=".">698.0</td>
<td valign="top" align="char" char=".">716.7</td>
<td valign="top" align="char" char="."><sup>e</sup>688</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">8</td>
<td valign="top" align="left">A4649</td>
<td valign="top" align="left">08/13/19</td>
<td valign="top" align="left">US 169</td>
<td valign="top" align="char" char=".">366.2</td>
<td valign="top" align="char" char=".">126,000</td>
<td valign="top" align="char" char=".">729.0</td>
<td valign="top" align="char" char=".">703.5</td>
<td valign="top" align="char" char=".">689.1</td>
<td valign="top" align="char" char=".">719.2</td>
<td valign="top" align="char" char=".">676</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">9</td>
<td valign="top" align="left">A4060</td>
<td valign="top" align="left">08/13/19</td>
<td valign="top" align="left">MO 9</td>
<td valign="top" align="char" char=".">365.5</td>
<td valign="top" align="char" char=".">126,000</td>
<td valign="top" align="char" char=".">728.2</td>
<td valign="top" align="char" char=".">700.1</td>
<td valign="top" align="char" char=".">689.9</td>
<td valign="top" align="char" char=".">715.1</td>
<td valign="top" align="char" char=".">678</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10</td>
<td valign="top" align="left">A7650</td>
<td valign="top" align="left">08/14/19</td>
<td valign="top" align="left">IS 35</td>
<td valign="top" align="char" char=".">364.7</td>
<td valign="top" align="char" char=".">142,000</td>
<td valign="top" align="char" char=".">728.2</td>
<td valign="top" align="char" char=".">697.6</td>
<td valign="top" align="char" char=".">689.7</td>
<td valign="top" align="char" char=".">714.1</td>
<td valign="top" align="char" char=".">671</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">11</td>
<td valign="top" align="left">A5817</td>
<td valign="top" align="left">08/14/19</td>
<td valign="top" align="left">MO 269</td>
<td valign="top" align="char" char=".">362.3</td>
<td valign="top" align="char" char=".">142,000</td>
<td valign="top" align="char" char=".">726.5</td>
<td valign="top" align="char" char=".">700.7</td>
<td valign="top" align="char" char=".">690.6</td>
<td valign="top" align="char" char=".">711.6</td>
<td valign="top" align="char" char=".">683</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">12</td>
<td valign="top" align="left">A0767</td>
<td valign="top" align="left">08/14/19</td>
<td valign="top" align="left">IS 435</td>
<td valign="top" align="char" char=".">360.3</td>
<td valign="top" align="char" char=".">139,000</td>
<td valign="top" align="char" char=".">725.1</td>
<td valign="top" align="char" char=".">694.1</td>
<td valign="top" align="char" char=".">682.1</td>
<td valign="top" align="char" char=".">711.1</td>
<td valign="top" align="char" char=".">668</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">13</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">A4757/L0568</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">08/14/19</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">MO 291</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">352.7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">141,000</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">720.1</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">688.8</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">679.3</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">706.3</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt"><sup>e</sup>664</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t05n1"><label><sup>a</sup></label><p>River mile is the distance upstream on the Lower Missouri River, with river mile 0 at the confluence with the Mississippi River at St. Louis, Missouri. (<xref ref-type="fig" rid="fig01">fig. 1</xref>), at river mile&#x00A0;195.2 of the Upper Mississippi River.</p></fn>
<fn id="t05n2"><label><sup>b</sup></label><p>The average streamflow obtained while making the various velocity transects. The reported value is the streamflow computed using Global Navigation Satellite System (GNSS) essential fix data string as the reference, as described in the &#x201C;Surveying Methods&#x201D; section of the text.</p></fn>
<fn id="t05n3"><label><sup>c</sup></label><p>The statistical average of the surveyed channel-bed elevations.</p></fn>
<fn id="t05n4"><label><sup>d</sup></label><p>The minimum channel-bed elevation, not necessarily in any scour holes near the bridge.</p></fn>
<fn id="t05n5"><label><sup>e</sup></label><p>The minimum channel-bed elevation is in a scour hole near a substructural element at this site.</p></fn></table-wrap-foot>
</table-wrap>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 755&#x00A0;ft wide, extending across the active channel from bank to bank (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). The upstream end of the survey area was about 770&#x00A0;ft upstream from the centerline of structure A1800 (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). The channel-bed elevations ranged from about 698&#x00A0;to 719&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig07">fig.&#x00A0;7</xref>). A thalweg along the outside of the channel bend on the right (south) bank was about 15&#x00A0;ft deeper than the channel bed on the inside of the bend on the left (north) bank (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). Several medium to large dune features were detected in the middle of the channel along the left side of the thalweg, and the left (north) side and thalweg on the right (south) side were covered with numerous small dunes and ripples (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). As in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), a rock outcrop and stone revetment were present on the right (south) bank throughout the reach (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>).</p>
<fig id="fig06" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 6</label><caption><p>Bathymetric survey of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 6.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 635 bridge on August 13, 2019.</long-desc><graphic xlink:href="rol21-0068_fig06"/></fig>
<fig id="fig07" position="float" fig-type="figure"><?Figure Large?><label>Figure 7</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 7.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Interstate 635.</long-desc><graphic xlink:href="rol21-0068_fig07"/></fig>
<p>The scour hole near main channel pier&#x00A0;3 had a minimum channel-bed elevation of about 692&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), about 18&#x00A0;ft below the average channel bed immediately upstream from the pier (the value of the &#x201C;depth of scour hole from upstream channel bed&#x201D; in <xref ref-type="table" rid="t06">table&#x00A0;6</xref>; <xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>), and about 10&#x00A0;ft below the elevation of the bottom of the pier seal course of 702.28&#x00A0;ft (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicates that pier&#x00A0;3 is founded on shafts drilled 20&#x00A0;ft into bedrock, and about 40&#x00A0;ft of bed material are between the bottom of the scour hole and bedrock at the upstream face of pier&#x00A0;3 (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<table-wrap id="t06" orientation="landscape" position="float">
<label>Table 6</label><caption><title>Results near piers from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</title>
<p content-type="toc"><bold>Table 6.</bold>&#x2003;Results near piers from surveys on the Missouri River near Kansas City, Missouri, August 13&#x2013;14, 2019.</p>
<p>[All elevations are referenced to the North American Vertical Datum of 1988. MoDOT, Missouri Department of Transportation; --, not known/applicable]</p>
</caption>
<table rules="groups">
<col width="5.81%"/>
<col width="6.9%"/>
<col width="6.11%"/>
<col width="8.8%"/>
<col width="5.4%"/>
<col width="8.97%"/>
<col width="8.67%"/>
<col width="10.12%"/>
<col width="9.69%"/>
<col width="8.66%"/>
<col width="10.75%"/>
<col width="10.12%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Site number (<xref ref-type="fig" rid="fig01">fig. 1</xref>)</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">MoDOT structure number</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">MoDOT pier number</td>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Foundation information</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate minimum elevation in scour hole near pier,<sup>a</sup> in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate elevation of scour hole at upstream pier face, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate elevation of bedrock near pier, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Approximate distance between bottom of scour hole and bedrock, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Depth of scour hole from upstream channel bed, in feet</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-bottom: solid 0.50pt">Type</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Width, in feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Penetration into bedrock, in feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Seal course or pile cap bottom elevation, in feet</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">6</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">A1800</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">3</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Drilled shaft</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">28</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">20</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">702.28</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">692.1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">692</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">652</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">40</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">18</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">7</td>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)">A8340</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">706.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">707</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">638</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">69</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">4</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">688.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">688</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">638</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">50</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">--</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">710.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">710</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">628</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">82</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">8</td>
<td valign="top" align="left">A4649</td>
<td valign="top" align="left">2</td>
<td valign="top" align="left">Caisson</td>
<td valign="top" align="char" char=".">24</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">--</td>
<td valign="top" align="char" char=".">678.3</td>
<td valign="top" align="char" char=".">678</td>
<td valign="top" align="char" char=".">670</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="char" char=".">24</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">9</td>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)">A4060</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">696.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">698.6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">699</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">665</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">34</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">5</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">696.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">692.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">692</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">667</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">25</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">6</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">34</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">696.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">686.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)"><sup>b</sup>690</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">670</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)"><sup>b</sup>11</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10</td>
<td valign="top" align="left">A7650</td>
<td valign="top" align="left">Pylon</td>
<td valign="top" align="left">Drilled shaft</td>
<td valign="top" align="char" char=".">46</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">699.50</td>
<td valign="top" align="char" char=".">677.3</td>
<td valign="top" align="char" char=".">686</td>
<td valign="top" align="char" char=".">647</td>
<td valign="top" align="char" char=".">30</td>
<td valign="top" align="char" char=".">12</td>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">11</td>
<td rowspan="2" valign="top" align="left" style="background-color:rgb(217,217,217)">A5817</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">687.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">687.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">687</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">677</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">689.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">702.0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">702</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">657</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">45</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" scope="row">12</td>
<td rowspan="2" valign="top" align="left">A0767</td>
<td valign="top" align="left">7</td>
<td valign="top" align="left">Drilled shaft</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">20</td>
<td valign="top" align="char" char=".">689.26</td>
<td valign="top" align="char" char=".">677.8</td>
<td valign="top" align="char" char=".">678</td>
<td valign="top" align="char" char=".">660</td>
<td valign="top" align="char" char=".">18</td>
<td valign="top" align="char" char=".">12</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">8</td>
<td valign="top" align="left">Drilled shaft</td>
<td valign="top" align="char" char=".">28</td>
<td valign="top" align="char" char=".">20</td>
<td valign="top" align="char" char=".">689.26</td>
<td valign="top" align="char" char=".">694.2</td>
<td valign="top" align="char" char=".">(<sup>c</sup>)</td>
<td valign="top" align="char" char=".">648</td>
<td valign="top" align="char" char=".">46</td>
<td valign="top" align="char" char=".">(<sup>c</sup>)</td>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">13</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A4757</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drilled shaft</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">666.26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">663.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">664</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">619</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">45</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">L0568</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Caisson</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">--</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">664.7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)"><sup>b</sup>672</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">618</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">47</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)"><sup>b</sup>7</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t06n1"><label><sup>a</sup></label><p>The point of lowest elevation in the scour hole near the bridge pier, not necessarily at the upstream pier face.</p></fn>
<fn id="t06n2"><label><sup>b</sup></label><p>Scour hole at this pier was substantially affected by upstream pier.</p></fn>
<fn id="t06n3"><label><sup>c</sup></label><p>Unable to obtain data because of accumulated debris around pier.</p></fn></table-wrap-foot>
</table-wrap>
<fig id="fig08" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 8</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A1800 on Interstate 635 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 8.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A1800 on Interstate 635 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Interstate 635 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig08"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous nonflood survey on June 2, 2015 (<xref ref-type="fig" rid="fig09">fig. 9</xref>), indicates about 73&#x00A0;percent of the joint area of interest had detectable change, which means about 27&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed about equal between scour and deposition in the middle part of the channel from 2015 to 2019 in the DoD map; however, in the thalweg downstream from the bridge and along the left (north) bank throughout the reach, scour is dominant (<xref ref-type="fig" rid="fig09">fig.&#x00A0;9</xref>). The average difference between the bathymetric surfaces (the statistical mean value of the gridded raster surface [<xref ref-type="fig" rid="fig09">fig.&#x00A0;9</xref>] created from the difference between the 2019 and 2015 gridded raster bathymetric surfaces) was &#x2013;1.59&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate channel degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 72,900&#x00A0;cubic yards (yd<sup>3</sup>), and the net volume of fill was about 20,900&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 52,000&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge are not substantially different from one another for most of the cross section, except near the left bank where the 2019 section is substantially lower than all the previous sections (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>). The frequency distribution of bed elevations in 2019 also was similar to 2015 but with a higher percentage of cells at lower channel-bed elevations (<xref ref-type="fig" rid="fig07">fig.&#x00A0;7</xref>). The scour hole near pier&#x00A0;3 was of a very similar shape in 2019 and 2015 (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>), as evidenced by the overall area of &#x201C;no data&#x201D; or minimal change around the pier (<xref ref-type="fig" rid="fig09">fig.&#x00A0;9</xref>). The rock outcrop on the right (south) bank showed signs of minor scour upstream from the bridge (<xref ref-type="fig" rid="fig09">fig.&#x00A0;9</xref>). Although rock ultimately is an erodible material, its rate of erosion is substantially slower than that of sand and silt (<xref ref-type="bibr" rid="r2">Arneson and others, 2012</xref>). The stone revetment on the downstream right (south) bank showed no signs of substantial change (<xref ref-type="fig" rid="fig09">fig.&#x00A0;9</xref>). Substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<table-wrap id="t07" orientation="landscape" position="float">
<label>Table 7</label><caption><title>Summary information and bathymetric surface difference statistics from surveys on the Missouri River near Kansas City, Missouri, from August 13&#x2013;14, 2019, and previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>).</title>
<p content-type="toc"><bold>Table 7.</bold>&#x2003;Summary information and bathymetric surface difference statistics from surveys on the Missouri River near Kansas City, Missouri, from August 13&#x2013;14, 2019, and previous surveys.</p>
<p>[Dates are shown as month/day/year. All elevations are referenced to the North American Vertical Datum of 1988. MoDOT, Missouri Department of Transportation; Min, minimum; Max, maximum; A, <xref ref-type="bibr" rid="r9">Huizinga (2010)</xref>; B, <xref ref-type="bibr" rid="r11">Huizinga (2012)</xref>; C, <xref ref-type="bibr" rid="r15">Huizinga (2016)</xref>; D, <xref ref-type="bibr" rid="r18">Huizinga (2020a)</xref>]</p>
</caption>
<table rules="groups">
<col width="5.65%"/>
<col width="6.25%"/>
<col width="5%"/>
<col width="6.25%"/>
<col width="7.5%"/>
<col width="6.25%"/>
<col width="8.12%"/>
<col width="7.5%"/>
<col width="6.87%"/>
<col width="8.12%"/>
<col width="5.62%"/>
<col width="6.25%"/>
<col width="6.25%"/>
<col width="7.5%"/>
<col width="6.87%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Site number (<xref ref-type="fig" rid="fig01">fig. 1</xref>)</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">MoDOT structure number</td>
<td valign="middle" colspan="5" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Previous survey</td>
<td valign="middle" colspan="3" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Difference between 2019 survey and previous survey</td>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Statistics of differences between 2019 and previous bathymetric survey surfaces, in feet</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Max difference near upstream pier face(s),<sup>b,c</sup><break/>in feet</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-bottom: solid 0.50pt">Source of data</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Date</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Streamflow, in cubic feet per second</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Surveyed area, in 1&#x00D7;10<sup>6</sup> square feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Average water-surface elevation, in feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Streamflow, in cubic feet per second</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Surveyed area, in 1&#x00D7;10<sup>6</sup> square feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Average water-surface elevation, in feet</td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Min<sup>a,b</sup></td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Max<sup>a,b</sup></td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Average<sup>b</sup></td>
<td valign="middle" align="center" scope="col" style="border-bottom: solid 0.50pt">Standard deviation</td>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="3" valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">6</td>
<td rowspan="3" valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">A1800</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">A</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">03/15/10</td>
<td valign="top" align="left" style="border-top: solid 0.50pt"><sup>d</sup>103,000</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">1.134</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">734.8</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">9,000</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">0.111</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x2212;2.9</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x2212;15.3</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">11.1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x2212;2.93</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">3.52</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x2212;5.1</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">B</td>
<td valign="top" align="left">07/16/11</td>
<td valign="top" align="left">213,000</td>
<td valign="top" align="char" char=".">1.209</td>
<td valign="top" align="char" char=".">745.3</td>
<td valign="top" align="char" char=".">&#x2212;101,000</td>
<td valign="top" align="char" char=".">0.036</td>
<td valign="top" align="char" char=".">&#x2212;13.4</td>
<td valign="top" align="char" char=".">&#x2212;21.5</td>
<td valign="top" align="char" char=".">17.4</td>
<td valign="top" align="char" char=".">&#x2212;1.77</td>
<td valign="top" align="char" char=".">4.39</td>
<td valign="top" align="char" char=".">&#x2212;2.2</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">C</td>
<td valign="top" align="left">06/02/15</td>
<td valign="top" align="left">73,000</td>
<td valign="top" align="char" char=".">1.227</td>
<td valign="top" align="char" char=".">730.4</td>
<td valign="top" align="char" char=".">39,000</td>
<td valign="top" align="char" char=".">0.018</td>
<td valign="top" align="char" char=".">1.5</td>
<td valign="top" align="char" char=".">&#x2212;16.0</td>
<td valign="top" align="char" char=".">10.4</td>
<td valign="top" align="char" char=".">&#x2212;1.59</td>
<td valign="top" align="char" char=".">3.01</td>
<td valign="top" align="char" char=".">&#x2212;2.7</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">7</td>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)">A8340</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">03/15/10</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)"><sup>d</sup>103,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.165</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">733.7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.172</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;16.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">46.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.33</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5.97</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)"><sup>e</sup>27.5</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">B</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">07/16/11</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">213,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.326</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">743.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;99,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.011</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;13.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;25.6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">41.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2.27</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5.04</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)"><sup>e</sup>23.8</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">D</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">05/22/17</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">140,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.351</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">736.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;26,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;0.013</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;6.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;26.6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28.7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1.90</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.93</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7.4</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" scope="row">8</td>
<td rowspan="3" valign="top" align="left">A4649</td>
<td valign="top" align="left">A</td>
<td valign="top" align="left">03/16/10</td>
<td valign="top" align="left">127,000</td>
<td valign="top" align="char" char=".">1.485</td>
<td valign="top" align="char" char=".">727.9</td>
<td valign="top" align="char" char=".">&#x2212;1,000</td>
<td valign="top" align="char" char=".">0.041</td>
<td valign="top" align="char" char=".">1.1</td>
<td valign="top" align="char" char=".">&#x2212;22.8</td>
<td valign="top" align="char" char=".">45.7</td>
<td valign="top" align="char" char=".">0.75</td>
<td valign="top" align="char" char=".">3.96</td>
<td valign="top" align="char" char=".">1.6</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">B</td>
<td valign="top" align="left">07/17/11</td>
<td valign="top" align="left">217,000</td>
<td valign="top" align="char" char=".">1.471</td>
<td valign="top" align="char" char=".">737.6</td>
<td valign="top" align="char" char=".">&#x2212;91,000</td>
<td valign="top" align="char" char=".">0.055</td>
<td valign="top" align="char" char=".">&#x2212;8.6</td>
<td valign="top" align="char" char=".">&#x2212;33.4</td>
<td valign="top" align="char" char=".">32.5</td>
<td valign="top" align="char" char=".">&#x2212;4.91</td>
<td valign="top" align="char" char=".">3.73</td>
<td valign="top" align="char" char=".">&#x2212;13.4</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">C</td>
<td valign="top" align="left">06/02/15</td>
<td valign="top" align="left">94,500</td>
<td valign="top" align="char" char=".">1.524</td>
<td valign="top" align="char" char=".">724.6</td>
<td valign="top" align="char" char=".">31,500</td>
<td valign="top" align="char" char=".">0.002</td>
<td valign="top" align="char" char=".">4.4</td>
<td valign="top" align="char" char=".">&#x2212;42.7</td>
<td valign="top" align="char" char=".">38.5</td>
<td valign="top" align="char" char=".">&#x2212;0.13</td>
<td valign="top" align="char" char=".">3.60</td>
<td valign="top" align="char" char=".">&#x2212;3.2</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">9</td>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)">A4060</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">03/16/10</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">126,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.492</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">727.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.014</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;33.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22.4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1.58</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.88</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;9.5</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">B</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">07/17/11</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">217,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.434</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">737.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;91,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.072</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;8.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;32.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">25.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3.64</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;9.8</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">06/03/15</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">93,900</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.389</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">723.7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32,100</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.117</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;40.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2.56</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.52</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7.3</td>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" scope="row">10</td>
<td rowspan="2" valign="top" align="left">A7650</td>
<td valign="top" align="left">B</td>
<td valign="top" align="left">07/17/11</td>
<td valign="top" align="left">217,000</td>
<td valign="top" align="char" char=".">1.372</td>
<td valign="top" align="char" char=".">736.4</td>
<td valign="top" align="char" char=".">&#x2212;75,000</td>
<td valign="top" align="char" char=".">&#x2212;0.051</td>
<td valign="top" align="char" char=".">&#x2212;8.2</td>
<td valign="top" align="char" char=".">&#x2212;40.2</td>
<td valign="top" align="char" char=".">26.7</td>
<td valign="top" align="char" char=".">&#x2212;1.29</td>
<td valign="top" align="char" char=".">5.44</td>
<td valign="top" align="char" char=".">6.8</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">C</td>
<td valign="top" align="left">06/03/15</td>
<td valign="top" align="left">97,100</td>
<td valign="top" align="char" char=".">1.318</td>
<td valign="top" align="char" char=".">723.1</td>
<td valign="top" align="char" char=".">44,900</td>
<td valign="top" align="char" char=".">0.003</td>
<td valign="top" align="char" char=".">5.1</td>
<td valign="top" align="char" char=".">&#x2212;31.6</td>
<td valign="top" align="char" char=".">16.9</td>
<td valign="top" align="char" char=".">&#x2212;3.48</td>
<td valign="top" align="char" char=".">3.07</td>
<td valign="top" align="char" char=".">7.1</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">11</td>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)">A5817</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">03/17/10</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">124,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.666</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">724.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;0.022</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;17.0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1.38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.90</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7.1</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">B</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">07/18/11</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">212,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.609</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">733.7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;70,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.035</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7.2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;18.0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17.0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4.76</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.15</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;17.1</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">06/03/15</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">103,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.572</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">721.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">39,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.071</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;15.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18.4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1.44</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.07</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7.3</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" scope="row">12</td>
<td rowspan="3" valign="top" align="left">A0767</td>
<td valign="top" align="left">A</td>
<td valign="top" align="left">03/17/10</td>
<td valign="top" align="left">123,000</td>
<td valign="top" align="char" char=".">1.540</td>
<td valign="top" align="char" char=".">722.5</td>
<td valign="top" align="char" char=".">16,000</td>
<td valign="top" align="char" char=".">&#x2212;0.012</td>
<td valign="top" align="char" char=".">2.6</td>
<td valign="top" align="char" char=".">&#x2212;23.6</td>
<td valign="top" align="char" char=".">25.3</td>
<td valign="top" align="char" char=".">&#x2212;4.47</td>
<td valign="top" align="char" char=".">4.40</td>
<td valign="top" align="char" char=".">3.3</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">B</td>
<td valign="top" align="left">07/18/11</td>
<td valign="top" align="left">212,000</td>
<td valign="top" align="char" char=".">1.540</td>
<td valign="top" align="char" char=".">732.3</td>
<td valign="top" align="char" char=".">&#x2212;73,000</td>
<td valign="top" align="char" char=".">&#x2212;0.012</td>
<td valign="top" align="char" char=".">&#x2212;7.2</td>
<td valign="top" align="char" char=".">&#x2212;17.0</td>
<td valign="top" align="char" char=".">35.0</td>
<td valign="top" align="char" char=".">&#x2212;2.28</td>
<td valign="top" align="char" char=".">4.91</td>
<td valign="top" align="char" char=".">2.3</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" scope="row">C</td>
<td valign="top" align="left">06/04/15</td>
<td valign="top" align="left">119,000</td>
<td valign="top" align="char" char=".">1.464</td>
<td valign="top" align="char" char=".">721.6</td>
<td valign="top" align="char" char=".">20,000</td>
<td valign="top" align="char" char=".">0.063</td>
<td valign="top" align="char" char=".">3.5</td>
<td valign="top" align="char" char=".">&#x2212;25.3</td>
<td valign="top" align="char" char=".">24.3</td>
<td valign="top" align="char" char=".">&#x2212;4.17</td>
<td valign="top" align="char" char=".">4.10</td>
<td valign="top" align="char" char=".">3.6</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">13</td>
<td rowspan="3" valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">A4757/ L0568</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">A</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">03/18/10</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">120,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.455</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">717.2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">21,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;0.047</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;27.3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23.8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2.82</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.92</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6.3</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="row">B</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">07/19/11</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">212,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.359</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">726.7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;71,000</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.049</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;6.6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;24.4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">38.0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.49</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8.3</td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">C</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">06/04/15</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">112,000</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">1.401</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">715.9</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">29,000</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">0.007</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">4.2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;30.8</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">35.6</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;1.51</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">2.93</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;2.4</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t07n1"><label><sup>b</sup></label><p>The maximum or minimum value of change likely is near a vertical pier face and affected by minor position variances.</p></fn>
<fn id="t07n1_1"><label><sup>b</sup></label><p>A positive value represents deposition, a negative value represents scour.</p></fn>
<fn id="t07n2"><label><sup>c</sup></label><p>The maximum difference near the upstream pier face was taken near the location of the &#x201C;approximate elevation of scour hole at upstream pier face&#x201D; in <xref ref-type="table" rid="t06">table 6</xref>.</p></fn>
<fn id="t07n3"><label><sup>d</sup></label><p>This streamflow is the value reported for the streamgage at St. Joseph, Missouri, for March 14, 2010, and does not match the value reported in <xref ref-type="bibr" rid="r9">Huizinga (2010)</xref>. The value reported in <xref ref-type="bibr" rid="r9">Huizinga (2010)</xref> for March 15, 2010, is for the streamgage at Kansas City, and includes inflow from the Kansas River and therefore would be higher than the streamflow measured at this site upstream from the confluence. The previous day at the St. Joseph streamgage was used to account for travel time between St. Joseph and Kansas City.</p></fn>
<fn id="t07n4"><label><sup>e</sup></label><p>Near the location of a new pier/bent, compared at the location of the old pier in the previous survey.</p></fn></table-wrap-foot>
</table-wrap>
<fig id="fig09" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 9</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and June 2, 2015.</p><p content-type="toc"><bold>Figure 9.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and June 2, 2015.</p></caption>
<long-desc>Difference between surveys at Interstate 635 bridge on August 13, 2019, and June 2, 2015.</long-desc><graphic xlink:href="rol21-0068_fig09"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous flood survey on July 16, 2011 (<xref ref-type="fig" rid="fig10">fig.&#x00A0;10</xref>), indicates about 85&#x00A0;percent of the joint area of interest had detectable change, which means about 15&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation is apparent from 2011 to 2019 in the DoD map, particularly near the thalweg where large dune features were present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>). Whereas scour of as much as 15&#x00A0;ft seems dominant on the left (north) side of the channel in the DoD map, deposition of as much as 10&#x00A0;ft seems dominant in the thalweg (<xref ref-type="fig" rid="fig10">fig.&#x00A0;10</xref>). The average difference between the bathymetric surfaces was &#x2013;1.77&#x00A0;ft (<xref ref-type="table" rid="t07">table 7</xref>), indicating moderate net channel degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 110,500&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 43,500&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 67,000&#x00A0;yd<sup>3</sup> of sediment between 2011 and 2019. As with the 2015 survey, the cross sections from the two surveys along the upstream face of the bridge are not substantially different from one another for most of the cross section, except near the left bank where the 2019 section is substantially lower than all the previous sections (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>). The frequency distribution of bed elevations in 2019 also was similar in shape but narrower to 2011, and had a higher percentage of cells at the middle channel-bed elevations (<xref ref-type="fig" rid="fig07">fig.&#x00A0;7</xref>). As with the 2015 survey, the scour hole near pier&#x00A0;3 was of a very similar shape in 2019 and 2011 (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>), again as evidenced by the overall area of &#x201C;no data&#x201D; or minimal change around the pier in the DoD map (<xref ref-type="fig" rid="fig10">fig.&#x00A0;10</xref>). The rock outcrop on the right (south) bank showed signs of more substantial scour upstream from the bridge, and the stone revetment on the downstream right (south) bank showed signs of minor scour (<xref ref-type="fig" rid="fig10">fig.&#x00A0;10</xref>). As with the previous DoD map, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig10" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 10</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and July 16, 2011.</p><p content-type="toc"><bold>Figure 10.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and July 16, 2011.</p></caption>
<long-desc>Difference between surveys at Interstate 635 bridge on August 13, 2019, and July 16, 2011.</long-desc><graphic xlink:href="rol21-0068_fig10"/></fig>
<p>The difference between the survey on August 13, 2019, and the earliest nonflood survey on March 15, 2010 (<xref ref-type="fig" rid="fig11">fig. 11</xref>), indicates about 87&#x00A0;percent of the joint area of interest had detectable change, which means about 13&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Scour is dominant throughout most of the reach between 2010 and 2019 in the DoD map, except near some dune features present in the middle of the channel in 2010 and near pier&#x00A0;3 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>; <xref ref-type="fig" rid="fig11">fig.&#x00A0;11</xref>). The average difference between the bathymetric surfaces was &#x2013;2.93&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial channel degradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 122,700&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 20,500&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 102,200&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. Whereas the cross sections from the two surveys along the upstream face of the bridge are not substantially different from one another for most of the cross section, as with all the surveys the 2019 section is substantially lower than all the previous sections near the left bank (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>). The frequency distribution of bed elevations in 2019 was very similar to 2010 for elevations below about 708&#x00A0;ft; however, above the 2019 distribution has a higher percentage of cells at a lower channel-bed elevation than 2010 (<xref ref-type="fig" rid="fig07">fig.&#x00A0;7</xref>). The scour hole near pier&#x00A0;3 was deeper and wider in 2010 than in 2019 (<xref ref-type="fig" rid="fig08">fig.&#x00A0;8</xref>), as evidenced by large horseshoe-shaped area of deposition around the pier in the DoD map (<xref ref-type="fig" rid="fig11">fig.&#x00A0;11</xref>). The rock outcrop on the right (south) bank showed signs of moderate scour upstream from the bridge, and the stone revetment on the downstream right (south) bank showed signs of minor scour (<xref ref-type="fig" rid="fig11">fig.&#x00A0;11</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig11" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 11</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and March 15, 2010.</p><p content-type="toc"><bold>Figure 11.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019, and March 15, 2010.</p></caption>
<long-desc>Difference between surveys at Interstate 635 bridge on August 13, 2019, and March 15, 2010.</long-desc><graphic xlink:href="rol21-0068_fig11"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the reach (<xref ref-type="fig" rid="fig12">fig.&#x00A0;12</xref>). A maximum velocity of about 11&#x00A0;feet per second (ft/s) was present in the thalweg immediately upstream from the bridge, and a minimum of 3&#x00A0;ft/s was present along the inside of the bend on the left (north) bank (<xref ref-type="fig" rid="fig12">fig.&#x00A0;12</xref>). The wake vortices downstream from pier&#x00A0;3 were not pronounced and seemed to be no greater than the general nonuniformity of flow observed in the channel (<xref ref-type="fig" rid="fig12">fig.&#x00A0;12</xref>). Minor turbulence was present in all the sections (<xref ref-type="fig" rid="fig12">fig.&#x00A0;12</xref>).</p>
<fig id="fig12" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 12</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 12.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A1800 on Interstate 635 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 635 bridge on August 13, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig12"/></fig>
</sec>
<sec>
<title>Structure A8340 on U.S. Highway 69</title>
<p>Structure A8340 (site&#x00A0;7; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on U.S.&#x00A0;Highway&#x00A0;69 crosses the Missouri River at RM&#x00A0;372.6, on the northwestern side of Kansas City (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 13, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GNSS tide solution, was 730.6&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). Streamflow on the Missouri River was about 114,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,550&#x00A0;ft long and averaged about 875&#x00A0;ft wide, extending across the active channel from bank to bank (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). The upstream end of the survey area was about 680&#x00A0;ft upstream from the centerline of structure A8340 (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). The channel-bed elevations ranged from about 698&#x00A0;to 717&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>), except near the central main channel bent&#x00A0;4 of structure A8340 (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). There was a defined thalweg along the toe of the right (south) bank, which was about 12&#x00A0;ft deeper than the channel bed in the middle of the channel (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). A series of medium dunes was present in the middle of the channel, and numerous other small dunes and ripples were present throughout the rest of the channel (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). As in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>), stone revetment was present on the right (south) bank throughout the reach, and two spur dikes were present on the left (north) bank (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). Partial remnants of the pier from old structure A0450 were evident to the right and downstream from bent&#x00A0;4 of structure A8340 (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>).</p>
<fig id="fig13" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 13</label><caption><p>Bathymetric survey of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 13.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at U.S. Highway 69 bridge on August 13, 2019.</long-desc><graphic xlink:href="rol21-0068_fig13"/></fig>
<fig id="fig14" position="float" fig-type="figure"><?Figure Large?><label>Figure 14</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2017 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, respectively).</p><p content-type="toc"><bold>Figure 14.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2017.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at U.S. Highway 69.</long-desc><graphic xlink:href="rol21-0068_fig14"/></fig>
<p>A local scour hole near bent&#x00A0;4 had an approximate minimum channel-bed elevation of about 688&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), the minimum elevation for the surveyed area (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>), and about 17&#x00A0;ft below the average channel bed immediately upstream from the bent (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>; <xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>). A local scour hole near bent&#x00A0;5 had a minimum elevation of 707&#x00A0;ft, about 5&#x00A0;ft below the average channel bed immediately upstream from the pier (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Bent&#x00A0;3 is surrounded by the rock revetment on the right (south) bank, but a very small depression of about 3&#x00A0;ft was present in the revetment near the upstream face of the upstream column (<xref ref-type="fig" rid="fig13">fig.&#x00A0;13</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicates that all the main channel bents of structure A8340 are shafts drilled about 23&#x00A0;to 28&#x00A0;ft into bedrock and have about 50&#x00A0;ft of bed material between the bottom of the scour hole and bedrock at bent&#x00A0;4 (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>; <xref ref-type="table" rid="t06">table 6</xref>); bents&#x00A0;5 and 3 have about 69&#x00A0;and 82&#x00A0;ft of bed material between the bottom of the scour hole and bedrock, respectively (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig15" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 15</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A8340 on U.S.&#x00A0;Highway 69 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 15.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A8340 on U.S.&#x00A0;Highway 69 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the U.S. Highway 69 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig15"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous nonflood survey on May 22, 2017 (<xref ref-type="fig" rid="fig16">fig.&#x00A0;16</xref>), indicates about 93&#x00A0;percent of the joint area of interest had detectable change, which means only 7&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation appears to be predominately scour from 2017 to 2019 in the DoD map, except downstream from the spur dikes and in the troughs of dunes present in the 2017 survey (<xref ref-type="bibr" rid="r18">Huizinga, 2020a</xref>; <xref ref-type="fig" rid="fig16">fig.&#x00A0;16</xref>). The average difference between the bathymetric surfaces was &#x2013;1.90&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate channel degradation between the 2017 and 2019 surveys. The net volume of cut in the reach from 2017 to 2019 was about 119,600&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 33,900&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 85,700&#x00A0;yd<sup>3</sup> of sediment between 2017 and 2019. The cross sections from the two surveys along the upstream face of the bridge indicate a nearly uniform lowering of about 5&#x00A0;ft for most of the cross section (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>). The frequency distribution of bed elevations in 2019 was similar in shape to 2017 but with a higher percentage of cells at lower channel-bed elevations (<xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>). The scour holes near main channel bents&#x00A0;4 and 5 were of a very similar shape in 2019 and 2017 (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>), as evidenced by the overall area of similar change around the bents in the DoD map (<xref ref-type="fig" rid="fig16">fig.&#x00A0;16</xref>). The stone revetment on the right (south) bank also showed signs of nearly uniform minor scour (<xref ref-type="fig" rid="fig16">fig.&#x00A0;16</xref>).</p>
<fig id="fig16" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 16</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and May 22, 2017.</p><p content-type="toc"><bold>Figure 16.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and May 22, 2017.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 69 bridge on August 13, 2019, and May 22, 2017.</long-desc><graphic xlink:href="rol21-0068_fig16"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous flood survey on July 16, 2011 (<xref ref-type="fig" rid="fig17">fig. 17</xref>), indicates about 88&#x00A0;percent of the joint area of interest had detectable change, which means about 12&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation is again apparent from 2011 to 2019 in the DoD map, with scour predominant throughout the reach except for substantial deposition at the former location of the old bridge piers near bent 4 and in the downstream thalweg and the troughs of dunes present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>). Whereas scour of greater than 10&#x00A0;ft appears dominant on the left (north) side of the channel in the DoD map, deposition of as much as 10&#x00A0;ft occurred in the thalweg, and deposition of more than 20 ft occurred downstream from the downstream spur dike (<xref ref-type="fig" rid="fig17">fig.&#x00A0;17</xref>). The average difference between the bathymetric surfaces was &#x2013;2.27&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial net channel degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 137,700&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 45,600&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 92,100&#x00A0;yd<sup>3</sup> of sediment between 2011 and 2019. As with the 2017 survey, the cross sections from the two surveys along the upstream face of the bridge indicate a nearly uniform lowering of 5&#x00A0;to 10&#x00A0;ft for most of the cross section except the location of the former pier (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>). The frequency distribution of bed elevations in 2019 also was similar in shape but slightly narrower to 2011, with a higher percentage of cells at the middle channel-bed elevations (<xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>). The differences in the frequency distribution of bed elevations in 2017 and 2019 from 2011 (<xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>) likely are a direct result of the new bridge bents, which are designed to be more hydrodynamic and less scour-inducing than the old bridge piers. The stone revetment on the right (south) bank also showed signs of nearly uniform minor scour in the DoD map (<xref ref-type="fig" rid="fig17">fig.&#x00A0;17</xref>).</p>
<fig id="fig17" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 17</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and July 16, 2011.</p><p content-type="toc"><bold>Figure 17.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and July 16, 2011.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 69 bridge on August 13, 2019, and July 16, 2011.</long-desc><graphic xlink:href="rol21-0068_fig17"/></fig>
<p>The difference between the survey on August 13, 2019, and the earliest nonflood survey on March 15, 2010 (<xref ref-type="fig" rid="fig18">fig.&#x00A0;18</xref>), indicates about 84&#x00A0;percent of the joint area of interest had detectable change, which means about 16&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation appeared about equal between scour and deposition from 2010 to 2019 in the DoD map, with scour predominant along the left (north) side of the channel and on the right (south) bank, and deposition predominant in the middle of the channel, particularly at the former location of the old bridge piers near bent 4, in the thalweg along the right (south) bank, and in the troughs of dunes present in the 2010 survey (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>; <xref ref-type="fig" rid="fig18">fig.&#x00A0;18</xref>). The average difference between the bathymetric surfaces was +1.33&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate channel aggradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 57,100&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 100,900&#x00A0;yd<sup>3</sup>, resulting in a net gain of about 43,800&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are substantially different from one another for most of the left side and become more similar to one another about midway between bents&#x00A0;3 and 4 (<xref ref-type="fig" rid="fig15">fig.&#x00A0;15</xref>). The frequency distribution of bed elevations in 2010 was somewhat unique compared to the other surveys, but the 2019 distribution was similar to 2010, except with a lower percentage of cells at a lower channel-bed elevation than 2010 (<xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>). As noted in the previous paragraph, the differences in the frequency distribution of bed elevations in 2017 and 2019 from 2011 and 2010 (<xref ref-type="fig" rid="fig14">fig.&#x00A0;14</xref>) likely are a direct result of the new bridge bents, which are designed to be more hydrodynamic and less scour-inducing than the old bridge piers. As with all the DoD maps for this site, stone revetment on the right (south) bank also showed signs of nearly uniform minor scour (<xref ref-type="fig" rid="fig18">fig.&#x00A0;18</xref>).</p>
<fig id="fig18" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 18</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and March 15, 2010.</p><p content-type="toc"><bold>Figure 18.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019, and March 15, 2010.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 69 bridge on August 13, 2019, and March 15, 2010.</long-desc><graphic xlink:href="rol21-0068_fig18"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the reach (<xref ref-type="fig" rid="fig19">fig.&#x00A0;19</xref>). A maximum velocity of about 10&#x00A0;ft/s was present in the upstream middle of the channel, and a minimum velocity of about 1&#x00A0;ft/s was present with flow reversal downstream from the various spur dikes in the reach (<xref ref-type="fig" rid="fig19">fig.&#x00A0;19</xref>). Minimal effect on the velocity was observed downstream from bent&#x00A0;4 (<xref ref-type="fig" rid="fig19">fig.&#x00A0;19</xref>), indicating the new pier design is appropriately hydrodynamic. Minor turbulence was present in all the sections (<xref ref-type="fig" rid="fig19">fig.&#x00A0;19</xref>).</p>
<fig id="fig19" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 19</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 19.</bold>&#x2003;Map showing the bathymetry and vertically averaged velocities of the Missouri River channel near structure A8340 on U.S.&#x00A0;Highway 69 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at U.S. Highway 69 bridge on August 13, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig19"/></fig>
</sec>
<sec>
<title>Structure A4649 on U.S. Highway 169</title>
<p>Structure A4649 (site&#x00A0;8; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on U.S.&#x00A0;Highway 169 crosses the Missouri River at RM&#x00A0;366.2, immediately north of downtown Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 13, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GNSS tide solution, was 729.0&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). Streamflow on the Missouri River was about 126,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,660&#x00A0;ft long and averaged about 910&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). The upstream end of the survey area was about 720&#x00A0;ft upstream from the centerline of structure A4649 at pier&#x00A0;2 (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). The channel-bed elevations ranged from about 689&#x00A0;to 719&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig21">fig.&#x00A0;21</xref>), except near pier&#x00A0;2 of structure A4649, the various railroad bridge piers, and the concrete nose upstream from the railroad bridge turntable pier (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). A deep thalweg on the right (south) bank on the upstream end of the surveyed area was about 20&#x00A0;ft deeper than the channel bed in the middle of the channel (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). The thalweg became shallower and shifted to the left at the bridges and downstream (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), remnants of piers from an old bridge were evident downstream from the existing railroad bridge (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). Numerous medium and small dunes and ripples were detected throughout the channel, with slightly larger features in the channel thalweg upstream from structure A4649 and on the left side of the channel downstream from the railroad bridge (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>). Also as in previous surveys, stone revetment was present on the right (south) bank throughout the reach (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>).</p>
<fig id="fig20" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 20</label><caption><p>Bathymetric survey of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 20.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at U.S. Highway 169 bridge on August 13, 2019.</long-desc><graphic xlink:href="rol21-0068_fig20"/></fig>
<fig id="fig21" position="float" fig-type="figure"><?Figure Large?><label>Figure 21</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 21.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at U.S. Highway 169.</long-desc><graphic xlink:href="rol21-0068_fig21"/></fig>
<p>A scour hole near main channel pier&#x00A0;2 (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>) had a minimum channel-bed elevation of about 678&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), about 24&#x00A0;ft below the average channel bed immediately upstream from the pier (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), the scour hole was more extensive around the right (south) side of the pier, with a submerged remnant of a structure near the left (north) downstream side of the pier (<xref ref-type="fig" rid="fig20">figs.&#x00A0;20</xref> and <xref ref-type="fig" rid="fig01.03">1.3<italic>A</italic></xref>), presumably a nose for the railroad bridge downstream similar to the concrete nose upstream from the railroad bridge turntable pier. Also, as in the previous surveys at this site, the remnants of the old railroad bridge piers were clearly defined, as were the piles of particulate rock debris around them. The remnant bridge pier downstream from the existing railroad bridge turntable pier had a maximum elevation of about 710&#x00A0;ft, which is about 13&#x00A0;ft above the channel bed immediately upstream from it and about 19&#x00A0;ft below the water surface at the time of the 2019 survey. Avoidance of this pier remnant might be difficult for large vessels in flow conditions lower than those on the day of the survey. The overall minimum channel-bed elevation was 676&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>) and was observed upstream from the left railroad bridge pier downstream from pier&#x00A0;2 of structure A4649. Information from bridge plans indicate that the main channel pier&#x00A0;2 of structure A4649 is a caisson on bedrock, and has about 8&#x00A0;ft of bed material between the bottom of the scour hole and the bottom of the caisson (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig22" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 22</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A4649 on U.S.&#x00A0;Highway 169 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 22.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A4649 on U.S.&#x00A0;Highway 169 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the U.S. Highway 169 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig22"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous nonflood survey on June 2, 2015 (<xref ref-type="fig" rid="fig23">fig.&#x00A0;23</xref>), indicates about 99&#x00A0;percent of the joint area of interest had detectable change, which means only 1&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. However, bed variation seems about equal between scour and deposition throughout the channel from 2015 to 2019 in the DoD map because deposition on the upstream left (north) side is balanced with scour in the middle (<xref ref-type="fig" rid="fig23">fig.&#x00A0;23</xref>). The average difference between the bathymetric surfaces was &#x2013;0.13&#x00A0;ft (<xref ref-type="table" rid="t07">table 7</xref>), indicating minimal channel degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 74,200&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 67,000&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 7,200&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar (<xref ref-type="fig" rid="fig22">fig. 22</xref>); there is deposition on the left end of the section and there is nearly uniform lowering of about 5&#x00A0;ft for most of the rest of the cross section. The frequency distribution of bed elevations in 2019 was wider than 2015 because a higher percentage of cells are at lower and higher channel-bed elevations (<xref ref-type="fig" rid="fig21">fig.&#x00A0;21</xref>). The scour hole near main channel pier&#x00A0;2 was of a similar shape in 2019 and 2015 (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>) but slightly deeper on the right (south) side as evidenced by the area of scour around that side of the pier in the DoD map (<xref ref-type="fig" rid="fig23">fig.&#x00A0;23</xref>). The stone revetment and bedrock outcrops on the right (south) bank showed signs of nearly uniform minor deposition throughout the surveyed reach (<xref ref-type="fig" rid="fig23">fig.&#x00A0;23</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig23" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 23</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and June 22, 2015.</p><p content-type="toc"><bold>Figure 23.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and June 22, 2015.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 169 bridge on August 13, 2019, and June 2, 2015.</long-desc><graphic xlink:href="rol21-0068_fig23"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous flood survey on July 17, 2011 (<xref ref-type="fig" rid="fig24">fig.&#x00A0;24</xref>), indicates about 83&#x00A0;percent of the joint area of interest had detectable change, which means about 17&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation is apparent from 2011 to 2019 in the DoD map, and scour was predominant throughout the reach except for moderate deposition in some localized scoured areas near the piers and the trough of a large dune present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>; <xref ref-type="fig" rid="fig24">fig.&#x00A0;24</xref>). The average difference between the bathymetric surfaces was &#x2013;4.91&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial net channel degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 216,700&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 6,000&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 210,700&#x00A0;yd<sup>3</sup> of sediment between 2011 and 2019. The cross sections from the two surveys along the upstream face of the bridge are substantially different except along the left side of the scour hole near pier&#x00A0;2 and on the right bank (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>). The frequency distribution of bed elevations in 2019 was similar in shape to 2011 but with a higher percentage of cells at lower elevations than in 2011 (<xref ref-type="fig" rid="fig21">fig.&#x00A0;21</xref>). The stone revetment and bedrock outcrops on the right (south) bank showed signs of localized scour in the DoD map, but much of the difference on the tops of the bedrock outcrop was within the uncertainties of the data (<xref ref-type="fig" rid="fig24">fig.&#x00A0;24</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig24" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 24</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and July 17, 2011.</p><p content-type="toc"><bold>Figure 24.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and July 17, 2011.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 169 bridge on August 13, 2019, and July 17, 2011.</long-desc><graphic xlink:href="rol21-0068_fig24"/></fig>
<p>The difference between the survey on August 13, 2019, and the earliest nonflood survey on March 16, 2010 (<xref ref-type="fig" rid="fig25">fig.&#x00A0;25</xref>), indicates about 74&#x00A0;percent of the joint area of interest had detectable change, which means about 26&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed about equal between scour and deposition from 2010 to 2019 in the DoD map, deposition was predominant along the left (north) side of the channel, and scour was predominant along the right (south) side (<xref ref-type="fig" rid="fig25">fig.&#x00A0;25</xref>). The average difference between the bathymetric surfaces was +0.75&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor channel aggradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 45,200&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 72,800&#x00A0;yd<sup>3</sup>, resulting in a net gain of about 27,600&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are substantially different from one another for most of the section to the left of pier&#x00A0;2 and are more similar to one another to the right of pier&#x00A0;2 (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>). The frequency distribution of bed elevations in 2019 was similar in shape but narrower than 2010 (<xref ref-type="fig" rid="fig21">fig.&#x00A0;21</xref>); however, the surveyed area was substantially wider in 2019 than in 2010 and extended higher on the channel banks. The stone revetment and bedrock outcrops on the right (south) bank showed signs of more substantial localized scour in the upstream reach in the DoD map, but much of the difference on the tops of the downstream bedrock outcrop was within the uncertainties of the data (<xref ref-type="fig" rid="fig25">fig.&#x00A0;25</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig25" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 25</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and March 16, 2010.</p><p content-type="toc"><bold>Figure 25.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and March 16, 2010.</p></caption>
<long-desc>Difference between surveys at U.S. Highway 169 bridge on August 13, 2019, and March 16, 2010.</long-desc><graphic xlink:href="rol21-0068_fig25"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow upstream from the structure A4649 ranging from a minimum of 2&#x00A0;ft/s along the inside of the bend on the upstream left (north) bank to a maximum velocity of about 10&#x00A0;ft/s in the channel thalweg along the outside of the bend on the right (south) bank, particularly near the bridges (<xref ref-type="fig" rid="fig26">fig.&#x00A0;26</xref>). Exceptions to uniform conditions include diagonal flows across the channel near structure A4649 (<xref ref-type="fig" rid="fig26">fig.&#x00A0;26</xref>), which may help explain the shift in the channel thalweg towards the left (north) bank through the reach. Substantial turbulence also was observed between structure A4649 and the railroad bridge and downstream from the railroad bridge piers (<xref ref-type="fig" rid="fig26">fig.&#x00A0;26</xref>). The rock piles near the right bank also appear to create turbulence (<xref ref-type="fig" rid="fig26">fig.&#x00A0;26</xref>).</p>
<fig id="fig26" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 26</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 26.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at U.S. Highway 169 bridge on August 13, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig26"/></fig>
<p>The history of scour observed near pier&#x00A0;2 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), and the nature of caisson foundations generally not being embedded in bedrock led MoDOT to install scour countermeasures around pier&#x00A0;2 during August&#x2013;October 2020. Partial surveys of the channel bed near pier&#x00A0;2 of structure A4649 were done before and after installation of these scour countermeasures to document and verify installation. The historical scour hole near pier&#x00A0;2 was clearly evident in the pre-installation survey on August 17, 2020 (<xref ref-type="fig" rid="fig27">fig.&#x00A0;27</xref>), but the difference between the survey on August 13, 2019, and the partial survey on August 17, 2020, indicates moderate deposition of 5&#x00A0;to 10&#x00A0;ft had occurred from 2019 to 2020 (<xref ref-type="fig" rid="fig28">fig.&#x00A0;28</xref>). The cross sections from the two surveys along the upstream face of the bridge also indicates this deposition from 2019 to 2020 (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>). The downstream edge of riprap blanket countermeasures installed around pier&#x00A0;2 was clearly evident in the post-installation survey on October 23, 2020 (<xref ref-type="fig" rid="fig29">figs.&#x00A0;29</xref>, <xref ref-type="fig" rid="fig01.04">1.4<italic>B</italic></xref>), and the difference between the pre- and post-installation surveys indicate the changes resulting from the installation (<xref ref-type="fig" rid="fig30">fig.&#x00A0;30</xref>). The net volume of cut in the partial reach from August 2019 to August 2020 was about 750&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 18,660&#x00A0;yd<sup>3</sup>, resulting in a net gain of about 17,910&#x00A0;yd<sup>3</sup> of sediment between August 2019 and August 2020 (<xref ref-type="fig" rid="fig28">fig. 28</xref>). However, the net volume of cut in the partial reach from August to October 2020 was about 6,300&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 5,000&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 1,300&#x00A0;yd<sup>3</sup> of sediment between August and October 2020 (<xref ref-type="fig" rid="fig30">fig.&#x00A0;30</xref>), despite installation of the countermeasures. The scour hole was effectively mitigated, with as much as 20&#x00A0;ft of deposition near the pier (<xref ref-type="fig" rid="fig30">fig.&#x00A0;30</xref>), including some deposition of material on top of the blanket upstream from the bridge (<xref ref-type="fig" rid="fig29">fig.&#x00A0;29</xref>); nevertheless, moderate scour occurred in much of the partial reach around the riprap blanket between August and October (<xref ref-type="fig" rid="fig30">fig.&#x00A0;30</xref>).</p>
<fig id="fig27" position="float" fig-type="figure"><?Figure Large?><label>Figure 27</label><caption><p>Bathymetric survey of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 17, 2020, before installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 27.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 17, 2020, before installation of scour countermeasures.</p></caption>
<long-desc>The Missouri River channel bottom near the main pier at U.S. Highway 169 bridge on August 17, 2020.</long-desc><graphic xlink:href="rol21-0068_fig27"/></fig>
<fig id="fig28" position="float" fig-type="figure"><?Figure Large?><label>Figure 28</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and August 17, 2020, before installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 28.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 13, 2019, and August 17, 2020, before installation of scour countermeasures.</p></caption>
<long-desc>Difference between surveys near the main pier at U.S. Highway 169 bridge on August 13, 2019, and August 17, 2020.</long-desc><graphic xlink:href="rol21-0068_fig28"/></fig>
<fig id="fig29" position="float" fig-type="figure"><?Figure Large?><label>Figure 29</label><caption><p>Bathymetric survey of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 29.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures.</p></caption>
<long-desc>The Missouri River channel bottom near the main pier at U.S. Highway 169 bridge on October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig29"/></fig>
<fig id="fig30" position="float" fig-type="figure"><?Figure Large?><label>Figure 30</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 17 and October 23, 2020, before and after installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 30.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A4649 on U.S.&#x00A0;Highway 169 in Kansas City, Missouri, on August 17 and October 23, 2020, before and after installation of scour countermeasures.</p></caption>
<long-desc>Difference between surveys near the main pier at U.S. Highway 169 bridge on August 17 and October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig30"/></fig>
</sec>
<sec>
<title>Structure A4060 on State Highway 9</title>
<p>Structure A4060 (site&#x00A0;9; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on State Highway&#x00A0;9 crosses the Missouri River at RM&#x00A0;365.5, immediately north of downtown Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), and is about 3,400 ft downstream from structure A4649 (site&#x00A0;8) on U.S.&#x00A0;Highway 169. The site was surveyed on August 13, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GPS tide solution, was 728.2&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). Streamflow on the Missouri River was about 126,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 900&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). Piers&#x00A0;5 and 6 were in the water and away from the banks, and the upstream end of the survey area was about 665 ft upstream from the centerline of structure A4060 at pier&#x00A0;6 (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). The channel-bed elevations ranged from about 690 to 715&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig32">fig.&#x00A0;32</xref>), except near the railroad bridge pier upstream from pier 6 of structure A4060 (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). A shallow but wide thalweg along the right (south) side of the surveyed area was about 10&#x00A0;to 15&#x00A0;ft deeper than the channel bed in the middle of the channel (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). A few medium dune features were detected in the middle of the channel upstream from the bridges, and numerous smaller dunes and ripples were present throughout the channel reach (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>). As in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), a stone revetment was present on the right (south) bank throughout the reach (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>).</p>
<fig id="fig31" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 31</label><caption><p>Bathymetric survey of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 31.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 9 bridge on August 13, 2019.</long-desc><graphic xlink:href="rol21-0068_fig31"/></fig>
<fig id="fig32" position="float" fig-type="figure"><?Figure Large?><label>Figure 32</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 32.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Missouri Highway 9.</long-desc><graphic xlink:href="rol21-0068_fig32"/></fig>
<p>Erosion near the left (north) bank resulted in a scour hole near main channel pier 4 on that bank (<xref ref-type="fig" rid="fig31">figs.&#x00A0;31</xref>, <xref ref-type="fig" rid="fig33">33</xref>) with a minimum channel-bed elevation of 699&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). A scour hole near main channel pier 5 (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>) had a minimum channel-bed elevation of about 692&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), about 4&#x00A0;ft below the elevation of the bottom of the pier seal course of 696.26&#x00A0;ft (<xref ref-type="fig" rid="fig33">fig.&#x00A0;33</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Near the right (south) main channel pier&#x00A0;6 (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>), a scour hole had a minimum channel-bed elevation of about 687&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), about 9&#x00A0;ft below the elevation of the bottom of the pier seal course of 696.26&#x00A0;ft (<xref ref-type="fig" rid="fig33">fig.&#x00A0;33</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). A substantially deeper scour hole was observed near the upstream railroad bridge pier (<xref ref-type="fig" rid="fig31">fig.&#x00A0;31</xref>), with a minimum elevation of about 678&#x00A0;ft, which is the overall minimum channel-bed elevation observed in this reach (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>). This deeper hole likely was the result of flow around the upstream railroad pier combine with flow over large sheet piling panels that were lying on the channel bottom on the right (south) side of pier first observed in the 2010 survey (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>), and seen in all subsequent surveys (<xref ref-type="bibr" rid="r11">Huizinga 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>). Information from bridge plans indicates that piers&#x00A0;4 through 6 are founded on shafts drilled 20&#x00A0;ft into bedrock, about 34&#x00A0;ft of bed material were between the bottom of the scour hole and bedrock at pier&#x00A0;4, about 25&#x00A0;ft of material were between the bottom of the scour hole and bedrock at pier&#x00A0;5, and about 17&#x00A0;ft of material were between the bottom of the scour hole and bedrock at pier&#x00A0;6 (<xref ref-type="fig" rid="fig33">fig.&#x00A0;33</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig33" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 33</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A4060 on State Highway 9 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 33.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A4060 on State Highway 9 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Missouri Highway 9 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig33"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous nonflood survey on June 3, 2015 (<xref ref-type="fig" rid="fig34">fig.&#x00A0;34</xref>), indicates about 81&#x00A0;percent of the joint area of interest had detectable change, which means about 19&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation is apparent from 2015 to 2019 in the DoD map, with scour predominant throughout the reach except along the left (north) side of the channel (<xref ref-type="fig" rid="fig34">fig.&#x00A0;34</xref>). The average difference between the bathymetric surfaces was &#x2013;2.56 ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate to substantial degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 143,100&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 37,300&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 105,800&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge also indicate these differences (<xref ref-type="fig" rid="fig33">fig. 33</xref>); there is localized scour near the left (north) bank, and there is nearly uniform lowering of about 10&#x00A0;ft between pier&#x00A0;6 and the right (south) bank. The frequency distribution of bed elevations in 2019 was wider than 2015, with a higher percentage of cells at lower and higher channel-bed elevations (<xref ref-type="fig" rid="fig32">fig.&#x00A0;32</xref>). The scour holes near main channel piers 5 and 6 were shallower on the left (north) side and deeper on the right (south) side of the pier as evidenced by the areas of deposition and scour near the piers in the DoD map (<xref ref-type="fig" rid="fig34">fig.&#x00A0;34</xref>). The scour of the left (north) bank near pier&#x00A0;4 also is clearly evident in the cross-section and DoD map (<xref ref-type="fig" rid="fig33">figs.&#x00A0;33</xref>, <xref ref-type="fig" rid="fig34">34</xref>). The stone revetment on the right (south) bank showed signs of very minor localized deposition and scour throughout the surveyed reach (<xref ref-type="fig" rid="fig34">fig.&#x00A0;34</xref>); most of the differences on the right (south) bank were within the uncertainties of the data. As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig34" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 34</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and June 3, 2015.</p><p content-type="toc"><bold>Figure 34.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and June 3, 2015.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 9 bridge on August 13, 2019, and June 3, 2015.</long-desc><graphic xlink:href="rol21-0068_fig34"/></fig>
<p>The difference between the survey on August 13, 2019, and the previous flood survey on July 17, 2011 (<xref ref-type="fig" rid="fig35">fig. 35</xref>), indicates about 90&#x00A0;percent of the joint area of interest had detectable change, which means about 10&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation is apparent from 2011 to 2019 in the DoD map, and scour is predominant throughout the reach except for moderate deposition in some localized scoured areas near the piers and in the channel downstream from the bridges in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>; <xref ref-type="fig" rid="fig35">fig.&#x00A0;35</xref>). The average difference between the bathymetric surfaces was &#x2013;3.64&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial net channel degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 186,100&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 14,600&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 171,500&#x00A0;yd<sup>3</sup> of sediment between 2011 and 2019. The cross sections from the two surveys along the upstream face of the bridge show some similarities near and between piers&#x00A0;5 and 6 and on the right (south) bank, and are substantially different elsewhere (<xref ref-type="fig" rid="fig33">fig.&#x00A0;33</xref>). The frequency distribution of bed elevations in 2019 was similar in shape to 2011, but with a higher percentage of cells at lower elevations than in 2011 (<xref ref-type="fig" rid="fig32">fig.&#x00A0;32</xref>). The stone revetment on the right (south) bank showed signs of nearly uniform minor scour in the DoD map (<xref ref-type="fig" rid="fig35">fig.&#x00A0;35</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig35" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 35</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and July 17, 2011.</p><p content-type="toc"><bold>Figure 35.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and July 17, 2011.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 9 bridge on August 13, 2019, and July 17, 2011.</long-desc><graphic xlink:href="rol21-0068_fig35"/></fig>
<p>The difference between the survey on August 13, 2019, and the earliest nonflood survey on March 16, 2010 (<xref ref-type="fig" rid="fig36">fig.&#x00A0;36</xref>), indicates about 85&#x00A0;percent of the joint area of interest had detectable change, which means about 15&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed more equal between scour and deposition from 2010 to 2019 in the DoD map than in the other DoD maps, deposition was predominant along the left (north) side of the channel, and scour was predominant along the right (south) side (<xref ref-type="fig" rid="fig36">fig.&#x00A0;36</xref>). However, the average difference between the bathymetric surfaces was &#x2013;1.58&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor to moderate channel degradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 109,900&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 44,200&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 65,700&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are substantially different from one another for most of the section, except near pier&#x00A0;5 and the right (south) bank (<xref ref-type="fig" rid="fig33">fig.&#x00A0;33</xref>). The frequency distribution of bed elevations in 2019 was similar in shape but slightly wider than 2010 (<xref ref-type="fig" rid="fig32">fig.&#x00A0;32</xref>); however, the surveyed area was substantially wider in 2019 than in 2010 and extended higher on the channel banks. The stone revetment on the right (south) bank showed signs of more substantial localized scour in the upstream reach in the DoD map (<xref ref-type="fig" rid="fig36">fig.&#x00A0;36</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig36" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 36</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and March 16, 2010.</p><p content-type="toc"><bold>Figure 36.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019, and March 16, 2010.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 9 bridge on August 13, 2019, and March 16, 2010.</long-desc><graphic xlink:href="rol21-0068_fig36"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the channel, ranging from about 1 to 9&#x00A0;ft/s (<xref ref-type="fig" rid="fig37">fig.&#x00A0;37</xref>). Exceptions to uniform conditions include substantial turbulence observed downstream from the railroad and highway bridge piers, and near the upstream left (north) bank (<xref ref-type="fig" rid="fig37">fig.&#x00A0;37</xref>).</p>
<fig id="fig37" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 37</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019.</p><p content-type="toc"><bold>Figure 37.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A4060 on State Highway 9 in Kansas City, Missouri, on August 13, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 9 bridge on August 13, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig37"/></fig>
</sec>
<sec>
<title>Structure A7650 on Interstate 35</title>
<p>Structure A7650 (site&#x00A0;10; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on Interstate 35 crosses the Missouri River at RM&#x00A0;364.7, immediately north of downtown Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), and is about 4,300&#x00A0;ft downstream from structure A4060 on State Highway 9 (site&#x00A0;9). The site was surveyed on August 14, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GPS tide solution, was 728.2&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). Streamflow on the Missouri River was about 142,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 875&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). The upstream end of the survey area was about 700&#x00A0;ft upstream from the centerline of structure A7650 at the main channel pylon (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). The channel-bed elevations ranged from about 690&#x00A0;to 714&#x00A0;ft for most of the surveyed area (5th to 95th percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig39">fig.&#x00A0;39</xref>), except near the pylon and downstream from the spur dike on the downstream left (north) bank (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). The shallow thalweg in the channel at upstream structure A4060 diminished, such that there was no definitive thalweg along either side of the channel upstream from structure A7650 (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). Numerous small to medium dunes and ripples were present throughout the channel, and downstream translation of the smaller dunes and ripples between survey passes were more pronounced at this site than at the upstream sites (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>). Downstream from the spur dike on the left (north) side of the downstream reach, the minimum channel-bed elevations of 671&#x00A0;ft was observed (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), stone revetment was present on the right (south) bank throughout the reach, including the apparent slumped area near the downstream end of the reach observed in the previous survey (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>).</p>
<fig id="fig38" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 38</label><caption><p>Bathymetric survey of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 38.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 35 bridge on August 14, 2019.</long-desc><graphic xlink:href="rol21-0068_fig38"/></fig>
<fig id="fig39" position="float" fig-type="figure"><?Figure Large?><label>Figure 39</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2011 and 2015 (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 39.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2011 and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Interstate 35.</long-desc><graphic xlink:href="rol21-0068_fig39"/></fig>
<p>As in previous surveys at this site (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), the main channel pylon seemed to be surrounded by a mound of rock riprap as a scour countermeasure, with a local minimum channel-bed elevation of about 677&#x00A0;ft near the downstream left (north) corner (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). The top of the riprap around the upstream face of the pylon was at an elevation of about 697&#x00A0;ft, which is slightly below the elevation of the bottom of the pylon seal course of 699.50&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>); the top of the riprap along the sides of the pylon is lower than at the upstream face (<xref ref-type="fig" rid="fig38">figs.&#x00A0;38</xref> and <xref ref-type="fig" rid="fig40">40</xref>). The minimum channel-bed elevation near the pylon was about 22&#x00A0;ft below the elevation of the bottom of the pylon seal course (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicates that the pylon is founded on shafts drilled 32&#x00A0;ft into bedrock, with about 30&#x00A0;ft of bed material between the bottom of the scour hole and bedrock (<xref ref-type="fig" rid="fig40">fig.&#x00A0;40</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig40" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 40</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A7650 on Interstate 35 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 40.</bold>&#x2003;Diagrams showing key features, substructural and superstructural details, and surveyed channel bed of structure A7650 on Interstate 35 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Interstate 35 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig40"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous nonflood survey on June 3, 2015 (<xref ref-type="fig" rid="fig41">fig.&#x00A0;41</xref>), indicates about 79&#x00A0;percent of the joint area of interest had detectable change, which means about 21&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation from 2015 to 2019 is moderate to substantial in the DoD map, and scour is predominant throughout the reach except small areas along the left (north) side of the channel and in the upstream right (south) part (<xref ref-type="fig" rid="fig41">fig.&#x00A0;41</xref>). The average difference between the bathymetric surfaces was &#x2013;3.48&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate to substantial degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 141,200&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 8,500&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 132,700&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar to each other but have uniform scour of about 5&#x00A0;ft between the pylon and the right (south) bank (<xref ref-type="fig" rid="fig40">fig.&#x00A0;40</xref>). The frequency distribution of bed elevations in 2019 was wider than 2015 because of a higher percentage of cells at lower channel-bed elevations (<xref ref-type="fig" rid="fig39">fig.&#x00A0;39</xref>). The scour hole near the main channel pylon was smaller and shallower upstream from the pylon but deeper downstream as evidenced by the areas of deposition and scour near the pylon in the DoD map (<xref ref-type="fig" rid="fig41">fig.&#x00A0;41</xref>). The rock riprap around the pylon base also indicated only minor differences, or differences within the uncertainty (<xref ref-type="fig" rid="fig41">fig.&#x00A0;41</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pylon footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section). The stone revetment on the right (south) bank showed signs of very minor localized deposition and scour, primarily downstream from the bridge (<xref ref-type="fig" rid="fig41">fig.&#x00A0;41</xref>); most of the differences on the right (south) bank were within the uncertainties of the data.</p>
<fig id="fig41" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 41</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, and June 3, 2015.</p><p content-type="toc"><bold>Figure 41.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, and June 3, 2015.</p></caption>
<long-desc>Difference between surveys at Interstate 35 bridge on August 14, 2019, and June 3, 2015.</long-desc><graphic xlink:href="rol21-0068_fig41"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous flood survey on July 17, 2011 (<xref ref-type="fig" rid="fig42">fig.&#x00A0;42</xref>), indicates about 74&#x00A0;percent of the joint area of interest had detectable change, which means about 26&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation appeared about equal between scour and deposition from 2011 to 2019 in the DoD map, with substantial scour downstream from the spur dike on the downstream left (north) side and in the upstream left (north) and downstream right (south) parts of the reach, and moderate to substantial deposition near the pylon and location of the old pier of structure L0734 (<xref ref-type="fig" rid="fig42">fig.&#x00A0;42</xref>). The average difference between the bathymetric surfaces was &#x2013;1.29&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor to moderate degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 86,900&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 39,600&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 47,300&#x00A0;yd<sup>3</sup> of sediment between 2011 and 2019. The cross sections from the two surveys along the upstream face of the bridge show the substantial variation in the surveyed sections (<xref ref-type="fig" rid="fig40">fig.&#x00A0;40</xref>). However, the frequency distribution of bed elevations in 2019 was remarkably similar in shape to 2011 (<xref ref-type="fig" rid="fig39">fig.&#x00A0;39</xref>). The scour hole near the main channel pylon was smaller and shallower upstream from the pylon, as evidenced by the area of deposition near the pylon in the DoD map (<xref ref-type="fig" rid="fig42">fig.&#x00A0;42</xref>). The rock riprap around the pylon base indicated moderate differences (<xref ref-type="fig" rid="fig42">fig.&#x00A0;42</xref>), and the cross-section along the upstream bridge face shows the riprap has lowered by as much as 7&#x00A0;ft since 2011 (<xref ref-type="fig" rid="fig40">fig.&#x00A0;40</xref>). As with previous DoD maps, substantial deposition or scour apparent at the faces of the pylon footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section). The stone revetment on the right (south) bank showed signs of nearly uniform minor scour in the DoD map (<xref ref-type="fig" rid="fig42">fig.&#x00A0;42</xref>).</p>
<fig id="fig42" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 42</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, and July 17, 2011.</p><p content-type="toc"><bold>Figure 42.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019, and July 17, 2011.</p></caption>
<long-desc>Difference between surveys at Interstate 35 bridge on August 14, 2019, and July 17, 2011.</long-desc><graphic xlink:href="rol21-0068_fig42"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout most of the reach, with velocities ranging from about 2&#x00A0;to 8&#x00A0;ft/s (<xref ref-type="fig" rid="fig43">fig.&#x00A0;43</xref>). Exceptions to uniform conditions include flow reversal along the left (north) bank near the upstream tributary and in the pool downstream from the spur dike (<xref ref-type="fig" rid="fig43">fig.&#x00A0;43</xref>). Substantial turbulence also was observed downstream from the main channel pylon (<xref ref-type="fig" rid="fig43">fig.&#x00A0;43</xref>), likely as a result of the pylon being skewed to flow. The velocities do not seem to be higher near the bulge in the left bank at the bridge.</p>
<fig id="fig43" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 43</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 43.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A7650 on Interstate 35 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 35 bridge on August 14, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig43"/></fig>
</sec>
<sec>
<title>Structure A5817 on State Highway 269</title>
<p>Structure A5817 (site&#x00A0;11; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on State Highway 269 crosses the Missouri River at RM&#x00A0;362.3, northeast of downtown Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 14, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GPS tide solution, was 726.5&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). Streamflow on the Missouri River was about 142,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 995&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). Piers&#x00A0;2 and 3 were in the water and away from the banks, and the upstream end of the survey area was about 670&#x00A0;ft upstream from the centerline of structure A5817 at pier&#x00A0;2 (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). The channel-bed elevations ranged from about 691&#x00A0;to 712&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig45">fig.&#x00A0;45</xref>). A moderately deep thalweg along the left (north) bank throughout the surveyed area contained evidence of bedrock exposure and was about 12&#x00A0;to 14&#x00A0;ft deeper than the channel bed in the middle of the channel (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). Numerous medium dune features were observed in the channel thalweg, and numerous medium to small dunes and ripples were present throughout the rest of the channel, decreasing in size towards the right (south) bank (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), stone revetment and bedrock outcrops were present on the left (north) bank throughout the reach (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>).</p>
<fig id="fig44" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 44</label><caption><p>Bathymetric survey of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 44.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 269 bridge on August 14, 2019.</long-desc><graphic xlink:href="rol21-0068_fig44"/></fig>
<fig id="fig45" position="float" fig-type="figure"><?Figure Large?><label>Figure 45</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 45.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Missouri Highway 269.</long-desc><graphic xlink:href="rol21-0068_fig45"/></fig>
<p>A scour hole near main channel pier&#x00A0;2 (<xref ref-type="fig" rid="fig44">fig. 44</xref>) had a minimum channel-bed elevation of about 687&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), which was about level with the elevation of the bottom of the pier seal course of 687.26&#x00A0;ft (<xref ref-type="fig" rid="fig46">fig.&#x00A0;46</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). The top of the pier footing was evident during the survey (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). The minor scour hole near pier&#x00A0;3 was difficult to discern from nearby small dunes and ripples (<xref ref-type="fig" rid="fig44">fig.&#x00A0;44</xref>). Information from bridge plans indicates that piers&#x00A0;2 and 3 of structure A5817 are founded on shafts drilled 20&#x00A0;ft into bedrock, with about 10&#x00A0;ft of bed material between the bottom of the scour hole and bedrock at pier&#x00A0;2 and about 45&#x00A0;ft of material at pier&#x00A0;3 (<xref ref-type="fig" rid="fig46">fig.&#x00A0;46</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig46" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 46</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A5817 on State Highway 269 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 46.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A5817 on State Highway 269 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Missouri Highway 269 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig46"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous nonflood survey on June 3, 2015 (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>), indicates about 89&#x00A0;percent of the joint area of interest had detectable change, which means about 11&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. There is moderate to substantial bed variation from 2015 to 2019 in the DoD map, with scour predominant throughout the middle of the reach, and deposition on both banks (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>). The average difference between the bathymetric surfaces was &#x2013;1.44&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor to moderate degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 114,200&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 40,800&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 73, 400&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar to each other but with uniform scour of 5&#x00A0;to 10&#x00A0;ft between the left (north) bank and pier&#x00A0;3 (<xref ref-type="fig" rid="fig46">fig.&#x00A0;46</xref>). The frequency distribution of bed elevations in 2019 was wider than 2015 because a higher percentage of cells were at lower and higher channel-bed elevations (<xref ref-type="fig" rid="fig45">fig.&#x00A0;45</xref>). The scour hole near the main channel pier&#x00A0;2 was deeper and wider than in 2015, as evidenced by the area of scour near that pier in the DoD map (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>). Alternatively, the change from 2015 to 2019 near main channel pier&#x00A0;3 was equivocal to the uncertainty on the left side of the footing, and there was deposition along the right side (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>). The bedrock outcrops and stone revetment on the left (north) bank showed signs of localized deposition throughout the reach between 2015 and 2019, which is somewhat unexpected (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>); however, the differences on the tops of some of the outcrops were within the uncertainties of the data, which implies there may be a horizontal offset to the 2019 data on the bank that is creating the appearance of deposition.</p>
<fig id="fig47" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 47</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and June 3, 2015.</p><p content-type="toc"><bold>Figure 47.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and June 3, 2015.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 269 bridge on August 14, 2019, and June 3, 2015.</long-desc><graphic xlink:href="rol21-0068_fig47"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous flood survey on July 18, 2011 (<xref ref-type="fig" rid="fig48">fig.&#x00A0;48</xref>), indicates about 89&#x00A0;percent of the joint area of interest had detectable change, which means about 11&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial bed variation was apparent from 2011 to 2019 in the DoD map, with substantial scour throughout the reach except along the left (north) bank and in the troughs of substantial dunes present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, fig.&#x00A0;48). The average difference between the bathymetric surfaces was &#x2013;4.76&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 268,900&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 20,000&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 248,900&#x00A0;yd<sup>3</sup> of sediment in the reach between 2011 and 2019. The cross sections from the two surveys along the upstream face of the bridge show the substantial difference in the surveyed sections (<xref ref-type="fig" rid="fig46">fig.&#x00A0;46</xref>). The frequency distribution of bed elevations in 2019 also was substantially different from 2011 (<xref ref-type="fig" rid="fig45">fig.&#x00A0;45</xref>). The DoD map shows the substantial scour throughout the reach, so the scour hole near main channel pier&#x00A0;2 is indistinguishable from the overall change between 2011 and 2019 (<xref ref-type="fig" rid="fig48">fig.&#x00A0;48</xref>). As with the DoD map for 2015 to 2019 (<xref ref-type="fig" rid="fig47">fig.&#x00A0;47</xref>), the bedrock outcrops and stone revetment on the left (north) bank showed signs of localized deposition throughout the reach between 2011 and 2019, which is somewhat unexpected (<xref ref-type="fig" rid="fig48">fig.&#x00A0;48</xref>); however, the differences on the tops of the outcrops were again within the uncertainties of the data, which implies there may be a horizontal offset to the 2019 data on the bank that is creating the appearance of deposition.</p>
<fig id="fig48" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 48</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and July 18, 2011.</p><p content-type="toc"><bold>Figure 48.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and July 18, 2011.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 269 bridge on August 14, 2019, and July 18, 2011.</long-desc><graphic xlink:href="rol21-0068_fig48"/></fig>
<p>The difference between the survey on August 14, 2019, and the earliest nonflood survey on March 17, 2010 (<xref ref-type="fig" rid="fig49">fig.&#x00A0;49</xref>), indicates about 80&#x00A0;percent of the joint area of interest had detectable change, which means about 20&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed nearly equal between scour and deposition from 2010 to 2019 in the DoD map, deposition was predominant along the thalweg on the left (north) side of the channel, and scour was predominant along the middle and right (south) side (<xref ref-type="fig" rid="fig49">fig.&#x00A0;49</xref>). However, the average difference between the bathymetric surfaces was &#x2013;1.38&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor to moderate channel degradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 111,500&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 50,100&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 61,400&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar to each other but had deposition of 5&#x00A0;to 10&#x00A0;ft between the left (north) bank and pier&#x00A0;2 and scour of 5&#x00A0;to 10&#x00A0;ft between piers&#x00A0;2 and 3 (<xref ref-type="fig" rid="fig46">fig.&#x00A0;46</xref>). The frequency distribution of bed elevations in 2019 was different from 2010 because a higher percentage of cells was at lower channel-bed elevations (<xref ref-type="fig" rid="fig45">fig.&#x00A0;45</xref>); however, the surveyed area was substantially wider in 2019 than in 2010 and extended higher on the channel banks, particularly on the right (south) side (<xref ref-type="fig" rid="fig49">fig.&#x00A0;49</xref>). The bedrock outcrops and stone revetment on the left (north) bank showed signs of minor, localized deposition, particularly in the upstream reach in the DoD map (<xref ref-type="fig" rid="fig49">fig.&#x00A0;49</xref>); however, much of the differences on the left (north) side of the channel&#x2014;and particularly the tops of the outcrops&#x2014;were again within the uncertainties of the data, as would be expected. As with previous DoD maps, substantial deposition or scour is apparent at the faces of the pier footings resulting from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig49" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 49</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and March 17, 2010.</p><p content-type="toc"><bold>Figure 49.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019, and March 17, 2010.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 269 bridge on August 14, 2019, and March 17, 2010.</long-desc><graphic xlink:href="rol21-0068_fig49"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the reach, ranging from about 3&#x00A0;ft/s along the inside of the bend on the right (south) bank to 9&#x00A0;ft/s in the thalweg along the left (north) bank (<xref ref-type="fig" rid="fig50">fig.&#x00A0;50</xref>). Exceptions to uniform flow include flows angled to the left (north) in the upstream part of the reach because of the bend in the channel (<xref ref-type="fig" rid="fig50">fig.&#x00A0;50</xref>). Moderate turbulence also was observed along the thalweg near the bedrock outcrops, along the inside of the bend along the right (south) bank, and downstream from pier&#x00A0;3 (<xref ref-type="fig" rid="fig50">fig.&#x00A0;50</xref>).</p>
<fig id="fig50" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 50</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 50.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A5817 on State Highway 269 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 269 bridge on August 14, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig50"/></fig>
</sec>
<sec>
<title>Structure A0767 on Interstate 435</title>
<p>Structure A0767 (site&#x00A0;12; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) on Interstate 435 crosses the Missouri River at RM 360.3, on the northeastern side Kansas City, Mo. (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 14, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GPS tide solution, was 725.1&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). Streamflow on the Missouri River was about 139,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 930&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). Piers&#x00A0;7 and 8 were in the water and away from the banks at structure A0767; however, as in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), pier 8 was immediately downstream from a spur dike and the upstream end of the pier was surrounded by a persistent substantial debris raft; however, bathymetric data could be obtained around the downstream end (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). A substantial and persistent sand bar also was present downstream from pier&#x00A0;8, as in previous surveys (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>; <xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). The upstream end of the survey area was about 660&#x00A0;ft upstream from the centerline of structure A0767 at pier&#x00A0;7 (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). The channel-bed elevations ranged from about 682&#x00A0;to 711&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>), except downstream from the tip of the spur dike and in the downstream reach near the rock outcrop on the left (north) bank (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). A shallow but wide thalweg was along the left (north) bank throughout the surveyed area, and became deeper in the downstream direction. The channel was filled with numerous medium dune features along the thalweg along the left (north) side of the channel and numerous small dunes and ripples throughout the rest of the channel, decreasing in size towards the banks (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), stone revetment and bedrock outcrops were present on the left (north) bank throughout the reach (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>).</p>
<fig id="fig51" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 51</label><caption><p>Bathymetric survey of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 51.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 435 bridge on August 14, 2019.</long-desc><graphic xlink:href="rol21-0068_fig51"/></fig>
<fig id="fig52" position="float" fig-type="figure"><?Figure Large?><label>Figure 52</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 52.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Interstate 435.</long-desc><graphic xlink:href="rol21-0068_fig52"/></fig>
<p>The scour hole near main channel pier&#x00A0;7 (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>) had a minimum channel-bed elevation of about 678&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), which was about 11&#x00A0;ft below the elevation of the bottom of the pier seal course of 689.26&#x00A0;ft (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). The undermined seal course are evident in a shaded triangulated irregular network (TIN) image of the right (south) side of pier&#x00A0;7 (<xref ref-type="fig" rid="fig01.08">fig.&#x00A0;1.8</xref>). The upstream end of pier&#x00A0;8 was embedded in the rock spur dike and could not be surveyed because of the persistent substantial debris raft (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>). The top of the footing on the downstream end of the pier was visible (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>), but the minimum channel elevation adjacent to the pier footing was about 694&#x00A0;ft, which was about 5&#x00A0;ft higher than the bottom of the seal course elevation of 689.26&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicates that piers&#x00A0;7 and 8 are founded on shafts drilled 20&#x00A0;ft into bedrock, with about 18&#x00A0;ft of bed material between the bottom of the scour hole and bedrock at pier&#x00A0;7 and about 46&#x00A0;ft of material at pier&#x00A0;8 (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). A substantial hole was present downstream from the tip of the spur dike, which contained the minimum channel elevation in the surveyed area of 668&#x00A0;ft (<xref ref-type="fig" rid="fig51">fig.&#x00A0;51</xref>; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>); however, this hole was more than 50&#x00A0;ft away from pier&#x00A0;8, and substantial alluvial material was present between the hole and the pier.</p>
<fig id="fig53" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 53</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A0767 on Interstate 435 crossing the Missouri River in Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 53.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A0767 on Interstate 435 crossing the Missouri River in Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Interstate 435 bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig53"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous nonflood survey on June 4, 2015 (<xref ref-type="fig" rid="fig54">fig.&#x00A0;54</xref>), indicates about 80&#x00A0;percent of the joint area of interest had detectable change, which means about 20&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation from 2015 to 2019 was moderate to substantial in the DoD map, deposition was predominant in the thalweg on the left (north) side, and scour was predominant throughout the middle and right (south) side of the reach (<xref ref-type="fig" rid="fig54">fig.&#x00A0;54</xref>). The average difference between the bathymetric surfaces was &#x2013;4.17&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 187,700&#x00A0;yd<sup>3</sup>, and the net volume of fill was only about 11,200&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 176,500&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the bridge indicate the trends from the DoD map, and deposition in the thalweg and scour was as much as 20&#x00A0;ft between pier 7 and the spur dike (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>). The frequency distribution of bed elevations in 2019 appeared similar to 2015 but had a higher percentage of cells at lower channel-bed elevations than 2015 (<xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>). The scour hole near main channel pier&#x00A0;7 was similar to that in 2015, as evidenced by the area of equivocal data in a horseshoe shape around the upstream end of that pier in the DoD map (<xref ref-type="fig" rid="fig54">fig.&#x00A0;54</xref>). However, on the downstream side of piers&#x00A0;7 and 8, substantial scour had occurred between 2015 and 2019 (<xref ref-type="fig" rid="fig54">fig.&#x00A0;54</xref>). The bedrock outcrops and stone revetment on the left (north) bank showed signs of localized scour and deposition throughout the reach between 2015 and 2019 (<xref ref-type="fig" rid="fig54">fig.&#x00A0;54</xref>), which was expected because of erroneous positioning during data collection in the 2015 survey (<xref ref-type="bibr" rid="r15">Huizinga, 2016</xref>) that created an offset of the data along the upstream left (north) bank between surveys.</p>
<fig id="fig54" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 54</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and June 4, 2015.</p><p content-type="toc"><bold>Figure 54.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and June 4, 2015.</p></caption>
<long-desc>Difference between surveys at Interstate 435 bridge on August 14, 2019, and June 4, 2015.</long-desc><graphic xlink:href="rol21-0068_fig54"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous flood survey on July 18, 2011 (<xref ref-type="fig" rid="fig55">fig.&#x00A0;55</xref>), indicates about 82&#x00A0;percent of the joint area of interest had detectable change, which means about 18&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation from 2015 to 2019 was moderate to substantial in the DoD map, deposition was predominant in the thalweg on the left (north) side and in the troughs of substantial dunes present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>), and scour was predominant throughout the middle and right (south) side of the reach (<xref ref-type="fig" rid="fig55">fig.&#x00A0;55</xref>). The average difference between the bathymetric surfaces was &#x2013;2.28&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate degradation between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 147,800&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 49,900&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 97,900&#x00A0;yd<sup>3</sup> of sediment in the reach between 2011 and 2019. The cross sections from the two surveys along the upstream face of the bridge show the substantial difference in the surveyed sections (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>). The frequency distribution of bed elevations in 2019 was remarkably similar to 2011 (<xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>), but a slightly higher percentage of cells was at a lower channel-bed elevation than 2011 in the middle of the range (<xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>). The scour hole near main channel pier&#x00A0;7 is shallower and narrower than in 2015, as indicated by the area of deposition in a horseshoe shape around that pier (<xref ref-type="fig" rid="fig55">fig.&#x00A0;55</xref>). The bedrock outcrops and stone revetment on the left (north) bank showed signs of localized deposition throughout the reach between 2011 and 2019 (<xref ref-type="fig" rid="fig55">fig.&#x00A0;55</xref>); however, the differences on the tops of the outcrops were within the uncertainties of the data, which implies there may be a slight horizontal offset to the 2019 data on the bank that is creating the appearance of deposition on the bank.</p>
<fig id="fig55" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 55</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and July 18, 2011.</p><p content-type="toc"><bold>Figure 55.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and July 18, 2011.</p></caption>
<long-desc>Difference between surveys at Interstate 435 bridge on August 14, 2019, and July 18, 2011.</long-desc><graphic xlink:href="rol21-0068_fig55"/></fig>
<p>The difference between the survey on August 14, 2019, and the earliest nonflood survey on March 17, 2010 (<xref ref-type="fig" rid="fig56">fig.&#x00A0;56</xref>), indicates about 80&#x00A0;percent of the joint area of interest had detectable change, which means about 20&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed nearly equal between scour and deposition from 2010 to 2019 in the DoD map, deposition was predominant along the thalweg on the left (north) side of the channel, and scour was predominant along the middle and right (south) side (<xref ref-type="fig" rid="fig56">fig.&#x00A0;56</xref>). However, the average difference between the bathymetric surfaces was &#x2013;4.47&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating substantial channel degradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 192,700&#x00A0;yd<sup>3</sup>, and the net volume of fill was only about 13,700&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 179,000&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar to each other between the left (north) bank and pier&#x00A0;7 but are substantially different between pier&#x00A0;7 and the spur dike (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>). The frequency distribution of bed elevations in 2019 seemed similar to 2010 but had a higher percentage of cells at lower channel-bed elevations than 2010 (<xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>); however, the surveyed area was substantially wider in 2019 than in 2010 and extended higher on the channel banks, particularly on the right (south) side (<xref ref-type="fig" rid="fig56">fig.&#x00A0;56</xref>). The bedrock outcrops and stone revetment on the left (north) bank showed signs of minor, localized deposition and scour (<xref ref-type="fig" rid="fig56">fig.&#x00A0;56</xref>); however, much of the differences on the left (north) side of the channel&#x2014;and particularly the tops of the outcrops&#x2014;were again within the uncertainties of the data, as would be expected. As with previous DoD maps, substantial deposition or scour apparent at the faces of the pier footings results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig56" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 56</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and March 17, 2010.</p><p content-type="toc"><bold>Figure 56.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019, and March 17, 2010.</p></caption>
<long-desc>Difference between surveys at Interstate 435 bridge on August 14, 2019, and March 17, 2010.</long-desc><graphic xlink:href="rol21-0068_fig56"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the reach, ranging from about 2&#x00A0;ft/s along the inside of the bend on the right (south) bank to 9&#x00A0;ft/s in the thalweg (<xref ref-type="fig" rid="fig57">fig.&#x00A0;57</xref>); however, turbulence and velocity reduction were observed downstream from the spur dike, debris raft, and pier 8, and moderate turbulence was observed in several transects (<xref ref-type="fig" rid="fig57">fig.&#x00A0;57</xref>).</p>
<fig id="fig57" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 57</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 57.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structure A0767 on Interstate 435 in Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Interstate 435 bridge on August 14, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig57"/></fig>
<p>The history of scour observed near pier&#x00A0;7 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>) led MoDOT to install scour countermeasures around pier&#x00A0;7 during August&#x2013;October 2020. Partial surveys of the channel bed near pier&#x00A0;7 of structure A0767 were surveyed before and after installation of these scour countermeasures to document and verify installation. The historical scour hole near pier&#x00A0;7 was clearly evident in the pre-installation survey on August 17, 2020 (<xref ref-type="fig" rid="fig58">fig.&#x00A0;58</xref>), but the cofferdam for an expanded seal course had been partially installed, creating a partially widened footprint to the pier (<xref ref-type="fig" rid="fig58">fig.&#x00A0;58</xref>). The difference between the survey on August 13, 2019, and the partial survey on August 17, 2020, indicates moderate deposition of 3&#x00A0;to 7&#x00A0;ft had occurred in much of the partial reach from 2019 to 2020, but that scour of 15&#x00A0;to 20&#x00A0;ft had occurred near the pier (<xref ref-type="fig" rid="fig59">fig.&#x00A0;59</xref>). The cross sections from the two surveys along the upstream face of the bridge also indicates this deeper and wider scour hole at the pier in 2020 (<xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>). The downstream and right (south) edges of the riprap blanket countermeasure installed around pier&#x00A0;7 was clearly evident in the post-installation survey on October 23, 2020 (<xref ref-type="fig" rid="fig60">figs.&#x00A0;60</xref>, <xref ref-type="fig" rid="fig01.09">1.9<italic>B</italic></xref>), and the difference between the pre- and post-installation surveys indicate the changes resulting from the installation (<xref ref-type="fig" rid="fig61">fig.&#x00A0;61</xref>). The net volume of cut in the partial reach from August 2019 to August 2020 was about 3,100&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 14,300&#x00A0;yd<sup>3</sup>, resulting in a net gain of about 11,200&#x00A0;yd<sup>3</sup> of sediment between August 2019 and August 2020 (<xref ref-type="fig" rid="fig59">fig.&#x00A0;59</xref>). The net volume of cut in the partial reach from August to October 2020 was about 5,300&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 8,400&#x00A0;yd<sup>3</sup>, resulting in an additional net gain of about 3,100&#x00A0;yd<sup>3</sup> of sediment between August and October 2020 (<xref ref-type="fig" rid="fig61">fig.&#x00A0;61</xref>). The scour hole was effectively mitigated because as much as 27&#x00A0;ft of deposition was near the pier (<xref ref-type="fig" rid="fig61">fig.&#x00A0;61</xref>), including some deposition of alluvial material on top of the blanket upstream from the bridge (<xref ref-type="fig" rid="fig60">fig.&#x00A0;60</xref>); nevertheless, moderate scour occurred in much of the partial reach around the riprap blanket between August and October (<xref ref-type="fig" rid="fig61">fig.&#x00A0;61</xref>).</p>
<fig id="fig58" position="float" fig-type="figure"><?Figure Large?><label>Figure 58</label><caption><p>Bathymetric survey of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 17, 2020, before installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 58.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 17, 2020, before installation of scour countermeasures.</p></caption>
<long-desc>The Missouri River channel bottom near the main pier at Interstate 435 bridge on August 17, 2020.</long-desc><graphic xlink:href="rol21-0068_fig58"/></fig>
<fig id="fig59" position="float" fig-type="figure"><?Figure Large?><label>Figure 59</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 13, 2019, and August 17, 2020, before installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 59.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 13, 2019, and August 17, 2020, before installation of scour countermeasures.</p></caption>
<long-desc>Difference between surveys near the main pier at Interstate 435 bridge on August 13, 2019, and August 17, 2020.</long-desc><graphic xlink:href="rol21-0068_fig59"/></fig>
<fig id="fig60" position="float" fig-type="figure"><?Figure Large?><label>Figure 60</label><caption><p>Bathymetric survey of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 60.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures.</p></caption>
<long-desc>The Missouri River channel bottom near the main pier at Interstate 435 bridge on October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig60"/></fig>
<fig id="fig61" position="float" fig-type="figure"><?Figure Large?><label>Figure 61</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 17 and October 23, 2020, before and after installation of scour countermeasures.</p><p content-type="toc"><bold>Figure 61.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near the main channel pier of structure A0767 on Interstate 435 in Kansas City, Missouri, on August 17 and October 23, 2020, before and after installation of scour countermeasures.</p></caption>
<long-desc>Difference between surveys near the main pier at Interstate 435 bridge on August 17 and October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig61"/></fig>
</sec>
<sec>
<title>Structures A4757 and L0568 on State Highway 291</title>
<p>Structures A4757 and L0568 (site&#x00A0;13; <xref ref-type="table" rid="t01">table&#x00A0;1</xref>) are dual bridges on State Highway 291, crossing the Missouri River at RM&#x00A0;352.7 on the northeastern side of the Kansas City, Mo., metropolitan area (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The site was surveyed on August 14, 2019, and the average water-surface elevation of the river in the survey area, determined by the RTK GPS tide solution, was 720.1&#x00A0;ft (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). Streamflow on the Missouri River was about 141,000&#x00A0;ft<sup>3</sup>/s during the survey (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>).</p>
<p>The survey area was about 1,640&#x00A0;ft long and averaged about 890&#x00A0;ft wide, extending from bank to bank in the main channel (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). The upstream end of the survey area was about 720&#x00A0;ft upstream from the centerline between structures A4757 and L0568 (<xref ref-type="fig" rid="fig42">fig. 42</xref>). The channel-bed elevations ranged from about 679&#x00A0;to 706&#x00A0;ft for most of the surveyed area (5th&#x00A0;to 95th&#x00A0;percentile range of the bathymetric data; <xref ref-type="table" rid="t05">table&#x00A0;5</xref>; <xref ref-type="fig" rid="fig63">fig.&#x00A0;63</xref>), except near the main channel piers of structures A4757 and L0568 (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). A channel thalweg was along the left (north) bank throughout the channel and was about 10 ft deeper than the middle of the channel (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). A row of medium dune features were observed in the thalweg on the left side of the channel, as well as numerous small dunes and ripples throughout the rest of the channel (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). As in previous surveys at this site (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>), a noticeable channel constriction was at and immediately downstream from the bridges, and the left (north) bank was covered with stone revetment (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>).</p>
<fig id="fig62" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 62</label><caption><p>Bathymetric survey of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 62.</bold>&#x2003;Map showing the bathymetric survey of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 291 bridges on August 14, 2019.</long-desc><graphic xlink:href="rol21-0068_fig62"/></fig>
<fig id="fig63" position="float" fig-type="figure"><?Figure Large?><label>Figure 63</label><caption><p>Frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, respectively).</p><p content-type="toc"><bold>Figure 63.</bold>&#x2003;Graph showing the frequency distribution of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins on the Missouri River near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, compared to previous surveys in 2010, 2011, and 2015.</p></caption>
<long-desc>Frequency distribution of channel bed elevations from various surveys at Missouri Highway 291.</long-desc><graphic xlink:href="rol21-0068_fig63"/></fig>
<p>A large scour hole near the main channel piers (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>) that essentially encompasses both piers had a minimum channel-bed elevation of about 664&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>), which also was the minimum channel-bed elevation for the entire reach (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>). The main channel piers were skewed to the approaching flow, which caused a wide scour hole with somewhat unique characteristics as compared to scour holes at the other surveyed bridges. Pier&#x00A0;5 of structure L0568 was in the wake of pier&#x00A0;2C of structure A4757 and, therefore, had a poorly defined scour hole near it (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). At the upstream end of pier 2C of structure A4757, the minimum channel-bed elevation was about 664 ft, and at the upstream end of pier&#x00A0;5 of structure L0568, the minimum channel-bed elevation was about 672&#x00A0;ft (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicates that the main channel pier&#x00A0;2C of structure A4757 is founded on shafts drilled 20&#x00A0;ft into bedrock (<xref ref-type="fig" rid="fig64">fig.&#x00A0;64</xref>), and about 45&#x00A0;ft of bed material are between the bottom of the scour hole and bedrock at the point of minimum elevation of the scour hole near the upstream pier face (<xref ref-type="fig" rid="fig64">fig.&#x00A0;64</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>). At the point of minimum elevation, the surveyed channel bed was about 2&#x00A0;ft below the bottom of the seal course elevation of 666.26&#x00A0;ft (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Information from bridge plans indicate that the main channel pier&#x00A0;5 of structure L0568 is a caisson on bedrock (<xref ref-type="fig" rid="fig65">fig.&#x00A0;65</xref>), and about 47&#x00A0;ft of bed material are between the bottom of the scour hole and bedrock at the point of minimum elevation of the scour hole near the downstream right (south) corner (<xref ref-type="fig" rid="fig65">fig.&#x00A0;65</xref>; <xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<fig id="fig64" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 64</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure A4757 on State Highway 291 crossing the Missouri River near Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 64.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure A4757 on State Highway 291 crossing the Missouri River near Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Missouri Highway 291 upstream bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig64"/></fig>
<fig id="fig65" position="float" fig-type="figure"><?Figure Sideturn?><label>Figure 65</label><caption><p>Key features, substructural and superstructural details, and surveyed channel bed of structure L0568 on State Highway 291 crossing the Missouri River near Kansas City, Missouri.</p><p content-type="toc"><bold>Figure 65.</bold>&#x2003;Diagram showing key features, substructural and superstructural details, and surveyed channel bed of structure L0568 on State Highway 291 crossing the Missouri River near Kansas City, Missouri.</p></caption>
<long-desc>Cross-section sketch of the Missouri Highway 291 downstream bridge with various surveys indicated.</long-desc><graphic xlink:href="rol21-0068_fig65"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous nonflood survey on June 4, 2015 (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>), indicates about 74&#x00A0;percent of the joint area of interest had detectable change, which means about 26&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Bed variation seemed nearly equal between scour and deposition from 2015 to 2019 in the DoD map, deposition was predominant from the upstream left through the downstream right of the reach, and scour was predominant from the upstream right to the downstream left (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>). The average difference between the bathymetric surfaces was &#x2013;1.51&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating minor to moderate degradation between the 2015 and 2019 surveys. The net volume of cut in the reach from 2015 to 2019 was about 82,100&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 25,100&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 57,000&#x00A0;yd<sup>3</sup> of sediment between 2015 and 2019. The cross sections from the two surveys along the upstream face of the upstream bridge are similar to each other but generally with uniform scour of 5&#x00A0;to 10&#x00A0;ft across the section (<xref ref-type="fig" rid="fig64">fig.&#x00A0;64</xref>). The cross sections from the two surveys along the upstream face of the downstream bridge also are similar to each other but generally with uniform scour of 10&#x00A0;ft across the section (<xref ref-type="fig" rid="fig65">fig.&#x00A0;65</xref>). The frequency distribution of bed elevations in 2019 was very similar to 2015, but a higher percentage of cells were at slightly lower channel-bed elevations in 2019 (<xref ref-type="fig" rid="fig63">fig.&#x00A0;63</xref>). The scour hole near upstream pier&#x00A0;2C was similar to 2015, as evidenced by the area of equivocal data in a horseshoe shape around the upstream end of that pier in the DoD map (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>). However, the scour hole was slightly deeper near downstream pier&#x00A0;5 than in 2015, as evidenced by the area of scour starting at the downstream side of upstream pier&#x00A0;2C and extending downstream around pier&#x00A0;5 in the DoD map (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>). The stone revetment on the left (north) bank showed signs of nearly uniform deposition throughout the reach between 2015 and 2019, which is somewhat unexpected (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>); as indicated with others surveys in the current study, there may be a horizontal offset to the 2019 data on the bank that is creating the appearance of deposition. The potential for a horizontal offset is substantiated by the appearance of substantial scour on the left (north) faces and deposition on the right (south) faces of the footing and caisson that likely results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig66" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 66</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and June 4, 2015.</p><p content-type="toc"><bold>Figure 66.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and June 4, 2015.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 291 bridges on August 14, 2019, and June 4, 2015.</long-desc><graphic xlink:href="rol21-0068_fig66"/></fig>
<p>The difference between the survey on August 14, 2019, and the previous flood survey on July 19, 2011 (<xref ref-type="fig" rid="fig67">fig.&#x00A0;67</xref>), indicates about 85&#x00A0;percent of the joint area of interest had detectable change, which means about 15&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial but approximately balanced bed variation was apparent from 2011 to 2019 in the DoD map, substantial scour was throughout the upstream part and along the right side of the reach, and substantial deposition was along the thalweg along the left (north) side and in the troughs of substantial dunes present in the 2011 survey (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="fig" rid="fig67">fig.&#x00A0;67</xref>). The average difference between the bathymetric surfaces was +0.22&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating little net different between the 2011 and 2019 surveys. The net volume of cut in the reach from 2011 to 2019 was about 77,900&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 87,400&#x00A0;yd<sup>3</sup>, resulting in a net gain of about 9,500&#x00A0;yd<sup>3</sup> of sediment in the reach between 2011 and 2019. However, the cross sections from the two surveys along the upstream faces of the bridges show the substantial difference in the surveyed sections (<xref ref-type="fig" rid="fig64">figs.&#x00A0;64</xref>, <xref ref-type="fig" rid="fig65">65</xref>). The frequency distribution of bed elevations in 2019 also was substantially narrower than 2011 because a higher percentage of cells was at the middle range of elevations (<xref ref-type="fig" rid="fig63">fig.&#x00A0;63</xref>). The DoD map shows that the substantial scour hole at upstream pier&#x00A0;2C was smaller and shallower in 2019, as evidenced by the horseshoe-shaped deposition around the nose of the pier (<xref ref-type="fig" rid="fig67">fig.&#x00A0;67</xref>). As with the DoD map for 2015 to 2019 (<xref ref-type="fig" rid="fig66">fig.&#x00A0;66</xref>), the stone revetment on the left (north) bank showed signs of localized deposition throughout the reach between 2011 and 2019, which is somewhat unexpected (<xref ref-type="fig" rid="fig67">fig.&#x00A0;67</xref>); however, the differences on the tops of steps in the bank were within the uncertainties of the data, which implies there may be a horizontal offset to the 2019 data on the bank that is creating the appearance of deposition. The appearance of substantial scour on the left (north) faces and deposition on the right (south) faces of the footing and caisson also likely results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig67" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 67</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and July 19, 2011.</p><p content-type="toc"><bold>Figure 67.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and July 19, 2011.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 291 bridges on August 14, 2019, and July 19, 2011.</long-desc><graphic xlink:href="rol21-0068_fig67"/></fig>
<p>The difference between the survey on August 14, 2019, and the earliest nonflood survey on March 18, 2010 (<xref ref-type="fig" rid="fig68">fig.&#x00A0;68</xref>), indicates about 75&#x00A0;percent of the joint area of interest had detectable change, which means about 25&#x00A0;percent of the differences in the joint area of interest are equivocal and within the uncertainty. Substantial but approximately balanced bed variation was apparent from 2010 to 2019 in the DoD map, scour was predominant in the upstream area and along the right (south) bank downstream, and deposition was in the substantial scour hole near the piers and troughs of large dunes in the downstream channel present in the 2010 survey (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>; <xref ref-type="fig" rid="fig68">fig.&#x00A0;68</xref>). The average difference between the bathymetric surfaces was &#x2013;2.82&#x00A0;ft (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), indicating moderate channel degradation between the 2010 and 2019 surveys. The net volume of cut in the reach from 2010 to 2019 was about 127,200&#x00A0;yd<sup>3</sup>, and the net volume of fill was about 24,600&#x00A0;yd<sup>3</sup>, resulting in a net loss of about 102,600&#x00A0;yd<sup>3</sup> of sediment between 2010 and 2019. The cross sections from the two surveys along the upstream face of the bridge are similar to each other, except near the piers and between the piers and the right (south) banks (<xref ref-type="fig" rid="fig64">figs.&#x00A0;64</xref>, <xref ref-type="fig" rid="fig65">65</xref>). The frequency distribution of bed elevations in 2019 was similar to 2010 at lower elevations but became different with increasing elevation, and a lower percentage of cells was at higher channel-bed elevations (<xref ref-type="fig" rid="fig63">fig.&#x00A0;63</xref>); however, the surveyed area was substantially wider in 2019 than in 2010 and extended higher on the channel banks, particularly on the right (south) side (<xref ref-type="fig" rid="fig68">fig.&#x00A0;68</xref>). The stone revetment on the left (north) bank showed signs of minor, localized scour and deposition, and much of the difference was within the uncertainties of the data, as would be expected. As with previous DoD maps, and substantial deposition or scour apparent at the faces of the pier footing results from minor horizontal positional variances between the surveys (see &#x201C;Uncertainty Estimation&#x201D; section).</p>
<fig id="fig68" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 68</label><caption><p>Difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and March 18, 2010.</p><p content-type="toc"><bold>Figure 68.</bold>&#x2003;Map showing the difference between surfaces created from bathymetric surveys of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019, and March 18, 2010.</p></caption>
<long-desc>Difference between surveys at Missouri Highway 291 bridges on August 14, 2019, and March 18, 2010.</long-desc><graphic xlink:href="rol21-0068_fig68"/></fig>
<p>The vertically averaged velocity vectors indicate mostly uniform flow throughout the reach, ranging from about 2&#x00A0;ft/s along the inside of the bend on the right (south) bank to about 9&#x00A0;ft/s in the thalweg (<xref ref-type="fig" rid="fig69">fig.&#x00A0;69</xref>). Exceptions to uniform flow include flows angled to the left (north) near the upstream and downstream faces of the bridges (<xref ref-type="fig" rid="fig69">fig.&#x00A0;69</xref>). Moderate turbulence also was observed in several transects, particularly near the bank protrusions near the bridges and downstream from the main channel piers (<xref ref-type="fig" rid="fig69">fig.&#x00A0;69</xref>). Velocities were slightly lower downstream from the bridges, likely caused by the flow expansion downstream from the constriction at the bridges (<xref ref-type="fig" rid="fig69">fig.&#x00A0;69</xref>).</p>
<fig id="fig69" position="float" fig-type="figure"><?Figure Oversize?><label>Figure 69</label><caption><p>Bathymetry and vertically averaged velocities of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019.</p><p content-type="toc"><bold>Figure 69.</bold>&#x2003;Map showing bathymetry and vertically averaged velocities of the Missouri River channel near structures A4757 and L0568 on State Highway 291 near Kansas City, Missouri, on August 14, 2019.</p></caption>
<long-desc>The Missouri River channel bottom at Missouri Highway 291 bridges on August 14, 2019, with overlain velocity vectors.</long-desc><graphic xlink:href="rol21-0068_fig69"/></fig>
</sec>
<sec>
<title>General Findings and Implications</title>
<p>Several of the findings at each surveyed bridge were common to all the bridges, and some findings were evident only when results of the surveys were examined as a set. These general findings are of benefit in the assessment of scour at the surveyed bridges, as well as other bridges close by or in similar settings.</p>
<sec>
<title>Effects of Moderate Flooding Compared to Previous Surveys</title>
<p><xref ref-type="bibr" rid="r2">Arneson and others (2012)</xref> separated long-term aggradation and degradation of a channel from the contraction and local scour that happens at a bridge site during floods. Contraction scour is the general change in the channel-bed elevation across a bridge opening resulting from the passage of a flood through a constriction, where more material is in suspension and transport. Local scour is the localized erosion of material caused by flow-vortex action that forms near bridge piers and abutments. Although all the scour processes (long term, contraction, and local scour) continually are at work, contraction and local scour generally are cyclic for the live-bed scour typically observed in alluvial channels and generally result in a decrease and subsequent increase of the channel-bed elevation during and after a flood.</p>
<p>It has been shown in the previous studies with the MBES in the Kansas City area (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>) that the configuration and size of bed forms observed during a particular survey depend on more than the instantaneous streamflow at a given site. Several factors and interactions of factors affect sediment transport conditions and the resultant bed configuration. Although it is beyond the scope of the current (2021) study to examine all the antecedent conditions that created the observed channel-bed configuration in the most recent (2019) surveys, the following discussion attempts to draw conclusions based on the conditions observed at each site during the most recent and previous surveys.</p>
<p>As discussed in the previous reports about the Kansas City area bridges (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>), most large flood durations on the Missouri River can be measured in days to weeks because of the large upstream contributing drainage area. The presence of dams on the upper Missouri River upstream from Yankton, South Dakota, can lessen the magnitude and lengthen the duration of a given flood wave somewhat because of streamflow regulation, as was seen during the 2011 flood (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>), but the substantial drainage area contributing unregulated streamflows downstream from Yankton can create substantial variability in the streamflow conditions at Kansas City. As described in the &#x201C;Description of Streamflow Conditions&#x201D; section earlier in this report, all the surveys in the current (2021) study were in a trough between minor, mid-summer flood rises; however, the trough happened during generally higher summer flows, which lasted from mid-March past the end of the water year in September (<xref ref-type="fig" rid="fig02">fig.&#x00A0;2</xref>). Furthermore, the peak streamflows in March and June were the highest since 1993.</p>
<p>Streamflows at the Kansas City sites during the 2019 surveys ranged from about 1.2&#x00A0;to 1.5&#x00A0;times greater than the streamflow during the 2015 surveys, and average water-surface elevations were 1.5&#x00A0;to 5.1&#x00A0;ft higher in 2019 than in 2015 (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>). The average differences between the 2019 and 2015 bathymetric surfaces ranged from &#x2013;0.13&#x00A0;to &#x2013;4.17&#x00A0;ft, which indicates overall scour between the survey dates (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>), as might be expected based purely on streamflow at the time of the survey. Streamflows at the Kansas City sites during the 2019 surveys ranged from 33&#x00A0;to 47&#x00A0;percent of the 2011 streamflows, and water-surface elevations were about 6.6&#x00A0;to 13.4&#x00A0;ft lower in 2019 than in 2011 (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>); nevertheless, the average differences between the 2019 and 2011 bathymetric surfaces ranged from 0.22&#x00A0;to &#x2013;4.91&#x00A0;ft, which again indicates overall scour (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>). The smaller average differences between surveys might be considered equivocal based on the uncertainty associated with points recorded for the surveys (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>) and the 95-percent thresholding used in the difference maps. Nevertheless, these trends are not consistent with what might be expected for scour and deposition based purely on streamflow at the time of the survey. The predominant scour observed between the various surveys implies the channel bed in the 2019 surveys might have still been rebounding from more substantial scour caused by the higher streamflow earlier in March and June. The site with the largest variability in intersurvey average difference was site&#x00A0;8, structure A4649 on U.S.&#x00A0;Highway 169 (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>). The average difference in bed elevation at site&#x00A0;8 indicated minor deposition between 2010 and 2019 (<xref ref-type="fig" rid="fig25">fig.&#x00A0;25</xref>) with nearly equal streamflows, substantial scour between 2011 and 2019 (<xref ref-type="fig" rid="fig24">fig.&#x00A0;24</xref>) with substantially less streamflow in 2019, and nearly equivocal scour between 2015 and 2019 (<xref ref-type="fig" rid="fig23">fig.&#x00A0;23</xref>) with approximately 34&#x00A0;percent more streamflow. The site with the smallest variability in intersurvey average difference was site&#x00A0;6, structure A1800 on Interstate 635 (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>); the average difference in bed elevation at site&#x00A0;6 indicated moderate scour of 1.59&#x00A0;to 2.93&#x00A0;ft between the 2019 and all other surveys.</p>
<p>Examining the average channel-bed and water-surface elevations with time (<xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>), the water-surface elevations during the 2019 surveys were the second-lowest of the four surveys at the two upstream-most structures A1800 (site&#x00A0;6) and A8340 (site&#x00A0;7), whereas the water-surface elevation during the 2019 surveys were the second-highest of the four surveys at the sites from structure A4649 (site&#x00A0;8) downstream. At sites&#x00A0;7, 8, 9 and 11, the channel bed was at a temporal maximum in 2011, and at sites&#x00A0;7 and 8, the channel bed was at a temporal minimum in 2010. The 2015 and 2019 average channel-bed elevations fell between the 2010 and 2011 surveys at sites&#x00A0;7 and 8. In contrast, the 2019 survey set or matched the temporal minimum at sites&#x00A0;6 and 9 through 12 (<xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>). The Kansas River joins the Missouri River immediately upstream from structure A4649 (site&#x00A0;8; <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), and additional inflow from the Kansas River likely accounts for the increased water-surface elevations at site&#x00A0;8 and downstream. The additional inflow may also account for why the average channel-bed elevations are at a temporal minimum in 2019 for nearly all the sites downstream from structure A4649 (site&#x00A0;8; <xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>). This configuration of average channel-bed elevations and average differences indicates that greater streamflow at the time of the survey alone does not necessarily result in more scour at a site (as would be evidenced by lower average channel-bed elevations with increased streamflow). It was hypothesized in the 2011 flood study at Kansas City (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>) that a slug of sediment may have been traveling through the upstream part of the Kansas City area at that time, given the substantial increase in channel-bed elevation from 2010 to 2011 at the upstream sites; it was further hypothesized after the 2015 surveys that this slug of sediment had been eroded away between 2011 and 2015 (<xref ref-type="bibr" rid="r15">Huizinga, 2016</xref>). The results of the 2019 surveys seem to substantiate that if a slug of sediment indeed was present in 2011, it had eroded away from the upstream sites; furthermore, additional erosion has occurred at nearly all the sites downstream from structure A4649 (site&#x00A0;8) since 2015 (<xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>) Again, it seems reasonable to assume that the higher streamflows in March and June had a substantial scouring effect in the reach, and the 2019 surveys captured a partial rebound.</p>
<fig id="fig70" position="float" fig-type="figure"><?Figure Large?><label>Figure 70</label><caption><p>Average channel-bed and water-surface elevations near bridges on the Missouri River near Kansas City, Missouri, from surveys in 2010, 2011, 2015, and 2019 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, and this report, respectively).</p><p content-type="toc"><bold>Figure 70.</bold>&#x2003;Graph showing average channel-bed and water-surface elevations near bridges on the Missouri River near Kansas City, Missouri, from surveys in 2010, 2011, 2015, and 2019.</p></caption>
<long-desc>Average channel-bed and water-surface elevations on the Missouri River in Kansas City.</long-desc><graphic xlink:href="rol21-0068_fig70"/></fig>
<p>The local spatial minimum observed at structure A7650 (site&#x00A0;10) in the 2015 surveys (<xref ref-type="bibr" rid="r15">Huizinga, 2016</xref>) persisted in the 2019 surveys (<xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>) and likely indicates this site is at or near a local feature that controls sediment deposition and scour. As posited in the report on the 2015 surveys, the feature may be a combination of the constriction at this site (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>) and being near the downstream end of the relatively straight reach of river between structures A4649 and A7650 (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>); furthermore, perhaps the sediment unable to deposit near structure A7650 is flushed downstream and deposits at the next downstream site, structure A5817 (site&#x00A0;11), as indicated by the average channel bed elevation curve (<xref ref-type="fig" rid="fig70">fig.&#x00A0;70</xref>). The relatively consistent shape of the frequency distribution and accumulation curves between the surveys at site&#x00A0;10 (<xref ref-type="fig" rid="fig39">fig.&#x00A0;39</xref>) further substantiates that the site may be a channel sediment control point, allowing minor deposition during lower streamflows as in 2015 but flushing to a relatively consistent bed-elevation distribution during higher streamflow. An examination of the frequency distributions of the various sites through time (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71</xref>) seems to further confirm the scenario of a sediment control feature near structure A7650. The frequency distribution curves for structures A4060 and A7650 tend to have local maxima with a higher percentage of survey-grid cells than other sites in all the surveys (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>A</italic></xref>), and the accumulation curves for these two sites generally are steeper than the other surveys in the area (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>B</italic></xref>), which indicates a more level bed with less variation in elevation at these sites. As would be expected, these maxima are at a lower elevation than sites upstream from them and generally at a higher elevation than most of sites downstream; however, the distribution curve for downstream site&#x00A0;11 (structure&#x00A0;A5817) consistently has a local maximum that is at a higher elevation than the two upstream sites, and the accumulation curve is to the right of (implying a higher elevation than) several of the upstream sites in the surveys (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>B</italic></xref>).</p>
<fig id="fig71" position="float" fig-type="figure"><?Figure Large?><label>Figure 71</label><caption><p>Comparison of frequency distribution and cumulative percentage of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins from various surveys on the Missouri River near Kansas City, Missouri, in 2010, 2011, 2015, and 2019 (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, and this report, respectively). <italic>A</italic>,&#x00A0;frequency distribution. <italic>B</italic>,&#x00A0;cumulative percentage.</p><p content-type="toc"><bold>Figure 71.</bold>&#x2003;Graphs showing the comparison of frequency distribution and cumulative percentage of bed elevations for bathymetric survey-grid cells in 1-foot elevation bins from various surveys on the Missouri River near Kansas City, Missouri, in 2010, 2011, 2015, and 2019.</p></caption>
<long-desc>Comparison of frequency distributions of channel bed elevations from various surveys at bridges in Kansas City.</long-desc><graphic xlink:href="rol21-0068_fig71"/></fig>
<p>Further examination of the frequency distributions of the 2019 surveys in relation to the others in 2019 indicates the similarity of several of the sites with a neighboring site or the uniqueness of a given site (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71</xref>). For example, sites&#x00A0;6 and 7 (structures&#x00A0;A1800 and A8340) have remarkably similar distributions and cumulative percentage curves in 2019. Sites&#x00A0;6 and 7 also were similar in the 2011 surveys and also relatively similar to site&#x00A0;8 (structure&#x00A0;A4649) in 2011. Sites&#x00A0;9 and 10 (structures&#x00A0;A4060 and A7650) were similar to one another in 2015, but site 9 was more similar to site&#x00A0;11 (structure&#x00A0;A5817) in 2019. Site&#x00A0;13 (structures&#x00A0;A4757/L0568) is likely too far removed from the other sites to have any similarity. The distributions at site&#x00A0;12 (structure&#x00A0;A0767) historically have been remarkably similar during the various surveys (<xref ref-type="fig" rid="fig52">fig.&#x00A0;52</xref>) but unique from the other sites (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>B</italic></xref>); the cumulative percentage curve above 70&#x00A0;percent was at a higher elevation than several sites upstream, including site&#x00A0;9 (structure&#x00A0;A4060) in 2010 and 2015 (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>B</italic></xref>). Site&#x00A0;8 (structure&#x00A0;A4649) also has a wider range of elevations than other sites (<xref ref-type="fig" rid="fig21">figs.&#x00A0;21</xref>, <xref ref-type="fig" rid="fig71">71<italic>A</italic></xref>), indicated by the more gradual slope of the cumulative percent curve which often crosses the downstream sites at the lower percentages and crosses the two upstream sites at the upper percentages in the various surveys (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>B</italic></xref>).</p>
<p>Furthermore, the frequency distributions of the 2019 surveys compared to the previous surveys reveals additional differences that may be the result of streamflow conditions during the 2019 surveys (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71</xref>). Whereas the frequency distributions generally were narrower in the 2015 survey than in either the 2010 or 2011 survey at each site with a higher percentage of survey-grid cells in a particular elevation range (<xref ref-type="fig" rid="fig71">fig.&#x00A0;71<italic>A</italic></xref>), the distributions for the 2019 survey generally were slightly wider, similar to 2011 and indicative of a wider spread of elevations in the surveys at a given site. Similarly, whereas the narrower distributions in 2015 resulted in generally steeper accumulation curves, the 2019 accumulation curves were more similar to 2010 (<xref ref-type="fig" rid="fig71">figs.&#x00A0;71<italic>B</italic></xref>). Accumulation curves that are steep indicate a channel bed with a narrower range of elevations (more level throughout the reach), whereas those that are less steep indicate a wider variation of elevations. Accumulation curves with &#x201C;steps&#x201D; indicate a channel with distinct groups of elevations, such as a thalweg on one side and a shallow area on the opposite side of the channel (such as structure&#x00A0;A1800, <xref ref-type="fig" rid="fig06">figs.&#x00A0;6</xref> and <xref ref-type="fig" rid="fig07">7</xref>).</p>
<p>The size and shape of the frequency distributions through time also may be an indication of the type of river reach the site is located upon. Sites&#x00A0;6 and 7 are both on the same gentle bend in the river, and the similarities of the curve shapes may be indicative of the channel bend characteristics (<xref ref-type="fig" rid="fig07">figs.&#x00A0;7</xref>, <xref ref-type="fig" rid="fig14">14</xref>, <xref ref-type="fig" rid="fig71">71</xref>). Sites&#x00A0;11 and 12 also are on gentle river bends and have distributions curves with a similar shape to sites&#x00A0;6 and 7 (<xref ref-type="fig" rid="fig45">figs.&#x00A0;45</xref>, <xref ref-type="fig" rid="fig52">52</xref>, <xref ref-type="fig" rid="fig71">71</xref>). Site&#x00A0;13 also is on a gentle river bend, but the frequency distribution is somewhat unique (<xref ref-type="fig" rid="fig63">figs.&#x00A0;63</xref>, <xref ref-type="fig" rid="fig71">71</xref>), likely because of the size and alignment of the piers at that site (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>) result in a larger spread of elevations. Site&#x00A0;8 is just downstream from a substantial channel bend and also has a somewhat unique distribution curve (<xref ref-type="fig" rid="fig21">figs.&#x00A0;21</xref>, <xref ref-type="fig" rid="fig71">71</xref>) that likely results from the channel bend and the size, alignment, and proximity of the various highway and railroad bridge piers at the site (<xref ref-type="fig" rid="fig19">figs.&#x00A0;19</xref>, <xref ref-type="fig" rid="fig21">21</xref>, <xref ref-type="fig" rid="fig71">71</xref>). Conversely, sites&#x00A0;9 and 10 are on a long, straight reach of the river and have narrow frequency distributions in all of the surveys (<xref ref-type="fig" rid="fig21">figs.&#x00A0;21</xref>, <xref ref-type="fig" rid="fig32">32</xref>, <xref ref-type="fig" rid="fig71">71</xref>).</p>
<p>Lastly, an examination of the dune features at the various sites with time is indicative of the different flow regimes during the various surveys. The dune features at the two upstream sites in the 2019 surveys were medium to large in size, whereas the dune features at all the other sites were small to medium in size. At structure&#x00A0;A1800 (site&#x00A0;6, <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), the dune features have been medium to very large for all the surveys at that site, almost regardless of the streamflow conditions (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>; <xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>). Whereas many of the surveys in the 2011 had a planar bed area and large to very large dune features indicative of high energy flow (<xref ref-type="bibr" rid="r33">Simons and Richardson, 1966</xref>), the 2019 surveys were more similar to the 2015 surveys, being filled throughout with mostly medium to small dune features and superimposed ripples (<xref ref-type="fig" rid="fig06">figs.&#x00A0;6</xref>, <xref ref-type="fig" rid="fig13">13</xref>, <xref ref-type="fig" rid="fig20">20</xref>, <xref ref-type="fig" rid="fig31">31</xref>, <xref ref-type="fig" rid="fig38">38</xref>, <xref ref-type="fig" rid="fig44">44</xref>, <xref ref-type="fig" rid="fig51">51</xref>, <xref ref-type="fig" rid="fig62">62</xref>). The largest dune features in the 2019 surveys were observed at structures&#x00A0;A1800 (site&#x00A0;6, <xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>) and A4757/L0568 (site&#x00A0;13, <xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). The smaller size and amplitude of the dune features compared to 2011 indicates less bed-material and bedload transport because of the lower streamflow values, whereas the larger size and amplitude of the dune features compared to 2015 indicates more bed-material and bedload transport (<xref ref-type="bibr" rid="r33">Simons and Richardson, 1966</xref>; <xref ref-type="bibr" rid="r34">Simon, Li and Associates, 1985</xref>).</p>
</sec>
<sec>
<title>Size and Shape of Scour Holes</title>
<p>Generally, every pier in the main channel area for which bathymetry could be obtained had some sort of scour hole, except those on banks or surrounded by riprap. However, the size and shape of these holes were different from one bridge to the next and occasionally even at the same bridge site. The factors affecting the size and shape of the pier scour holes have been discussed in previous survey reports (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>), and in some cases, the frontal slope of the various scour holes has been determined. Frontal slopes were not computed for the sites in this (2019) study. However, the factors that affect the local pier scour equation in <xref ref-type="bibr" rid="r2">Arneson and others (2012)</xref>, including the depth and velocity of approach flow, the width and nose shape of the pier, the angle of approach flow, and the condition and armoring of the channel bed, are discussed below.</p>
<p>For the various bridges in this study, streamflow velocities generally were greater in the deeper parts of the channel (the thalweg), and lower in the shallow parts of the channel, which is consistent with previous surveys. Of course, there were local exceptions, such as downstream from a spur dike where a local deep area may have had a low velocity (for example, <xref ref-type="fig" rid="fig19">figs.&#x00A0;19</xref>, <xref ref-type="fig" rid="fig43">43</xref>, <xref ref-type="fig" rid="fig57">57</xref>). Exceptions notwithstanding, the size of the scour holes at sites having more than one pier in the water was related to the depth and velocity of flow upstream from the pier in question, and consistent with the local pier scour equation in <xref ref-type="bibr" rid="r2">Arneson and others (2012)</xref>. Deeper flow or higher velocity generally resulted in larger, deeper scour holes than shallow flow or lower velocities (<xref ref-type="fig" rid="fig15">figs.&#x00A0;15</xref>, <xref ref-type="fig" rid="fig33">33</xref>, <xref ref-type="fig" rid="fig46">46</xref>) in the absence of bedrock or riprap as a designed scour countermeasure (pier&#x00A0;3, <xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>; pier&#x00A0;7, <xref ref-type="fig" rid="fig53">fig. 53</xref>). Similar findings have been observed during all the various studies using the MBMS in Missouri (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>).</p>
<p>Also consistent with the local pier scour equation in <xref ref-type="bibr" rid="r2">Arneson and others (2012)</xref>, piers having wide or blunt noses resulted in larger, deeper scour holes than those having narrow, round, or sharp noses. Almost all the piers at the sites in the Kansas City area had some part of the foundation exposed to flow, whether the footing, seal course, or caisson. When the channel bed immediately upstream from a pier was above the top of a footing, the scour holes near that pier occasionally did not penetrate below the top of the footing (pier&#x00A0;3, <xref ref-type="fig" rid="fig44">figs.&#x00A0;44</xref>, <xref ref-type="fig" rid="fig46">46</xref>); the footing effectively limited scour at these piers. However, when the upstream edge of the top of the footing was exposed, the substantial extra width of the footing tended to widen the scour hole (pier&#x00A0;3, <xref ref-type="fig" rid="fig06">figs.&#x00A0;6</xref>, <xref ref-type="fig" rid="fig08">8</xref>; piers&#x00A0;5 and 6, <xref ref-type="fig" rid="fig31">figs.&#x00A0;31</xref>, <xref ref-type="fig" rid="fig33">33</xref>; pier&#x00A0;2, <xref ref-type="fig" rid="fig44">figs.&#x00A0;44</xref>, <xref ref-type="fig" rid="fig46">46</xref>; pier&#x00A0;7, <xref ref-type="fig" rid="fig51">figs.&#x00A0;51</xref>, <xref ref-type="fig" rid="fig53">53</xref>; pier&#x00A0;2C, <xref ref-type="fig" rid="fig62">figs.&#x00A0;62</xref>, <xref ref-type="fig" rid="fig64">64</xref>). Similar findings have been observed during the various studies using the MBMS in Missouri (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r10">2011</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r13">2014</xref>, <xref ref-type="bibr" rid="r14">2015</xref>, <xref ref-type="bibr" rid="r15">2016</xref>, <xref ref-type="bibr" rid="r16">2017a</xref>, <xref ref-type="bibr" rid="r18">2020a</xref>, <xref ref-type="bibr" rid="r22">e</xref>), particularly during the 2011 flood (<xref ref-type="bibr" rid="r11">Huizinga, 2012</xref>). The bents at structure&#x00A0;A8340 (site&#x00A0;7) consist of cylindrical drilled shafts 10.5&#x00A0;ft in diameter, and although the scour hole was somewhat smaller near the central bent (bent&#x00A0;4) compared to other sites (<xref ref-type="fig" rid="fig13">figs.&#x00A0;13</xref>, <xref ref-type="fig" rid="fig15">15</xref>), the bent still had a scour hole that was about 17&#x00A0;ft deep (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<p>Several of the surveyed bridges had piers that were skewed to approach flow, resulting in asymmetric scour holes at those bridges: pier&#x00A0;3 of structure A1800 on Interstate 635 (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>); pier&#x00A0;2 of structure A4649 on U.S.&#x00A0;Highway 169 (<xref ref-type="fig" rid="fig20">fig.&#x00A0;20</xref>); the railroad bridge pier upstream from pier 6 of structure A4060 on State Route 9 (<xref ref-type="fig" rid="fig31">fig. 31</xref>); the main channel pylon of structure A7650 on Interstate 35 (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>); and pier&#x00A0;2C of structure&#x00A0;A4757 and pier&#x00A0;5 of structure L0568 on State Highway 291 (<xref ref-type="fig" rid="fig62">fig.&#x00A0;62</xref>). At all the structures except A7650, the scour hole was deeper and longer on the side of the pier with impinging flow, and some amount of deposition was on the leeward side, as typically has been observed at piers skewed to approach flow; however, at structure&#x00A0;A7650, the scour hole was deeper and longer on the leeward side of the pier, possibly because of a deflection and contraction of flow caused by the protruding left bank at the bridge (<xref ref-type="fig" rid="fig38">figs.&#x00A0;38</xref>, <xref ref-type="fig" rid="fig43">43</xref>). Although the velocities were not substantially affected by the constriction (<xref ref-type="fig" rid="fig43">fig.&#x00A0;43</xref>), the pylon and constriction may cause enough turbulence to pull sediment into suspension. At all the structures, the skew to approach flow is apparent in the velocity vectors (<xref ref-type="fig" rid="fig12">figs.&#x00A0;12</xref>, <xref ref-type="fig" rid="fig26">26</xref>, <xref ref-type="fig" rid="fig37">37</xref>, <xref ref-type="fig" rid="fig43">43</xref>, <xref ref-type="fig" rid="fig69">69</xref>). At structures A4757/L0568, the skew seems to be exacerbated by shear flow from the contraction of the right bank at the bridge (<xref ref-type="fig" rid="fig69">fig.&#x00A0;69</xref>).</p>
</sec>
<sec>
<title>Effects of Riprap Blankets near Piers</title>
<p>The main channel pylon of structure A7650 (site&#x00A0;10) has piles of rock surrounding it (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>), and scour countermeasures in the form of a riprap blanket were placed around the central main channel pier of structures A4649 (site&#x00A0;8) and A0767 (site&#x00A0;12) between August and October of 2020. The riprap blankets at structures A4649 (site&#x00A0;8) and A0767 (site&#x00A0;12) were specifically designed to resist scour at those sites; it is unknown whether the rock around the main channel pylon of structure A7650 (site&#x00A0;10) was specifically designed, was an ad hoc placement of riprap to mitigate potential scour at that substructural bridge element, or simply was construction detritus. Nevertheless, the presence of these features had a substantial effect on the observed scour at these piers, particularly when compared to other piers at the same sites without such a feature, or when examining the survey results from before and after installation.</p>
<p>The main channel pylon of structure&#x00A0;A7650 (site&#x00A0;10) seemed to be partially surrounded with piles of coarse material (<xref ref-type="fig" rid="fig38">figs.&#x00A0;38</xref>, <xref ref-type="fig" rid="fig40">40</xref>, <xref ref-type="fig" rid="fig01.06">1.6</xref>). Bridge plans do not indicate that these piles are a designed scour countermeasure. Some settling of the piles was observed in the 2019 survey compared to the previous surveys in 2015 and 2011 (<xref ref-type="fig" rid="fig41">figs.&#x00A0;41</xref>, <xref ref-type="fig" rid="fig42">42</xref>) such that the bottom of the seal course was exposed by 5&#x00A0;to 10&#x00A0;ft along the upstream face of the bridge (<xref ref-type="fig" rid="fig40">fig.&#x00A0;40</xref>). Nevertheless, these piles seem to effectively divert most of the scour near the pylon away from the pylon base. Scour immediately downstream from the pylon was substantial (<xref ref-type="fig" rid="fig38">fig.&#x00A0;38</xref>) but likely does not directly affect the stability of the pylon.</p>
<p>Pier&#x00A0;2 of structure A4696 on U.S. Highway 169 (site&#x00A0;8, <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) had a riprap blanket installed between August and October of 2020 (<xref ref-type="fig" rid="fig27">figs.&#x00A0;27</xref>, <xref ref-type="fig" rid="fig29">29</xref>) that was a minimum of 7.5&#x00A0;ft thick per the bridge plans (Travis S. Stump, Missouri Department of Transportation, written commun., December 9, 2020; <xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>). The survey after the installation clearly indicated the riprap blanket limited scour near pier&#x00A0;2 (<xref ref-type="fig" rid="fig29">figs.&#x00A0;29</xref>, <xref ref-type="fig" rid="fig30">30</xref>). The top surface of the blanket is very irregular, partly because of the size of riprap stones used (<xref ref-type="fig" rid="fig22">figs.&#x00A0;22</xref>, <xref ref-type="fig" rid="fig01.04">1.4</xref>), and seemed to have a depression next to the pier nose that seemed to penetrate the top of the blanket (<xref ref-type="fig" rid="fig22">fig.&#x00A0;22</xref>), which may have been the result of back-filling the existing scour hole or other low spot when the blanket was installed.</p>
<p>Pier&#x00A0;7 of structure A0767 on Interstate&#x00A0;435 (site&#x00A0;12, <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) has had a long history of substantial scour (<xref ref-type="bibr" rid="r9">Huizinga, 2010</xref>, <xref ref-type="bibr" rid="r11">2012</xref>, <xref ref-type="bibr" rid="r15">2016</xref>). An enlarged seal course and riprap blanket were installed between August and October of 2020 (<xref ref-type="fig" rid="fig53">figs.&#x00A0;53</xref>, <xref ref-type="fig" rid="fig58">58</xref>, <xref ref-type="fig" rid="fig59">59</xref>) that was a minimum of 7.5&#x00A0;ft thick per the bridge plans (Travis S. Stump, Missouri Department of Transportation, written commun., December 16, 2020; <xref ref-type="fig" rid="fig53">fig.&#x00A0;53</xref>). The survey after the installation also clearly indicated the riprap blanket limited scour near pier&#x00A0;7 (<xref ref-type="fig" rid="fig58">figs.&#x00A0;58</xref>, <xref ref-type="fig" rid="fig59">59</xref>). As at site&#x00A0;8, the top surface of the blanket is very irregular, partly because of the size of riprap stones used (<xref ref-type="fig" rid="fig53">figs.&#x00A0;53</xref>, <xref ref-type="fig" rid="fig01.09">1.9</xref>), and had a substantial depression next to the pier nose that seemed to penetrate the top of the blanket (<xref ref-type="fig" rid="fig53">figs.&#x00A0;53</xref>, <xref ref-type="fig" rid="fig01.09">1.9</xref>), which may have been the result of back-filling the existing scour hole or other low spot when the blanket was installed.</p>
</sec>
</sec>
</sec>
<sec>
<title>Summary and Conclusions</title>
<p>Bathymetric and velocimetric data were collected by the U.S.&#x00A0;Geological Survey, in cooperation with the Missouri Department of Transportation, near 9&#x00A0;bridges at 8&#x00A0;highway crossings of the Missouri River near Kansas City, Missouri, on August 13&#x2013;14, 2019. A multibeam echosounder mapping system was used to obtain channel-bed elevations for areas ranging from 1,550&#x00A0;to 1,660&#x00A0;feet longitudinally and generally extending across the active channel from bank to bank in the Missouri River during moderate flood-flow conditions. Two additional, limited surveys were completed in cooperation with Clarkson Construction near the central main channel pier of two of the sites in August and October 2020, before and after installation of scour countermeasures near these piers. These surveys document the channel-bed conditions and velocity distribution at the time of the surveys and provide characteristics of scour holes that may be useful in the development of predictive guidelines or equations for scour holes. These data also may be used by the Missouri Department of Transportation as a moderate flow assessment of the bridges for stability and integrity issues with respect to bridge scour during floods.</p>
<p>The estimated uncertainty for the bathymetric surface of each survey area was computed as an estimate of the accuracy to be expected for each point with all relevant sources of error taken into account. An analysis of the surveys indicated that more than 99&#x00A0;percent of the bathymetric data at all the sites have an uncertainty of less than 0.50&#x00A0;foot (ft), and more than 96&#x00A0;percent of the channel-bed elevations at the sites have an uncertainty of less than 0.25&#x00A0;ft.</p>
<p>At all the surveyed bridges, a variety of fluvial geomorphic features were detected in the channel, ranging from small ripples to large dunes that indicate moderate transport of bedload. Rock outcrops also were detected along one bank at several sites where the alluvial material of the channel bed had been washed away. Bathymetric data were collected around every pier that was in water, except around the nose of one pier that is surrounded by a persistent debris raft. Scour holes were present at most piers for which bathymetry could be obtained, except those on banks or surrounded by riprap. The observed scour holes at the surveyed bridges were examined with respect to shape and depth.</p>
<p>All of the bridge sites in this study were previously surveyed. Comparisons between bathymetric surfaces from the previous surveys (in March 2010, during the 2011 flood, and in June 2015) and those of this study do not indicate any consistent correlation in channel-bed elevations with streamflow conditions. Most of the surveys in the current (2019) study happened during a trough between flood rises during generally higher summer streamflows, and the measured streamflow generally was the second lowest compared to previous surveys; however, a simplified assumption of equal to lesser magnitude scour with lower streamflow did not consistently prove to be true, particularly with respect to the depth of observed scour near the piers when compared to results from the 2011 flood. Streamflow during the 2019 surveys ranged from 33&#x00A0;to 47&#x00A0;percent of the 2011 streamflow, and water-surface elevations were about 6.6&#x00A0;to 13.4&#x00A0;ft lower in 2019 than in 2011. Streamflow during the 2019 surveys ranged from about 1.2&#x00A0;to 1.5&#x00A0;times greater than the 2015 streamflow, and water-surface elevations were 1.5&#x00A0;to 5.1&#x00A0;ft higher in 2019 than in 2015; however, the average difference between the bathymetric surfaces varied from 0.13 to 4.17&#x00A0;ft lower in 2019 than 2015, and varied from 0.22&#x00A0;ft higher to 4.91&#x00A0;ft lower in 2019 than 2011. The predominant overall scour observed between the various surveys implies the channel bed in the 2019 surveys might have been rebounding from more substantial scour caused by the high streamflow earlier in March and June 2019, which was the highest streamflow since 1993.</p>
<p>A local spatial minimum average channel-bed elevation at structure A7650 (site&#x00A0;10) compared to adjacent sites observed in previous surveys may indicate this site is at or near a local feature that controls sediment deposition and scour. The feature may be a combination of the minor constriction at the site and being near the downstream end of the relatively straight reach of river; furthermore, the average channel-bed elevation values and the distribution of channel-bed elevations imply that sediment unable to deposit near structure A7650 may be flushed downstream and deposited at the next downstream site, structure A5817 (site&#x00A0;11).</p>
<p>Pier size and nose shape also had a substantial effect on the size of the scour hole observed at a given pier. Many of the piers at the Kansas City area bridges have wide or blunt noses caused by exposed footings, seal courses, or caissons, which resulted in larger, deeper scour holes at most piers. Several of the structures had piers that were skewed to primary approach flow, and at most of the structures, the scour hole was deeper and longer on the side of the pier with impinging flow, with some amount of deposition on the leeward side, as typically has been observed at piers skewed to approach flow. However, at structure A7650 (site&#x00A0;10), the scour hole was deeper and longer on the leeward side of the pier, possibly because of a deflection and contraction of flow caused by a protrusion of the corresponding bank at the bridge.</p>
<p>Two piers had scour countermeasures in the form of a riprap blanket installed between August and October 2020. Survey results from before and after installation of these countermeasures show these features had a substantial effect on mitigating the observed scour at these piers, particularly when compared to other piers at other sites without such a feature.</p>
</sec>
</body>
</book-part>
</book-body>
<book-back>
<ref-list>
<title>References Cited</title>
<ref id="r1"><mixed-citation publication-type="other">Applanix Corporation, 2017, POSPac MMS GNSS-inertial tools software (rev. 15): Richmond Hill, Ontario, Canada, Applanix Corporation, PUBS&#x2013;MAN&#x2013;001768, 246 p.</mixed-citation></ref>
<ref id="r2"><mixed-citation publication-type="book">Arneson, L.A., Zevenbergen, L.W., Lagasse, P.F., and Clopper, P.E., 2012, Evaluating scour at bridges (5th ed.): U.S. Federal Highway Administration Publication FHWA&#x2013;HIF&#x2013;12&#x2013;003, Hydraulic Engineering Circular no. 18, 340 p., accessed March 9, 2021, at <ext-link ext-link-type="uri" xlink:href="https://www.fhwa.dot.gov/engineering/hydraulics/pubs/hif12003.pdf">https://www.fhwa.dot.gov/engineering/hydraulics/pubs/hif12003.pdf</ext-link>.</mixed-citation></ref>
<ref id="r3"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Becker</surname>, <given-names>L.D.</given-names></string-name></person-group>, <year>1994</year>, <source>Investigation of bridge scour at selected sites on Missouri streams</source>: <series>U.S. Geological Survey Water-Resources Investigations Report</series> <volume>94&#x2013;4200</volume>, <size units="page">40</size>&#x00A0;p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/wri944200">https://doi.org/10.3133/wri944200</ext-link>.]</mixed-citation></ref>
<ref id="r4"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Calder</surname>, <given-names>B.R.</given-names></string-name>, and <string-name><surname>Mayer</surname>, <given-names>L.A.</given-names></string-name></person-group>, <year>2003</year>, Automatic processing of high-rate, high-density multibeam echosounder data: Geochemistry, Geophysics, Geosystems (G<sup>3</sup>), v. 4, no. 6, 22 p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1029/2002GC000486">https://doi.org/10.1029/2002GC000486</ext-link>.]</mixed-citation></ref>
<ref id="r5"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Densmore</surname>, <given-names>B.K.</given-names></string-name>, <string-name><surname>Strauch</surname>, <given-names>K.R.</given-names></string-name>, and <string-name><surname>Dietsch</surname>, <given-names>B.J.</given-names></string-name></person-group>, <year>2013</year>, <source>Hydrographic surveys of the Missouri and Yellowstone Rivers at selected bridges and through Bismarck, North Dakota, during the 2011 flood</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2013&#x2013;5087</volume>, <size units="page">59</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20135087">https://doi.org/10.3133/sir20135087</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r6"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Dietsch</surname>, <given-names>B.J.</given-names></string-name>, <string-name><surname>Densmore</surname>, <given-names>B.K.</given-names></string-name>, and <string-name><surname>Strauch</surname>, <given-names>K.R.</given-names></string-name></person-group>, <year>2014</year>, <source>Hydrographic surveys at selected highway bridges crossing the Missouri River using a multibeam echosounder, 2011</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2014&#x2013;5062</volume>, <size units="page">53</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20145062">https://doi.org/10.3133/sir20145062</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r7"><mixed-citation publication-type="other">Esri, 2020, ArcGIS: Esri software, accessed February 2020 at <ext-link ext-link-type="uri" xlink:href="https://www.esri.com/software/arcgis/">https://www.esri.com/software/arcgis/</ext-link>.</mixed-citation></ref>
<ref id="r8"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Gilbert</surname>, <given-names>G.K.</given-names></string-name>, and <string-name><surname>Murphy</surname>, <given-names>E.C.</given-names></string-name></person-group>, <year>1914</year>, <source>The transportation of debris by running water</source>: <series>U.S. Geological Survey Professional Paper</series> <volume>86</volume>, <size units="page">263</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/pp86">https://doi.org/10.3133/pp86</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r9"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2010</year>, <source>Bathymetric surveys at highway bridges crossing the Missouri River in Kansas City, Missouri, using a multibeam echo sounder, 2010</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2010&#x2013;5207</volume>, <size units="page">61</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20105207">https://doi.org/10.3133/sir20105207</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r10"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2011</year>, <source>Bathymetric surveys at highway bridges crossing the Missouri and Mississippi Rivers near St. Louis, Missouri, 2010</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2011&#x2013;5170</volume>, <size units="page">75</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20115170">https://doi.org/10.3133/sir20115170</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r11"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2012</year>, <source>Bathymetric and velocimetric surveys at highway bridges crossing the Missouri River in and into Missouri during summer flooding, July&#x2013;August 2011</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2012&#x2013;5204</volume>, <size units="page">166</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20125204">https://doi.org/10.3133/sir20125204</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r12"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2013</year>, <source>Results of repeat bathymetric and velocimetric surveys at the Amelia Earhart Bridge on U.S. Highway 59 over the Missouri River at Atchison, Kansas, 2009&#x2013;2013</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2013&#x2013;5177</volume>, <size units="page">50</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20135177">https://doi.org/10.3133/sir20135177</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r13"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2014</year>, <source>Bathymetric and velocimetric surveys at highway bridges crossing the Missouri River between Kansas City and St. Louis, Missouri, April&#x2013;May, 2013</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2014&#x2013;5116</volume>, <size units="page">79</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20145116">https://doi.org/10.3133/sir20145116</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r14"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2015</year>, <source>Bathymetric and velocimetric surveys at highway bridges crossing the Missouri and Mississippi Rivers on the periphery of Missouri, June 2014</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2015&#x2013;5048</volume>, <size units="page">81</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20155048">https://doi.org/10.3133/sir20155048</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r15"><mixed-citation publication-type="book">Huizinga, R.J., 2016, Bathymetric and velocimetric surveys at highway bridges crossing the Missouri River near Kansas City, Missouri, June 2&#x2013;4, 2015: U.S. Geological Survey Scientific Investigations Report 2016&#x2013;5061, 93 p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20165061">https://doi.org/10.3133/sir20165061</ext-link>.]</mixed-citation></ref>
<ref id="r16"><mixed-citation publication-type="book">Huizinga, R.J., 2017a, Bathymetric and velocimetric surveys at highway bridges crossing the Missouri and Mississippi Rivers near St. Louis, Missouri, May 23&#x2013;27, 2016: U.S. Geological Survey Scientific Investigations Report 2017&#x2013;5076, 102 p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20175076">https://doi.org/10.3133/sir20175076</ext-link>.]</mixed-citation></ref>
<ref id="r17"><mixed-citation publication-type="web">Huizinga, R.J., 2017b, Bathymetry and velocity data from surveys at highway bridges crossing the Missouri and Mississippi Rivers near St. Louis, Missouri, October 2008 through May 2016: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/F71C1VCC">https://doi.org/10.5066/F71C1VCC</ext-link>.</mixed-citation></ref>
<ref id="r18"><mixed-citation publication-type="book">Huizinga, R.J., 2020a, Bathymetric and velocimetric surveys at highway bridges crossing the Missouri River between Kansas City and St. Louis, Missouri, May 22&#x2013;31, 2017: U.S. Geological Survey Scientific Investigations Report 2020&#x2013;5018, 104 p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20205018">https://doi.org/10.3133/sir20205018</ext-link>.]</mixed-citation></ref>
<ref id="r19"><mixed-citation publication-type="web">Huizinga, R.J., 2020b, Bathymetry and velocity data from surveys at highway bridges crossing the Missouri River in Kansas City, Missouri, March 2010 through May 2017: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9L6GW57">https://doi.org/10.5066/P9L6GW57</ext-link>.</mixed-citation></ref>
<ref id="r20"><mixed-citation publication-type="web">Huizinga, R.J., 2020c, Bathymetry and velocity data from surveys at highway bridges crossing the Missouri River between Kansas City and St. Louis, Missouri, January 2010 through May 2017: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P94M4US7">https://doi.org/10.5066/P94M4US7</ext-link>.</mixed-citation></ref>
<ref id="r21"><mixed-citation publication-type="web">Huizinga, R.J., 2020d, Bathymetry and velocity data from surveys at highway bridges crossing the Missouri and Mississippi Rivers on the periphery of Missouri, December 2008 through August 2018: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9WDI9YF">https://doi.org/10.5066/P9WDI9YF</ext-link>.</mixed-citation></ref>
<ref id="r22"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2020</year><comment>e</comment>, <source>Bathymetric and velocimetric surveys at highway bridges crossing the Missouri and Mississippi Rivers on the periphery of Missouri, July&#x2013;August 2018</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2020&#x2013;5088</volume>, <size units="page">100</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20205088">https://doi.org/10.3133/sir20205088</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r23"><mixed-citation publication-type="web">Huizinga, R.J., 2021, Bathymetry and velocity data from surveys at highway bridges crossing the Missouri River in Kansas City, Missouri, in August 2019, August 2020, and October 2020: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P96TX8AE">https://doi.org/10.5066/P96TX8AE</ext-link>.</mixed-citation></ref>
<ref id="r24"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name>, <string-name><surname>Elliott</surname>, <given-names>C.M.</given-names></string-name>, and <string-name><surname>Jacobson</surname>, <given-names>R.B.</given-names></string-name></person-group>, <year>2010</year>, <source>Bathymetric and velocimetric survey and assessment of habitat for pallid sturgeon on the Mississippi River in the vicinity of the proposed Interstate 70 Bridge at St. Louis, Missouri</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2010&#x2013;5017</volume>, <size units="page">28</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20105017">https://doi.org/10.3133/sir20105017</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r25"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Huizinga</surname>, <given-names>R.J.</given-names></string-name>, and <string-name><surname>Rydlund</surname>, <given-names>P.H.</given-names>, <suffix>Jr</suffix></string-name></person-group>., <year>2004</year>, <source>Potential-scour assessments and estimates of scour depth using different techniques at selected bridge sites in Missouri</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2004&#x2013;5213</volume>, <size units="page">42</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20045213">https://doi.org/10.3133/sir20045213</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r26"><mixed-citation publication-type="book">HYPACK, Inc., 2018, HYPACK hydrographic survey software user manual: Middletown, Conn., HYPACK, Inc., 2434 p., accessed February 2020 at <ext-link ext-link-type="uri" xlink:href="https://www.hypack.com/file%20library/resource%20library/manuals/2018/2018-hypack-user-manual.pdf">https://www.hypack.com/file%20library/resource%20library/manuals/2018/2018-hypack-user-manual.pdf</ext-link>.</mixed-citation></ref>
<ref id="r27"><mixed-citation publication-type="book">International Hydrographic Organization, 2008, IHO standards for hydrographic surveys (5th ed.): Monaco, International Hydrographic Bureau, Special publication no. 44, 27 p.</mixed-citation></ref>
<ref id="r28"><mixed-citation publication-type="book">Mueller, D.S., Wagner, C.R., Rehmel, M.S., Oberg, K.A., and Rainville, F., 2013, Measuring discharge with acoustic Doppler current profilers from a moving boat (ver. 2.0, December 2013): U.S. Geological Survey Techniques and Methods, book 3, chap. A22, 95 p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/tm3A22">https://doi.org/10.3133/tm3A22</ext-link>.]</mixed-citation></ref>
<ref id="r29"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>National Marine Electronics Association</collab></person-group>, <year>2002</year>, <source>NMEA 0183&#x2014;Standard for interfacing marine electronic devices (ver. 3.01)</source>. <publisher-name>National Marine Electronics Association</publisher-name>, <size units="page">88</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r30"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Parsons</surname>, <given-names>D.R.</given-names></string-name>, <string-name><surname>Jackson</surname>, <given-names>P.R.</given-names></string-name>, <string-name><surname>Czuba</surname>, <given-names>J.A.</given-names></string-name>, <string-name><surname>Engel</surname>, <given-names>F.L.</given-names></string-name>, <string-name><surname>Rhoads</surname>, <given-names>B.L.</given-names></string-name>, <string-name><surname>Oberg</surname>, <given-names>K.A.</given-names></string-name>, <string-name><surname>Best</surname>, <given-names>J.L.</given-names></string-name>, <string-name><surname>Mueller</surname>, <given-names>D.S.</given-names></string-name>, <string-name><surname>Johnson</surname>, <given-names>K.K.</given-names></string-name>, and <string-name><surname>Riley</surname>, <given-names>J.D.</given-names></string-name></person-group>, <year>2013</year>, <article-title>Velocity Mapping Toolbox (VMT)&#x2014;A processing and visualization suite for moving-vessel ADCP measurements</article-title>: <source>Earth Surface Processes and Landforms</source>, v.&#x00A0;<volume>38</volume>, no.&#x00A0;<issue>11</issue>, p.&#x00A0;<fpage>1244</fpage>&#x2013;<lpage>1260</lpage><comment>. [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/esp.3367">https://doi.org/10.1002/esp.3367</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r31"><mixed-citation publication-type="other">Riverscapes Consortium, 2020, Geomorphic change detection software: Riverscapes Consortium, accessed December 2020 at <ext-link ext-link-type="uri" xlink:href="http://gcd.riverscapes.xyz/">http://gcd.riverscapes.xyz/</ext-link>.</mixed-citation></ref>
<ref id="r32"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Rydlund</surname>, <given-names>P.H.</given-names>, <suffix>Jr</suffix></string-name></person-group>., <year>2009</year>, <source>Real-time river channel-bed monitoring at the Chariton and Mississippi Rivers in Missouri, 2007&#x2013;09</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2009&#x2013;5254</volume>, <size units="page">27</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20095254">https://doi.org/10.3133/sir20095254</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r33"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Simons</surname>, <given-names>D.B.</given-names></string-name>, and <string-name><surname>Richardson</surname>, <given-names>E.V.</given-names></string-name></person-group>, <year>1966</year>, <source>Resistance to flow in alluvial channels</source>: <series>U.S. Geological Survey Professional Paper</series> <volume>422&#x2013;J</volume>, <size units="page">61</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/pp422J">https://doi.org/10.3133/pp422J</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r34"><mixed-citation publication-type="book">Simon, Li and Associates, 1985, Seasonal effects of river stage-discharge relations at selected gages, Final Report: Fort Collins, Colo., prepared for U.S. Army Corps of Engineers, Contract No. DACW43&#x2013;85&#x2013;D&#x2013;0017, 96 p.</mixed-citation></ref>
<ref id="r35"><mixed-citation publication-type="web">U.S. Army Corps of Engineers, 2004, Upper Mississippi River System flow frequency study, appendix E: Rock Island, Ill., U.S. Army Corps of Engineers, accessed December 2020 at <ext-link ext-link-type="uri" xlink:href="https://www.mvr.usace.army.mil/Portals/48/docs/FRM/UpperMissFlowFreq/App.%20E%20Kansas%20City%20Dist.%20Hydrology_Hydraulics.pdf">https://www.mvr.usace.army.mil/Portals/48/docs/FRM/UpperMissFlowFreq/App.%20E%20Kansas%20City%20Dist.%20Hydrology_Hydraulics.pdf</ext-link>.</mixed-citation></ref>
<ref id="r36"><mixed-citation publication-type="book">U.S. Army Corps of Engineers, 2013, Engineering and design&#x2014;Hydrographic surveying: Washington D.C., U.S. Army Corps of Engineers, manual no. EM 1110&#x2013;2&#x2013;1003, 560 p.</mixed-citation></ref>
<ref id="r37"><mixed-citation publication-type="web">U.S. Geological Survey, 2020, USGS water data for the Nation: U.S. Geological Survey National Water Information System database, accessed December 2020 at <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/F7P55KJN">https://doi.org/10.5066/F7P55KJN</ext-link>.</mixed-citation></ref>
<ref id="r38"><mixed-citation publication-type="web">U.S. Geological Survey, 2021, USGS Streamgage Statistics for station 06893000: U.S. Geological Survey WaterWatch toolkit, accessed April 2021 at <ext-link ext-link-type="uri" xlink:href="https://waterwatch.usgs.gov/index.php?sno=06893000&amp;ds=dv01d_por&amp;btnGo=GO&amp;m=sitempnn">https://waterwatch.usgs.gov/index.php?sno=06893000&amp;ds=dv01d_por&amp;btnGo=GO&amp;m=sitempnn</ext-link>.</mixed-citation></ref>
</ref-list>
<glossary content-type="Glossary">
<title>Glossary</title>
<def-list>
<def-item><term>bent</term><def><p>A vertical, load-bearing, intermediate bridge <bold>substructure</bold> unit between the ends of a bridge used to support the bridge at intermediate intervals, typically consisting of two or more <bold>piles</bold> (referred to as a &#x201C;pile bent&#x201D;) or <bold>columns,</bold> each supported by an individual <bold>footing</bold>, <bold>pile</bold>, or <bold>drilled shaft.</bold></p></def></def-item>
<def-item><term>caisson</term><def><p>An older type of bridge foundation consisting of a watertight retaining structure used as the foundation of a bridge <bold>pier</bold>, constructed in such a way that the water can be pumped out, keeping the work environment dry while the ground under the caisson is excavated and the caisson &#x201C;sunk&#x201D; into final position below the ground line. Upon reaching its final position, the caisson is backfilled with sand or gravel for added weight and stability.</p></def></def-item>
<def-item><term>cap</term><def><p>The upper or bearing part of a bridge <bold>pier</bold> or <bold>bent</bold>, usually made of concrete or hard stone and designed to distribute concentrated loads from the bridge <bold>superstructure</bold> evenly over the <bold>columns</bold> of the <bold>pier</bold> or <bold>bent</bold>.</p></def></def-item>
<def-item><term>cofferdam</term><def><p>A temporary retaining structure used in <bold>pier</bold> and <bold>pylon</bold> construction to retain water and support the sides of an excavation where water is present. A cofferdam generally consists of vertical sheet piling around the perimeter of a bracing system and a bottom <bold>seal course</bold>. Once sealed, the water can be pumped out, keeping the work environment dry while the <bold>footing</bold>, <bold>columns,</bold> and other <bold>substructural</bold> elements are built.</p></def></def-item>
<def-item><term>column</term><def><p>The primary part of a bridge <bold>bent</bold>, <bold>pier</bold>, or <bold>pylon</bold> used to convey the load of the bridge <bold>superstructure</bold> to the foundation.</p></def></def-item>
<def-item><term>drilled shaft</term><def><p>A cylindrical shaft that is drilled into the ground as a bridge foundation, typically extending through the alluvial material into underlying rock and filled with reinforced concrete.</p></def></def-item>
<def-item><term>footing</term><def><p>A part of the foundation of a bridge <bold>bent</bold>, <bold>pier</bold>, or <bold>pylon</bold> used to transmit the load from the <bold>column</bold> to the ground, either directly or indirectly through <bold>piles</bold> or <bold>drilled shafts.</bold></p></def></def-item>
<def-item><term>pedestal</term><def><p>A transitional element occasionally used in a bridge <bold>pier</bold> or <bold>pylon</bold>, typically found between the <bold>column</bold> and a <bold>footing</bold> or <bold>caisson</bold>.</p></def></def-item>
<def-item><term>pier</term><def><p>A vertical, load-bearing, intermediate bridge <bold>substructure</bold> unit between the ends of a bridge used to support the bridge at intermediate intervals, consisting of a single <bold>column</bold> or shaft, or multiple <bold>columns</bold> connected with a solid web, and generally supported by a single <bold>footing</bold>.</p></def></def-item>
<def-item><term>pile</term><def><p>A long, narrow cylinder or beam made of wood, metal, or concrete used as part of the foundation of a bridge, typically driven into the ground from above and integrated into a <bold>seal course</bold> of a pier, or the <bold>cap</bold> of a pile <bold>bent</bold>.</p></def></def-item>
<def-item><term>pylon</term><def><p>A tower-like vertical, load-bearing <bold>substructural</bold> unit that usually supports the cables of a suspension bridge or a cable-stayed bridge. A pylon typically extends above the bridge <bold>superstructure</bold>.</p></def></def-item>
<def-item><term>seal course</term><def><p>The base of a newer type of bridge foundation, created when a <bold>cofferdam</bold> used to build the foundation is &#x201C;sealed&#x201D; with concrete at the underwater ground level to prevent water from entering the <bold>cofferdam</bold> from below.</p></def></def-item>
<def-item><term>substructure</term><def><p>The part of a bridge that supports the <bold>superstructure</bold> and transmits the load of the <bold>superstructure</bold> and deck to the ground through the foundations.</p></def></def-item>
<def-item><term>superstructure</term><def><p>The part of a bridge that supports the bridge deck, and connects one <bold>substructural</bold> element to another and thereby transmits the load of the deck and anything on the deck to the <bold>substructure</bold>.</p></def></def-item>
<def-item><term>water year</term><def><p>A continuous 12-month period selected to present data relative to hydrologic or meteorological phenomena during which a complete annual hydrologic cycle normally occurs. The water year used by the U.S.&#x00A0;Geological Survey runs from October 1 through September 30, and is designated by the year in which it ends.</p></def></def-item>
</def-list>
</glossary>
<book-app-group>
<book-app id="a1"><book-part-meta>
<title-group>
<label>Appendix 1</label><title>Shaded Triangulated Irregular Network Images of the Channel and Side of Pier for Each Surveyed Pier</title>
</title-group>
</book-part-meta>
<body>
<p>Shaded triangulated irregular network images of the channel and side of pier were prepared for each surveyed pier at structure A1800 (<xref ref-type="fig" rid="fig01.01">fig.&#x00A0;1.1</xref>), structure A8340 (<xref ref-type="fig" rid="fig01.02">fig.&#x00A0;1.2</xref>), structure A4649 (<xref ref-type="fig" rid="fig01.03">figs.&#x00A0;1.3</xref>, <xref ref-type="fig" rid="fig01.04">1.4</xref>), structure A4060 (<xref ref-type="fig" rid="fig01.05">fig.&#x00A0;1.5</xref>), structure A7650 (<xref ref-type="fig" rid="fig01.06">fig.&#x00A0;1.6</xref>), structure A5817 (<xref ref-type="fig" rid="fig01.07">fig.&#x00A0;1.7</xref>), structure A0767 (<xref ref-type="fig" rid="fig01.08">figs.&#x00A0;1.8</xref>, <xref ref-type="fig" rid="fig01.09">1.9</xref>), and structures A4757 and L0568 (<xref ref-type="fig" rid="fig01.10">fig.&#x00A0;1.10</xref>).</p>
<fig id="fig01.01" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.1</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structure A1800 on Interstate 635 over the Missouri River in Kansas City, Missouri. <italic>A</italic>,&#x00A0;left (northeast) side of pier 3. <italic>B</italic>,&#x00A0;right (southwest) side of pier 3. <italic>C</italic>,&#x00A0;left (northeast) side of pier 2.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Interstate 635 bridge.</long-desc><graphic xlink:href="rol21-0068_fig01.01"/></fig>
<fig id="fig01.02" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.2</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel bents of structure A8340 on U.S.&#x00A0;Highway 69 over the Missouri River in Kansas City, Missouri. <italic>A</italic>,&#x00A0;left (north) side of bent 5. <italic>B</italic>,&#x00A0;right (south) side of bent 5. <italic>C</italic>,&#x00A0;left (north) side of bent 4. <italic>D</italic>,&#x00A0;right (south) side of bent 4. <italic>E</italic>,&#x00A0;left (north) side of bent 3.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at U.S. Highway 69 bridge.</long-desc><graphic xlink:href="rol21-0068_fig01.02"/></fig>
<fig id="fig01.03" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.3</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structure A4649 on U.S.&#x00A0;Highway 169 crossing the Missouri River in Kansas City, Missouri, on August 13, 2019, before installation of scour countermeasures. <italic>A</italic>,&#x00A0;left (northwest) side of pier 2. <italic>B</italic>,&#x00A0;right (southeast) side of pier 2. <italic>C</italic>,&#x00A0;left (northwest) side of pier 1.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at U.S. Highway 169 bridge on August 13, 2019.</long-desc><graphic xlink:href="rol21-0068_fig01.03"/></fig>
<fig id="fig01.04" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.4</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel pier&#x00A0;2 of structure A4649 on U.S.&#x00A0;Highway 169 crossing the Missouri River in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures. <italic>A</italic>,&#x00A0;left (northwest) side of pier 2. <italic>B</italic>,&#x00A0;right (southeast) side of pier 2.</p></caption>
<long-desc>Visualization of channel bottom and sides of main pier at U.S. Highway 169 bridge on October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig01.04"/></fig>
<fig id="fig01.05" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.5</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structure A4060 on State Highway 9 over the Missouri River in Kansas City, Missouri. <italic>A</italic>,&#x00A0;right (southeast) side of pier 4. <italic>B</italic>,&#x00A0;left (northwest) side of pier 5. <italic>C</italic>,&#x00A0;right (southeast) side of pier 5. <italic>D</italic>,&#x00A0;left (northwest) side of pier 6. <italic>E</italic>,&#x00A0;right (southeast) side of pier 6.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Missouri Highway 9 bridge.</long-desc><graphic xlink:href="rol21-0068_fig01.05"/></fig>
<fig id="fig01.06" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.6</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel pylon of structure A7650 on Interstate 35 over the Missouri River in Kansas City, Missouri. <italic>A</italic>,&#x00A0;left (northwest) side. <italic>B</italic>,&#x00A0;right (southeast) side.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Interstate 35 bridge.</long-desc><graphic xlink:href="rol21-0068_fig01.06"/></fig>
<fig id="fig01.07" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.7</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structure A5817 on State Highway 269 over the Missouri River in Kansas City, Missouri. <italic>A</italic>,&#x00A0;left (northwest) side of pier 2. <italic>B</italic>,&#x00A0;right (southeast) side of pier 2. <italic>C</italic>,&#x00A0;left (northwest) side of pier 3. <italic>D</italic>,&#x00A0;right (southeast) side of pier 3.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Missouri Highway 269 bridge.</long-desc><graphic xlink:href="rol21-0068_fig01.07"/></fig>
<fig id="fig01.08" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.8</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structure A0767 on Interstate 435 over the Missouri River in Kansas City, Missouri, on August 14, 2019, before installation of scour countermeasures. <italic>A</italic>,&#x00A0;right (south) side of pier 6. <italic>B</italic>,&#x00A0;left (north) side of pier 7. <italic>C</italic>,&#x00A0;right (south) side of pier 7. <italic>D</italic>,&#x00A0;left (north) side of pier 8. <italic>E</italic>,&#x00A0;right (south) side of pier 8.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Interstate 435 bridge on August 14, 2019.</long-desc><graphic xlink:href="rol21-0068_fig01.08"/></fig>
<fig id="fig01.09" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.9</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel pier 7 of structure A0767 on Interstate 435 over the Missouri River in Kansas City, Missouri, on October 23, 2020, after installation of scour countermeasures. <italic>A</italic>,&#x00A0;left (north) side of pier 7. <italic>B</italic>,&#x00A0;right (south) side of pier 7.</p></caption>
<long-desc>Visualization of channel bottom and sides of main pier at Interstate 435 bridge on October 23, 2020.</long-desc><graphic xlink:href="rol21-0068_fig01.09"/></fig>
<fig id="fig01.10" position="float" fig-type="figure"><?Figure Large?><label>Figure 1.10</label><caption><p>Shaded triangulated irregular network visualization of the channel bed and main channel piers of structures A4757 and L0568 on State Highway 291 over the Missouri River near Kansas City, Missouri. <italic>A</italic>,&#x00A0;right (south) side of piers 1C and 6. <italic>B</italic>,&#x00A0;left (north) side of piers 2C and 5. <italic>C</italic>,&#x00A0;right (south) side of piers 2C and 5.</p></caption>
<long-desc>Visualization of channel bottom and sides of piers at Missouri Highway 291 bridges.</long-desc><graphic xlink:href="rol21-0068_fig01.10"/></fig>
</body>
</book-app>
</book-app-group>
</book-back>
</book>
