<?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>
<contrib>
<aff><institution>U.S. Department of the Interior</institution></aff></contrib>
<contrib>
<aff><institution>U.S. Geological Survey</institution></aff></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">2026-5017</book-id>
<book-id book-id-type="doi">10.3133/sir20265017</book-id><book-title-group><book-title>Precipitation-Based Flood-Inundation Maps for the East Fork Little Blue River and Tributaries at Lee&#x2019;s Summit, Missouri, 2024</book-title>
<alt-title alt-title-type="sentence-case">Precipitation-based flood-inundation maps for the East Fork Little Blue River and tributaries at Lee&#x2019;s Summit, Missouri, 2024</alt-title>
<alt-title alt-title-type="running-head">Precipitation-Based Flood-Inundation Maps for the East Fork Little Blue River and Tributaries at Lee&#x2019;s Summit, Mo., 2024</alt-title></book-title-group>
<contrib-group content-type="collaborator">
<contrib><collab>Prepared in cooperation with the City of Lee&#x2019;s Summit, Missouri</collab></contrib>
</contrib-group>
<contrib-group content-type="authors">
<contrib contrib-type="author"><string-name><x>By</x><x> </x><given-names>Allison A.</given-names><x> </x><surname>Atkinson</surname></string-name></contrib>
</contrib-group>
<pub-date date-type="pub">
<year>2026</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>The U.S. Geological Survey, in cooperation with the City of Lee&#x2019;s Summit, Missouri, assessed flooding of the East Fork Little Blue River and tributaries for varying precipitation magnitudes and durations, varying antecedent runoff conditions, and projected climate-change conditions. The precipitation scenarios were used to develop a library of flood-inundation maps for a 2.95-mile reach of the East Fork Little Blue River and tributaries within the city.</p>
<p>A two-dimensional U.S.&#x00A0;Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System (HEC&#x2013;RAS; ver.&#x00A0;6.5) rain-on-grid model was calibrated to selected runoff events representing a range of antecedent runoff conditions and hydrologic responses. Lowest adjacent grades for structures within the nearby study area were incorporated into the terrain, and depth grids and water-surface elevation grids were developed for the study area. Simulated velocities at selected bridge locations were also developed from the model. The model was calibrated using water-surface elevation data collected from water-level loggers (pressure transducers) and streamflow measurements and water-surface elevation measurements made at a reference point during runoff events. The calibrated HEC&#x2013;RAS model was used to simulate streamflows from design rainfall events of 15-minute to 24-hour durations and ranging from a 100- to 0.1-percent annual exceedance probability (1-year to 1,000-year recurrence intervals). Flood-inundation maps were produced for depths at a reference location of 3 to 16&#x00A0;feet, or a depth exceeding the 0.1-percent annual exceedance probability interval precipitation. The results of each precipitation duration-frequency value were represented by a 1-foot-increment inundation map based on the generated peak streamflow from that rainfall event and the corresponding water-surface elevation at the East Fork Little Blue River reference location.</p>
<p>Within the HEC&#x2013;RAS model, 240&#x00A0;scenarios were developed from the design rainfall events with each of 3&#x00A0;antecedent conditions. Additional scenarios were created to simulate the effects of projected precipitation scenarios on the 100-year recurrence interval, 24-hour storm and the 100-year recurrence interval, 6-hour storm. All simulation results were assigned to a flood-inundation map condition based on the generated peak flow and corresponding water-surface elevation at the East Fork Little Blue River reference location.</p>
<p>The flood-inundation maps are shown on a web mapping application made available to the public through the City of Lee&#x2019;s Summit (hyperlink will be added when available). The flood-inundation maps are tied to real-time precipitation data obtained from the Automated Surface Observing System weather station at the Lee&#x2019;s Summit Municipal Airport, accessible at <ext-link ext-link-type="uri" xlink:href="https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS">https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS</ext-link>. The availability of these maps, along with information regarding observed rainfall, could help provide emergency management personnel and residents with information that is critical for flood-response activities, such as evacuations and road closures, and for postflood recovery efforts.</p></abstract>
<abstract abstract-type="plain-language-summary">
<title>Plain Language Summary</title>
<p>The U.S. Geological Survey, in cooperation with the City of Lee&#x2019;s Summit, Missouri, assessed flooding of the East Fork Little Blue River and tributaries for varying precipitation magnitudes and durations, varying antecedent runoff conditions, and projected climate-change conditions. The precipitation scenarios were used to develop a library of flood-inundation maps that included a 2.95-mile reach of the East Fork Little Blue River and tributaries within the city. The availability of these maps, along with information regarding observed rainfall, could help provide emergency management personnel and residents with information that is critical for flood-response activities, such as evacuations and road closures, and for postflood recovery efforts.</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="associated-data">
<p>Atkinson, A.A., 2026, Geospatial data and model archives associated with precipitation-driven flood-inundation mapping of the East Fork Little Blue River and associated tributaries at Lee&#x2019;s Summit, Missouri: U.S.&#x00A0;Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P13NSPHQ">https://doi.org/10.5066/P13NSPHQ</ext-link>.</p></notes>
<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>.</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> or contact the store at 1&#x2013;888&#x2013;275&#x2013;8747.</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 <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/survey-manual/11006-use-copyrighted-material-usgs-information-products">copyrighted items</ext-link> must be secured from the copyright owner.</p></notes>
</book-meta>
<front-matter>
<front-matter-part>
<named-book-part-body>
<fig fig-type="cover"><caption><p><bold>Cover.</bold> Map of the peak simulated flood-inundation extent of the East Fork Little Blue River in Lee's Summit, Missouri, for a precipitation amount of 7.19 inches in 6 hours.</p></caption></fig>
</named-book-part-body>
</front-matter-part>
<ack>
<title>Acknowledgments</title>
<p>The author acknowledges funding provided by the City of Lee&#x2019;s Summit, Missouri, for this study and thanks Kara Starlin, Environmental Specialist, and Karen Quackenbush, Senior Staff Engineer, with the City of Lee&#x2019;s Summit for their feedback throughout the project.</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="34.63%"/>
<col width="25.12%"/>
<col width="40.25%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Multiply</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">By</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">To obtain</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Length</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">inch (in.)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;2.54</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">centimeter (cm)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">inch (in.)</td>
<td valign="top" align="left">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;25.4</td>
<td valign="top" align="left">millimeter (mm)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">foot (ft)</td>
<td valign="top" align="left">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0.3048</td>
<td valign="top" align="left">meter (m)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">mile (mi)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;1.609</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">kilometer (km)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Area</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">square mile (mi<sup>2</sup>)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;2.590</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">square kilometer (km<sup>2</sup>)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Flow rate</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">foot per second (ft/s)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0.3048</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">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="left" style="border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;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>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Hydraulic gradient</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">foot per mile (ft/mi)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0.1894</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">meter per kilometer (m/km)</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="tb" position="float"><caption><title>International System of Units to U.S. customary units</title></caption>
<table rules="groups">
<col width="44.24%"/>
<col width="16.34%"/>
<col width="39.42%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Multiply</td>
<td valign="middle" align="char" char="." scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">By</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">To obtain</td>
</tr>
</thead>
<tbody>
<tr>
<th valign="middle" colspan="3" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Length</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">centimeter (cm)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.3937</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">inch (in.)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">meter (m)</td>
<td valign="top" align="left">3.281</td>
<td valign="top" align="left">foot (ft)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">meter (m)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">1.094</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">yard (yd)</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Temperature in degrees Fahrenheit (&#x00B0;F) may be converted to degrees Celsius (&#x00B0;C) as follows:</p>
<p>&#x00B0;C = (&#x00B0;F &#x2013; 32) / 1.8.</p>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Datums">
<book-part-meta>
<title-group>
<title>Datums</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>Vertical coordinate information is referenced to (1)&#x00A0;stage, the height above an arbitrary datum established at a streamgage, and (2)&#x00A0;elevation, the height above 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>Representative concentration pathway scenario stabilized radiative forcing is given in watts per square meter (W/m<sup>2</sup>).</p>
</named-book-part-body>
</front-matter-part>
<glossary content-type="Abbreviations"><title>Abbreviations</title>
<def-list><def-item><term>AEP</term>
<def>
<p>annual exceedance probability</p></def></def-item><def-item><term>ASOS</term>
<def>
<p>Automated Surface Observing System</p></def></def-item><def-item><term>CMIP</term>
<def>
<p>Coupled Model Intercomparison Project</p></def></def-item><def-item><term>CN</term>
<def>
<p>curve number</p></def></def-item><def-item><term>DEM</term>
<def>
<p>digital elevation model</p></def></def-item><def-item><term>FIS</term>
<def>
<p>flood-insurance study</p></def></def-item><def-item><term>GIS</term>
<def>
<p>geographic information system</p></def></def-item><def-item><term>HEC&#x2013;RAS</term>
<def>
<p>Hydrologic Engineering Center&#x2013;River Analysis System</p></def></def-item><def-item><term>lidar</term>
<def>
<p>light detection and ranging</p></def></def-item><def-item><term><italic>n-</italic>value</term>
<def>
<p>Manning&#x2019;s roughness coefficient</p></def></def-item><def-item><term>NOAA</term>
<def>
<p>National Oceanic and Atmospheric Administration</p></def></def-item><def-item><term>NSE</term>
<def>
<p>Nash-Sutcliffe efficiency</p></def></def-item><def-item><term>NWS</term>
<def>
<p>National Weather Service</p></def></def-item><def-item><term>RCP</term>
<def>
<p>representative concentration pathway used to project future greenhouse gas concentration scenarios</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>The City of Lee&#x2019;s Summit, in Jackson County in west-central Missouri (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>), had an estimated population of 101,108 in 2020 (<xref ref-type="bibr" rid="r27">U.S.&#x00A0;Census Bureau, 2021</xref>). The city has experienced moderate historical flooding from the East Fork Little Blue River and tributaries (City of Lee&#x2019;s Summit, written commun., 2023) along an area with a high population density within the city. Floodplains along the main stem of the East Fork Little Blue River and its tributaries are generally highly developed and contain mostly residential structures and a few commercial structures. Before this study, emergency responders in Lee&#x2019;s Summit, Missouri, relied on a few key information sources (all of which are available on the internet) to make decisions on how to best alert the public and mitigate flood damages. For example, the National Weather Service (NWS) issues watches, warnings, and advisories at <ext-link ext-link-type="uri" xlink:href="https://www.weather.gov/">https://www.weather.gov/</ext-link> (<xref ref-type="bibr" rid="r19">National Weather Service, 2025c</xref>). Precipitation information, in addition to the rainfall data provided by the Automated Surface Observing System (ASOS) at the Lee&#x2019;s Summit Municipal Airport, is available through Weather Underground&#x2019;s WunderMap (<xref ref-type="bibr" rid="r31">Weather Underground, 2025</xref>). Weather Underground&#x2019;s WunderMap also provides information from rain gages owned and operated by individual residents. Another source of information is the Federal Emergency Management Agency flood-insurance study (FIS) for Jackson County, Mo., and incorporated areas and Kansas City, which is available online and was most recently revised in December&#x00A0;2023 (<xref ref-type="bibr" rid="r8">Federal Emergency Management Agency, 2023</xref>). The maps included in the FIS provide flooding extents for the 1-percent annual exceedance probability (AEP) flood (100-year recurrence interval flood), but they do not provide any kind of dynamic mapping corresponding to current conditions nor do they provide detail on flood extents other than those for the 1-percent AEP flood.</p>
<fig id="fig01" position="float" fig-type="figure"><label>Figure 1</label><caption><p>Map showing the East Fork Little Blue River and associated tributaries study basin within the City of Lee&#x2019;s Summit in Jackson County, Missouri. Water-level monitoring locations are also shown.</p><p content-type="toc"><bold>Figure 1.</bold>&#x2003;Map showing the East Fork Little Blue River and associated tributaries study basin within the City of Lee&#x2019;s Summit in Jackson County, Missouri.</p></caption><long-desc>The East Fork Little Blue River Basin and main stem are in the southwestern part of the City of Lee&#x2019;s Summit, south of Lake Jacomo and Prairie Lee Lake. The discrete water-surface elevation measurement and discharge measurement site and three continuous water-surface elevation monitoring location sites are in the northern part of the basin.</long-desc><graphic xlink:href="rol25-0054_fig01"/></fig>
<p>In 2023, the U.S. Geological Survey (USGS), in cooperation with the City of Lee&#x2019;s Summit, Mo., began a project to develop a library of flood-inundation maps for a selected reach of the East Fork Little Blue River (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) and to relate these maps to different rainfall frequencies and durations. This study uses real-time precipitation data from the ASOS weather system at Lee&#x2019;s Summit Municipal Airport (also known as KLXT), which is near the East Fork Little Blue River study basin (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). Although having the water-surface elevation based on recent precipitation at a particular reference location is useful for residents near the location, this information is of limited use to residents farther upstream or downstream from the reference location because the resulting water-surface elevations are not constant across the drainage basin. Furthermore, knowledge of rainfall is difficult to translate into water levels or depths and areal extent of flooding.</p>
<p>The small drainage area (4.28&#x00A0;square miles) and highly developed nature of this selected reach of the East Fork Little Blue River Basin at Lee&#x2019;s Summit mean that floods will peak in a short amount of time; for some storms, the time to peak may be less than 2&#x00A0;hours. Because the times to the flood peak are rather short, it is difficult to provide advance notice of potential flooding. One way to address this informational gap is to produce a library of flood-inundation maps that are based on varying precipitation amounts and durations and referenced to the stream water-surface elevation levels recorded at a selected reference location. By referring to the appropriate map based on the amount of rainfall in a recent time period, emergency responders can discern the expected severity of flooding (depth of water, areal extent, water-surface elevations, and expected water velocities at key locations), identify roads that are or will soon be flooded, and make plans for notification or evacuation of residents in harm&#x2019;s way for the expected flooding at some distance upstream and downstream from a selected location. In addition, the capability to visualize the potential extent of flooding has been determined to motivate residents to heed flood warnings and take precautions that they previously might have disregarded.</p>
<sec>
<title>Purpose and Scope</title>
<p>This report describes the development of a series of estimated flood-inundation maps for the East Fork Little Blue River and its tributaries at Lee&#x2019;s Summit, Mo., and identifies where on the internet the maps and ancillary data (geographic information system [GIS] flood polygons, depth grids, water-surface elevation grids, and velocity markers at key locations) can be located and downloaded. The 2.95-mile-long study extent begins at Missouri State Highway&#x00A0;291, just north of the intersection with Blue Parkway, and flows northeast to NE Scruggs Road (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The maps were produced for flood conditions using simulated flood peaks from a range of precipitation totals and durations and reference water-surface elevations at the East Fork Little Blue River near NE Scruggs Road. The maps were produced from a hydraulic model calibrated to water-surface elevation data collected from three pressure transducers throughout the reach and to streamflow measurements and water-surface elevation measurements made at a reference point at the outlet of the basin near NE Scruggs Road. The pressure transducers were installed in the following locations: (1)&#x00A0;just downstream from NE Todd George Road (EFLB3), (2)&#x00A0;near NE Concord Street (EFLB2), and (3)&#x00A0;just upstream from NE Scruggs Road (EFLB1). All three pressure transducers were within the City of Lee&#x2019;s Summit. The reference point was just downstream from NE Scruggs Road (RF1; <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>).</p>
<p>The hydraulic model was used to simulate flood-inundation scenarios resulting from rainfall events of 15-minute to 24-hour durations and magnitudes ranging from a 100- to 0.1-percent AEP (1-year to 1,000-year recurrence interval). The procedures applied in constructing the hydraulic model are described within this report.</p>
<p>The flood-inundation maps produced from the model cover a range from 884 to 897&#x00A0;feet (ft) above the North American Vertical Datum of 1988, which translates to about 3 to 16&#x00A0;ft in water depth at the reference point RF1 that is immediately downstream from NE Scruggs Road. Generally, USGS flood-inundation maps are developed beginning at the NWS &#x201C;action stage&#x201D; or the stage that, when reached by a rising stream, requires the NWS or partner to take some type of mitigation action in preparation for possible substantial hydrologic activity. Because no NWS flood stages were already defined for this stream, some discretion was available to modelers in choosing a bankfull location where, once the water-surface elevation exceeded bankfull, the river would be considered to be flooding and maps would be generated. For this project, the EFLB1 location was chosen as the bankfull location (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). Once the simulated water-surface elevation exceeded bankfull at the EFLB1 location, maps were developed to represent 1-ft water-surface elevation changes at the reference point (RF1; <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) immediately downstream from NE Scruggs Road.</p>
</sec>
<sec>
<title>Study Area Description</title>
<p>The East Fork Little Blue River is in west-central Missouri, within the City of Lee&#x2019;s Summit in Jackson County (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The study basin is characterized by gently rolling topography with about 100&#x00A0;ft of relief as determined using the 2020 Jackson County digital elevation model (DEM; <xref ref-type="bibr" rid="r29">U.S.&#x00A0;Geological Survey, 2021a</xref>). The river begins near Missouri State Highway&#x00A0;291 and flows northeast to Prairie Lee Lake. Tributary A1 joins the main stem of the East Fork Little Blue River upstream from the study basin outlet (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). Tributary&#x00A0;A2 joins tributary&#x00A0;A1 about one-half mile upstream from the confluence of tributary A1 with the East Fork Little Blue River main stem (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The East Fork Little Blue River drains into Prairie Lee Lake about 0.5-mile downstream from the reference point at NE Scruggs Road (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The drainage area for the study reach, terminating at NE Scruggs Road, is 4.28&#x00A0;square miles, as determined using the USGS StreamStats utility (<xref ref-type="bibr" rid="r30">U.S.&#x00A0;Geological Survey, 2021b</xref>). The typical top-of-bank width in the study reach is 10&#x00A0;ft, and the channel slope is about 33&#x00A0;feet per mile.</p>
<p>About 94 percent of the land cover in the study reach drainage area is classified as &#x201C;developed&#x201D; and almost completely residential (<xref ref-type="bibr" rid="r5">Dewitz, 2023</xref>; <xref ref-type="fig" rid="fig02">fig. 2</xref>). The rest of the study area is classified as &#x201C;deciduous forest&#x201D; (1&#x00A0;percent), &#x201C;pasture/hay&#x201D; (3&#x00A0;percent), and &#x201C;cultivated crops&#x201D; (2&#x00A0;percent). The nondeveloped areas are near the outfall of the basin. Because the study reach is a developed area, roads and channel structures were considered to be of importance in the modeling process and the flood-inundation map generating process. According to the Missouri Department of Transportation&#x2019;s Functional Classification System for Lee&#x2019;s Summit (<xref ref-type="bibr" rid="r14">Missouri Department of Transportation, 2024</xref>), the study basin is traversed by one east-west minor arterial, one east-west freeway/expressway, one north-south principal arterial, and one north-south minor arterial (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). In the study hydraulic model, 21&#x00A0;channel structures (bridges and culverts) were included.</p>
<fig id="fig02" position="float" fig-type="figure"><label>Figure 2</label><caption><p>Map showing land cover for the East Fork Little Blue River and associated tributaries study basin based on the National Land Cover Database land-cover types (<xref ref-type="bibr" rid="r5">Dewitz, 2023)</xref>.</p><p content-type="toc"><bold>Figure 2.</bold>&#x2003;Map showing land cover for the East Fork Little Blue River and associated tributaries study basin based on the National Land Cover Database land-cover types.</p></caption><long-desc>The most prevalent types of land cover in the study basin are developed (low, medium, and high intensity) based on the National Land Cover Database land-cover types.</long-desc><graphic xlink:href="rol25-0054_fig02"/></fig>
</sec>
<sec>
<title>Previous Studies</title>
<p>Probabilistic flood-inundation maps showing the extent of flood inundation for the 1-percent AEP flood previously were generated as part of the latest FIS for the East Fork Little Blue River and the City of Lee&#x2019;s Summit (<xref ref-type="bibr" rid="r8">Federal Emergency Management Agency, 2023</xref>). The FIS also provides estimates of peak streamflows of 10-, 2-, 1-, and 0.2-percent AEPs and their associated water-surface elevations for the East Fork Little Blue River, tributary&#x00A0;A1, and tributary&#x00A0;A2. The Flood Insurance Rate Map for this area was last revised in 2017, and the streamflow values within the FIS were last revised in 1999 (<xref ref-type="bibr" rid="r8">Federal Emergency Management Agency, 2023</xref>). This study was begun with a furnished model that was developed as part of an ongoing FIS update (Alicia Williams, WSP, Inc., written commun., 2023).</p>
</sec>
</sec>
<sec>
<title>Creation of Flood-Inundation-Map Library</title>
<p>The USGS has standardized the procedures for creating flood-inundation maps for flood-prone communities (<xref ref-type="bibr" rid="r28">U.S.&#x00A0;Geological Survey, 2018</xref>) so that the process followed and products produced are similar regardless of which USGS office is responsible for the work. Tasks specific to the development of the flood maps for this study generally fell into three categories: (1)&#x00A0;collecting hydrologic and topographic data, (2)&#x00A0;calibrating parameters associated with the model, and (3)&#x00A0;running selected storm scenarios and processing the results. Data collection consisted of acquiring and developing the combined hydrologic and hydraulic model for the East Fork Little Blue River study basin, collecting streamflow measurements and high-water marks for high-flow events during the study period through the use of pressure transducers and field visits, and collecting rainfall data from NWS records and processing the rainfall data for use in the model using GIS software. Calibrating the model involved calibrating the curve number (CN) parameters associated with the hydrologic component of the U.S.&#x00A0;Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System (HEC&#x2013;RAS) computer program (ver.&#x00A0;6.5; <xref ref-type="bibr" rid="r25">U.S. Army Corps of Engineers, 2024</xref>) rain-on-grid model and calibrating energy-loss factors (roughness coefficients) in the stream channel and floodplain associated with the hydraulic component of the model. The final category of tasks, running the selected storm scenarios and processing the results, involved running selected storm scenarios developed from NWS records, computing water-surface profiles using the HEC&#x2013;RAS model, producing estimated flood-inundation maps for the selected study reach using HEC&#x2013;RAS and GIS, and preparing the maps as shapefile polygons that depict the areal extent of flood inundation at various stages and as depth and water-surface elevation grids that provide the depth and water-surface elevations of floodwaters shown on a USGS flood-inundation mapping application. Additionally, peak velocities were derived from the HEC&#x2013;RAS results at locations just downstream from selected hydraulic structures.</p>
<sec>
<title>Computation of Water-Surface Profiles from Precipitation-Derived Streamflow</title>
<p>Flood stages at the reference point location RF1 at NE Scruggs Road (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) were determined from an estimated bankfull water-surface elevation threshold. Flood hydrographs were generated for varying rainfall magnitudes and durations using the calibrated model.</p>
</sec>
<sec>
<title>Hydraulic Data</title>
<p>This study uses hydraulic data from discrete streamflow measurements and discrete and continuous stage measurements made at pressure transducer locations (EFLB1, EFLB2, and EFLB3) on the East Fork Little Blue River and tributary A1 upstream from NE Scruggs Road (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) and discrete streamflow and water-surface elevation measurements made at RF1 (<xref ref-type="table" rid="t01">table&#x00A0;1</xref>). Two other pressure transducers were also initially installed in the basin but were ultimately removed because of continued vandalism, and no usable data were available from the removed pressure transducers for the calibration process. Discrete streamflow measurements during selected high-flow events were collected in accordance with techniques provided in <xref ref-type="bibr" rid="r24">Turnipseed and Sauer (2010)</xref>. Stage at pressure transducer locations (continuous water-surface elevation monitoring locations; <xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) was measured every 5&#x00A0;minutes using a submersible data logger, and data were corrected for atmospheric pressure changes using continuous (5-minute increments) barometric pressure data. The stage data at the pressure transducer locations were converted to water-surface elevations referenced to the North American Vertical Datum of 1988 by adding the relevant elevation of the pressure transducer (<xref ref-type="table" rid="t01">table&#x00A0;1</xref>). The time-series data for the pressure transducers used in this study are available in an accompanying USGS data release (<xref ref-type="bibr" rid="r1">Atkinson, 2026</xref>). A level&#x00A0;IV survey (<xref ref-type="bibr" rid="r22">Rydlund and Densmore, 2012</xref>) procedure was used in acquiring reference elevations for pressure transducer locations in the study reach. The pressure transducer locations were used as calibration points in the hydraulic modeling.</p>
<table-wrap id="t01" position="float"><label>Table 1</label><caption>
<title>Locations of pressure transducers where continuous water-surface elevation data were recorded and the location of the reference point where discrete streamflow and water-surface elevation measurements were made.</title>
<p content-type="toc"><bold>Table 1.</bold>&#x2003;Locations of pressure transducers where continuous water-surface elevation data were recorded and the location of the reference point where discrete streamflow and water-surface elevation measurements were made.</p>
<p>[&#x00B0;, degree; N, north; W, west; ft, foot; &#x02B9;, minute; &#x02BA;, second]</p></caption>
<table rules="groups">
<col width="10.53%"/>
<col width="22.28%"/>
<col width="13.34%"/>
<col width="16.63%"/>
<col width="20.03%"/>
<col width="17.19%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Point name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Type of data recorded</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Stream reach</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Latitude (&#x00B0;N)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Longitude (&#x00B0;W)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Elevation (ft)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">EFLB1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Continuous water-surface elevations</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">East Fork Little Blue River</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">38&#x00B0;55&#x02B9;51&#x02BA;</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">94&#x00B0;19&#x02B9;44&#x02BA;</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">884.05</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB2</td>
<td valign="top" align="left">Continuous water-surface elevations</td>
<td valign="top" align="left">Tributary A1</td>
<td valign="top" align="left">38&#x00B0;55&#x02B9;27&#x02BA;</td>
<td valign="top" align="left">94&#x00B0;19&#x02B9;48&#x02BA;</td>
<td valign="top" align="left">898.89</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB3</td>
<td valign="top" align="left">Continuous water-surface elevations</td>
<td valign="top" align="left">East Fork Little Blue River</td>
<td valign="top" align="left">38&#x00B0;55&#x02B9;11&#x02BA;</td>
<td valign="top" align="left">94&#x00B0;20&#x02B9;18&#x02BA;</td>
<td valign="top" align="left">917.56</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">RF1</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Discrete streamflow measurements and water-surface elevations during calibration events</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">East Fork Little Blue River</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">38&#x00B0;55&#x02B9;51&#x02BA;</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">94&#x00B0;19&#x02B9;44&#x02BA;</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">881.40</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Hydrologic and Hydraulic Model Development</title>
<p>A combined hydrologic and hydraulic model was used to simulate the peak streamflow for the East Fork Little Blue River using design rainfall events covering a range of magnitudes and probabilities of exceedance. The combined model was developed using the U.S.&#x00A0;Army Corps of Engineers modeling system HEC&#x2013;RAS (ver.&#x00A0;6.5; <xref ref-type="bibr" rid="r25">U.S.&#x00A0;Army Corps of Engineers, 2024</xref>). HEC&#x2013;RAS is capable of running one-dimensional, step-backwater models for simulation of water-surface profiles with steady-state (gradually varied) flows and running one-dimensional and two-dimensional unsteady-state flow computations. The two-dimensional unsteady-state hydrologic and hydraulic model used for this study was originally developed for a detailed (Federal Emergency Management Agency zone AE) excess-rain-on-grid study by WSP, Inc. (formerly Wood E&amp;IS), using HEC&#x2013;RAS (ver.&#x00A0;6.2) in the year 2022 (Alicia Williams, WSP, Inc., written commun., 2023).</p>
<p>The two-dimensional HEC&#x2013;RAS rain-on-grid model was calibrated using a series of event calibrations that represented a variety of antecedent moisture conditions and flow conditions with water-surface elevations measured at three pressure transducers: EFLB1, EFLB2, and EFLB3 (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The model was also calibrated to discrete streamflow measurements made at a reference location just downstream from NE Scruggs Road (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). The primary calibration event was on July&#x00A0;1, 2024; this storm most closely matched the hydrograph of the simulated storms and captured a 4-percent AEP event during &#x201C;normal&#x201D; antecedent moisture conditions. An additional calibration event was on April&#x00A0;28, 2024 (&#x201C;wet&#x201D; antecedent moisture conditions), and a third calibration event was on May&#x00A0;2, 2024 (&#x201C;dry&#x201D; antecedent moisture conditions with no initial abstractions). According to the Natural Resources Conservation Service, initial abstractions consist primarily of &#x201C;interception, infiltration during early parts of the storm, and surface depression storage&#x201D; (<xref ref-type="bibr" rid="r20">Natural Resources Conservation Service, 2004</xref>, chap.&#x00A0;10, p.&#x00A0;10&#x2013;3). The calibrated two-dimensional HEC&#x2013;RAS rain-on-grid model was then used to simulate precipitation runoff from National Oceanic and Atmospheric Administration (NOAA) Atlas&#x00A0;14 rainfall events covering a range of 15&#x00A0;minutes to 24&#x00A0;hours in duration and AEPs of 100 to 0.1&#x00A0;percent (<xref ref-type="bibr" rid="r1">Atkinson, 2026</xref>) and selected rainfall events modified based on projected climate-change scenarios. For this study, the NOAA Atlas&#x00A0;14 partial-duration series was used. The data release accompanying this study (<xref ref-type="bibr" rid="r1">Atkinson, 2026</xref>) includes the model input files such as the rainfall events. The partial-duration series calculates storm depths using all storm values greater than a base value, as opposed to the annual maximum series, which only includes the greatest values for each year (<xref ref-type="bibr" rid="r13">Miller, 1964</xref>). The NOAA Atlas&#x00A0;14 precipitation frequency results were originally downloaded in recurrence interval format (years). In this study, the recurrence interval was converted to AEP for reporting purposes.</p>
<sec>
<title>Model Scenarios</title>
<p>For this study, 248 overall hydrologic and hydraulic model scenarios were developed (<xref ref-type="table" rid="t02">table&#x00A0;2</xref>). Because of the similarities among the results of the different combinations of magnitude and duration, the final results were condensed into 14&#x00A0;representative stage conditions. These scenarios included the probabilistic storm simulations and &#x201C;dry,&#x201D; &#x201C;normal,&#x201D; and &#x201C;wet&#x201D; antecedent runoff condition variations. The probabilistic simulated storms are modeled as simple events; that is, they are stand alone and do not take into account possible combined effects that would result from multiple successive storms and runoff peaks. Climate-change conditions were developed based on the Coupled Model Intercomparison Project (CMIP) Climate Data Processing Tool&#x00A0;2.1, which was created by the Federal Highway Administration (<xref ref-type="bibr" rid="r12">Kilgore and others, 2021</xref>).</p>
<table-wrap id="t02" position="float"><label>Table 2</label><caption>
<title>Description of U.S. Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System model scenarios developed in the study.</title>
<p content-type="toc"><bold>Table 2.</bold>&#x2003;Description of U.S. Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System model scenarios developed in the study.</p>
<p>[CNII, Soil Conservation Service runoff curve number representing a &#x201C;normal&#x201D; antecedent runoff condition; yr, year; min, minute; hr, hour; CNI, Soil Conservation Service runoff curve number representing a &#x201C;dry&#x201D; antecedent runoff condition; NOAA, National Oceanic and Atmospheric Administration; CNIII, Soil Conservation Service runoff curve number representing a &#x201C;wet&#x201D; antecedent runoff condition; RCP, representative concentration pathway used to project future greenhouse gas concentration scenarios; RCP 4.5 30 yr, representative concentration pathway of 4.5 watts per square meter and 30 years in the future; RCP 4.5 50 yr, representative concentration pathway of 4.5 watts per square meter and 50 years in the future; RCP 8.5 30 yr, representative concentration pathway of 8.5 watts per square meter and 30 years in the future; RCP 8.5 50 yr, representative concentration pathway of 8.5 watts per square meter and 50 years in the future]</p></caption>
<table rules="groups">
<col width="14.88%"/>
<col width="27.37%"/>
<col width="33.57%"/>
<col width="24.18%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Model scenario</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Antecedent runoff condition</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Storm scenarios</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Climate scenario</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">CNII, normal</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">1 yr, 15 min</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">2</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">3</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">4</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">5</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">6</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">7</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">8</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">9</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">11</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">12</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">13</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">14</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">15</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">16</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">2 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">17</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">18</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">19</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">20</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">21</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">22</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">23</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">24</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">5 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">25</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">26</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">27</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">28</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">29</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">30</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">31</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">32</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">10 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">33</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">34</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">35</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">36</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">37</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">38</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">39</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">40</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">25 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">41</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">42</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">43</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">44</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">45</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">46</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">47</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">48</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">50 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">49</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">50</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">51</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">52</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">53</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">54</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">55</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">56</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">57</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">58</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">59</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">60</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">61</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">62</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">63</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">64</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">200 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">65</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">66</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">67</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">68</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">69</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">70</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">71</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">72</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">500 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">73</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 15 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">74</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 30 min</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">75</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 1 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">76</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 2 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">77</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 3 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">78</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 4 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">79</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">80</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">1,000 yr, 24 hr</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">81&#x2013;160</td>
<td valign="top" align="left">CNI, dry</td>
<td valign="top" align="left">All NOAA Atlas 14 simulated storms</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">161&#x2013;240</td>
<td valign="top" align="left">CNIII, wet</td>
<td valign="top" align="left">All NOAA Atlas 14 simulated storms</td>
<td valign="top" align="left">Base</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">241</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">242</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">243</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">244</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 8.5 50 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">245</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">246</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">247</td>
<td valign="top" align="left">CNII, normal</td>
<td valign="top" align="left">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">248</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">CNII, normal</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">100 yr, 24 hr</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">RCP 8.5 50 yr</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="sir20265017.PrecipitationData">
<title>Precipitation Data</title>
<p>Accurate precipitation data are needed as inputs to the hydrologic model to simulate the resulting runoff and stream profiles. The precipitation data used for model calibration events were from NOAA&#x2019;s Multi-Radar Multi-Sensor system (<xref ref-type="bibr" rid="r11">Iowa State University of Science and Technology, 2024b</xref>). The precipitation data used for the model scenarios were probabilistic precipitation magnitudes associated with storm durations of 15&#x00A0;minutes to 24&#x00A0;hours at a single location within the basin (<xref ref-type="bibr" rid="r16">National Oceanic and Atmospheric Administration, 2024</xref>). To more closely align the methodology for processing the precipitation from the radar source with that of the point-source data to be used in practice, the gridded radar data were converted to a time series and averaged within four subbasins in the study area (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). In practice, precipitation data used for the display and interpretation of the flood-inundation maps would be obtained from the NWS&#x2019;s ASOS network site at the Lee&#x2019;s Summit Municipal Airport (<xref ref-type="bibr" rid="r10">Iowa State University of Science and Technology, 2024a</xref>).</p>
<p>Probabilistic precipitation events used as inputs to the hydrologic model for the modeled scenarios (<xref ref-type="table" rid="t02">table&#x00A0;2</xref>) were developed from the NOAA Atlas&#x00A0;14 point-precipitation frequency estimates (<xref ref-type="bibr" rid="r16">National Oceanic and Atmospheric Administration, 2024</xref>). The Atlas&#x00A0;14 event duration values were refined to include additional 4-hour duration events for this small study basin. The precipitation values for the 4-hour storms were interpolated by fitting a logarithmic trend line to the 5-, 10-, 15-, and 30-minute and 1-, 2-, 3-, 6-, 12-, and 24-hour duration values for each recurrence interval (<xref ref-type="fig" rid="fig03">fig.&#x00A0;3</xref>). The values represent a total amount of rainfall for the specified time duration. The storm distributions, or time series of precipitation based on the Atlas&#x00A0;14 totals, were developed by distributing the precipitation in 5-minute increments over the storm duration using an alternating block distribution approach (<xref ref-type="bibr" rid="r2">Chow and others, 1988</xref>).</p>
<fig id="fig03" position="float" fig-type="figure"><label>Figure 3</label><caption><p>Graph showing examples of the interpolation of 4-hour precipitation totals for 1-, 2-, and 5-year recurrence interval frequencies (100-, 50-, and 20-percent annual exceedance probabilities) using provided 5-, 10-, 15-, and 30-minute and 1-, 2-, 3-, 6-, 12-, and 24-hour precipitation values from the National Oceanic and Atmospheric Administration Atlas&#x00A0;14 precipitation frequency estimates (<xref ref-type="bibr" rid="r16">National Oceanic and Atmospheric Administration, 2024</xref>).</p><p content-type="toc"><bold>Figure 3.</bold>&#x2003;Graph showing examples of the interpolation of 4-hour precipitation totals for 1-, 2-, and 5-year recurrence interval frequencies using provided 5-, 10-, 15-, and 30-minute and 1-, 2-, 3-, 6-, 12-, and 24-hour precipitation values from the National Oceanic and Atmospheric Administration Atlas 14 precipitation frequency estimates.</p></caption><long-desc>Logarithmic trend lines are used to interpolate the 4-hour precipitation totals for three of the storm recurrence intervals used in the study. Precipitation is highest for the 5-year recurrence interval and lowest for the 1-year recurrence interval.</long-desc><graphic xlink:href="rol25-0054_fig03"/></fig>
</sec>
<sec>
<title>Infiltration Method</title>
<p>The volume of precipitation in the HEC&#x2013;RAS rain-on-grid model exceeding soil infiltration and storage is calculated and transformed into runoff using the Soil Conservation Service CN loss model with initial abstractions (<xref ref-type="bibr" rid="r23">Soil Conservation Service, 1986</xref>; <xref ref-type="bibr" rid="r20">Natural Resources Conservation Service, 2004</xref>). The infiltration layer in HEC&#x2013;RAS was created by combining a Soil Survey Geographic database (<xref ref-type="bibr" rid="r21">Natural Resources Conservation Service, 2022</xref>) soils layer and the 2021 land cover from the National Land Cover Database (<xref ref-type="bibr" rid="r5">Dewitz, 2023</xref>).</p>
<p>For this project, initial abstraction values, representing the amount of soil storage before runoff, were applied to each CN value. The initial abstraction values were chosen from <xref ref-type="bibr" rid="r23">Soil Conservation Service (1986</xref>, table&#x00A0;4&#x2013;1). Using the Soil Conservation Service CN approach, antecedent runoff conditions were divided into three classes: CNI for &#x201C;dry,&#x201D; CNII for &#x201C;normal,&#x201D; and CNIII for &#x201C;wet&#x201D; antecedent runoff conditions (<xref ref-type="bibr" rid="r23">Soil Conservation Service, 1986</xref>). All three antecedent runoff conditions were simulated in this study. The initial average, or &#x201C;normal,&#x201D; runoff condition (CNII) values used in this model were converted to initial estimates of &#x201C;dry&#x201D; conditions (CNI) and &#x201C;wet&#x201D; conditions (CNIII) using the following equations from <xref ref-type="bibr" rid="r2">Chow and others (1988)</xref>:<disp-formula id="e01"><alternatives><mml:math id="m1"><mml:mrow><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>I</mml:mtext><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mn>4.2</mml:mn><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>II</mml:mtext></mml:mrow><mml:mrow><mml:mn>10</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mn>0.058</mml:mn><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>II</mml:mtext></mml:mrow></mml:mfrac></mml:mrow></mml:math><graphic position="anchor" xlink:href="rol25-0054_m01"/></alternatives><label>(1)</label></disp-formula>and<disp-formula id="e02"><alternatives><mml:math id="m2"><mml:mrow><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>III</mml:mtext><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mn>23</mml:mn><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>II</mml:mtext></mml:mrow><mml:mrow><mml:mn>10</mml:mn><mml:mo>+</mml:mo><mml:mn>0.13</mml:mn><mml:mi>C</mml:mi><mml:mi>N</mml:mi><mml:mtext>II</mml:mtext></mml:mrow></mml:mfrac></mml:mrow></mml:math><graphic position="anchor" xlink:href="rol25-0054_m02"/></alternatives><label>(2)</label></disp-formula>After the initial calculation of the CN values for the &#x201C;dry&#x201D; and &#x201C;wet&#x201D; antecedent runoff conditions was completed, the values were further refined manually during the calibration process.</p>
</sec>
<sec>
<title>Streamflow Routing and Antecedent Flow</title>
<p>In a two-dimensional HEC&#x2013;RAS hydrologic and hydraulic rain-on-grid model, &#x201C;each computational cell face is evaluated similar to a cross section and is pre-processed into detailed hydraulic property tables&#x201D; (<xref ref-type="bibr" rid="r26">U.S.&#x00A0;Army Corps of Engineers, 2025</xref>). For these types of models, the routing method depends on the equations chosen to run the model because water-surface elevations, velocities, and depths are calculated at each cell face based on the equations chosen (<xref ref-type="bibr" rid="r26">U.S.&#x00A0;Army Corps of Engineers, 2025</xref>). For this study, the model computations were completed using the shallow water equations method (<xref ref-type="bibr" rid="r26">U.S.&#x00A0;Army Corps of Engineers, 2025</xref>).</p>
<p>To calibrate the model, antecedent flows were added to the East Fork Little Blue River, tributary&#x00A0;A1, and tributary&#x00A0;A2. The antecedent flow added to the East Fork Little Blue River was 10&#x00A0;cubic feet per second, and the antecedent flow added to both of the tributaries was 5&#x00A0;cubic feet per second. Adding the antecedent flows generated water-surface elevations that matched the observed water-surface elevations before the simulated storm event began. These antecedent flow values were held constant throughout the calibration simulations. For continuity purposes, these antecedent flows were also included in the probabilistic simulations.</p>
</sec>
<sec>
<title>Topographic and Bathymetric Data</title>
<p>The elevation data used in the HEC&#x2013;RAS model were obtained from a 1-meter DEM that was derived from light detection and ranging (lidar) data collected by Quantum Spatial, Inc., between April and December&#x00A0;2020 (<xref ref-type="bibr" rid="r29">U.S.&#x00A0;Geological Survey, 2021a</xref>). As per USGS quality level&#x00A0;2 data-accuracy specifications (ver.&#x00A0;1.2; <xref ref-type="bibr" rid="r9">Heidemann, 2018</xref>), the lidar data required a nonvegetated vertical accuracy of a maximum of 30&#x00A0;centimeters at the 95th&#x00A0;percentile. For the DEM used in this study, the nonvegetated vertical accuracy had a tested value of 8.12&#x00A0;centimeters at the 95th&#x00A0;percentile confidence level. Channel bathymetry at the reference location was verified by the USGS using channel bottom elevations the USGS hydrologist obtained while making streamflow measurements.</p>
</sec>
<sec>
<title>Hydraulic Structures</title>
<p>In the hydraulic model of the East Fork Little Blue River and its tributaries, 21&#x00A0;hydraulic structures are represented. These 21&#x00A0;structures include 3&#x00A0;four-lane road crossings and 3&#x00A0;extended pipe culverts and have the potential to affect water-surface elevations during flooding along the stream. The rest of the culverts and bridges are two-lane road crossings. All bridge-geometry information is contained in the hydraulic models used for analyses and provided in <xref ref-type="bibr" rid="r1">Atkinson (2026)</xref>.</p>
</sec>
<sec>
<title>Energy-Loss Factors</title>
<p>Hydraulic analysis requires the estimation of energy losses that result from frictional resistance exerted by a channel on flow. These energy losses are quantified by the Manning&#x2019;s roughness coefficient (<italic>n-</italic>value). Initial <italic>n</italic>-values were refined on the basis of field observations, aerial imagery, and the land-cover data downloaded from <xref ref-type="bibr" rid="r5">Dewitz (2023)</xref>. During the calibration process, the initial <italic>n</italic>-values were varied by flow and adjusted until the differences between simulated and observed water-surface elevations at the calibration locations (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) were minimized. Calibration regions were added to simulate the channel bottom throughout the reach and the overbank areas near the pressure transducer locations EFLB2 and EFLB3. The final <italic>n</italic>-values ranged from 0.015 for paved areas to 0.16 for wooded areas. The channel <italic>n</italic>-value was 0.05. The channel coefficient was consistent along the length of the East Fork Little Blue River channel and all tributaries. The highest <italic>n</italic>-values were detected in wooded residential areas. Some of these areas were in the overbank area, but others were scattered throughout nearby parks and fields. The lowest <italic>n</italic>-values were in open parking lot areas and on the streets and cul-de-sacs.</p>
</sec>
<sec>
<title>Model Boundary Conditions</title>
<p>The HEC&#x2013;RAS analysis for this study was completed using the two-dimensional unsteady-state flow computation option. Inflow boundary conditions consisted of (1)&#x00A0;precipitation time series applied to the entire study basin using the &#x201C;precipitation&#x201D; boundary condition and (2)&#x00A0;constant flow hydrographs applied to the channels within the study basin using the &#x201C;flow hydrograph&#x201D; boundary condition. The input hydrographs for the HEC&#x2013;RAS model scenarios were generated using a range of precipitation frequency-duration events, as detailed in the &#x201C;<xref ref-type="sec" rid="sir20265017.PrecipitationData">Precipitation Data</xref>&#x201D; section. The model used the original shallow water equations, Eulerian-Lagrangian method to calculate the water-surface elevations (<xref ref-type="bibr" rid="r25">U.S.&#x00A0;Army Corps of Engineers, 2024</xref>). Normal depth, based on an estimated average water-surface slope of 0.01&#x00A0;foot per foot, was used as the downstream boundary condition.</p>
</sec>
<sec>
<title>Model Calibration</title>
<p>The HEC&#x2013;RAS model was calibrated to observed streamflow-stages collected during the April&#x00A0;28, 2024; May&#x00A0;2, 2024, and July&#x00A0;1, 2024, events at the reference point RF1 and to observed continuous water-surface elevations at the pressure transducer locations (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). Although the July&#x00A0;1 event was considered the primary event because the hydrograph pattern of the event followed a pattern similar to the modeled storms, the model was also calibrated to the other events to capture the full range of antecedent moisture conditions. Model calibration was completed by adjusting CN values until the results of the computations closely agreed with the observed water-surface elevations with a primary focus of calibration at the reference point RF1 (<xref ref-type="fig" rid="fig04">fig.&#x00A0;4<italic>A</italic>&#x2013;<italic>C</italic></xref>). In limited cases, the channel terrain was modified to provide a uniform channel. The channel and tributaries are small and narrow; consequently, the pixelation of the lidar-derived terrain could result in unreasonable fluctuations in water-surface levels.</p>
<fig id="fig04" position="float" fig-type="figure"><label>Figure 4</label><caption><p>Graphs showing observed and simulated water-surface elevations and profiles for the flood events on the East Fork Little Blue River and tributaries at Lee&#x2019;s Summit, Missouri, at the EFLB1 location. <italic>A</italic>,&#x00A0;April&#x00A0;28, 2024; <italic>B</italic>,&#x00A0;May&#x00A0;2, 2024; <italic>C</italic>,&#x00A0;July&#x00A0;1, 2024.</p><p content-type="toc"><bold>Figure 4.</bold>&#x2003;Graphs showing observed and simulated water-surface elevations and profiles for the flood events on the East Fork Little Blue River and tributaries at Lee&#x2019;s Summit, Missouri, at the EFLB1 location.</p></caption><long-desc>The simulated and recorded water-surface elevations for the calibration storms at the EFLB1 location are the most similar for July 1, 2024, and differ the most for May 2, 2024.</long-desc><graphic xlink:href="rol25-0054_fig04"/></fig>
<p>Simulated water-surface elevations generally were within 0.51&#x00A0;ft of observed values, with the exception of the location of pressure transducer EFLB2 (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). For the July&#x00A0;1 event, the primary event, the difference between the observed and simulated water-surface elevation at the reference point RF1 was 0.06&#x00A0;ft (<xref ref-type="table" rid="t03">table&#x00A0;3</xref>). The differences during the July&#x00A0;1 event were 0.33&#x00A0;ft, 0.72&#x00A0;ft, and 0.10&#x00A0;ft for EFLB1, EFLB2, and EFLB3, respectively. Water-surface elevation comparisons between the simulated storms and the observed water-surface elevations at the EFLB1 location are shown in <xref ref-type="fig" rid="fig04">figure&#x00A0;4<italic>A</italic>&#x2013;<italic>C</italic></xref>. Simulated flood peaks for the three calibration events were within 23.2&#x00A0;percent, and the timing of the flood peaks was within 37&#x00A0;minutes of the observed peaks (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>).</p>
<table-wrap id="t03" position="float"><label>Table 3</label><caption>
<title>U.S. Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System calibration of selected high-flow events on April&#x00A0;28, 2024; May&#x00A0;2, 2024; and July&#x00A0;1, 2024.</title>
<p content-type="toc"><bold>Table 3.</bold>&#x2003;U.S. Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System calibration of selected high-flow events on April 28, 2024; May 2, 2024; and July 1, 2024.</p>
<p>[ft, foot; NAVD 88, North American Vertical Datum of 1988; CNIII, Soil Conservation Service runoff curve number representing a &#x201C;wet&#x201D; antecedent runoff condition; CNI, Soil Conservation Service runoff curve number representing a &#x201C;dry&#x201D; antecedent runoff condition; CNII, Soil Conservation Service runoff curve number representing a &#x201C;normal&#x201D; antecedent runoff condition]</p></caption>
<table rules="groups">
<col width="25.73%"/>
<col width="25.71%"/>
<col width="23.8%"/>
<col width="24.76%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water-level recording location (<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">Target water-surface elevation (ft above NAVD 88)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Simulated water-surface elevation (ft above NAVD 88)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Absolute difference in elevation (ft)</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="4" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;April 28, 2024<sup>a</sup>&#x2014;CNIII</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">EFLB1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">885.91</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">885.89</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.02</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB2</td>
<td valign="top" align="left">901.67</td>
<td valign="top" align="left">902.92</td>
<td valign="top" align="left">1.25</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB3</td>
<td valign="top" align="left">919.08</td>
<td valign="top" align="left">918.87</td>
<td valign="top" align="left">0.21</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Streamflow measurement location</td>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt">884.17</td>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt">884.22</td>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt">0.05</td>
</tr>
<tr>
<th colspan="4" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;May 2, 2024<sup>a</sup>&#x2014;CNI with no initial abstractions</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">EFLB1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">885.55</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">885.78</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.23</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB2</td>
<td valign="top" align="left">901.27</td>
<td valign="top" align="left">901.61</td>
<td valign="top" align="left">0.34</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB3</td>
<td valign="top" align="left">918.44</td>
<td valign="top" align="left">918.27</td>
<td valign="top" align="left">0.17</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Streamflow measurement location</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">883.74</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">888.80</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">0.06</td>
</tr>
<tr>
<th colspan="4" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;July 1, 2024&#x2014;CNII</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">EFLB1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">890.42</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">890.75</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.33</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB2</td>
<td valign="top" align="left">906.19</td>
<td valign="top" align="left">906.91</td>
<td valign="top" align="left">0.72</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">EFLB3</td>
<td valign="top" align="left">922.08</td>
<td valign="top" align="left">922.18</td>
<td valign="top" align="left">0.10</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Streamflow measurement location</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">888.73</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">888.67</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">0.06</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t03n1"><label><sup>a</sup></label>
<p>The April 28, 2024, and May&#x00A0;2, 2024, events were &#x201C;double peaked.&#x201D; The pressure transducer water-surface elevation value comparisons for the first peak are provided in this table.</p></fn>
</table-wrap-foot>
</table-wrap>
<table-wrap id="t04" position="float"><label>Table 4</label><caption>
<title>Simulated and observed hydrograph characteristics of the April&#x00A0;28, 2024; May&#x00A0;2, 2024; and July&#x00A0;1, 2024, high-flow events at reference point RF1 on the East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</title>
<p content-type="toc"><bold>Table 4.</bold>&#x2003;Simulated and observed hydrograph characteristics of the April 28, 2024; May 2, 2024; and July 1, 2024, high-flow events at reference point RF1 on the East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</p>
<p>[Dates are given in month/day/year format, and time is given in astronomical format; ft<sup>3</sup>/s, cubic foot per second]</p></caption>
<table rules="groups">
<col width="14.2%"/>
<col width="0.14%"/>
<col width="14.28%"/>
<col width="0.74%"/>
<col width="13.54%"/>
<col width="0.24%"/>
<col width="11.2%"/>
<col width="17.11%"/>
<col width="0.12%"/>
<col width="14.15%"/>
<col width="3.08%"/>
<col width="11.2%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="rowgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Storm event</td>
<td rowspan="2" valign="middle" colspan="3" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Target streamflow measurement (ft<sup>3</sup>/s)</td>
<td rowspan="2" valign="middle" colspan="2" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Simulated streamflow (ft<sup>3</sup>/s)</td>
<td rowspan="2" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Percentage difference</td>
<td valign="middle" colspan="5" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Date and time of peak at RF1</td>
</tr>
<tr>
<td valign="middle" colspan="2" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Simulated</td>
<td valign="middle" colspan="2" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Observed</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Difference<sup>a</sup></td>
</tr>
</thead>
<tbody>
<tr>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt" scope="row">April 28, 2024<sup>b</sup></td>
<td valign="top" align="left" style="border-top: solid 0.50pt">555.01</td>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt">450.35</td>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt">23.2</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">4/27/2024, 2123</td>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt">4/27/2024, 2200</td>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt">00:37:00</td>
</tr>
<tr>
<td colspan="2" valign="top" align="left" scope="row">May 2, 2024<sup>b</sup></td>
<td valign="top" align="left">262.56</td>
<td colspan="2" valign="top" align="left">248.35</td>
<td colspan="2" valign="top" align="left">5.7</td>
<td valign="top" align="left">5/2/2024, 0930</td>
<td colspan="2" valign="top" align="left">5/2/2024, 0948</td>
<td colspan="2" valign="top" align="left">00:18:00</td>
</tr>
<tr>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">July 1, 2024</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">2,497</td>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">2,312</td>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">8.0</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">7/1/2024, 1230</td>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">7/1/2024, 1218</td>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt">00:12:00</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t04n1"><label><sup>a</sup></label>
<p>Difference is given in hour:minute:second format.</p></fn>
<fn id="t04n2"><label><sup>b</sup></label>
<p>The April 28, 2024, and May 2, 2024, events were &#x201C;double peaked.&#x201D; The streamflow and time of peak value comparisons for the first peak are provided in this table.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>The Nash-Sutcliffe efficiency (NSE) coefficient (<xref ref-type="bibr" rid="r15">Nash and Sutcliffe, 1970</xref>) was used to assess model fit. Values of NSE can vary from negative infinity (&#x2212;&#x221E;) to 1. Values of 1 correspond to a perfect match between simulated and observed time series, whereas values less than 0 indicate the observed average is a better predictor than the simulated values. Because the model does not account for changing hydrologic response conditions during the event, even though the first peaks hit within calibration limits, later peaks had greater variability. Hydrographs for all the calibration events are shown in <xref ref-type="fig" rid="fig04">figure&#x00A0;4<italic>A</italic>&#x2013;<italic>C</italic></xref>, and time-of-peak comparisons for all events are listed in <xref ref-type="table" rid="t04">table&#x00A0;4</xref>. The NSE values of the calibrated models for the April&#x00A0;28, 2024; May&#x00A0;2, 2024; and July&#x00A0;1, 2024, storms were about 0.84, 0.81, and 0.94, respectively, indicating a good fit for all storms (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>). Overall, the results demonstrate that the model is capable of simulating accurate water levels throughout the reach at varying antecedent moisture conditions.</p>
<table-wrap id="t05" position="float"><label>Table 5</label><caption>
<title>Model performance metrics of the U.S.&#x00A0;Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System models developed for East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</title>
<p content-type="toc"><bold>Table 5.</bold>&#x2003;Model performance metrics of the U.S. Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System models developed for East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</p>
<p>[NSE, Nash-Sutcliffe model efficiency; CNIII, Soil Conservation Service runoff curve number representing a &#x201C;wet&#x201D; antecedent runoff condition; CNI, Soil Conservation Service runoff curve number representing a &#x201C;dry&#x201D; antecedent runoff condition; CNII, Soil Conservation Service runoff curve number representing a &#x201C;normal&#x201D; antecedent runoff condition]</p></caption>
<table rules="groups">
<col width="81.25%"/>
<col width="18.75%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Storm event</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">NSE</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">CNIII, April 28, 2024, calibration event</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.840</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">CNI, May 2, 2024, calibration event</td>
<td valign="top" align="left">0.806</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">CNII, July 1, 2024, calibration event</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">0.940</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Development of Water-Surface Profiles</title>
<p>All the probabilistic storm scenarios (<xref ref-type="table" rid="t02">table&#x00A0;2</xref>) were run using the model for &#x201C;dry,&#x201D; &#x201C;normal,&#x201D; and &#x201C;wet&#x201D; antecedent runoff conditions, and the peak water-surface elevations at the reference point RF1 were ranked in order from smallest to largest. A rating curve that was initially developed using the discrete streamflow measurements at the reference point RF1 was extended using the HEC&#x2013;RAS model results so that inundation maps could be produced and associated streamflows estimated for water-surface elevations that exceeded the maximum observed condition. A representative scenario was then selected for each 1-ft water-surface elevation interval between 884&#x00A0;ft at the reference point (corresponding to the approximate bankfull condition at EFLB1) and 897&#x00A0;ft above the North American Vertical Datum of 1988 (water level corresponding to the 1,000-year recurrence interval, 24-hour event with &#x201C;wet&#x201D; antecedent runoff conditions). This 14-ft range of water-surface elevations corresponds to the approximate bankfull condition at EFLB1, or 3&#x00A0;ft of depth at the reference point RF1, to 16&#x00A0;ft of depth at the reference point RF1 (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Inundation extents were then processed using Esri ArcGIS Pro (<xref ref-type="bibr" rid="r6">Esri, 2024</xref>) for these 14&#x00A0;selected scenarios. Each water-surface profile is intended to represent 1&#x00A0;ft of depth; specifically, the scenario representing a water-surface elevation of 886&#x00A0;ft is intended to represent the inundation extents for water-surface elevations ranging from 885.5 to 886.5&#x00A0;ft. The resulting flood-inundation maps indicate the maximum water-surface elevation attained at each location throughout the longitudinal reach for the corresponding precipitation magnitude and duration. A rating curve that was initially developed using the discrete streamflow measurements at the reference point RF1 was extended using the HEC&#x2013;RAS model results. Simulated results were used to determine approximate flows at the reference point RF1 for each of the water-surface elevations (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>).</p>
<table-wrap id="t06" position="float"><label>Table 6</label><caption>
<title>Selected scenarios used to represent flood-inundation water-surface elevations of 884 to 897&#x00A0;feet at the reference point RF1 at East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</title>
<p content-type="toc"><bold>Table 6.</bold>&#x2003;Selected scenarios used to represent flood-inundation water-surface elevations of 884 to 897 feet at the reference point RF1 at East Fork Little Blue River at Lee&#x2019;s Summit, Missouri.</p>
<p>[ft, foot; NAVD 88, North American Vertical Datum of 1988; ft<sup>3</sup>/s, cubic foot per second; yr, year; min, minute; CNII, Soil Conservation Service runoff curve number representing a &#x201C;normal&#x201D; antecedent runoff condition; hr, hour; CNIII, Soil Conservation Service runoff curve number representing a &#x201C;wet&#x201D; antecedent runoff condition]</p></caption>
<table rules="groups">
<col width="25.97%"/>
<col width="23.23%"/>
<col width="25.08%"/>
<col width="25.72%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Precipitation scenario (summary table)<sup>a</sup></td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Depth of water at RF1 (ft above NAVD 88)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water-surface elevation at RF1 (ft above NAVD 88)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Simulated peak streamflow (ft<sup>3</sup>/s)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">2 yr, 30 min&#x2014;CNII</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">3</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">884</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">350</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">1 yr, 4 hr&#x2014;CNII</td>
<td valign="middle" align="center">4</td>
<td valign="middle" align="center">885</td>
<td valign="middle" align="center">630</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10 yr, 1 hr&#x2014;CNII</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">886</td>
<td valign="top" align="center">950</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">10 yr, 3 hr&#x2014;CNII</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">887</td>
<td valign="top" align="center">1,460</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">25 yr, 2 hr&#x2014;CNII</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">888</td>
<td valign="top" align="center">1,840</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">25 yr, 6 hr&#x2014;CNII</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">889</td>
<td valign="top" align="center">2,750</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 3 hr&#x2014;CNII</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">890</td>
<td valign="top" align="center">3,710</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">200 yr, 3 hr&#x2014;CNII</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">891</td>
<td valign="top" align="center">4,600</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">200 yr, 6 hr&#x2014;CNII</td>
<td valign="top" align="center">11</td>
<td valign="top" align="center">892</td>
<td valign="top" align="center">5,780</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr&#x2014;CNII</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">893</td>
<td valign="top" align="center">6,510</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">200 yr, 24 hr&#x2014;CNII</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">894</td>
<td valign="top" align="center">7,500</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">500 yr, 24 hr&#x2014;CNII</td>
<td valign="top" align="center">14</td>
<td valign="top" align="center">895</td>
<td valign="top" align="center">9,700</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">1,000 yr, 24 hr&#x2014;CNII</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">896</td>
<td valign="top" align="center">11,300</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">1,000 yr, 24 hr&#x2014;CNIII</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">16</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">897</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">13,000</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t06n1"><label><sup>a</sup></label>
<p>Summary of simulated results for all scenarios in <xref ref-type="bibr" rid="r1">Atkinson (2026)</xref>.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>In addition to flood-inundation extents, depth grids, water-surface elevation grids, and velocities at key locations downstream from bridges and culverts were derived from the model. The depth grid maps indicate the approximate depth of water within the inundated area, and the water-surface elevation grids indicate the approximate water-surface elevation within the inundated area for each of the 14&#x00A0;selected scenarios. The depths and water-surface elevations are provided to the user as a range of 1&#x00A0;ft; for example, a calculated flood depth of 7.5&#x00A0;ft would be shown on the mapper as 7&#x2013;8&#x00A0;ft, and a calculated water-surface elevation of 941.45&#x00A0;ft would be shown on the mapper as 940.9&#x2013;941.9&#x00A0;ft. The depth grids and the water-surface elevation grids incorporate lowest adjacent grade data. The lowest adjacent grades are the bare-earth surfaces nearest the buildings (<xref ref-type="bibr" rid="r7">Federal Emergency Management Agency, 2020</xref>). When a building is within the inundation extent, the flood depth and water-surface elevations over the building area would be an estimate of the flood depth and water level inside the structure, excluding any implemented elevating or flood-proofing measures. Finally, velocities downstream from bridges and culverts were derived from the model for each of the 14&#x00A0;selected scenarios. Similar to the depth grids and water-surface elevation grids, velocities are shown to users as a range; for example, a calculated velocity of 4.4&#x00A0;feet per second would be shown as 4&#x2013;5&#x00A0;feet per second.</p>
</sec>
</sec>
<sec>
<title>Development of Flood-Inundation Maps</title>
<p>Flood-inundation maps were created for the East Fork Little Blue River study reach based on modeled peak water-surface elevations at the reference location RF1. The model was calibrated to the nearest 0.5&#x00A0;ft; therefore, the maps have an estimated vertical accuracy of plus or minus 1&#x00A0;ft. Estimated flood-inundation boundaries and depth grids for each simulated profile were developed with the HEC&#x2013;RAS mapper and exported from HEC&#x2013;RAS (<xref ref-type="bibr" rid="r1">Atkinson, 2026</xref>). Shapefile polygons, depth grid rasters, and water-surface elevation grid rasters of the inundated areas for each profile were modified as needed in ArcGIS Pro (ver.&#x00A0;3.3; <xref ref-type="bibr" rid="r6">Esri, 2024</xref>) to ensure a hydraulically reasonable transition of the flood boundaries along the length of the East Fork Little Blue River and tributaries.</p>
<p>Any inundated areas that were detached from the main channel were examined to determine if they were hydrologically connected with the main river, such as through culverts under roadways. Where such connections existed, the mapped inundated areas were retained in their respective flood maps; otherwise, the erroneously delineated parts of the flood extent were deleted. For this study, possible connections because of overflowing storm sewers were not included in the final inundation extents because the storm sewers were not included in the model. The flood-inundation areas were overlain on high-resolution, georeferenced, aerial photographs of the study area to aid in this decision making. Bridge surfaces are not shown as inundated until the lowest flood stage exceeds the elevation of the bridge deck, in which case, the bridge surface is depicted as being inundated. Estimates of water depth, depth of water above the lowest adjacent grade, water-surface elevations, and maximum velocities at selected road crossings can be obtained with the presentation of the flood-inundation maps on an interactive mapping application described in the &#x201C;<xref ref-type="sec" rid="sir20265017.Flood-InundationMapDelivery">Flood-Inundation Map Delivery</xref>&#x201D; section. The &#x201C;existing conditions&#x201D; scenario flood-inundation map corresponding to the highest simulated water-surface profile, a water-surface elevation of 897&#x00A0;ft, is shown in <xref ref-type="fig" rid="fig05">figure&#x00A0;5</xref>.</p>
<fig id="fig05" position="float" fig-type="figure"><label>Figure 5</label><caption><p>Flood-inundation map for the East Fork Little Blue River at Lee&#x2019;s Summit, Missouri, study reach corresponding to a water-surface elevation of 897&#x00A0;feet at the reference location.</p><p content-type="toc"><bold>Figure 5.</bold>&#x2003;Flood-inundation map for the East Fork Little Blue River at Lee&#x2019;s Summit, Missouri, study reach corresponding to a water-surface elevation of 897 feet at the reference location.</p></caption><long-desc>The inundation extents at the reference location are mostly along waterbodies.</long-desc><graphic xlink:href="rol25-0054_fig05"/></fig>
<p>Only the &#x201C;existing conditions&#x201D; scenario maps are shown on the interactive flood-inundation map application; projected climate-change scenarios are discussed in the &#x201C;<xref ref-type="sec" rid="sir20265017.Climate-ChangeScenarios">Climate-Change Scenarios</xref>&#x201D; section. The net differences in the resulting stages and corresponding flood-inundation maps for the various scenarios are provided in the &#x201C;East Fork Little Blue River_summary_tables&#x201D; file in <xref ref-type="bibr" rid="r1">Atkinson (2026)</xref>.</p>
<sec id="sir20265017.Climate-ChangeScenarios">
<title>Climate-Change Scenarios</title>
<p>The climate-change scenarios were developed using the Federal Highway Administration&#x2019;s CMIP Climate Data Processing Tool&#x00A0;2.1 (<xref ref-type="bibr" rid="r12">Kilgore and others, 2021</xref>). This online software tool was developed to &#x201C;take Localized Constructed Analogs (LOCA) downscaled CMIP5 data and process the information into statistical and other variables that can be used in planning and design with greater ease&#x201D; (<xref ref-type="bibr" rid="r12">Kilgore and others, 2021</xref>, p.&#x00A0;i). Using the CMIP tool, users can select a geographic area of interest, a period of interest, and an emissions condition, called the representative concentration pathway (RCP), to determine adjustment factors applied to &#x201C;existing conditions&#x201D; precipitation to obtain projected precipitation conditions.</p>
<p>The climate-change scenarios and CMIP tool were used to simulate the 100-year, 24-hour storm and the 100-year, 6-hour storm for all three antecedent moisture conditions. Projected precipitation amounts for varying future time and emission conditions were 4&#x2013;7&#x00A0;percent greater than existing conditions (<xref ref-type="table" rid="t07">table&#x00A0;7</xref>).</p>
<table-wrap id="t07" position="float"><label>Table 7</label><caption>
<title>Projected changes in precipitation based on the Federal Highway Administration&#x2019;s Coupled Model Intercomparison Project tool (<xref ref-type="bibr" rid="r12">Kilgore and others, 2021</xref>).</title>
<p content-type="toc"><bold>Table 7.</bold>&#x2003;Projected changes in precipitation based on the Federal Highway Administration&#x2019;s Coupled Model Intercomparison Project tool.</p>
<p>[yr, year; hr, hour; RCP, representative concentration pathway used to project future greenhouse gas concentration scenarios; RCP 4.5 30 yr, representative concentration pathway of 4.5 watts per square meter of radiative forcing and 30 years in future; RCP 4.5 50 yr, representative concentration pathway of 4.5 watts per square meter of radiative forcing and 50 years in the future; RCP 8.5 30 yr, representative concentration pathway of 8.5 watts per square meter of radiative forcing and 30 years in the future; RCP 8.5 50 yr, representative concentration pathway of 8.5 watts per square meter of radiative forcing and 50 years in the future]</p></caption>
<table rules="groups">
<col width="34.65%"/>
<col width="31.01%"/>
<col width="34.34%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Precipitation scenario</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Climate scenario</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Percentage increase in projected precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Base</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
<td valign="top" align="left">4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
<td valign="top" align="left">7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
<td valign="top" align="left">6</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 8.5 50 yr</td>
<td valign="top" align="left">7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
<td valign="top" align="left">0</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
<td valign="top" align="left">4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
<td valign="top" align="left">7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
<td valign="top" align="left">6</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">RCP 8.5 50 yr</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">7</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>After the scenarios were run, the modeled peak values at the reference point RF1 (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>) were recorded. Overall, the increase in water-surface elevation at RF1 because of the increased precipitation is less than 0.5&#x00A0;ft, although increases are greater for the 100-year, 24-hour scenarios than the 100-year, 6-hour scenarios (<xref ref-type="table" rid="t08">table&#x00A0;8</xref>). However, although increases are larger for the 100-year, 24-hour scenarios, the changes in flood-inundation extents are similar for each scenario (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6<italic>A</italic> and <italic>B</italic></xref>).</p>
<table-wrap id="t08" position="float"><label>Table 8</label><caption>
<title>Climate-change scenario comparison of percentage difference from base scenario and the magnitude of the increase or decrease from the base at the reference location.</title>
<p content-type="toc"><bold>Table 8.</bold>&#x2003;Climate-change scenario comparison of percentage difference from base scenario and the magnitude of the increase or decrease from the base at the reference location.</p>
<p>[CNII, Soil Conservation Service runoff curve number representing a &#x201C;normal&#x201D; antecedent runoff condition; ft, foot; yr, year; hr, hour; RCP, representative concentration pathway used to project future greenhouse gas concentration scenarios; RCP 4.5 30 yr, representative concentration pathway of 4.5 watts per square meter of radiative forcing and 30 years in future; RCP 4.5 50 yr, representative concentration pathway of 4.5 watts per square meter of radiative forcing and 50 years in the future; RCP 8.5 30 yr, representative concentration pathway of 8.5 watts per square meter of radiative forcing and 30 years in the future; RCP 8.5 50 yr, representative concentration pathway of 8.5 watts per square meter of radiative forcing and 50 years in the future]</p></caption>
<table rules="groups">
<col width="25.85%"/>
<col width="25.9%"/>
<col width="23.52%"/>
<col width="24.73%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Precipitation scenario</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Climate scenario&#x2014;CNII</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Peak water-surface elevation (ft)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Difference (ft)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Base</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">892.712</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
<td valign="top" align="left">893.059</td>
<td valign="top" align="left">0.347</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
<td valign="top" align="left">893.152</td>
<td valign="top" align="left">0.440</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
<td valign="top" align="left">893.140</td>
<td valign="top" align="left">0.428</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 24 hr</td>
<td valign="top" align="left">RCP 8.5 50 yr</td>
<td valign="top" align="left">893.178</td>
<td valign="top" align="left">0.466</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">Base</td>
<td valign="top" align="left">890.981</td>
<td valign="top" align="left">0</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 30 yr</td>
<td valign="top" align="left">891.159</td>
<td valign="top" align="left">0.178</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 4.5 50 yr</td>
<td valign="top" align="left">891.325</td>
<td valign="top" align="left">0.344</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left">RCP 8.5 30 yr</td>
<td valign="top" align="left">891.321</td>
<td valign="top" align="left">0.340</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">100 yr, 6 hr</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">RCP 8.5 50 yr</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">891.332</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">0.351</td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="fig06" position="float" fig-type="figure"><label>Figure 6</label><caption><p>Flood-inundation maps for the East Fork Little Blue River and tributaries at Lee&#x2019;s Summit, Missouri, study reach showing changes in flood-inundation extents based on selected climate-change scenarios. <italic>A</italic>,&#x00A0;24-hour storm projection; <italic>B</italic>,&#x00A0;6-hour storm projection. [50-year representative concentration pathway 8.5 refers to the representative concentration pathway (used to project future greenhouse gas concentration scenarios) of 8.5&#x00A0;watts per square meter and 50&#x00A0;years in the future]</p><p content-type="toc"><bold>Figure 6.</bold>&#x2003;Flood-inundation maps for the East Fork Little Blue River and tributaries at Lee&#x2019;s Summit, Missouri, study reach showing changes in flood-inundation extents based on selected climate-change scenarios.</p></caption><long-desc>The inundation extents are in the southern part of the map area for the 24-hour storm projection and in the northern part of the map area for the 6-hour storm projection.</long-desc><graphic xlink:href="rol25-0054_fig06a"/><graphic xlink:href="rol25-0054_fig06b"/></fig>
</sec>
<sec id="sir20265017.Flood-InundationMapDelivery">
<title>Flood-Inundation Map Delivery</title>
<p>The geospatial data files of developed flood-inundation polygons and corresponding depth grids, water-surface elevation rasters, depth of water above lowest adjacent grade, and velocity data are available in <xref ref-type="bibr" rid="r1">Atkinson (2026)</xref>. Additionally, a flood-inundation mapping interface (<xref ref-type="bibr" rid="r3">City of Lee&#x2019;s Summit, 2025</xref>) has been established to make the fully processed USGS flood-inundation study information available to the public. The website links to a mapping application that provides map libraries and detailed information on flood extents and depths for modeled sites.</p>
<p>Determining an appropriate flood-inundation map to reference for a particular event begins with monitoring rainfall. At the time of this report, the Lee&#x2019;s Summit mapping application, precipitation totals are gathered every 10&#x00A0;minutes from the NWS&#x2019;s ASOS network station at the Lee&#x2019;s Summit Municipal Airport. For the mapping application associated with this study, these data can be downloaded through Iowa State University&#x2019;s Environmental Mesonet (<xref ref-type="bibr" rid="r10">Iowa State University of Science and Technology, 2024a</xref>) and shown on a mapping application. Forecasted precipitation is based on the quantitative precipitation forecast for the area and is available from the NWS&#x2019;s text products (<xref ref-type="bibr" rid="r18">National Weather Service, 2025b</xref>).</p>
<p>The mapping application provides the opportunity to show current conditions or a user-specified rainfall. Based on the rainfall option chosen by the user or the recently downloaded current and forecasted precipitation, the hydrologic response of various precipitation events is used to determine the flood-inundation map shown to the user of the application. For example, if current conditions are showing a rainfall amount closely corresponding to 3.44&#x00A0;inches (in.) of rain falling in 2&#x00A0;hours, which is equivalent to the 25-year, 2-hour storm, then the mapping application would show the flood-inundation extents corresponding to the map related to the peak value produced for this particular storm at the reference point RF1 (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). Alternatively, the user can opt to choose a rainfall depth and time combination to view the resulting flood-inundation extents.</p>
<p>The response of the East Fork Little Blue River and tributaries to a rainstorm that is associated with a precipitation magnitude and duration and represented by the selected flood-inundation map will also vary depending on the selected antecedent runoff condition (&#x201C;dry,&#x201D; &#x201C;normal,&#x201D; or &#x201C;wet&#x201D;). In the mapping application, the antecedent runoff condition associated with the current condition is determined based on awareness of hydroclimatic conditions in the basin preceding an event. The current antecedent moisture conditions are based on the flash-flood guidance for a particular basin. The flash-flood guidance value for the basin is determined based on the soil moisture conditions before a storm event. The current value is downloaded from the NWS&#x2019;s application programming interface (<xref ref-type="bibr" rid="r17">National Weather Service, 2025a</xref>) and shown on the flood-inundation mapping application (<xref ref-type="bibr" rid="r3">City of Lee&#x2019;s Summit, 2025</xref>). Alternatively, users may manually select an antecedent moisture condition to pair with a manually selected rainfall amount and duration.</p>
<p>In calibrating the models for this study, the &#x201C;normal&#x201D; antecedent runoff condition was observed in the summer (July&#x00A0;1, 2024, event) with full vegetation cover with an antecedent 7-day rainfall of 2.87&#x00A0;in., mostly (2.72&#x00A0;in.) from one storm about 5&#x00A0;days before the July&#x00A0;1 event. The maximum daily air temperatures, in degrees Fahrenheit, were in the 80s and 90s for 4&#x00A0;weeks before the event. The &#x201C;wet&#x201D; condition calibration event was in April under growing vegetation with an antecedent 7-day rainfall of 1.62&#x00A0;in., mostly from a 1.46-in. event 2&#x00A0;days before April&#x00A0;28th. Maximum daily temperatures in the preceding month were mostly in the 50s, 60s, and low 70s, and a few days were in the 80s. &#x201C;Dry&#x201D; antecedent runoff conditions with no initial abstractions were observed for the May&#x00A0;2, 2024, event with still growing vegetation cover, and antecedent rainfall after the April&#x00A0;28 event was about 0.55&#x00A0;in. Maximum daily temperatures for these few days varied from the high 60s to mid-80s. Based on these conditions, the antecedent moisture conditions seem most affected by the rainfall and temperatures immediately before the calibration event. The application draws from the NWS&#x2019;s application programming interface to update the estimated antecedent moisture condition each hour (<xref ref-type="bibr" rid="r17">National Weather Service, 2025a</xref>).</p>
<p>The estimated flood-inundation maps are shown in sufficient detail so that preparations for flooding and decisions for emergency response could be completed efficiently. Depending on the flood magnitude, roadways are shown as shaded (inundated and likely impassable) or not shaded (dry and likely passable) to facilitate emergency planning and use. Bridges are shaded (that is, shown as inundated) when the flood stage exceeds the elevation of the bridge deck. A shaded building should not be interpreted to mean that the structure is completely submerged; rather, the lowest adjacent grade bare-earth surfaces near the building are inundated (<xref ref-type="bibr" rid="r7">Federal Emergency Management Agency, 2020</xref>). In these instances, the water depth near the building would be an estimate of the water level inside the structure, unless elevating or flood-proofing measures had been implemented. For this study of the East Fork Little Blue River and associated tributaries, the mapping application shows water-surface elevations and water depths. Additionally, the mapping application shows approximate velocities just downstream from selected bridge locations.</p>
</sec>
<sec>
<title>Disclaimer for Flood-Inundation Maps</title>
<p>The flood-inundation maps should not be used for navigation, regulatory, permitting, or other legal purposes. The USGS provides these maps &#x201C;as is&#x201D; for a quick reference, emergency planning tool but assumes no legal liability or responsibility resulting from the use of this information.</p>
</sec>
<sec>
<title>Uncertainties and Limitations Regarding Use of Flood-Inundation Maps</title>
<p>Although the flood-inundation maps represent the boundaries of inundation areas with a distinct line, some uncertainty is associated with these maps. The flood boundaries shown were estimated based on water stages at a selected reference location based on the hydrologic response from selected precipitation magnitudes and durations. Water-surface elevations along the stream reach were estimated by unsteady-state hydraulic modeling, assuming unobstructed flow, and used streamflows and hydrologic conditions anticipated at the East Fork Little Blue River main stem, tributary&#x00A0;A1, and tributary&#x00A0;A2. The rain-on-grid model reflects the land-cover characteristics and any bridge, culvert, dam, levee, or other hydraulic structures existing as of June&#x00A0;2023. Unique meteorological factors (timing and distribution of precipitation) may cause actual streamflows along the modeled reach to vary from those assumed during a flood, which may lead to deviations in the water-surface elevations and inundation boundaries shown. Additional areas may be flooded because of unanticipated conditions such as changes in the streambed elevation or roughness, backwater into major tributaries along a river main stem, or backwater from localized debris or ice jams. The accuracy of the flood water extent portrayed on these maps will vary with the accuracy of the DEM used to simulate the land surface. Of the 14&#x00A0;flood-inundation map scenarios, 8 exceed the largest streamflow measurement made at the East Fork Little Blue River reference location. This highest measurement corresponds to a water-surface elevation of 888.7&#x00A0;ft, which corresponds to the 889-ft stage map; therefore, additional uncertainty for flood-inundation maps exists at water-surface elevations greater than 889&#x00A0;ft.</p>
<p>The user should be aware of additional uncertainties that may be inherent or factored into the simulation of flood peaks using rainfall-runoff simulations. A rain-on-grid model was used to simulate flood peaks associated with various probabilistic precipitation amounts, and the precipitation was assumed to follow a defined temporal distribution over the duration of the event with an even spatial distribution over the basin. The actual temporal and spatial distribution of precipitation may vary, thereby affecting the timing and magnitude of the predicted flood peak in the main stem or one of the tributaries; thus, a single &#x201C;simple&#x201D; storm was simulated with a near-base-flow starting condition to develop the flood-inundation maps. For multiple compounding precipitation events, the user should take into consideration that the starting streamflow condition may be considerably higher than base flow used in the simulations, and therefore, the peak condition also will be higher than simulated conditions. Other sources of uncertainty will arise from the selection of the appropriate antecedent runoff condition and the occurrence of atypical precipitation events including rainfall on frozen ground or on a substantial existing snowpack, all of which may affect the timing and magnitude of the predicted flood peak.</p>
</sec>
<sec>
<title>Additional Components to the Flood-Inundation Map</title>
<p>For this project, the cooperator wanted to incorporate some additional components into the final flood-inundation map dashboard (<xref ref-type="bibr" rid="r3">City of Lee&#x2019;s Summit, 2025</xref>) beyond the standard inundation extents and water depths (<xref ref-type="bibr" rid="r28">U.S.&#x00A0;Geological Survey, 2018</xref>). These enhancements include indicating depth of inundation above the lowest adjacent grade of structures within the floodplain, indicating water-surface elevation in addition to water depth at a selected location, and indicating maximum water velocity at selected locations. For this project, the lowest adjacent grade, or bare-earth surfaces near a building (<xref ref-type="bibr" rid="r7">Federal Emergency Management Agency, 2020</xref>), values were used to indicate whether or not a particular structure is likely to be flooded.</p>
<p>The Cybersecurity &amp; Infrastructure Security Agency of the Federal Government defines several sectors of critical facilities (<xref ref-type="bibr" rid="r4">Cybersecurity &amp; Infrastructure Security Agency, 2025</xref>). For this project, critical infrastructure within the study basin was included in the flood-inundation mapping display. For the purpose of this study, critical infrastructure was defined as emergency services; water and wastewater treatment plants; healthcare facilities, including pharmacies; government facilities, including schools; and any chemical and manufacturing facilities. Several businesses and churches are also within the basin area, although most of the basin contains residential properties.</p>
</sec>
</sec>
</sec>
<sec>
<title>Summary</title>
<p>A library containing 14 digital flood-inundation maps was developed by the U.S.&#x00A0;Geological Survey, in cooperation with the City of Lee&#x2019;s Summit, Missouri, for a 2.95-mile reach of the East Fork Little Blue River and tributaries within the city. The maps were developed using input streamflows derived from precipitation values of 15-minute to 24-hour durations and ranging from 1- to 1,000-year recurrence intervals (100- to 0.1-percent annual exceedance probability) and the U.S.&#x00A0;Army Corps of Engineers Hydrologic Engineering Center&#x2013;River Analysis System (ver.&#x00A0;6.5). Water-surface profiles from the rain-on-grid two-dimensional unsteady-state model were used to estimate flood-inundation areas and depths of flooding. The hydraulic model was calibrated to continuous water-surface elevations recorded during the April&#x00A0;28, 2024; May&#x00A0;2, 2024; and July&#x00A0;1, 2024, high-flow events representing a range of antecedent runoff conditions and hydrologic responses and to discrete streamflow measurements from a reference location on the East Fork Little Blue River.</p>
<p>The hydrologic and hydraulic model encompassing the study reach was used to simulate runoff, route streamflows, and map the resulting 14&#x00A0;water-surface profiles for flood stages at 1-foot (ft) intervals referenced to the reference point and ranging from a water-surface elevation of 884&#x00A0;ft at the reference point, equating to bankfull at the EFLB1 pressure transducer location, to 897&#x00A0;ft. The 897-ft water-surface elevation corresponds to the estimated 0.1-percent annual exceedance probability (1,000-year recurrence interval) precipitation under &#x201C;wet&#x201D; antecedent conditions.</p>
<p>Within the HEC&#x2013;RAS model, 240&#x00A0;scenarios were developed from the design rainfall events with each of 3&#x00A0;antecedent conditions (&#x201C;dry,&#x201D; &#x201C;normal,&#x201D; or &#x201C;wet&#x201D;). Additional scenarios were created to simulate the effects of projected precipitation scenarios on the 100-year recurrence interval, 24-hour storm and the 100-year recurrence interval, 6-hour storm. The rainfall for these scenarios was modified based on the representative concentration pathways (RCPs) used to project future greenhouse gas concentration scenarios that apply rainfall modified based on projected precipitation conditions 30 and 50&#x00A0;years into the future: RCP&#x00A0;8.5 30-year (RCP of 8.5&#x00A0;watts per square meter [W/m<sup>2</sup>] and 30&#x00A0;years in the future), RCP&#x00A0;8.5 50-year (RCP of 8.5&#x00A0;W/m<sup>2</sup> and 50 years in the future), RCP&#x00A0;4.5 30-year (RCP of 4.5&#x00A0;W/m<sup>2</sup> and 30&#x00A0;years in the future), and RCP&#x00A0;4.5 50-year (RCP of 4.5&#x00A0;W/m<sup>2</sup> and 50&#x00A0;years in the future) scenarios. All simulation results were assigned to a flood-inundation map condition based on the generated peak flow and corresponding water-surface elevation at the East Fork Little Blue River reference location.</p>
<p>The simulated water-surface profiles were then combined with a geographic information system and a digital elevation model derived from light detection and ranging (also known as lidar) data to delineate estimated flood-inundation areas as shapefile polygons showing inundation extents, depth grids, water-surface elevations, velocities at selected locations, critical infrastructure locations, and lowest adjacent grades for each profile. These flood-inundation polygons were overlaid on high-resolution, georeferenced aerial photographs of the study area.</p>
<p>Interactive use of the maps on this mapping application can give users a general indication of the depth of water or the water-surface elevation at any point in the inundated area by using the mouse cursor to click within the shaded areas. The flood-inundation maps are tied to real-time precipitation data obtained from the Automated Surface Observing System weather station at the Lee&#x2019;s Summit Municipal Airport, accessible at <ext-link ext-link-type="uri" xlink:href="https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS">https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS</ext-link>. The joint products could help guide the public in taking individual safety precautions and provide emergency-management personnel with a tool to mitigate and prepare for flood-related emergencies, efficiently manage emergency flood operations, and effectively complete postflood recovery efforts.</p>
</sec>
</body>
</book-part>
</book-body>
<book-back>
<ref-list><title>References Cited</title>
<ref id="r1"><mixed-citation publication-type="data">Atkinson, A.A., 2026, Geospatial data and model archives associated with precipitation-driven flood-inundation mapping of the East Fork Little Blue River and associated tributaries at Lee&#x2019;s Summit, Missouri: U.S.&#x00A0;Geological Survey data release, <pub-id pub-id-type="doi">https://doi.org/10.5066/P13NSPHQ</pub-id>.</mixed-citation></ref>
<ref id="r2"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Chow</surname>, <given-names>V.T.</given-names></string-name>, <string-name><surname>Maidment</surname>, <given-names>D.R.</given-names></string-name>, and <string-name><surname>Mays</surname>, <given-names>L.W.</given-names></string-name></person-group>, <year>1988</year>, <source>Applied hydrology</source>: <publisher-loc>New York</publisher-loc>, <publisher-name>McGraw-Hill Book Company</publisher-name>, <size units="page">572</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r3"><mixed-citation publication-type="web">City of Lee&#x2019;s Summit, 2025, Flood-inundation mapping application for the East Fork Little Blue River: City of Lee&#x2019;s Summit website, accessed February&#x00A0;20, 2026, at <ext-link ext-link-type="uri" xlink:href="https://apps.usgs.gov/fim-lees-summit/">https://apps.usgs.gov/fim-lees-summit/</ext-link>.</mixed-citation></ref>
<ref id="r4"><mixed-citation publication-type="web">Cybersecurity &amp; Infrastructure Security Agency, 2025, Critical infrastructure sectors: Cybersecurity &amp; Infrastructure Security Agency website, accessed March&#x00A0;28, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.cisa.gov/topics/critical-infrastructure-security-and-resilience/critical-infrastructure-sectors">https://www.cisa.gov/topics/critical-infrastructure-security-and-resilience/critical-infrastructure-sectors</ext-link>.</mixed-citation></ref>
<ref id="r5"><mixed-citation publication-type="data">Dewitz, J., 2023, National Land Cover Database (NLCD) 2021&#x00A0;products: U.S.&#x00A0;Geological Survey data release, accessed November&#x00A0;5, 2023, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9JZ7AO3</pub-id>.</mixed-citation></ref>
<ref id="r6"><mixed-citation publication-type="web">Esri, 2024, ArcGIS Pro (ver. 3.3): Esri software release, accessed June&#x00A0;4, 2024, at <ext-link ext-link-type="uri" xlink:href="https://www.esri.com/en-us/arcgis/products/arcgis-pro/overview">https://www.esri.com/en-us/arcgis/products/arcgis-pro/overview</ext-link>.</mixed-citation></ref>
<ref id="r7"><mixed-citation publication-type="web">Federal Emergency Management Agency, 2020, Lowest adjacent grade: Federal Emergency Management Agency website, accessed March&#x00A0;28, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.fema.gov/about/glossary/lowest-adjacent-grade">https://www.fema.gov/about/glossary/lowest-adjacent-grade</ext-link>.</mixed-citation></ref>
<ref id="r8"><mixed-citation publication-type="web">Federal Emergency Management Agency, 2023, Flood insurance study, Jackson County, Missouri, and incorporated areas and Kansas City: Washington, D.C., Federal Emergency Management Agency, accessed on August&#x00A0;11, 2025, at <ext-link ext-link-type="uri" xlink:href="https://msc.fema.gov/portal/availabilitySearch?addcommunity=290173%26communityName=KANSAS%20CITY,%20CITY%20OF#searchresultsanchor">https://msc.fema.gov/portal/availabilitySearch?addcommunity=290173&amp;communityName=KANSAS%20CITY,%20CITY%20OF#searchresultsanchor</ext-link>.</mixed-citation></ref>
<ref id="r9"><mixed-citation publication-type="other">Heidemann, H.K., 2018, Lidar base specification (ver.&#x00A0;1.3, February&#x00A0;2018): U.S.&#x00A0;Geological Survey Techniques and Methods, book&#x00A0;11, chap.&#x00A0;B4, 101&#x00A0;p., accessed March&#x00A0;28, 2025, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm11B4</pub-id>.</mixed-citation></ref>
<ref id="r10"><mixed-citation publication-type="web">Iowa State University of Science and Technology, 2024a, ASOS network&#x2014;ASOS-AWOS-METAR data download: Iowa State University of Science and Technology digital data, accessed August&#x00A0;20, 2024, at <ext-link ext-link-type="uri" xlink:href="https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS">https://mesonet.agron.iastate.edu/request/download.phtml?network=MO_ASOS</ext-link>.</mixed-citation></ref>
<ref id="r11"><mixed-citation publication-type="web">Iowa State University of Science and Technology, 2024b, Iowa Environmental Mesonet&#x2014;GIS raster in ERDAS Imagine (.IMG) format: Iowa State University of Science and Technology digital data, accessed September&#x00A0;11, 2024, at <ext-link ext-link-type="uri" xlink:href="https://mesonet.agron.iastate.edu/rainfall/">https://mesonet.agron.iastate.edu/rainfall/</ext-link>.</mixed-citation></ref>
<ref id="r12"><mixed-citation publication-type="book">Kilgore, R., Bhat, C., Sharar-Salgado, D., and Kafalenos, R., 2021, Coupled Model Intercomparison Project (CMIP) Data Processing Tool&#x00A0;2.1&#x2014;User&#x2019;s guide: Washington, D.C., Federal Highway Administration report no.&#x00A0;FHWA&#x2013;HIF&#x2013;21&#x2013;016, 45&#x00A0;p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://rosap.ntl.bts.gov/view/dot/73035">https://rosap.ntl.bts.gov/view/dot/73035</ext-link>.]</mixed-citation></ref>
<ref id="r13"><mixed-citation publication-type="web">Miller, J.F., 1964, Two- to ten-day precipitation for return periods of 2 to 100&#x00A0;years in the contiguous United States: U.S.&#x00A0;Weather Bureau, Technical Paper no.&#x00A0;49, 29&#x00A0;p. [Also available at <ext-link ext-link-type="uri" xlink:href="https://www.weather.gov/media/owp/hdsc_documents/TechnicalPaper_No49.pdf">https://www.weather.gov/media/owp/hdsc_documents/TechnicalPaper_No49.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r14"><mixed-citation publication-type="web">Missouri Department of Transportation, 2024, Functional classification system, Lees Summit, Jackson County, Cass County, Missouri: Missouri Department of Transportation, 1&#x00A0;p., accessed February&#x00A0;7, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.modot.org/sites/default/files/documents/LeesSummit.pdf">https://www.modot.org/sites/default/files/documents/LeesSummit.pdf</ext-link>.</mixed-citation></ref>
<ref id="r15"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Nash</surname>, <given-names>J.E.</given-names></string-name>, and <string-name><surname>Sutcliffe</surname>, <given-names>J.V.</given-names></string-name></person-group>, <year>1970</year>, <article-title>River flow forecasting through conceptual models part 1&#x2014;A discussion of principles</article-title>: <source>Journal of Hydrology</source>, v.&#x00A0;<volume>10</volume>, no.&#x00A0;<issue>3</issue>, p.&#x00A0;<fpage>282</fpage>&#x2013;<lpage>290.</lpage> <comment>[Also available at </comment><pub-id pub-id-type="doi">https://doi.org/10.1016/0022-1694(70)90255-6</pub-id><comment>.]</comment></mixed-citation></ref>
<ref id="r16"><mixed-citation publication-type="web">National Oceanic and Atmospheric Administration, 2024, Precipitation frequency data server (PFDS): National Weather Service digital data, accessed September&#x00A0;11, 2024, at <ext-link ext-link-type="uri" xlink:href="https://hdsc.nws.noaa.gov/pfds/pfds_map_cont.html?bkmrk=mo">https://hdsc.nws.noaa.gov/pfds/pfds_map_cont.html?bkmrk=mo</ext-link>.</mixed-citation></ref>
<ref id="r17"><mixed-citation publication-type="web">National Weather Service, 2025a, API web service: National Weather Service website, accessed May&#x00A0;5, 2025, <ext-link ext-link-type="uri" xlink:href="https://www.weather.gov/documentation/services-web-api">https://www.weather.gov/documentation/services-web-api</ext-link>.</mixed-citation></ref>
<ref id="r18"><mixed-citation publication-type="web">National Weather Service, 2025b, National blend of models&#x2014;Text products: National Weather Service website, accessed September&#x00A0;27, 2024, at <ext-link ext-link-type="uri" xlink:href="https://www.weather.gov/mdl/nbm_text">https://www.weather.gov/mdl/nbm_text</ext-link>.</mixed-citation></ref>
<ref id="r19"><mixed-citation publication-type="web">National Weather Service, 2025c, National Weather Service home: National Weather Service website, accessed March&#x00A0;28, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.weather.gov">https://www.weather.gov</ext-link>.</mixed-citation></ref>
<ref id="r20"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>Natural Resources Conservation Service</collab></person-group>, <year>2004</year>, <source>Estimation of direct runoff from storm rainfall&#x2014;Part&#x00A0;630 hydrology&#x2014;National engineering handbook</source>: <publisher-loc>Washington, D.C.</publisher-loc>, <publisher-name>U.S.&#x00A0;Department of Agriculture</publisher-name>, <comment>[variously paged]. [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://www.hydrocad.net/neh/630contents.htm">https://www.hydrocad.net/neh/630contents.htm</ext-link><comment>.]</comment></mixed-citation></ref>
<ref id="r21"><mixed-citation publication-type="web">Natural Resources Conservation Service, 2022, Soil Survey Geographic database (SSURGO): Natural Resources Conservation Service database, accessed June&#x00A0;14, 2024, at <ext-link ext-link-type="uri" xlink:href="https://www.nrcs.usda.gov/resources/data-and-reports/soil-survey-geographic-database-ssurgo">https://www.nrcs.usda.gov/resources/data-and-reports/soil-survey-geographic-database-ssurgo</ext-link>.</mixed-citation></ref>
<ref id="r22"><mixed-citation publication-type="book">Rydlund, P.H., Jr., and Densmore, B.K., 2012, Methods of practice and guidelines for using survey-grade global navigation satellite systems (GNSS) to establish vertical datum in the United States Geological Survey: U.S.&#x00A0;Geological Survey Techniques and Methods, book&#x00A0;11, chap.&#x00A0;D1, 102&#x00A0;p. with appendixes. [Also available at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm11D1</pub-id>.]</mixed-citation></ref>
<ref id="r23"><mixed-citation publication-type="book">Soil Conservation Service, 1986, Urban hydrology for small watersheds: Washington, D.C., Soil Conservation Service report no.&#x00A0;TR&#x2013;55, [variously paged; 105&#x00A0;p.]. [Also available at <ext-link ext-link-type="uri" xlink:href="https://www.nrc.gov/docs/ML1421/ML14219A437.pdf">https://www.nrc.gov/docs/ML1421/ML14219A437.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r24"><mixed-citation publication-type="book">Turnipseed, D.P., and Sauer, V.B., 2010, Discharge measurements at gaging stations: U.S.&#x00A0;Geological Survey Techniques and Methods, book&#x00A0;3, chap.&#x00A0;A8, 87&#x00A0;p. [Also available at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm3A8</pub-id>.]</mixed-citation></ref>
<ref id="r25"><mixed-citation publication-type="web">U.S. Army Corps of Engineers, 2024, HEC&#x2013;RAS user&#x2019;s manual (ver.&#x00A0;6.5, February&#x00A0;2024): U.S.&#x00A0;Army Corps of Engineers website, accessed March&#x00A0;14, 2024, at <ext-link ext-link-type="uri" xlink:href="https://www.hec.usace.army.mil/confluence/rasdocs/rasum/6.5">https://www.hec.usace.army.mil/confluence/rasdocs/rasum/6.5</ext-link>.</mixed-citation></ref>
<ref id="r26"><mixed-citation publication-type="web">U.S. Army Corps of Engineers, 2025, HEC&#x2013;RAS 2D user&#x2019;s manual: U.S.&#x00A0;Army Corps of Engineers website, accessed March&#x00A0;14, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.hec.usace.army.mil/confluence/rasdocs/r2dum/latest">https://www.hec.usace.army.mil/confluence/rasdocs/r2dum/latest</ext-link>.</mixed-citation></ref>
<ref id="r27"><mixed-citation publication-type="web">U.S. Census Bureau, 2021, Decennial census [Lee&#x2019;s Summit city, Missouri]: U.S.&#x00A0;Census Bureau digital data, accessed March&#x00A0;28, 2025, at <ext-link ext-link-type="uri" xlink:href="https://data.census.gov/table/DECENNIALPL2020.P1?q=Lee%27s+Summit,+MO">https://data.census.gov/table/DECENNIALPL2020.P1?q=Lee%27s+Summit,+MO</ext-link>.</mixed-citation></ref>
<ref id="r28"><mixed-citation publication-type="web">U.S. Geological Survey, 2018, Flood Inundation Mapping (FIM) Program: U.S.&#x00A0;Geological Survey web page, accessed March&#x00A0;28, 2025, at <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/mission-areas/water-resources/science/flood-inundation-mapping-fim-program">https://www.usgs.gov/mission-areas/water-resources/science/flood-inundation-mapping-fim-program</ext-link>.</mixed-citation></ref>
<ref id="r29"><mixed-citation publication-type="web">U.S. Geological Survey, 2021a, 3DEP LidarExplorer: U.S.&#x00A0;Geological Survey digital data, accessed January&#x00A0;4, 2021, at <ext-link ext-link-type="uri" xlink:href="https://apps.nationalmap.gov/lidar-explorer/#/">https://apps.nationalmap.gov/lidar-explorer/#/</ext-link>.</mixed-citation></ref>
<ref id="r30"><mixed-citation publication-type="web">U.S. Geological Survey, 2021b, StreamStats, version&#x00A0;4.40, Missouri: U.S.&#x00A0;Geological Survey digital data, accessed June&#x00A0;2021 at <ext-link ext-link-type="uri" xlink:href="https://streamstats.usgs.gov/ss/">https://streamstats.usgs.gov/ss/</ext-link>.</mixed-citation></ref>
<ref id="r31"><mixed-citation publication-type="web">Weather Underground, 2025, WunderMap&#x2014;Interactive weather map and radar: Weather Underground digital data, accessed December&#x00A0;17, 2024, at <ext-link ext-link-type="uri" xlink:href="https://www.wunderground.com/wundermap">https://www.wunderground.com/wundermap</ext-link>.</mixed-citation></ref>
</ref-list>
<notes notes-type="colophon">
<sec>
<title>For more information about this publication, contact:</title>
<p>Director, USGS Central Midwest Water Science Center</p>
<p>1400 Independence Road</p>
<p>Rolla, MO 65401</p>
<p>573&#x2013;308&#x2013;3667</p>
<p>For additional information, visit: <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/centers/cm-water">https://www.usgs.gov/centers/cm-water</ext-link></p>
<p>Publishing support provided by the</p>
<p>USGS Science Publishing Network,</p>
<p>Rolla Publishing Service Center</p>
</sec></notes>
</book-back>
</book>
