<?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 Open-File Report</title>
<alt-title alt-title-type="pub-short-title">Open-File Report</alt-title>
<alt-title alt-title-type="pub-acronym-title">OFR</alt-title>
</title-group><contrib-group content-type="secretary-director"><contrib><string-name><given-names>DAVID</given-names><surname>BERNHARDT</surname></string-name><aff><institution>U.S. Department of the Interior</institution></aff><role>Secretary</role></contrib><contrib><string-name><given-names>James F.</given-names><surname>Reilly</surname><suffix>II</suffix></string-name><aff><institution>U.S. Geological Survey</institution></aff><role>Director</role></contrib></contrib-group><issn publication-format="print">0196-1497</issn><issn publication-format="online">2331-1258</issn></collection-meta>
<book-meta><book-id book-id-type="publisher-id">2021-1121</book-id><book-id book-id-type="doi">10.3133/ofr20211121</book-id><book-title-group>
<book-title>Evaluation of Two Existing Flood Management Structures in U.S. Army Garrison Fort Gordon, Georgia, 2020</book-title>
<alt-title alt-title-type="sentence-case">Evaluation of two existing flood management structures in U.S. Army Garrison Fort Gordon, Georgia, 2020</alt-title>
<alt-title alt-title-type="running-head">Evaluation of Two Existing Flood Management Structures in U.S. Army Garrison Fort Gordon, Georgia</alt-title>
</book-title-group><contrib-group content-type="collaborator">
<contrib>
<collab>Prepared in cooperation with the Environmental and Natural Resources Management Division of the U.S. Army Garrison Fort Gordon</collab>
</contrib>
</contrib-group><contrib-group content-type="authors">
<contrib contrib-type="author"><string-name><x>By</x><x> </x><given-names>Charles C.</given-names><x> </x><surname>Stillwell</surname></string-name></contrib>
</contrib-group><pub-date date-type="pub"><year>2021</year></pub-date><book-volume-number/><publisher>
<publisher-name>U.S. Geological Survey</publisher-name>
<publisher-loc>Reston, Virginia</publisher-loc>
</publisher><edition/><abstract>
<title>Abstract</title>
<p>Two existing flood management structures in U.S. Army Garrison Fort Gordon, Georgia, were evaluated for potential retrofitting to address water-quality impacts, pursuant of U.S. Army Garrison Fort Gordon&#x2019;s storm water management program. Stormwater calculations were computed according to the Georgia Stormwater Management Manual, including drainage area delineations, design-storm runoff volumes and peak discharges, stage-storage and stage-discharge curves, and outflow calculations. The results of these analyses were compared to Georgia&#x2019;s regulatory requirements for dry detention basins. The two existing flood management structures did not meet the requirements for a dry detention basin. Planning-level analyses for these basins indicate that the existing structures do not have adequate storage capacity for the overbank flood design-storm runoff volume (25-year, 24-hour storm) or the extreme flood design-storm runoff volume (100-year, 24-hour storm) and neither storm water structural control 2 nor storm water structural control 3 has the emergency spillway needed to safely convey overflows. Furthermore, land use changes (forest removal) and the risk for additional sediment loads to these structures may reduce available storage volume, increasing the risk for design failure. Three potential retrofit alternatives were provided for planning purposes only, with a brief discussion of advantages and disadvantages of each alternative retrofit strategy.</p>
</abstract><custom-meta-group>
<custom-meta><meta-name>Online Only</meta-name><meta-value>True</meta-value></custom-meta>
</custom-meta-group><notes notes-type="further-information"><p>For more information on the USGS&#x2014;the Federal source for science about the Earth, its natural and living resources, natural hazards, and the environment&#x2014;visit <ext-link>https://www.usgs.gov</ext-link> or call 1&#x2013;888&#x2013;ASK&#x2013;USGS.</p></notes><notes notes-type="overview"><p>For an overview of USGS information products, including maps, imagery, and publications, visit <ext-link>https://store.usgs.gov/</ext-link>.</p></notes><notes notes-type="disclaimer"><p>Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</p></notes><notes notes-type="permissions"><p>Although this information product, for the most part, is in the public domain, it also may contain copyrighted materials as noted in the text. Permission to reproduce copyrighted items must be secured from the copyright owner.</p></notes></book-meta>
<front-matter>
<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="41.88%"/>
<col width="13.69%"/>
<col width="44.43%"/>
<thead>
<tr>
<td valign="top" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Multiply</td>
<td valign="top" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">By</td>
<td valign="top" 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">&#x00A0;&#x00A0;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">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">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">0.3048</td>
<td valign="top" align="left">meter (m)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">mile (mi)</td>
<td valign="top" align="left">1.609</td>
<td valign="top" align="left">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">&#x00A0;&#x00A0;Area</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">acre</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">4,047</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">square meter (m<sup>2</sup>)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">acre</td>
<td valign="top" align="left">0.4047</td>
<td valign="top" align="left">hectare (ha)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">acre</td>
<td valign="top" align="left">0.004047</td>
<td valign="top" align="left">square kilometer (km<sup>2</sup>)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">square foot (ft<sup>2</sup>)</td>
<td valign="top" align="left">0.09290</td>
<td valign="top" align="left">square meter (m<sup>2</sup>)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">square mile (mi<sup>2</sup>)</td>
<td valign="top" align="left">259.0</td>
<td valign="top" align="left">hectare (ha)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">square mile (mi<sup>2</sup>)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">2.590</td>
<td valign="top" align="left" style="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">&#x00A0;&#x00A0;Volume</th>
</tr>
<tr>
<td valign="top" align="left" scope="row">cubic foot (ft<sup>3</sup>)</td>
<td valign="top" align="left">0.02832</td>
<td valign="top" align="left">cubic meter (m<sup>3</sup>)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;Discharge rate</th>
</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">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">Mass</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">ton, short (2,000 lb)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">0.9072</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">metric ton (t)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">ton, long (2,240 lb)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">1.016</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">metric ton (t)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Density</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">pound per cubic foot (lb/ft<sup>3</sup>)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">0.01602</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">gram per cubic centimeter (g/cm<sup>3</sup>)</td>
</tr>
</tbody></table></table-wrap>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Datum">
<book-part-meta>
<title-group>
<title>Datum</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>Vertical coordinate information is referenced to the North American Vertical Datum of 1988 (NAVD 88).</p>
<p>Horizontal coordinate information is referenced to the North American Datum of 1983 (NAD 83).</p>
<p>Elevation, as used in this report, refers to distance above the vertical datum.</p>
</named-book-part-body>
</front-matter-part>
<glossary content-type="Abbreviations">
<title>Abbreviations</title>
<def-list>
<def-item><term>BMP</term><def><p>best management practice</p></def></def-item>
<def-item><term>COVID&#x2013;19</term><def><p>coronavirus disease 2019</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>lidar</term><def><p>light detection and ranging</p></def></def-item>
<def-item><term>MS4</term><def><p>municipal separate storm sewer system</p></def></def-item>
<def-item><term>NRCS</term><def><p>Natural Resources Conservation Service</p></def></def-item>
<def-item><term>SWSC&#x2013;02</term><def><p>Storm water structural control 2</p></def></def-item>
<def-item><term>SWSC&#x2013;03</term><def><p>Storm water structural control 3</p></def></def-item>
<def-item><term>TR&#x2013;55</term><def><p>Technical Release 55</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>U.S. Army Garrison Fort Gordon, Georgia encompasses about 56,000&#x00A0;acres and supports a population of about 80,000&#x00A0;service members, families, contractors, and others (<xref ref-type="bibr" rid="r13">U.S. Army Garrison Fort Gordon, 2020</xref>). U.S. Army Garrison Fort Gordon&#x2019;s storm water management program is regulated through the National Pollution Discharge Elimination System municipal separate storm sewer system (MS4) permitting program. U.S. Army Garrison Fort Gordon&#x2019;s current storm water management plan defines six minimum control measures with each including multiple best management practices (BMPs) that outline specific actions to improve stormwater management (S. Scott, U.S. Army Garrison Fort Gordon, written commun., 2019). This study was designed to support U.S. Army Garrison Fort Gordon with assessing the effectiveness of two existing flood management structures (detention/retention ponds) for providing adequate runoff reduction and treatment.</p>
<p>In cooperation with the Environmental and Natural Resources Management Division of the U.S. Army Garrison Fort Gordon, the U.S. Geological Survey (USGS) South Atlantic Water Science Center evaluated the hydrologic, hydraulic, and water-quality design parameters for two existing dry detention basins. The two dry detention basins are storm water structural control 2 (SWSC&#x2013;02) and storm water structural control 3 (SWSC&#x2013;03), in the western part of U.S. Army Garrison Fort Gordon&#x2019;s municipal area in Richmond County (<xref ref-type="fig" rid="fig01">fig.&#x00A0;1</xref>). These dry detention basins discharge to unnamed tributaries to Spirit Creek (not shown), which is listed as impaired on Georgia&#x2019;s 2020 303(d) impaired waters list because of urban stormwater runoff (<xref ref-type="bibr" rid="r4">Georgia Department of Natural Resources Environmental Protection Division, 2020</xref>). SWSC&#x2013;02 and SWSC&#x2013;03 were constructed in 1999&#x2013;2000 before the latest edition of the Georgia Stormwater Management Manual (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). In this study, SWSC&#x2013;02 and SWSC&#x2013;03 were evaluated using methods and criteria from the 2016 edition of the Georgia Stormwater Management Manual (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>).</p>
<fig id="fig01" position="float" fig-type="figure"><label>Figure 1</label><caption><p>Location map showing flood management structures, storm water structural control 2 (SWSC&#x2013;02) and storm water structural control 3 (SWSC&#x2013;03), in U.S. Army Garrison Fort Gordon, Richmond County, Georgia.</p><p content-type="toc">Figure 1.&#x2003;Location map showing flood management structures, storm water structural control 2 (SWSC&#x2013;02) and storm water structural control 3 (SWSC&#x2013;03), in U.S. Army Garrison Fort Gordon, Richmond County, Georgia.</p></caption>
<long-desc>Map showing the study area, including topography, impervious areas, and flood management structures.</long-desc><graphic xlink:href="res21-0074_fig01"/></fig>
<p>This report presents the following: (1)&#x00A0;computed stormwater runoff characteristics for the existing dry detention basins, including stormwater runoff volumes, peak inflows and allowable outflow rates, and storage requirements for multiple design storms; (2)&#x00A0;comparison of the existing dry detention basins to the requirements from the 2016 edition of the Georgia Stormwater Management Manual (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>) to identify criteria compliance; and (3)&#x00A0;potential retrofit alternatives to update any noncompliant requirements per the 2016 edition of the Georgia Stormwater Management Manual (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). The retrofit alternatives examined by the USGS are provided only for preliminary planning-level estimates of the potential feasibility of retrofitting the existing facilities. Specific retrofits and designs that may be required by the U.S. Army Garrison Fort Gordon will need to be fully evaluated by a licensed engineer. This collaborative project aligns with the USGS water science strategy&#x2019;s core capabilities to partner with other Federal agencies, including the Department of Defense, to provide support for water resource issues such as flooding (<xref ref-type="bibr" rid="r3">Evenson and others, 2013</xref>).</p>
</sec>
<sec>
<title>Stormwater Calculations for Existing Flood Management Structures</title>
<p>Calculations described in this section are found in &#x201C;Section 3.1&#x2014;Methods for Estimating Stormwater Runoff&#x201D; of the Georgia Stormwater Management Manual Volume 2&#x2014;Technical Handbook (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). The use of the Georgia Stormwater Management Manual for this study was necessitated by local regulations and standards relevant to the U.S. Army Garrison Fort Gordon and does not imply endorsement by the U.S. Government.</p>
<sec>
<title>Justification for Remote Desktop Analyses</title>
<p>This project began in late 2019 and was initially expected to be completed by September 2020. However, the coronavirus disease 2019 (COVID&#x2013;19) was first detected in the United States in January 2020 and proceeded to spread across the Nation, causing shut-downs and halting work. As a result, the timeline and approach for this project were amended to accommodate national COVID&#x2013;19 safety protocols put forth by the Centers for Disease Control and Prevention. Therefore, flood management structures were evaluated remotely using existing geospatial datasets, which obviated the need for manual data collection tasks that would require USGS staff to enter the U.S. Army Garrison Fort Gordon.</p>
<p>The geospatial datasets used for the evaluation of the existing flood management structures are summarized in <xref ref-type="table" rid="t01">table&#x00A0;1</xref>. The datasets provided for use in this study by U.S. Army Garrison Fort Gordon have limited availability, contact the Environmental and Natural Resources Management Division of the U.S. Army Garrison Fort Gordon for further information. All geospatial analysis was completed using Esri ArcGIS Desktop 10.7.1. A 4-foot digital elevation model (DEM) developed from light detection and ranging (lidar) data collected in 2011 was used for drainage area and stage-storage analyses. The 2011 4-foot DEM was the most recent elevation data available in the study area with the required spatial resolution for the intended analyses. Calculations requiring the 2011 DEM did not represent 2020 elevations; however, changes to elevations between 2011 and 2020 because of sediment accumulation, erosion, or other potential sources are not expected to alter the outcomes of the evaluations of existing flood management projects.</p>
<table-wrap id="t01" position="float">
<label>Table 1</label><caption><title>Geospatial datasets used for this study.</title>
<p content-type="toc">Table 1.&#x2003;Geospatial datasets used for this study.</p>
<p>[lidar, light detection and ranging; DEM, digital elevation model; NAVD 88, North American Vertical Datum of 1988; MS4, municipal separate storm sewer system]</p>
</caption>
<table rules="groups">
<col width="26.94%"/>
<col width="42.3%"/>
<col width="30.76%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Dataset</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Description</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Source</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">2011 Georgia Lidar DEM: Burke Richmond Lincoln Columbia Counties</td>
<td valign="top" align="left" style="border-top: solid 0.50pt">Raster DEM, cell size 4&#x00A0;feet, vertical accuracy 2.36&#x00A0;inches, horizontal accuracy 48&#x00A0;inches, NAVD 88.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt"><xref ref-type="bibr" rid="r10">Office for Coastal Management, 2021</xref>.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">U.S. Army Garrison Fort Gordon impervious areas</td>
<td valign="top" align="left">Geodatabase of all impervious surfaces (buildings, parking areas, roadways, and sidewalks) as polygon features.</td>
<td valign="top" align="left">U.S. Army Garrison Fort Gordon.</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">U.S. Army Garrison Fort Gordon MS4</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Geodatabase of all MS4 components (inlets, ditches, pipes, culverts, nodes, and discharge points) as line and point features.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">U.S. Army Garrison Fort Gordon.</td>
</tr>
</tbody></table></table-wrap>
</sec>
<sec>
<title>Drainage Area Analysis</title>
<p>All geospatial data were projected to the North American Datum of 1983 (NAD&#x00A0;83) Universal Transverse Mercator zone 17 north coordinate system. The 2011 4-foot DEM was modified to ensure flow paths, drainage areas, and catchment areas conformed with existing stormwater infrastructure. In this section and subsequent sections, the phrase &#x201C;drainage area&#x201D; refers to the full area that drains to an existing stormwater management structure and the phrase &#x201C;catchment area&#x201D; refers to subunits within a drainage area.</p>
<p>First, the MS4 network was hydroenforced into the DEM by converting linear features (ditches and pipes) into rasters and subtracting 10&#x00A0;feet (an arbitrary value) from all DEM cells with overlapping MS4 features. This process allowed for subsurface features to be properly represented in subsequent flow direction and flow accumulation analyses to be completed for this study. Second, flow barriers also were hydroenforced into the DEM by adding 10&#x00A0;feet (an arbitrary value) to all DEM cells containing roof ridges or curbs to ensure proper delineation of catchment areas.</p>
<p>Once all MS4 features and flow barriers were represented in the modified DEM, drainage and catchment areas were delineated using the hydrology toolset within the spatial analyst toolbox. First, flow directions of each cell in the modified DEM were determined using the flow direction tool. Second, sinks (cells representing local minima without a downstream flow direction value) were identified using the sink tool and inspected for validity. Some sinks were appropriately identified, such as the existing flood management structures, but other sinks were not appropriately identified because of random variation in the DEM (from the raw lidar data used to create the 4-foot DEM). Next, the fill tool was used to fill in sinks; the Z-limit, or sink filling threshold, was iteratively modified to ensure that sinks from random variations in the DEM were filled while true sink features were maintained. Once all sinks from random variations in the DEM were filled, the flow direction tool was reapplied using the modified and filled DEM, followed by reapplication of the flow accumulation tool. The inflow and outflow locations for each flood management structure were selected as pour points using the snap pour point tool. Lastly, the watershed tool was used to delineate rasterized catchment areas for each pour point that were then converted to polygon features. A map showing the delineated catchment areas is shown in <xref ref-type="fig" rid="fig02">figure&#x00A0;2</xref>, and catchment area attributes are summarized in <xref ref-type="table" rid="t02">table&#x00A0;2</xref>.</p>
<table-wrap id="t02" position="float">
<label>Table 2</label><caption><title>Catchment area attributes.</title>
<p content-type="toc">Table 2.&#x2003;Catchment area attributes</p>
<p>[SWSC&#x2013;03, storm water structural control 3; %, percent; SWSC&#x2013;02, storm water structural control 2]</p>
</caption>
<table rules="groups">
<col width="42.43%"/>
<col width="21.21%"/>
<col width="36.36%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Catchment area name</td>
<td valign="middle" align="char" char="." scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;Size (acres)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Percent impervious</td>
</tr>
</thead>
<tbody>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">SWSC&#x2013;03</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;03 Inlet1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">18.55</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">85.0%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;03 Inlet2</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;3.95</td>
<td valign="top" align="center">46.6%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;03 Inlet3</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;4.51</td>
<td valign="top" align="center">80.9%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;03 Other</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;7.83</td>
<td valign="top" align="center">2.9%</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Total SWSC&#x2013;03 area</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;34.84<sup>a</sup></td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">61.7%<sup>b</sup></td>
</tr>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;SWSC&#x2013;02</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;02 Inlet1a</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;9.81</td>
<td valign="top" align="center" style="border-top: solid 0.50pt">73.5%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;02 Inlet1b</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;44.54</td>
<td valign="top" align="center">4.1%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;02 Inlet2</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;1.24</td>
<td valign="top" align="center">58.9%</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">SWSC&#x2013;02 Other</td>
<td valign="top" align="char" char=".">&#x00A0;&#x00A0;&#x00A0;3.57</td>
<td valign="top" align="center">7.8%</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Total SWSC&#x2013;02 area</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x00A0;&#x00A0;&#x00A0;59.16<sup>a</sup></td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">17.0%<sup>b</sup></td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t02n1"><label><sup>a</sup></label><p>Sum of individual catchment area sizes.</p></fn>
<fn id="t02n2"><label><sup>b</sup></label><p>Weighted average of catchment area percent impervious values.</p></fn></table-wrap-foot>
</table-wrap>
<fig id="fig02" position="float" fig-type="figure"><label>Figure 2</label><caption><p>Map showing delineated catchment areas. The &#x2018;SWSC&#x2013;02&#x2019; and &#x2018;SWSC&#x2013;03&#x2019; prefix indicates the larger drainage area in which the catchment is contained. Discharge from storm water structural control 3 (SWSC&#x2013;03) reenters the municipal separate storm sewer system (MS4) network and is conveyed to storm water structural control 2 (SWSC&#x2013;02). Discharge from SWSC&#x2013;02 is conveyed east to an unnamed tributary to Spirit Creek (not shown).</p><p content-type="toc"><bold>Figure 2.</bold>&#x2003; Map showing delineated catchment areas.</p></caption>
<long-desc>Map showing catchment areas and stormwater infrastructure (ditches, pipes, and inlets) within the study area.</long-desc><graphic xlink:href="res21-0074_fig02"/></fig>
<p>A review of historical satellite imagery indicated that the wooded tract in drainage area SWSC&#x2013;02 Inlet1b was cleared between 2018 and 2019. In theory, tree clearing may have caused changes to elevations and local drainage patterns. However, catchment area SWSC&#x2013;02 Inlet1b is bounded by roadways; therefore, the catchment area delineations likely represent current conditions. Tree clearing also is expected to change the rainfall-runoff response, most likely causing higher runoff volumes (<xref ref-type="bibr" rid="r11">Shepard, 1994</xref>; McBroom and others, 2008; <xref ref-type="bibr" rid="r2">Boggs and others, 2016</xref>). All subsequent runoff volume calculations computed for catchment area SWSC&#x2013;02 Inlet1b were based on deforested conditions.</p>
</sec>
<sec>
<title>Design-Storm Inflow Calculations</title>
<p>Runoff volumes and inflow hydrographs were calculated for the water-quality (1.2 inches), channel protection (1-year, 24-hour storm), overbank flood (25-year, 24-hour storm), and extreme flood (100-year, 24-hour storm) design storms (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Runoff volumes for each design storm were calculated for each catchment area and are summarized in <xref ref-type="table" rid="t03">table 3</xref>.</p>
<table-wrap id="t03" position="float">
<label>Table 3</label><caption><title>Runoff volumes from each catchment area for each design storm.</title>
<p content-type="toc">Table 3.&#x2003;Runoff volumes from each catchment area for each design storm.</p>
<p>[SWSC&#x2013;03, storm water structural control 3; SWSC&#x2013;02, storm water structural control 2]</p>
</caption>
<table rules="groups">
<col width="30.89%"/>
<col width="16.2%"/>
<col width="20.47%"/>
<col width="16.23%"/>
<col width="16.21%"/>
<thead>
<tr>
<td rowspan="3" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Catchment area name</td>
<td valign="middle" colspan="4" align="char" char="." scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Runoff volume (cubic feet)</td>
</tr>
<tr>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Design storm</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="char" char="." scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water quality</td>
<td valign="middle" align="char" char="." scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Channel protection<sup>1</sup></td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Overbank flood</td>
<td valign="middle" align="char" char="." scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Extreme flood</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;03 Inlet1</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">65,865</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">96,256</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">341,095</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">470,161</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;03 Inlet2</td>
<td valign="middle" align="char" char=".">8,074</td>
<td valign="middle" align="char" char=".">8,517</td>
<td valign="middle" align="char" char=".">44,442</td>
<td valign="middle" align="char" char=".">68,280</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;03 Inlet3</td>
<td valign="middle" align="char" char=".">15,292</td>
<td valign="middle" align="char" char=".">21,780</td>
<td valign="middle" align="char" char=".">79,283</td>
<td valign="middle" align="char" char=".">110,408</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">SWSC&#x2013;03 Other</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">2,607</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">2,195</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">35,528</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">67,023</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">Total SWSC&#x2013;03 area</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">91,838</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">128,748</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">500,348</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">715,872</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;02 Inlet1a</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">30,403</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">40,563</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">158,310</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt">224,748</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;02 Inlet1b</td>
<td valign="middle" align="char" char=".">16,836</td>
<td valign="middle" align="char" char=".">13,617</td>
<td valign="middle" align="char" char=".">208,955</td>
<td valign="middle" align="char" char=".">391,000</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;02 Inlet2</td>
<td valign="middle" align="char" char=".">3,132</td>
<td valign="middle" align="char" char=".">3,678</td>
<td valign="middle" align="char" char=".">16,637</td>
<td valign="middle" align="char" char=".">24,601</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">SWSC&#x2013;02 Other</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">1,875</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">1,534</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">18,582</td>
<td valign="middle" align="char" char="." style="border-bottom: solid 0.50pt">33,915</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="row">Total SWSC&#x2013;02 area</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">52,246</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">59,391</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">402,484</td>
<td valign="middle" align="char" char="." style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">674,265</td>
</tr>
</tbody></table>
<table-wrap-foot>
<fn id="t03n1"><label><sup>1</sup></label><p>Required storage volumes (from <xref ref-type="disp-formula" rid="e06">eqs.&#x00A0;6</xref>&#x2013;<xref ref-type="disp-formula" rid="e08">8</xref>) are listed for the channel protection design storm rather than runoff volumes (from <xref ref-type="disp-formula" rid="e03">eqs.&#x00A0;3</xref>&#x2013;<xref ref-type="disp-formula" rid="e05">5</xref>) (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>).</p></fn></table-wrap-foot>
</table-wrap>
<p>Runoff volumes for the water-quality design storm were calculated using <xref ref-type="disp-formula" rid="e01">equations 1</xref> and <xref ref-type="disp-formula" rid="e02">2</xref> as follows and as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>:<disp-formula id="e01">	<alternatives><mml:math id="m1">
 <mml:mrow>
  <mml:msub>
   <mml:mi>R</mml:mi>
   <mml:mi>v</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mn>0.05</mml:mn><mml:mo>+</mml:mo><mml:mn>0.009</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:mi>I</mml:mi><mml:mtext>&#x00A0;</mml:mtext></mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m01"/></alternatives><label>(1)</label></disp-formula>
<disp-formula id="e02">	<alternatives><mml:math id="m2">
 <mml:mrow>
  <mml:mi>W</mml:mi><mml:msub>
   <mml:mi>Q</mml:mi>
   <mml:mi>v</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mi>P</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:msub>
   <mml:mi>R</mml:mi>
   <mml:mi>v</mml:mi>
  </mml:msub>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m02"/></alternatives><label>(2)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>R<sub>v</sub></italic></term><def><p>is the runoff coefficient (unitless);</p></def></def-item>
<def-item><term><italic>I</italic></term><def><p>is the percent of impervious cover, in percent;</p></def></def-item>
<def-item><term><italic>WQ<sub>v</sub></italic></term><def><p>is the water-quality volume, in inches; and</p></def></def-item>
<def-item><term><italic>P</italic></term><def><p>is the precipitation depth, in inches.</p></def></def-item>
</def-list>
<p>The water-quality design-storm precipitation depth is the average 85th percentile annual rainfall depth across the State of Georgia, which is 1.2&#x00A0;inches (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>).</p>
<p>Runoff volumes for the channel protection, overbank flood, and extreme flood design storms were calculated using the Soil Conservation Service Natural Resources Conservation Service (NRCS) Technical Release (TR&#x2013;55) hydrologic method, as indicated in <xref ref-type="disp-formula" rid="e03">equations 3</xref>, <xref ref-type="disp-formula" rid="e04">4</xref>, and <xref ref-type="disp-formula" rid="e05">5</xref> as follows and as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>:<disp-formula id="e03">	<alternatives><mml:math id="m3">
 <mml:mrow>
  <mml:mi>Q</mml:mi><mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mfrac>
   <mml:mrow>
    <mml:msup>
     <mml:mrow>
      <mml:mfenced>
       <mml:mrow>
        <mml:mi>P</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mo>&#x2212;</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:msub>
         <mml:mi>I</mml:mi>
         <mml:mi>a</mml:mi>
        </mml:msub>
        </mml:mrow>
      </mml:mfenced></mml:mrow>
     <mml:mn>2</mml:mn>
    </mml:msup>
    </mml:mrow>
   <mml:mrow>
    <mml:mfenced>
     <mml:mrow>
      <mml:mi>P</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mo>&#x2212;</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:msub>
       <mml:mi>I</mml:mi>
       <mml:mi>a</mml:mi>
      </mml:msub>
      </mml:mrow>
    </mml:mfenced><mml:mo>+</mml:mo><mml:mi>S</mml:mi></mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m03"/></alternatives><label>(3)</label></disp-formula>
<disp-formula id="e04">	<alternatives><mml:math id="m4">
 <mml:mrow>
  <mml:msub>
   <mml:mi>I</mml:mi>
   <mml:mi>a</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mn>0.2</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:mi>S</mml:mi></mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m04"/></alternatives><label>(4)</label></disp-formula>
<disp-formula id="e05">	<alternatives><mml:math id="m5">
 <mml:mrow>
  <mml:mi>S</mml:mi><mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mfrac>
   <mml:mrow>
    <mml:mn>1000</mml:mn></mml:mrow>
   <mml:mrow>
    <mml:mi>C</mml:mi><mml:mi>N</mml:mi></mml:mrow>
  </mml:mfrac>
  <mml:mo>&#x2212;</mml:mo><mml:mn>10</mml:mn></mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m05"/></alternatives><label>(5)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>Q</italic></term><def><p>is the direct runoff depth, in inches;</p></def></def-item>
<def-item><term><italic>P</italic></term><def><p>is the precipitation depth, in inches;</p></def></def-item>
<def-item><term><italic>I<sub>a</sub></italic></term><def><p>is the initial abstraction, including surface storage, interception, evaporation, and infiltration before runoff, in inches;</p></def></def-item>
<def-item><term><italic>S</italic></term><def><p>is the potential maximum soil retention, in inches; and</p></def></def-item>
<def-item><term><italic>CN</italic></term><def><p>is the NRCS TR&#x2013;55 curve number (unitless).</p></def></def-item>
</def-list>
<p>Precipitation depth estimates for the channel protection design storm (3.18&#x00A0;inches, the 1-year, 24-hour storm), overbank flood design storm (6.15&#x00A0;inches, the 25-year, 24-hour storm), and extreme flood design storm (8.10&#x00A0;inches, the 100-year, 24-hour storm) were obtained for the study area from the Precipitation Frequency Data Server (<xref ref-type="bibr" rid="r8">National Weather Service, 2017</xref>). Per guidance from the Georgia Stormwater Management Manual, a composite NRCS TR&#x2013;55 curve number (CN) was determined for each catchment area (<xref ref-type="table" rid="t04">table&#x00A0;4</xref>) by computing the weighted average of impervious surfaces (CN=98) and pervious surfaces (CN=49, fair condition open space in hydrologic soil group A) as listed in table&#x00A0;3.1.5&#x2013;1 in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>.</p>
<table-wrap id="t04" position="float">
<label>Table 4</label><caption><title>Composite Natural Resources Conservation Service Technical Release 55 curve numbers for each catchment area.</title>
<p content-type="toc">Table 4.&#x2003;Composite Natural Resources Conservation Service Technical Release 55 curve numbers for each catchment area.</p>
<p>[SWSC&#x2013;03, storm water structural control 3; SWSC&#x2013;02, storm water structural control 2]</p>
</caption>
<table rules="groups">
<col width="58.7%"/>
<col width="41.3%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Catchment area name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Curve number</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;03 Inlet1</td>
<td valign="top" align="center" style="border-top: solid 0.50pt">91</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;03 Inlet2</td>
<td valign="top" align="center">72</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;03 Inlet3</td>
<td valign="top" align="center">89</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;03 Other</td>
<td valign="top" align="center">50</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;02 Inlet1a</td>
<td valign="top" align="center" style="border-top: solid 0.50pt">85</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;02 Inlet1b</td>
<td valign="top" align="center">51</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">SWSC&#x2013;02 Inlet2</td>
<td valign="top" align="center">78</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">SWSC&#x2013;02 Other</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">53</td>
</tr>
</tbody></table></table-wrap>
<p>For the channel protection design storm, additional steps were required to determine the required storage volume (which, for only the channel protection design storm and not the water-quality, overbank flood, or extreme flood design storms, does not equal the runoff volume; details in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission [2016]</xref>). First, the longest flow path in each catchment area was determined, and the traveltime along each flow path was estimated using <xref ref-type="disp-formula" rid="e06">equations 6</xref> and <xref ref-type="disp-formula" rid="e07">7</xref> as follows and as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>:<disp-formula id="e06">	<alternatives><mml:math id="m6">
 <mml:mrow>
  <mml:msub>
   <mml:mi>V</mml:mi>
   <mml:mrow>
    <mml:mi>p</mml:mi><mml:mi>a</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi></mml:mrow>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mn>20.33</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:msup>
   <mml:mi>s</mml:mi>
   <mml:mrow>
    <mml:mn>0.5</mml:mn></mml:mrow>
  </mml:msup>
  </mml:mrow>
</mml:math><inline-graphic xlink:href="res21-0074_m06"/></alternatives> or <alternatives><mml:math id="m7">
 <mml:mrow>
  <mml:msub>
   <mml:mi>V</mml:mi>
   <mml:mrow>
    <mml:mi>u</mml:mi><mml:mi>n</mml:mi><mml:mi>p</mml:mi><mml:mi>a</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi></mml:mrow>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mn>16.13</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:msup>
   <mml:mi>s</mml:mi>
   <mml:mrow>
    <mml:mn>0.5</mml:mn></mml:mrow>
  </mml:msup>
  </mml:mrow>
</mml:math><inline-graphic xlink:href="res21-0074_m07"/></alternatives><label>(6)</label></disp-formula>
<disp-formula id="e07">	<alternatives><mml:math id="m8">
 <mml:mrow>
  <mml:msub>
   <mml:mi>T</mml:mi>
   <mml:mi>t</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mfrac>
   <mml:mi>L</mml:mi>
   <mml:mrow>
    <mml:mn>3600</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:mi>V</mml:mi></mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m08"/></alternatives><label>(7)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>V<sub>paved</sub></italic></term><def><p>is the average velocity of shallow concentrated flow over paved surfaces, in feet per second;</p></def></def-item>
<def-item><term><italic>V<sub>unpaved</sub></italic></term><def><p>is the average velocity of shallow concentrated flow over unpaved surfaces, in feet per second;</p></def></def-item>
<def-item><term><italic>s</italic></term><def><p>is the average slope along the longest flow path, in feet per foot;</p></def></def-item>
<def-item><term><italic>T<sub>t</sub></italic></term><def><p>is the traveltime, in hours; and</p></def></def-item>
<def-item><term><italic>L</italic></term><def><p>is the length of the longest flow path, in feet.</p></def></def-item>
</def-list>
<p>Next, the unit peak discharge was estimated using figure&#x00A0;3.1.5&#x2013;6 <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref> using the traveltime from <xref ref-type="disp-formula" rid="e07">equation 7</xref>, the <italic>I<sub>a</sub></italic>/<italic>P</italic> as calculated from <xref ref-type="disp-formula" rid="e04">equation 4</xref>, and the channel protection design-storm depth (3.18&#x00A0;inches). The ratio of outflow to inflow was estimated using figure&#x00A0;3.3.5&#x2013;1 in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref> using an extended detention time of 24&#x00A0;hours (T=24) and the estimated unit peak discharges for each catchment area. The ratio of required storage volume to runoff volume was then calculated using <xref ref-type="disp-formula" rid="e08">equation&#x00A0;8</xref> as follows and as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>:<disp-formula id="e08">	<alternatives><mml:math id="m9">
 <mml:mrow>
  <mml:mfrac>
   <mml:mrow>
    <mml:msub>
     <mml:mi>V</mml:mi>
     <mml:mi>s</mml:mi>
    </mml:msub>
    </mml:mrow>
   <mml:mrow>
    <mml:msub>
     <mml:mi>V</mml:mi>
     <mml:mi>r</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  <mml:mo>=</mml:mo><mml:mn>0.682</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mn>1.43</mml:mn><mml:mfenced>
   <mml:mrow>
    <mml:mfrac>
     <mml:mrow>
      <mml:msub>
       <mml:mi>q</mml:mi>
       <mml:mi>o</mml:mi>
      </mml:msub>
      </mml:mrow>
     <mml:mrow>
      <mml:msub>
       <mml:mi>q</mml:mi>
       <mml:mi>i</mml:mi>
      </mml:msub>
      </mml:mrow>
    </mml:mfrac>
    </mml:mrow>
  </mml:mfenced><mml:mo>+</mml:mo><mml:mn>1.64</mml:mn><mml:msup>
   <mml:mrow>
    <mml:mfenced>
     <mml:mrow>
      <mml:mfrac>
       <mml:mrow>
        <mml:msub>
         <mml:mi>q</mml:mi>
         <mml:mi>o</mml:mi>
        </mml:msub>
        </mml:mrow>
       <mml:mrow>
        <mml:msub>
         <mml:mi>q</mml:mi>
         <mml:mi>i</mml:mi>
        </mml:msub>
        </mml:mrow>
      </mml:mfrac>
      </mml:mrow>
    </mml:mfenced></mml:mrow>
   <mml:mn>2</mml:mn>
  </mml:msup>
  <mml:mo>&#x2212;</mml:mo><mml:mn>0.804</mml:mn><mml:msup>
   <mml:mrow>
    <mml:mfenced>
     <mml:mrow>
      <mml:mfrac>
       <mml:mrow>
        <mml:msub>
         <mml:mi>q</mml:mi>
         <mml:mi>o</mml:mi>
        </mml:msub>
        </mml:mrow>
       <mml:mrow>
        <mml:msub>
         <mml:mi>q</mml:mi>
         <mml:mi>i</mml:mi>
        </mml:msub>
        </mml:mrow>
      </mml:mfrac>
      </mml:mrow>
    </mml:mfenced></mml:mrow>
   <mml:mn>3</mml:mn>
  </mml:msup>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m09"/></alternatives><label>(8)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><inline-formula><alternatives><mml:math id="m10">
 <mml:mrow>
  <mml:mfrac>
   <mml:mrow>
    <mml:msub>
     <mml:mi>V</mml:mi>
     <mml:mi>s</mml:mi>
    </mml:msub>
    </mml:mrow>
   <mml:mrow>
    <mml:mtext>&#x00A0;</mml:mtext><mml:msub>
     <mml:mi>V</mml:mi>
     <mml:mi>r</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><inline-graphic xlink:href="res21-0074_m10"/></alternatives></inline-formula></term><def><p>is the ratio of required storage volume to runoff volume (unitless); and</p></def></def-item>
<def-item><term><inline-formula><alternatives><mml:math id="m11">
 <mml:mrow>
  <mml:mfrac>
   <mml:mrow>
    <mml:msub>
     <mml:mi>q</mml:mi>
     <mml:mi>o</mml:mi>
    </mml:msub>
    </mml:mrow>
   <mml:mrow>
    <mml:mtext>&#x00A0;</mml:mtext><mml:msub>
     <mml:mi>q</mml:mi>
     <mml:mi>i</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><inline-graphic xlink:href="res21-0074_m11"/></alternatives></inline-formula></term><def><p>is the ratio of outflow to inflow (unitless).</p></def></def-item>
</def-list>
<p>The ratio of required storage volume to runoff volume was multiplied by the runoff volume from the channel protection design storm to determine the required storage volume.</p>
<p>Inflow hydrographs were developed for each design storm in each catchment area using the NRCS TR&#x2013;55 tabular hydrograph procedure, as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>. First, the traveltime for each catchment area was determined using <xref ref-type="disp-formula" rid="e06">equations&#x00A0;6</xref> and <xref ref-type="disp-formula" rid="e07">7</xref>. Then, the time to peak was calculated using <xref ref-type="disp-formula" rid="e09">equation&#x00A0;9</xref> as follows:<disp-formula id="e09">	<alternatives><mml:math id="m12">
 <mml:mrow>
  <mml:msub>
   <mml:mi>T</mml:mi>
   <mml:mi>p</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mn>0.025</mml:mn><mml:mo>+</mml:mo><mml:mn>0.6</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:msub>
   <mml:mi>T</mml:mi>
   <mml:mi>t</mml:mi>
  </mml:msub>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m12"/></alternatives><label>(9)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>T<sub>p</sub></italic></term><def><p>is the time to peak, in hours; and</p></def></def-item>
<def-item><term><italic>T<sub>t</sub></italic></term><def><p>is the traveltime, in hours.</p></def></def-item>
</def-list>
<p>If the computed time to peak for any catchment area was less than 0.1&#x00A0;hour (6 minutes), the time to peak was changed to equal 0.1 hour. Then, the peak discharge was determined using <xref ref-type="disp-formula" rid="e10">equation&#x00A0;10</xref> as follows:<disp-formula id="e10">	<alternatives><mml:math id="m13">
 <mml:mrow>
  <mml:msub>
   <mml:mi>q</mml:mi>
   <mml:mi>u</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mfrac>
   <mml:mrow>
    <mml:mi>P</mml:mi><mml:mi>F</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mi>A</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mi>Q</mml:mi></mml:mrow>
   <mml:mrow>
    <mml:msub>
     <mml:mi>T</mml:mi>
     <mml:mi>p</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m13"/></alternatives><label>(10)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>q<sub>u</sub></italic></term><def><p>is the unit hydrograph peak discharge, in cubic feet per second;</p></def></def-item>
<def-item><term><italic>PF</italic></term><def><p>is the peaking factor (unit-conversion factor);</p></def></def-item>
<def-item><term><italic>A</italic></term><def><p>is the catchment area, in square miles;</p></def></def-item>
<def-item><term><italic>Q</italic></term><def><p>is the runoff depth, in inches; and</p></def></def-item>
<def-item><term><italic>T<sub>p</sub></italic></term><def><p>is the time to peak, in hours.</p></def></def-item>
</def-list>
<p>Per guidance in the Georgia Stormwater Management Manual Volume 2, the default peaking factor for rolling hills (484) was used for <xref ref-type="disp-formula" rid="e10">equation&#x00A0;10</xref> (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Lastly, the incremental discharge rate was determined in 1-minute intervals by computing the ratio of incremental discharge to peak discharge using <xref ref-type="disp-formula" rid="e11">equation&#x00A0;11</xref> as follows:<disp-formula id="e11">	<alternatives><mml:math id="m14">
 <mml:mrow>
  <mml:mfrac>
   <mml:mi>q</mml:mi>
   <mml:mrow>
    <mml:msub>
     <mml:mi>q</mml:mi>
     <mml:mi>u</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  <mml:mo>=</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:msup>
   <mml:mrow>
    <mml:mfenced close="]" open="[">
     <mml:mrow>
      <mml:mfrac>
       <mml:mi>t</mml:mi>
       <mml:mrow>
        <mml:msub>
         <mml:mi>T</mml:mi>
         <mml:mi>p</mml:mi>
        </mml:msub>
        </mml:mrow>
      </mml:mfrac>
      <mml:mtext>&#x00A0;</mml:mtext><mml:msup>
       <mml:mi>e</mml:mi>
       <mml:mrow>
        <mml:mfenced>
         <mml:mrow>
          <mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mfrac>
           <mml:mi>t</mml:mi>
           <mml:mrow>
            <mml:msub>
             <mml:mi>T</mml:mi>
             <mml:mi>p</mml:mi>
            </mml:msub>
            </mml:mrow>
          </mml:mfrac>
          </mml:mrow>
        </mml:mfenced></mml:mrow>
      </mml:msup>
      </mml:mrow>
    </mml:mfenced></mml:mrow>
   <mml:mrow>
    <mml:mn>3.79</mml:mn></mml:mrow>
  </mml:msup>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m14"/></alternatives><label>(11)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><inline-formula><alternatives><mml:math id="m15">
 <mml:mrow>
  <mml:mfrac>
   <mml:mi>q</mml:mi>
   <mml:mrow>
    <mml:mtext>&#x00A0;</mml:mtext><mml:msub>
     <mml:mi>q</mml:mi>
     <mml:mi>u</mml:mi>
    </mml:msub>
    </mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><inline-graphic xlink:href="res21-0074_m15"/></alternatives></inline-formula></term><def><p>is the ratio of incremental discharge to peak discharge;</p></def></def-item>
<def-item><term><italic>t</italic></term><def><p>is the time, in hours; and</p></def></def-item>
<def-item><term><italic>T<sub>p</sub></italic></term><def><p>is the time to peak, in hours.</p></def></def-item>
</def-list>
<p>For each 1-minute increment, the ratio of incremental discharge to peak discharge was multiplied by the catchment area&#x2019;s peak discharge rate from <xref ref-type="disp-formula" rid="e10">equation&#x00A0;10</xref>. Inflow hydrographs were determined for each catchment area, and the total inflow hydrograph for each flood management structure was calculated as the sum of all the catchment area&#x2019;s individual inflow hydrographs (<xref ref-type="fig" rid="fig03">fig. 3</xref>).</p>
<fig id="fig03" position="float" fig-type="figure"><label>Figure 3</label><caption><p>Predevelopment and postdevelopment inflow hydrographs. <italic>A</italic>, storm water control structure 3 (SWSC&#x2013;03) and <italic>B</italic>, storm water structural control 2 (SWSC&#x2013;02).</p><p content-type="toc">Figure 3.&#x2003;Predevelopment and postdevelopment inflow hydrographs.</p></caption>
<long-desc>Design storm inflow hydrographs for each flood management structure</long-desc><graphic xlink:href="res21-0074_fig03"/></fig>
<p>The predevelopment hydrographs shown in <xref ref-type="fig" rid="fig03">figure 3</xref> were estimated by assuming all catchment areas represented fair condition open space land cover (CN=49, per table&#x00A0;3.1.5&#x2013;1 in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission [2016]</xref>). This predevelopment condition does not reflect pristine conditions (mature forests); instead, fair condition open space land cover was selected to acknowledge that the land had already been partially converted from mature forest before the construction of buildings, roads, and other impervious surfaces. Per guidance in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>, predevelopment hydrographs were generated only for the overbank flood and extreme flood design storms (<xref ref-type="fig" rid="fig03">fig. 3</xref>; the water-quality and channel protection design-storm evaluations are not dependent upon predevelopment conditions).</p>
</sec>
<sec>
<title>Stage-Storage Analysis</title>
<p>The storage capacity of each flood management structure was computed as a function of stage using the storage capacity tool within the spatial analyst supplemental toolbox. The storage capacity tool requires an elevation model as an input, with an optional polygon feature to identify a specific area, and outputs a tabular summary of storage volume and surface area at specified elevation intervals. Because the hydroenforced DEM that was used for watershed and catchment delineation had depressions smoothed and removed for routing purposes (by filling sinks), the original 2011 4-foot DEM was used to develop stage-storage relations. Elevation profiles also were drawn along the embankment of each flood management structure to identify the elevation at which the embankment would breach.</p>
<p>The elevations of key outlet structure features (for example, orifice invert and weir invert) could not be precisely determined because direct field measurements were not permissible under travel restrictions associated with the COVID&#x2013;19 pandemic during the study. Instead, a simple procedure was developed to estimate elevations of each outlet structure feature. The base of each outlet structure was assigned as the relative reference datum (stage equal to zero foot), and each outlet feature&#x2019;s height above the reference datum was measured by U.S. Army Garrison Fort Gordon personnel. Field observations and photographs were used to verify that the base of each outlet structure was about flush with the ground elevations. Because of the presence of depressions within the flood management structures, the base elevation of the outlet structure was not necessarily equal to the minimum elevation in the DEM. However, depressional areas were not determined to substantially change stage-storage relations. The stage-storage curves for each flood management structure are shown in <xref ref-type="fig" rid="fig04">figure&#x00A0;4</xref> and the elevations of key outlet structure features are shown in <xref ref-type="fig" rid="fig05">figure 5</xref>.</p>
<fig id="fig04" position="float" fig-type="figure"><label>Figure 4</label><caption><p>Stage-area and stage-storage curves for each flood management structure. <italic>A</italic>, storm water structural control 3 (SWSC&#x2013;03), and <italic>B</italic>, storm water structural control 2 (SWSC&#x2013;02).</p><p content-type="toc">Figure 4.&#x2003;Stage-area and stage-storage curves for each flood management structure.</p></caption>
<long-desc>Stage-storage curves for each flood management structure.</long-desc><graphic xlink:href="res21-0074_fig04"/></fig>
<fig id="fig05" position="float" fig-type="figure"><label>Figure 5</label><caption><p>Front-view schematic of the outlet structures. <italic>A</italic>, storm water structural control 3 (SWSC&#x2013;03) and <italic>B</italic>, storm water structural control 2 (SWSC&#x2013;02).</p><p content-type="toc">Figure 5.&#x2003;Front-view schematic of the outlet structures.</p></caption>
<long-desc>Front-view schematics of the outlet structures for each flood management structure.</long-desc><graphic xlink:href="res21-0074_fig05"/></fig>
<p>To comply with COVID&#x2013;19 safety protocols, the stage-storage analysis was completed remotely and was not supported with a field survey. One disadvantage of this approach was that key elevations could not be verified in the field. Although the procedure described in the previous paragraph provided reasonable estimates, the exact elevations could not be verified. A second disadvantage is the DEM represented 2011 conditions; therefore, elevations within the flood management structures could have changed, possibly from sediment accumulation or erosion.</p>
<p>A rough estimate of upland erosion from the drainage areas was calculated to gage the possibility of sediment infill reducing storage capacity within the flood management structures. Upland erosion rates from impervious surfaces and forests were assumed to be zero, whereas erosion rates from pervious open spaces (lawns in fair condition) were assumed to be 4.41&#x00A0;tons per acre per year, the average rate reported from the 2017 National Resources Inventory for cropland erosion in Georgia between 2012 and 2017 (<xref ref-type="bibr" rid="r14">U.S. Department of Agriculture, 2017</xref>). Cropland erosion rates generally are higher than erosion rates from unmanaged open space, so the estimates provided are regarded as being conservative. Erosion rates in tons per acre per year were converted to cubic feet using the soil&#x2019;s reported bulk density of 1.5&#x00A0;grams per cubic centimeter (<xref ref-type="bibr" rid="r9">Natural Resources Conservation Service, 2021</xref>) then compared to the total storage capacities of the flood management structures. From 2011 through 2020, the estimated sediment infill into SWSC&#x2013;03 was about 10,740&#x00A0;cubic feet, or 2.8&#x00A0;percent of the total storage capacity (see <xref ref-type="fig" rid="fig04">fig. 4</xref>). During the same time period, the estimated sediment infill into SWSC&#x2013;02 was about 16,030&#x00A0;cubic feet, or 6.6&#x00A0;percent of the total storage capacity. These infill estimates did not account for potential sediment resuspension and discharge from the flood management structures, which would reduce sediment accumulation, or tree clearing that occurred between 2018 and 2019 in the SWSC&#x2013;02 Inlet1b catchment area. Tree clearing can cause a substantial increase to soil erosion rates when erosion and sediment control measures are not used (<xref ref-type="bibr" rid="r11">Shepard, 1994</xref>; McBroom and others, 2008; <xref ref-type="bibr" rid="r2">Boggs and others, 2016</xref>). Because the tree-clearing efforts may have a substantial effect on runoff hydrology and sediment transport, the effects of these operations may be of substantial interest for the management and modification of these structures.</p>
</sec>
<sec>
<title>Design-Storm Outflow Calculations</title>
<p>The predevelopment inflow hydrographs from each design storm were used in conjunction with the stage-storage curves to simulate runoff accumulation within the flood management structures. Inflows, stage, and outflow were estimated in 1-minute time steps. Outflow was dependent upon the outlet structure dimensions (<xref ref-type="fig" rid="fig05">fig.&#x00A0;5</xref>) and stage (<xref ref-type="fig" rid="fig06">fig.&#x00A0;6</xref>). Readers should reference <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref> for equations to estimate discharge through orifices and weirs of various geometries. The outlet pipe configuration was used to estimate maximum discharge through the outlet structure using <xref ref-type="disp-formula" rid="e12">equations 12</xref> and <xref ref-type="disp-formula" rid="e13">13</xref> as follows and as described in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>:<disp-formula id="e12">	<alternatives><mml:math id="m16">
 <mml:mrow>
  <mml:msub>
   <mml:mi>Q</mml:mi>
   <mml:mrow>
    <mml:mi>m</mml:mi><mml:mi>a</mml:mi><mml:mi>x</mml:mi></mml:mrow>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mi>A</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:msup>
   <mml:mrow>
    <mml:mfenced>
     <mml:mrow>
      <mml:mfrac>
       <mml:mrow>
        <mml:mfenced close="]" open="[">
         <mml:mrow>
          <mml:mn>2</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:mi>g</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mi>H</mml:mi></mml:mrow>
        </mml:mfenced></mml:mrow>
       <mml:mrow>
        <mml:mfenced close="]" open="[">
         <mml:mrow>
          <mml:mn>1</mml:mn><mml:mo>+</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:msub>
           <mml:mi>k</mml:mi>
           <mml:mi>p</mml:mi>
          </mml:msub>
          <mml:mtext>&#x00A0;</mml:mtext><mml:mi>L</mml:mi></mml:mrow>
        </mml:mfenced></mml:mrow>
      </mml:mfrac>
      </mml:mrow>
    </mml:mfenced></mml:mrow>
   <mml:mrow>
    <mml:mn>0.5</mml:mn></mml:mrow>
  </mml:msup>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m16"/></alternatives><label>(12)</label></disp-formula>
<disp-formula id="e13">	<alternatives><mml:math id="m17">
 <mml:mrow>
  <mml:msub>
   <mml:mi>k</mml:mi>
   <mml:mi>p</mml:mi>
  </mml:msub>
  <mml:mo>=</mml:mo><mml:mfrac>
   <mml:mrow>
    <mml:mn>5087</mml:mn><mml:mtext>&#x00A0;</mml:mtext><mml:msup>
     <mml:mi>n</mml:mi>
     <mml:mn>2</mml:mn>
    </mml:msup>
    </mml:mrow>
   <mml:mrow>
    <mml:msup>
     <mml:mi>D</mml:mi>
     <mml:mrow>
      <mml:mfrac>
       <mml:mn>4</mml:mn>
       <mml:mn>3</mml:mn>
      </mml:mfrac>
      </mml:mrow>
    </mml:msup>
    </mml:mrow>
  </mml:mfrac>
  </mml:mrow>
</mml:math><graphic position="anchor" xlink:href="res21-0074_m17"/></alternatives><label>(13)</label></disp-formula>where</p>
<def-list list-type="equation-where">
<def-item><term><italic>Q<sub>max</sub></italic></term><def><p>is the maximum discharge from the outlet structure, in cubic feet per second;</p></def></def-item>
<def-item><term><italic>A</italic></term><def><p>is the cross sectional area of the outlet pipe, in square feet;</p></def></def-item>
<def-item><term><italic>g</italic></term><def><p>is the standard acceleration because of gravity, in feet per second squared;</p></def></def-item>
<def-item><term><italic>H</italic></term><def><p>is the height of water above the outlet pipe discharge point, in feet;</p></def></def-item>
<def-item><term><italic>k<sub>p</sub></italic></term><def><p>is the pipe friction coefficient (1 per foot);</p></def></def-item>
<def-item><term><italic>L</italic></term><def><p>is the length of the outlet pipe, in feet;</p></def></def-item>
<def-item><term><italic>5087</italic></term><def><p>is a coefficient derived from an empirical regression;</p></def></def-item>
<def-item><term><italic>n</italic></term><def><p>is the Manning&#x2019;s roughness coefficient (unitless); and</p></def></def-item>
<def-item><term><italic>D</italic></term><def><p>is the outlet pipe diameter, in inches.</p></def></def-item>
</def-list>
<fig id="fig06" position="float" fig-type="figure"><label>Figure 6</label><caption><p>Stage-discharge curves for each flood management structure. <italic>A</italic>, storm water structural control 3 (SWSC&#x2013;03) and <italic>B</italic>, storm water structural control 2 (SWSC&#x2013;02).</p><p content-type="toc">Figure 6.&#x2003; Stage-discharge curves for each flood management structure.</p></caption>
<long-desc>Stage-discharge curves for each flood management structure.</long-desc><graphic xlink:href="res21-0074_fig06"/></fig>
<p>The SWSC&#x2013;03 outlet pipe is a 175-foot, 18-inch diameter concrete pipe. The SWSC&#x2013;02 outlet pipe is a 70-foot, 36-inch diameter concrete pipe. The slopes of the outlet pipes were unknown and assumed to be 1-percent based on topography at the flood management structures. A sensitivity analysis was completed to test different outlet pipe slopes and results indicated that the maximum outlet discharge was not substantially affected by the slope of the outlet pipe. Outflows from SWSC&#x2013;03 were conveyed to SWSC&#x2013;02 via the MS4 network and were superimposed with the inflow runoff hydrographs from the SWSC&#x2013;02 catchment areas to create the inflow hydrographs for SWSC&#x2013;02 (see <xref ref-type="fig" rid="fig02">fig.&#x00A0;2</xref>).</p>
<p>If the modeled design storm stage breached the embankment, overflows were assumed to equal the inflow rate minus the discharge rate from the outlet structure; stage was assumed to remain constant at the breach elevation. Overflows from SWSC&#x2013;03 were assumed to discharge overland and into SWSC&#x2013;02 after about 9&#x00A0;minutes (based on <xref ref-type="disp-formula" rid="e07">eq.&#x00A0;7</xref>). Overflows from SWSC&#x2013;02 were assumed to breach the roadway to the east of SWSC&#x2013;02 and discharge offsite. The true timing and direction of overflows from these flood management structures is unknown and would require a process-based hydraulic model, which was outside the scope of this study.</p>
<p>The predevelopment inflow hydrograph, postdevelopment inflow hydrograph, and postdevelopment outflow hydrograph for each design storm are shown on <xref ref-type="fig" rid="fig07">figure&#x00A0;7</xref>. The drawdown times within the flood management structures for each design storm are listed in <xref ref-type="table" rid="t05">table&#x00A0;5</xref>. Drawdown times assume no clogging at the orifice structure and are dependent upon the inflow hydrograph for each design storm.</p>
<table-wrap id="t05" position="float">
<label>Table 5</label><caption><title>Drawdown times for each design storm.</title>
<p content-type="toc">Table 5.&#x2003;Drawdown times for each design storm.</p>
<p>[SWSC&#x2013;03, storm water structural control 3; SWSC&#x2013;02, storm water structural control 2]</p>
</caption>
<table rules="groups">
<col width="28.12%"/>
<col width="15.45%"/>
<col width="22.21%"/>
<col width="17.69%"/>
<col width="16.53%"/>
<thead>
<tr>
<td rowspan="3" valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Flood management structure</td>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Drawdown time (hours)</td>
</tr>
<tr>
<td valign="middle" colspan="4" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Design storm</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water quality</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Channel protection</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Overbank flood</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Extreme flood</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="middle" align="center" style="border-top: solid 0.50pt" scope="row">SWSC&#x2013;03</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">4.8</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">6.3</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">11.5</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">11.6</td>
</tr>
<tr>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt" scope="row">SWSC&#x2013;02</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">7.3</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">8.8</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">14.3</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">14.3</td>
</tr>
</tbody></table></table-wrap>
<fig id="fig07" position="float" fig-type="figure"><label>Figure 7</label><caption><p>Predevelopment inflow, postdevelopment inflow, and postdevelopment outflow. <italic>A</italic>, storm water structural control 3 (SWSC&#x2013;03) and <italic>B</italic>, storm water structural control 2 (SWSC&#x2013;02).</p><p content-type="toc">Figure 7.&#x2003; Hydrographs showing predevelopment inflow, postdevelopment inflow, and postdevelopment outflow.</p></caption>
<long-desc>Design storm inflow and outflow hydrographs for each flood management structure.</long-desc><graphic xlink:href="res21-0074_fig07"/></fig>
</sec>
</sec>
<sec>
<title>Comparison of Existing Flood Management Structures to Dry Detention Basin Design Criteria</title>
<p>The Georgia Stormwater Management Manual describes a dry detention basin as &#x201C;a surface storage basin or facility designed to provide water quality treatment and water quantity control through detention of stormwater runoff&#x201D; (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). A dry &#x201C;extended&#x201D; detention basin performs all the same functions as a standard dry detention basin with the additional provision of 24-hour detention of the channel protection volume. The flood management structures (SWSC&#x2013;03 and SWSC&#x2013;02) do not provide 24-hour detention of the channel protection volume (<xref ref-type="table" rid="t05">table&#x00A0;5</xref>), so the flood management structures will be compared to the design criteria for dry detention basins (not dry &#x201C;extended&#x201D; detention basins). Refer to <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref> for the full list of stormwater control measures. The design requirements and compliance for each existing flood management structure are summarized in <xref ref-type="table" rid="t06">table 6</xref>. <xref ref-type="table" rid="t06">Table&#x00A0;6</xref> also lists design &#x201C;requirements&#x201D; but does not include &#x201C;recommendations&#x201D;; full details of the design requirements, as well as recommendations, for dry detention basins are in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref>.</p>
<table-wrap id="t06" position="float">
<label>Table 6</label><caption><title>Summary of design compliance for each flood management structure.</title>
<p content-type="toc">Table 6.&#x2003;Summary of design compliance for each flood management structure.</p>
<p>[SWSC&#x2013;03, storm water structural control 3; SWSC&#x2013;02, storm water structural control 2; --, noncompliance; &#x2713;, compliance; ?, unknown compliance; NA, nonapplicable criterion]</p>
</caption>
<table rules="groups">
<col width="69.24%"/>
<col width="15.38%"/>
<col width="15.38%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Design criterion</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">SWSC&#x2013;03</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">SWSC&#x2013;02</td>
</tr>
</thead>
<tbody>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;Design-storm hydraulics</th>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">Storage of the water-quality runoff volume</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">--</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">--</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">Temporary storage of the overbank flood runoff volume</td>
<td valign="middle" align="center">--</td>
<td valign="middle" align="center">--</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">Control of the extreme flood runoff volume</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">--</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">--</td>
</tr>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;Basin geometry</th>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">Safe design of embankments (height, slope)</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">&#x2713;</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">&#x2713;</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">Depth of basin less than 10&#x00A0;feet</td>
<td valign="middle" align="center">&#x2713;</td>
<td valign="middle" align="center">&#x2713;</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">Grading within basin sloped towards outlet</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">&#x2713;</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">&#x2713;</td>
</tr>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;Inlet features</th>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">Stabilized inflow channels</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">&#x2713;</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">&#x2713;</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">Appropriately sized pretreatment device</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">--</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">--</td>
</tr>
<tr>
<th valign="middle" colspan="3" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">&#x00A0;&#x00A0;Outlet features</th>
</tr>
<tr>
<td valign="middle" align="left" style="border-top: solid 0.50pt" scope="row">Water-quality orifice designed to prevent clogging</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">--</td>
<td valign="middle" align="center" style="border-top: solid 0.50pt">--</td>
</tr>
<tr>
<td valign="middle" align="left" scope="row">Seepage control on all outlet pipes</td>
<td valign="middle" align="center">?</td>
<td valign="middle" align="center">?</td>
</tr>
<tr>
<td valign="middle" align="left" style="border-bottom: solid 0.50pt" scope="row">Outlet pipe erosion control</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">NA</td>
<td valign="middle" align="center" style="border-bottom: solid 0.50pt">?</td>
</tr>
</tbody></table></table-wrap>
<sec>
<title>Design-Storm Hydraulics</title>
<p>The following three hydraulic criteria are specified for an appropriately designed dry detention basin: (1)&#x00A0;storage of the water-quality volume, (2)&#x00A0;temporary storage of the overbank flood volume, and (3)&#x00A0;control of the extreme flood volume (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Neither SWSC&#x2013;03 or SWSC&#x2013;02 meet any of these three criteria. Per the Georgia Stormwater Management Manual, dry detention basins may provide partial water-quality treatment (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Storage of the water-quality volume, while only partially applicable for dry detention basins, is listed in <xref ref-type="table" rid="t06">table 6</xref> because the U.S. Army Garrison Fort Gordon storm water management plan aims to prevent or reduce pollutant runoff (S. Scott, U.S. Army Garrison Fort Gordon, written commun., 2019). Many other stormwater control measures are specifically designed to store and treat the water-quality volume.</p>
<p>Storage of the water-quality volume requires that the invert of the water-quality orifice is at the stage to store the water-quality volume. The water-quality orifices are at or near the bottom of the flood management structures (<xref ref-type="fig" rid="fig04">figs.&#x00A0;4</xref>&#x2013;<xref ref-type="fig" rid="fig05">5</xref>); therefore, less than the required storage capacity is being provided for the water-quality design storm.</p>
<p>Temporary storage of the overbank flood volume requires the postdevelopment peak discharge of the overbank flood design storm to be reduced to the predevelopment rate. The peak of the postdevelopment outflow is greater than the peak of the predevelopment runoff for SWSC&#x2013;03 and SWSC&#x2013;02 (<xref ref-type="fig" rid="fig07">fig.&#x00A0;7</xref>). Both exceedances occur during overflows (gray background), indicating that the flood management structures are undersized and cannot fully store the overbank flood volume.</p>
<p>Control of the extreme flood volume requires that the dry detention basin can store the extreme flood volume within structure and must include an emergency spillway designed to convey flood volumes above the extreme flood (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). The existing flood management structures do not have adequate storage capacity for the extreme flood volume. Further, neither SWSC&#x2013;03 nor SWSC&#x2013;02 includes an emergency spillway.</p>
</sec>
<sec>
<title>Basin Geometry</title>
<p>Three main geometric criteria are specified for an appropriately designed dry detention basin&#x2014;safe design of embankments, basin depth less than 10&#x00A0;feet, and grading within the basin sloped towards the outlet (for more details, see <xref ref-type="bibr" rid="r1">Atlanta Regional Commission [2016]</xref>). SWSC&#x2013;03 and SWSC&#x2013;02 meet each of these three criteria. Any retrofits or redesigns must ensure that the geometric criteria are maintained.</p>
</sec>
<sec>
<title>Inlet Features</title>
<p>Two inlet criteria are specified for an appropriately designed dry detention basin&#x2014;stabilized inflow channels and appropriately designed pretreatment devices (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). SWSC&#x2013;03 and SWSC&#x2013;02 meet the first criterion but neither SWSC&#x2013;03 nor SWSC&#x2013;02 contain a pretreatment device. The most common and recommended pretreatment device is a sediment forebay, sized to 0.1-inch runoff per impervious acre of contributing drainage area (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Alternative pretreatment devices include grass filter strips or grass channels.</p>
</sec>
<sec>
<title>Outlet Features</title>
<p>The following three outlet criteria are specified for an appropriately designed dry detention basin: (1)&#x00A0;water-quality orifice designed to prevent clogging, (2)&#x00A0;seepage control on outlet pipes, and (3)&#x00A0;erosion control on outlet pipes (for more details, see <xref ref-type="bibr" rid="r1">Atlanta Regional Commission [2016]</xref>). None of the outlet structures for SWSC&#x2013;03 or SWSC&#x2013;02 contain devices to prevent clogging of the water-quality orifice, such as an external trash rack or similar device. The presence of seepage control measures on outlet pipes is unknown. Outlet pipe erosion controls are applicable only for SWSC&#x2013;02 (because SWSC&#x2013;03 discharge reenters the pipe network and is conveyed to SWSC-02) and may include riprap, plunge pools or pads, or other energy dissipators placed at the outlet pipe discharge point. The presence of outlet pipe erosion controls for SWSC&#x2013;02 is unknown.</p>
</sec>
</sec>
<sec>
<title>Potential Retrofits to Existing Flood Management Structures</title>
<p>Potential retrofit alternatives are provided only for planning purposes. Specific retrofits and designs that may be required by the U.S. Army Garrison Fort Gordon will need to be fully evaluated by a licensed engineer. This section presents three retrofit alternatives for potential consideration as part of U.S. Army Garrison Fort Gordon&#x2019;s overall plans to evaluate and determine appropriate actions that may be needed to update or enhance the existing flood management structures. Potential advantages and disadvantages are provided for each alternative.</p>
<sec>
<title>Modify Existing Flood Management Structures to Meet Dry Detention Basin Design Criteria</title>
<p>The existing flood management structures can be modified to meet the dry detention basin criteria in <xref ref-type="bibr" rid="r1">Atlanta Regional Commission (2016)</xref> (<xref ref-type="table" rid="t06">table&#x00A0;6</xref>). Design changes may include, but are not limited to, the following: (1)&#x00A0;increasing the storage capacity of each flood management structure, (2)&#x00A0;redesigning both outlet structures, and (3)&#x00A0;adding pretreatment devices and emergency spillways. The flood management structures could be designed to store and release the extreme flood volume (and the volumes from smaller design storms). Depending on existing spatial constraints, the flood management structures might need to be deepened to account for additional storage requirements. The outlet structures could be redesigned in accordance with the water-quality orifice requirements, whereas outlet structures and pipes could be redesigned to allow controlled passage of the overbank flood and extreme flood design storms. Furthermore, pretreatment devices could be installed at all inlet features for each flood management structure, and emergency spillways could be designed to safely convey storm volumes that exceed the extreme flood.</p>
<p>One potential advantage of modifying the existing flood management structures to meet the dry detention basin design criteria is that it may be an efficient option to meet regulatory requirements considering that the existing flood management structures are most closely aligned with the Georgia Stormwater Management Manual definition of a dry detention basin. However, dry detention basins may not provide runoff reduction and may only provide partial water-quality treatment (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>).</p>
</sec>
<sec>
<title>Convert Existing Flood Management Structures to Alternative Stormwater Control Measures</title>
<p>Rather than modifying the existing flood management structures to meet the dry detention basin criteria, SWSC&#x2013;03 and SWSC&#x2013;02 could be converted into different stormwater control measures, such as &#x201C;extended&#x201D; dry detention basins, sand filters, stormwater ponds, or stormwater wetlands. A discussion of the advantages and disadvantages of each of the stormwater control measures was beyond the scope of this study (see <xref ref-type="bibr" rid="r1">Atlanta Regional Commission [2016]</xref>). Each of these stormwater control measures also have specific maintenance requirements intended to ensure proper hydraulic performance and water-quality treatment throughout time.</p>
<p>One advantage of this retrofit alternative is that further water-quality treatment may be provided as compared to standard dry detention basins. However, &#x201C;extended&#x201D; dry detention basins, sand filters, stormwater ponds, or stormwater wetlands will not reduce inflow runoff volumes. Other potential disadvantages of this retrofit alternative include, but are not limited to, design complexity and maintenance considerations.</p>
</sec>
<sec>
<title>Install Stormwater Control Measures Upstream of Existing Flood Management Structures</title>
<p>Instead of increasing the storage capacities of the existing flood management structures, the design-storm inflow volumes could be reduced by using upstream stormwater control measures. The use of stormwater control measures in series is called a &#x201C;treatment train&#x201D; (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). Some stormwater control measures are specifically designed to reduce runoff volumes&#x2014;bioretention basins, bioslopes, downspout disconnects, dry wells, enhanced dry swales, green roofs, infiltration trenches, permeable paver systems, pervious concrete, porous asphalt, rainwater harvesting, stormwater planters/tree boxes, and vegetated filter strips (<xref ref-type="bibr" rid="r1">Atlanta Regional Commission, 2016</xref>). A discussion of the advantages and disadvantages of each of these stormwater control measures was beyond the scope of this study, but these issues are documented in the literature (including, but not limited to, <xref ref-type="bibr" rid="r6">Leisenring and others, 2013</xref>; <xref ref-type="bibr" rid="r12">Taylor and others, 2014</xref>; and <xref ref-type="bibr" rid="r5">Granato and others, 2021</xref>). Generally, most stormwater control measures that are designed to reduce runoff volumes can be designed to fit within existing site constraints, but the cost and complexity of such designs will vary by selected stormwater control measure and site. Each of these stormwater control measures also have specific maintenance requirements intended to ensure proper hydraulic performance and water-quality treatment throughout time.</p>
<p>An advantage of this alternative is the potential for runoff reduction and water-quality treatment, none of which are fully realized when a dry detention basin is the only stormwater control measure installed at a site. Reducing runoff volumes from the upstream catchment areas may reduce, or potentially eliminate, the need to increase the storage capacities of the existing flood management structures to meet all required design criteria. Finally, volume control in the upstream drainage areas may reduce the risk that the dry ponds could fail from overtopping and threaten life or property downstream of the flood management structures. Potential disadvantages of this retrofit alternative include, but are not limited to, design complexity and maintenance considerations.</p>
</sec>
</sec>
<sec>
<title>Summary</title>
<p>Two existing flood management structures, storm water control structure 3 (SWSC&#x2013;03) and storm water control structure 2 (SWSC&#x2013;02), in U.S. Army Garrison Fort Gordon, Georgia, were evaluated for potential retrofitting to address water-quality impacts, pursuant of U.S. Army Garrison Fort Gordon&#x2019;s storm water management program. The evaluations were completed remotely using existing geospatial datasets to accommodate coronavirus disease 2019 (COVID&#x2013;19) safety protocols. Drainage areas were delineated for each existing flood management structure to calculate runoff volumes, peak discharges, and inflow hydrographs from four design storms&#x2014;the water-quality (1.2&#x00A0;inches), channel protection (1-year, 24-hour storm), overbank flood (25-year, 24-hour storm), and extreme flood (100-year, 24-hour storm) design storms. Stage-storage and stage-discharge curves were developed for each existing flood management structure and the inflow hydrographs of the four design storms were routed through the municipal separate storm sewer system (MS4) network to estimate outflow hydrographs.</p>
<p>The results of these analyses were compared to the regulatory requirements for dry detention basins. Neither SWSC&#x2013;03 nor SWSC&#x2013;02 met the requirement for a dry detention basin, and planning-level analyses for these basins indicated that the existing structures do not have adequate storage capacity for the overbank flood design-storm runoff volume (25-year, 24-hour storm) or the extreme flood design-storm runoff volume (100-year, 24-hour storm). Also, neither SWSC&#x2013;03 nor SWSC&#x2013;02 has the emergency spillway needed to properly handle an overflow event. Furthermore, land use changes (forest removal) and the risk for additional sediment loads to these structures may reduce available storage volume, increasing the risk for design failure.</p>
<p>Three potential retrofit alternatives were examined to provide preliminary information for planning purposes only and include: (1)&#x00A0;modify the existing flood management structures to comply with the design requirements for a dry detention basin, (2)&#x00A0;convert the existing flood management structures to alternative stormwater control measures, and (3)&#x00A0;install stormwater control measures upstream of the existing flood management structures. Potential advantages and disadvantages of each retrofit alternative were briefly discussed.</p>
</sec>
</body>
</book-part>
</book-body>
<book-back>
<ref-list>
<title>References Cited</title>
<ref id="r1"><mixed-citation publication-type="web">Atlanta Regional Commission, 2016, 2016 edition of the Georgia Stormwater Management Manual volumes 1 and 2: accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://atlantaregional.org/natural-r.esources/water/georgia-stormwater-management-manual/.">https://atlantaregional.org/natural-r.esources/water/georgia-stormwater-management-manual/.</ext-link></mixed-citation></ref>
<ref id="r2"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Boggs</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Sun</surname>, <given-names>G.</given-names></string-name>, and <string-name><surname>McNulty</surname>, <given-names>S.</given-names></string-name></person-group>, <year>2016</year>, <article-title>Effects of timber harvest on water quantity and quality in small watersheds in the Piedmont of North Carolina</article-title>: <source>Journal of Forestry</source>, v.&#x00A0;<volume>114</volume>, no.&#x00A0;<issue>1</issue>, p.&#x00A0;<fpage>27</fpage>&#x2013;<lpage>40</lpage>.<comment> [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5849/jof.14-102">https://doi.org/10.5849/jof.14-102</ext-link>.]</mixed-citation></ref>
<ref id="r3"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Evenson</surname>, <given-names>E.J.</given-names></string-name>, <string-name><surname>Orndorff</surname>, <given-names>R.C.</given-names></string-name>, <string-name><surname>Blome</surname>, <given-names>C.D.</given-names></string-name>, <string-name><surname>B&#x00F6;hlke</surname>, <given-names>J.K.</given-names></string-name>, <string-name><surname>Hershberger</surname>, <given-names>P.K.</given-names></string-name>, <string-name><surname>Langenheim</surname>, <given-names>V.E.</given-names></string-name>, <string-name><surname>McCabe</surname>, <given-names>G.J.</given-names></string-name>, <string-name><surname>Morlock</surname>, <given-names>S.E.</given-names></string-name>, <string-name><surname>Reeves</surname>, <given-names>H.W.</given-names></string-name>, <string-name><surname>Verdin</surname>, <given-names>J.P.</given-names></string-name>, <string-name><surname>Weyers</surname>, <given-names>H.W.</given-names></string-name>, and <string-name><surname>Wood</surname>, <given-names>T.M.</given-names></string-name></person-group>, <year>2013</year>, <source>U.S. Geological Survey water science strategy&#x2014;Observing, understanding, predicting, and delivering water science to the Nation</source>: <series>U.S. Geological Survey Circular</series> <volume>1383&#x2013;G</volume>, <size units="page">49</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/cir1383G">https://doi.org/10.3133/cir1383G</ext-link>.]</mixed-citation></ref>
<ref id="r4"><mixed-citation publication-type="web">Georgia Department of Natural Resources Environmental Protection Division, 2020, Water quality in Georgia 2018&#x2013;19&#x2014;Georgia 305b/303d Integrated Report)&#x2014;2020 list of waters: Georgia Environmental Protection Division website, accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="http://epd.georgia.gov/watershed-protection-branch/watershed-planning-and-monitoring-program/water-quality-georgia#toc-georgia-305-b-303-d-integrated-report.">http://epd.georgia.gov/watershed-protection-branch/watershed-planning-and-monitoring-program/water-quality-georgia#toc-georgia-305-b-303-d-integrated-report.</ext-link></mixed-citation></ref>
<ref id="r5"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Granato</surname>, <given-names>G.E.</given-names></string-name>, <string-name><surname>Spaetzel</surname>, <given-names>A.B.</given-names></string-name>, and <string-name><surname>Medalie</surname>, <given-names>L.</given-names></string-name></person-group>, <year>2021</year>, <source>Statistical methods for simulating structural stormwater runoff best management practices (BMPs) with the stochastic empirical dilution and loading model (SELDM)</source>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2020&#x2013;5136</volume>, <size units="page">41</size>&#x00A0;p. <comment>[Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/sir20205136">https://doi.org/10.3133/sir20205136</ext-link>.]</mixed-citation></ref>
<ref id="r6"><mixed-citation publication-type="web">Leisenring, M., Hobson, P., Clary, J., and Krall, J., 2013, International stormwater best management practices (BMP) database advanced analysis&#x2014;Influence of design parameters on achievable effluent concentrations: Geosyntec Consultants, Inc. and Wright Water Engineers, Inc., accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://bmpdatabase.org/performance-summary-reports.">https://bmpdatabase.org/performance-summary-reports.</ext-link></mixed-citation></ref>
<ref id="r7"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>McBroom</surname>, <given-names>M.W.</given-names></string-name>, <string-name><surname>Beasley</surname>, <given-names>R.S.</given-names></string-name>, <string-name><surname>Chang</surname>, <given-names>M.</given-names></string-name>, and <string-name><surname>Ice</surname>, <given-names>G.G.</given-names></string-name></person-group>, <year>2008</year>, <article-title>Storm runoff and sediment losses from forest clearcutting and stand re-establishment with best management practices in East Texas, USA</article-title>: <source>Hydrological Processes</source>, v.&#x00A0;<volume>22</volume>, no.&#x00A0;<issue>10</issue>, p.&#x00A0;<fpage>1509</fpage>&#x2013;<lpage>1522</lpage>.<comment> [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/hyp.6703">https://doi.org/10.1002/hyp.6703</ext-link>.]</mixed-citation></ref>
<ref id="r8"><mixed-citation publication-type="web">National Weather Service, 2017, Precipitation Frequency Data Server: National Oceanic and Atmospheric Administration, accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://hdsc.nws.noaa.gov/hdsc/pfds/.">https://hdsc.nws.noaa.gov/hdsc/pfds/.</ext-link></mixed-citation></ref>
<ref id="r9"><mixed-citation publication-type="web">Natural Resources Conservation Service, 2021, Web Soil Survey: U.S. Department of Agriculture, accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://websoilsurvey.sc.egov.usda.gov/.">https://websoilsurvey.sc.egov.usda.gov/.</ext-link></mixed-citation></ref>
<ref id="r10"><mixed-citation publication-type="web">Office for Coastal Management, 2021, 2011 Georgia Lidar DEM&#x2014;Burke Richmond Lincoln Columbia Counties from 2010&#x2013;06&#x2013;15 to 2010&#x2013;08&#x2013;15: National Oceanic and Atmospheric Administration National Centers for Environmental Information, accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://www.fisheries.noaa.gov/inport/item/48375.">https://www.fisheries.noaa.gov/inport/item/48375.</ext-link></mixed-citation></ref>
<ref id="r11"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Shepard</surname>, <given-names>J.P.</given-names></string-name></person-group>, <year>1994</year>, <article-title>Effects of forest management on surface water quality in wetland forests</article-title>: <source>Wetlands</source>, v.&#x00A0;<volume>14</volume>, no.&#x00A0;<issue>1</issue>, p.&#x00A0;<fpage>18</fpage>&#x2013;<lpage>26</lpage>.<comment> [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/BF03160618">https://doi.org/10.1007/BF03160618</ext-link>.]</mixed-citation></ref>
<ref id="r12"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Taylor</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Barrett</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Leisenring</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Sahu</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Pankani</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Poresky</surname>, <given-names>A.</given-names></string-name>, <string-name><surname>Questad</surname>, <given-names>A.</given-names></string-name>, <string-name><surname>Strecker</surname>, <given-names>E.</given-names></string-name>, <string-name><surname>Weinstein</surname>, <given-names>N.</given-names></string-name>, and <string-name><surname>Venner</surname>, <given-names>M.</given-names></string-name></person-group>, <year>2014</year>, <article-title>Long-term performance and life-cycle costs of stormwater best management practices</article-title>: <source>Transportation Research Board National Cooperative Highway Research Program Report</source>, v.&#x00A0;<volume>792</volume>, <elocation-id>148&#x00A0;p</elocation-id>.<comment> [Also available at </comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.17226/22275">https://doi.org/10.17226/22275</ext-link>.]</mixed-citation></ref>
<ref id="r13"><mixed-citation publication-type="web">U.S. Army Garrison Fort Gordon, 2020, Visitor and access Information: accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://home.army.mil/gordon/index.php/about/visitor-information.">https://home.army.mil/gordon/index.php/about/visitor-information.</ext-link></mixed-citation></ref>
<ref id="r14"><mixed-citation publication-type="web">U.S. Department of Agriculture, 2017, 2017 National resources inventory: accessed January 26, 2021, at <ext-link ext-link-type="uri" xlink:href="https://www.nrcs.usda.gov/Internet/NRCS_RCA/reports/nri_eros_ga.html">https://www.nrcs.usda.gov/Internet/NRCS_RCA/reports/nri_eros_ga.html</ext-link><ext-link ext-link-type="uri" xlink:href="http://.">.</ext-link></mixed-citation></ref>
</ref-list>
<notes notes-type="colophon">
<sec>
<title>For more information about this publication, contact</title>
<p>Director, South Atlantic Water Science Center</p>
<p>U.S. Geological Survey</p>
<p>1770 Corporate Drive</p>
<p>Suite 500</p>
<p>Norcross, GA 30093</p>
<p>Find additional information at</p>
<p><ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/water/southatlantic">https://www.usgs.gov/water/southatlantic</ext-link></p>
<p>Publishing support provided by</p>
<p>Reston and Rolla Publishing Science Center</p>
</sec>
</notes>
</book-back>
</book>
