<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book SYSTEM "BITS-book2.dtd">
<book xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" dtd-version="2.0" xml:lang="EN">
<collection-meta collection-type="series">
<title-group>
<title>U.S. Geological Survey Scientific Investigations Report</title>
<alt-title alt-title-type="pub-short-title">Scientific Investigations Report</alt-title>
<alt-title alt-title-type="pub-acronym-title">SIR</alt-title>
</title-group>
<contrib-group>
<contrib>
<aff><institution>U.S. Department of the Interior</institution></aff></contrib>
<contrib>
<aff><institution>U.S. Geological Survey</institution></aff></contrib>
</contrib-group><issn publication-format="print">2328-031X</issn><issn publication-format="online">2328-0328</issn>
</collection-meta>
<book-meta>
<book-id book-id-type="publisher-id">2026-5005</book-id>
<book-id book-id-type="doi">10.3133/sir20265005</book-id><book-title-group><book-title>Salinas Valley Integrated Hydrologic and Reservoir Operations Models, Monterey and San Luis Obispo Counties, California</book-title>
<alt-title alt-title-type="sentence-case">Salinas Valley integrated hydrologic and reservoir operations models, Monterey and San Luis Obispo Counties, California</alt-title>
<alt-title alt-title-type="running-head">Salinas Valley Integrated Hydrologic and Reservoir Operations Models, Monterey and San Luis Obispo Counties</alt-title></book-title-group>
<contrib-group content-type="collaborator">
<contrib><collab>Prepared in cooperation with Monterey County Resources Agency, Monterey County, and the Salinas Valley Basin Groundwater Sustainability Agency</collab></contrib>
</contrib-group>
<contrib-group content-type="authors">
<contrib contrib-type="author"><string-name><x>By</x><x> </x><given-names>Wesley R.</given-names><x> </x><surname>Henson</surname></string-name><x>, </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Randy</given-names><x> </x><surname>Hanson</surname></string-name><x>, </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Scott</given-names><x> </x><surname>Boyce</surname></string-name><x>, </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Joseph</given-names><x> </x><surname>Hevesi</surname></string-name><x>, </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Marisa M.</given-names><x> </x><surname>Earll</surname></string-name><x>, </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Deidre M.</given-names><x> </x><surname>Herbert</surname></string-name><x>, and </x></contrib>
<contrib contrib-type="author"><string-name><given-names>Elizabeth R.</given-names><x> </x><surname>Jachens</surname></string-name></contrib>
</contrib-group>
<pub-date date-type="pub">
<year>2026</year></pub-date><book-volume-number/>
<publisher>
<publisher-name>U.S. Geological Survey</publisher-name>
<publisher-loc>Reston, Virginia</publisher-loc>
</publisher>
<edition/>
<abstract>
<title>Abstract</title>
<p>The area surrounding the Salinas Valley groundwater basin in Monterey and San Luis Obispo Counties of California is a highly productive agricultural area, contributes substantially to the local economy, and provides a substantial portion of vegetables and other agricultural commodities to the Nation. This region of California provides about half of the Nation&#x2019;s lettuce, celery, broccoli, and spinach each year. Thus, this agricultural area provides substantial volumes of agricultural products not just for California but for the United States.</p>
<p>Changes in population and increased agricultural development, which includes a shift toward more water-intensive crops, and climate variability, have put increasing demand on both surface-water and groundwater resources in the valley. This situation has resulted in water management challenges in the Salinas Valley that generally relate to the distribution of the water supply throughout the basin. Where and when the water is present in the surface and subsurface does not coincide with where and when the water is needed. Historically, to deal with the distribution issue, water has been used conjunctively in the valley. Conjunctive use is a water management strategy that coordinates surface-water and groundwater use to maximize water availability. Groundwater is used throughout the Salinas Valley to meet water demands when surface-water supplies are insufficient. The availability of surface water is constrained by climate. Precipitation and streamflow vary seasonally and year to year. Although there are two reservoirs in the Salinas Valley to capture and store water during wet periods, the only conveyance of reservoir water to coastal agricultural areas is the Salinas River. Increasing demand for groundwater and surface-water resources throughout the Salinas Valley has resulted in undesirable effects from unsustainable water use, such as surface-water depletion, groundwater-level declines, storage depletion in the principal aquifers, and seawater intrusion. To address these escalating issues, local communities, water management agencies, and groundwater sustainability agencies are evaluating how to sustainably manage both their surface-water and groundwater resources. To meet water demands and reduce the undesirable effects of unsustainable water use, continued conjunctive management of surface water and groundwater would ideally incorporate strategies to deal with increases in demand and climate variability.</p>
<p>To evaluate the challenging water management issues in the Salinas Valley, the U.S. Geological Survey, Monterey County Water Resources Agency, and the Salinas Valley Basin Groundwater Sustainability Agency developed a comprehensive suite of models that represent the Salinas Valley hydrogeologic system called the Salinas Valley System Model. The geologic framework is known as the Salinas Valley Geologic Framework and was developed to characterize the subsurface using various topographic and geologic data sources, including information on hydrogeologic units, their surfaces and extents, geologic structures, lithology, and elevations from borehole data and cross sections, as well as details on faults and existing models. The surface-water model is called the Salinas Valley Watershed Model and simulates the Salinas River watershed. Monthly surface-water inflows into the integrated hydrologic model domain were simulated using the Salinas Valley Watershed Model. The historical model uses historical climate data, water and land use data, and reservoir releases to simulate agricultural operations, including landscape water demands, diversions, and reclaimed wastewater. The operational model adds an embedded reservoir operations framework to the simulation of the historical model that allows specified operational rules to simulate reservoir releases and changes in reservoir storage. The operational model assumes current reservoir operations and constant land use, which differs from historical conditions. Thus, the operational model is a hypothetical baseline model that can be used by local water managers to evaluate and quantify potential benefits of water supply projects. Together, the geologic framework, watershed, historical, and operational models form a tool that can be used to simulate irrigated agriculture and associated reservoir operations of the integrated hydrologic system of the Salinas Valley.</p></abstract>
<custom-meta-group>
<custom-meta><meta-name>Supersedes</meta-name><meta-value>preprint <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.31223/X5ZD9N">https://doi.org/10.31223/X5ZD9N</ext-link></meta-value></custom-meta>
<custom-meta><meta-name>Online Only</meta-name><meta-value>True</meta-value></custom-meta>
</custom-meta-group>
<notes notes-type="associated-data">
<p>Henson, W., Boyce, S.E., Franklin, H., Woodrow, A., Baillie, M., and Jachens, E.R., 2022, Salinas Valley operational model&#x2014;Input operational data (ver. 2.0, September 2023): U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9CWNHN3">https://doi.org/10.5066/P9CWNHN3</ext-link>.</p>
<p>Henson, W., and Culling, D.P., 2025, Salinas Valley Integrated Hydrologic and Reservoir Operations Model, Monterey and San Luis Obispo Counties, California: U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P13U6JPT">https://doi.org/10.5066/P13U6JPT</ext-link>.</p>
<p>Henson, W.R., Earll, M.M., Bond, S., Jachens, E.R., and Woodrow, A., 2023, Lower Salinas Valley hydrologic models&#x2014;Agricultural and municipal water supply and groundwater data (ver. 2.1, August 2024): U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9U67MIQ">https://doi.org/10.5066/P9U67MIQ</ext-link>.</p>
<p>Henson, W.R., Hevesi, J.A., Hanson, R.T., Bittner, D., Herbert, D.M., and Jachens, E.R., 2022, Salinas Valley hydrologic models&#x2014;Surface water data (ver.1.1, September 2024): U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P93COXL6">https://doi.org/10.5066/P93COXL6</ext-link>.</p>
<p>Henson, W.R., Hevesi, J.A., Hanson, R.T., Stern, M.A., and Jachens, E.R., 2022, Lower Salinas Valley hydrologic models&#x2014;Climate data (ver. 2.0, March 2025): U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9GTQCCF">https://doi.org/10.5066/P9GTQCCF</ext-link>.</p>
<p>Henson, W.R., and Jachens, E.R., 2022, Lower Salinas Valley hydrologic models&#x2014;Discretization data (ver. 1.2, August 2024): U.S. Geological Survey data release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9850MAK">https://doi.org/10.5066/P9850MAK</ext-link>.</p>
<p>Henson, W.R., and Voss, S.A., 2023, CalPUR-LUE, version 1.0: U.S. Geological Survey software release, <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5066/P9GUWKZZ">https://doi.org/10.5066/P9GUWKZZ</ext-link>.</p></notes>
<notes notes-type="further-information">
<p>For more information on the USGS&#x2014;the Federal source for science about the Earth, its natural and living resources, natural hazards, and the environment&#x2014;visit <ext-link>https://www.usgs.gov</ext-link>.</p></notes>
<notes notes-type="overview">
<p>For an overview of USGS information products, including maps, imagery, and publications, visit <ext-link>https://store.usgs.gov/</ext-link> or contact the store at 1&#x2013;888&#x2013;275&#x2013;8747.</p></notes>
<notes notes-type="disclaimer">
<p>Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</p></notes>
<notes notes-type="permissions">
<p>Although this information product, for the most part, is in the public domain, it also may contain copyrighted materials as noted in the text. Permission to reproduce <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/survey-manual/11006-use-copyrighted-material-usgs-information-products">copyrighted items</ext-link> must be secured from the copyright owner.</p></notes>
</book-meta>
<front-matter>
<front-matter-part>
<named-book-part-body>
<fig fig-type="cover"><caption><p><bold>Cover</bold>.&#x2003;Lettuce fields in Salinas Valley looking east. Photograph by Wesley Henson, U.S. Geological Survey, July 10, 2023.</p></caption></fig>
</named-book-part-body>
</front-matter-part>
<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="36.82%"/>
<col width="23.59%"/>
<col width="39.59%"/>
<thead>
<tr>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">Multiply</td>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">By</td>
<td valign="top" align="center" scope="col" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt">To obtain</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt" scope="col">Length</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.75pt; background-color:rgb(217,217,217)" scope="row">inch (in.)</td>
<td valign="top" align="char" char="." style="border-top: solid 0.75pt; background-color:rgb(217,217,217)">2.54</td>
<td valign="top" align="left" style="border-top: solid 0.75pt; background-color:rgb(217,217,217)">centimeter (cm)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">inch (in.)</td>
<td valign="top" align="char" char=".">25.4</td>
<td valign="top" align="left">millimeter (mm)</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">foot (ft)</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3048</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">meter (m)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">mile (mi)</td>
<td valign="top" align="char" char=".">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.75pt; border-bottom: solid 0.75pt" scope="col">Area</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.75pt; background-color:rgb(217,217,217)" scope="row">acre</td>
<td valign="top" align="char" char="." style="border-top: solid 0.75pt; background-color:rgb(217,217,217)">4,047</td>
<td valign="top" align="left" style="border-top: solid 0.75pt; background-color:rgb(217,217,217)">square meter (m<sup>2</sup>)</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">acre</td>
<td valign="top" align="char" char=".">0.4047</td>
<td valign="top" align="left">hectare (ha)</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">acre</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.004047</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">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="char" char=".">0.09290</td>
<td valign="top" align="left">square meter (m<sup>2</sup>)</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">square mile (mi<sup>2</sup>)</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">259.0</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">hectare (ha)</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.75pt" scope="row">square mile (mi<sup>2</sup>)</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.75pt">2.590</td>
<td valign="top" align="left" style="border-bottom: solid 0.75pt">square kilometer (km<sup>2</sup>)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt" scope="col">Flow rate</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">cubic foot per second (ft<sup>3</sup>/s)</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.02832</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">cubic meter per second (m<sup>3</sup>/s)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt" scope="col">Transmissivity</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)" scope="row">foot squared per day (ft<sup>2</sup>/d)</td>
<td valign="top" align="char" char="." style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)">0.09290</td>
<td valign="top" align="left" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)">meter squared per day (m<sup>2</sup>/d)</td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(255,255,255)" scope="col">Hydraulic conductivity</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)" scope="row">foot per day (ft/d)</td>
<td valign="top" align="char" char="." style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)">0.3048</td>
<td valign="top" align="left" style="border-top: solid 0.75pt; border-bottom: solid 0.75pt; background-color:rgb(217,217,217)">meter per day (m/d)</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Temperature in degrees Celsius (&#x00B0;C) may be converted to degrees Fahrenheit (&#x00B0;F) as follows:</p>
<p>&#x00B0;F = (1.8 &#x00D7; &#x00B0;C) + 32.</p>
<p>Temperature in degrees Fahrenheit (&#x00B0;F) may be converted to degrees Celsius (&#x00B0;C) as follows:</p>
<p>&#x00B0;C = (&#x00B0;F &#x2212; 32) / 1.8.</p>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Datums">
<book-part-meta>
<title-group>
<title>Datums</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>Horizontal coordinate information is referenced to the North American Datum of 1983 (NAD 83).</p>
<p>Vertical coordinate information is referenced to the North American Vertical Datum of 1988 (NAVD 88).</p>
</named-book-part-body>
</front-matter-part>
<front-matter-part book-part-type="Supplemental-Information">
<book-part-meta>
<title-group>
<title>Supplemental Information</title>
</title-group>
</book-part-meta>
<named-book-part-body>
<p>A water year is the 12-month period from October 1 through September 30 and is designated by the calendar year in which it ends. Concentrations of chemical constituents in water are in milligrams per liter (mg/L).</p>
</named-book-part-body>
</front-matter-part>
<glossary content-type="Abbreviations"><title>Abbreviations</title>
<def-list><def-item><term>Afyf</term>
<def>
<p>acre-feet per year per foot</p></def></def-item><def-item><term>CalPUR</term>
<def>
<p>California Pesticide Use Reporting</p></def></def-item><def-item><term>CIMIS</term>
<def>
<p>California Irrigation Management Information System 	</p></def></def-item><def-item><term>COOP</term>
<def>
<p>Cooperative Observer Network</p></def></def-item><def-item><term>CSIP</term>
<def>
<p>Castroville Seawater Intrusion Project</p></def></def-item><def-item><term>DEM</term>
<def>
<p>digital elevation model</p></def></def-item><def-item><term>DRT </term>
<def>
<p>Drain Return Flow package</p></def></def-item><def-item><term>ETref</term>
<def>
<p>reference evapotranspiration</p></def></def-item><def-item><term>FEI</term>
<def>
<p>fraction of evaporation from irrigation</p></def></def-item><def-item><term>FEP</term>
<def>
<p>fraction of evaporation from precipitation</p></def></def-item><def-item><term>FMP</term>
<def>
<p>Farm Process</p></def></def-item><def-item><term>FTR</term>
<def>
<p>fraction of transpiration</p></def></def-item><def-item><term>GHB </term>
<def>
<p>general head boundary</p></def></def-item><def-item><term>GIS</term>
<def>
<p>geographic information system</p></def></def-item><def-item><term>Kc</term>
<def>
<p>crop coefficient</p></def></def-item><def-item><term>M &amp; I</term>
<def>
<p>municipal and industrial</p></def></def-item><def-item><term>MCWRA</term>
<def>
<p>Monterey County Water Resources Agency</p></def></def-item><def-item><term>MF-OWHM</term>
<def>
<p>MODFLOW-One Water Hydrologic Model</p></def></def-item><def-item><term>MNW2</term>
<def>
<p>multi-node well package</p></def></def-item><def-item><term>NLCD</term>
<def>
<p>National Land Cover Database</p></def></def-item><def-item><term>NSME</term>
<def>
<p>Nash-Sutcliffe model efficiency</p></def></def-item><def-item><term>OFE</term>
<def>
<p>on-farm efficiency factor</p></def></def-item><def-item><term>PEST-HP</term>
<def>
<p>parameter estimation highly parallelized</p></def></def-item><def-item><term>PET</term>
<def>
<p>potential evapotranspiration</p></def></def-item><def-item><term>RAWS</term>
<def>
<p>Remote Automatic Weather Stations</p></def></def-item><def-item><term>RMSE</term>
<def>
<p>root mean square error</p></def></def-item><def-item><term>SFR2</term>
<def>
<p>Stream Flow Routing Package</p></def></def-item><def-item><term>SGMA</term>
<def>
<p>Sustainable Groundwater Management Act</p></def></def-item><def-item><term>SRDF</term>
<def>
<p>Salinas River Diversion Facility</p></def></def-item><def-item><term>SVGF</term>
<def>
<p>Salinas Valley Geologic Framework</p></def></def-item><def-item><term>SVIGSM</term>
<def>
<p>Salinas Valley Integrated Groundwater Model and Surface Model</p></def></def-item><def-item><term>SVIHM</term>
<def>
<p>Salinas Valley Integrated Hydrologic Model</p></def></def-item><def-item><term>SVOM</term>
<def>
<p>Salinas Valley Operational Model</p></def></def-item><def-item><term>SVWM</term>
<def>
<p>Salinas Valley Watershed Model</p></def></def-item><def-item><term>SVWP</term>
<def>
<p>Salinas Valley Water Project</p></def></def-item><def-item><term>SWO</term>
<def>
<p>surface-water operations</p></def></def-item><def-item><term>TAFY</term>
<def>
<p>thousand acre-feet per year</p></def></def-item><def-item><term>TAW</term>
<def>
<p>total applied water</p></def></def-item><def-item><term>TDR</term>
<def>
<p>total delivery requirement</p></def></def-item><def-item><term>USGS</term>
<def>
<p>U.S. Geological Survey</p></def></def-item><def-item><term>WBS</term>
<def>
<p>water balance subregion</p></def></def-item><def-item><term>WY</term>
<def>
<p>water year</p></def></def-item>
</def-list>
</glossary>
</front-matter>
<book-body>
<book-part>
<body>
<sec>
<title>Introduction</title>
<p>The Salinas Valley that surrounds the Salinas Valley groundwater basin in Monterey and San Luis Obispo Counties, California (<xref ref-type="fig" rid="fig01">fig. 1</xref>), is one of the most productive agricultural basins in California (<xref ref-type="bibr" rid="r17">California Department of Food and Agriculture, 2022</xref>) because of its fertile soil, temperate climate, and availability of water for irrigation (<xref ref-type="bibr" rid="r111">Lapham and Heileman, 1901</xref>; <xref ref-type="bibr" rid="r34">Cook, 1978</xref>). Agricultural production supports more than 76,000 local jobs (nearly 1 in 4 households) and contributes an estimated $5.7 billion per year to Monterey County&#x2019;s economic output and $8.12 billion to the local economy (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>). In addition, the Salinas Valley provides a substantial number of agricultural products for the Nation. Salinas Valley agriculture produces approximately 150 types of crops that comprise large percentages of the Nation&#x2019;s food, including 61 percent of leaf lettuce, 57 percent of celery, 56 percent of head lettuce, 48 percent of broccoli, 38 percent of spinach, 30 percent of cauliflower, 28 percent of strawberries, and 3.6 percent of wine grapes (<xref ref-type="bibr" rid="r17">California Department of Food and Agriculture, 2022</xref>). Therefore, water supply sustainability in the Salinas Valley is critical for local and national agricultural supplies. Changes in population (<xref ref-type="bibr" rid="r157">U.S. Census Bureau, 2018</xref>), increased agricultural development that includes a shift toward more water-intensive crops (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>), and climate variability have put increasing demand on water resources throughout the basin.</p>
<fig id="fig01" position="float" fig-type="figure"><label>Figure 1</label><caption><p>Salinas River watershed in Monterey and San Luis Obispo Counties of California, including the Salinas Valley groundwater basin, Zone 2C Water Management Area, Salinas, Lake Nacimiento and San Antonio reservoirs, Castroville Seawater Intrusion Project (CSIP), Salinas River Diversion Facility (SRDF), Clark Colony, and Tembladero Slough diversions.</p><p content-type="toc"><bold>1.</bold>	Map showing the Salinas River watershed in Monterey and San Luis Obispo Counties, including the Salinas Valley groundwater basin, Zone 2C Water Management Area, Salinas, Lake Nacimiento and San Antonio reservoirs, Castroville Seawater Intrusion Project, Salinas River Diversion Facility, Clark Colony, and Tembladero Slough diversions</p></caption><long-desc>1.	The Salinas River watershed is along California&#x2019;s central coast and includes nine major cities, two major highways, and one river.</long-desc><graphic xlink:href="sac23-0784_fig01"/></fig>
<sec>
<title>Motivation</title>
<p>Water management challenges in the Salinas Valley include coordinating conjunctive use of surface water and groundwater throughout the basin. Surface water and groundwater are used conjunctively to support coordinated management of reservoirs for flood mitigation, agricultural water supply, and habitat for federally listed threatened steelhead populations while mitigating aquifer storage losses that have resulted in groundwater level declines, seawater intrusion (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r113">Leedshill-Herkenhoff, Inc., 1985</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>, <xref ref-type="bibr" rid="r119">1996</xref>), and nitrate contamination (<xref ref-type="bibr" rid="r21">California Department of Water Resources, 1971a</xref>; <xref ref-type="bibr" rid="r110">Kulongoski and Belitz, 2007</xref>; <xref ref-type="bibr" rid="r126">Moran and others, 2011</xref>; <xref ref-type="bibr" rid="r83">Harter and others, 2012</xref>). Surface water is plentiful during wet periods, but precipitation and streamflow vary seasonally and year to year (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Thus, many people, industries, and ecosystems depend directly or indirectly on groundwater because surface-water supplies are variable in space and time. Surface-water sources used to meet agricultural water demands and support riparian habitat include reservoir releases from two reservoirs in the study area, recycled water deliveries near the coast, surface-water diversions from Arroyo Seco, and diversions from the Salinas River (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Surface-water resources are insufficient to meet water demands for all municipal, industrial, and agricultural needs in the basin (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>). Although there are two reservoirs within the study area that capture and store water during wet periods, the only conveyance of reservoir water to coastal agricultural areas is the Salinas River. The riverbed near the reservoirs is highly permeable with stream leakage that recharges nearby unconfined aquifers (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). This stream leakage results in reduction of streamflow through infiltration in the river as it drains toward the coast near Monterey Bay (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). The delivery of surface water to the coastal areas is limited by conveyance during dry periods and by surface-water storage capacity during wet periods (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>).</p>
<p>Groundwater pumpage is used extensively to supplement surface-water supplies to meet water demands where and when surface water is unavailable. Limitations on the spatial and temporal availability of surface water and associated dependence on groundwater has resulted in substantial groundwater storage losses in several groundwater basins (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Groundwater provides about 95 percent of the water used in the Salinas Valley (<xref ref-type="bibr" rid="r23">California Department of Water Resources, 1973</xref>), and groundwater extraction has been occurring in the area for at least a century. Extraction was estimated at 353 thousand acre-feet per year (TAFY) in the 1930s (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>), and groundwater use has increased over time. The average annual estimated groundwater pumpage from 1970 to 1994 was 519&#x2013;535 TAFY (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). The estimated Salinas Valley water budget for 2013 indicated a total reported pumpage of 509 TAFY, with an estimated cumulative storage depletion of 559,000 acre-feet from 1944 to 2013 (<xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>). Extensive use of groundwater has resulted in declines of groundwater levels (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>), groundwater storage depletion (<xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>), and seawater intrusion into aquifers near the coast (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r23">California Department of Water Resources, 1973</xref>; <xref ref-type="bibr" rid="r113">Leedshill-Herkenhoff, Inc., 1985</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>).</p>
<p>In the Salinas Valley near the Pacific coast, seawater intrusion has been observed in the primary water-bearing units of the Salinas Valley 180/400-Foot groundwater subbasin&#x2014;the 180- and 400-Foot Aquifers (<xref ref-type="bibr" rid="r113">Leedshill-Herkenhoff, Inc., 1985</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>, <xref ref-type="bibr" rid="r123">2020</xref>). The landward extent of the estimated acreage affected by seawater intrusion from 1944 to 2015 is estimated to be 28,257 and 17,125 acres in the 180- and 400-Foot Aquifers, respectively (<xref ref-type="bibr" rid="r123">Monterey County Water Resources Agency, 2020</xref>). Seawater intrusion advances inland, preferentially along geologic pathways that allow for easier movement of water, affecting land over the 180-Foot Aquifer at a rate of approximately 265 acres per year in the 180-Foot Aquifer and the land over the 400-Foot Aquifer at a rate of 414 acres per year. Several projects have been implemented that aim to reduce coastal groundwater pumping and seawater intrusion. The Monterey County Reclamation Project consists of the Salinas Valley Reclamation Project recycled water plant and the Castroville Seawater Intrusion Project (CSIP) distribution system. The Salinas Valley Water Project includes the Salinas River Diversion Facility (SRDF) to divert Salinas River water for treatment at the recycled water plant for distribution through CSIP to coastal agricultural fields and to offset groundwater pumpage.</p>
<p>Water quality changes from seawater intrusion are not the only concern for water managers in the Salinas Valley. Nitrate contamination continues to be a major concern (<xref ref-type="bibr" rid="r83">Harter and others, 2012</xref>). The State of California Water Resources Control Board is working to assess and monitor nitrate concentrations in groundwater and surface water in the Salinas Valley. Nitrate has been measured in groundwater and surface water, with some areas exceeding 130 milligrams per liter (mg/L), which is above the regulatory limit for drinking water of 45 mg/L (<xref ref-type="bibr" rid="r126">Moran and others, 2011</xref>). Although an evaluation of nitrate is not an aspect of this study, quantifying hydrologic flows and recharge rates are vital to understanding the timing and extent of nitrate contamination.</p>
<p>Water managers are challenged with operating the Lake San Antonio and Lake Nacimiento reservoirs to attain a variety of objectives. The reservoirs have mandated operational rules to control releases and storage for flood mitigation and water supply and to promote habitat for federally listed steelhead (<italic>Oncorhynchus mykiss</italic>) populations (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). These objectives have priorities, water rights, and regulatory requirements. Reservoir releases into the riverbed can contribute substantially to stream leakage as water is conveyed through the Salinas River to meet these objectives. Managing the timing and volume of releases is key to meeting objectives.</p>
<p>Conjunctive use of surface water and groundwater has been used in the Salians Valley to help manage groundwater resources. In 2014, the California legislature passed the Sustainable Groundwater Management Act (SGMA). The <xref ref-type="bibr" rid="r28">California Department of Water Resources (2023)</xref> provides a complete description of how SGMA is being implemented. As a part of SGMA, each groundwater basin throughout the State must develop a plan to assess historical groundwater conditions and develop groundwater sustainability plans to sustainably manage groundwater by 2040 or 2042, depending on its priority, as assigned by the California Department of Water Resources. To understand the historical conjunctive use of groundwater and surface water, it is important to define the quantity of the groundwater and surface-water supplies and to assess the efficiency of water resource use in the context of changing population, land use, crop type, irrigation practices, reservoir management, and climate. Analysis of the complex relationship between the use and movement of water in the Salinas Valley requires an integrated hydrologic model capable of tracking the three-dimensional flow of water in the aquifers, surface-water drainage networks, engineered conveyance structures, and reservoirs. Moreover, a comprehensive set of tools is needed to evaluate water supply projects and understand feedback between water quality and water supply. These evaluations are vital to the development of groundwater sustainability plans.</p>
<p>The evaluation of the Salinas Valley hydrologic system requires an integrated approach to describe the surface and subsurface and simulate natural and managed hydrologic flows. To simulate this system, a collection of geologic framework, surface-water, integrated, and operational models were developed into a comprehensive Salinas Valley System Model. The geologic framework is known as the Salinas Valley Geologic Framework (SVGF) and was developed to characterize the subsurface using various topographic and geologic data sources (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>). The surface-water model is called the Salinas Valley Watershed Model (SVWM) and simulates the Salinas River watershed that is used as monthly surface-water inflows into the integrated model (<xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>, <xref ref-type="bibr" rid="r97">b</xref>). The integrated model is called the Salinas Valley Integrated Hydrologic Model (SVIHM) and simulates historical conditions for groundwater levels and hydrologic budgets (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). The operational model is called the Salinas Valley Operational Model (SVOM) and adds an embedded reservoir operations framework to the simulation of SVIHM, which allows specified operational rules to simulate reservoir releases for two reservoirs (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p>
<p>Together, the Salinas Valley System Model was specifically developed to understand groundwater availability and use, support decision making throughout the Salinas Valley, and provide tools that can be used to evaluate sustainability plans and water supply projects. This study provides a description of the hydrologic conditions in the Salinas Valley, including an evaluation of total water demand for existing uses, seawater intrusion on an annual basis for the study period, and groundwater levels. The integrated hydrologic and reservoir operation models developed for this study will aid entities throughout Monterey County in evaluating water resources and groundwater sustainability in the Salinas Valley.</p>
</sec>
<sec>
<title>Previous Model Studies</title>
<p>Geologic mapping within the Salinas Valley occurred as early as 1900 (<xref ref-type="bibr" rid="r134">Nutter, 1901</xref>) and continued in the 1970s in the northern Salinas Valley (<xref ref-type="bibr" rid="r45">Durham, 1974</xref>) and southern Salinas Valley (<xref ref-type="bibr" rid="r156">Tinsley, 1975</xref>). Geologic mapping and hydrologic studies in the early 2000s (<xref ref-type="bibr" rid="r52">Feeney and Rosenberg, 2003</xref>; <xref ref-type="bibr" rid="r106">Kennedy/Jenks Consultants, 2004a</xref>, <xref ref-type="bibr" rid="r107">b</xref>) helped define the aquifer system and controls on groundwater flow. These geologic and hydrogeologic studies, among others, contribute to the conceptualization of the hydrogeologic units in the SVGF (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>).</p>
<p>There have been several modeling studies in the Salinas Valley. The first basin-scale model was developed by the U.S. Army Corps of Engineers and U.S. Geological Survey (USGS) in 1978. This model comprised a stream tributary model and a Salinas River model, and two-dimensional and three-dimensional finite difference groundwater models were developed as part of the study (<xref ref-type="bibr" rid="r44">Durbin and others, 1978</xref>). In 1986, Boyle Engineering Corporation used these models as the basis to develop a finite element model of the Salinas Valley Integrated Groundwater Model and Surface Model (SVIGSM, <xref ref-type="fig" rid="fig02">fig. 2</xref>; <xref ref-type="bibr" rid="r11">Boyle Engineering Corporation, 1987</xref>). <xref ref-type="bibr" rid="r175">Yates (1988)</xref> updated <xref ref-type="bibr" rid="r44">Durbin and others&#x2019; (1978)</xref> original two-dimensional model. In 1997, the SVIGSM was updated with refined input data, updated model parameters were developed through recalibration, and the model was extended through 1994 (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). In addition to the basin-scale models for the Salinas Valley, the adjudicated Seaside groundwater subbasin of the Salinas Valley (<xref ref-type="fig" rid="fig02">fig. 2</xref>) has a locally focused groundwater model that is used to develop the adjudication. In 2009, a MODFLOW-2005 (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>) groundwater model for the Seaside subbasin was developed by the watermaster to support the adjudication of water rights in the Seaside subbasin (<xref ref-type="bibr" rid="r102">Hydrometrics, LLC, 2009</xref>). Although the area that contains the Seaside subbasin is included in the newly developed integrated hydrologic model domain in this study, the Seaside subbasin was not specifically evaluated. The development of the watershed and integrated hydrologic models included the refinement of previous conceptual models (<xref ref-type="bibr" rid="r44">Durbin and others, 1978</xref>; <xref ref-type="bibr" rid="r175">Yates, 1988</xref>; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). The conceptual model for the integrated hydrologic models required the incorporation of natural and engineered features in the region, such as the SRDF, and reservoirs simulated in the operational model.</p>
<fig id="fig02" position="float" fig-type="figure"><label>Figure 2</label><caption><p>Integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing the Monterey County groundwater sustainability management area, Zone 2C Water Management Area, integrated hydrologic model domain, Salinas Valley Integrated Groundwater Model domain, and Seaside adjudicated groundwater subbasin.</p><p content-type="toc"><bold>2.</bold>	Map showing the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing the Monterey County groundwater sustainability management area, Zone 2C Water Management Area, integrated hydrologic model domain, Salinas Valley Integrated Groundwater Model domain, and Seaside adjudicated groundwater subbasin</p></caption><long-desc>2.	The active model domain follows the Salinas River and spans groundwater management areas and subbasins.</long-desc><graphic xlink:href="sac23-0784_fig02"/></fig>
<p>Prior models of the Salinas Valley groundwater basin were developed with the best tools available at the time of publication. Although the fundamental framework for simulating surface and groundwater flow was represented in these models, the spatial resolution was coarse (approximately 1,600 finite elements with areas ranging from 56 to 550 acres), aquifer representation was simplified to 1&#x2013;3 layers, model simulation periods were limited by challenges in updating and maintaining the model, and the representation of land use categories, agricultural demands, and reservoirs was simplified. Previous efforts within the region have either integrated all crop demands using an approach that considers consumptive use (SVIGSM; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>) or used virtual crop coefficients to represent water demands based on assumed or estimated distributions of crops (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r72">2014a</xref>, <xref ref-type="bibr" rid="r75">b</xref>). Simulations that group agricultural demands can provide a reasonable estimate of basin-scale water needs; however, there are limitations in using simulation alone for discerning the effect of changing acreages and harvest frequency of individual crops on water demands.</p>
<p>In the Salinas Valley, surface and groundwater are managed conjunctively to meet water demands; water demands are spatially variable and driven by land use; complex operational frameworks are applied to diversions, reservoir releases, and agricultural practices; and reservoirs are managed to meet multiple environmental and water supply objectives. Estimating crop production and water needs is key to managing groundwater and surface water sustainably and forecasting future water supply needs under climate variability and change. A comprehensive tool is needed that can represent the regional hydrologic system, where (1) the geologic framework is well defined, discretely representing all major aquifers as hydrogeologic units; (2) hydrologic processes and operations are represented at high resolution; (3) hydrologic budgets are aggregated to meaningful subareas with minimal processing; (4) hydrologic flows can be evaluated among groundwater and surface water regionally and among subareas; (5) land use input is comprehensive with representation of the land surface and the numerous crops grown in the basin; (6) crop demands and irrigation efficiencies are computed; (7) complex water supply projects can be implemented and evaluated; and (8) multi-objective reservoir operations can be simulated using established operational rules or configured to evaluate alternative rules. The integrated hydrologic models developed for this study meet these goals by building on the conceptual understanding of previous modeling efforts and leveraging recently developed software.</p>
</sec>
</sec>
<sec>
<title>Purpose and Scope</title>
<p>The purpose of this report is to document (1) the implementation of the geologic framework model and texture-based property characterization from the SVGF (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) into hydrogeologic units representing aquifers in integrated hydrologic models, (2) the evaluation of the hydrology and hydrogeology of the groundwater system, (3) the development of the historical and operational integrated hydrologic models, and (4) the analysis of historical water availability from the results of the integrated hydrologic models. There were three hydrologic models developed as part of this effort. The SVWM simulates the Salinas River watershed (<xref ref-type="fig" rid="fig01">fig. 1</xref>) and is documented in a separate report (<xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>, <xref ref-type="bibr" rid="r97">b</xref>). The two integrated hydrologic models developed in this study and documented here are SVIHM and SVOM. These models represent the Salinas Valley groundwater basin (<xref ref-type="fig" rid="fig01">fig. 1</xref>) with primary focus on the primary water-producing subareas of Monterey County Water Resources Agency (MCWRA) Zone 2C Water Management Area (<xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>) and the groundwater sustainability management area (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>; <xref ref-type="fig" rid="fig02">fig. 2</xref>). The integrated hydrologic models simulate the integrated surface-water and groundwater system for water years (WY) 1968&#x2013;2018. This report supersedes the preprint of the same name (<xref ref-type="bibr" rid="r95">Henson and others, 2025b</xref>).</p>
</sec>
<sec id="sac23-0784_Final_20260508_kc.DescriptionofStudyArea">
<title>Description of Study Area</title>
<p>The Salinas River watershed (<xref ref-type="fig" rid="fig01">fig. 1</xref>) includes the drainage areas of the Salinas River in San Luis Obispo and Monterey Counties and includes upland tracts of surrounding hills and mountains, coastal lowlands, and offshore areas within Monterey Bay and the drainage areas of other creeks and canals within the Salinas Valley. The Salinas River watershed (<xref ref-type="fig" rid="fig01">fig. 1</xref>) and adjacent coastal drainages, including the areas of agricultural and groundwater development, comprise a total area of 4,529 square miles (mi<sup>2</sup>; <xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>). The watershed encompasses the Salinas River, and the portion of the watershed in Monterey County is referred to as the &#x201C;Salinas Valley.&#x201D; The Salinas River is the largest river within California&#x2019;s central coast region (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). The Salinas River begins in San Luis Obispo County at the Santa Margarita Lake and enters the Salinas Valley near the boundary between San Luis Obispo and Monterey Counties. The Salinas Valley extends approximately 150 miles (mi) from the border of San Luis Obispo County north-northwest to its mouth at Monterey Bay, with a total area of 4,200 mi<sup>2</sup> in Monterey and San Luis Obispo Counties. The Salinas Valley is bounded on the west by the Santa Lucia Range and Sierra de Salinas and on the east by the Gabilan and Diablo Ranges. Monterey Bay acts as the northwestern boundary of the Salinas Valley (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>), and the Monterey County border is the southern boundary (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). In the southern Salinas Valley, there are two reservoirs that release flow into tributaries of the Salinas River, Lake San Antonio and Lake Nacimiento (<xref ref-type="fig" rid="fig01">fig. 1</xref>).</p>
<p>Several subareas of interest are the Zone 2C Water Management Area, Salinas Valley groundwater sustainability basin management boundary, and the integrated hydrologic model domain. The Zone 2C Water Management Area was defined by Monterey County (Ordinance 3717; <xref ref-type="fig" rid="fig02">fig. 2</xref>) as a benefit assessment zone for water resource management of surface water and groundwater among the streams, reservoirs, and groundwater subbasins of the Salinas Valley within Monterey County (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). Some of the Salinas Valley groundwater subbasins have similar names to the hydrogeologic units defined for the Salinas Valley (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>). For example, the Salinas Valley 180/400-Foot Aquifer groundwater subbasin represents an area defined by <xref ref-type="bibr" rid="r27">California Department of Water Resources (2020)</xref> and the 180-Foot Aquifer hydrogeologic unit (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) describes the lateral extent of the subsurface 180-Foot Aquifer. The extent of the subsurface 180-Foot Aquifer may continue beyond the boundary of the 180/400-Foot Aquifer groundwater subbasin. For consistency, all references to the hydrogeologic units for the 180-Foot Aquifer and 400-Foot Aquifer are capitalized. To provide clear management boundaries for assessing surface water, groundwater, and their interaction in the Salinas Valley, the California Department of Water Resources defined the groundwater sustainability management boundary in this study area as the portion of the Salinas Valley groundwater basin in Monterey County (<xref ref-type="fig" rid="fig02">fig. 2</xref>; <xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>); the rest of the Salinas Valley groundwater basin in San Luis Obispo County is separately managed. In this report, the term &#x201C;Salinas Valley&#x201D; is used to generally refer to the area represented by the integrated hydrologic model domain that surrounds the groundwater sustainability management boundary. The integrated hydrologic model domain surrounds both the Zone 2C Water Management Area and the Salinas Valley and extends to the ridges of the surrounding hillsides and offshore (<xref ref-type="fig" rid="fig02">fig. 2</xref>). The integrated hydrologic model domain described in this report focuses on the Salinas River, two reservoirs, and groundwater basins within the Salinas Valley (<xref ref-type="fig" rid="fig02">fig. 2</xref>).</p>
<sec id="sac23-0784_Final_20260508_kc.Climate">
<title>Climate</title>
<p>The Salinas Valley has a Mediterranean climate, with generally dry and mild summers, and wet, cool winters (<xref ref-type="bibr" rid="r175">Yates, 1988</xref>). Topography and proximity to the Pacific Ocean have a strong effect on the spatial distribution of precipitation within the integrated hydrologic model domain (<xref ref-type="fig" rid="fig03">fig. 3</xref>). Mean annual gridded precipitation at a 530 by 530-foot (ft) resolution for WY 1968&#x2013;2018 within the study area (<xref ref-type="fig" rid="fig03">fig. 3</xref>) shows higher precipitation values in adjacent mountain ranges and the coastal area of the integrated hydrologic model area (16&#x2013;26 inches [in.] per year) with lower values in the center and upper valley of the integrated hydrologic model area (10&#x2013;15 in. per year; <xref ref-type="bibr" rid="r89">Henson and others, 2022c</xref>). Throughout the integrated hydrologic model area, precipitation is almost entirely rain, with approximately 90 percent falling during the 6-month period from November to April (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>; <xref ref-type="bibr" rid="r175">Yates, 1988</xref>). Climate zones were defined to analyze variations in climate throughout the Salinas Valley. California Irrigation Management Information System (CIMIS) climate zones in the Salinas Valley (<xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>) were aggregated into inland and coastal climate zones and clipped to the integrated hydrologic model area boundary for this study (<xref ref-type="fig" rid="fig03">fig. 3</xref>; <xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>). The aggregation of CIMIS climate zones was informed by analysis of the spatial distribution of precipitation and potential evapotranspiration (PET) and showed precipitation and PET change in the middle of the basin. Precipitation and cumulative departure of precipitation are shown for two Cooperative Observer Network (COOP) climate stations (<xref ref-type="fig" rid="fig04">fig. 4</xref>): one station is near the coast at the Salinas Airport (COOP station USW00023233), and one station is inland near King City (COOP station USC00044555). Climate data show the following: (1) year-to-year variability in precipitation is prevalent, (2) cumulative precipitation departure from the mean includes multiple wet and dry periods, and (3) there is a precipitation gradient such that mean precipitation is higher near the coast than inland. Mean precipitation at climate stations is 12.27 in. near the coast (<xref ref-type="fig" rid="fig04">fig. 4<italic>A</italic></xref>) and 11.27 in. inland (<xref ref-type="fig" rid="fig04">fig. 4<italic>B</italic></xref>). Similarly, long-term average gridded climate data show average precipitation as 14&#x2013;15 in. near the coast and 10&#x2013;13 in. inland (<xref ref-type="fig" rid="fig03">fig. 3</xref>). Climate data show that year-to-year variability in precipitation is prevalent (<xref ref-type="fig" rid="fig04">figs. 4<italic>A</italic></xref>, <xref ref-type="fig" rid="fig04">4<italic>B</italic></xref>). Cumulative precipitation departure from the mean at both stations in the study area in Monterey and San Luis Obispo Counties of California show relatively dry periods when cumulative precipitation departure from the mean decreases over multiple years, where mean precipitation is calculated from water years 1968&#x2013;2018. Periods where the cumulative precipitation departure from the mean is flat represent average conditions and are interpreted using antecedent conditions. Shaded tan areas on <xref ref-type="fig" rid="fig04">figure 4</xref> highlight the relatively dry conditions from WY 1984 to 1994 and from 2012 to 2018.</p>
<fig id="fig03" position="float" fig-type="figure"><label>Figure 3</label><caption><p>Average annual gridded precipitation in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California at 530-foot resolution for water years 1968&#x2013;2018. The coastal and inland climate zones are based on aggregation of California Irrigation Management Information System (CIMIS) climate zones, CIMIS stations, selected climate stations, Remote Automatic Weather Stations (RAWS), Cooperative Observer Network (COOP) stations, and two analysis COOP stations: Salinas Airport (USW00023233) and King City, California (USC00044555; <xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>).</p><p content-type="toc"><bold>3.</bold>	Map showing the average annual gridded precipitation in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California at 530-foot resolution for water years 1968&#x2013;20</p></caption><long-desc>3.	Precipitation in the active model domain is generally higher in adjacent mountain ranges and the coastal area with lower values in the central and upper valley.</long-desc><graphic xlink:href="sac23-0784_fig03"/></fig>
<fig id="fig04" position="float" fig-type="figure"><label>Figure 4</label><caption><p>Annual precipitation at selected Cooperative Observer Network stations (COOP; <xref ref-type="bibr" rid="r132">National Oceanic and Atmospheric Administration, 2020</xref>) for water years 1968&#x2013;2018 for <italic>A</italic>, Salinas Airport (USW00023233) and <italic>B</italic>, King City, California (USC00044555). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18 based on the cumulative precipitation departure from the mean. <italic>C</italic>, Cumulative precipitation departure from the mean at Salinas Airport (USW00023233) and King City, California (USC00044555), showing delineation of analysis periods A, B, C, and D for the study.</p><p content-type="toc"><bold>4.</bold>	Graphs showing annual precipitation at selected Cooperative Observer Network stations for water years 1968&#x2013;2018 for Salinas Airport and King City, California</p></caption><long-desc>4. Interannual precipitation variability is high at both Salinas Airport (north) and King City climate stations, with greater cumulative deviation at the Salinas Airport.</long-desc><graphic xlink:href="sac23-0784_fig04"/></fig>
<p>Climate year types (wet, normal, or dry) affect availability of surface water, magnitudes of groundwater recharge, and agricultural practices; climate year types are used by MCWRA to guide operation of Lake San Antonio and Lake Nacimiento. Moreover, climate year types can be used to analyze changes caused by wet or dry periods in data and results. Climate year types are defined by the percentile of annual mean flow at the Arroyo Seco near Soledad gage (USGS 11152000; <xref ref-type="fig" rid="fig02">fig. 2</xref>). A wet year is defined as years with annual mean flow greater than or equal to the 75th percentile of flow. Dry years are defined as years with annual mean flow less than or equal to the 25th percentile. Normal WYs are defined as having annual mean flow between the 25th and 75th percentiles, preliminarily determined on March 15th and officially on April 1st (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>). The MCWRA assesses climate year types using a five-tiered WY classification (dry, dry-normal, normal, wet-normal, wet); for the integrated hydrologic models, we reclassify these into a three-tiered classification: dry, normal (which includes dry-normal, normal, and wet-normal), and wet. These climate types are based on flow conditions at streamgage USGS 11152000, not precipitation at climate stations, so there may be years when precipitation is low, but the climate year type is normal.</p>
<p>A critical component of the hydrologic cycle in the region is evapotranspiration. Available monthly gridded 530-ft resolution PET data (<xref ref-type="bibr" rid="r89">Henson and others, 2022c</xref>) were aggregated to mean annual values. Mean annual PET for WY 1968&#x2013;2018 within the study area (<xref ref-type="fig" rid="fig05">fig. 5</xref>) shows relationships between topography and proximity to the Pacific Ocean, with higher PET values in adjacent mountain ranges and the upper valley (52&#x2013;65 in. per year) and lower values in the center of the valley and coastal region (39&#x2013;51 in. per year). Throughout the domain, PET is higher than precipitation (<xref ref-type="fig" rid="fig03">figs. 3</xref>, <xref ref-type="fig" rid="fig05">5</xref>).</p>
<fig id="fig05" position="float" fig-type="figure"><label>Figure 5</label><caption><p>Annual average gridded potential evapotranspiration in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California at 530-foot resolution for water years 1968&#x2013;2018. Coastal and inland climate zones are based on aggregation of California Irrigation Management Information System (CIMIS) climate zones, CIMIS evaluation locations, Remote Automatic Weather Stations (RAWS), and Cooperative Observer Network (COOP) stations.</p><p content-type="toc"><bold>5.</bold>	Map showing annual average gridded potential evapotranspiration in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California at 530-foot resolution for water years 1968&#x2013;2018</p></caption><long-desc>5. Potential evapotranspiration in the active model domain is generally higher in the upper valley and decreases toward the coast.</long-desc><graphic xlink:href="sac23-0784_fig05"/></fig>
</sec>
<sec>
<title>Land Use</title>
<p>Land use data compiled for the study include maps of native, urban, and managed land cover from the National Land Cover Database (NLCD; <xref ref-type="bibr" rid="r159">U.S. Geological Survey, 2000</xref>, <xref ref-type="bibr" rid="r160">2003</xref>, <xref ref-type="bibr" rid="r161">2011</xref>, <xref ref-type="bibr" rid="r163">2014</xref>; <xref ref-type="bibr" rid="r38">Dewitz and U.S. Geological Survey, 2021</xref>) that were integrated with locally developed periodic land use maps (<xref ref-type="bibr" rid="r22">California Department of Water Resources, 1971b</xref>, <xref ref-type="bibr" rid="r25">1997</xref>, <xref ref-type="bibr" rid="r26">2014</xref>). Additionally, we incorporated land use data obtained by MCWRA from the Association of Monterey Bay Area Governments for 1992 and for the recent update to the Salinas Valley Integrated Geologic System Model in 2012. We then supplemented our analysis using National Agriculture Imagery Program aerial photography (<xref ref-type="bibr" rid="r158">U.S. Department of Agriculture, 2016</xref>), economic reports (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>), and pesticide application records (<xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation, 2018</xref>).</p>
<p>Categorized and summarized land use data for the years 1968, 1984, 2000, and 2014 illustrate land use change in the Salinas Valley on <xref ref-type="fig" rid="fig06">figures 6<italic>A</italic>&#x2013;<italic>D</italic></xref>, respectively. On each land use map, a pie diagram highlights land use categories to illustrate total land use change through time. This study evaluates irrigated agriculture where agricultural demand data are available in the Zone 2C Water Management Area. Data from a national irrigated lands dataset (<xref ref-type="bibr" rid="r174">Xie and others, 2019</xref>) are shown (<xref ref-type="fig" rid="fig06">fig. 6<italic>D</italic></xref>) to illustrate additional potential irrigated areas within the study area that are not evaluated in this study. The development of land use data and model input are summarized in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.IntegratedHydrologicandOperationalModelDevelo">Integrated Hydrologic and Operational Model Development</xref>&#x201D; section in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.LandUseData">Land Use Data</xref>&#x201D; subsection of this report and are fully described by <xref ref-type="bibr" rid="r92">Henson and Jachens (2024)</xref>.</p>
<fig id="fig06" position="float" fig-type="figure"><label>Figure 6</label><caption><p>Land use in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California (<xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>) for calendar years <italic>A</italic>, 1968; <italic>B</italic>, 1984; <italic>C</italic>, 1998; and <italic>D</italic>, 2014. The model includes additional remotely sensed irrigated areas within the study area and outside of Zone 2C Water Management Area.</p><p content-type="toc"><bold>6.</bold>	Maps and pie diagrams showing land use in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for calendar years 1968, 1984, 1998, and 2014</p></caption><long-desc>6. Native vegetation and high frequency rotational crops cover more than 80 percent of land use in the active model domain.</long-desc><graphic xlink:href="sac23-0784_fig06a"/><graphic xlink:href="sac23-0784_fig06b"/><graphic xlink:href="sac23-0784_fig06c"/><graphic xlink:href="sac23-0784_fig06d"/></fig>
<sec>
<title>Native Land Cover and Urban and Managed Land Use</title>
<p>Native land cover and urban and managed land use categories in the Salinas Valley have been stable through time (<xref ref-type="fig" rid="fig06">figs. 6<italic>A</italic>&#x2013;<italic>D</italic></xref>). The native land cover category includes water bodies, riparian areas, upland grasslands/shrub lands, woodlands, beach-dunes, and barren-burned land cover and represents approximately 54&#x2013;56 percent of land cover (<xref ref-type="fig" rid="fig06">figs. 6<italic>A</italic>&#x2013;<italic>D</italic></xref>). The managed land use category includes pasture, non-irrigated fields, semiagricultural fields, idle-fallow fields, and quarries; the urban land use category includes golf course turf/parks and urban areas. The largest urban areas are the Cities of Monterey, Salinas, and King City (<xref ref-type="bibr" rid="r110">Kulongoski and Belitz, 2007</xref>). Urban areas represent the maximum extent of urban areas for the period from 1968 to 2014 based on aerial imagery. The combined urban and managed land use category represents more area in 1968 (approximately 15 percent of land use) due to pasture distributed throughout the Salinas Valley. After 1968, the pasture is supplanted by irrigated land uses, and both the urban and managed land use category areas are relatively stable (approximately representing 6&#x2013;8 percent of land use; <xref ref-type="fig" rid="fig06">figs. 6<italic>B</italic>&#x2013;<italic>D</italic></xref>).</p>
</sec>
<sec>
<title>Irrigated Land Use</title>
<p>The variety of crops grown within the Salinas Valley has changed substantially throughout the simulation period; however, leafy vegetables, such as lettuce, have been a primary crop of the Salinas Valley for more than 70 years (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>). Other important crops in the Salinas Valley include artichokes, crucifers (broccoli and cauliflower), wine grapes, celery, onions, and strawberries (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>). Multi-cropping, more than one harvest of one or more crops from a given field, is a common practice in the Salinas Valley (<xref ref-type="bibr" rid="r25">California Department of Water Resources, 1997</xref>; <xref ref-type="bibr" rid="r145">Smukler and others, 2008</xref>). Land use maps (<xref ref-type="fig" rid="fig06">figs. 6<italic>A</italic>&#x2013;<italic>D</italic></xref>) represent the physical extent of planted acreage, not the harvested acreage that is reported in agricultural reports (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>). To illustrate potential changes in land use due to multi-cropping, land use data were categorized based on the frequency with which they were likely to change within one growing season. There were three irrigated land use subcategories delineated: annually stable, high frequency rotational, and multi-year. If multiple crops can occupy the same area within a year, the land use was defined as &#x201C;high frequency rotational.&#x201D; If crops are stable for at least 1 year but can change year to year, the land use was defined as &#x201C;annually stable.&#x201D; If crops are likely to change over multiple years to decades, the land use was defined as &#x201C;multi-year.&#x201D;</p>
<p>The sum of the irrigated areas represented by the three irrigated land use subcategories was relatively stable through time ranging from approximately 31 to 37 percent of land use (<xref ref-type="fig" rid="fig06">figs. 6<italic>A</italic>&#x2013;<italic>D</italic></xref>). Although the total irrigated land use area did not vary substantially, there were changes in the distribution of irrigated land use subcategory areas and the implementation of multi-cropping increased. The distribution of irrigated land use subcategories for multi-year and annually stable crops increased through time. The most substantial increases in these subcategories occurred between 1968 (<xref ref-type="fig" rid="fig06">fig. 6<italic>A</italic></xref>) and 1984 (<xref ref-type="fig" rid="fig06">fig. 6<italic>B</italic></xref>). The percentage of areas represented by multi-year vineyards increased by approximately 5 percent, and annually stable strawberries increased to represent approximately 1 percent of the land use. These trends of increased land use area for multi-year vineyards and annually stable strawberries continued into the year 2000 (<xref ref-type="fig" rid="fig06">fig. 6<italic>C</italic></xref>) and remained relatively stable from 2000 to 2014 (<xref ref-type="fig" rid="fig06">fig. 6<italic>D</italic></xref>). Over the same period from 1968 to 2000, the practice of multi-cropping increased, as shown by the total reported harvested acres (<xref ref-type="fig" rid="fig07">fig. 7</xref>; <xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>), which increased more than the area represented by the high frequency rotational irrigated land use subcategory (approximately 27&#x2013;31 percent of land use, <xref ref-type="fig" rid="fig06">figs. 6<italic>A</italic>&#x2013;<italic>D</italic></xref>).</p>
<fig id="fig07" position="float" fig-type="figure"><label>Figure 7</label><caption><p>Cropped acreage estimates in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California and total harvested acres in Monterey County during the study period. Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>7</bold>.	Graph showing cropped acreage estimates in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California and total harvested acres in Monterey County during the study period</p></caption><long-desc>7. Total harvested acreage varies annually and trends upward throughout the study period.</long-desc><graphic xlink:href="sac23-0784_fig07"/></fig>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.SurfaceWaterandWatershed">
<title>Surface Water and Watershed</title>
<p>The characteristics of high relief and mountainous terrain combined with a focused distribution of annual precipitation to a limited number of winter (December&#x2013;March) storms result in large variations in Salinas River streamflow, both seasonally and between peak and mean streamflow conditions (<xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>). Streamflow enters the Salinas River from ephemeral runoff from valley slopes; local, ungaged surface-water drainage networks, such as the Arroyo Seco and San Lorenzo Creek tributaries; and local reservoirs, such as Santa Margarita Lake, Lake Nacimiento, and Lake San Antonio (<xref ref-type="fig" rid="fig01">fig. 1</xref>). Flows into the Salinas Valley from ephemeral drainages and intermittent creeks that feed into the Salinas River can be substantial but vary in time. <xref ref-type="fig" rid="fig08">Figure 8</xref> shows a comparison between total annual estimated ungaged inflows to the watershed inflows (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>) and total annual streamflow at the first streamgage on the Salinas River within the study area (USGS 11150500 Salinas River near Bradley; <xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>) to illustrate the relative magnitude of stream and watershed inflows into the Salinas River within the Salinas Valley. This comparison confirms that watershed inflows are intermittent, but there are periods where watershed inflows can provide substantial runoff to the Salinas Valley. Arroyo Seco has long been considered a substantial tributary for water supply in the study area (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>). Surface-water flows measured in Arroyo Seco (USGS 11152000, <xref ref-type="fig" rid="fig01">fig. 1</xref>; <xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>) are used to manage reservoir operational decisions (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Three reservoirs are connected to the Salinas River: Santa Margarita Lake completed in 1941, Lake Nacimiento dam and reservoir completed in 1957, and Lake San Antonio dam and reservoir completed in 1967 (<xref ref-type="fig" rid="fig01">fig. 1</xref>). Santa Margarita Lake is not represented in the hydrologic models presented in this report because it is outside of the integrated hydrologic model domain; however, it is the upper boundary of the Salinas River.</p>
<fig id="fig08" position="float" fig-type="figure"><label>Figure 8</label><caption><p>Comparison of total annual watershed inflows into the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California from the Salinas Valley Watershed Model and observed Salinas River flows at the first gage on Salinas River in the study area (USGS 11150500 Salinas River near Bradley, California; <xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>) to show the relative contribution of surface water from adjacent watershed inflows and inflows from the upper watershed outside of the study area for water years 1968&#x2013;2018. Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>8.</bold>	Graph showing a comparison of total annual watershed inflows into the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California from the Salinas Valley Watershed Model and observed Salinas River flows at the first gage on Salinas River in the study area to show the relative contribution of surface water from adjacent watershed inflows and inflows from the upper watershed outside of the study area for water years 1968&#x2013;2018</p></caption><long-desc>8. Total annual watershed inflows are greater than annual gaged streamflow for most of the study period.</long-desc><graphic xlink:href="sac23-0784_fig08"/></fig>
<p>Flow from the Salinas River travels down approximately 115 mi of stream channel within the study area before discharging to Monterey Bay. Streamflow is highly variable both spatially and temporally in the Salinas River due to variation in climate and streamflow gains and losses. At the uppermost Salinas River gage in the integrated hydrologic model area (USGS 11150500 Salinas River near Bradley) for WY 1968&#x2013;2018, monthly average streamflow is 518 cubic feet per second (ft<sup>3</sup>/s) but is highly variable, ranging from less than 1 to 10,185 ft<sup>3</sup>/s (<xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>). Stream gains and losses vary along the length of the river. Between the Salinas River near Bradley (USGS 11150500) and near Soledad (USGS 11151700) gages, the average monthly streamflow difference is 117 ft<sup>3</sup>/s and ranges between 859 ft<sup>3</sup>/s (loss) and &#x2212;1,655 ft<sup>3</sup>/s (gain), with losing conditions occurring between the gages for 83 percent of months with observations (<xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>). Between the Salinas River near Bradley (USGS 11150500) gage and the last gage on the Salinas River (USGS 11152500 Salinas River near Spreckels), the average monthly streamflow difference is positive, indicating losing stream conditions with a mean reduction in streamflow of 88 ft<sup>3</sup>/s and a maximum of 683 ft<sup>3</sup>/s over all observations. The streamflow gains occur typically from intermittent storm flow, and streamflow losses are due to stream leakage through coarse materials in the streambed.</p>
<p>Historically, surface-water supply from the Salinas River and its tributaries was limited due to variability and uncertainty in streamflow year to year (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>). To support irrigated agriculture, there is a continued need to develop new water supplies using conjunctive use strategies to meet existing and projected water demand. Currently, these strategies focus on increasing storage of surface water in reservoirs during wet periods, deliveries of recycled water from urban areas to coastal regions to offset groundwater pumpage, and regular surface-water diversions from the Salinas River and its tributaries.</p>
<p>Lakes Nacimiento and San Antonio provide flood control for the Salinas Valley and hydroelectric power, with a maximum storage capacity of 377,900 and 335,000 acre-feet, respectively. Throughout the study period, average annual reservoir storage varied with climate and ranged from approximately 14,000 to 300,000 acre-feet in Lake San Antonio and from 22,000 to 300,000 acre-feet in Lake Nacimiento (<xref ref-type="fig" rid="fig09">fig. 9</xref>; <xref ref-type="bibr" rid="r85">Henson and others, 2022a</xref>). In 1998, the Monterey County Water Recycling Project began delivering a new supply of tertiary-treated wastewater to 12,000 acres of coastal farmland as part of the CSIP to reduce the need for groundwater pumping and mitigate seawater intrusion. Reported diversion from Arroyo Seco at Clark Colony (Clark Colony diversion) has been used to meet agricultural demands, and a 1 ft<sup>3</sup>/s diversion from Tembladero Slough has been used for maintaining wetted channel conditions. These two diversions represent the most continuously reported surface-water source for irrigation (<xref ref-type="fig" rid="fig10">fig. 10</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). The Salinas Valley Water Project (SVWP) was started in 2003 to deliver supplemental water to meet irrigation needs and recharge the basin (<xref ref-type="bibr" rid="r120">Monterey County Water Resources Agency, 2001</xref>). In 2010, enhancements to the SVWP involved installation of a rubber spillway gate and dam near the SRDF that diverts flow from the Salinas River to be treated and delivered to coastal farmland as part of CSIP.</p>
<fig id="fig09" position="float" fig-type="figure"><label>Figure 9</label><caption><p>Comparison of annual mean storage in Lakes San Antonio and Nacimiento in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2018. Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>9.</bold>	Graph showing a comparison of annual mean storage in Lakes San Antonio and Nacimiento in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2018</p></caption><long-desc>9. Lake San Antonio generally had a higher annual storage than Lake Nacimiento most of the study period.</long-desc><graphic xlink:href="sac23-0784_fig09"/></fig>
<fig id="fig10" position="float" fig-type="figure"><label>Figure 10</label><caption><p>Surface-water deliveries from agricultural diversions for Clark Colony and Salinas River Diversion Facility (SRDF), channel wetting diversions for Tembladero Slough, and recycled water deliveries for the Castroville Seawater Intrusion Project (CSIP) for water years 1968&#x2013;2018 (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>10.</bold>	Graph showing surface-water deliveries from agricultural diversions for Clark Colony and Salinas River Diversion Facility, channel wetting diversions for Tembladero Slough, and recycled water deliveries for the Castroville Seawater Intrusion Project for water years 1968&#x2013;2018</p></caption><long-desc>10. The largest surface-water delivery was from Clark Colony until 1999, after which recycled water was the largest.</long-desc><graphic xlink:href="sac23-0784_fig10"/></fig>
</sec>
<sec>
<title>Geology of Groundwater Basins</title>
<p>The Salinas Valley is a large intermontane valley that extends southeastward from Monterey Bay to Paso Robles. The groundwater basins of the Salinas Valley are some of the largest coastal groundwater basins in central California (<xref ref-type="fig" rid="fig11">fig. 11</xref>; <xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). The groundwater basins are structural basins formed, in part, by normal faulting along the western margin of the valley from King City to Monterey Bay (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). Downward movement of the valley-side fault block resulted in the deposition of a westward thickening alluvial wedge above crystalline bedrock (<xref ref-type="bibr" rid="r144">Showalter and others, 1984</xref>) that is as thick as 10,000 ft on the east side of the basin and as thick as 15,000 ft on the west side. These Tertiary and Quaternary marine and terrestrial sediments include as much as 2,000 ft of saturated alluvium (<xref ref-type="bibr" rid="r144">Showalter and others, 1984</xref>). The sediments that contain the aquifers of the Salinas Valley are a combination of gravels, sands, silts, and clays that are organized into sequences of relatively coarse-grained and fine-grained materials. The three-dimensional distribution of sediment texture and hydrogeologic units in the Salinas Valley are defined in the SVGF (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>). A summary of the geologic framework is provided in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.GeologicFramework">Geologic Framework</xref>&#x201D; section and fully described by <xref ref-type="bibr" rid="r151">Sweetkind (2023)</xref>.</p>
<fig id="fig11" position="float" fig-type="figure"><label>Figure 11</label><caption><p>Groundwater basins and subbasins within and adjacent to the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California.</p><p content-type="toc"><bold>11.</bold>	Map showing groundwater basins and subbasins within and adjacent to the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>11. Salinas Valley groundwater subbasins include Paso Robles Area, Upper Valley Aquifer, Seaside, Monterey, 180/400-Foot Aquifer, and Langley Area.</long-desc><graphic xlink:href="sac23-0784_fig11"/></fig>
</sec>
<sec>
<title>Groundwater</title>
<p>Groundwater movement is generally from the southern part of the Salinas Valley north toward Monterey Bay. Components of the groundwater flow system include groundwater recharge, groundwater use, and natural groundwater discharge. Groundwater budget components include total recharge, total pumpage, aquifer storage changes, seawater coastal inflow (an analogue for seawater intrusion), and groundwater exchanges among groundwater subbasins within the Salinas Valley. The Salinas Valley groundwater basin is divided into seven subbasins that represent both hydrologic and management boundaries: the 180- and 400-Foot Aquifer subbasin, East Side Aquifer subbasin, Forebay Aquifer subbasin, Langley Area subbasin, Monterey subbasin, Seaside subbasin, and Upper Valley Aquifer subbasin (<xref ref-type="fig" rid="fig11">fig. 11</xref>; <xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). These groundwater subbasins are used to manage groundwater sustainability by groundwater sustainability agencies and water agencies. The tools developed for this study support the evaluation of groundwater and surface-water availability and conjunctive use of groundwater throughout these groundwater subbasins. The geologic framework developed alongside this study (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) contains the Salinas Valley groundwater basin and the hydrogeologic units that span its subbasins. Therefore, the individual groundwater subbasins are not described in detail in this report. A full description of the groundwater subbasins is provided by the <xref ref-type="bibr" rid="r27">California Department of Water Resources (2020)</xref>.</p>
<sec>
<title>Groundwater Recharge</title>
<p>Recharge to the groundwater system is primarily from stream-channel infiltration from the major rivers and their tributaries and from infiltration of water from precipitation and irrigation (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Infiltration of runoff along with percolation of a fraction of precipitation and irrigation below the root zone contribute to groundwater recharge. Mountain block recharge into the East Side Aquifer and Langley Area subbasins occurs along the Gabilan Range (<xref ref-type="fig" rid="fig11">fig. 11</xref>). Additional regional groundwater flow occurs under the Salinas River where the river enters the Salinas Valley at the southern integrated hydrologic model boundary (<xref ref-type="fig" rid="fig02">fig. 2</xref>).</p>
</sec>
<sec>
<title>Observed Trends in Groundwater Levels</title>
<p>Groundwater level contours (<xref ref-type="fig" rid="fig12">figs. 12<italic>A</italic></xref>, <xref ref-type="fig" rid="fig12">12<italic>B</italic></xref>) for 1994 conditions were developed by MCWRA (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Shallow and deep groundwater contours show that lateral gradients in the aquifer generally follow the gradient of the Salinas River stream channel through the valley. Where contoured groundwater data are available for the deeper aquifers, contours show vertical hydraulic gradients are downward from the shallow (180-Foot Aquifer) to the deep (400-Foot Aquifer) in the 180/400-Foot Aquifer groundwater subbasin. The combined effects of groundwater pumping for irrigation and water supply have periodically depressed the groundwater levels in and near the 180/400-Foot Aquifer, East Side Aquifer, and Forebay Aquifer groundwater subbasins of the Salinas Valley during dry periods, where most agriculture and urban development has been centered since the 1920s (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r115">Manning, 1963</xref>). A region of lower groundwater levels is observed in both aquifers near the city of Salinas. Long-term groundwater level declines over the study period have been observed in monitoring wells (<xref ref-type="bibr" rid="r119">Monterey County Water Resources Agency, 1996</xref>) throughout the 180/400-Foot Aquifer and East Side Aquifer groundwater subbasins (<xref ref-type="fig" rid="fig13">figs. 13<italic>A</italic></xref>, <xref ref-type="fig" rid="fig13">13<italic>B</italic></xref>), resulting from lowering of groundwater levels during the 1984&#x2013;94 dry period. The groundwater levels did not recover to levels observed before the dry period. The long-term groundwater level decline in the 180/400-Foot Aquifer groundwater subbasin is approximately 10 ft and stabilized after 1995 (<xref ref-type="fig" rid="fig13">fig. 13<italic>A</italic></xref>); declines in the East Side Aquifer groundwater subbasin are approximately 50 ft (<xref ref-type="fig" rid="fig13">fig. 13<italic>B</italic></xref>) and are larger than the annual variability. Wells in the Forebay Aquifer groundwater subbasin (<xref ref-type="fig" rid="fig13">fig. 13<italic>C</italic></xref>) show groundwater levels decreased in response to the 1984&#x2013;94 dry period, but groundwater recovered afterward. Wells in the Upper Valley Aquifer groundwater subbasin (<xref ref-type="fig" rid="fig13">fig. 13<italic>D</italic></xref>) show stable groundwater levels through the study period and a faster recovery after the dry period relative to other groundwater subbasins, likely due to groundwater recharge from reservoir operations in the Upper Valley Aquifer groundwater subbasin.</p>
<fig id="fig12" position="float" fig-type="figure"><label>Figure 12</label><caption><p>Estimated groundwater level contours in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for <italic>A</italic>, shallow aquifers (less than 200 feet deep) and <italic>B</italic>, deep aquifers (greater than 200 feet deep) in fall 1994. The Salinas River, Salinas Valley groundwater subbasins, and selected observation wells also are shown.</p><p content-type="toc"><bold>12.</bold>	Maps showing estimated groundwater level contours in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for shallow aquifers and deep aquifers in fall 1994</p></caption><long-desc>12. Lateral groundwater gradients align with the Salinas River channel and decrease northwest toward the coast in both aquifer zones.</long-desc><graphic xlink:href="sac23-0784_fig12"/></fig>
<fig id="fig13" position="float" fig-type="figure"><label>Figure 13</label><caption><p>Observed water levels during the study period for <italic>A</italic>, well BDA331 in the 180/400-Foot Aquifer groundwater subbasin; <italic>B</italic>, well ZES1572 in the East Side Aquifer groundwater subbasin; <italic>C</italic>, ZFS1001 in the Forebay Aquifer groundwater subbasin; and <italic>D</italic>, well ZSE733 in the Upper Valley Aquifer groundwater subbasin in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California. Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18. </p><p content-type="toc"><bold>13.</bold>	Graphs showing observed water levels during the study period for well BDA331 in the 180/400-Foot Aquifer groundwater subbasin, well ZES1572 in the East Side Aquifer groundwater subbasin, ZFS1001 in the Forebay Aquifer groundwater subbasin, and well ZSE733 in the Upper Valley Aquifer groundwater subbasin in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>13. Water levels trend downward during the study period, except in the Upper Valley Aquifer with early drops followed by partial recovery.</long-desc><graphic xlink:href="sac23-0784_fig13"/></fig>
</sec>
<sec>
<title>Groundwater Use and Natural Discharge</title>
<p>The primary sources of groundwater discharge are irrigation and municipal supply wells, evapotranspiration, and discharge to streams. There is a long history of irrigation in the study area, and groundwater is the primary source of water for irrigating agricultural crops and meeting domestic, municipal, and industrial water demands (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>; <xref ref-type="bibr" rid="r23">California Department of Water Resources, 1973</xref>). There is little groundwater outflow to the ocean, but the existing groundwater outflow to the ocean occurs in shallow alluvium along the coast (<xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>). Water also leaves the system through evapotranspiration from native vegetation, urban landscapes, and irrigated agriculture.</p>
<p>To monitor groundwater pumpage throughout the basin, the Groundwater Extraction Management System database was developed in 1994 to comply with MCWRA ordinance 3717. All groundwater withdrawals in the Zone 2C Water Management Area for municipal and industrial (M &amp; I) and agricultural water use in the Salinas Valley are currently reported and maintained in this database (<xref ref-type="bibr" rid="r119">Monterey County Water Resources Agency, 1996</xref>). Before 1994, M &amp; I pumpage was estimated using census data (<xref ref-type="fig" rid="fig14">fig. 14</xref>; <xref ref-type="bibr" rid="r157">U.S. Census Bureau, 2018</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Domestic pumpage is not reported nor directly simulated in this study. However, census-based population estimates in the year 2000 suggest 92 percent of the population is in cities served by reported M &amp; I wells (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Overall, M &amp; I water use is approximately 10&#x2013;15 percent of agricultural pumpage but is important to subregional groundwater budgets (<xref ref-type="fig" rid="fig14">fig. 14</xref>). Monthly agricultural pumpage has been reported since WY 1995 and shows total agricultural pumpage ranges from approximately 379 to 571 TAFY; it is the most substantial use of groundwater within the Salinas Valley.</p>
<fig id="fig14" position="float" fig-type="figure"><label>Figure 14</label><caption><p>Annual total municipal, industrial, and agricultural pumpage in the Zone 2C Water Management Area in Monterey County, California, from water year 1970 to 2018. Pumpage is estimated before 1994 and reported for water years 1995&#x2013;2018.</p><p content-type="toc"><bold>14.</bold>	Graph showing annual total municipal, industrial, and agricultural pumpage in the Zone 2C Water Management Area in Monterey County, California, from water year 1970 to 2018</p></caption><long-desc>14. Total groundwater pumpage includes municipal and industrial as well as agricultural, with agricultural being larger and with more variability.</long-desc><graphic xlink:href="sac23-0784_fig14"/></fig>
</sec>
<sec>
<title>Groundwater Budget</title>
<p>The groundwater system has been under stress since the 1920s, but extensive development of the groundwater system did not begin in earnest until the 1940s and 1950s (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>). In the late 1900s and early 2000s, groundwater pumping accounted for 95 percent of the outflow from the basin, and the remaining loss was from evapotranspiration (<xref ref-type="bibr" rid="r55">Ferriz, 2001</xref>; <xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>). The <xref ref-type="bibr" rid="r19">California Department of Public Works (1946)</xref> estimated groundwater recharge to be approximately 220 TAFY, with negligible regional groundwater flow from the groundwater basins south of San Ardo. At that time, groundwater overdraft was estimated to be about 55 TAFY in the 180-Foot Aquifer. Groundwater modeling and water budget analyses by <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency (1995)</xref> further quantified components of recharge and discharge in the basin. Groundwater recharge was estimated to be 454 TAFY, of which 144 TAFY was agricultural return flows, 244 TAFY was streamflow infiltration, and 66 TAFY was precipitation recharge. Over the same period from 1970 to 1994, average groundwater overdraft basin-wide was 44 TAFY.</p>
</sec>
<sec>
<title>Seawater Intrusion</title>
<p>Substantial pumping in aquifers of the coastal region has caused substantial seawater intrusion and groundwater-level declines that were first documented in the 1930s (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>). The landward extent of seawater intrusion in the 180-Foot and 400-Foot Aquifers is estimated by MCWRA using spatial sampling of chloride concentrations in coastal monitoring wells. Since it was first studied in 1946 (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>), seawater intrusion had advanced nearly 6 mi inland by 1995 and affected the groundwater wells supplying approximately 20,000 acres of coastal farmland (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Chloride concentrations of greater than 500 mg/L in those wells indicated that groundwater was impaired in approximately 20,000 acres of the 180-Foot Aquifer and 10,000 acres of the 400-Foot Aquifer (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). An analogue for evaluating seawater intrusion is seawater coastal inflow, which is the aquifer freshwater volume displaced by seawater intrusion. In 1946, an estimated 6&#x2013;12 TAFY annual seawater coastal inflow occurred. When estimated in 1995, the average annual seawater coastal inflow from 1970 to 1992 was 15 TAFY.</p>
</sec>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.IntegratedHydrologicandOperationalModelDevelo">
<title>Integrated Hydrologic and Operational Model Development</title>
<p>The integrated hydrologic and operational models were developed to support analysis of groundwater and surface-water availability and use, quantify regional groundwater flow among groundwater subbasins, and examine current and proposed operational schemes for managing reservoir and water supply projects. The SVIHM, referred to herein as the &#x201C;historical model,&#x201D; simulates historical conditions for groundwater levels and hydrologic budgets. The SVOM, referred to herein as the &#x201C;operational model,&#x201D; simulates the engineered surface-water and reservoir operations for two reservoirs. This operational model implements current reservoir operations and uses 2014 fixed land use and current water supply projects with observed historical climate records to provide baseline information for project benefit analyses and evaluation of water supply projects and reservoir operations. The historical and operational models are referred to together herein as the &#x201C;integrated hydrologic models.&#x201D; The integrated hydrologic models represent aquifers and confining units using hydrogeologic units and spatially distributed estimates of sediment texture from the SVGF (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>). Monthly surface-water inflows (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>) into the integrated hydrologic model domain were simulated using the SVWM, herein referred to as the &#x201C;watershed model,&#x201D; that is documented by <xref ref-type="bibr" rid="r96">Hevesi and others (2025a</xref>, <xref ref-type="bibr" rid="r97">b</xref>).</p>
<p>The focus of this report is the development of inputs and calibration of the integrated hydrologic models. The historical model parameter estimation is used to define properties that are then used in the operational model (discussed in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.SalinasValleyOperationalModel">Salinas Valley Operational Model</xref>&#x201D; section). The integrated hydrologic models share many model files and are explained together. Differences among the integrated hydrologic models are noted using the specific model&#x2019;s name where relevant; otherwise, the same description of model construction applies to both models. The integrated hydrologic models simulate transient conditions dependent on the interactions among head-and-flow-dependent components of hydrologic processes simulated in the model, including engineered systems and management constraints on operations and water availability. The integrated hydrologic models were developed to analyze conjunctive water use and the movement of water throughout the landscape, including the surface-water drainage network and aquifers. The integrated hydrologic models simulate water budgets, changes in groundwater storage and related seawater coastal inflow (an analogue for seawater intrusion), and agricultural, municipal, and industrial water demands in different hydrologic regions of Salinas Valley, California.</p>
<p>The integrated hydrologic models are supported by a watershed model documented by <xref ref-type="bibr" rid="r96">Hevesi and others (2025a</xref>, <xref ref-type="bibr" rid="r97">b</xref>). The integrated hydrologic models have a smaller footprint than the watershed model and are geographically focused near the Zone 2C Water Management Area and associated groundwater basins of the Salinas Valley (<xref ref-type="fig" rid="fig02">fig. 2</xref>). Specifically, the watershed model provides basin-wide estimates of monthly watershed inflows for ungaged streams and tributaries that flow into the integrated hydrologic model area from the watershed outside of the active simulation area (<xref ref-type="fig" rid="fig02">fig. 2</xref>). The watershed model was built using the Hydrologic Simulation Program-FORTRAN (<xref ref-type="bibr" rid="r8">Bicknell and others, 1997</xref>), and the model simulates the period from October 1, 1948, to September 30, 2018. This period encompasses several years before the Lake Nacimiento reservoir was built through WY 2018. The watershed and integrated hydrologic models use the same regional climate input (<xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>) and surface-water drainage network (<xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>).</p>
<sec>
<title>Simulation Code</title>
<p>The integrated hydrologic models were built using MODFLOW-One-Water Hydrologic Flow Model version 2.3 (MF-OWHM; <xref ref-type="bibr" rid="r72">Hanson and others, 2014a</xref>; <xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>; <xref ref-type="bibr" rid="r10">Boyce, 2023</xref>) with the latest version of the MODFLOW package called the Farm Process (FMP). The MF-OWHM is a MODFLOW-2005-based integrated hydrologic model designed to dynamically simulate the conjunctive use of surface water and groundwater to meet agricultural demands (<xref ref-type="bibr" rid="r72">Hanson and others, 2014a</xref>; <xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>). The term &#x201C;integrated&#x201D; refers to the tight coupling of groundwater flow, surface-water flow, reservoir operations, and landscape processes, such as agricultural management and evapotranspiration. Within the active integrated hydrologic model domain (<xref ref-type="fig" rid="fig02">fig. 2</xref>), surface and subsurface hydrologic processes, operations, and water use constraints are simulated simultaneously, allowing for consideration of conjunctive-use, water-management, water-food-security, and climate-crop-water scenarios in the Salinas Valley. The FMP simulates a land-use-based water supply and demand framework and specifies a water balance subregion (WBS) as a subarea of the model domain. Within each WBS, quantities of interest for agricultural water supply management are computed, such as the total delivery requirement (TDR) to meet agricultural demands, total applied water (TAW), surface-water and groundwater supply, and excess applied irrigation water. These quantities of interest for agricultural water supply management depend on simulated head- and flow-dependent inflows and outflows. For example, direct uptake of groundwater to meet crop demands can occur when simulated water levels are above the bottom of the root zone, which reduces the amount of water required to be diverted or pumped to meet land use water demands. The FMP simulates the operational and water allocation constraints on water resources available to each WBS. For example, the water available for diversions or volume and timing of reservoir releases could be dependent on flow constraints in designated locations and times of the year. These constraints guide the simulation of the conjunctive use of groundwater and surface water to meet agricultural demands. A full list of the processes and packages of MF-OWHM used in the integrated hydrologic models are provided in <xref ref-type="table" rid="t01">table 1</xref>.</p>
<table-wrap id="t01" position="float"><label>Table 1</label><caption>
<title>Summary of MODFLOW-One Water Hydrologic Model (MF-OWHM) packages and processes used in the Salinas Valley Integrated Hydrologic Model and Salinas Valley Operational Model.</title>
<p content-type="toc"><bold>1.</bold>	Summary of MODFLOW-One Water Hydrologic Model packages and processes used in the Salinas Valley Integrated Hydrologic Model and Salinas Valley Operational Model</p></caption>
<table rules="groups">
<col width="29.66%"/>
<col width="53.02%"/>
<col width="17.32%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Computer program (packages, processes, parameter estimation)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Function</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Reference</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">Processes and solvers</th>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="rowgroup">Farm process (FMP)</td>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Set up and solve equations simulating use and movement of water on the landscape as irrigated agriculture, urban landscape, and natural vegetation.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r142">Schmid and Hanson (2009)</xref></td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="col"><xref ref-type="bibr" rid="r9">Boyce and others (2020)</xref></td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Surface-water operations (SWO)</td>
<td valign="top" align="left">Subpackage of FMP that simulates the reservoir storage, releases, and operations for the operational model.</td>
<td valign="top" align="left"><xref ref-type="bibr" rid="r87">Henson and others (2023)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Groundwater Flow (GWF) processes of MODFLOW model</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Set up and solve equations simulating a basic groundwater flow model.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Preconditioned conjugate-gradient with improved nonlinear control (PCGN)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Solves groundwater flow equations; requires convergence of heads and (or) flow rates.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Discretization</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Basic package (BAS6)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Defines the initial conditions and some of the boundary conditions of the model.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Discretization package (DIS)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Space and time information.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Boundary conditions</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Streamflow routing (SFR2)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Simulates the routed streamflow, infiltration, exfiltration, runoff, and return flows from FMP.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r133">Niswonger and Prudic (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" scope="row">General head boundaries (GHB)</td>
<td valign="top" align="left">Head-dependent boundary condition used along the edge of the model to allow groundwater to flow into or out of the model under a regional gradient.</td>
<td valign="top" align="left"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Multi-node wells (MNW2)</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Simulates pumpage from wells with screens that span multiple layers.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r108">Konikow and others (2009)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Drain return package (DRT)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Simulates drain boundary condition and routes drain flows to streams.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Aquifer parameters</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Layer property flow package (LPF)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Calculates the hydraulic conductance between cell centers.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Hydrologic flow barriers (HFB6)</td>
<td valign="top" align="left">Simulates a groundwater barrier by defining a hydraulic conductance between two adjacent cells in the same layer.</td>
<td valign="top" align="left"><xref ref-type="bibr" rid="r101">Hsieh and Freckelton (1993)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Multiplier package (MULT)</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Defines multiplier arrays for calculation of model-layer characteristics from parameter values.</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Zones (ZONE)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Defines arrays of different zones. Parameters may be composed of one or many zones.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Output and observations</th>
</tr>
<tr>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="rowgroup">Head observation (HOB)</td>
<td rowspan="2" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Defines the head observation and weight by layer(s), row, column, and time and generates simulated values for comparison with observed values.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r99">Hill and others (2000)</xref></td>
</tr>
<tr>
<td valign="top" colspan="1" align="left" style="background-color:rgb(217,217,217)" scope="col"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Hydmod (HYD)</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Generates simulated values for specified locations at each time step for groundwater levels and streamflow attributes.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt"><xref ref-type="bibr" rid="r73">Hanson and Leake (1999)</xref></td>
</tr>
<tr>
<th colspan="3" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Files</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Name file (name)</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Controls the capabilities of MODFLOW One Water Hydrologic Model used during a simulation. Lists most of the files used in the model, observations, and FMP processes.</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Output control option (OC)</td>
<td valign="top" align="left">Used in conjunction with flags in other packages for output head, drawdown, and budget information for specified time periods into separate files.</td>
<td valign="top" align="left"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">List file</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Output file for allocation information, values used by the GWF, and calculated results, such as head, drawdown, and the water budget.</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)"><xref ref-type="bibr" rid="r80">Harbaugh (2005)</xref></td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Discretization</title>
<p>The study area is shown on <xref ref-type="fig" rid="fig01">figure 1</xref>. The study area contains a watershed model domain that represents the Salinas River watershed (<xref ref-type="fig" rid="fig01">fig. 1</xref>) and an integrated hydrologic model domain that simulates the Salinas Valley and Salinas River within the surrounding Salinas Valley groundwater basins, as well as Lake San Antonio and Lake Nacimiento reservoirs (<xref ref-type="fig" rid="fig02">fig. 2</xref>). The active integrated hydrologic model domain completely contains the current Salinas Valley groundwater sustainability management area (<xref ref-type="fig" rid="fig02">fig. 2</xref>; <xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>).</p>
<sec>
<title>Temporal Discretization</title>
<p>The total simulation period for the integrated hydrologic models was from October 1, 1967, to September 30, 2018. The 51-year simulation period encompasses the period just after the construction of the second reservoir in the integrated hydrologic model area, Lake San Antonio, to the recent period. To better represent the dynamics of the changing climate, streamflow, and growing season (irrigation supply and demand components), the integrated hydrologic models are discretized into 612 monthly stress periods to reflect the common frequency of some of the reported data, such as groundwater pumpage. A model stress period is an interval of time in which the user-specified inflows and outflows are held constant, and time steps are units for which groundwater levels and flows are calculated throughout all model cells (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>). We discretize monthly aquifer stresses into input for each stress period. The historical model has two equal-length, semi-monthly time steps (approximately 15 days) for each monthly stress period. Semi-monthly time steps are commonly used in regional scale historical models that include agriculture (<xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>; <xref ref-type="bibr" rid="r75">Hanson and others, 2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>). To represent reservoir operations, the operational model has a smaller time step than the historical model. For each monthly operational model stress period, a model time step of 5 or 6 days is used for the temporal discretization of the operational model to account for the approximately 5-day transit time for reservoir releases through the integrated hydrologic model area (Howard Franklin, Monterey County Water Resources Agency, oral commun., 2018) and to comply with steelhead fish passage requirements specified in the National Oceanic and Atmospheric Administration&#x2019;s National Marine Fisheries Service&#x2019;s biological opinion <xref ref-type="bibr" rid="r130">(National Marine Fisheries Service, 2007)</xref>.</p>
</sec>
<sec>
<title>Spatial Discretization and Layering</title>
<p>The integrated hydrologic model area encompasses the Salinas Valley groundwater basin and its offshore extent (<xref ref-type="fig" rid="fig02">fig. 2</xref>). The total active modeled area is 957 mi<sup>2</sup>. The top of the integrated hydrologic models is represented by the elevation of the land surface. The finite-difference model grid used to represent the land surface and subsurface deposits consists of a series of orthogonal 530-ft (6.46-acre) square model cells of variable thickness. Spatial discretization was held constant through time. There are 976 rows, 272 columns, and 9 layers that have a varying number of active cells in each layer, for a total of 589,720 active model cells. Active model cells within the model grid are defined using the IBOUND parameter in the MODFLOW basic package. Where model cells are active, the IBOUND parameter is set to a value greater than 0. The uppermost active model cell could be within model layers one, three, five, seven, eight, and nine. Where hydrogeologic units pinch out, a &#x201C;pinched&#x201D; cell type was defined to transmit water between layers. Where confined hydrogeologic units are not present, the layer is specified as an approximately 1-ft thick layer. Based on the Salinas Valley Geologic Framework (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>), the nine model layers were defined to represent each of the nine hydrogeologic units of the regional aquifer system: three confining units&#x2014;upper (layer 2), middle (layer 4), and lower (layer 6), and six aquifers&#x2014;surficial aquifer (layer 1), 180-Foot Aquifer (layer 3), 400-Foot Aquifer (layer 5), Paso Robles Formation (layer 7), Purisima Formation (layer 8), and basement aquifer (layer 9). These hydrogeologic units are further described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.GeologicFramework">Geologic Framework</xref>&#x201D; section of this report.</p>
</sec>
<sec>
<title>Analysis Regions</title>
<p>All historical model results and hydrologic budgets are discussed for five analysis regions and the integrated hydrologic model domain. The five analysis regions represent the riparian area that includes the Salinas River and the four primary water-producing subareas of the Zone 2C Water Management Area (<xref ref-type="fig" rid="fig15">fig. 15</xref>). The five analysis regions are the Riparian, Pressure, East Side-Langley, Forebay, and Upper Valley. The analysis regions are aligned with Salinas Valley groundwater subbasins shown on <xref ref-type="fig" rid="fig11">figure 11</xref>. <xref ref-type="table" rid="t02">Table 2</xref> shows the relationship between analysis regions, Salinas Valley groundwater subbasins, named subareas, and water balance subregions, as implemented in the integrated hydrologic models.</p>
<fig id="fig15" position="float" fig-type="figure"><label>Figure 15</label><caption><p>Analysis regions and other areas that are simulated within the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California.</p><p content-type="toc"><bold>15.</bold>	Map showing analysis regions and other areas that are simulated within the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>15. The Upper Valley, Forebay, and Pressure and East Side-Langley regions span the upper, middle, and lower thirds of the valley, respectively.</long-desc><graphic xlink:href="sac23-0784_fig15"/></fig>
<table-wrap id="t02" orientation="landscape" position="float"><label>Table 2</label><caption>
<title>Summary of analysis regions, Salinas Valley groundwater subbasins, named subareas, water-balance subregions, and their available water sources to meet demands.</title>
<p content-type="toc"><bold>2.</bold>	Summary of analysis regions, Salinas Valley groundwater subbasins, named subareas, water-balance subregions, and their available water sources to meet demands</p>
<p>[&#x2014;, no data]</p></caption>
<table rules="groups">
<col width="8.12%"/>
<col width="12.59%"/>
<col width="13.67%"/>
<col width="11.02%"/>
<col width="37.97%"/>
<col width="16.63%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis region</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Salinas Valley groundwater subbasin</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water balance subregion</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Water balance subregion identifier</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Region description</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Simulated water supply</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Riparian</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Riparian Corridor</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Monterey and San Luis Obispo Counties</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pressure</td>
<td valign="top" align="left">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left">Castroville Seawater Intrusion Project area</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="left">Area receiving water from Castroville Seawater Intrusion Project</td>
<td valign="top" align="left">Root zone, surface water, groundwater, recycled water</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Pressure</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Coastal Urban areas</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Areas containing cities of Salinas, Castroville, Marina, Seaside, Sand City, Monterey, and Del Rey Oaks</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, municipal groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="left">Forebay Aquifer</td>
<td valign="top" align="left">Inland Urban areas</td>
<td valign="top" align="char" char=".">4</td>
<td valign="top" align="left">Areas containing Cities of Chualar, Gonzales, Soledad, Greenfield, King City, and San Ardo</td>
<td valign="top" align="left">Root zone, municipal groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Highlands South</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Northwest of East Side analysis region outside of Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">East Side</td>
<td valign="top" align="left">Langley Area</td>
<td valign="top" align="left">Granite Ridge</td>
<td valign="top" align="char" char=".">6</td>
<td valign="top" align="left">Northwest of East Side analysis region outside of Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Monterey</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Corral De Tierra</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">South of Pressure analysis region within Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pressure</td>
<td valign="top" align="left">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left">Blanco Drain Area</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="left">Drain subarea within Pressure subarea of Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">East Side</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">East Side Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">East Side</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Remainder of East Side subarea in Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pressure</td>
<td valign="top" align="left">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left">Pressure Northeast</td>
<td valign="top" align="char" char=".">10</td>
<td valign="top" align="left">Pressure subarea northeast of Salinas River in Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Pressure</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">180-Foot/400-Foot Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Pressure Southwest</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Pressure subarea southwest of Salinas River in Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="left">Forebay Aquifer</td>
<td valign="top" align="left">Forebay Northeast</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="left">Forebay subarea northeast of Salinas River in Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Forebay</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Forebay Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Forebay Southwest</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">13</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Forebay subarea southwest of Salinas River in Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="left">Forebay Aquifer</td>
<td valign="top" align="left">Arroyo Seco</td>
<td valign="top" align="char" char=".">14</td>
<td valign="top" align="left">Subarea southwest of Salinas River outside of Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Forebay</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Forebay Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Clark Colony</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">15</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Subarea southwest of Salinas River partly outside of Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, surface water, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Upper Valley</td>
<td valign="top" align="left">Upper Valley Aquifer</td>
<td valign="top" align="left">Upper Valley Northeast</td>
<td valign="top" align="char" char=".">16</td>
<td valign="top" align="left">Upper Valley subarea northeast of Salinas River and northeast of King City in Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Upper Valley</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley Northwest</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley subarea northwest of Salinas River and west of King City in Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Upper Valley</td>
<td valign="top" align="left">Upper Valley Aquifer</td>
<td valign="top" align="left">Upper Valley Southeast</td>
<td valign="top" align="char" char=".">18</td>
<td valign="top" align="left">Upper Valley subarea southeast of Salinas River and east of King City in Zone 2C</td>
<td valign="top" align="left">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Upper Valley</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley Southwest</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">19</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Valley subarea southwest of Salinas River and west of King City in Zone 2C</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Below Dam</td>
<td valign="top" align="left">Upper Valley Aquifer</td>
<td valign="top" align="left">Below Dam</td>
<td valign="top" align="char" char=".">20</td>
<td valign="top" align="left">Subregion below Nacimiento Dam and within Zone 2C</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Forebay Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Westside Region</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">21</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Westside regions of model domain outside of Zone 2C boundary in Monterey County, inland and southwest of Arroyo Seco and Clark Colony subregion</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone, groundwater</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Outside</td>
<td valign="top" align="left">Upper Valley Aquifer</td>
<td valign="top" align="left">Hames Valley</td>
<td valign="top" align="char" char=".">22</td>
<td valign="top" align="left">Outside Zone 2C but in Monterey County</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">East Side Aquifer</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Northeast Quarries</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Outside Zone 2C but in Monterey County</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Outside</td>
<td valign="top" align="left">&#x2014;</td>
<td valign="top" align="left">Northeast Region</td>
<td valign="top" align="char" char=".">24</td>
<td valign="top" align="left">Northeast regions of model domain outside of Zone 2C on the northeast side of the East Side, Granite Ridge, and Highlands South subregions</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Southwest Region</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">25</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Southwest regions of model domain outside of Coastal Pressure subregion Zone 2C boundary in Monterey County</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Outside</td>
<td valign="top" align="left">&#x2014;</td>
<td valign="top" align="left">Northeast Region</td>
<td valign="top" align="char" char=".">26</td>
<td valign="top" align="left">Northeast region of model domain outside of Zone 2C Forebay subregion in Monterey County</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Southwest Region</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Southwest regions of model domain outside of the Upper Valley and Forebay subregions of Zone 2C in Monterey County and outside of Arroyo Seco, Hames Valley, and San Luis Obispo County active subregions</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Outside</td>
<td valign="top" align="left">&#x2014;</td>
<td valign="top" align="left">Southeast Region</td>
<td valign="top" align="char" char=".">28</td>
<td valign="top" align="left">Southeast region of model domain outside of Below Dam and Upper Valley subregions of Zone2C boundary in Monterey County</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Outside</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Paso Robles Area</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Paso Robles</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">29</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Portion of active model grid located in San Luis Obispo County</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Seaside</td>
<td valign="top" align="left">&#x2014;</td>
<td valign="top" align="left">Seaside Basin</td>
<td valign="top" align="char" char=".">30</td>
<td valign="top" align="left">Seaside adjudicated basin not included in analysis due to adjudication</td>
<td valign="top" align="left">Root zone</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Offshore</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Offshore</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">31</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Offshore region used to support analysis of seawater-aquifer exchanges</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">None</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The five analysis regions (<xref ref-type="fig" rid="fig15">fig. 15</xref>) represent nearly the entire integrated hydrologic model area (93 percent of Zone 2C Water Management Area and 74 percent of the onshore study area; <xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>). The analysis regions account for more than 98 percent of reported groundwater usage within the Zone 2C Water Management Area recorded in the Groundwater Extraction Management System (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). There are other regions within the integrated hydrologic model domain that are hydrologically connected but outside of the analysis regions (<xref ref-type="fig" rid="fig15">fig. 15</xref>). These other areas include the area outside of analysis regions but within the integrated hydrologic model domain: the separately adjudicated Seaside groundwater subbasin (Seaside), the area below Lakes Nacimiento and San Antonio (Below dam), the area outside of Zone 2C Water Management Area (Outside Zone 2C), and the offshore region (offshore).</p>
</sec>
<sec>
<title>Water Balance Subregions</title>
<p>The FMP in MF-OWHM was used to define the landscape processes in the integrated hydrologic model area using WBSs. These WBSs are used to represent analysis regions (<xref ref-type="fig" rid="fig15">fig. 15</xref>), named subareas, and other areas that are within the integrated hydrologic model domain (<xref ref-type="fig" rid="fig16">fig. 16</xref>; <xref ref-type="table" rid="t02">table 2</xref>). Each analysis region comprises one or more WBSs. Results are aggregated for each analysis region from its associated WBS. Each WBS represents an area on the model&#x2019;s surface that has common water use properties, crop properties, water supply, and runoff and recharge characteristics. Within each WBS, water supply and demand calculations are made, deliveries from connected water sources (for example, groundwater; <xref ref-type="table" rid="t02">table 2</xref>) are applied to meet demands, and recharge and runoff are simulated. The integrated hydrologic models are discretized into 31 WBSs (<xref ref-type="fig" rid="fig16">fig. 16</xref>) to better associate the location of water demands with the location of water sources used to satisfy them. This approach ensures that groundwater pumpage from one side of the river is not used to meet crop demands on the other side of the river. The Salinas River riparian area was delineated as a separate WBS, WBS 1, so that net groundwater regional groundwater flow and water balances within the Salinas River riparian area could be specifically evaluated. Some WBS were delineated to represent specific named subareas within the Salinas Valley, including the area for the CSIP (<xref ref-type="fig" rid="fig01">fig. 1</xref>), the area around Arroyo Seco in the Forebay analysis region, and Clark Colony (<xref ref-type="table" rid="t02">table 2</xref>). Although the extent and number of WBSs defined in this version of the models are held constant, the model input for WBSs can be adjusted by users to vary the extent and number of WBSs through time (<xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>). This flexibility presents opportunities to specifically delineate changes in future model efforts for areas of interest, such as growing urban centers. The delineation of multiple WBSs throughout the integrated hydrologic model domain can support refined analyses of water supply projects in the future. In analyses in this report, WBS landscape and groundwater budgets are aggregated to their associated analysis regions and the integrated hydrologic model domain. However, in the model output, landscape and groundwater budgets are output for each WBS.</p>
<fig id="fig16" position="float" fig-type="figure"><label>Figure 16</label><caption><p>Thirty-one water balance subregions of the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California.</p><p content-type="toc"><bold>16.</bold>	Map showing 31 water balance subregions of the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>16. Most water balance subregions are continuous and confined to the south side of the Salinas River.</long-desc><graphic xlink:href="sac23-0784_fig16"/></fig>
</sec>
</sec>
<sec>
<title>Landscape</title>
<p>The FMP provides coupled simulation of the groundwater and surface-water components of the hydrologic cycle and managed flows and operations by water managers for irrigated and non-irrigated lands (for example, native vegetation). The FMP estimates water demands and allocates water supply, simulates runoff and recharge, simulates groundwater evapotranspiration, and computes surface-water deliveries and groundwater pumpage for agricultural supply for each WBS in the active model domain. The FMP has a demand-driven and supply-constrained representation of the landscape. The FMP utilizes land use and water demands to partition precipitation and groundwater and surface-water deliveries into evapotranspiration, runoff, and recharge.</p>
<sec id="sac23-0784_Final_20260508_kc.FarmProcessOverview">
<title>Farm Process Overview</title>
<p>Within each model cell for each WBS, FMP estimates landscape consumptive use as uptake and transpiration by plants and the associated evaporation. For each land use category in every active model cell, a landscape consumptive use of water is estimated based on a modified United Nations Food and Agriculture Organization method (<xref ref-type="bibr" rid="r1">Allen and others, 1998</xref>) that has been applied widely throughout California (<xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>; <xref ref-type="bibr" rid="r75">Hanson and others, 2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>). A summary of FMP landscape consumptive use and water demand simulation is provided here; a complete explanation of the method is provided by <xref ref-type="bibr" rid="r9">Boyce and others (2020)</xref>.</p>
<sec>
<title>Input Parameters</title>
<p>The landscape consumptive use for every model stress period is computed using (1) reference evapotranspiration (ETref) for each model cell that is approximated using PET, (2) a seasonally varying crop coefficient (Kc), which is a scalar value that is multiplied by ETref to estimate a landscape consumptive use, (3) specification of the fraction of the maximum leaf area in each cell (that is, fraction of transpiration; FTR) and fractions representing the remainder of the area subject to evaporation from precipitation (FEP) and irrigation (FEI), and (4) the land use area.</p>
<p>The ETref is a reference value that assumes a well-watered grass surface and is used for landscape consumptive use calculation. The Kc value represents a stage of crop growth and associated landscape consumptive use. The FTR represents the fraction of land use &#x201C;leaf area&#x201D; in each model cell where plant transpiration occurs and varies between 0 and 1. The FTR is assumed to be independent of whether the transpiratory portion of landscape consumptive use is satisfied by irrigation, precipitation, or groundwater uptake. The remaining fraction (1&#x2212;FTR) of each cell is assumed to represent FEP and FEI. The FEP represents the fraction of the land use area over which evaporation occurs and is calculated internally by FMP as 1&#x2212;FTR. The FEI can be conceptualized as the irrigated area that is not planted, such as the irrigated area between plants or planting beds. FEI is specified as a fraction less than or equal to FEP. The FTRs vary linearly with the respective area occupied by crops and the area open to soil evaporation (<xref ref-type="bibr" rid="r143">Schmid and others, 2006</xref>). FTR or FEP and FEI depends strongly on the type of land use and the associated crop growth stage. When the vegetation cover approaches 100 percent, FTR=1 and FEP and FEI=0. As a result, the fractions of transpiration and evaporation vary by land use type for different months of the year.</p>
</sec>
<sec>
<title>Landscape Consumptive Use</title>
<p>The landscape consumptive use is the sum of transpiration and evaporation consumptive use. The transpiration consumptive use by plants is estimated based on FTR, ETref, and Kc parameters. The transpiration consumptive use is computed as ETref multiplied by each land use area and Kc in each cell. The transpiration consumptive use is then prorated by the monthly FTR for each land use type. The evaporative consumptive use is computed using the FEP and FEI parameters that are multiplied by the volumes of precipitation and irrigation that are applied to each cell. The consumptive use due to transpiration and evaporation are summed to estimate a landscape consumptive use in each model cell.</p>
</sec>
<sec>
<title>Water Demands</title>
<p>In FMP, landscape consumptive uses can be satisfied from natural sources, such as precipitation and direct uptake from shallow groundwater above a specified rooting depth. If natural sources of water are not available to meet the calculated landscape consumptive use for a WBS, a TDR is computed. For each model time step, FMP determines a residual of total landscape consumptive use that cannot be satisfied by natural sources&#x2014;the TDR. For irrigated land uses, this residual water demand is increased using an on-farm efficiency factor (OFE) to account for crop, WBS-specific, and irrigation-type inefficiency losses to estimate the amount that must be supplied to meet demand. Available supplies are used to meet the TDR for the WBSs. The TAW represents the amount of water applied to meet land use water demands. In the integrated hydrologic models, the deficit-irrigation scenario is used; when demand cannot be satisfied with available supplies for a WBS, demand is reduced to the supply, and the deficit is shared among all land uses in the WBS. If the irrigated water demand cannot be satisfied with available water supply, then the TAW will be less than the TDR. Due to the prevalence of groundwater wells with substantial pumping capacity throughout the study area, this deficit irrigation scenario is unlikely to occur under current conditions. If constraints were placed on well pumpage in future simulations, this deficit scenario would affect the calculation of demands. More details for how the FMP accounts for inflows and outflows for each WBS are available in the MF-OWHM documentation (<xref ref-type="bibr" rid="r143">Schmid and others, 2006</xref>; <xref ref-type="bibr" rid="r142">Schmid and Hanson, 2009</xref>; <xref ref-type="bibr" rid="r72">Hanson and others, 2014a</xref>; <xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>).</p>
</sec>
<sec>
<title>Water Supply</title>
<p>The TDR in irrigated lands can be satisfied by additional water supplies, such as semi-routed surface-water deliveries from streams or canals (diversions), reservoir releases, non-routed delivery from external sources (for example, wastewater reclamation or pipelines), or groundwater pumpage by wells. Where the conjunctive use of surface water and groundwater are major sources of water used for irrigation, FMP attempts to satisfy the TDR by using surface-water diversions or non-routed deliveries (such as pipelines and recycled water) first, with residual water demand satisfied by groundwater. Surface-water deliveries can be limited to a specified allocation (surface-water allotments) to the agricultural WBSs that use both surface water and groundwater (<xref ref-type="bibr" rid="r75">Hanson and others, 2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>). If diverted flows to a WBS through a semi-routed delivery are more than land use water demands, diverted surface water is returned to the surface-water drainage network for potential reuse downstream. For each WBS, the FMP computes the collective potential pumping capacity of all wells that can provide groundwater for supplemental irrigation water. The residual water demand is distributed to every well in the WBS, and all active wells are pumped. The volume of groundwater pumpage is only limited by well capacity and any imposed volumetric constraints specified using groundwater allotments.</p>
</sec>
<sec>
<title>Runoff and Recharge</title>
<p>Runoff and recharge from each WBS are partitioned based on a specified fraction of excess water after all demands have been satisfied. Runoff is routed on a segment-length weighted basis to all streams within a WBS. Recharge results from excess irrigation and excess precipitation, reduced by losses to surface-water runoff and evapotranspiration from groundwater (<xref ref-type="bibr" rid="r143">Schmid and others, 2006</xref>). The evapotranspiration from groundwater is subtracted from the potential net downward flux as deep percolation to the uppermost aquifer. Hence, recharge to groundwater can be affected both by user-specified and head-dependent processes. This definition of recharge requires the following assumptions: deep percolation below the active root zone is equal to groundwater recharge; evapotranspiration from groundwater equals an instantaneous outflow from aquifer storage in any time step; and the net change in soil-moisture storage for irrigated, well-managed agricultural areas for periods of weeks to months is negligible (<xref ref-type="bibr" rid="r143">Schmid and others, 2006</xref>). The recharge to the aquifers is applied on a cell-by-cell basis to the uppermost active model cell in each WBS. Recharge is computed after evapotranspiration consumption losses. Therefore, recharge can be negative if groundwater evapotranspiration is greater than deep percolation. When negative recharge occurs, it is constrained to specific areas. For example, in the model cells near the stream in the Riparian analysis region, the amount of groundwater evapotranspiration from riparian vegetation may be higher than the amount of deep percolation into those cells, resulting in a negative recharge value; however, stream leakage is also occurring in those cells. Therefore, the recharge may be negative, but the total recharge (stream leakage plus recharge) is positive.</p>
</sec>
<sec>
<title>Surface-Water Operations</title>
<p>The FMP also includes a surface-water operations (SWO) module that allows for simulation of large-scale surface-water storage and distribution systems&#x2014;including simulation of surface-water storage, allocation, release, and distribution&#x2014;to meet agricultural, municipal, and industrial water demand, maintain a minimum streamflow requirement, and reserve a portion of storage for flood protection. This additional functionality facilitates improved analysis of basin-scale conjunctive use and large-scale surface-water management. To simulate two-way interactions and feedback between surface-water and groundwater management and use, SWO interacts with the Stream Flow Routing Package (SFR2; <xref ref-type="bibr" rid="r133">Niswonger and Prudic, 2005</xref>) and with the FMP. Reservoir dynamics are simulated using SWO by simulating surface-water storage, management objectives, allocation, and reservoir release. Reservoir dynamics using SWO determines downstream diversion amounts and makes reservoir releases as inflow to SFR2 that routes flow through a surface-water drainage network to simulate distribution. Then SFR2 calculates the associated groundwater/surface-water interaction. The appropriate reservoir releases and downstream diversion amounts are determined by SWO based on the surface-water conveyance calculated from SFR2. Reservoirs simulated by SWO can provide supply to FMP WBSs. Each connected WBS has a computed water demand, and SWO can deliver the appropriate water based on allocation, storage, and SFR2 stream gains and losses.</p>
<p>SWO was developed to allow analysis of the complete feedback cycle between surface-water and groundwater management and use, including effects of groundwater management and use on reservoir storage, allocation, and releases and corresponding effects of surface-water management on groundwater recharge and demand. SWO can be used to evaluate how changes in groundwater pumping affect surface-water management, including storage, allocation, release, and distribution of surface-water supplies. Notably, SWO also allows for analysis of how changes in surface-water management affect groundwater recharge via stream leakage and deep percolation of applied water and thus how surface-water management affects groundwater storage and movement. SWO further allows for analysis of how changes in surface-water management affect groundwater demand and use due to changes in surface-water allocations and deliveries, thus providing for complete two-way interactions between groundwater and surface-water management and use.</p>
</sec>
</sec>
<sec>
<title>Climate Data</title>
<p>For the Salinas River watershed, high-resolution, 270-meter (m) gridded maps of daily precipitation, daily maximum and minimum air temperature, and daily PET were developed (<xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>). These regional climate input data were derived using methods from a regional-scale Basin Characterization Model developed for the State of California (<xref ref-type="bibr" rid="r56">Flint and Flint, 2007</xref>, <xref ref-type="bibr" rid="r57">2012</xref>; <xref ref-type="bibr" rid="r58">Flint and others, 2021</xref>). Climate input data were developed using the gradient-inverse-distance-squared method (<xref ref-type="bibr" rid="r128">Nalder and Wein, 1998</xref>), and daily climate records from a network of 155 climate stations were used to spatially interpolate daily precipitation and maximum and minimum daily air temperature onto a 270-m digital elevation model (DEM) grid (<xref ref-type="bibr" rid="r162">U.S. Geological Survey, 2013</xref>). The gridded daily and PET maps are inputs into the watershed model. These same gridded climate datasets were also used as input for the FMP in the integrated hydrologic models. However, because the model&#x2019;s stress periods are monthly, the daily climate input data were averaged to monthly values and assigned to each of the model cells in the integrated hydrologic models using an area-weighted approach. The complete description of the development of climate datasets is provided with the regional climate data (uniform grid with 270-m resolution; <xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>) and monthly climate data (uniform grid with 530-ft resolution; <xref ref-type="bibr" rid="r89">Henson and others, 2022c</xref>).</p>
<sec>
<title>Reference Evapotranspiration</title>
<p>There are two related measures that describe the potential for evapotranspiration, ETref and PET. The ETref is a reference value that assumes a well-watered grass surface and is used for crop demand calculation. The PET is the total potential for evaporation from a surface if evaporation is not limited by water availability (<xref ref-type="bibr" rid="r1">Allen and others, 1998</xref>). The two quantities are related, but PET values may be higher seasonally. For all locations within the integrated hydrologic model area, the average annual ETref rate, calculated by CIMIS, exceeds average annual precipitation (<xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>; <xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>). The highest ETref rates of 53&#x2013;62 in. per year occur in the lowlands that define the valley floor in the central and southern parts of the integrated hydrologic model domain (<xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>). Mean monthly ETref rates for these locations vary from 1 to 1.5 in. for December and from 8 to 9 in. for July (<xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>).</p>
<p>The ETref values in the integrated hydrologic models are estimated using adjusted PET, as described here. Measured field-scale ETref from <xref ref-type="bibr" rid="r30">California Irrigation Management Information System (2020)</xref> was compared to 270-m resolution PET (<xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>) at CIMIS stations within the study area (<xref ref-type="fig" rid="fig03">figs. 3</xref>, <xref ref-type="fig" rid="fig05">5</xref>). These 270-m climate data were mapped using an area-weighted approach to the uniform 530-ft model grid. Comparison of WY-averaged ETref and PET for stations in the study area that have long-term records (greater than 9 years) show reasonable correspondence, with an <italic>R</italic><sup>2</sup> value of 0.897 (<xref ref-type="fig" rid="fig17">fig. 17<italic>A</italic></xref>; <xref ref-type="bibr" rid="r140">Python Software Foundation, 2021</xref>). Regressions for all stations did not have good correlation, so only long-term stations with records greater than 9 years were evaluated. The time series of values at stations with long records were further evaluated at these stations: Castroville (CIMIS 019, <xref ref-type="fig" rid="fig17">fig. 17<italic>B</italic></xref>), Arroyo Seco (CIMIS 114, <xref ref-type="fig" rid="fig17">fig. 17<italic>C</italic></xref>), Salinas South (CIMIS 089, <xref ref-type="fig" rid="fig17">fig. 17<italic>D</italic></xref>), King City-Oasis Rd. (CIMIS 113, <xref ref-type="fig" rid="fig17">fig. 17<italic>E</italic></xref>), and Salinas North (CIMIS 116, <xref ref-type="fig" rid="fig17">fig. 17<italic>F</italic></xref>). The ETref records and PET estimates at these sites show reasonable correspondence, although PET is slightly underestimated in the winter and slightly overestimated in the summer. Accordingly, seasonal bias adjustment factors are used in this study to adjust PET values to estimate ETref for crop demand calculations (further discussed in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.CropCoefficients">Crop Coefficients</xref>&#x201D; section of this report).</p>
<fig id="fig17" position="float" fig-type="figure"><label>Figure 17</label><caption><p>California Irrigation Management Information System (CIMIS; <xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>) field-scale reference evapotranspiration (ETref) and potential evapotranspiration (PET) estimated using the 270-meter-resolution Basin Characterization Model (<xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>) at the same location in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California. <italic>A</italic>, Correlation and comparison of stations with long-term records used for more detailed comparisons. Comparisons of time series are shown for <italic>B</italic>, Castroville (CIMIS 019); <italic>C</italic>, Arroyo Seco (CIMIS 114); <italic>D</italic>, Salinas South (CIMIS 089); <italic>E</italic>, King City-Oasis Rd. (CIMIS 113); and <italic>F</italic>, Salinas North (CIMIS 116).</p><p content-type="toc"><bold>17.</bold>	Graphs showing California Irrigation Management Information System field-scale reference evapotranspiration and potential evapotranspiration estimated using the 270-meter-resolution Basin Characterization Model at the same location in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>17. Basin Characterization Model potential evapotranspiration estimates are more variable than CIMIS estimates at all CIMIS stations except the Castroville station.</long-desc><graphic xlink:href="sac23-0784_fig17abc"/><graphic xlink:href="sac23-0784_fig17def"/></fig>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.LandUseData">
<title>Land Use Data</title>
<p>Land use data were compiled from available local, State, and Federal datasets. A complete description of the development of land use input data for the models are provided by <xref ref-type="bibr" rid="r92">Henson and Jachens (2024)</xref>. Available multi-year composite land use data were integrated with national-scale land use and land cover data (<xref ref-type="bibr" rid="r159">U.S. Geological Survey, 2000</xref>, <xref ref-type="bibr" rid="r160">2003</xref>, <xref ref-type="bibr" rid="r161">2011</xref>, <xref ref-type="bibr" rid="r163">2014</xref>; <xref ref-type="bibr" rid="r38">Dewitz and U.S. Geological Survey, 2021</xref>) and supplemented with information from the California Pesticide Use Reporting (CalPUR) database (<xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation, 2018</xref>; <xref ref-type="bibr" rid="r94">Henson and Voss, 2023</xref>) to provide a comprehensive edge-to-edge land use map for each year (<xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>). Native vegetation was defined using NLCD data and intersected in a geographic information system (GIS) with other available land use data. All land areas were presumed to be stable year to year until updated land use data showed changes in their distribution. If available land use data for an irrigated crop was present where NLCD data showed a native land use cover class, the irrigated land area was preserved. There were 56 land use identifiers developed to represent native vegetation, urban areas, and crops in the Salinas Valley (<xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>). As described above, land use analysis categories were grouped based on native or urban classes and the frequency that crops may change: high frequency rotational, annually stable, and multi-year. There is a climate gradient across the valley that could lead to differences in crop management and demand in coastal and inland areas&#x2014;for example, gradients in precipitation (<xref ref-type="fig" rid="fig03">fig. 3</xref>) and PET (<xref ref-type="fig" rid="fig05">fig. 5</xref>). Additionally, coastal areas can have differences in fog occurrence and cloud cover relative to inland areas. Inland and coastal climate zones (<xref ref-type="fig" rid="fig03">figs. 3</xref>, <xref ref-type="fig" rid="fig05">5</xref>) were used to support delineation of cropping and growth in land uses. Of the 56 land use identifiers, 40 were defined as irrigated land use categories with an inland and coastal member. Discriminating crops between these regions and climate zones allows for specification of crop properties specific to the climate region and resulting simulation of potential differences in climate, water demands, and crop management.</p>
<p>In land use data, irrigated land use often is classified broadly into categories with similar uses, such as irrigated land or truck and vegetable crop. For regions in the study area with these broad categorizations of land use, available land use data were supplemented with CalPUR data (<xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation, 2018</xref>). Applications of pesticides, including the date, crop, and application area are reported by each grower in the CalPUR database. Crop categories for the study area were defined by grouping reported crops from the CalPUR database into classes of vegetation with similar water demand and cultivation practices. Tabular data for Monterey County from 1974 to 2018 were obtained (<xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation, 2018</xref>, <ext-link ext-link-type="uri" xlink:href="https://www.cdpr.ca.gov/docs/pur/purmain.htm">https://www.cdpr.ca.gov/docs/pur/purmain.htm</ext-link>). The CalPUR land use estimator (<xref ref-type="bibr" rid="r94">Henson and Voss, 2023</xref>) was used to filter and aggregate the tabular data to an approximately 1-mi resolution defined by the public land survey system. Each row in each annual table is an application record and is associated with a public land survey system section (approximately 1 mi<sup>2</sup>). For each section, all crop applications were tabulated, and a cropped area fraction was computed for each of the irrigated land use types in the integrated hydrologic models (land use identifiers 1&#x2013;48; <xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>). These fractions were applied to each model cell within each section to provide more detailed information where land use is more broadly defined in NLCD or other land use data. To capture the intra-annual changes in the distribution of crops (for example, early spring and late fall), these fractions were computed for the January&#x2013;June and June&#x2013;December period each year. This computation results in two land use maps for every simulation year where land use is mapped to each model cell supporting the potential for multiple land uses in each model cell.</p>
<p>Urban areas are represented using two land use categories: an urban and a golf course turf/parks land-use type that are used to estimate outdoor irrigation and runoff. The extent of cities and settlements in the Salinas Valley were delineated based on NLCD data and aerial imagery. The extent of these developed areas was specified as both an urban or golf course turf/parks land-use type and an urban WBS. It is assumed that urban and golf course turf/parks land areas have access to shallow groundwater and groundwater pumpage by wells from the municipal systems where they are located.</p>
<p>Streams and riparian areas were delineated using aerial imagery (<xref ref-type="bibr" rid="r158">U.S. Department of Agriculture, 2016</xref>) and the National Hydrography Database (<xref ref-type="bibr" rid="r167">U.S. Geological Survey, 2019b</xref>). A riparian buffer of 530 ft was applied to the main channel of the Salinas River, resulting in 3,252 riparian model cells. These cells were grouped into their own WBS to support evaluation of the riparian areas in subsequent studies. A riparian land use type was developed using other hydrologic models in the region (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>) and vegetation data surveys from the Salinas River that show substantial woody and shrub vegetation with the invasive giant reed species <italic>Arundo donax</italic> L. (Howard Franklin, Monterey County Water Resources Agency, oral commun., 2018).</p>
<sec>
<title>Simulation of Crop Acreage</title>
<p>To show the relation between physical land use acreage compiled for the study and harvested acres, time series for eight crops are compared for calendar years 1967&#x2013;2014 (<xref ref-type="fig" rid="fig18">fig. 18</xref>). To better illustrate the representation of multi-cropping in the simulation, simulated acres for multi-cropped land uses were estimated for high frequency rotational and annually stable crops that can have multiple harvests. To estimate the simulated crop acres, the physical crop acres were multiplied by a multi-cropping factor of 1.97, as defined and used in the previous SVIGSM (<xref ref-type="bibr" rid="r11">Boyle Engineering Corporation, 1987</xref>; <xref ref-type="bibr" rid="r175">Yates, 1988</xref>; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). The time series show the comparison of estimated harvested acres from county crop reports, estimated physical acres using CalPUR data and land use GIS data (<xref ref-type="bibr" rid="r92">Henson and Jachens, 2024</xref>), and simulated acres assuming a multi-cropping factor of 1.97 applied to the estimated physical acres (<xref ref-type="fig" rid="fig18">fig. 18</xref>). The data show that harvested and simulated acres have similar trends, variability, and magnitudes. The trends of increased strawberries and vineyard acreage starting in the 1980s, the reduction in root vegetables (for example, sugar beets), and the steady increase in lettuce production correspond well (<xref ref-type="fig" rid="fig18">fig. 18</xref>). Although some of the simulated acreage values are lower than the harvested acres (for example, crucifers), these comparisons are for demonstration. The model simulates a long growing season with multiple harvests that account for the water demands due to multi-cropping but does not simulate individual harvests. After 2014, the strawberry and vineyard physical acreages do not increase as much in the model as the harvested acres reported in crop reports. Some of this effect could be due to differences between multiple harvests that may be counted in harvested acres. Physical acreage area is always the area that the crop occupies regardless of harvest. Although some differences among crop group harvested and simulated acres are present, the land use captures much more of the distribution and variability in crop group acreage than the common practices of estimating a crop group area that remains the same between land use datasets (for example, step functions in crop group acreage or linearly interpolating crop group acreages between land use datasets).</p>
<fig id="fig18" position="float" fig-type="figure"><label>Figure 18</label><caption><p>Comparison of time series of physical acreage, simulated acreage assuming a multi-cropping factor of 1.97, and harvested acreage for selected land use types in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2014.</p><p content-type="toc"><bold>18.</bold>	Graphs showing a comparison of time series of physical acreage, simulated acreage assuming a multi-cropping factor of 1.97, and harvested acreage for selected land use types in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2014</p></caption><long-desc>18. Comparison acres for estimated physical, simulated, and estimated harvested with the latter tending to be the greatest.</long-desc><graphic xlink:href="sac23-0784_fig18"/></fig>
</sec>
<sec id="sac23-0784_Final_20260508_kc.CropCoefficients">
<title>Crop Coefficients</title>
<p>Each of the land use categories in the study are represented by seasonally varying crop properties. The closer association between crop type and properties used in this study allows for better definition of individual crops of interest and supports future refinements of crop properties in the model as data become available. When available, published Kc values for similar coastal areas were used (<xref ref-type="bibr" rid="r13">Brouwer and others, 1985</xref>; <xref ref-type="bibr" rid="r14">Brouwer and Heibloem, 1986</xref>; <xref ref-type="bibr" rid="r146">Snyder and others, 1987a</xref>, <xref ref-type="bibr" rid="r147">b</xref>; <xref ref-type="bibr" rid="r1">Allen and others, 1998</xref>; Michael Cahn, University of California Agriculture and Natural Resources, Crop Manager, written communication, 2018). When no published Kc values for coastal areas were available, published Kc values for the western San Joaquin Valley compiled by <xref ref-type="bibr" rid="r15">Brush and others (2004)</xref> were used. Additional specific Kc values were used for greenhouse crops (<xref ref-type="bibr" rid="r136">Orgaz and others, 2005</xref>), turfgrass (<xref ref-type="bibr" rid="r62">Gibeault and others, 1989</xref>), and strawberries (<xref ref-type="bibr" rid="r148">Snyder and Schullbach, 1992</xref>; <xref ref-type="bibr" rid="r68">Hanson and Bendixen, 2004</xref>). The Kc values from the literature were adjusted to account for differences between field-measured CIMIS ETref and 530-ft resolution gridded PET used in this study using a seasonal bias adjustment factor. A seasonal bias adjustment factor for winter, spring, summer, and fall was computed to reduce the sum of squares error from the simulated PET and estimated ETref from CIMIS station data at five long-term stations throughout the Salinas Valley. The seasonal bias adjustment factors for PET were highest in the winter (1.00) and lowest in the summer (0.88), with a value of 0.94 for the spring and 0.97 for the fall. The seasonal bias adjustment factor for each season was multiplied by the Kc value to account for the difference between PET and ETref, and the Kc values for each of the land uses in each land use category was defined (<xref ref-type="fig" rid="fig19">fig. 19</xref>; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p>
<fig id="fig19" position="float" fig-type="figure"><label>Figure 19</label><caption><p>Crop coefficients by land use type for <italic>A</italic>, high frequency land use; <italic>B</italic>, annually stable land use; <italic>C</italic>, multi-year land use; <italic>D</italic>, urban and managed land use; and <italic>E</italic>, native land in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California.</p><p content-type="toc"><bold>19.</bold>	Graphs showing crop coefficients by land use type for high frequency land use, annually stable land use, multi-year land use, urban and managed land use, and native land in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>19. Monthly crop coefficients tend to be highest in the spring and summer months except for field crops, grain crops, pasture, semiagricultural, and upland grasslands and shrublands.</long-desc><graphic xlink:href="sac23-0784_fig19abc"/><graphic xlink:href="sac23-0784_fig19de"/></fig>
<p>Superimposed on the consumptive-use estimates are additional climatic-stress scale factors applied to Kc values as seasonal wet, normal, or dry scale-factor parameters that were estimated during parameter estimation and analysis. These climate-stress scale factors are applied to adjust Kc values for the period before and after 1995 in the model input (further described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.Landscape-ProcessParameters">Landscape-Process Parameters</xref>&#x201D; section and defined in the model archive by <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). Climate year type is defined using methods defined by MCWRA for reservoir operations (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>). Each year was defined as wet, normal, or dry based on the minimum storage in Lakes San Antonio and Nacimiento and the percentile of April 1st streamflow in Arroyo Seco. These seasonal scale factors are used to reflect potential differences in agricultural practices more appropriately among defined WBSs embedded in the consumptive-use estimates and the year-to-year changes in surface-water allocations and deliveries during the 1967&#x2013;2018 simulation period. This approach is consistent with several studies of the region (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r49">c</xref>).</p>
</sec>
<sec>
<title>Fractions of Transpiration, Precipitation, and Evaporation</title>
<p>The complete time series of FTR and FEI values are provided in the model archive (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>); a summary is provided here. The FEP is calculated internally by FMP as 1&#x2212;FTR. There are no specific data for FTR available in the literature. The FTR was developed based on expert knowledge, crop type and month, informed by other model applications in the region that use MF-OWHM (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r49">c</xref>), and adjusted during parameter estimation using reported withdrawal data. The FTR values for cropped land uses range from 0.39 to 0.73. Conceptually, the FTR means that the leaf area of each land use in each cell can vary between 39 and 73 percent of the land use area. For non-irrigated land uses, the FTR only affects the consumption of precipitation and shallow groundwater from the root zone. Thus, the FTR values mainly affect runoff to the streams generated from these land uses. For many of the non-irrigated land uses (for example, beach-dunes, barren-burned, quarries, semiagricultural, and idle-fallow), constant values of 0.3 are assumed for land use. This constant value of 0.3 assumes that grasses and weedy vegetation covers as much as 30 percent of these areas. Constant values of 0.08 are assumed for urban areas, which assumes that about 8 percent of the urban areas are subject to evapotranspiration from precipitation, and 92 percent are subject to evaporation of precipitation. It is assumed that the urban water uses that include irrigation are included in M &amp; I pumpage. The FEI is computed by crop for each irrigated land use type and can be conceptualized as the non-vegetated area that is irrigated (for example, sprinkler overspray). Through the simulation period, harvested acres have increased (<xref ref-type="fig" rid="fig07">fig. 7</xref>), yet water use has been relatively stable (<xref ref-type="fig" rid="fig14">fig. 14</xref>). Thus, FEI was reduced through time alongside assumed changes in irrigation methods. This reduction was done to represent the effects of shifting from sprinkler to drip irrigation and implementation of irrigation water conservation practices to reduce wetted areas that are not planted. This calculation is supported by documented increases in irrigation efficiency between 2001 and 2010, as noted by <xref ref-type="bibr" rid="r141">Sandoval&#x2010;Solis and others (2013)</xref> and <xref ref-type="bibr" rid="r155">Tindula and others (2013)</xref>. FEI values for crops range from 0.05 to 0.15 before the year 2000 and 0.01 to 0.05 after 2000.</p>
</sec>
<sec>
<title>Irrigation Efficiencies</title>
<p>In general, irrigation efficiencies and irrigation system types are poorly known (<xref ref-type="bibr" rid="r173">Williamson and others, 1989</xref>; <xref ref-type="bibr" rid="r24">California Department of Water Resources, 1994</xref>; <xref ref-type="bibr" rid="r15">Brush and others, 2004</xref>). Data describing the association between crops and irrigation system type, distribution of irrigation systems, and associated efficiencies in the integrated hydrologic model area are not available. We used expert input from agricultural producers, regional information, and a statewide report (<xref ref-type="bibr" rid="r141">Sandoval&#x2010;Solis and others, 2013</xref>) to estimate irrigation system type throughout the simulation period. Specification of OFE and their variation in time was informed by similarly constructed hydrologic and agricultural models in this region of California, the Central Valley Hydrologic Model (<xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r49">c</xref>, <xref ref-type="bibr" rid="r51">2024</xref>), Cuyama Valley (<xref ref-type="bibr" rid="r75">Hanson and others, 2014b</xref>), and the Pajaro Valley Hydrologic Model (<xref ref-type="bibr" rid="r77">Hanson and others, 2014c</xref>, <xref ref-type="bibr" rid="r78">d</xref>) and were adjusted during model parameter estimation. <xref ref-type="bibr" rid="r173">Williamson and others (1989)</xref> report values averaging 59 percent and ranging from 38 to 92 percent for the 1961&#x2013;77 period. California Department of Water Resources reports overall efficiencies of 60&#x2013;70 percent for parts of the Central Valley (<xref ref-type="bibr" rid="r24">California Department of Water Resources, 1994</xref>). The irrigation types specified in the integrated hydrologic models are a sprinkler and drip irrigation type for each of the two climate regions (inland and coastal) and nursery, flood, and urban for a total of seven specified irrigation types. For each of those irrigation types, an OFE was specified for each WBS. The OFE in the integrated hydrologic models vary between 0.3 for flood irrigation and 0.95 for drip irrigation. The OFE increase in time alongside assumed changes in irrigation methods (for example, shifting from sprinkler to drip irrigation) and improvements in irrigation water conservation practices. All OFE values used in the model are provided by <xref ref-type="bibr" rid="r86">Henson and Culling (2025)</xref>.</p>
</sec>
</sec>
<sec>
<title>Surface-Water Inflows and Outflows</title>
<p>The simulation of surface-water inflows and outflows in the integrated hydrologic models relies on observed streamflows at gages, reported diversions, reservoir outflows, and monthly average simulated watershed inflows as well as structural information about the surface-water drainage network, watershed inflow point, and reservoir release locations. The simulation of surface-water budgets relies on the simulation of streamflow gains and losses and flow from the surface-water drainage network into the ocean. Direct evaporation of surface water is not simulated within the surface-water drainage network. In the operational model, the simulation of surface-water outflows includes simulation of evaporation from reservoirs. Runoff to streams is simulated by FMP as a fraction of inefficient irrigation and precipitation for each model cell. However, runoff is not explicitly routed across the land surface; it is distributed equally to all stream reaches within each WBS where the runoff was generated. The surface-water drainage network is simulated with the SFR2 package (<xref ref-type="bibr" rid="r133">Niswonger and Prudic, 2005</xref>).</p>
<sec>
<title>Surface-Water Flow Data</title>
<p>Surface-water flow data used as input to the integrated hydrologic models include available monthly records of the three surface-water diversions (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>), simulated monthly average watershed inflows (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>; <xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>, <xref ref-type="bibr" rid="r97">2025b</xref>), and monthly historical reservoir inflows and releases (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Simulated daily watershed inflows from the watershed model are aggregated to monthly average inflow time series at 148 watershed inflow points along the boundary of the integrated hydrologic model domain (<xref ref-type="fig" rid="fig20">fig. 20</xref>; <xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>). These monthly watershed inflow time series are input to the streams within the integrated hydrologic model simulation (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). There are two watershed inflow points coincident with the location of reservoir releases. At these inflow points, the watershed model simulated monthly average natural flows are summed with monthly average historical reservoir flows. For the historical model, the watershed model inflows are summed with historical monthly average reservoir releases. For the operational model, the watershed model inflows are summed with simulated reservoir releases.</p>
<fig id="fig20" position="float" fig-type="figure"><label>Figure 20</label><caption><p>Surface-water drainage network channel types within the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California, U.S. Geological Survey National Water Information System streamgages, stream diversion locations, and point locations of watershed inflows from outside the active model domain.</p><p content-type="toc"><bold>20.</bold>	Map showing surface-water drainage network channel types within the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California, U.S. Geological Survey National Water Information System streamgages, stream diversion locations, and point locations of watershed inflows from outside the active model domain</p></caption><long-desc>20. Ephemeral watershed and tributary inflow channels tend to orient from the valley edges toward the Salinas River that extends from the upper valley to the coast.</long-desc><graphic xlink:href="sac23-0784_fig20"/></fig>
</sec>
<sec>
<title>Surface-Water Flow Simulation</title>
<p>The surface-water drainage network in the integrated hydrologic model area represents the Salinas River, major canals, diversion channels, drains, and tributaries that drain each surrounding upland watershed outside the integrated hydrologic model area (<xref ref-type="bibr" rid="r88">Henson and others, 2022b</xref>). The topology of the surface-water drainage network (<xref ref-type="bibr" rid="r88">Henson and others, 2022b</xref>) was developed using analysis of surficial geology and land-surface elevations from the SVGF, National Hydrography Dataset stream data (<xref ref-type="bibr" rid="r167">U.S. Geological Survey, 2019b</xref>), and aerial imagery (<xref ref-type="bibr" rid="r158">U.S. Department of Agriculture, 2016</xref>). The surface-water drainage network simulates the distribution and conveyance of surface water within the integrated hydrologic model area (<xref ref-type="fig" rid="fig20">fig. 20</xref>). This network is represented by a collection of stream cells (referred to as &#x201C;reaches&#x201D;), which are combined to form a collection of cells or reaches known as a &#x201C;segment.&#x201D; The total surface-water drainage network contains 524 segments, 9,008 reaches (model cells), 3 diversions, 148 watershed inflows, and 2 outflows to the ocean (<xref ref-type="fig" rid="fig20">fig. 20</xref>). There are a total of 93 collector segments that collect surface runoff but do not discharge to the Salinas River or its tributaries. These collector segments represent abandoned drainage canals, intermittent arroyo channels not present in National Hydrography Dataset stream data and were specifically delineated to facilitate simulation of intermittent recharge so that the magnitude of recharge from these features can be evaluated as part of future sustainability analyses. These collector segments have high streambed permeability to facilitate infiltration. Estimated watershed inflows from 42 of the 148 watershed inflows are routed into intermittent runoff from these ungaged watersheds at watershed inflow points connected to the surface-water drainage network. All streamflow that does not infiltrate into the underlying aquifer or flow into another stream is assumed to be lost to evapotranspiration. Riparian vegetation evapotranspiration in streams outside of the Salinas River is not directly simulated. The flows into collector segments are intermittent such that flow in any collector segment was greater than 10 ft<sup>3</sup>/s in only 24 of the 1,224 model time steps (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). Within the surface-water drainage network, channel bed elevations are specified on a model cell-by-cell (reach) basis using 1-m horizontal resolution light detection and ranging (lidar) data (<xref ref-type="bibr" rid="r166">U.S. Geological Survey, 2019a</xref>), where available, or a 10-m horizontal resolution DEM (<xref ref-type="bibr" rid="r162">U.S. Geological Survey, 2013</xref>). Streambeds were specified to be 1 ft thick throughout the network.</p>
<p>The surface-water flow simulation and water balance calculation used in SFR2 allow for streamflow routing, streamflow infiltration into the aquifer (losing stream reaches), and any potential base flow as groundwater discharge to streams (gaining stream reaches). Hydraulic flows among segments of the surface-water drainage network were simulated using two approaches based on available data for each stream segment: (1) a rating table approach that relates channel depth, width, and flow for a range of flow values and (2) an approach that assumes Manning&#x2019;s equation and a wide rectangular channel. The rating table approach was applied to seven stream segments in the surface-water drainage network that contain a USGS streamgage with long-term streamflow records (USGS 11150500, USGS 11151700, USGS 11152300, USGS 11152500, USGS 11152050, USGS 11152000, USGS 11152650; <xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>; <xref ref-type="bibr" rid="r88">Henson and others, 2022b</xref>). The Manning&#x2019;s equation approach was used for the rest of the stream segments. These stream segments were grouped based on the channel type (tributary, main channel, canal, ditch, or segment) that collects surface runoff and facilitate recharge but does not have a downgradient connection. Manning&#x2019;s roughness coefficient for each segment was specified using literature values for natural channels, developed channels, and canals for each segment (<xref ref-type="bibr" rid="r3">Arcement and Schneider, 1989</xref>). Roughness coefficient values varied within the range of 0.02&#x2013;0.05. When supported by local conditions, for example, in the upper Salinas Valley where vegetation in the channel can increase roughness, a value of about 0.05 was specified. The channel type was evaluated using adjacent land use through visual inspection of aerial imagery (<xref ref-type="bibr" rid="r158">U.S. Department of Agriculture, 2016</xref>). Hydraulic properties for these groups of segments have been parameterized to help with the parameter estimation of surface-water flow parameters. Surface-water flows were output using the HYDMOD package (<xref ref-type="bibr" rid="r73">Hanson and Leake, 1999</xref>).</p>
<p>To illustrate the spatial distribution of net stream leakage into the aquifer, the long-term (WY 1968&#x2013;2018) annual average stream leakage in each stream segment was computed using output from the historical model. The net stream leakage for each segment was divided by the segment length to provide a normalized value in acre-feet per year per foot (afyf) of stream segment length. The resulting long-term stream leakage map is shown on <xref ref-type="fig" rid="fig21">figure 21</xref>. Stream leakage varies along the length of the river, such that substantial leakage in the Salinas River (greater than 0.5 afyf) and even greater leakage (greater than 1.5 afyf) occurs in the center of the model domain, and much lower leakage (less than 0.25 afyf) occurs in the tributary segments and canals. This distribution of stream leakage through the model domain aligns with the streamflow analysis described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.SurfaceWaterandWatershed">Surface Water and Watershed</xref>&#x201D; section of this report, which showed substantial leakage in several segments of the Salinas River between Salinas River near Bradley (USGS 11150500), Salinas River near Soledad (USGS 11151700), and the gage farthest downstream, Salinas River near Spreckels (USGS 11152500).</p>
<fig id="fig21" position="float" fig-type="figure"><label>Figure 21</label><caption><p>Annual average net stream leakage normalized by segment length in the surface-water drainage network in acre-feet per year per foot (afyf), diversion locations, and selected streamgages used for analysis in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California.</p><p content-type="toc"><bold>21.</bold>	Map showing annual average net stream leakage normalized by segment length in the surface-water drainage network in acre-feet per year per foot, diversion locations, and selected streamgages used for analysis in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>21. Most streamflow seepage occurs along the Salinas River with maximum seepage occurring in the middle third of the valley.</long-desc><graphic xlink:href="sac23-0784_fig21"/></fig>
</sec>
</sec>
<sec>
<title>Surface-Water Agricultural Supply</title>
<p>There are three major surface-water supply sources in the integrated hydrologic models: diversions, reclaimed wastewater, and two reservoirs. Each surface-water source provides water to only one WBS. Surface-water diversions were simulated for two WBSs. To support the implementation of surface-water diversions for agriculture, a semi-routed delivery segment was added to the SFR2 stream for each of the two WBSs that receive surface water for irrigation. The addition of the semi-routed delivery allows for water deliveries to FMP to be constrained by available water in the SFR2 package and to be returned to the surface-water drainage network, which maintains the MF-OWHM framework of demand-driven and supply-constrained conjunctive use. Diversions for CSIP (WBS 2) are supplied by the SRDF. Diversions for Clark Colony (WBS 15) are supplied by Clark Colony Canal diversion on Arroyo Seco. Reclaimed wastewater is simulated as an additional source to the CSIP (WBS 2). Reclaimed wastewater deliveries are simulated as a non-routed delivery where a volume of water is specified for each month that is available to meet water demands. Lastly, reservoir releases from Lakes Nacimiento and San Antonio are used to meet streamflow targets at the SRDF and support surface-water deliveries to CSIP to offset groundwater pumpage.</p>
</sec>
<sec>
<title>Groundwater Pumpage Agricultural Supply</title>
<p>Monthly reported agricultural groundwater pumpage for each WBS was used to evaluate and calibrate the historical model (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). A specific representation of groundwater pumpage from individual wells was not an objective of this study nor is it appropriate given the regional scale and application of the integrated hydrologic models. The estimated well pumping capacities are provided with the well data by <xref ref-type="bibr" rid="r87">Henson and others (2023)</xref>. Currently, there are no groundwater allotments declared in the integrated hydrologic models. The overall required pumpage within a WBS is distributed among all wells associated with the WBS using the &#x201C;PRORATE ByCapacity&#x201D; option in the FMP and divides the pumping requirement of the WBS to each well proportional to the specified maximum capacity of each well (<xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>). Thus, wells with more specified capacity supply more of the groundwater for irrigation. Simulated groundwater pumpage by each irrigation well may differ substantially from the actual pumping value because the aggregated demands for a WBS are distributed among all irrigation wells. This assumption may result in local-scale errors in simulated groundwater levels near actual pumping wells but will result in accurate overall regional groundwater-level simulation.</p>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.GeologicFramework">
<title>Geologic Framework</title>
<p>Multiple sources of topographic and geologic data were used to define the geologic framework and the hydrogeologic units that are simulated in the integrated hydrologic models. Input to the final geologic framework included faults, hydrogeologic unit surfaces and extents, and hydrogeologic texture interpreted from borehole data, existing cross sections, and models. A brief discussion of the geologic framework is provided here; a full enumeration of the geologic framework&#x2019;s development is given by <xref ref-type="bibr" rid="r151">Sweetkind (2023)</xref>.</p>
<sec>
<title>Hydrogeologic Units</title>
<p>A hydrogeologic map of the study area (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>) was created from digital geologic maps using a GIS to merge the mapped stratigraphic units into the nine hydrogeologic units defined in <xref ref-type="table" rid="t03">table 3</xref>. Geologic map data for the onshore part of the study area were compiled from the digital geologic map of Monterey County (<xref ref-type="bibr" rid="r170">Wagner and others, 2002</xref>). South of this map, the California State geologic map (<xref ref-type="bibr" rid="r104">Jennings, 2010</xref>) was the primary source of geologic map data, locally augmented by larger scale maps (<xref ref-type="bibr" rid="r39">Dibblee, 1971</xref>, <xref ref-type="bibr" rid="r40">1972</xref>; <xref ref-type="bibr" rid="r82">Hart, 1985</xref>; <xref ref-type="bibr" rid="r32">Clark and others, 1997</xref>, <xref ref-type="bibr" rid="r31">2000</xref>). Geologic map data for the offshore part of the study area were compiled from <xref ref-type="bibr" rid="r64">Greene (1970</xref>, <xref ref-type="bibr" rid="r65">1977</xref>), <xref ref-type="bibr" rid="r66">Greene and Clark (1979)</xref>, <xref ref-type="bibr" rid="r170">Wagner and others (2002)</xref>, <xref ref-type="bibr" rid="r63">Golden and Cochrane (2013)</xref>, <xref ref-type="bibr" rid="r36">Dartnell and others (2016)</xref>, and <xref ref-type="bibr" rid="r105">Johnson and others (2016)</xref>. Geologic maps were combined and consolidated into a single hydrogeologic unit map (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>).</p>
<fig id="fig22" position="float" fig-type="figure"><label>Figure 22</label><caption><p>Map showing <italic>A</italic>, surface extent of hydrogeologic units and fault traces adapted from the Salinas Valley Geologic Framework (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>); and <italic>B</italic>, conceptual cross section through hydrogeologic units of the Salinas Valley Geologic Framework along the central axis of the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California. Vertical exaggeration is approximately 100 times.</p><p content-type="toc"><bold>22.</bold>	Map showing surface extent of hydrogeologic units and fault traces adapted from the Salinas Valley Geologic Framework and conceptual cross section through hydrogeologic units of the Salinas Valley Geologic Framework along the central axis of the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>22. The shallow aquifer is the primary unit at the surface in the active model domain. Only the shallow aquifer and Paso Robles Formation and older units extend throughout the valley.</long-desc><graphic xlink:href="sac23-0784_fig22a"/><graphic xlink:href="sac23-0784_fig22b"/></fig>
<table-wrap id="t03" orientation="landscape" position="float"><label>Table 3</label><caption>
<title>Summary of geologic formations and hydrogeologic units in the Salinas Valley Geologic Framework (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>).</title>
<p content-type="toc"><bold>3.</bold>	Summary of geologic formations and hydrogeologic units in the Salinas Valley Geologic Framework</p></caption>
<table rules="groups">
<col width="11.71%"/>
<col width="5.93%"/>
<col width="13.68%"/>
<col width="13.85%"/>
<col width="54.83%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Hydrogeologic unit name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Model layer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Geologic material</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Age</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Shallow aquifer</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">1</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Sand and gravel of unspecified origin</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Quaternary</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">The shallow aquifer is a shallow surficial aquifer in the Salinas Valley basin north of the Salinas River consisting of unconfined sands and gravels.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Upper confining unit</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="left">Alluvial sediment, mostly fine-grained</td>
<td valign="top" align="left">Quaternary</td>
<td valign="top" align="left">The upper confining unit is a laterally extensive series of blue or yellow sandy clay layers, with minor sand layers covering much of the Salinas Valley basin, east of Fort Ord, and from the Monterey Bay south past Salinas. This aquitard ranges in thickness from 25 feet near Salinas to more than 100 feet near Monterey Bay.</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">The 180-Foot Aquifer</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Alluvial sediment, mostly coarse-grained</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Quaternary</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">The 180-Foot Aquifer is the uppermost laterally extensive aquifer in the northern Salinas Valley. The 180-Foot Aquifer name is based on the depth where it is typically encountered in the subsurface. This unit consists of a complex zone of interconnected sands and gravels with intervening clay layers. The thickness of the 180-Foot Aquifer varies from 50 to 150 feet, with an average of about 100 feet. The 180-Foot Aquifer may be in part correlative to older portions of Quaternary terrace deposits or the upper Aromas Sands.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Middle confining unit</td>
<td valign="top" align="char" char=".">4</td>
<td valign="top" align="left">Alluvial sediment, mostly fine-grained</td>
<td valign="top" align="left">Quaternary</td>
<td valign="top" align="left">The middle confining unit separates the 180-Foot Aquifer from the underlying 400-Foot Aquifer. It is a zone of variably thick layers of blue clay to thin layers of brown clay. This aquitard is widespread in the Salinas Valley basin and varies in thickness and quality. The middle confining unit is commonly 50 to 100 feet thick and rarely as much as 200&#x2013;250 feet thick; local variations in thickness produce local areas where the 180-Foot and 400-Foot Aquifers are connected.</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">400-Foot Aquifer</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Alluvial sediment, mostly coarse-grained</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Quaternary</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">The 400-Foot Aquifer is areally extensive and consists of sands, gravels, and clay lenses; it is typically encountered between 270 and 470 feet below ground surface. The 400-Foot Aquifer has an average thickness of 200 feet, although the depth to the top of the aquifer, the thickness of the aquifer, and the degree of complex interbedding with clay layers is quite variable between wells. The thickness of this aquifer is variable, but typical sand beds are from 50 to 100 feet thick and can be more than 200-feet thick. The upper portion of this aquifer may be correlative with the Aromas Sands and the lower portion with the upper part of the Paso Robles Formation.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Lower confining unit</td>
<td valign="top" align="char" char=".">6</td>
<td valign="top" align="left">Alluvial sediment, mostly coarse-grained</td>
<td valign="top" align="left">Pleistocene</td>
<td valign="top" align="left">Interval of blue marine clay that separates the 400-Foot Aquifer from the deeper Paso Robles, Purisima, and basement aquifers. The lower confining unit thickness is highly variable, from as thin as 50 feet to as much as 750 feet.</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Paso Robles aquifer</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Clastic sedimentary rock</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Upper Pliocene to middle to lower Pleistocene</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Paso Robles aquifer sediments consist of lenticular beds of sand, gravel, silt, and clay. Beds are laterally discontinuous and may indicate an alluvial fan or braided stream depositional environment, likely deposited in part by an ancestral Salinas River. In places, the unit forms a part of the deep aquifer system of Monterey County, which in general terms includes all sediments below the 400-Foot Aquifer without respect to geology. Together, the Paso Robles, Purisima, and basement aquifers are referred to in general terms as the &#x201C;deep aquifer.&#x201D;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Purisima aquifer</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="left">Clastic sedimentary rock</td>
<td valign="top" align="left">Pliocene</td>
<td valign="top" align="left">Purisima aquifer sediments are the Pliocene Purisima Formation that is a shallow marine unit composed of intercalated siltstone, sandstone, conglomerate, clay, and shale. In places, the unit forms a part of the deep aquifer system of Monterey County, which in general terms includes all sediments below the 400-Foot Aquifer without respect to geology.</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Basement</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">9</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Rock</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Miocene and older</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">The rocks that form the basement aquifer are the Santa Margarita Formation, Monterey Formation, and older consolidated-rock units. The upper 500 feet of this hydrogeologic unit is considered the base of the hydrologic system.</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>A topographic model of the land surface at the model resolution was developed to describe the top of the uppermost hydrogeologic unit. Digital elevation data for the study area were extracted from a seamless 1:24,000-scale USGS National Elevation Dataset DEM (<xref ref-type="bibr" rid="r164">U.S. Geological Survey, 2017</xref>), resampled using spatial averaging to the 530-ft by 530-ft model grid, and processed using the Cascade Routing Tool for eight direction routing (<xref ref-type="bibr" rid="r93">Henson and others, 2013</xref>). Elevations of contacts between hydrogeologic units were compiled from structure-contour maps and well borehole data. The elevation of specific hydrogeologic unit tops were obtained from published structure contour maps of the onshore Salinas Valley as follows: base of Purisima Formation (<xref ref-type="bibr" rid="r52">Feeney and Rosenberg, 2003</xref>); base of Paso Robles Formation in the Paso Robles basin (<xref ref-type="bibr" rid="r59">Fugro West, Inc., and Cleath and Associates, 2002</xref>); and elevation of tops of the 400-Foot Aquifer, the Middle aquitard, and the 180-Foot Aquifer (<xref ref-type="bibr" rid="r4">Baillie and others, 2015</xref>). For the Seaside subbasin, contour maps of the tops of the Monterey Formation, Purisima Formation, and Paso Robles Formation were digitized (<xref ref-type="bibr" rid="r102">Hydrometrics, LLC, 2009</xref>). For the offshore region, geologic surface data were obtained from the elevation of the top of granitic basement and thickness contours of Miocene and Pliocene sedimentary rocks and Pleistocene and Holocene sediments (<xref ref-type="bibr" rid="r66">Greene and Clark, 1979</xref>). Contours representing modeled depth to pre-Cenozoic basement based on analysis of gravity data were digitized from <xref ref-type="bibr" rid="r171">Watt and others (2010)</xref>. A surface for each hydrogeologic unit was estimated using correlation of borehole data and augmented using geologic sections from eight reports (<xref ref-type="bibr" rid="r153">Thorup, 1983</xref>, <xref ref-type="bibr" rid="r154">1985</xref>; <xref ref-type="bibr" rid="r33">Cleath and Associates, 1991</xref>; <xref ref-type="bibr" rid="r67">Hall, 1992</xref>; <xref ref-type="bibr" rid="r149">Staal, Gardner, and Dunne, Inc., 1993</xref>; <xref ref-type="bibr" rid="r52">Feeney and Rosenberg, 2003</xref>; <xref ref-type="bibr" rid="r106">Kennedy/Jenks Consultants, 2004a</xref>, <xref ref-type="bibr" rid="r107">b</xref>; <xref ref-type="bibr" rid="r60">GEOSCIENCE Support Services, Inc., 2013</xref>). A conceptual diagram of the SVGF along the central axis of the Salinas Valley is shown (<xref ref-type="fig" rid="fig22">fig. 22<italic>B</italic></xref>) to illustrate the distribution of hydrogeologic units and their thickness from the coastal area to the edge of the integrated hydrologic model domain.</p>
</sec>
<sec>
<title>Geologic Structures</title>
<p>Structures, predominantly faults for the onshore part of the study area, were compiled from the digital geologic map of Monterey County (<xref ref-type="bibr" rid="r170">Wagner and others, 2002</xref>) and from the California State geologic map (<xref ref-type="bibr" rid="r104">Jennings, 2010</xref>). Offshore faults were compiled from digital offshore geologic map data (<xref ref-type="bibr" rid="r170">Wagner and others, 2002</xref>; <xref ref-type="bibr" rid="r63">Golden and Cochrane, 2013</xref>; <xref ref-type="bibr" rid="r36">Dartnell and others, 2016</xref>; <xref ref-type="bibr" rid="r105">Johnson and others, 2016</xref>) and digitized from georeferenced maps of the offshore region (<xref ref-type="bibr" rid="r64">Greene, 1970</xref>, <xref ref-type="bibr" rid="r65">1977</xref>; <xref ref-type="bibr" rid="r66">Greene and Clark, 1979</xref>). Faults were attributed according to their recency, defined by the youngest geologic unit that the fault cuts completely (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>). Fault recency was determined through comparison with the Quaternary fault and fold database of the United States (<xref ref-type="bibr" rid="r169">U.S. Geological Survey and California Geological Survey, 2021</xref>) and through inspection of the structural offset of each fault, as shown on geologic cross sections (<xref ref-type="bibr" rid="r153">Thorup, 1983</xref>, <xref ref-type="bibr" rid="r154">1985</xref>; <xref ref-type="bibr" rid="r33">Cleath and Associates, 1991</xref>; <xref ref-type="bibr" rid="r67">Hall, 1992</xref>; <xref ref-type="bibr" rid="r149">Staal, Gardner, and Dunne, Inc., 1993</xref>; <xref ref-type="bibr" rid="r52">Feeney and Rosenberg, 2003</xref>; <xref ref-type="bibr" rid="r106">Kennedy/Jenks Consultants, 2004a</xref>, <xref ref-type="bibr" rid="r107">b</xref>; <xref ref-type="bibr" rid="r60">GEOSCIENCE Support Services, Inc., 2013</xref>).</p>
</sec>
<sec>
<title>Hydrogeologic Texture</title>
<p>Lithologic data were compiled from a database of monitoring and water wells provided by MCWRA and augmented by data transcribed from water wells obtained from the California Department of Water Resources Well Completion Report database (<ext-link ext-link-type="uri" xlink:href="https://water.ca.gov/Programs/Groundwater-Management/Wells/Well-Completion-Reports">https://water.ca.gov/Programs/Groundwater-Management/Wells/Well-Completion-Reports</ext-link>). Downhole stratigraphy was transcribed for monitoring and water wells that appear on cross sections where aquifer and confining units were interpreted on cross sections in the following reports: <xref ref-type="bibr" rid="r153">Thorup (1983</xref>, <xref ref-type="bibr" rid="r154">1985)</xref>, <xref ref-type="bibr" rid="r33">Cleath and Associates (1991)</xref>, <xref ref-type="bibr" rid="r67">Hall (1992)</xref>, <xref ref-type="bibr" rid="r149">Staal, Gardner, and Dunne, Inc. (1993)</xref>, <xref ref-type="bibr" rid="r81">Harding ESE (2001)</xref>, <xref ref-type="bibr" rid="r52">Feeney and Rosenberg (2003)</xref>, <xref ref-type="bibr" rid="r106">Kennedy/Jenks Consultants (2004a</xref>, <xref ref-type="bibr" rid="r107">b</xref>), and <xref ref-type="bibr" rid="r60">GEOSCIENCE Support Services, Inc. (2013)</xref>. Geohydrologic information for the deeper aquifers near the coast was obtained from <xref ref-type="bibr" rid="r74">Hanson and others (2002)</xref>. Stratigraphic information for deeper hydrogeologic units in the southern, upstream part of the Salinas Valley was compiled from 336 oil and gas exploration wells obtained from the California Department of Conservation Geologic Energy Management Division (<ext-link ext-link-type="uri" xlink:href="https://www.conservation.ca.gov/calgem/Pages/WellFinder.aspx">https://www.conservation.ca.gov/calgem/Pages/WellFinder.aspx</ext-link>). Drilled depths to the tops of formations penetrated in the well were compiled. The source of the formation depth data for each well depended on the year the well was completed. Before 1964, summary tables of data for oil and gas prospect wells were used. From 1964 to 1980, year-by-year tables from <xref ref-type="bibr" rid="r29">California Division of Oil, Gas and Geothermal Resources (1982)</xref> were used. For all other wells, the interpretation of formations was evaluated using electric logs obtained through the California Department of Conservation Geologic Energy Management Division. The deepest hydrogeologic units, basement and the Purisima Formation, were assumed to be mostly consolidated with potential secondary alteration of porosity; thus, textural information was not developed for them. The remaining hydrogeologic units were considered less consolidated where sediment texture substantially affects the distribution of permeability. Textural properties of the seven remaining hydrogeologic units were derived from lithologic data in the basin using methods developed in nearby basins in California (<xref ref-type="bibr" rid="r137">Phillips and Belitz, 1991</xref>; <xref ref-type="bibr" rid="r16">Burow and others, 2004</xref>; <xref ref-type="bibr" rid="r47">Faunt and others, 2009a</xref>, <xref ref-type="bibr" rid="r50">2015</xref>; <xref ref-type="bibr" rid="r152">Sweetkind and others, 2013</xref>). Downhole lithologic data from nearly 1,400 wells were used to calculate the percentage of coarse-grained deposits within each hydrogeologic unit at each borehole. This percentage was interpolated using two-dimensional kriging from each borehole onto the model cells to create gridded estimates of the percentage of coarse-grained materials in each hydrogeologic unit. The hydraulic properties in the integrated hydrologic models were estimated based on the percentage of coarse-grained deposits, as was done for the Cuyama Valley (<xref ref-type="bibr" rid="r152">Sweetkind and others, 2013</xref>), Pajaro Valley (<xref ref-type="bibr" rid="r77">Hanson and others, 2014c</xref>, <xref ref-type="bibr" rid="r78">d</xref>), and Borrego Valley (<xref ref-type="bibr" rid="r50">Faunt and others, 2015</xref>). The hydrogeologic unit thickness and texture are shown side by side for the less consolidated hydrogeologic units (<xref ref-type="fig" rid="fig23">figs. 23<italic>A</italic>&#x2013;<italic>G</italic></xref>) that had textural classification in the SVGF. The thickness for the basement and Purisima Formation hydrogeologic units is provided on <xref ref-type="fig" rid="fig23">figure 23<italic>H</italic></xref>.</p>
<fig id="fig23" position="float" fig-type="figure"><label>Figure 23</label><caption><p>Hydrogeologic unit thickness and percentage of coarse material for hydrogeologic units that are not fully consolidated in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California (<xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) showing <italic>A</italic>, shallow aquifer; <italic>B</italic>, upper confining unit; <italic>C</italic>, 180-Foot Aquifer; <italic>D</italic>, middle confining unit; <italic>E</italic>, 400-Foot Aquifer; <italic>F</italic>, lower confining unit; and <italic>G</italic>, Paso Robles Formation; and <italic>H</italic>, maps showing hydrogeologic unit thickness for Purisima Formation; and <italic>I</italic>, bedrock hydrogeologic units. The Purisima Formation and bedrock hydrogeologic units represent composite rock aquifers without a textural classification so the percentage of coarse materials is not shown. </p><p content-type="toc"><bold>23.</bold>	Maps showing hydrogeologic unit thickness and percentage of coarse material for hydrogeologic units that are not fully consolidated in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>23. Hydrogeologic unit thickness and percentage coarse material is variable for all units. The deepest units are generally thickest.</long-desc><graphic xlink:href="sac23-0784_fig23a"/><graphic xlink:href="sac23-0784_fig23b"/><graphic xlink:href="sac23-0784_fig23c"/><graphic xlink:href="sac23-0784_fig23d"/><graphic xlink:href="sac23-0784_fig23e"/><graphic xlink:href="sac23-0784_fig23f"/><graphic xlink:href="sac23-0784_fig23g"/><graphic xlink:href="sac23-0784_fig23hi"/></fig>
</sec>
</sec>
<sec>
<title>Groundwater Inflows and Outflows</title>
<p>The simulation of groundwater pumpage and levels in the integrated hydrologic models relies on specification of boundary conditions, reported pumpage that is specified as model input, and simulated groundwater pumpage and recharge using FMP. Simulation of agricultural groundwater pumpage in MF-OWHM is constrained by reported aggregated pumpage by WBS when available. Simulation of M &amp; I groundwater pumpage is specified based on estimated or reported data when available. Simulation of groundwater recharge is constrained by observed water levels. Groundwater flows within the study area are computed using simulation of regional groundwater flow to adjacent groundwater basins, vertical exchanges among hydrogeologic units, pumpage, and evaporation of groundwater in the shallow root zone.</p>
<sec>
<title>Groundwater Data</title>
<p>Groundwater pumpage data were obtained for the period from October 1, 1967, to September 30, 2018 (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>), and reported groundwater pumpage data from as many as 353 M &amp; I wells were used to specify groundwater pumpage (<xref ref-type="fig" rid="fig24">fig. 24<italic>A</italic></xref>). Reported data aggregated to the WBS scale from as many as 2,002 agricultural wells (<xref ref-type="fig" rid="fig24">fig. 24<italic>A</italic></xref>) were used to evaluate the performance of simulated agricultural demand. A subset of wells was used to estimate M &amp; I pumpage before 1995. Reported groundwater levels from 439 wells were used to evaluate groundwater levels in the simulation (<xref ref-type="fig" rid="fig24">fig. 24<italic>B</italic></xref>). Of the 439 observation wells, 340 also were specified as agricultural wells and pumped to meet simulated agricultural demands (<xref ref-type="fig" rid="fig24">fig. 24<italic>B</italic></xref>) because many are used as agricultural supply wells, and information about available pumping wells in the basin was limited. Groundwater pumpage in the integrated hydrologic models is (1) FMP-simulated pumpage from irrigation wells (herein referred to as agricultural supply) and (2) estimated and specified M &amp; I and domestic pumpage (herein referred to as water supply). Because the integrated hydrologic models use monthly stress periods, pumping information from available data sources was converted into monthly values to define model input.</p>
<fig id="fig24" position="float" fig-type="figure"><label>Figure 24</label><caption><p>Well locations in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for <italic>A</italic>, municipal, industrial, and agricultural wells, and a subset of wells used to estimate municipal and industrial pumpage from water year 1968 to 1994 (pre-1995 wells); and <italic>B</italic>, location of observation wells.</p><p content-type="toc"><bold>24.</bold>	Maps showing well locations in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for municipal, industrial, and agricultural wells, and a subset of wells used to estimate municipal and industrial pumpage from water year 1968 to 1994, and location of observation wells</p></caption><long-desc>24. Agricultural wells, observation wells, and combined observation wells are widespread throughout the valley, whereas municipal and industrial and pre-1995 wells are concentrated around cities.</long-desc><graphic xlink:href="sac23-0784_fig24a"/><graphic xlink:href="sac23-0784_fig24b"/></fig>
<sec>
<title>Specified Groundwater Pumpage for Water Supply</title>
<p>Groundwater pumpage for M &amp; I is specified based on reported and estimated values. Domestic pumpage from individual landowners is not explicitly estimated. The M &amp; I pumpage estimates before 1995 are based on population and include potential domestic groundwater pumpage. After 1995, domestic pumpage is assumed to be less than 10 percent of M &amp; I pumpage. For example, domestic pumpage only meets water demands for approximately 31,000 of the 402,000 people estimated to live in Monterey County in the year 2000 (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Groundwater pumpage information for each M &amp; I well was estimated for the model period before November 1994 and specified using observations for the remainder of the simulation. For the model period before November 1994, the volume of groundwater pumpage was estimated using census population data and estimated gallons per capita per day for years 1970, 1980, and 1990 (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). After November 1994, M &amp; I pumpage was specified based on reported data. A complete description of the M &amp; I estimation methods and pumpage data are provided by <xref ref-type="bibr" rid="r87">Henson and others (2023)</xref>. The estimated monthly pumpage rate was divided among the wells in each area on a monthly time step and assigned to wells that were known or assumed to exist at that time.</p>
</sec>
</sec>
<sec>
<title>Groundwater Flow Simulation</title>
<p>Groundwater flow within the Salinas Valley occurs within the sediments of the nine hydrogeologic units and is assumed to be bounded at depth by the basement hydrogeologic unit and laterally by the outermost extent of the seven groundwater subbasins and mountain ridgelines that bound the Salinas Valley. Within the Salinas Valley, fault systems can act as barriers that affect groundwater flow and levels. Groundwater recharge and inflows can occur in hydrogeologic units exposed in the hillsides that bound the catchment of the Salinas Valley through ephemeral, intermittent, and perennial stream channels, through surface alluvium, and as underflow from Monterey Bay, the Paso Robles Area groundwater subbasin, and the Corralitos-Pajaro Valley groundwater subbasin (<xref ref-type="fig" rid="fig11">fig. 11</xref>). Groundwater outflow occurs as streamflow discharge, drain return flows, discharge to Monterey Bay, groundwater pumpage, and evapotranspiration. Groundwater pumpage for M &amp; I supply is specified. Groundwater flow, hydraulic properties, and initial and boundary conditions are described in this section. Groundwater recharge, pumpage for agricultural water supply, and evapotranspiration are simulated together using the representation of the land surface and land use water demands in the integrated hydrologic models, as described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.FarmProcessOverview">Farm Process Overview</xref>&#x201D; section.</p>
<sec>
<title>No-Flow Boundaries</title>
<p>No-flow boundaries in the integrated hydrologic models were used for the bottom of the basement hydrogeologic unit (layer 9) that represents the basement aquifer and for the lateral boundaries of the active model domain. The lateral no-flow boundaries are defined at the topographic ridges of ranges that bound the Salinas Valley and represent the contact between the low-permeability basement hydrogeologic unit and the aquifers at the edges of the groundwater basin (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>). No-flow boundaries were also specified for faults that bound parts of the foothills surrounding the Salinas Valley. The lower boundary of the model was limited to 500 ft below the top of the basement hydrogeologic unit, which is deeper than the deepest supply wells.</p>
</sec>
<sec>
<title>General-Head Boundaries</title>
<p>Lateral and vertical head-dependent flow boundaries are implemented to represent net regional groundwater flow from adjacent groundwater subbasins. Using the General Head Boundary Package of MODFLOW (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>), head-dependent flow boundaries were simulated in three locations in the model: a coastal, inland, and offshore general head boundary (GHB). The net coastal and inland GHB groundwater flow data were summed to create a category referred to as the &#x201C;interbasin underflow&#x201D; groundwater budget, and the offshore GHB net groundwater flow data were summed for all model layers to create a category referred to as the &#x201C;seawater coastal inflow&#x201D; groundwater budget. This seawater coastal inflow groundwater budget category is an analogue for seawater intrusion. Seawater intrusion is usually quantified as an area of the aquifer that has water quality degradation due to contamination by saline water, and the seawater coastal inflow budget category reflects the total volume of water that enters the landward portion of the model domain from the ocean. The hydraulic conductance for each group of GHB cells was based on the hydraulic conductivity of the aquifer sediments (described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.HydraulicProperties">Hydraulic Properties</xref>&#x201D; section) and the cell geometry. Hydraulic conductance for each GHB boundary was adjusted during model parameter estimation.</p>
<p>For the coastal GHB, lateral head-dependent flow boundaries were specified in selected cells in layers 1, 3, 5, 7, and 8 near the northern boundary of the study area near the coast in the 180/400-Foot Aquifer and Langley Area groundwater subbasins (<xref ref-type="fig" rid="fig25">fig. 25</xref>). The coastal GHB represents interbasin underflow between the integrated hydrologic model domain and the Pajaro Valley groundwater subbasin to the north. For the coastal GHB, four GHBs were specified with spatially constant and time-varying boundary heads obtained from nearby monitoring well groundwater levels (<xref ref-type="fig" rid="fig26">figs. 26<italic>A</italic>&#x2013;<italic>D</italic></xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). The hydraulic conductance for the group of cells associated with each monitoring well in each layer is considered constant.</p>
<fig id="fig25" position="float" fig-type="figure"><label>Figure 25</label><caption><p>Specification of general head boundaries (GHB) in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing the location of GHB wells and the cells used to define the offshore GHB, coastal GHB, and inland GHB.</p><p content-type="toc"><bold>25.</bold>	Map showing specification of general head boundaries in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>25. The location of the general head boundary (GHB): Offshore, coastal in the north, and inland at uppermost point of the Salinas River.</long-desc><graphic xlink:href="sac23-0784_fig25"/></fig>
<fig id="fig26" position="float" fig-type="figure"><label>Figure 26</label><caption><p>General head boundary (GHB) time series in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for <italic>A</italic>, coastal GHB boundary well 33H1; <italic>B</italic>, coastal GHB boundary well 16D1; <italic>C</italic>, coastal GHB boundary well 4L1; <italic>D</italic>, coastal GHB boundary well 12D1 (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>); and <italic>E</italic>, mean monthly sea level (<xref ref-type="bibr" rid="r131">National Oceanic and Atmospheric Administration, 2019</xref>). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>26.</bold>	Plots showing general head boundary time series in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>26. Groundwater levels trend downward for some wells and upward for others. Sea level varies annually and has trended upward since 2010.</long-desc><graphic xlink:href="sac23-0784_fig26abcd"/><graphic xlink:href="sac23-0784_fig26e"/></fig>
<p>For the inland GHB, lateral head-dependent flow boundaries also were specified in layer 7 near the Salinas River at the southern boundary of the integrated hydrologic model domain. This inland GHB represents interbasin underflow between the integrated hydrologic model domain and the Paso Robles Area groundwater subbasin to the south. For the inland GHB (<xref ref-type="fig" rid="fig25">fig. 25</xref>), a GHB is defined for seven cells in layer 7 perpendicular to the first river reach. The inland GHB time-series value was a constant 400 ft through time, estimated as the mean hydraulic head near the river from the Paso Robles hydrologic model of the upper Salinas Valley (<xref ref-type="bibr" rid="r61">GEOSCIENCE Support Services, Inc., 2016</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>).</p>
<p>For the offshore GHB, vertical head-dependent flow boundaries were specified for the exposed offshore geologic units to estimate seawater coastal inflow in the aquifers along the coast. The offshore GHB is used to estimate coastal inflow exchanges among the onshore and offshore areas of each hydrogeologic unit. The integrated hydrologic models do not explicitly simulate the density of seawater for the simulation of exchanges between the onshore and offshore areas of the model domain. For each model cell exposed on the seafloor, a vertical GHB boundary was applied. A monthly time series of sea-level variation was estimated using the mean monthly sea level elevation data (<xref ref-type="fig" rid="fig26">fig. 26<italic>E</italic></xref>; <xref ref-type="bibr" rid="r131">National Oceanic and Atmospheric Administration, 2019</xref>) in San Francisco Bay before 1974 (identifier 9414290) and in Monterey Bay after 1974 (station 9413450). An equivalent freshwater hydraulic head was used to account for the density of seawater in the offshore hydraulic heads using the methods described by <xref ref-type="bibr" rid="r127">Motz and Sedighi (2009)</xref>. The elevation value was based on the North American Vertical Datum of 1988. This approximation of equivalent freshwater hydraulic head was determined to yield accurate values for hydraulic heads in a coastal aquifer based on experiments in three-dimensional groundwater flow models. The GHB along the coastline was computed using <xref ref-type="disp-formula" rid="e01">equation 1</xref>:<disp-formula id="e01"><alternatives><mml:math id="m1"><mml:mrow><mml:msub><mml:mi>h</mml:mi><mml:mrow><mml:mi>f</mml:mi><mml:mi>w</mml:mi><mml:mtext>&#x00A0;</mml:mtext></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mfrac><mml:mi>&#x03C1;</mml:mi><mml:mrow><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mi>f</mml:mi></mml:msub></mml:mrow></mml:mfrac><mml:mi>h</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mfrac><mml:mrow><mml:mi>&#x03C1;</mml:mi><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mi>f</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mi>f</mml:mi></mml:msub></mml:mrow></mml:mfrac><mml:mtext>&#x00A0;</mml:mtext><mml:msub><mml:mi>Z</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:math><graphic position="anchor" xlink:href="sac23-0784_m01"/></alternatives><label>(1)</label></disp-formula>where</p>
<def-list list-type="equation-where"><def-item><term><named-content content-type="math"><italic>h<sub>fw</sub></italic></named-content></term>
<def>
<p>is the hydraulic head of freshwater equivalence,</p></def></def-item><def-item><term><named-content content-type="math"><italic>h</italic></named-content></term>
<def>
<p>is the pressure head at a point N above a datum,</p></def></def-item><def-item><term><named-content content-type="math"><italic>&#x03C1;</italic></named-content></term>
<def>
<p>is the density of saline groundwater at point N above a datum,</p></def></def-item><def-item><term><named-content content-type="math"><italic>&#x03C1;<sub>f</sub></italic></named-content></term>
<def>
<p>is the density of freshwater, and</p></def></def-item><def-item><term><named-content content-type="math"><italic>Z<sub>i</sub></italic></named-content></term>
<def>
<p>is the node of each GHB cell along the coast.</p></def></def-item>
</def-list>
<p>The equivalent freshwater head used to compute the GHB value was variable for each cell with an offshore GHB. The equivalent GHB value depends on the height of the column of water above the center of cell <named-content content-type="math"><italic>Z<sub>i</sub></italic></named-content> where the GHB was applied. If the top of the cell where the GHB was applied was closer to the ocean surface (for example, near the shoreline), the GHB value was lower. If the top of the cell where the GHB was applied was deep under the sea level (for example, far from shore), the GHB value was higher. The range of GHB values over all offshore GHBs ranged from 2.5 to 97.4 ft.</p>
</sec>
<sec>
<title>Groundwater Wells</title>
<p>Irrigation, municipal, and industrial wells are simulated as multiple-aquifer wells that can extract water from more than one hydrogeologic unit (<xref ref-type="fig" rid="fig24">fig. 24<italic>A</italic></xref>). All single and multiple-aquifer wells were simulated by the multi-node well package (MNW2; <xref ref-type="bibr" rid="r108">Konikow and others, 2009</xref>). The MNW2 simulates two processes: (1) the produced groundwater from single or multiple aquifers during pumping and (2) the flow of water between aquifers via boreholes when multiple aquifers are connected to the same well and have different hydraulic heads. For many of the wells, data for each well describing the operational history, open screen intervals, construction information, and radius were estimated where they were incomplete. This section summarizes the methods used for estimating the missing well data to create a complete set of well-related data and properties needed for model construction. The resulting complete set of well information was published by <xref ref-type="bibr" rid="r87">Henson and others (2023)</xref>.</p>
<p>Estimated operational history information (drill dates, active pumping periods, and destruction dates, if applicable) was used to construct the monthly pumping time series for each well. The number of active wells for any given stress period varied through time based on reported drill dates and destruction dates. Well construction and destruction dates were used where available to specify when wells are active in the simulation. Specifying wells with undefined construction information as active for the simulation is warranted based on historical reports of extensive agricultural groundwater development (<xref ref-type="bibr" rid="r20">California Department of Water Resources, 1968</xref>). Available open-screen interval data were used to identify the model layers from which water was withdrawn, with the assumption that wells fully penetrate each layer they pump from. If a well contained multiple open-screen intervals, all layers from the top of the uppermost open interval to the bottom of the lowermost interval are assumed to be completely screened and fully penetrating in those model layers. When well-screen intervals span multiple model layers, the well is simulated as a multiple-aquifer well, allowing pumping to be dynamically distributed along with intra-wellbore flow between all corresponding layers. Thus, pumpage for each well was allocated dynamically to individual model layers based on the available construction information to determine which layers contribute to potential pumpage or intra-wellbore flow within a well. There is substantial uncertainty about the hydrogeologic unit to which each well is connected, which can contribute to uncertainty in the magnitude of simulated well drawdowns, distribution of pumpage, and intra-borehole exchanges of water among layers. To mitigate this uncertainty to the extent possible, wells with missing construction information were assigned open screen intervals based on their WBS, construction date, depth, and the nearby MCWRA-estimated 500 mg/L chloride concentration contour (<xref ref-type="fig" rid="fig24">fig. 24<italic>A</italic></xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>; <xref ref-type="bibr" rid="r124">Monterey County Water Resources Agency, 2023</xref>). Where available, the well pumping capacity and casing diameter of each well was obtained from MCWRA. Missing well pumping capacity and the casing diameter of each MNW2 well was estimated based on properties of similar wells from the MCWRA well database (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). If the casing diameter was not available for a well, the well was either assigned a casing diameter from a nearby well or assumed to have the median casing diameter of all wells with the same well-use category. The diameter of the well skin, representing the region of disturbed aquifer material surrounding the well casing due to drilling activities, was assumed based on the drill date and casing diameter of the well.</p>
</sec>
<sec>
<title>Drain Return Flows</title>
<p>Groundwater discharge to the land surface was simulated using the MODFLOW Drain Return Flow package (DRT; <xref ref-type="bibr" rid="r5">Banta, 2000</xref>; <xref ref-type="bibr" rid="r72">Hanson and others, 2014a</xref>). This drainage boundary condition was applied to each of the uppermost model cells in the integrated hydrologic models, with the drain elevation set to the land surface elevation plus 1 foot inside the riparian area and cells containing streams and the land surface elevation everywhere else. This model setup allows routing of groundwater discharge to streams when using the DRT. The DRT applies a drain boundary condition to compute groundwater-level rise above the land surface and routes this drain flow to adjacent streams. This drain flow becomes streamflow that is managed by the SFR2.</p>
<p>To better quantify the magnitude and timing of groundwater discharge to streams in different locations of the study area, the model cells specified in DRT were grouped into three different budget group categories in the model output. Each cell in the riparian WBS was defined as a riparian drain and assigned to a riparian drainage groundwater budget category in the analysis. Each cell coincident with or adjacent to a stream cell that is not a part of the riparian WBS was defined as a tributary drain and assigned to a tributary drainage groundwater outflow budget category. Every other cell in the model domain was defined as a surface drain and assigned to a surface drainage groundwater outflow budget category. These budget categories are used to evaluate the role of different locations of groundwater discharge to streams in hydrologic budgets throughout the basin.</p>
</sec>
<sec id="sac23-0784_Final_20260508_kc.HydraulicProperties">
<title>Hydraulic Properties</title>
<p>The Layer Property Flow package (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>) was used to define storage and hydraulic conductivity properties in each of the aquifers represented in the integrated hydrologic models. The Layer Property Flow package, along with the Parameter Value (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>) and Multiplier (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>) packages, was used to calculate and specify the aquifer storage and hydraulic conductivity parameters. Lateral and vertical variations in sediment texture affect the direction and rate of groundwater flow by constraining the magnitude and distribution of aquifer-system permeability, porosity, and storativity. The hydrogeologic units defined in the SVGF (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>; <xref ref-type="table" rid="t02">table 2</xref>; <xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) were used as surrogates to define the vertical and lateral hydraulic conductivity and storage property distributions within the integrated hydrologic models. Each hydrogeologic unit can be characterized by variations in hydraulic properties, which are based on the textural distribution of coarse- and fine-grained sediments in zones that represent subregions in which sediments accumulated in particular depositional environments, referred to as &#x201C;facies&#x201D; (<xref ref-type="bibr" rid="r150">Sweetkind, 2017</xref>). For this study, facies generally are represented by the Salinas Valley groundwater subbasins (<xref ref-type="fig" rid="fig11">fig. 11</xref>) and are implemented as parameter zones using the ZONE package (<xref ref-type="bibr" rid="r80">Harbaugh, 2005</xref>). Hydraulic properties for the three model layers of the most recent SVIGSM (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>) were used as initial values for the integrated hydrologic models (<xref ref-type="table" rid="t04">table 4</xref>). Hydraulic properties were then estimated as separate parameters that were adjusted by groundwater subbasin using regional-scale factors.</p>
<table-wrap id="t04" position="float"><label>Table 4</label><caption>
<title>Summary of hydrogeologic units, model layers, and aquifer properties in the Salinas Valley Integrated Hydrologic Model and Salinas Valley Operational Model, with corresponding layers and properties from the previously developed Salinas Valley Integrated Groundwater and Surface Model (SVIGSM; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>).</title>
<p content-type="toc"><bold>4.</bold>	Summary of hydrogeologic units, model layers, and aquifer properties in the Salinas Valley Integrated Hydrologic Model and Salinas Valley Operational Model</p>
<p>[ft/day, foot per day; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="15.32%"/>
<col width="7.87%"/>
<col width="9.12%"/>
<col width="16.65%"/>
<col width="16.41%"/>
<col width="19.33%"/>
<col width="15.3%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="rowgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Hydrogeologic unit</td>
<td valign="middle" colspan="6" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Salinas Valley Integrated Hydrologic Model (SVIHM)</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Model layer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Statistic</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Horizontal hydraulic conductivity (ft/day)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Vertical hydraulic conductivity (ft/day)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Specific yield for composite upper layer (dimensionless)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Specific storage (per foot)</td>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="3" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="rowgroup">Shallow aquifer</td>
<td rowspan="3" valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">1</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Max</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">139</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.14</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Mean</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">55</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.12</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Min</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.02</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.88E&#x2212;04</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.05</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" scope="rowgroup">Upper confining unit</td>
<td rowspan="3" valign="top" align="char" char=".">2</td>
<td valign="top" align="center">Max</td>
<td valign="top" align="char" char=".">0.58</td>
<td valign="top" align="char" char=".">0.07</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">5.00E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Mean</td>
<td valign="top" align="char" char=".">0.04</td>
<td valign="top" align="char" char=".">2.63E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">4.95E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Min</td>
<td valign="top" align="char" char=".">7.98E&#x2212;04</td>
<td valign="top" align="char" char=".">9.58E&#x2212;05</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">4.88E&#x2212;05</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="rowgroup">180-Foot aquifer</td>
<td rowspan="3" valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">Max</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">230</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">15</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.09E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Mean</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">94</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.83E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Min</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.98E&#x2212;01</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.49E&#x2212;03</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7.21E&#x2212;06</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" scope="rowgroup">Middle confining unit</td>
<td rowspan="3" valign="top" align="char" char=".">4</td>
<td valign="top" align="center">Max</td>
<td valign="top" align="char" char=".">7.71E&#x2212;03</td>
<td valign="top" align="char" char=".">6.72E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">2.76E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Mean</td>
<td valign="top" align="char" char=".">4.33E&#x2212;03</td>
<td valign="top" align="char" char=".">2.35E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">1.99E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Min</td>
<td valign="top" align="char" char=".">1.46E&#x2212;03</td>
<td valign="top" align="char" char=".">1.36E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">1.09E&#x2212;05</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="rowgroup">400-Foot Aquifer</td>
<td rowspan="3" valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">Max</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">242</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7.21E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Mean</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">70</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.88E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Min</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.40</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.30E&#x2212;03</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6.34E&#x2212;06</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" scope="rowgroup">Deep confining unit</td>
<td rowspan="3" valign="top" align="char" char=".">6</td>
<td valign="top" align="center">Max</td>
<td valign="top" align="char" char=".">0.04</td>
<td valign="top" align="char" char=".">4.35E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">8.86E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Mean</td>
<td valign="top" align="char" char=".">0.02</td>
<td valign="top" align="char" char=".">1.85E&#x2212;03</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">5.76E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Min</td>
<td valign="top" align="char" char=".">1.21E&#x2212;03</td>
<td valign="top" align="char" char=".">1.21E&#x2212;04</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">1.26E&#x2212;05</td>
</tr>
<tr>
<td rowspan="3" valign="top" align="left" style="background-color:rgb(217,217,217)" scope="rowgroup">Paso Robles aquifer</td>
<td rowspan="3" valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">Max</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">87</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.21E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Mean</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.5</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8.17E&#x2212;05</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Min</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.02</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.84E&#x2212;06</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.07E&#x2212;06</td>
</tr>
<tr>
<td rowspan="4" valign="top" align="left" scope="rowgroup">Purisima aquifer</td>
<td rowspan="4" valign="top" align="char" char=".">8</td>
<td valign="top" align="center">Max</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">0.36</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Mean</td>
<td valign="top" align="char" char=".">1.2</td>
<td valign="top" align="char" char=".">0.05</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" scope="row">Min</td>
<td valign="top" align="char" char=".">8.47E&#x2212;03</td>
<td valign="top" align="char" char=".">3.53E&#x2212;05</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td colspan="4" valign="top" align="left" scope="row">Constant</td>
<td valign="top" align="char" char=".">1.49E&#x2212;05</td>
</tr>
<tr>
<td rowspan="4" valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="rowgroup">Bedrock aquifer</td>
<td rowspan="4" valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">9</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">Max</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3.66</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6.80E&#x2212;03</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Mean</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4.46E&#x2212;03</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" colspan="1" align="center" style="background-color:rgb(217,217,217)" scope="row">Min</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.09</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6.80E&#x2212;04</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td colspan="4" valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Constant</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">1.62E&#x2212;06</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec>
<title>Zones</title>
<p>The distributions of storage properties and horizontal and vertical hydraulic conductivities vary with the distribution of subregions or zones of each hydrogeologic unit (<xref ref-type="fig" rid="fig27">figs. 27<italic>A</italic>&#x2013;<italic>F</italic></xref>). The parameters used to represent these subregions within each model layer represent unconfined aquifers in outcrop areas and subareas of confined aquifers that underlie other aquifers. Therefore, the hydraulic properties of each of these subareas were estimated with separate model parameters during model parameter estimation. In subareas where hydrogeologic units (layers) pinch out or were otherwise missing, the hydraulic properties are represented by a zone of pinched cells with relatively small storativity, high vertical hydraulic conductivity, and low horizontal hydraulic conductivity that allow communication between the present layers. To define model parameters, zones were combined with information about sediment texture from the SVGF.</p>
<fig id="fig27" position="float" fig-type="figure"><label>Figure 27</label><caption><p>Distribution of parameter zones used for estimation of hydraulic properties in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for the six aquifer hydrogeologic units: <italic>A</italic>, shallow aquifer (model layer 1); <italic>B</italic>, 180-Foot Aquifer (model layer 3); <italic>C</italic>, 400-Foot Aquifer (model layer 5); <italic>D</italic>, Paso Robles Formation (model layer 7); <italic>E</italic>, Purisima Formation (model layer 8); and <italic>F</italic>, bedrock (model layer 9; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>27.</bold>	Maps showing the distribution of parameter zones used for estimation of hydraulic properties in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California for the six aquifer hydrogeologic units</p></caption><long-desc>27. Parameter zones generally are continuous and align with the Salinas Valley groundwater subbasins.</long-desc><graphic xlink:href="sac23-0784_fig27ab"/><graphic xlink:href="sac23-0784_fig27cd"/><graphic xlink:href="sac23-0784_fig27ef"/></fig>
</sec>
<sec>
<title>Texture-Based Hydraulic Properties</title>
<p>The hydraulic water-transmitting properties of aquifer sediments are represented by hydraulic storage properties and horizontal and vertical hydraulic conductivity of the hydrogeologic units. The relation between hydrogeologic units in the aquifer system, lithology, texture, and hydraulic properties has been developed in many previous studies that include both the properties of the aquifers and those of any fine-grained interbeds or confining units (<xref ref-type="bibr" rid="r70">Hanson and others, 1990</xref>, <xref ref-type="bibr" rid="r79">2003</xref>, <xref ref-type="bibr" rid="r76">2004</xref>, <xref ref-type="bibr" rid="r72">2014a</xref>, <xref ref-type="bibr" rid="r75">b</xref>; <xref ref-type="bibr" rid="r112">Laudon and Belitz, 1991</xref>; <xref ref-type="bibr" rid="r137">Phillips and Belitz, 1991</xref>; <xref ref-type="bibr" rid="r71">Hanson and Benedict, 1994</xref>; <xref ref-type="bibr" rid="r7">Belitz and Phillips, 1995</xref>; <xref ref-type="bibr" rid="r114">Leighton and others, 1995</xref>; <xref ref-type="bibr" rid="r16">Burow and others, 2004</xref>; <xref ref-type="bibr" rid="r138">Phillips and others, 2007</xref>; <xref ref-type="bibr" rid="r47">Faunt and others, 2009a</xref>, <xref ref-type="bibr" rid="r48">b</xref>). The storage and hydraulic conductivity parameter values for each model cell in each hydrogeologic unit are assumed to be correlated to sediment texture in the SVGM, using the fraction of coarse-grained to fine-grained sediment. The percentage of coarse material estimated from the SVGF (<xref ref-type="fig" rid="fig23">fig. 23</xref>) was used to develop values for storage and hydraulic conductivity properties. All hydrogeologic units, except the Purisima and basement aquifers, have separate estimates of the coarse material percentage. The zones are used to distribute hydraulic properties in the Purisima and basement aquifer hydrogeologic units, whereas the zones and estimates of the coarse material percentage in each model cell are used for all other hydrogeologic units. Within each model layer, these distributed values are scaled within defined zones (<xref ref-type="table" rid="t05">table 5</xref>; <xref ref-type="fig" rid="fig27">figs. 27<italic>A&#x2013;F</italic></xref>) to estimate final values derived from parameter estimation (<xref ref-type="fig" rid="fig21">figs. 21<italic>A</italic>&#x2013;<italic>H</italic></xref>). The final parameters from parameter estimation representing hydraulic properties and related scale factors are discussed in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.ParameterEstimationandHistoryMatchingSalinas">Parameter Estimation and History Matching&#x2014;Salinas Valley Integrated Hydrologic Model</xref>&#x201D; section.</p>
<table-wrap id="t05" position="float"><label>Table 5</label><caption>
<title>Summary of MODFLOW boundary parameter and zone codes used to represent the hydrogeologic properties within the integrated hydrologic model domain.</title>
<p content-type="toc"><bold>5.</bold>	Summary of MODFLOW boundary parameter and zone codes used to represent the hydrogeologic properties within the integrated hydrologic model domain.</p>
<p>[&#x2014;, no data]</p></caption>
<table rules="groups">
<col width="11.99%"/>
<col width="9.33%"/>
<col width="10.55%"/>
<col width="8.94%"/>
<col width="10.82%"/>
<col width="8.94%"/>
<col width="10.73%"/>
<col width="8.86%"/>
<col width="10.11%"/>
<col width="9.73%"/>
<thead>
<tr>
<td rowspan="2" valign="middle" align="center" scope="rowgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Codes</td>
<td valign="middle" colspan="9" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Hydrogeologic units</td>
</tr>
<tr>
<td valign="middle" colspan="1" align="center" scope="colgroup" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Shallow aquifer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Upper confining <break/>unit</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">180-Foot Aquifer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Middle confining unit</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">400-Foot Aquifer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Deep confining unit</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Paso Robles aquifer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Purisima aquifer</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Bedrock aquifer</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Offshore codes</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Pinched</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">None</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">91</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">92</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">93</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">94</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">95</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">96</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">97</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Active</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">10</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">11</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">12</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">13</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">14</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">15</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">16</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">17</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">18</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Onshore codes</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Pinched</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">None</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">81</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">82</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">83</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">84</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">85</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">86</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">87</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pinched with nearby well</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
<td valign="top" align="char" char=".">69</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Active main zone</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian</td>
<td valign="top" align="char" char=".">101</td>
<td valign="top" align="char" char=".">201</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian Upper Valley</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">701</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Granite Ridge</td>
<td valign="top" align="char" char=".">102</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">302</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">502</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">702</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Highlands South</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">103</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">303</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">503</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">703</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">East Side</td>
<td valign="top" align="char" char=".">104</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">304</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">504</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Pressure</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">105</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">305</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">505</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="char" char=".">106</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">306</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">506</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">430</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Arroyo Seco</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">107</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">307</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">507</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Coastal Region</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">708</td>
<td valign="top" align="char" char=".">420</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Upper Valley</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">709</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">440</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Central</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">460</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Uplands</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">470</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">530</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Seaside</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">450</td>
<td valign="top" align="char" char=".">510</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Southern side</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">520</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Northern side</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">540</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Groundwater Storage</title>
<p>Simulation of groundwater storage consisted of two storage terms (<xref ref-type="bibr" rid="r84">Helm, 1975</xref>; <xref ref-type="bibr" rid="r69">Hanson, 1988</xref>): specific yield (<named-content content-type="math"><italic>Sy</italic></named-content>) for unconfined subregions and elastic specific storage (<named-content content-type="math"><italic>S</italic></named-content>) that includes the compressibility of water for unconfined and confined subregions. The <named-content content-type="math"><italic>Sy</italic></named-content> and <named-content content-type="math"><italic>S</italic></named-content> are storage terms that represent and govern the reversible uptake and release of water to and from storage (<xref ref-type="disp-formula" rid="e02">eq. 2</xref>). The <named-content content-type="math"><italic>Sy</italic></named-content> storage term represents unconfined storage and gravity-driven draining or filling (resaturation) of sediments as changes to the water table occur. The <named-content content-type="math"><italic>Sy</italic></named-content> is a function of sediment porosity and moisture-retention characteristics; it cannot exceed the porosity. Specific yield typically is orders of magnitude larger than specific storage and is volumetrically the dominant storage parameter for aquifers in outcrops of basement, Purisima Formation, Paso Robles Formation, and recent alluvium. The <named-content content-type="math"><italic>S</italic></named-content> storage term represents the component of confined storage owing to the compressibility of water and to the reversible compressibility of the matrix or the skeletal framework of the aquifer system (<xref ref-type="bibr" rid="r103">Jacob, 1940</xref>; <xref ref-type="bibr" rid="r69">Hanson, 1988</xref>). The inelastic storage coefficient is another storage term that sometimes is defined and included in the storage formulation. The inelastic storage coefficient governs the irreversible release of water from the inelastic compaction of the fine-grained deposits or permanent reduction of pore space, which also can lead to land subsidence. There has not been land subsidence documented in the Salinas Valley where assessments have occurred (<xref ref-type="bibr" rid="r12">Brandt and others, 2021</xref>), and this version of the integrated hydrologic models does not simulate subsidence; thus, the inelastic storage coefficient storage term was not considered in the composite storage formulation shown in <xref ref-type="disp-formula" rid="e02">equation 2</xref>.</p>
<p>The resulting equation for composite storage is represented (<xref ref-type="bibr" rid="r69">Hanson, 1988</xref>) as follows:<disp-formula id="e02"><named-content content-type="math"><italic>S*</italic> = <italic>S</italic> + <italic>S<sub>y</sub></italic></named-content><label>(2)</label></disp-formula>where</p>
<def-list list-type="equation-where"><def-item><term><named-content content-type="math"><italic>S*</italic></named-content></term>
<def>
<p>is the total storage of the aquifer layer,</p></def></def-item><def-item><term><named-content content-type="math"><italic>S</italic></named-content></term>
<def>
<p>is the elastic specific storage, and</p></def></def-item><def-item><term><named-content content-type="math"><italic>Sy</italic></named-content></term>
<def>
<p>is the specific yield from water table drainage for unconfined portions of an aquifer.</p></def></def-item>
</def-list>
<p>The elastic specific storage (<italic>S</italic>) from <xref ref-type="disp-formula" rid="e02">equation 2</xref> can be further represented by its respective components as follows:<disp-formula id="e03"><named-content content-type="math"><italic>S = b * S<sub>s</sub> = &#x03C1;g(a + n&#x03B2;) * b</italic></named-content><label>(3)</label></disp-formula>where</p>
<def-list list-type="equation-where"><def-item><term><named-content content-type="math"><italic>&#x03C1;g</italic></named-content></term>
<def>
<p>is the weight of water,</p></def></def-item><def-item><term><named-content content-type="math"><italic>&#x03B1;</italic></named-content></term>
<def>
<p>is the compressibility of coarse- or fine-grained facies matrix material,</p></def></def-item><def-item><term><named-content content-type="math"><italic>n</italic></named-content></term>
<def>
<p>is the total porosity of the coarse- or fine-grained facies,</p></def></def-item><def-item><term><named-content content-type="math"><italic>b</italic></named-content></term>
<def>
<p>is the cell-by-cell thickness of the aquifer layer,</p></def></def-item><def-item><term><named-content content-type="math"><italic>&#x03B2;</italic></named-content></term>
<def>
<p>is the compressibility of water, and</p></def></def-item><def-item><term><named-content content-type="math"><italic>Ss</italic></named-content></term>
<def>
<p>is the total specific storage.</p></def></def-item>
</def-list>
<p>The elastic specific storage of water (<xref ref-type="disp-formula" rid="e03">eq. 3</xref>) is dependent on the specified porosities for the coarse- and fine-grained facies of each hydrogeologic unit (model layer). The product of average porosity and the compressibility of water (1.4x10<sup>&#x2212;6</sup> ft<sup>&#x2212;1</sup>) yields one part of the composite aquifer specific storage value. Accordingly, the porosity and compressibility of the fine and coarse end members of each hydrogeologic unit were estimated during parameter estimation. Storage properties in the outcrop subregions (<xref ref-type="fig" rid="fig28">fig. 28<italic>A</italic></xref>) of the uppermost layers (layers 1, 3, 5, 7, or 9) are represented by specific yield and are adjusted as necessary to represent the unconfined portion of the system. For the parts of hydrogeologic units that represent areas of the aquifers that are unconfined, aquifers were simulated as confined. This simplifying assumption has been applied in complex regional integrated hydrologic models (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>) and is further discussed in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.ModelUncertaintyLimitationsandPotentialImpr">Model Uncertainty, Limitations, and Potential Improvements</xref>&#x201D; section.</p>
<fig id="fig28" position="float" fig-type="figure"><label>Figure 28</label><caption><p>Hydrogeologic unit <italic>A</italic>, specific yield; and <italic>B</italic>, thickness for the uppermost layer of each model cell in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California. The uppermost layer is a composite of hydrogeologic units in the uppermost cell in layers 1, 3, 5, 7, 8, or 9 (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>28.</bold>	Maps showing hydrogeologic unit specific yield and thickness for the uppermost layer of each model cell in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>28. In general, the uppermost layer for each model cell is less than 100-feet thick, with a high specific yield.</long-desc><graphic xlink:href="sac23-0784_fig28"/></fig>
</sec>
<sec>
<title>Hydraulic Conductivity</title>
<p>Hydraulic conductivities generally decrease with depth and with increasing distance from the original sediment source (eroded and [or] transported from the adjacent mountain ranges and river channels), which is consistent with colluvial, fluvial, and eolian processes that resulted in fining upward and fining toward the center (distal) sequences observed in aquifer sediments in the SVGF. These expected behaviors can be observed in the horizontal and vertical hydraulic conductivity plots of each aquifer (<xref ref-type="fig" rid="fig29">fig. 29<italic>A</italic>&#x2013;<italic>F</italic></xref>). In several subregions, smaller values of hydraulic conductivity were estimated in fine-grained facies that may also reflect secondary alteration, such as cementation. Coarse-grained sediments are represented near stream channels in the alluvium. Coarse and fine end member values of hydraulic conductivity were used to make initial estimates of the horizontal and vertical hydraulic conductivity for each cell in each hydrogeologic unit in the model. <xref ref-type="bibr" rid="r48">Faunt and others (2009b)</xref> identified the power mean as a useful means for estimating hydraulic conductivity values. This approach specifies a power exponent for each hydrogeologic unit that is adjusted during model parameter estimation. A power exponent equal to 1.0 indicates the hydraulic conductivity is the weighted arithmetic mean of the hydraulic conductivities of the coarse-grained and fine-grained lithologic end members and the sediment texture for each model cell. In each hydrogeologic unit, the fine-grained lithologic end member hydraulic conductivity is much smaller than the coarse-grained lithologic end member hydraulic conductivity; thus, the arithmetic mean heavily weights the coarse-grained end member. For horizontal hydraulic conductivity, the arithmetic mean was assumed. Vertical hydraulic conductivity between model layers was calculated as the weighted power mean of the hydraulic conductivities of the coarse- and fine-grained lithologic end members (<xref ref-type="bibr" rid="r47">Faunt and others, 2009a</xref>). The harmonic mean is a weighted power mean with the power law exponent equal to &#x2212;1.0, resulting in increased vertical anisotropy. The geometric mean is a weighted power mean with the power law exponent equal to 0.0 and results in decreased vertical anisotropy. <xref ref-type="bibr" rid="r137">Phillips and Belitz (1991)</xref> determined that vertical conductivities could be calculated by using either weighted harmonic or weighted geometric means. <xref ref-type="bibr" rid="r6">Belitz and others (1993)</xref> represented the vertical conductivities with the weighted harmonic mean. <xref ref-type="bibr" rid="r48">Faunt and others (2009b)</xref> calculated the vertical conductivities as power means in which the power mean exponent varied between &#x2212;1.0 (the harmonic mean) and 0.0 (the geometric mean). The vertical hydraulic conductivity is sensitive to the averaging method used. Both the harmonic and geometric means more heavily weight the fine-grained end member, and, as a result, the calculated vertical hydraulic conductivity is much lower than the horizontal. <xref ref-type="bibr" rid="r41">Dimitrakopoulos and Desbarats (1993)</xref> determined that the value of the power law exponent depended to some extent on the size and thickness of the grid blocks used to discretize the model domain; smaller grid cells resulted in smaller values of the power law exponent. An initial value of the power law exponent was set for each model layer and adjusted during model parameter estimation.</p>
<fig id="fig29" position="float" fig-type="figure"><label>Figure 29</label><caption><p>Horizontal and vertical hydraulic conductivity in the six aquifer hydrogeologic units in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing <italic>A</italic>, shallow aquifer; <italic>B</italic>, 180-Foot Aquifer; <italic>C</italic>, 400-Foot Aquifer; <italic>D</italic>, Paso Robles Formation; <italic>E</italic>, Purisima Formation; and <italic>F</italic>, bedrock (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>29.</bold>	Maps showing horizontal and vertical hydraulic conductivity in the six aquifer hydrogeologic units in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing shallow aquifer, 180-Foot Aquifer, 400-Foot Aquifer, Paso Robles Formation, Purisima Formation, and bedrock</p></caption><long-desc>29. Hydraulic conductivities tend to decrease with depth and with increasing distance from the original sediment source.</long-desc><graphic xlink:href="sac23-0784_fig29a"/><graphic xlink:href="sac23-0784_fig29b"/><graphic xlink:href="sac23-0784_fig29c"/><graphic xlink:href="sac23-0784_fig29d"/><graphic xlink:href="sac23-0784_fig29e"/><graphic xlink:href="sac23-0784_fig29f"/></fig>
</sec>
<sec>
<title>Faults</title>
<p>Some faults within the model domain cut across some of the hydrogeologic units; these faults are simulated as potential hydrologic flow barriers (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>). Many faults are on the western edge of the model and offshore. For computational convenience and to maintain consistency with published interpretations (<xref ref-type="bibr" rid="r65">Greene, 1977</xref>; <xref ref-type="bibr" rid="r52">Feeney and Rosenberg, 2003</xref>), all faults in the study area were generalized as vertical boundaries, with locations shown on <xref ref-type="fig" rid="fig22">figure 22<italic>A</italic></xref>. Some faults intersect more than one hydrogeologic unit and extend outside of the defined groundwater basins. The MODFLOW Horizontal Flow Barrier package (<xref ref-type="bibr" rid="r101">Hsieh and Freckelton, 1993</xref>) was used to simulate resistance to horizontal flow across these structures. The effectiveness of these faults as partial flow barriers to horizontal flow was then estimated by five parameters representing the conductance of the vertical model cell faces aligned with the fault trace. These parameters were specified based on the hydrogeologic unit onshore (180-Foot Aquifer, 400-Foot Aquifer, Purisima Formation, and basement aquifer) and by age in the offshore region (Quaternary or older). Groundwater levels at selected wells that straddle the faults show lateral head differences that may also reflect a combination of screened depths and the faults acting as flow barriers. Barriers to horizontal groundwater flow in the integrated hydrologic models were represented using the Horizontal Flow Barrier package across the model cell faces of 34,932 model cells.</p>
</sec>
<sec>
<title>Initial Conditions</title>
<p>The initial October 1967 groundwater levels in all active cells were set as a composite of water-table contours estimated using available groundwater elevation records and of an assumed correspondence between potentiometric surface contours and surface topography in upland areas of aquifers where limited measurements were available. The initial condition of groundwater elevations in the model was refined during parameter estimation. Defining a steady-state initial condition for the model is not warranted because substantial groundwater pumpage was already occurring before 1967. Salinas Valley groundwater development started in the 1890s with groundwater pumpage from windmills, and more development occurred in the 1920s and 1940s (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>). A steady-state or pre-development initial condition assumes that groundwater flows are affected primarily by the natural cycles of climate variability with no effects of regulated streamflows or groundwater pumpage affecting changes in groundwater levels. Although multiple periods of historical conditions could be defined to represent pre-development conditions and stages of development, data are limited, and the period of interest in this study is focused on more recent periods when reservoirs were operating. Defining a steady-state initial condition for the model is highly uncertain. The initial conditions used in the integrated hydrologic models represent composite estimates of hydrologic conditions after extensive groundwater development for irrigation in the 1920s. With little historical information about aquifer stresses, such as pumpage or climate variability, arriving at a potentially less uncertain set of initial conditions is difficult. The initial conditions were further refined by periodically adjusting scale factors for each layer and region as refinements to estimates of initial heads during parameter estimation. This adjustment of scaling parameters of the overall elevation of initial groundwater levels helped refine the initial heads for all nine model layers during parameter estimation.</p>
<p>For transient models, initial conditions define the system state at the beginning of the simulation. When the simulation is started, the simulated heads and flows change in response to the initially specified and simulated inflows and outflows. Because the irrigation and pumping stress on the system change rapidly, the inconsistencies between the initially specified conditions and the simulated initial processes and properties generally are not problematic because the magnitudes of the next stress regime (for example, pattern of pumpage) soon dominate the solution (<xref ref-type="bibr" rid="r100">Hill and Tiedeman, 2007</xref>). As a result, comparing observed and simulated values becomes meaningful after a relatively short simulation time. This study and previous studies (<xref ref-type="bibr" rid="r7">Belitz and Phillips, 1995</xref>; <xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>) show that the time frame for stabilization is typically less than several months to several years of the simulation, depending on the magnitude of the changes in the stresses that drive inflows and outflows and the overall hydraulic diffusivity of the aquifer systems. The initial conditions are regularly updated during model parameter estimation to develop stable starting conditions. For the water budget analyses in the historical model, WY 1968 and 1969 are considered spin-up years, and analysis of water budgets begins with WY 1970.</p>
</sec>
</sec>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.ParameterEstimationandHistoryMatchingSalinas">
<title>Parameter Estimation and History Matching&#x2014;Salinas Valley Integrated Hydrologic Model</title>
<p>The historical model, SVIHM, was used to simulate historical conditions and represent historical observations (history matching). Therefore, parameter estimation used to calibrate the integrated hydrologic models is focused on the historical model. The operational model, SVOM, relies on the historical model properties derived from parameter estimation. Simulation with integrated hydrologic models can require specification of several hundred parameters that vary spatially and temporally, some of which are correlated through their process-based relations; thus, developing an optimized set of calibrated parameter values within an integrated hydrologic model can be challenging. Accordingly, a parameterization procedure was employed that allows a limited number of parameter values to control the temporal and spatial variability of a much larger number of model properties specified as inputs. The parameterization procedure followed that of <xref ref-type="bibr" rid="r100">Hill and Tiedeman (2007)</xref> in defining the term &#x201C;parameters&#x201D; to mean model inputs of hydraulic and hydrologic properties; this definition was extended to include landscape and land-use-related properties from the FMP.</p>
<sec>
<title>Parameter Estimation</title>
<p>The following subsections summarize the (1) parameter estimation method and application; (2) observations used for parameter estimation, including how observations were processed and weighted; (3) description of parameters; and (4) parameter sensitivity analysis. Parameter estimation employed a combination of trial-and-error and computer-assisted processes of minimizing differences between &#x201C;real-world&#x201D; observations and their simulated equivalent values. Parameter estimation requires more than just matching historical observations by estimating parameters, it also requires adjustments in the conceptual framework of the integrated hydrologic models to integrate information obtained during parameter estimation and to improve numerical instabilities&#x2014;for example, making small alterations to hydrogeologic unit layer elevations within the uncertainty of the geologic framework from which they are defined. The result of this iterative process is a more consistent framework for parameter estimation. Once the structural framework is consistent, then observations and parameters can be compiled and grouped.</p>
<p>The parameter estimation software package (PEST Highly Parallelized; PEST-HP; <xref ref-type="bibr" rid="r42">Doherty, 2024</xref>) was used for the computer-assisted parameter estimation and sensitivity analyses. The PEST-HP is a serial parameter-estimation program that allows execution of parallel model runs on multiple computers. PEST-HP uses the Gauss-Levenberg-Marquardt algorithm to systematically adjust parameter values to find a minimum of an objective function over a space of parameters. To improve parameter estimation, the correlation among parameters was addressed, where possible, using singular value decomposition to reduce the total number of parameters into super-parameters that represent more than one parameter. Tikhonov regularization (<xref ref-type="bibr" rid="r42">Doherty, 2024</xref>) was employed to prevent parameter overfitting. Regularization also adds stability to the parameter estimation process because parameters that are insensitive to observations do not change values during each PEST-HP iteration (<xref ref-type="bibr" rid="r42">Doherty, 2024</xref>). The objective function is the sum of squared, weighted residuals between observed values and their simulated equivalents. For each parameter, an initial value and range is specified. The observations are grouped and weighted to ensure that the observation measurement scale does not affect its contribution to the objective function and that the simulation focuses on the information obtained from observations that can be replicated by the simulation.</p>
<p>Many simulated hydrologic fluxes are head dependent or were correlated through their exchange of water (flow dependent); thus, parameters controlling each set of processes were adjusted through automated and trial-and-error analysis. Initial parameter estimation was performed in a stepwise format that started with the landscape processes, followed by adjustment of hydraulic properties, streambed properties, multiple-aquifer well properties, general-head boundary conductance, and fault conductance. The parameter estimation process also required modifications to the parameter framework. For example, parameters and observations for the surface-water drainage network were further partitioned, and climate and efficiency factors were included for improved consumptive-use and related agricultural pumpage estimates. Parameter estimation was later limited to a subset of parameters using composite scaled sensitivity analyses to define meaningfully sensitive parameters. Even though some parameters demonstrated substantial correlations, those parameters selected for parameter estimation were assumed to be independent or were calibrated in a stepwise manner to minimize the effect of parameter correlation. Observations were classified, grouped, and weighted to ensure that simulated hydrologic flows in the integrated hydrologic models represent the important hydrologic flows (for example, agricultural water supply) and changes in regional groundwater levels. The weighting of observation groups in parameter estimation is described further in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.ObservationWeighting">Observation Weighting</xref>&#x201D; section. Parameter adjustments were based on the comparison of observed values to their simulated equivalents. The simulated equivalent values were compared to all observed values and provided a measure of model performance through various historical time intervals and model analysis regions. The resulting error distributions constrain model parameters, and the comparison between simulated and observed values provided a basis for a sensitivity analysis of selected parameters.</p>
<sec>
<title>Observation Data</title>
<p>The parameter estimation includes observation data for the period from October 1967 to December 2014. Observations representing groundwater conditions include groundwater levels, temporal changes in groundwater levels (drawdowns), vertical gradients in groundwater levels between units, published changes in groundwater level contours, aggregated agricultural groundwater pumpage by WBS, and streamflow differences among upstream and downstream gages. Observations representing surface-water conditions include surface-water flows along the Salinas River and in rivers within the integrated hydrologic model domain at USGS streamgaging stations, canals/laterals, and drains where data were available, as well as flow-differences between gages (<xref ref-type="fig" rid="fig20">fig. 20</xref>; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p>
<sec>
<title>Surface Water</title>
<p>Surface-water flow data used to develop observations for parameter estimation include monthly averaged streamflow data (<xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>) at gages along the Salinas River and its tributaries, Arroyo Seco and Reliz Creek (<xref ref-type="fig" rid="fig20">fig. 20</xref>); available surface-water diversions records (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>); and flow differences between selected streamgages (<xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>). Where sufficient measurements were available, surface-water data were averaged to quarterly and annual mean values as additional observations for parameter estimation. Pairs of USGS gages were selected for flow-difference observations on the major tributaries: Arroyo Seco and Reliz Creek (USGS 11152050 and USGS 11152000) and the USGS gages along the Salinas River (USGS 11150500, USGS 11151700, USGS 11152300, and USGS 11152500). Streamflow differences were computed as upstream minus downstream, meaning that negative values represent streamflow gains in the surface-water drainage network between the gages. There were 5,736 streamflow observations, 291 diversion observations, 2,508 streamflow difference observations, 2,011 quarterly mean streamflow observations, and 527 annual mean streamflow observations. Each observation was classified into subgroups based on observed low flow (flow less than 25 ft<sup>3</sup>/s), stream name (Salinas River or Arroyo Seco), differences, or diversions.</p>
</sec>
<sec>
<title>Groundwater</title>
<p>Groundwater-level histories are largely restricted to the Salinas Valley floor. The largest set of observed values used for parameter estimation were groundwater levels and changes in groundwater levels over time. The dataset used for parameter estimation consists of groundwater-level measurements from WY 1968 to 2014 from 439 single and multiple-aquifer wells and multi-well monitoring sites (<xref ref-type="fig" rid="fig24">figs. 24<italic>A</italic></xref>, <xref ref-type="fig" rid="fig24">24<italic>B</italic></xref>). These groundwater-level measurements were developed into groundwater-level observations and drawdown observations. Where the frequency of measurement at a given well was sufficient, mean quarterly and mean annual groundwater level and drawdown observations were generated. Drawdown observations measure the change in groundwater level relative to the first head observation for the time span of measurements from each well. A negative drawdown value represents a lowering of groundwater levels. To represent the overall trend in heads throughout the region and to minimize the potential effects of initial conditions, a set of drawdown observations were made for each well. There were 459 monthly groundwater-level observations and 50,992 monthly drawdown observations; 11,942 quarterly mean groundwater-level observations and 11,942 quarterly drawdown observations; 5,415 annual mean groundwater-level observations and 5,415 annual mean drawdown observations; and 1,576 head difference observations.</p>
<p>During the development of groundwater-level and drawdown observations for parameter estimation, the effects of local and regional pumpage were considered. The density of pumping wells in each of the analysis regions (<xref ref-type="fig" rid="fig30">fig. 30</xref>) can be substantial (<xref ref-type="fig" rid="fig24">figs. 24<italic>A</italic></xref>, <xref ref-type="fig" rid="fig24">24<italic>B</italic></xref>). Moreover, 340 of the 439 observation wells are also agricultural supply wells. For these wells, there is an unknown pumping time series and no information about when these wells or adjacent wells were pumping relative to the time of groundwater-level measurement. Thus, data from these wells were carefully managed during parameter estimation. Seasonal oscillations in these wells are not expected to be well matched because the well pumping rates simulated in the models are not simulated using time series from individual well owners but are based on the water demands of the WBS across all available wells. The groundwater-level and drawdown observations are classified into one of two classes depending on if they were potentially affected by pumping (pumping affected) or not. This classification is based on the following conditions: the observation well is also an agricultural supply well, and the measurement occurs in the peak growing season from March through September. This classification does not capture every measurement that could be affected by pumping because pumping occurs year-round. However, it does help delineate the measurements that are most likely to be affected by pumping. Groundwater level and drawdown observations for a historical dry period from WY 1984 to 1994 were grouped by analysis region and if they were affected by pumping, then further grouped by quarterly mean values and by annual mean values.</p>
<fig id="fig30" position="float" fig-type="figure"><label>Figure 30</label><caption><p>Analysis regions in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing locations of selected observation wells.</p><p content-type="toc"><bold>30.</bold>	Map showing analysis regions in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing locations of selected observation wells</p></caption><long-desc>30. There are two to three analysis wells in each analysis region.</long-desc><graphic xlink:href="sac23-0784_fig30"/></fig>
</sec>
<sec>
<title>Agricultural Pumpage</title>
<p>The monthly agricultural pumpage reported by the Groundwater Extraction Management System was aggregated by WBS (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>), spanning the period from November 1994 through December 2014. Before November 1994, when monthly agricultural pumpage observations were not available, simulated annual agricultural pumpage was compared to published long-term estimates (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). The monthly agricultural pumpage data were averaged to generate quarterly and annual average observations for each WBS. In addition, monthly observations from each WBS were aggregated to the analysis regions (<xref ref-type="fig" rid="fig15">fig. 15</xref>; <xref ref-type="bibr" rid="r91">Henson and Jachens, 2022</xref>). There are 3,630 monthly, 1,215 quarterly, and 315 annual agricultural observations.</p>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.ObservationWeighting">
<title>Observation Weighting</title>
<p>During parameter estimation, observations were weighted. The sensitivity of a parameter is also dependent on the observation weights. Observation weights are used for a variety of purposes, including accounting for differences in measurement units and quantification of measurement error; they are sometimes imposed to help distribute the importance of observations across many different types of observations (for example, to remove the effects of spatial or temporal clustering of measurements or to emphasize areas where a model will be used to make predictions). The weighting of observations helps to determine how the contribution to the objective function is distributed among the various types of observations. This weighting procedure also helps ensure that the parameter estimation only considers observations that the model can reproduce given data and model limitations, including observations that the model cannot reproduce that can lead to parameter compensation and model structural error (<xref ref-type="bibr" rid="r172">White and others, 2021</xref>). Therefore, some observations were weighted near zero or scaled to focus parameter estimation on observations of interest. For example, observations for the first 2 years of the simulation had reduced weights to allow for the parameter estimation to focus on the period after the assumed 2-year model spin-up. There were many parameter estimation iterations that alternated between trial and error and PEST-HP. Through this process, observations were regularly reweighted so that the objective function was updated and the contribution of error from each observation group was equalized.</p>
<p>Each observation group type (surface-water, groundwater, and agricultural pumpage) was weighted to represent about one-third of the total error; subgroups (for example, low flows) within each observation group were weighted differently. Within the stream observation group, selected streamflow observations in the stream network were given relatively more importance to the parameter estimation if they affected pumpage and groundwater levels, specifically those within the main channel of the Salinas River, diversion locations, and places where reservoir operational target flows were defined. The low flows and all other flows were equally weighted, ensuring parameters that control high and low flows affected model parameter estimation. High flows are driven primarily by precipitation runoff, whereas low flows are typically driven by irrigation runoff and groundwater and surface-water exchange. Many of the groundwater level observations in the model were affected by pumping or occurred in wells that were used for groundwater supply. The observations associated with these agricultural supply wells were weighted lower than other wells, and the observations that represented annual minima of groundwater levels were assigned zero weights. The observations associated with annual mean groundwater levels and drawdowns were increased to twice the weight of other groundwater level and drawdown observations. The monthly and quarterly mean agricultural pumpage observations were weighted based on their fraction of total agricultural pumpage reported in the Groundwater Extraction Management System. These weights were doubled for annual average agricultural pumpage observations.</p>
</sec>
<sec>
<title>Parameters</title>
<p>The number of adjustable parameters changed during parameter estimation. A total of 311 parameters were created initially to facilitate model parameter estimation, and after initial global sensitivity and parameter estimation, about 40 parameters were determined to be relatively sensitive and were included in the computer-assisted and trial-and-error parameter estimation process (<xref ref-type="fig" rid="fig31">fig. 31</xref>; <xref ref-type="table" rid="t06">table 6</xref>). All other parameters were less sensitive than the least sensitive parameter shown on <xref ref-type="fig" rid="fig31">figure 31</xref>. The full enumeration of parameters is provided by <xref ref-type="bibr" rid="r86">Henson and Culling (2025)</xref>. These parameters included aquifer conductivity, aquifer storage, climate scale factors, drain conductance, runoff, and stream conductance parameters. As discussed, hydraulic properties were initially assigned values based on previous modeling studies, then adjusted during model parameter estimation. Model parameters were adjusted within ranges of reasonable values to best-fit historical hydrologic conditions (history matching) and observations in the groundwater, surface-water network, and landscape.</p>
<fig id="fig31" position="float" fig-type="figure"><label>Figure 31</label><caption><p>Magnitudes of the relative composite scaled sensitivity for selected parameters of the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California. Refer to <xref ref-type="table" rid="t06">table 6</xref> for a full description of the sensitive parameter names and values. All model parameters are described by <xref ref-type="bibr" rid="r86">Henson and Culling (2025)</xref>.</p><p content-type="toc"><bold>31.</bold>	Graph showing magnitudes of the relative composite scaled sensitivity for selected parameters of the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>31. Of the 40 relatively sensitive parameters, 13 are climate scale factors and 10 are aquifer conductivity.</long-desc><graphic xlink:href="sac23-0784_fig31"/></fig>
<table-wrap id="t06" orientation="landscape" position="float"><label>Table 6</label><caption>
<title>Summary of sensitive calibration parameters from composite scaled sensitivity analyses for the Salinas Valley Integrated Hydrologic Model.</title>
<p content-type="toc"><bold>6.</bold>	Summary of sensitive calibration parameters from composite scaled sensitivity analyses for the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties, California</p>
<p>[ft/day, foot per day]</p></caption>
<table rules="groups">
<col width="17.08%"/>
<col width="11.48%"/>
<col width="44.46%"/>
<col width="9.71%"/>
<col width="6.86%"/>
<col width="10.41%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Parameter type</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Parameter name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Parameter description</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Conductance (ft/day)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Rank</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Composite <break/>scaled <break/>sensitivity<sup>1</sup></td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Stream conductance</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">salriv_lcr</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Salinas River stream segments near the coast</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">4.15</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream conductance</td>
<td valign="top" align="left">salriv_lv</td>
<td valign="top" align="left">Salinas River stream segments in the lower central valley</td>
<td valign="top" align="char" char=".">8.08</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">0.6</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Stream conductance</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">salriv_cv</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Salinas River stream segments located near the center of the valley</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.66</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">15</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream conductance</td>
<td valign="top" align="left">salriv_cvl</td>
<td valign="top" align="left">Salinas River stream segments located near the center of the valley</td>
<td valign="top" align="char" char=".">5.36</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="char" char=".">0.8</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Stream conductance</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">wch_as</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Arroyo Seco stream segments</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">6.93</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.6</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream conductance</td>
<td valign="top" align="left">cst_ditch</td>
<td valign="top" align="left">Central coastal region ditch</td>
<td valign="top" align="char" char=".">12.96</td>
<td valign="top" align="char" char=".">29</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Multiplier</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">l1hkpressure</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Layer 1 pressure lateral hydraulic conductivity</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.75</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer conductivity</td>
<td valign="top" align="left">l7hkrip</td>
<td valign="top" align="left">Layer 7 riparian lateral hydraulic conductivity</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">33</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">l2vk</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Layer 2 vertical hydraulic conductivity</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Conductance (ft/day)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_ly1</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Hydraulic conductivity end member for 100-percent coarse</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">141</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer conductivity</td>
<td valign="top" align="left">kf_ly2</td>
<td valign="top" align="left">Hydraulic conductivity end member for 0-percent coarse</td>
<td valign="top" align="char" char=".">0.01</td>
<td valign="top" align="char" char=".">37</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_ly3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Hydraulic conductivity end member for 100-percent coarse</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">160</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer conductivity</td>
<td valign="top" align="left">kc_ly5</td>
<td valign="top" align="left">Hydraulic conductivity end member for 100-percent coarse</td>
<td valign="top" align="char" char=".">161</td>
<td valign="top" align="char" char=".">22</td>
<td valign="top" align="char" char=".">0.4</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_ly7</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Hydraulic conductivity end member for 100-percent coarse</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">90.4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">21</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.4</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Value (unitless)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer conductivity</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">pl7</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Power law exponent layer 7 where aquifer is confined</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2.7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer conductivity</td>
<td valign="top" align="left">pl7u</td>
<td valign="top" align="left">Power law exponent layer 7 where aquifer is closer to surface in upper valley</td>
<td valign="top" align="char" char=".">0.1</td>
<td valign="top" align="char" char=".">16</td>
<td valign="top" align="char" char=".">0.4</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Scaling factor (ft/day)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer storage</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">sy_ly1c</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Specific yield of aquifer materials for 100-percent coarse</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">31</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage</td>
<td valign="top" align="left">sy_ly1f</td>
<td valign="top" align="left">Specific yield of aquifer materials for 0-percent coarse</td>
<td valign="top" align="char" char=".">0.13</td>
<td valign="top" align="char" char=".">39</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Multiplier (fraction)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer storage</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">l1ss</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Specific storage scaling factor layer 1 in upland areas of the valley</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Multiplier (fraction)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_norm_sum</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor normal year before 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.75</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">40</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_dry_win2</td>
<td valign="top" align="left">Crop coefficient climate scale factor dry year after 1995</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">18</td>
<td valign="top" align="char" char=".">0.4</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_dry_spr2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor dry year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.9</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_dry_sum2</td>
<td valign="top" align="left">Crop coefficient climate scale factor dry year after 1995</td>
<td valign="top" align="char" char=".">0.94</td>
<td valign="top" align="char" char=".">6</td>
<td valign="top" align="char" char=".">1.1</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_dry_fal2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor dry year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.55</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_norm_win2</td>
<td valign="top" align="left">Crop coefficient climate scale factor normal year after 1995</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">0.7</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_norm_spr2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor normal year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.08</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.9</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_norm_sum2</td>
<td valign="top" align="left">Crop coefficient climate scale factor normal year after 1995</td>
<td valign="top" align="char" char=".">0.96</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2.3</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_norm_fal2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor normal year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.27</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">13</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_wet_win2</td>
<td valign="top" align="left">Crop coefficient climate scale factor wet year after 1995</td>
<td valign="top" align="char" char=".">0.95</td>
<td valign="top" align="char" char=".">24</td>
<td valign="top" align="char" char=".">0.4</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_wet_spr2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor wet year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.01</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left">kc_wet_sum2</td>
<td valign="top" align="left">Crop coefficient climate scale factor wet year after 1995</td>
<td valign="top" align="char" char=".">0.95</td>
<td valign="top" align="char" char=".">4</td>
<td valign="top" align="char" char=".">1.7</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Climate-stress scale factor</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">kc_wet_fal2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Crop coefficient climate scale factor wet year after 1995</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1.1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">19</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.4</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Conductance (ft/day)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Drain conductance</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">drt_rip</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Drain conductance in model cells adjacent to Salinas River</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1,180</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">30</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<th colspan="6" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Multiplier (fraction)</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Runoff parameter</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">ag_pcpc</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Inefficient loss from precipitation factor for agricultural land uses</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.05</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Runoff parameter</td>
<td valign="top" align="left">ag_pcpc2</td>
<td valign="top" align="left">Inefficient loss from precipitation factor for agricultural land uses</td>
<td valign="top" align="char" char=".">0.05</td>
<td valign="top" align="char" char=".">34</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Runoff parameter</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">ag_pcpi</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Inefficient loss from precipitation factor for agricultural land uses</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.07</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Runoff parameter</td>
<td valign="top" align="left">ag_irrc</td>
<td valign="top" align="left">Inefficient loss from irrigation factor for agricultural land uses</td>
<td valign="top" align="char" char=".">0.05</td>
<td valign="top" align="char" char=".">25</td>
<td valign="top" align="char" char=".">0.4</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Runoff parameter</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">ag_irrc2</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Inefficient loss from irrigation factor for agricultural land uses</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.07</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Runoff parameter</td>
<td valign="top" align="left">ag_irri</td>
<td valign="top" align="left">Inefficient loss from irrigation factor for agricultural land uses</td>
<td valign="top" align="char" char=".">0.05</td>
<td valign="top" align="char" char=".">26</td>
<td valign="top" align="char" char=".">0.3</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Runoff parameter</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">semi_nati</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">Inefficient loss from precipitation factor for semi-agricultural land uses</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">35</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">0.3</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t06n1"><label><sup>1</sup></label>
<p>Composite scaled sensitivity computed using the parameter estimation software package highly parallelized (PEST-HP) for highly parallelized computing environments (<xref ref-type="bibr" rid="r42">Doherty, 2024</xref>).</p></fn>
</table-wrap-foot>
</table-wrap>
<sec id="sac23-0784_Final_20260508_kc.Landscape-ProcessParameters">
<title>Landscape-Process Parameters</title>
<p>Landscape-process parameters within FMP that were adjusted during parameter estimation included selected properties related to land use. Some parameters were fixed to initial estimated values, some were adjusted manually, and some were adjusted using PEST-HP. These included seasonal climate-stress scale factors and fractions of inefficient losses to runoff from irrigation and precipitation that vary by crop type. Climate-stress scale factors for crop demands represent factors, such as irrigation stress and climate-based changes in the crop demands (for example, hot and dry conditions). The climate-stress scale factors adjust crop demands in response to different climate regimes (for example wet, normal, or dry, and winter, spring, summer, or fall) and represent the effect of Kc stress factors (<xref ref-type="bibr" rid="r1">Allen and others, 1998</xref>) that amplify or reduce Kc values used to estimate agricultural demands. Estimation of Kc values typically occurs under unstressed conditions. These factors were adjusted during parameter estimation to improve the simulation of estimated pumpage. To align estimated agricultural pumpage with reported monthly pumpage and groundwater-level declines, adjustment factors for Kc were decreased from as much as &#x2212;25 percent and increased by as much as 55 percent, depending on the season and climate year type. Many of these climate-stress scale factors were sensitive and are shown in <xref ref-type="table" rid="t06">table 6</xref>. The fractions of irrigation losses and precipitation losses to surface-water runoff for all land uses are provided in the model archive (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). The fraction of irrigation losses to surface-water runoff was assumed to be relatively small and range from 0.1 percent for indoor nursery crops to 7 percent of outdoor nursery crops, with most values equal to 5 percent. The fraction of precipitation losses to surface-water runoff was assumed to be greater than the irrigation losses, with precipitation losses to surface water ranging from 5 to 7 percent for agricultural areas, 40 percent for grasslands, and 100 percent for the riparian areas. Excess applied irrigation was assumed to contribute mostly to deep percolation to groundwater, along with subsequent lateral flow and capture by nearby drain canals.</p>
</sec>
<sec>
<title>Hydraulic Parameters</title>
<p>The historical model was calibrated to estimate values of hydraulic properties within each hydrogeologic zone within each model layer. Parameters include the values of horizontal and vertical hydraulic conductivity and specific storage for each facies zone within each hydrogeologic unit and the power law exponents for vertical hydraulic conductivity. Defining these three parameters for each of the 47 textural zones across all hydrogeologic units (<xref ref-type="fig" rid="fig27">figs. 27<italic>A</italic>&#x2013;<italic>F</italic></xref>) yields 88 parameter values for horizontal and vertical hydraulic conductivities and 9 multipliers for storage properties. An additional group of 18 parameters for specific storage, porosities, and specific yields were included using the MODFLOW MULT package that was used to build the specific storage values and horizontal and vertical values for hydraulic conductivity. For the specific storage formulation, the compressibility of water was held constant. Specific yield was specified as a component of the storage properties proportional to the estimated porosity.</p>
<p>The parameter estimation of hydraulic properties required the adjustment of horizontal and vertical hydraulic conductivity and rescaling of specific storage based on groundwater-level hydrographs and vertical head differences. The most sensitive parameters were vertical hydraulic conductivities that, in part, controlled the seasonal amplitudes and vertical water-level differences between aquifer layers. Other sensitive parameters include the hydrogeologic unit power law exponents used to define vertical hydraulic conductivity values in each cell (using a weighted power mean of the hydraulic conductivities of coarse- and fine-grained lithologic end members; <xref ref-type="bibr" rid="r47">Faunt and others, 2009a</xref>). Reductions in vertical hydraulic conductivity and storage properties were required for some confined zones, and scaled increases in these properties were required for certain unconfined zones. Horizontal hydraulic conductivities (represented by the hydraulic conductivity of the subregional facies) were increased during model parameter estimation in many of the hydrogeologic units. Specific yield was assigned to each upper active cell. During calibration, a multiplier was used for each zone to determine the final range in specific yield. Specific yield values ranged from a maximum 0.14 for the shallow aquifer to 0.05 for the basement aquifer (<xref ref-type="table" rid="t04">table 4</xref>).</p>
</sec>
<sec>
<title>Horizontal-Flow Barrier Parameters</title>
<p>The model cells represented by the horizontal flow barrier package were combined by faults and fault groups into six parameter groups that have hydraulic characteristics specified as adjustable parameters. The characteristic values are used to rescale row and column conductances for the model cell face between the adjacent model cells that are coincident with the trace of the barrier. In addition, the faults were combined into groups first based on their assigned recency of faulting (youngest age of faulted units) and then grouped based on orientation of faulting. Based on their tectonic setting, the north-south trending faults were assumed to be a barrier with lower characteristic values; computer-assisted and manual parameter estimation confirmed relatively low parameter values (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). Fault conductances were initially model-estimated parameters but ultimately were specified at low values that were held constant for final calibration. These low conductances are consistent with discontinuities observed in groundwater levels of selected wells in the Langley Area groundwater subbasin.</p>
</sec>
<sec>
<title>Regional Groundwater Flow and Seawater Coastal Inflow Parameters</title>
<p>The conductance factors in the GHB package, which simulated regional groundwater flow, were specified in groups of model cells and were manually adjusted as constant values within each group of boundary cells (<xref ref-type="fig" rid="fig25">fig. 25</xref>). These GHB conductance values controlled the small inflows to and from the Pajaro River groundwater basin in the northwest corner of the integrated hydrologic model domain and underflow in the aquifer beneath the Salinas River from the Paso Robles Area groundwater subbasin in the southeast part of the model domain. These GHB conductance values range from 1.9 to 552 square feet per day (ft<sup>2</sup>/d) near the Pajaro River groundwater basin (WBS 6) and are 535 ft<sup>2</sup>/d near the Paso Robles Area groundwater subbasin (WBS 29). For seawater coastal inflow, the general head boundaries represent vertical boundaries instead of horizontal boundaries. Therefore, conductance values for the seawater coastal inflow GHB have a larger magnitude because the cross-sectional areas they represent at the boundary are different. The offshore GHB conductance values range from 596 to 6,590 ft<sup>2</sup>/d.</p>
</sec>
<sec>
<title>Single and Multiple-Aquifer Well Parameters</title>
<p>The flowrate to each single and multiple-aquifer well from each aquifer depends on aquifer properties, including hydraulic head. This flowrate is restricted by flow through the well screen and the narrow zone of formation damage that was created during the well drilling process. This zone of restriction is known collectively as the skin, and the hydraulic conductivity of the skin is selected as the only adjustable parameter for multiple-aquifer wells. The skin factor affects the interlayer flow that occurs as wellbore flow and related vertical water-level difference between model layers. Eighteen skin factors were used as parameters to control the delay of wellbore flow within all layers screened for all multiple-aquifer wells. Wells were assigned skin-factor parameters based on whether they were constructed before 1960 (old) or after 1960 (new) and have casing diameters less than or equal to 5 in. (small) or greater than 5 in. (large), resulting in five parameter groups. The calibrated values of these parameters were relatively large to maintain the observed vertical head differences and to control wellbore flow between layers. The final calibrated skin factors ranged from 25.3 to 40 feet per day (ft/d) for the older, small-diameter wells and from 10.3 to 89.5 ft/d for the newer, large-diameter wells.</p>
</sec>
<sec>
<title>Surface-Water Network and Drain Return Flow Parameters</title>
<p>For the surface-water drainage network infrastructure, all channel geometry parameters were held constant, and the only adjustable parameter is the vertical hydraulic conductivity of the bed material. This conductivity controls the leakage rate to or from the surface-water feature, which, in turn, controls artificial recharge, shallow groundwater heads, and conveyance of water throughout the network. Stream, canal, drain, and arroyo segments were combined into groups with similar channel properties, yielding 26 adjustable parameters for streambed hydraulic conductivity (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). Natural stream channels were separated into groups representing the Salinas River and its tributaries or adjacent surface-water drainage networks within the model domain, which resulted in 26 groups of multiple segments that span 524 segments. The parameter grouping of segments within the Salinas River was based on the general distributions of gains and losses estimated from seepage runs. The parameterization of the Salinas River streambed was subdivided into four parameter groups representing the upper middle, lower, and tidal portions of the valley. The final distribution of parameter groups of streambed vertical hydraulic conductivities for the calibrated values ranges from 0.0001 ft/d at the coast in the Pressure analysis region of the Salinas River to as much as 11.34 ft/d along some tributaries in the East Side-Langley analysis region (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). For the DRT input, drain conductances were specified for each drain type: riparian was 1,180 ft<sup>2</sup>/d, tributary was 3,780 ft<sup>2</sup>/d, and land surface was 3,390 ft<sup>2</sup>/d.</p>
</sec>
</sec>
<sec>
<title>Parameter Sensitivity Analysis</title>
<p>Computer-assisted parameter-estimation techniques using PEST-HP (<xref ref-type="bibr" rid="r43">Doherty and Hunt, 2010</xref>; <xref ref-type="bibr" rid="r42">Doherty, 2024</xref>) primarily were used to estimate selected model parameters and related sensitivities, but additional insight was provided by trial-and-error analyses. PEST-HP computes the sensitivity of simulated values to changes in model parameters at the locations of measurements. Sensitive parameters were identified (<xref ref-type="fig" rid="fig31">fig. 31</xref>), which helped guide which parameters were adjusted during the parameter estimation process (<xref ref-type="bibr" rid="r99">Hill and others, 2000</xref>). The measure of parameter sensitivity used to remove insensitive parameters was composite scaled sensitivities (<xref ref-type="bibr" rid="r100">Hill and Tiedeman, 2007</xref>). Composite scaled sensitivities indicate the information content of all observations for the estimation of a parameter and provide insight into parameter importance and sensitivity.</p>
<p>The most sensitive parameter was the power law exponent for distributing the texture distribution within layer 7 in the Pressure and Forebay analysis regions. This aquifer is closest to the surface in the Upper Valley analysis region (<xref ref-type="fig" rid="fig22">fig. 22<italic>A</italic></xref>), so the textural distribution where layer 7 is deeper may be important for transmission of recharge in the Upper Valley analysis region toward the coast in deeper aquifers. The next set of important parameters were the climate scale factors that represent seasonal stress adjustments for Kc values. An additional sensitive parameter was the streambed conductance in the Upper Valley analysis region between the USGS 11150500 and USGS 11151700 gages, where substantial stream leakage has been documented (<xref ref-type="fig" rid="fig21">fig. 21</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Similarly, the sensitivity of the streambed conductance between the USGS 11151700 and USGS 11152300 gages was substantial for the same reasons. Other sensitive parameters include hydraulic conductivity (kc_ly1, l1hkpressure), specific storage (l1ss), and specific yield (sy_ly1c) of the shallow aquifer. The sensitivity of the parameters that govern (1) recharge and storage in the shallow aquifer, (2) streambed conductance, and (3) climate factors that affect agricultural demand simulation are to be expected given that the primary recharge to the aquifer from precipitation and agricultural return flows is affected by the storage and hydraulic conductivity of layer 1 and the Salinas River, and agricultural demands are such a substantial portion of the total water demand.</p>
</sec>
</sec>
<sec>
<title>History Matching Results</title>
<p>The ability of the integrated hydrologic models to simulate the hydrologic system was evaluated based on comparisons of historical model results to spatially and temporally distributed observations of groundwater levels, surface-water flows, diversions, and observed pumpage throughout the integrated hydrologic model domain. These comparisons were used to assess the capacity of the historical model to simulate effects of changing inflows and outflows on the hydrologic system. The goodness of fit between observed values and their simulated equivalents was evaluated using (1) correlation plots, (2) matching groups of hydrographs for subregions and model layers, (3) mean residuals (or the average of the differences between the simulated equivalent values and observation values), (4) minimal root mean square errors (RMSE; <xref ref-type="bibr" rid="r2">Anderson and others, 1992</xref>), (5) scaled RMSE (or RMSE divided by observation maxima minus minima), and (6) the Nash-Sutcliffe model efficiency (NSME) statistic (<xref ref-type="bibr" rid="r129">Nash and Sutcliffe, 1970</xref>; <xref ref-type="bibr" rid="r116">Markstrom and others, 2008</xref>), which is a standardized mean squared-error statistic varying between 0 and 1. An NSME value greater than 0.5 indicates that the model provides a better match to the observed streamflow values than the mean of the observed streamflow values (<xref ref-type="bibr" rid="r129">Nash and Sutcliffe, 1970</xref>). The closer the NSME is to 1.0, the better the match is between simulated and observed values, with a value of 1.0 indicating a perfect match. The NMSE was not used for evaluation of groundwater level history matching. Additionally, the correspondence between simulated groundwater levels and MCWRA estimated groundwater-level contours for the shallow and deep aquifers (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>) was evaluated by visual inspection. The groundwater-level maps were used for qualitative comparisons. However, these maps were considered less reliable than time-series data because the composite water-level measurements and manually drawn contour lines represent various combinations of depth- and time-averaged conditions.</p>
<p>The parameter estimation focuses on minimizing the absolute value of the mean residual, RMSE, and scaled RMSE and maximizing the NSME value for hydrologic flow observations. Some observations are challenging to simulate in regional-scale models, especially when they represent intermittent extreme values. The simulated equivalent values for these extreme observed values can be biased low due to limitations of model formulation and temporal and spatial averaging. Many observations developed for parameter estimation and history matching aggregate daily observed values to monthly averages or resolve measurements at point-scale spatial units (for example, streamgages) to the model discretization (for example, stream reaches). The overall history matching is evaluated using the mean residual, RMSE, and normalized RMSE that is less sensitive to singular observations. The NSME is sensitive to high flows, as noted by <xref ref-type="bibr" rid="r109">Krause and others (2005)</xref>. Therefore, if observed values and their simulated equivalents have substantial range or if the magnitude of simulated equivalent values for extreme values is biased low, then the NSME values can be low. Therefore, the model performance for groups of hydrologic flow observations with extreme high and low values (such as stream differences) that have low NSME values are evaluated using the mean residual, RMSE, and normalized RMSE.</p>
<sec>
<title>Streamflow</title>
<p>Correlation plots show good correspondence among observed and simulated equivalent streamflow values (<xref ref-type="fig" rid="fig32">fig. 32<italic>A</italic></xref>) across the range of highly variable streamflows within the Salinas Valley. There is more spread around the 1:1 line for high peak streamflows. <xref ref-type="fig" rid="fig32">Figures 32<italic>B</italic>&#x2013;<italic>G</italic></xref> show observed and simulated equivalent flows at selected observation gages of the Salinas River and its major tributary, Arroyo Seco. Streamflow differences for four pairs of gages are shown on <xref ref-type="fig" rid="fig32">figures 32<italic>H</italic>&#x2013;<italic>K</italic></xref>. These hydrographs illustrate a reasonable match of streamflows through time within the region from the uppermost to the lowermost gage in the system. Monthly peak streamflows are well characterized, but low flows are commonly overestimated. This effect of low-flow overestimation increases downstream along the Salinas River due to accumulation of simulation error.</p>
<fig id="fig32" position="float" fig-type="figure"><label>Figure 32</label><caption><p>Observed and simulated equivalent streamflow hydrographs for selected river gages and diversions from the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2018 showing <italic>A</italic>, correlation among simulated and observed streamflows for all stream observations. Simulated and observed streamflow at <italic>B</italic>, USGS 11150500; <italic>C</italic>, USGS 11152000; <italic>D</italic>, USGS 11152050;<italic> E</italic>, USGS 11151700; <italic>F</italic>, USGS 11152300; <italic>G</italic>, USGS 11152500 gages. Simulated and observed stream difference for <italic>H</italic>, USGS 11150500&#x2212;USGS 11151700; <italic>I</italic>, USGS 11152000&#x2212;USGS 11152050; <italic>J</italic>, USGS 11151700&#x2212;USGS 11152300; and <italic>K</italic>, USGS 11152300&#x2212;USGS 11152500 (<xref ref-type="bibr" rid="r165">U.S. Geological Survey, 2018</xref>). Simulated and observed diversions from <italic>L</italic>, Salinas River at the Salinas River Diversion Facility and <italic>M</italic>, Arroyo Seco for Clark Colony (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>32.</bold>	Graphs showing observed and simulated equivalent streamflow hydrographs for selected river gages and diversions from the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1968&#x2013;2018</p></caption><long-desc>32. There is a positive, linear correlation between observed and simulated streamflow. Simulated flows generally overestimate low observed flows.</long-desc><graphic xlink:href="sac23-0784_fig32ab"/><graphic xlink:href="sac23-0784_fig32cdef"/><graphic xlink:href="sac23-0784_fig32ghij"/><graphic xlink:href="sac23-0784_fig32klm"/></fig>
<p>Streamflow hydrographs indicate a good visual fit of monthly observed values and their simulated equivalents (<xref ref-type="fig" rid="fig32">figs. 32<italic>B</italic>&#x2013;<italic>K</italic></xref>) such that the absolute value of all mean residuals is less than or equal to 81 ft<sup>3</sup>/s, RMSE is less than or equal to 437 ft<sup>3</sup>/s, scaled RMSE is less than or equal to 5 percent, and NMSE values are greater than or equal to 0.87 (<xref ref-type="table" rid="t07">table 7</xref>). Streamflow difference plots (<xref ref-type="fig" rid="fig32">figs. 32<italic>H</italic>&#x2013;<italic>K</italic></xref>) show a good visual fit of observed values and their simulated equivalents, such that the absolute value of all mean residuals is less than or equal to 48 ft<sup>3</sup>/s, RMSE is less than or equal to 238 ft<sup>3</sup>/s, and scaled RMSE is less than or equal to 8 percent (<xref ref-type="table" rid="t07">table 7</xref>). The NMSE values for streamflow differences are lower (less than 0.5) because of the effect of extreme values that are not simulated well by the model. Stream differences are challenging to match because errors propagate downstream, leading to even larger differences in USGS gages lower in the Salinas Valley. Also, stream gains and losses can be affected by localized runoff or withdrawal from shallow wells adjacent to the river that may not be represented by the model.</p>
<table-wrap id="t07" orientation="landscape" position="float"><label>Table 7</label><caption>
<title>Summary of streamflow history matching showing streamflow statistics for the period from 1970 to 2018, mean residual streamflow computed as observed minus the simulated equivalent value, root mean squared error, scaled root mean square error, and Nash-Sutcliffe model efficiency for U.S. Geological Survey gages and diversions in the Salinas Valley Integrated Hydrologic Model (<xref ref-type="bibr" rid="r97">Hevesi and others, 2025b</xref>).</title>
<p content-type="toc"><bold>7.</bold>	Summary of streamflow history matching showing streamflow statistics for the period from 1970 to 2018, mean residual streamflow computed as observed minus the simulated equivalent value, root mean squared error, scaled root mean square error, and Nash-Sutcliffe model efficiency for U.S. Geological Survey gages and diversions in the Salinas Valley Integrated Hydrologic Model</p>
<p>[ft<sup>3</sup>/s, cubic foot per second; &#x2014;, no data; &lt;, less than]</p></caption>
<table rules="groups">
<col width="13.4%"/>
<col width="10.03%"/>
<col width="9.54%"/>
<col width="9.64%"/>
<col width="9.07%"/>
<col width="9.86%"/>
<col width="7.41%"/>
<col width="8.34%"/>
<col width="11.92%"/>
<col width="10.79%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Gage identifiers</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Observation group</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Number of <break/>observations</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Minimum observed value <break/>(ft<sup>3</sup>/s)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Mean observed value <break/>(ft<sup>3</sup>/s)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Maximum observed value <break/>(ft<sup>3</sup>/s)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Mean residual <break/>(ft<sup>3</sup>/s)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Root mean square error <break/>(ft<sup>3</sup>/s)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Scaled root mean square error <break/>(percentage)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Nash Suttcliffe model efficiency <break/>(unitless)</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt" scope="col">Streamflow</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">USGS 11150500</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">SANT_BR</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">566</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">519</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">10,185</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;83</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">333</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.89</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">USGS 11152050</td>
<td valign="top" align="left">ARS_REL</td>
<td valign="top" align="char" char=".">243</td>
<td valign="top" align="char" char=".">0</td>
<td valign="top" align="char" char=".">117</td>
<td valign="top" align="char" char=".">2,801</td>
<td valign="top" align="char" char=".">&#x2212;9</td>
<td valign="top" align="char" char=".">116</td>
<td valign="top" align="char" char=".">4</td>
<td valign="top" align="char" char=".">0.87</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">USGS 11152000</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">ARS_SOL</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">567</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">175</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2,697</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">125</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.88</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">USGS 11151700</td>
<td valign="top" align="left">SAL_SOL</td>
<td valign="top" align="char" char=".">495</td>
<td valign="top" align="char" char=".">0</td>
<td valign="top" align="char" char=".">371</td>
<td valign="top" align="char" char=".">11,169</td>
<td valign="top" align="char" char=".">&#x2212;38</td>
<td valign="top" align="char" char=".">343</td>
<td valign="top" align="char" char=".">3</td>
<td valign="top" align="char" char=".">0.89</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">USGS 11152300</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">SAL_CHU</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">459</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">414</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14,352</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">19</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">388</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.91</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">USGS 11152500</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">SAL_SPR</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">567</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">402</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">16,204</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x2212;11</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">437</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">3</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.90</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Streamflow difference</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">USGS 11150500&#x2013;USGS 11151700</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">BR_SOL</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">494</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;1,655</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">117</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">860</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;45</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">210</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.14</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">USGS 11151700&#x2013;USGS 11152300</td>
<td valign="top" align="left">SOL_CHU</td>
<td valign="top" align="char" char=".">399</td>
<td valign="top" align="char" char=".">&#x2212;3,183</td>
<td valign="top" align="char" char=".">3</td>
<td valign="top" align="char" char=".">729</td>
<td valign="top" align="char" char=".">&#x2212;30</td>
<td valign="top" align="char" char=".">197</td>
<td valign="top" align="char" char=".">5</td>
<td valign="top" align="char" char=".">0.52</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">USGS 11152300&#x2013;USGS 11152500</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">CHU_SPR</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">459</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2,153</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1,331</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">238</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">0.00</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">USGS 11152000&#x2013;USGS 11152050</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">ARR_SEC</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">243</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x2212;537</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">52</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">323</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">5</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">64</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0.17</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt" scope="col">Diversion</th>
</tr>
<tr>
<td colspan="2" valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">CLARK_DIV</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">139</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">13</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">0.52</td>
</tr>
<tr>
<td colspan="2" valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">SRDF_DIV</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">23</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">0</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&lt;1</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&lt;1</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">1.00</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Diversions are well matched where inflow data to the channel are sufficiently accurate. The historical model has a good visual fit for diversions at Clark Colony (<xref ref-type="fig" rid="fig32">fig. 32<italic>M</italic></xref>); the mean residual is 3 ft<sup>3</sup>/s, RMSE is 8 units, scaled RMSE is 13 percent, and NMSE is 0.52. The higher scaled RMSE and lower NSME are because Clark Colony diversions were estimated, and the estimated diversion values are commonly higher than the observed flow in the upgradient channel at USGS 11152000. Nonetheless, the low mean residual and RMSE for Clark Colony diversions imply that the diversion is reasonably represented even though the estimated diversions were typically higher than the available flow. Diversions at the SRDF (<xref ref-type="fig" rid="fig32">fig. 32<italic>L</italic></xref>) are well matched, with a mean residual and RMSE less than 1 ft<sup>3</sup>/s, scaled RMSE of about 2 percent, and NMSE equal to 0.99. The well-matched diversions at SRDF indicate that the FMP is computing the full amount of the surface diversions used to meet demands at CSIP. Overall, these results indicate that the surface-water flow system is well represented in the integrated hydrologic model.</p>
</sec>
<sec>
<title>Groundwater</title>
<p>Groundwater hydrographs that show both simulated and observed heads for selected wells help to illustrate the match of groundwater levels throughout the model subareas of the historical model. An analysis well subset of hydrographs for 10 wells (<xref ref-type="fig" rid="fig33">fig. 33</xref>) was selected as representative due to the wells&#x2019; long period of record, regular measurements, and representation of the important aquifers in each region. <xref ref-type="table" rid="t09">Table 9</xref> summarizes the hydrogeologic units and model layers for each well in the analysis well subset. Analysis wells were selected in each analysis region to evaluate the 180-Foot Aquifer, 400-Foot Aquifer, and deeper hydrogeologic units (Paso Robles Formation, Purisima Formation, and basement). The four wells selected in the Pressure analysis region represent hydrogeologic units of the 180-Foot Aquifer (CSI239 and ZPN1529) and the 400-Foot Aquifer (ZPN441 and CSI239). The hydrographs for the East Side-Langley analysis region represent the composite of the 180-Foot Aquifer, 400-Foot Aquifer, and Paso Robles Formation hydrogeologic units (ZES871 and ZES1572). The hydrographs for the Forebay analysis region represent the 400-Foot Aquifer hydrogeologic unit (ZFS1001) and the composite Paso Robles Formation and Purisima Formation hydrogeologic units (ZNE1267). The hydrographs for the Upper Valley analysis region represent the Purisima Formation hydrogeologic unit (ZSE355 and ZSE733). The hydrographs for all observation wells can be obtained in the head observation output file in the model archive (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p>
<fig id="fig33" position="float" fig-type="figure"><label>Figure 33</label><caption><p>Groundwater observations and simulated equivalent values from the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California showing <italic>A</italic>, correlation among groundwater-level measurements and simulated equivalent groundwater-level hydrographs for selected wells. Hydrographs are shown for wells <italic>B</italic>, CSI239; <italic>C</italic>, BDA331; <italic>D</italic>, ZPN1529; and <italic>E</italic>, ZPN441 in the Pressure analysis region; wells <italic>F</italic>, ZES1572 and <italic>G</italic>, ZES871 in the East Side-Langley analysis region; wells <italic>H</italic>, ZFS1001 and <italic>I</italic>, ZNE1267 in the Forebay analysis region; and wells <italic>J</italic>, ZSE355 and <italic>K</italic>, ZSE733 in the Upper Valley analysis region (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>33.</bold>	Graphs showing groundwater observations and simulated equivalent values from the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California showing correlation among groundwater-level measurements and simulated equivalent groundwater-level hydrographs for selected wells, and hydrographs for wells CSI239, BDA331, ZPN1529, and ZPN441 in the Pressure analysis region; wells ZES1572 and ZES871 in the East Side-Langley analysis region; wells ZFS1001 and ZNE1267 in the Forebay analysis region; and wells ZSE355 and ZSE733 in the Upper Valley analysis region</p></caption><long-desc>33. There is a positive, linear correlation between observed and simulated groundwater levels, but seasonal oscillations are not always matched.</long-desc><graphic xlink:href="sac23-0784_fig33ab"/><graphic xlink:href="sac23-0784_fig33cdef"/><graphic xlink:href="sac23-0784_fig33ghij"/><graphic xlink:href="sac23-0784_fig33k"/></fig>
<p>Correlation plots (<xref ref-type="fig" rid="fig33">fig. 33<italic>A</italic></xref>) and examples of hydrographs from the East Side-Langley, Pressure, Forebay, and Upper Valley analysis regions (<xref ref-type="fig" rid="fig33">figs. 33<italic>B</italic>&#x2013;<italic>K</italic></xref>) are used to illustrate the temporal fit of groundwater-level observations and their simulated equivalents. The observed and simulated equivalent groundwater-level correlation is good across the range of groundwater levels (<xref ref-type="fig" rid="fig33">fig. 33<italic>A</italic></xref>). The monthly to interannual fluctuations in observed groundwater levels indicate the effect of groundwater pumping, followed by climate variability (<xref ref-type="fig" rid="fig33">figs. 33<italic>B</italic>&#x2013;<italic>K</italic></xref>) and streamflow infiltration (for example, wells CSI239, ZPN1529, and ZSE733 near the Salinas River). Even though there are places where the groundwater levels are over- or underpredicted, the change in groundwater levels from the first measurement in each observation well (drawdown) have low mean residuals (<xref ref-type="table" rid="t08">tables 8</xref>, <xref ref-type="table" rid="t09">9</xref>).</p>
<table-wrap id="t08" position="float"><label>Table 8</label><caption>
<title>Summary of selected observation wells used to illustrate Salinas Valley Integrated Hydrologic Model history matching, indicating number of observations, representative model layers, hydrogeologic units, mean residual computed as observed minus the simulated equivalent value, and root mean square error.</title>
<p content-type="toc"><bold>8.</bold>	Summary of selected observation wells used to illustrate Salinas Valley Integrated Hydrologic Model history matching, indicating number of observations, representative model layers, hydrogeologic units, mean residual computed as observed minus the simulated equivalent value, and root mean square error</p></caption>
<table rules="groups">
<col width="10.86%"/>
<col width="16.77%"/>
<col width="13.21%"/>
<col width="9.54%"/>
<col width="25.11%"/>
<col width="10.97%"/>
<col width="13.54%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Well name</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Construction date<break/>(month/day/year)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Number of <break/>observations</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Model layers</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Hydrogeologic units</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Mean residual <break/>(feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Root mean square error <break/>(feet)</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="7" valign="top" align="center" style="border-top: solid 0.50pt" scope="col">Pressure</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">CSI239</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">12/22/1961</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">639</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">400-Foot Aquifer</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">6</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">10</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">BDA331</td>
<td valign="top" align="center">01/25/1964</td>
<td valign="top" align="char" char=".">84</td>
<td valign="top" align="center">3</td>
<td valign="top" align="left">180-Foot Aquifer</td>
<td valign="top" align="char" char=".">&#x2212;14</td>
<td valign="top" align="char" char=".">16</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">ZPN1529</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">04/01/1954</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">53</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">180-Foot Aquifer</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;15</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">ZPN441</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">08/01/1941</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">40</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">5</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">400-Foot Aquifer</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">8</td>
</tr>
<tr>
<th colspan="7" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">East Side</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">ZES1572</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">12/18/1946</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">608</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">3,5,7</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">180-Foot, 400-Foot, and Paso Robles aquifers</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">6</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">ZES871</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">08/10/1950</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">534</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">3,5,7</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">180-Foot, 400-Foot, and Paso Robles aquifers</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x2212;7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">13</td>
</tr>
<tr>
<th colspan="7" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Forebay</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">ZFS1001</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">11/01/1938</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">44</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">5</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">400-Foot Aquifer</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">4</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">ZNE1267</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">01/01/1900</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">40</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">7,8</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Paso Robles and Purisima aquifers</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">&#x2212;4</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">6</td>
</tr>
<tr>
<th colspan="7" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Upper Valley</th>
</tr>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">ZSE355</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">06/06/1951</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">597</td>
<td valign="top" align="center" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">8</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Purisima aquifer</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">2</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">9</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">ZSE733</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">04/17/1952</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">41</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">8</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Purisima aquifer</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">4</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">5</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="t09" position="float"><label>Table 9</label><caption>
<title>Summary of groundwater level history matching showing drawdown mean residual computed as observed minus the simulated equivalent value, root mean square error, and scaled root mean square error for the Salinas Valley Integrated Hydrologic Model domain and analysis regions.</title>
<p content-type="toc"><bold>9.</bold>	Summary of groundwater level history matching showing drawdown mean residual computed as observed minus the simulated equivalent value, root mean square error, and scaled root mean square error for the Salinas Valley Integrated Hydrologic Model domain and analysis regions in Monterey and San Luis Obispo Counties, California</p>
<p>[&lt;, less than]</p></caption>
<table rules="groups">
<col width="18.42%"/>
<col width="13.55%"/>
<col width="9.1%"/>
<col width="12.2%"/>
<col width="11.76%"/>
<col width="11.19%"/>
<col width="11.39%"/>
<col width="12.39%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis region</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Number of observations</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Number of wells</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Minimum observed water level (feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Maximum <break/>observed <break/>water level <break/>(feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Mean drawdown residual (feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Drawdown <break/>root mean <break/>square error <break/>(feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Scaled root mean square error (percent)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Entire domain</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">3,805</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">439</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;168</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">472</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">&lt;1</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">6</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pressure</td>
<td valign="top" align="char" char=".">779</td>
<td valign="top" align="char" char=".">171</td>
<td valign="top" align="char" char=".">&#x2212;103</td>
<td valign="top" align="char" char=".">113</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">14</td>
<td valign="top" align="char" char=".">8</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">East Side-Langley</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1,144</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">119</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;168</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">472</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="char" char=".">1,196</td>
<td valign="top" align="char" char=".">100</td>
<td valign="top" align="char" char=".">&#x2212;10</td>
<td valign="top" align="char" char=".">282</td>
<td valign="top" align="char" char=".">&#x2212;3</td>
<td valign="top" align="char" char=".">10</td>
<td valign="top" align="char" char=".">9</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Upper Valley</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">686</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">39</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">201</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">447</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">14</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Groundwater levels and drawdowns generally show good agreement between observed and simulated equivalent values. There are some areas of the Forebay analysis region where groundwater levels are overpredicted by about 10 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>I</italic></xref>), and in the Upper Valley analysis region, they are overpredicted by 20 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>K</italic></xref>). The absolute value of the mean residual for all drawdown observations is less than 1 ft, with an RMSE of 15 ft and a scaled RMSE of 6 percent. There are drawdowns in the Pressure analysis region that are underpredicted by approximately 19 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>C</italic></xref>; <xref ref-type="table" rid="t08">table 8</xref>) or 21 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>D</italic></xref>; <xref ref-type="table" rid="t08">table 8</xref>) or overpredicted by 6 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>B</italic></xref>; <xref ref-type="table" rid="t08">table 8</xref>) or less than 1 ft (<xref ref-type="fig" rid="fig33">fig. 33<italic>E</italic></xref>; <xref ref-type="table" rid="t08">table 8</xref>). This under- or overprediction of mean drawdowns is affected by the capability of the model to simulate the seasonal oscillations in these observation wells where pumping is occurring at unknown rates. The magnitude of seasonal oscillations in some wells were not matched everywhere. For example, seasonal oscillations in groundwater levels in the East Side-Langley analysis region are commonly 40 ft or more (<xref ref-type="fig" rid="fig33">fig. 33<italic>F</italic></xref>). This effect results in the spread of simulated and observed groundwater levels across the 1:1 correlation line in the correlation plot (<xref ref-type="fig" rid="fig33">fig. 33<italic>A</italic></xref>). This poor representation of seasonal oscillations is likely because 340 of the 439 observation wells are also agricultural supply wells, and pumping rates in the models are not simulated using time series from individual well owners. The differences between simulated and observed seasonal oscillations are caused by using subregional distributed pumping rates to replicate the pumpage rates applied to each well. Observations that were assumed to be affected by pumping were delineated to help focus the parameter estimation and analysis. Pumping occurs year-round, so the assumptions for pumping effect did not capture all wells where large oscillations due to pumping can be observed. The effects of pumping and oscillations are still observed in some wells, especially in the Pressure and East Side-Langley analysis regions (<xref ref-type="fig" rid="fig33">fig. 33<italic>A</italic></xref>). The effect of this difference between observed and simulated can be observed in hydrographs that have multiple measurements per year (<xref ref-type="fig" rid="fig33">figs. 33<italic>B</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>C</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>G</italic></xref>, and <xref ref-type="fig" rid="fig33">33<italic>J</italic></xref>). Many of these wells are in the Pressure and East Side-Langley analysis regions, where mean residual drawdowns are low (from 1 ft to &#x2212;1 ft, respectively), and RMSE values (15 ft and 18 ft, respectively; <xref ref-type="table" rid="t09">table 9</xref>) are higher in these regions. Nonetheless, the scaled RMSE for the Pressure and East Side-Langley analysis regions are 8 and 7 percent, respectively. Mean residual drawdowns in the Forebay analysis region were &#x2212;3 ft with an RMSE of 10 ft and scaled RMSE of 9 percent. Mean residual drawdowns in the Upper Valley analysis region were 1 ft, with a RMSE of 7 ft and a scaled RMSE of 13 percent. The scaled RMSE is higher here because there are fewer wells in this region that have known properties added to the integrated hydrologic models. Thus, all observation wells in the Upper Valley analysis region were specified as agricultural supply wells, with pumping rates specified on analysis region demands that are likely to be different from pumping time series applied at those wells. The specification of simultaneous pumping and observation wells was unavoidable because there are fewer reported supply wells in the Upper Valley analysis region (<xref ref-type="fig" rid="fig24">figs. 24<italic>A</italic></xref>, <xref ref-type="fig" rid="fig24">24<italic>B</italic></xref>) among which to distribute estimated agricultural demands. Defining concurrent pumping and observation wells resulted in oscillations in some wells that differ from measured values.</p>
<p>Model results in early time periods are sensitive to estimates of initial conditions. Although the rates of decline and the elevations are like those in historical records, some of the temporal changes are not reflected in the simulated values. The magnitude of substantial drawdowns and subsequent recovery in the dry period from WY 1984&#x2013;94 is not captured in some wells (for example, <xref ref-type="fig" rid="fig33">figs. 33<italic>F</italic>&#x2013;<italic>H</italic></xref>), which could be due to an interaction between the time of the groundwater level measurement and residual pumping effects of the observation well and adjacent wells. Other places where simulated and observed groundwater levels diverge could be a function of changes in actual land use or irrigation practices that are not well represented in the available land use data, variability in Kc values that estimate crop demands, and divergence between the rates of actual groundwater pumpage at a specific well and the wells simulating groundwater pumpage. Although there are some places where seasonal oscillations are not well matched, or drawdowns are well matched and groundwater levels are elevated or depressed, overall historical model results show reasonable correspondence among simulated and observed groundwater levels throughout the integrated hydrologic model domain.</p>
<p>Groundwater observation well mean residuals also show reasonable correspondence across all analysis regions (<xref ref-type="fig" rid="fig34">fig. 34</xref>); 77 percent of observation wells have mean residual drawdowns from &#x2212;30 to 30 ft, and 56 percent of wells have mean residual drawdowns between &#x2212;15 and 15 ft. These residuals are affected substantially by the aforementioned challenges in representing seasonal oscillations in observation wells that are also pumping wells. In the Langley Area groundwater subbasin of the East Side-Langley analysis region, some water levels are not well matched, but several faults in the groundwater basin here cause water level offsets of more than 100 ft in adjacent wells. There are three isolated wells in this area that have absolute mean drawdown residuals greater than 50 ft (<xref ref-type="fig" rid="fig34">fig. 34</xref>), indicating that the model residual bias is limited spatially.</p>
<fig id="fig34" position="float" fig-type="figure"><label>Figure 34</label><caption><p>Mean residuals computed as the difference between observed and simulated equivalent values in the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for all observation wells for the parameter estimation period from water year 1968 through 2014 (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>34.</bold>	Map showing mean residuals computed as the difference between observed and simulated equivalent values in the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for all observation wells for the parameter estimation period from water year 1968 through 2014</p></caption><long-desc>34. Mean residuals are generally from &#x2212;20 to 20 feet with a few wells that have residuals less than &#x2212;20 feet or greater than 20 feet.</long-desc><graphic xlink:href="sac23-0784_fig34"/></fig>
<p>To allow for a spatial comparison of the simulated historical model values to observed data, groundwater-level maps were developed for fall of 1994, 2003, and 2011 (<xref ref-type="fig" rid="fig35">figs. 35<italic>A</italic>&#x2013;<italic>F</italic></xref>). The observed data in these plots are contours generated by MCWRA for a composite of shallow aquifers (depth less than 201 ft) and deep aquifers (depth greater than 201 ft and less than 420 ft). The shallow contours from the historical model are approximated using the December simulated equivalent groundwater levels in the 180-Foot Aquifer (model layer 3). The deep contours from the historical model are approximated by the December simulated equivalent groundwater levels in the 400-Foot Aquifer (model layer 5). These maps were used during historical model parameter estimation to provide additional information on the effects of internal flow boundaries along faults and to help adjust selected model hydraulic properties, such as vertical hydraulic conductivities.</p>
<fig id="fig35" position="float" fig-type="figure"><label>Figure 35</label><caption><p>Historical model groundwater contours in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing Salinas Valley Integrated Hydrologic Model simulated equivalent December groundwater levels and Monterey County Water Resources Agency (MCWRA) fall composite contoured groundwater levels. The shallow aquifer composite contour map was computed by MCWRA using measurements in aquifers that are less than 200 feet deep. The shallow contours are compared to groundwater level contours from model cells within the 180-Foot Aquifer hydrogeologic unit (layer 3). The deep aquifer composite contour map was computed by MCWRA using measurements greater than 200 but less than 420 feet deep. The deep contours are compared to groundwater level contours from model cells within the 400-Foot Aquifer hydrogeologic unit (layer 5). These maps show <italic>A</italic>, shallow aquifer composite contours and simulated equivalent contours in fall 1994; <italic>B</italic>, deep aquifer composite contours and simulated equivalent contours in fall 1994; <italic>C</italic>, shallow aquifer composite contours and simulated equivalent contours in fall 2003; <italic>D</italic>, deep aquifer composite contours and simulated equivalent contours in fall 2003; and <italic>E</italic>, shallow aquifer composite contours and simulated equivalent contours in fall 2011; and <italic>F</italic>, deep aquifer composite contours and simulated equivalent contours in fall 2011.</p><p content-type="toc"><bold>35.</bold>	Maps showing historical model groundwater contours in the integrated hydrologic model domain in Monterey and San Luis Obispo Counties of California showing Salinas Valley Integrated Hydrologic Model simulated equivalent December groundwater levels and Monterey County Water Resources Agency fall composite contoured groundwater levels</p></caption><long-desc>35. Modeled groundwater-level contours are higher than previously mapped but have similar magnitude and regional flow direction.</long-desc><graphic xlink:href="sac23-0784_fig35ab"/><graphic xlink:href="sac23-0784_fig35cd"/><graphic xlink:href="sac23-0784_fig35ef"/></fig>
<p>The MCWRA and simulated groundwater level contour maps show good correspondence among the shallow and deep aquifers in 1994, 2003, and 2011 (<xref ref-type="fig" rid="fig35">fig. 35</xref>). The simulated groundwater levels have similar areas of over- and underprediction. The historical model data and contours both show that water level declines are concentrated in the Pressure and East Side-Langley analysis regions and increase in magnitude toward the City of Salinas. Additional declines in groundwater levels are observed in the East Side-Langley analysis region over time. Simulated groundwater levels in 1994, 2003, and 2011 overestimate the MCWRA contours in the Upper Valley analysis region of the historical model by about 20&#x2013;30 ft, where additional refinement of aquifer properties, land use, or recharge may be required.</p>
</sec>
<sec>
<title>Agricultural Pumpage</title>
<p>The reported monthly agricultural pumpage was aggregated by WBS, resulting in 3,630 observations spanning the period from November 1994 through December 2014 that were compared to FMP simulated equivalent agricultural pumpage values during calibration. Before November 1994 when monthly agricultural pumpage observations were not available, simulated equivalent annual agricultural pumpage was compared to published long-term estimates. The historical model matches the total reported annual agricultural pumpage from November 1994 through September 2018 for Salinas Valley within 99 percent and has general agreement among monthly reported and simulated agricultural pumpage throughout the model domain (<xref ref-type="fig" rid="fig36">figs. 36<italic>A</italic>&#x2013;<italic>E</italic></xref>). Simulated equivalent annual agricultural pumpage varies from year to year with an average of approximately 470 TAFY for the period between 1970 and 1994. This value is consistent with prior modeling efforts (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>) and MCWRA reports (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). After November 1994, annual reported agricultural pumpage has varied from 380 TAFY in 2001 to as much as 529 TAFY in 1997, with an average of 439 TAFY (<xref ref-type="fig" rid="fig36">fig. 36<italic>B</italic></xref>). The annual mean residual (annual reported pumpage minus simulated equivalent annual pumpage) for the history matching period (WY 1995&#x2013;2014) was &#x2212;4.3 TAFY, which is approximately 1 percent of the mean annual pumpage. There is reasonable correspondence among monthly simulated equivalent and reported agricultural pumpage (<xref ref-type="fig" rid="fig36">fig. 36<italic>A</italic></xref>). The monthly reported and simulated equivalent agricultural pumpage for each analysis region for the simulation with reported observations is shown on <xref ref-type="fig" rid="fig36">figures 36<italic>C</italic>&#x2013;<italic>G</italic></xref>. The absolute value of all monthly mean residuals for the integrated hydrologic model domain and the analysis regions is less than or equal to 181 acre-feet, with RMSE less than 1,350 acre-feet and all scaled RMSE less than 9 percent (<xref ref-type="table" rid="t10">table 10</xref>). Approximately 73 percent of all simulated equivalent monthly agricultural pumping is within 700 acre-feet of the reported monthly values. The close correspondence of reported and simulated equivalent annual total pumpage indicates that monthly errors tend to cancel themselves out over the growing season. There is reasonable correspondence between simulated and observed pumpage among areas in analysis regions exclusively irrigated by groundwater (East Side-Langley and Upper Valley analysis regions; <xref ref-type="fig" rid="fig36">figs. 36<italic>D</italic></xref> and <xref ref-type="fig" rid="fig36">36<italic>F</italic></xref>, respectively) and among areas that have irrigation from surface-water diversions and recycled water deliveries (Pressure and Forebay analysis regions; <xref ref-type="fig" rid="fig36">figs. 36<italic>C</italic></xref> and <xref ref-type="fig" rid="fig36">36<italic>E</italic></xref>, respectively).</p>
<fig id="fig36" position="float" fig-type="figure"><label>Figure 36</label><caption><p>Reported and simulated equivalent agricultural pumpage within the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California showing <italic>A</italic>, Correlation among monthly reported and simulated equivalent groundwater pumpage. Time series of monthly observed and simulated equivalent farm deliveries for the <italic>B</italic>, Pressure analysis region; <italic>C</italic>, East Side-Langley analysis region; <italic>D</italic>, Forebay analysis region; and <italic>E</italic>, Upper Valley analysis region. Times series of annual observed and simulated equivalent pumpage for <italic>F</italic>, entire integrated hydrologic model domain; <italic>G</italic>, Pressure analysis region; <italic>H</italic>, East Side-Langley analysis region; <italic>I</italic>, Forebay analysis region; and J, Upper Valley analysis region (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). Shaded tan areas highlight the relatively dry conditions for water years 1984&#x2013;94 and 2012&#x2013;18.</p><p content-type="toc"><bold>36.</bold>	Graphs showing reported and simulated equivalent agricultural pumpage within the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>36. There is a positive, linear correlation between observed and simulated agricultural pumping rates. Observed and simulated deliveries have similar values.</long-desc><graphic xlink:href="sac23-0784_fig36abc"/><graphic xlink:href="sac23-0784_fig36def"/><graphic xlink:href="sac23-0784_fig36ghi"/><graphic xlink:href="sac23-0784_fig36j"/></fig>
<table-wrap id="t10" position="float"><label>Table 10</label><caption>
<title>Summary of monthly agricultural pumpage history matching showing drawdown mean residual computed as observed minus the simulated equivalent value, root mean square error, and scaled root mean square error for the Salinas Valley Integrated Hydrologic Model domain and analysis regions.<?Table Med?></title>
<p content-type="toc"><bold>10.</bold>	Summary of monthly agricultural pumpage history matching showing drawdown mean residual computed as observed minus the simulated equivalent value, root mean square error, and scaled root mean square error for the Salinas Valley Integrated Hydrologic Model domain and analysis regions.</p></caption>
<table rules="groups">
<col width="24.11%"/>
<col width="20.71%"/>
<col width="16.99%"/>
<col width="18.08%"/>
<col width="20.11%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis region</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Number of monthly observations</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Mean residual <break/>(acre-feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Root mean square error <break/>(acre-feet)</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Scaled root mean square error <break/>(percentage)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Entire domain</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">3,630</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">39</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">774</td>
<td valign="top" align="char" char="." style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">5</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pressure</td>
<td valign="top" align="char" char=".">968</td>
<td valign="top" align="char" char=".">107</td>
<td valign="top" align="char" char=".">727</td>
<td valign="top" align="char" char=".">5</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">East Side</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">242</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;53</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1,346</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Forebay</td>
<td valign="top" align="char" char=".">968</td>
<td valign="top" align="char" char=".">183</td>
<td valign="top" align="char" char=".">784</td>
<td valign="top" align="char" char=".">8</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Upper Valley</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">968</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">&#x2212;119</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">804</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt; background-color:rgb(217,217,217)">9</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
</sec>
<sec>
<title>Hydrologic Flow Budgets&#x2014;Salinas Valley Integrated Hydrologic Model</title>
<p>The natural and man-made inflows and outflows in the hydrologic budgets represent the supply and demand components of water use and variability of groundwater and surface water in the Salinas Valley. The historical model simulation of the conjunctive use and movement of water in the Salinas Valley shows cyclic storage depletion that is driven by reduced supply during dry periods combined with sustained and increased agriculture and related demand for water. Although periodic events of recharge occur from natural climate cycles, the recent and historical sustained demand for water exceeds the long-term replenishment rate associated with quasi-periodic climate cycles. The historical model results confirm that overdraft conditions have periodically occurred since the onset of increased groundwater development in the 1960s through the end of the historical simulation period (2018) and are related to periodic dry periods and increased agricultural production. The historical model results indicate a level of pumpage that is consistent with estimates from the selected years of reported total annual agricultural increase in water demand with increased agricultural development. The periodic groundwater storage depletion is predominantly the result of cycles of storage depletion in the 180-Foot, 400-Foot, and deeper Paso Robles Formation, Purisima Formation, and basement aquifers. Annual landscape and groundwater budgets were computed for the model domain and for each of the five analysis regions along with a summary of groundwater budgets for the domain and all analysis regions.</p>
<sec>
<title>Analysis Periods</title>
<p>The groundwater budgets for the study are evaluated over five periods: the simulation after the model spin-up period (1970&#x2013;2018) and four analysis periods when changes throughout the Salinas Valley have occurred (<xref ref-type="fig" rid="fig04">fig. 4<italic>C</italic></xref>). The periods examine changes in groundwater budgets due to land use change, dry periods, and development of water supply projects. The first analysis period (A) includes land use change from WY 1970 through 1983 where there were changes in cropping practices, such as multi-cropping and development of vineyards. In analysis period A, there were 3 dry years, 7 normal years, and 4 wet years. During this period, land use within the Salinas Valley started to shift toward more quick-duration, water-intensive crops, such as lettuce and herbs. Over 20 years, a steep increase is observed in harvested acres of vineyards, quick herb crops, and leafy commodity crops, such as lettuce and broccoli (<xref ref-type="fig" rid="fig07">fig. 7</xref>). This shift resulted in increased demands and associated groundwater pumping through this period (<xref ref-type="fig" rid="fig36">fig. 36</xref>). This transition in agricultural commodities continued through analysis period B (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>). This second analysis period (B) is a historical dry period from WY 1984 through 1994. In analysis period B, there were 5 dry years, 4 normal years, and only 2 wet years. Of the 5 dry years, four are the driest consecutive years on record, resulting in the most severe dry period during the simulation period. The third analysis period (C) is a relatively wet period of aquifer recovery, with groundwater pumpage reporting and development of a new recycled water supply for CSIP. Analysis period C had 1 dry year, 10 normal years, and 4 wet years. During this period, several initiatives began to encourage better data collection and water use reporting. Monitoring networks were expanded, and 19 monitoring wells were added in 1993 alone. The Groundwater Extraction Management System was established, and growers and urban communities began to report monthly water usage. Agricultural irrigation efficiency improvements and urban conservation efforts were implemented, leading to reductions in agricultural groundwater pumpage from the year 1998 onward and reductions in M &amp; I pumpage from 2004 onward (<xref ref-type="fig" rid="fig14">fig. 14</xref>). Conversion of a larger area to drip or low-flow irrigation systems increased agricultural efficiency (<xref ref-type="bibr" rid="r46">Edinger-Marshall and Letey, 1997</xref>; <xref ref-type="bibr" rid="r135">Orang and others, 2008</xref>; <xref ref-type="bibr" rid="r141">Sandoval&#x2010;Solis and others, 2013</xref>; <xref ref-type="bibr" rid="r155">Tindula and others, 2013</xref>). The fourth analysis period (D) is a relatively dry period from WY 2010 through 2018. Further implementation of the SVWP increased reservoir storage, and the SRDF was developed to deliver Salinas River diversions to CSIP. Accordingly, groundwater budget analysis of period D can provide insight into the effect of the recent developments of the SVWP on groundwater resources. Analysis period D is the driest period of them all (66 percent of the time), with 6 dry years, 1 normal year, and 2 wet years. Five of the 6 dry years occurred during the last 5 years of the model simulation period, 2014&#x2013;18, resulting in another dry period. Observation data after 1994 were much more frequent and comprehensive for water level measurements, M &amp; I pumpage, agricultural pumpage, and land use. Thus, there is more confidence in the budgets of the two most recent analysis periods after 1994 (analysis periods C and D; <xref ref-type="fig" rid="fig04">fig. 4<italic>C</italic></xref>).</p>
</sec>
<sec>
<title>Salinas Valley Landscape Budget</title>
<p>The landscape is a specific area of the land surface (except for stream channels) that is modeled as a container different from the groundwater system for which we estimate a water budget with inflows and outflows. This landscape budget includes items of interest that are represented as net flows in the groundwater budgets, such as volumes associated with components of evapotranspiration and runoff to streams. Landscape budgets are computed in this study to support analyses of landscape water demands and supplies and to assess the effects of changes in land use, climate, and water management. Landscape budgets are presented for the integrated hydrologic model domain and the analysis regions using bar charts showing the inflows and outflows.</p>
<sec>
<title>Landscape Budget Components</title>
<p>No water storage is considered in the landscape budget. Streams exist within the landscape; however, stream inflows and outflows are counted in the surface-water budget. Groundwater entering and exiting streams (gains and losses) also is not accounted for in the landscape budget (to avoid double counting with the groundwater budget). Runoff here is defined as overland runoff that goes into streams and thus out of the reference landscape area. Pumpage and surface-water diversions are taken from groundwater and streams (outside of the container) and flow into the container. Deep percolation flows out of the container and into groundwater. Instead, the landscape budget represents the flows into and out of the landscape throughout the historical model. Inflows to the landscape are precipitation, shallow groundwater, agricultural pumpage, surface-water diversions, and recycled water. Outflows from the landscape are evapotranspiration of precipitation, groundwater, irrigation, deep percolation to groundwater, and runoff to streams. Irrigation TDR to meet agricultural demands is represented by the sum of agricultural pumpage, recycled water deliveries, and surface-water deliveries on <xref ref-type="fig" rid="fig37">figure 37</xref>. The TDR analysis allows for evaluation of the landscape components that support deliveries to meet agricultural demands.</p>
<fig id="fig37" position="float" fig-type="figure"><label>Figure 37</label><caption><p>Distribution of landscape-budget inflow and outflow components for the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1970 to 2018 showing the <italic>A</italic>, entire integrated hydrologic model domain; <italic>B</italic>, Riparian analysis region; <italic>C</italic>, Pressure analysis region; <italic>D</italic>, East Side-Langley analysis region; <italic>E</italic>, Forebay analysis region; and <italic>F</italic>, Upper Valley analysis region (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). </p><p content-type="toc"><bold>37.</bold>	Graphs showing distribution of landscape-budget inflow and outflow components for the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1970 to 2018 showing the entire integrated hydrologic model domain, Riparian analysis region, Pressure analysis region, East Side-Langley analysis region, Forebay analysis region, and Upper Valley analysis region</p></caption><long-desc>37. The major inflows are precipitation and agricultural pumpage, and the major outflows are evapotranspiration and deep percolation.</long-desc><graphic xlink:href="sac23-0784_fig37a"/><graphic xlink:href="sac23-0784_fig37b"/><graphic xlink:href="sac23-0784_fig37c"/><graphic xlink:href="sac23-0784_fig37d"/><graphic xlink:href="sac23-0784_fig37e"/><graphic xlink:href="sac23-0784_fig37f"/></fig>
</sec>
<sec>
<title>Climate Variability</title>
<p>The temporal distribution of inflows and outflows to the landscape and surface-water systems indicates a strong climatic effect, with higher values overall in wet periods. Precipitation generally aligns with reported data. However, 2013 shows lower precipitation than expected given that it was a normal climate year, which is likely an anomaly in the estimated climate data. The watershed inflows and other surface-water flows align with historical records and are consistent with periods before and after 2013. The climate year type that is used for reservoir operations (based on surface-water flow percentiles as described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.Climate">Climate</xref>&#x201D; subsection of the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.DescriptionofStudyArea">Description of Study Area</xref>&#x201D; section) is not always aligned with observed climate within the basin, which is especially true for normal and dry climate year types; for example, 1984 (normal) and 1988 (dry) have similar precipitation magnitudes for the integrated hydrologic model domain (<xref ref-type="fig" rid="fig37">fig. 37<italic>A</italic></xref>). There is also subregional inconsistency where the climate year type does not align with analysis region conditions; for example, 1984 precipitation in the Pressure analysis region is less than the 1988 precipitation (<xref ref-type="fig" rid="fig37">fig. 37<italic>C</italic></xref>). Generally, runoff is higher in normal and wet years than dry years. However, substantial runoff can occur in dry years from inefficient irrigation. Analysis of landscape budgets among all analysis regions show similar trends within the basin (<xref ref-type="fig" rid="fig37">figs. 37<italic>B</italic>&#x2013;<italic>F</italic></xref>), including a strong relationship between climate and TDR, with increased pumpage during dry periods.</p>
</sec>
<sec>
<title>Total Delivery Requirement</title>
<p>The effect of climate on TDR is evident in the simulation results. Although some variability does occur among analysis regions, the TDR commonly exceeds precipitation over the basin, with 1988&#x2013;90 and 2007 having annual TDR values more than 1.5 times the precipitation those years. The TDR is greater than 1.5 times precipitation for 15 years in the Pressure analysis region (<xref ref-type="fig" rid="fig37">fig. 37<italic>C</italic></xref>), 7 years in the East Side-Langley analysis region (<xref ref-type="fig" rid="fig37">fig. 37<italic>D</italic></xref>), 33 years in the Forebay analysis region (<xref ref-type="fig" rid="fig37">fig. 37<italic>E</italic></xref>), and 18 years in the Upper Valley analysis region (<xref ref-type="fig" rid="fig37">fig. 37<italic>F</italic></xref>). This spatial variability in the ratio of precipitation to TDR in each analysis region further illustrates the water management challenges in delivering water to meet demands throughout the basin (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>). Because local TDR commonly exceeds precipitation, groundwater is used extensively in the basin to meet demands. More instances of years with TDR greater than 1.5 times the precipitation in the analysis regions compared to the integrated hydrologic model domain suggest an interconnected water supply with water demands supported by flows from adjacent areas. Water demands in each analysis region are supported by recharge from precipitation in the uplands outside of the analysis regions (other areas, <xref ref-type="fig" rid="fig15">fig. 15</xref>) and potentially underflow from the Riparian analysis region and groundwater subbasins in adjacent analysis regions. This interbasin underflow is evaluated using the groundwater budgets in the next section.</p>
<p>Offsetting groundwater use, surface-water deliveries (recycled water deliveries and surface-water diversions) have increased steadily since 1998, reaching nearly 4 percent of the TDR by the end of the simulation period, with a maximum of as much as 23,000 acre-feet in 2013 (<xref ref-type="fig" rid="fig37">fig. 37<italic>A</italic></xref>). Especially in the Pressure analysis region, the TDR supplied by groundwater has been substantially reduced since 1998 through increases in recycled water deliveries and the development of surface-water diversions supported by the Salinas Valley Reclamation Project at the SRDF. These new surface-water supplies provide a substantial portion of the TDR. The surface-water supplies have supported decreases in observed pumpage in the Pressure analysis region.</p>
</sec>
</sec>
<sec>
<title>Salinas Valley Groundwater Budget</title>
<p>Each groundwater budget treats the subsurface system as a container. The frame of reference for all net flows, storage changes, and outflows in the aquifers is represented by the hydrogeologic units. Groundwater budgets are computed in this study to support analysis of groundwater availability and use and to assess the effects of changes in land use, climate, and water management. Quantifying groundwater budget components and metrics is vital to assessing historical conditions and evaluating the effects that water supply projects (SVWP, SRDF, CSIP) and reservoir operations have on groundwater and surface-water availability. Groundwater budgets are presented in three ways for the integrated hydrologic model domain and the analysis regions: (1) bar charts showing the inflows and outflows; (2) summary tables with additional metrics that provide average groundwater budget components and metrics for the simulation period, the four analysis periods, and for the years with highest and lowest precipitation that occurred before and after the implementation of water supply projects; and (3) average groundwater budget flow charts of inflows, outflows, and storage loss that can be readily compared to similar plots published for prior analyses (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>).</p>
<sec id="sac23-0784_Final_20260508_kc.GroundwaterBudgetComponents">
<title>Groundwater Budget Components</title>
<p>Some items in the groundwater budget bar graphs and summary tables are presented as net values where the sum of inflow and outflow for each budget component are added to compute a net gain or loss. Positive values equal a gain in flow, and negative values equal a loss in flow. These net budget components include recharge, stream leakage, interbasin underflow, subbasin underflow, riparian underflow, seawater coastal inflow, and aquifer storage change. Recharge is computed as the difference between direct groundwater uptake by vegetation and the amount of water that percolates into the subsurface. Recharge is generally positive in the groundwater budget but can be negative if groundwater evapotranspiration is greater than the amount of percolation. Stream leakage is the amount of water that infiltrates in all stream segments and is comprised of Salinas River infiltration and other channel infiltration. Interbasin underflow is the onshore flow into the model domain from adjacent groundwater basins outside of the active model domain that is simulated by the inland GHB (<xref ref-type="fig" rid="fig25">fig. 25</xref>). Subbasin underflow is the regional groundwater flow to the analysis region within the active model domain. Riparian underflow is the regional groundwater flow to an analysis region from the riparian area. Seawater coastal inflow is landward flow from the ocean simulated at the coastal GHB (<xref ref-type="fig" rid="fig25">fig. 25</xref>). Aquifer storage change is the difference between all outflows and inflows. The sign convention for aquifer storage can lead to positive and negative values that are counterintuitive; they are explained in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.GroundwaterBudgetBarPlots">Groundwater Budget Bar Plots</xref>&#x201D; section.</p>
<p>The components of outflows in groundwater budgets include surface drainage, riparian drainage, tributary drainage, surface drainage, M &amp; I pumpage, and agricultural pumpage. Surface drainage occurs when groundwater is above the land surface in a model cell that is not associated with a stream. Riparian drainage occurs when groundwater is above the land surface in a model cell in the riparian area. Tributary drainage occurs when groundwater is above the land surface in a model cell that contains a stream segment outside of the Salinas River. Municipal and industrial pumpage is specified using furnished and estimated data (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). Agricultural pumpage is simulated to meet demands by FMP. Important groundwater budget components for water managers include total recharge, stream recharge (recharge from the surface-water drainage network outside of the Salinas River), riparian underflow to each analysis region sourced from recharge in the Salinas River, total pumpage, pumpage-recharge fraction (the fraction of analysis region pumping to recharge), aquifer storage change, and groundwater depletion.</p>
</sec>
<sec id="sac23-0784_Final_20260508_kc.GroundwaterBudgetBarPlots">
<title>Groundwater Budget Bar Plots</title>
<p>Groundwater budget bar plots (<xref ref-type="fig" rid="fig38">fig. 38</xref>) show the volumes of each groundwater budget component. In these plots, aquifer storage change is negative if there are more inflows than outflows. This sign convention for the groundwater budget bar plots ensures that the sum of inflows equals the sum of outflows. In the cumulative storage change line plots for each groundwater budget bar plot and in the groundwater budget summary tables (<xref ref-type="table" rid="t11">tables 11</xref>&#x2013;<xref ref-type="table" rid="t16">16</xref>), the sign for aquifer storage change and cumulative storage change are reversed (multiplied by &#x2212;1) so that the changes in storage are shown as expected, with positive values indicating an increase in storage and negative values indicating a decrease in storage. The cumulative storage curves plotted on each groundwater budget bar plot show the actual change in groundwater volume starting in 1970.</p>
<fig id="fig38" position="float" fig-type="figure"><label>Figure 38</label><caption><p>Distribution of groundwater-budget components of inflows and outflows for the flow system of the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1970&#x2013;2018. <italic>A</italic>, Entire integrated hydrologic model domain; <italic>B</italic>, Riparian analysis region; <italic>C</italic>, Pressure analysis region; <italic>D</italic>, East Side-Langley analysis region; <italic>E</italic>, Forebay analysis region; and <italic>F</italic>, Upper Valley analysis region (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>38.</bold>	Graphs showing distribution of groundwater-budget components of inflows and outflows for the flow system of the Salinas Valley Integrated Hydrologic Model in Monterey and San Luis Obispo Counties of California for water years 1970&#x2013;2018</p></caption><long-desc>38. The major groundwater inflow is stream leakage, and the major outflow is agricultural pumpage.</long-desc><graphic xlink:href="sac23-0784_fig38a"/><graphic xlink:href="sac23-0784_fig38b"/><graphic xlink:href="sac23-0784_fig38c"/><graphic xlink:href="sac23-0784_fig38d"/><graphic xlink:href="sac23-0784_fig38e"/><graphic xlink:href="sac23-0784_fig38f"/></fig>
</sec>
<sec>
<title>Groundwater Budget Summary Tables</title>
<p>Groundwater budget summary tables provide quantities of interest averaged over analysis periods and for selected high and low precipitation years. Comparison of quantities of interest over analysis periods and for selected high and low precipitation years allows the evaluation of these quantities under different historical conditions. The quantities of interest distill information from the budgets to inform decision making and sustainability efforts. These quantities of interest include net average groundwater inflows and outflows, as described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.GroundwaterBudgetComponents">Groundwater Budget Components</xref>&#x201D; section, and summarized values, such as local stream recharge, total recharge, total pumpage, pumpage-recharge fraction, storage loss, and groundwater depletion. Analyses of recharge, pumping, and groundwater depletion are supported by these summarized quantities of interest.</p>
<p>The local stream recharge is the stream leakage from all other surface-water drainage features except the Salinas River minus the sum of riparian and tributary drainage. Total recharge is computed as the sum of components of groundwater recharge, consisting of the recharge and stream recharge. Total pumpage is the sum of M &amp; I and agricultural pumpage. Total recharge, total pumpage, and their ratio (pumpage-recharge fraction) provide information about drivers of aquifer storage change and local groundwater sustainability. Storage loss is the absolute value of the aquifer storage change groundwater budget component if aquifer storage change is negative. Groundwater depletion is the sum of storage loss and the seawater coastal inflow groundwater budget component. Groundwater depletion is an important quantity for sustainability analyses and to quantify the effect of water management strategies on the undesirable effects of unsustainable groundwater use, such as seawater coastal inflow and storage loss.</p>
</sec>
<sec>
<title>Groundwater Budget Flow Charts</title>
<p>The groundwater budget flow charts show the average annual budget components and summarized values for the integrated hydrologic model domain and each of the five analysis regions. Each flow chart has defined inflows and outflows and provides a concise view of the groundwater budgets. The groundwater budget terms and summarized values are represented using boxes with arrows that indicate the direction of flow (in or out). This simple view of the budget facilitates an easy comparison to budgets evaluated in prior Salinas Valley analyses.</p>
</sec>
<sec>
<title>Integrated Hydrologic Model Domain Groundwater Budget</title>
<p>The groundwater budget bar plots for the integrated hydrologic model domain show pumpage and cycles of wet and dry years with cumulative storage change increasing in period A, decreasing during the dry period (period B), recovering in period C, and declining again in the most recent dry period (period D; <xref ref-type="fig" rid="fig38">fig. 38<italic>A</italic></xref>). Groundwater budget analysis for the integrated hydrologic model domain (<xref ref-type="table" rid="t11">table 11</xref>) shows that average aquifer storage changes over the four analysis periods range from 139 TAFY (out) to 158 TAFY (in). There is substantial variability within the high and low precipitation end-member years before and after the SRDF, with pre-SRDF values ranging from 451 TAFY (out) in 1989 to 214 TAFY (in) in 1983, and post-SRDF values ranging from 275 TAFY (out) in 2013 to 112 TAFY (in) in 2013. The average storage losses were high during dry periods&#x2014;139 TAFY (out) in analysis period B and 83 TAFY (out) in analysis period D. The driest year in period B (1989) had a substantial storage depletion of 469 TAFY. The driest year in period D (2013) had substantial but lower storage depletion of 275 TAFY. The effects of this depletion can be observed in the lowering of groundwater levels throughout the basin (<xref ref-type="fig" rid="fig33">figs. 33<italic>A</italic>&#x2013;<italic>E</italic></xref>). The lowest recorded measurements of groundwater levels occurred during the dry years of analysis, period B. The long-term average groundwater depletion is about 15 TAFY, comprised of mostly seawater coastal inflow. The average seawater coastal inflow varied over the analysis periods and individual years from 12 to 18 TAFY. There are slightly lower average values after the implementation of the SRDF (analysis period D) even though the conditions were dry for much of that analysis period. The magnitude of seawater coastal inflow is higher in years with higher overdraft (<xref ref-type="fig" rid="fig38">fig. 38<italic>A</italic></xref>), so the cumulative effect of multiple years of overdraft may have a more substantial effect on usable storage of the aquifer than the long-term average implies.</p>
<table-wrap id="t11" orientation="landscape" position="float"><label>Table 11</label><caption>
<title>Summary of groundwater budget data for the Salinas Valley Integrated Hydrologic Model domain for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>11.</bold>	Summary of groundwater budget data for the Salinas Valley Integrated Hydrologic Model domain for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="23.55%"/>
<col width="8.2%"/>
<col width="7.1%"/>
<col width="7.12%"/>
<col width="8.54%"/>
<col width="7.05%"/>
<col width="9.5%"/>
<col width="9.72%"/>
<col width="9.5%"/>
<col width="9.72%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire simulation 1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period A 1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period B 1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period C 1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period D 2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">93</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">159</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">79</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">80</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">168</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">55</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">58</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">2</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">683</td>
<td valign="top" align="char" char=".">790</td>
<td valign="top" align="char" char=".">575</td>
<td valign="top" align="char" char=".">757</td>
<td valign="top" align="char" char=".">527</td>
<td valign="top" align="char" char=".">1113</td>
<td valign="top" align="char" char=".">271</td>
<td valign="top" align="char" char=".">748</td>
<td valign="top" align="char" char=".">386</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;171</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;208</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;147</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;190</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;112</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;350</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;74</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;181</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;90</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="char" char=".">&#x2212;8</td>
<td valign="top" align="char" char=".">&#x2212;9</td>
<td valign="top" align="char" char=".">&#x2212;6</td>
<td valign="top" align="char" char=".">&#x2212;11</td>
<td valign="top" align="char" char=".">&#x2212;6</td>
<td valign="top" align="char" char=".">&#x2212;18</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="char" char=".">&#x2212;10</td>
<td valign="top" align="char" char=".">&#x2212;3</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;89</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;116</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;73</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;99</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;47</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;238</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;30</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;88</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;35</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Interbasin underflow</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
<td valign="top" align="char" char=".">&#x2212;5</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Municipal and industrial pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;53</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;48</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;67</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;57</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;44</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;49</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;66</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;62</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char=".">&#x2212;457</td>
<td valign="top" align="char" char=".">&#x2212;431</td>
<td valign="top" align="char" char=".">&#x2212;530</td>
<td valign="top" align="char" char=".">&#x2212;447</td>
<td valign="top" align="char" char=".">&#x2212;423</td>
<td valign="top" align="char" char=".">&#x2212;426</td>
<td valign="top" align="char" char=".">&#x2212;635</td>
<td valign="top" align="char" char=".">&#x2212;356</td>
<td valign="top" align="char" char=".">&#x2212;481</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Seawater coastal inflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">15</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">13</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="char" char=".">158</td>
<td valign="top" align="char" char=".">&#x2212;139</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">&#x2212;83</td>
<td valign="top" align="char" char=".">214</td>
<td valign="top" align="char" char=".">&#x2212;451</td>
<td valign="top" align="char" char=".">112</td>
<td valign="top" align="char" char=".">&#x2212;275</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">415</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">457</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">349</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">457</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">362</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">507</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">165</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">469</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">258</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">508</td>
<td valign="top" align="char" char=".">616</td>
<td valign="top" align="char" char=".">428</td>
<td valign="top" align="char" char=".">537</td>
<td valign="top" align="char" char=".">390</td>
<td valign="top" align="char" char=".">675</td>
<td valign="top" align="char" char=".">220</td>
<td valign="top" align="char" char=".">527</td>
<td valign="top" align="char" char=".">260</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">510</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">469</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">578</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">514</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">480</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">470</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">684</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">422</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">543</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">0.8</td>
<td valign="top" align="char" char=".">1.4</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">1.2</td>
<td valign="top" align="char" char=".">0.7</td>
<td valign="top" align="char" char=".">3.1</td>
<td valign="top" align="char" char=".">0.8</td>
<td valign="top" align="char" char=".">2.1</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">139</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">83</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">451</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">275</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">15</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">16</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">155</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">14</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">95</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">14</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">469</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">12</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">288</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t11n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t11n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t11n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t11n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t11n5"><label><sup>5</sup></label>
<p>Stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t11n6"><label><sup>6</sup></label>
<p>Recharge plus stream recharge.</p></fn>
<fn id="t11n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t11n8"><label><sup>8</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t11n9"><label><sup>9</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t11n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Over the simulation analysis period, the average total recharge was 597 TAFY, average recharge was 93 TAFY, and average stream recharge was 504 TAFY (<xref ref-type="table" rid="t11">table 11</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>A</italic></xref>). Total recharge varied from year to year over the individual wet and dry analysis years, ranging from 250 TAFY in 1989 to 913 TAFY in 1983. The average total recharge for analysis periods A and B (1970&#x2013;1994), 732 and 501 TAFY, respectively, are higher than previous groundwater budget tabulations that were 454 TAFY for the period 1970&#x2013;92 (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). However, the model domain in this study is about 40 percent larger than the SVIGSM from which that estimate was determined.</p>
<fig id="fig39" position="float" fig-type="figure"><label>Figure 39</label><caption><p>Average groundwater budget from water year 1970 through 2018 showing budget components (in thousands of acre-feet) for the <italic>A</italic>, entire Salinas Valley Integrated Hydrologic Model domain in Monterey and San Luis Obispo Counties of California; <italic>B</italic>, Riparian analysis region; <italic>C</italic>, Pressure analysis region; <italic>D</italic>, East Side-Langley analysis region; <italic>E</italic>, Forebay analysis region; and <italic>F</italic>, Upper Valley analysis region of Salinas Valley Integrated Hydrologic Model domain (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>39.</bold>	Graphs showing average groundwater budget from water year 1970 through 2018 showing budget components for the entire Salinas Valley Integrated Hydrologic Model domain in Monterey and San Luis Obispo Counties of California, Riparian analysis region, Pressure analysis region, East Side-Langley analysis region, Forebay analysis region, and Upper Valley analysis region of Salinas Valley Integrated Hydrologic Model domain</p></caption><long-desc>39. On average, the major inflow is stream leakage, and the major outflow is total pumpage.</long-desc><graphic xlink:href="sac23-0784_fig39"/></fig>
<p>For the integrated hydrologic model domain, interbasin underflow is minimal and did not vary among analysis subperiods; flow to adjacent groundwater basins outside of the study area was less than 1 percent of total pumpage (5 TAFY out). The interbasin underflow is different from the 1970&#x2013;1994 estimates of 38 TAFY into the SVIGSM model domain (<xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>; <xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). The boundaries for interbasin underflow are defined using measured GHB well data in the SVIHM (<xref ref-type="fig" rid="fig25">figs. 25</xref>&#x2013;<xref ref-type="fig" rid="fig26">26</xref>), which is constructed differently from the formulation in the SVIGSM. Additionally, the SVIHM has a greater extent that may capture some regional flow paths not within the SVIGSM boundary.</p>
<p>Over the simulation period, average annual total pumpage was 510 TAFY (<xref ref-type="table" rid="t11">table 11</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>A</italic></xref>), with average agricultural pumpage of 457 TAFY and average M &amp; I pumpage of about 12 percent of agricultural pumpage (53 TAFY; <xref ref-type="table" rid="t11">table 11</xref>). The average total pumpage for analysis periods A and B (1970&#x2013;1994), 469 and 578 TAFY, respectively, average to 524 TAFY, which is close to the previous groundwater budget tabulations of 519 TAFY for the period from 1970 to 1994 (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). Total pumpage in the most recent analysis period D (480 TAFY) is similar to the earliest period (469 TAFY) even though total harvested area has increased from approximately 300,000 to 400,000 acres over that time (<xref ref-type="fig" rid="fig07">fig. 7</xref>). An increase in total harvest area while maintaining a similar pumpage illustrates the effect of water conservation efforts and more efficient irrigation technology.</p>
<p>The average pumpage-recharge fraction is an indicator of the relationship between the magnitude of pumping relative to the magnitude of recharge. For basin wide groundwater sustainability, values should be less than 1.0. The average pumpage-recharge fraction for the simulation period is 0.9 (<xref ref-type="table" rid="t11">table 11</xref>). The maximum average pumpage-recharge fraction among all analysis periods is 1.2 during the dry years of analysis, period B. The average pumpage-recharge fraction over the entire simulation period of 0.9 suggests that a substantial amount of total recharge for the integrated hydrologic model domain is used to meet current demands on an average basis. The average pumpage-recharge fraction for dry years greater than 1 highlights the challenges of interannual and seasonal variability and meeting water demands sustainably.</p>
</sec>
<sec>
<title>Analysis Region Groundwater Budgets</title>
<p>Over the simulation period, analysis regions other than the Riparian analysis region (Pressure, East Side-Langley, Forebay, and Upper Valley) had similar trends across analysis subperiods A through D, showing similar responses to the climate. Riparian underflow from the Riparian analysis region contributed substantially to inflows in each period throughout three of the four other analysis regions, all but the East Side-Langley analysis region (<xref ref-type="fig" rid="fig38">figs. 38<italic>C</italic>&#x2013;<italic>F</italic></xref>; <xref ref-type="table" rid="t12">tables 12</xref>&#x2013;<xref ref-type="table" rid="t15">15</xref>). Generally, the sources of inflows to analysis regions in order of decreasing magnitude are riparian underflow (groundwater flow between the Riparian analysis region and other analysis regions), recharge, and local stream recharge (locally sourced recharge from surface-water network drainage within the analysis region). The sources of outflows from analysis regions in order of decreasing magnitude are agricultural pumpage, M &amp; I pumpage, and surface drainage. The average pumpage-recharge fraction in each analysis region is an indicator of the relationship between the magnitude of pumping relative to the magnitude of locally sourced recharge. Simulation period and analysis period average pumpage-recharge fractions above 1.0 indicate that water demands are met using riparian underflow from the Salinas River, subbasin underflow from adjacent analysis regions, or reductions in groundwater storage. The pumpage-recharge fraction can be a useful indicator for understanding local versus exogenous sources of groundwater supply to each analysis region.</p>
<sec>
<title>Riparian Analysis Region</title>
<p>The Salinas River is an important source of recharge in the integrated hydrologic model domain. The riparian area of the Salinas River is its own WBS, so the regional groundwater flow to adjacent analysis regions is represented clearly. The contribution of the Salinas River recharge to each analysis region is represented by the riparian underflow budget component. The contribution of all other surface-water drainage features in each analysis region is represented by the &#x201C;stream recharge&#x201D; budget component. The year-by-year groundwater budget is shown on <xref ref-type="fig" rid="fig38">figure 38<italic>B</italic></xref> and illustrates substantial contributions from stream leakage and subbasin underflow to adjacent analysis regions. <xref ref-type="table" rid="t12">Table 12</xref> provides a summary of the groundwater budget for the Riparian analysis region to support evaluation of annual average groundwater budgets over the period from WY 1970 to 2018 (<xref ref-type="fig" rid="fig39">fig. 39<italic>B</italic></xref>).</p>
<table-wrap id="t12" orientation="landscape" position="float"><label>Table 12</label><caption>
<title>Summary of groundwater budget data for the Riparian analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>12.</bold>	Summary of groundwater budget data for the Riparian analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="22.58%"/>
<col width="8.45%"/>
<col width="7.04%"/>
<col width="7.04%"/>
<col width="8.45%"/>
<col width="7.04%"/>
<col width="9.85%"/>
<col width="9.85%"/>
<col width="9.85%"/>
<col width="9.85%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire simulation <break/>1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period A <break/>1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period B 1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period C 1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period D 2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;101</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;98</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;100</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;104</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;100</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;100</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;106</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;96</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;106</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">569</td>
<td valign="top" align="char" char=".">662</td>
<td valign="top" align="char" char=".">478</td>
<td valign="top" align="char" char=".">629</td>
<td valign="top" align="char" char=".">436</td>
<td valign="top" align="char" char=".">948</td>
<td valign="top" align="char" char=".">212</td>
<td valign="top" align="char" char=".">622</td>
<td valign="top" align="char" char=".">324</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;171</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;208</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;147</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;190</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;112</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;350</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;74</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;181</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;90</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian underflow</td>
<td valign="top" align="char" char=".">&#x2212;291</td>
<td valign="top" align="char" char=".">&#x2212;339</td>
<td valign="top" align="char" char=".">&#x2212;243</td>
<td valign="top" align="char" char=".">&#x2212;325</td>
<td valign="top" align="char" char=".">&#x2212;221</td>
<td valign="top" align="char" char=".">&#x2212;530</td>
<td valign="top" align="char" char=".">&#x2212;114</td>
<td valign="top" align="char" char=".">&#x2212;321</td>
<td valign="top" align="char" char=".">&#x2212;166</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Interbasin underflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Municipal &amp; industrial pumpage</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;13</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;13</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;16</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;14</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Seawater coastal inflow</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">2</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;41</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;97</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;51</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Local stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">297</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">356</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">231</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">335</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">224</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">498</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">345</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">128</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">297</td>
<td valign="top" align="char" char=".">356</td>
<td valign="top" align="char" char=".">231</td>
<td valign="top" align="char" char=".">335</td>
<td valign="top" align="char" char=".">224</td>
<td valign="top" align="char" char=".">498</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">345</td>
<td valign="top" align="char" char=".">128</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">13</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">0.1</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">0.1</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">0.5</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">0.1</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">41</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">97</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">51</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">7</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">2</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">26</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">5</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">10</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">43</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">99</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">1</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">53</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t12n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t12n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t12n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t12n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t12n5"><label><sup>5</sup></label>
<p>Analysis region recharge plus stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t12n6"><label><sup>6</sup></label>
<p>Stream recharge.</p></fn>
<fn id="t12n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t12n8"><label><sup>8</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t12n9"><label><sup>9</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t12n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>In the Riparian analysis region, riparian vegetation water demands near streams are greater than deep percolation, resulting in a negative average recharge value among all analysis periods that ranges from 98 to 104 TAFY (out). To prevent confusion caused by the negative recharge values in discussion of this analysis region, total recharge is assumed to be equal to the sum of recharge, stream leakage, and riparian and tributary drainage. The average annual total recharge is 297 TAFY and ranges from 224 and 356 TAFY among all analysis periods. Subbasin underflow out to adjacent analysis regions is an average of 291 TAFY and varies between 221 and 339 TAFY among the analysis periods (<xref ref-type="table" rid="t12">table 12</xref>). Total pumpage is less than 14 TAFY, which is approximately 2 percent of the average total pumpage in the basin (<xref ref-type="table" rid="t11">tables 11</xref>&#x2013;<xref ref-type="table" rid="t12">12</xref>). However, this amount of pumpage in the riparian area is based on the defined riparian area of the riparian WBS and reported groundwater use where required. This volume may not represent the total volume of pumpage within or near the riparian area. Aerial imagery indicates that there are agricultural fields, wells, and storage ponds near the stream channels with water use that may not be subject to mandatory reporting. However, the pumpage-recharge fraction is still very low in this analysis region. The cumulative groundwater storage change line plot shows increases and decreases in response to wetter and drier analysis periods but minimal groundwater storage depletion overall. Storage loss is low, averaging 5 TAFY, with a minimum average near zero in analysis period A and a maximum average of 24 TAFY in the driest analysis, period B (<xref ref-type="table" rid="t12">table 12</xref>). Seawater coastal inflow is relatively consistent (2 TAFY) and is a small portion of the total simulated values for the integrated hydrologic model domain.</p>
</sec>
<sec>
<title>Pressure Analysis Region</title>
<p>The Pressure analysis region is along the Monterey Bay coast and is a substantial area of agricultural production with several water supply projects, including CSIP and SRDF. The 180/400-Foot Aquifer groundwater basin represented by this analysis region has had substantial seawater coastal inflow. The year-by-year groundwater budget is shown on <xref ref-type="fig" rid="fig38">figure 38<italic>C</italic></xref> and illustrates substantial contributions from riparian underflow and agricultural pumpage. <xref ref-type="table" rid="t13">Table 13</xref> provides a summary of the groundwater budget for the Pressure analysis region to support evaluation of annual average groundwater budgets over the period from WY 1970 to 2018 (<xref ref-type="fig" rid="fig39">fig. 39<italic>C</italic></xref>).</p>
<table-wrap id="t13" orientation="landscape" position="float"><label>Table 13</label><caption>
<title>Summary of groundwater budget data for the Pressure analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>13.</bold>	Summary of groundwater budget data for the Pressure analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="23.43%"/>
<col width="8.51%"/>
<col width="7.02%"/>
<col width="7.16%"/>
<col width="8.51%"/>
<col width="7.09%"/>
<col width="9.46%"/>
<col width="9.68%"/>
<col width="9.46%"/>
<col width="9.68%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire simulation 1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period A 1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period B 1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period C 1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period D 2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">46</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">64</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">47</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">37</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">64</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">48</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">29</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">24</td>
<td valign="top" align="char" char=".">32</td>
<td valign="top" align="char" char=".">23</td>
<td valign="top" align="char" char=".">43</td>
<td valign="top" align="char" char=".">14</td>
<td valign="top" align="char" char=".">30</td>
<td valign="top" align="char" char=".">16</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="char" char=".">&#x2212;3</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="char" char=".">&#x2212;6</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;65</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;8</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian underflow</td>
<td valign="top" align="char" char=".">105</td>
<td valign="top" align="char" char=".">122</td>
<td valign="top" align="char" char=".">88</td>
<td valign="top" align="char" char=".">118</td>
<td valign="top" align="char" char=".">76</td>
<td valign="top" align="char" char=".">186</td>
<td valign="top" align="char" char=".">45</td>
<td valign="top" align="char" char=".">113</td>
<td valign="top" align="char" char=".">56</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Subbasin underflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Interbasin underflow</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Municipal and industrial pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;40</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;42</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;43</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char=".">&#x2212;118</td>
<td valign="top" align="char" char=".">&#x2212;119</td>
<td valign="top" align="char" char=".">&#x2212;148</td>
<td valign="top" align="char" char=".">&#x2212;108</td>
<td valign="top" align="char" char=".">&#x2212;96</td>
<td valign="top" align="char" char=".">&#x2212;118</td>
<td valign="top" align="char" char=".">&#x2212;180</td>
<td valign="top" align="char" char=".">&#x2212;78</td>
<td valign="top" align="char" char=".">&#x2212;110</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Seawater coastal inflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char=".">6</td>
<td valign="top" align="char" char=".">45</td>
<td valign="top" align="char" char=".">&#x2212;33</td>
<td valign="top" align="char" char=".">7</td>
<td valign="top" align="char" char=".">&#x2212;16</td>
<td valign="top" align="char" char=".">73</td>
<td valign="top" align="char" char=".">&#x2212;96</td>
<td valign="top" align="char" char=".">27</td>
<td valign="top" align="char" char=".">&#x2212;62</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Local stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">30</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">37</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">51</td>
<td valign="top" align="char" char=".">65</td>
<td valign="top" align="char" char=".">52</td>
<td valign="top" align="char" char=".">40</td>
<td valign="top" align="char" char=".">43</td>
<td valign="top" align="char" char=".">36</td>
<td valign="top" align="char" char=".">56</td>
<td valign="top" align="char" char=".">38</td>
<td valign="top" align="char" char=".">35</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">150</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">141</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">176</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">148</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">134</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">144</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">208</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">120</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">153</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="char" char=".">2.9</td>
<td valign="top" align="char" char=".">2.2</td>
<td valign="top" align="char" char=".">3.4</td>
<td valign="top" align="char" char=".">3.7</td>
<td valign="top" align="char" char=".">3.1</td>
<td valign="top" align="char" char=".">4</td>
<td valign="top" align="char" char=".">3.7</td>
<td valign="top" align="char" char=".">3.2</td>
<td valign="top" align="char" char=".">4.4</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">33</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">16</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">96</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">62</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">11</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">10</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">44</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">11</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">26</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">9</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">110</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">10</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">72</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t13n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t13n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t13n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t13n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t13n5"><label><sup>5</sup></label>
<p>Analysis region stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t13n6"><label><sup>6</sup></label>
<p>Recharge plus stream recharge.</p></fn>
<fn id="t13n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t13n8"><label><sup>8</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t13n9"><label><sup>9</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t13n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Average total recharge for the simulation and all analysis periods ranges from 54 to 94 TAFY, with local stream recharge representing about 30 percent of total recharge. Riparian underflow is a substantial inflow, with averages that range from 76 to 122 TAFY and an average of 105 TAFY over the simulation period. The average subbasin underflow to adjacent analysis regions is minimal, with a simulation period average of 11 TAFY (out) that varies between 8 and 14 TAFY (out) among the analysis periods (<xref ref-type="table" rid="t13">table 13</xref>). The average total pumpage simulation period average is 150 TAFY and varies between 134 and 176 TAFY among all analysis periods. Pressure analysis region average pumpage-recharge fraction for the simulation period is 2.1. The maximum average pumpage-recharge fraction among all analysis periods is 2.5 and occurred during the dry years of analysis, periods B and D. Higher riparian underflow and negative (out) subbasin underflow suggests that riparian underflow and groundwater storage are used to meet a portion of current pumping demands on an average basis, and reductions in Salinas River streamflow may contribute to storage loss. The cumulative groundwater storage change line plot shows an increase in analysis period A, substantial storage loss in analysis period B, recovery in analysis period C, and storage declines in the most recent analysis, period D (<xref ref-type="fig" rid="fig38">fig. 38<italic>C</italic></xref>). Historical storage declines (<xref ref-type="fig" rid="fig38">fig. 38<italic>C</italic></xref>) are supported by changes in groundwater levels. A steep decline in groundwater levels was observed in response to the dry period B; however, overall average drawdown observations for the region suggest that groundwater levels have recovered (<xref ref-type="fig" rid="fig33">figs. 33<italic>B</italic>&#x2013;<italic>E</italic></xref>) but are still low in the area near the city of Salinas (<xref ref-type="fig" rid="fig35">fig. 35</xref>). Average seawater coastal inflow ranges from 10 to 11 TAFY among all analysis periods, with an average of 11 TAFY over the simulation period. Groundwater depletion ranged from 11 to 44 TAFY among all analysis periods, with an average of 11 TAFY over the simulation period (<xref ref-type="table" rid="t13">table 13</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>C</italic></xref>).</p>
</sec>
<sec>
<title>East Side-Langley Analysis Region</title>
<p>The East Side-Langley analysis region is along the northern edge of the integrated hydrologic model on the flanks of the Gabilan Range and relatively disconnected from the Salinas River; thus, it does not receive much riparian underflow (averaging less than 1 TAFY for the simulation and analysis periods; <xref ref-type="table" rid="t14">table 14</xref>). The year-by-year groundwater budget is shown on <xref ref-type="fig" rid="fig38">figure 38<italic>D</italic></xref> and illustrates substantial contributions from subbasin underflow, recharge, and agricultural pumpage. <xref ref-type="table" rid="t14">Table 14</xref> provides a summary of the groundwater budget for the Eastside-Langley analysis region to support evaluation of annual average groundwater budgets over the period from WY 1970 to 2018 (<xref ref-type="fig" rid="fig39">fig. 39<italic>D</italic></xref>).</p>
<table-wrap id="t14" orientation="landscape" position="float"><label>Table 14</label><caption>
<title>Summary of groundwater budget data for the East Side-Langley analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>14.</bold>	Summary of groundwater budget data for the East Side-Langley analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="23.75%"/>
<col width="8.28%"/>
<col width="7.11%"/>
<col width="7.11%"/>
<col width="8.28%"/>
<col width="7.11%"/>
<col width="9.59%"/>
<col width="9.59%"/>
<col width="9.59%"/>
<col width="9.59%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire <break/>simulation <break/>1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis <break/>period A <break/>1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis <break/>period B <break/>1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis <break/>period C <break/>1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis <break/>period D <break/>2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high <break/>precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low <break/>precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high <break/>precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low <break/>precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">40</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">58</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">40</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">25</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">62</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">36</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">14</td>
<td valign="top" align="char" char=".">11</td>
<td valign="top" align="char" char=".">13</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">18</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">8</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian underflow</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Subbasin underflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">23</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">19</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Interbasin underflow</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Municipal and industrial pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;1</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char=".">&#x2212;81</td>
<td valign="top" align="char" char=".">&#x2212;83</td>
<td valign="top" align="char" char=".">&#x2212;96</td>
<td valign="top" align="char" char=".">&#x2212;74</td>
<td valign="top" align="char" char=".">&#x2212;71</td>
<td valign="top" align="char" char=".">&#x2212;84</td>
<td valign="top" align="char" char=".">&#x2212;104</td>
<td valign="top" align="char" char=".">&#x2212;59</td>
<td valign="top" align="char" char=".">&#x2212;80</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Seawater coastal inflow</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char=".">&#x2212;9</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">&#x2212;26</td>
<td valign="top" align="char" char=".">&#x2212;8</td>
<td valign="top" align="char" char=".">&#x2212;17</td>
<td valign="top" align="char" char=".">17</td>
<td valign="top" align="char" char=".">&#x2212;44</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="char" char=".">&#x2212;31</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Local stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">13</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">52</td>
<td valign="top" align="char" char=".">72</td>
<td valign="top" align="char" char=".">51</td>
<td valign="top" align="char" char=".">45</td>
<td valign="top" align="char" char=".">34</td>
<td valign="top" align="char" char=".">80</td>
<td valign="top" align="char" char=".">44</td>
<td valign="top" align="char" char=".">39</td>
<td valign="top" align="char" char=".">28</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">83</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">85</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">99</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">76</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">73</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">87</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">107</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">62</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">81</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="char" char=".">1.6</td>
<td valign="top" align="char" char=".">1.2</td>
<td valign="top" align="char" char=".">1.9</td>
<td valign="top" align="char" char=".">1.7</td>
<td valign="top" align="char" char=".">2.1</td>
<td valign="top" align="char" char=".">1.1</td>
<td valign="top" align="char" char=".">2.4</td>
<td valign="top" align="char" char=".">1.6</td>
<td valign="top" align="char" char=".">2.9</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">9</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">17</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">44</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">1</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">31</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">9</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">26</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">8</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">17</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">44</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">1</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">31</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t14n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t14n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t14n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t14n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t14n5"><label><sup>5</sup></label>
<p>Analysis region stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t14n6"><label><sup>6</sup></label>
<p>Recharge plus stream recharge.</p></fn>
<fn id="t14n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t14n8"><label><sup>8</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t14n9"><label><sup>9</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t14n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Average total recharge for the simulation and all analysis periods ranges from 34 to 72 TAFY, with local stream recharge representing about 20&#x2013;30 percent of total recharge. Subbasin underflow is a substantial inflow, with average values that range from 22 to 23 TAFY and an average of 22 TAFY over the simulation period (<xref ref-type="table" rid="t14">table 14</xref>). The average total pumpage over the simulation period is 83 TAFY and varies between 73 and 99 TAFY among all analysis periods. The average pumpage-recharge fraction for the East Side-Langley analysis region for the simulation period is 1.6. The maximum average pumpage-recharge fraction among all analysis periods is 2.1 during the recent dry years of analysis, period D. Low riparian underflow (less than 1 TAFY) and positive (in) subbasin underflow suggest that subbasin underflow and storage loss are used to meet a portion of current pumping demands on an average basis. This combination of the low riparian underflow and positive subbasin underflow suggests that groundwater budgets may be affected more by activities in adjacent analysis regions and underscores the role of analysis region connectivity in regional sustainability efforts. The cumulative groundwater storage change line plot shows a moderate increase in analysis period A and substantial storage declines for the rest of the simulation (<xref ref-type="fig" rid="fig38">fig. 38<italic>D</italic></xref>). Historical storage declines (<xref ref-type="fig" rid="fig38">fig. 38<italic>D</italic></xref>) are supported by changes in groundwater levels. A steep decline in groundwater levels was observed in response to dry analysis period B and have not recovered since (<xref ref-type="fig" rid="fig33">figs. 33<italic>F</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>G</italic></xref>). Groundwater depletion ranged from 8 to 26 TAFY among all analysis periods, with an average of 9 TAFY over the simulation period (<xref ref-type="table" rid="t14">table 14</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>D</italic></xref>).</p>
</sec>
<sec>
<title>Forebay Analysis Region</title>
<p>The Forebay analysis region is near the center of the basin. This region receives stream recharge from Arroyo Seco and the Salinas River and represents the transition between where deeper hydrogeologic units (Paso Robles and Purisima Formations) are closer to the surface (<xref ref-type="fig" rid="fig22">fig. 22<italic>B</italic></xref>) and the 180-Foot Aquifer and 400-Foot Aquifer hydrogeologic units thin or pinch out (<xref ref-type="fig" rid="fig23">figs. 23<italic>D</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>E</italic></xref>). The year-by-year groundwater budget is shown on <xref ref-type="fig" rid="fig38">figure 38<italic>E</italic></xref> and illustrates substantial contributions from subbasin underflow, recharge, and agricultural pumpage. <xref ref-type="table" rid="t15">Table 15</xref> provides a summary of the groundwater budget for the Forebay analysis region to support evaluation of annual average groundwater budgets over the period from WY 1970 to 2018 (<xref ref-type="fig" rid="fig39">fig. 39<italic>E</italic></xref>).</p>
<table-wrap id="t15" orientation="landscape" position="float"><label>Table 15</label><caption>
<title>Summary of groundwater budget data for the Forebay analysis region for the period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>15.</bold>	Summary of groundwater budget data for the Forebay analysis region for the period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="23.6%"/>
<col width="8.23%"/>
<col width="7.07%"/>
<col width="7.07%"/>
<col width="8.33%"/>
<col width="7.14%"/>
<col width="9.53%"/>
<col width="9.75%"/>
<col width="9.53%"/>
<col width="9.75%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire simulation 1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period A 1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period B 1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period C 1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period D 2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">46</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">59</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">44</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">47</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">53</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">48</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">32</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">28</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">48</td>
<td valign="top" align="char" char=".">53</td>
<td valign="top" align="char" char=".">39</td>
<td valign="top" align="char" char=".">55</td>
<td valign="top" align="char" char=".">39</td>
<td valign="top" align="char" char=".">68</td>
<td valign="top" align="char" char=".">23</td>
<td valign="top" align="char" char=".">56</td>
<td valign="top" align="char" char=".">23</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="char" char=".">&#x2212;6</td>
<td valign="top" align="char" char=".">&#x2212;6</td>
<td valign="top" align="char" char=".">&#x2212;4</td>
<td valign="top" align="char" char=".">&#x2212;7</td>
<td valign="top" align="char" char=".">&#x2212;4</td>
<td valign="top" align="char" char=".">&#x2212;10</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="char" char=".">&#x2212;7</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;36</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;48</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;42</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;18</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;102</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;13</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian underflow</td>
<td valign="top" align="char" char=".">110</td>
<td valign="top" align="char" char=".">128</td>
<td valign="top" align="char" char=".">93</td>
<td valign="top" align="char" char=".">122</td>
<td valign="top" align="char" char=".">82</td>
<td valign="top" align="char" char=".">194</td>
<td valign="top" align="char" char=".">48</td>
<td valign="top" align="char" char=".">120</td>
<td valign="top" align="char" char=".">62</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Subbasin underflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;6</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Interbasin underflow</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Municipal and industrial pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;9</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;15</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;11</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char=".">&#x2212;146</td>
<td valign="top" align="char" char=".">&#x2212;135</td>
<td valign="top" align="char" char=".">&#x2212;163</td>
<td valign="top" align="char" char=".">&#x2212;147</td>
<td valign="top" align="char" char=".">&#x2212;141</td>
<td valign="top" align="char" char=".">&#x2212;130</td>
<td valign="top" align="char" char=".">&#x2212;202</td>
<td valign="top" align="char" char=".">&#x2212;118</td>
<td valign="top" align="char" char=".">&#x2212;161</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Seawater coastal inflow</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char=".">2</td>
<td valign="top" align="char" char=".">43</td>
<td valign="top" align="char" char=".">&#x2212;33</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">&#x2212;27</td>
<td valign="top" align="char" char=".">64</td>
<td valign="top" align="char" char=".">&#x2212;108</td>
<td valign="top" align="char" char=".">30</td>
<td valign="top" align="char" char=".">&#x2212;78</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Local stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">42</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">47</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">48</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">35</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">58</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">21</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">49</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">21</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">52</td>
<td valign="top" align="char" char=".">58</td>
<td valign="top" align="char" char=".">50</td>
<td valign="top" align="char" char=".">53</td>
<td valign="top" align="char" char=".">46</td>
<td valign="top" align="char" char=".">9</td>
<td valign="top" align="char" char=".">59</td>
<td valign="top" align="char" char=".">43</td>
<td valign="top" align="char" char=".">36</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">155</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">139</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">170</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">162</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">151</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">135</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">209</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">128</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">172</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="char" char=".">3</td>
<td valign="top" align="char" char=".">2.4</td>
<td valign="top" align="char" char=".">3.4</td>
<td valign="top" align="char" char=".">3.1</td>
<td valign="top" align="char" char=".">3.3</td>
<td valign="top" align="char" char=".">15</td>
<td valign="top" align="char" char=".">3.5</td>
<td valign="top" align="char" char=".">3</td>
<td valign="top" align="char" char=".">4.8</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">33</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">27</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">108</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">78</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">33</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">27</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">108</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">78</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t15n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t15n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t15n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t15n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t15n5"><label><sup>5</sup></label>
<p>Analysis region stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t15n6"><label><sup>6</sup></label>
<p>Recharge plus stream recharge.</p></fn>
<fn id="t15n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t15n8"><label><sup>8</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t15n9"><label><sup>9</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t15n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Average total recharge for the simulation and all analysis periods ranges from 64 to 106 TAFY, with local stream recharge representing most total recharge. Subbasin underflow is out of the analysis region and not substantial, with average values among analysis periods that range from 4 to 6 TAFY for all analysis periods (<xref ref-type="table" rid="t15">table 15</xref>). Riparian underflow is a substantial inflow, with average values among analysis periods that range from 82 to 128 TAFY and an average of 110 TAFY over the simulation period. The average total pumpage over the simulation period is 155 TAFY and varies between 139 and 170 TAFY among all analysis periods. The average pumpage-recharge fraction for the Forebay analysis region for the simulation period is 1.8. The maximum average pumpage-recharge fraction among all analysis periods is 2.4 during the dry years of recent analysis, period D. Higher riparian underflow and negative (out) subbasin underflow suggests that riparian underflow is used to meet a portion of current pumping demands on an average basis, and reductions in Salinas River streamflow may contribute to storage loss. The cumulative groundwater storage change line plot shows an increase in analysis period A, substantial storage loss in analysis period B, recovery in analysis period C, and storage declines in the most recent analysis, period D. Historical storage declines and increases (<xref ref-type="fig" rid="fig38">fig. 38<italic>E</italic></xref>) are supported by changes in groundwater levels. A steep decline in groundwater levels was observed in response to dry period B, with recoveries in many areas (<xref ref-type="fig" rid="fig33">figs. 33<italic>H</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>I</italic></xref>). Groundwater depletion ranged from 27 to 33 TAFY among all analysis periods and averaged less than 1 TAFY over the simulation period (<xref ref-type="table" rid="t15">table 15</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>E</italic></xref>).</p>
</sec>
<sec>
<title>Upper Valley Analysis Region</title>
<p>In the Upper Valley analysis region, deeper hydrogeologic units (Paso Robles and Purisima Formations) are closer to the surface (<xref ref-type="fig" rid="fig22">fig. 22<italic>B</italic></xref>) and 180-Foot Aquifer and 400-Foot Aquifer hydrogeologic units thin or pinch out (<xref ref-type="fig" rid="fig23">figs. 23<italic>D</italic></xref>, <xref ref-type="fig" rid="fig23">23<italic>E</italic></xref>). Also, the number of known and specified supply and observation wells and groundwater level observations are more limited in the Upper Valley analysis region (<xref ref-type="table" rid="t09">table 9</xref>). All these factors should be considered in the evaluation of the groundwater budgets. The year-by-year groundwater budget is shown on <xref ref-type="fig" rid="fig38">figure 38<italic>F</italic></xref> and illustrates substantial contributions from agricultural pumpage, riparian underflow, and recharge. <xref ref-type="table" rid="t16">Table 16</xref> provides a summary of the groundwater budget for the Upper Valley analysis region to support evaluation of average groundwater budgets over the period from WY 1970 to 2018 (<xref ref-type="fig" rid="fig39">fig. 39<italic>F</italic></xref>).</p>
<table-wrap id="t16" orientation="landscape" position="float"><label>Table 16</label><caption>
<title>Summary of groundwater budget data for the Upper Valley analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented.</title>
<p content-type="toc"><bold>16.</bold>	Summary of groundwater budget data for the Upper Valley analysis region for the simulation period 1970&#x2013;2018, analysis periods A&#x2013;D, and high and low precipitation years representing conditions before and after the Salinas River Diversion Facility was implemented</p>
<p>[Average flows in thousands of acre-feet per year rounded to the nearest thousand. The calendar year is January through December. <bold>Abbreviations</bold>: GW, groundwater; &#x2014;, no data]</p></caption>
<table rules="groups">
<col width="23.61%"/>
<col width="8.17%"/>
<col width="7.02%"/>
<col width="7.02%"/>
<col width="8.81%"/>
<col width="7.09%"/>
<col width="9.46%"/>
<col width="9.68%"/>
<col width="9.46%"/>
<col width="9.68%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">GW-flow components</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Entire simulation 1970&#x2013;2018</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period A 1970&#x2013;83</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period B 1984&#x2013;94</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period C 1995&#x2013;2004</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Analysis period D 2010&#x2013;18</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>1</sup>1983 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>2</sup>1989 <break/>low precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>3</sup>2010 <break/>high precipitation</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt"><sup>4</sup>2013 <break/>low precipitation</td>
</tr>
</thead>
<tbody>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Net average GW inflows and outflows</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Recharge</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">33</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">41</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">34</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">42</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">25</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">33</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">22</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Stream leakage</td>
<td valign="top" align="char" char=".">11</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">10</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">8</td>
<td valign="top" align="char" char=".">16</td>
<td valign="top" align="char" char=".">7</td>
<td valign="top" align="char" char=".">12</td>
<td valign="top" align="char" char=".">8</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Riparian drainage</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Tributary drainage</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">&#x2212;2</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="char" char=".">&#x2212;1</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Surface drainage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;28</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;38</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;24</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;29</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;16</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;69</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;12</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;26</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;14</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Riparian underflow</td>
<td valign="top" align="char" char=".">74</td>
<td valign="top" align="char" char=".">83</td>
<td valign="top" align="char" char=".">61</td>
<td valign="top" align="char" char=".">82</td>
<td valign="top" align="char" char=".">61</td>
<td valign="top" align="char" char=".">132</td>
<td valign="top" align="char" char=".">27</td>
<td valign="top" align="char" char=".">85</td>
<td valign="top" align="char" char=".">48</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Subbasin underflow</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">5</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Interbasin underflow</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
<td valign="top" align="center">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Municipal and industrial pumpage</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;2</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;4</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">&#x2212;3</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Agricultural pumpage</td>
<td valign="top" align="char" char=".">&#x2212;94</td>
<td valign="top" align="char" char=".">&#x2212;78</td>
<td valign="top" align="char" char=".">&#x2212;103</td>
<td valign="top" align="char" char=".">&#x2212;99</td>
<td valign="top" align="char" char=".">&#x2212;98</td>
<td valign="top" align="char" char=".">&#x2212;80</td>
<td valign="top" align="char" char=".">&#x2212;124</td>
<td valign="top" align="char" char=".">&#x2212;86</td>
<td valign="top" align="char" char=".">&#x2212;111</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Seawater coastal inflow</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Aquifer storage change</td>
<td valign="top" align="char" char=".">&#x2212;4</td>
<td valign="top" align="char" char=".">20</td>
<td valign="top" align="char" char=".">&#x2212;26</td>
<td valign="top" align="char" char=".">1</td>
<td valign="top" align="char" char=".">&#x2212;20</td>
<td valign="top" align="char" char=".">41</td>
<td valign="top" align="char" char=".">&#x2212;76</td>
<td valign="top" align="char" char=".">17</td>
<td valign="top" align="char" char=".">&#x2212;47</td>
</tr>
<tr>
<th colspan="10" valign="top" align="center" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt" scope="col">Summarized quantities of interest</th>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Local stream recharge<sup>5</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">10</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">14</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">7</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">11</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">8</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Total recharge<sup>6</sup></td>
<td valign="top" align="char" char=".">15</td>
<td valign="top" align="char" char=".">14</td>
<td valign="top" align="char" char=".">15</td>
<td valign="top" align="char" char=".">16</td>
<td valign="top" align="char" char=".">16</td>
<td valign="top" align="char" char=".">&#x2212;13</td>
<td valign="top" align="char" char=".">20</td>
<td valign="top" align="char" char=".">18</td>
<td valign="top" align="char" char=".">16</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Total pumpage<sup>7</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">97</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">81</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">106</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">101</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">101</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">83</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">127</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">90</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">114</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Pumpage-recharge fraction<sup>8</sup></td>
<td valign="top" align="char" char=".">6.5</td>
<td valign="top" align="char" char=".">5.8</td>
<td valign="top" align="char" char=".">7.1</td>
<td valign="top" align="char" char=".">6.3</td>
<td valign="top" align="char" char=".">6.3</td>
<td valign="top" align="char" char=".">&#x2212;6.4</td>
<td valign="top" align="char" char=".">6.4</td>
<td valign="top" align="char" char=".">5</td>
<td valign="top" align="char" char=".">7.1</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Storage loss<sup>9</sup></td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">4</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">26</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">20</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">76</td>
<td valign="top" align="center" style="background-color:rgb(217,217,217)">&#x2014;</td>
<td valign="top" align="char" char="." style="background-color:rgb(217,217,217)">47</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Groundwater depletion<sup>10</sup></td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">4</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">26</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">20</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">76</td>
<td valign="top" align="center" style="border-bottom: solid 0.50pt">&#x2014;</td>
<td valign="top" align="char" char="." style="border-bottom: solid 0.50pt">47</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="t16n1"><label><sup>1</sup></label>
<p>Highest total precipitation for the entire active model domain before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t16n2"><label><sup>2</sup></label>
<p>Lowest total precipitation for the entire active model domain was before the implementation of the Salinas Valley Water Project.</p></fn>
<fn id="t16n3"><label><sup>3</sup></label>
<p>Highest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t16n4"><label><sup>4</sup></label>
<p>Lowest total precipitation for the entire active model domain after Salinas Valley Water Project implementation.</p></fn>
<fn id="t16n5"><label><sup>5</sup></label>
<p>Analysis region stream leakage plus riparian drainage plus tributary drainage.</p></fn>
<fn id="t16n6"><label><sup>6</sup></label>
<p>Recharge plus stream recharge.</p></fn>
<fn id="t16n7"><label><sup>7</sup></label>
<p>Agricultural pumpage plus municipal and industrial pumpage.</p></fn>
<fn id="t16n8"><label><sup>8</sup></label>
<p>Aquifer storage change less than 0.</p></fn>
<fn id="t16n9"><label><sup>9</sup></label>
<p>Absolute value of total pumpage/total recharge.</p></fn>
<fn id="t16n10"><label><sup>10</sup></label>
<p>Storage loss plus seawater intrusion.</p></fn>
</table-wrap-foot>
</table-wrap>
<p>Average total recharge for the simulation and all analysis periods ranges from 32 to 52 TAFY, with local stream recharge representing about 25 percent of total recharge. Subbasin underflow is not substantial, with average values between 3 and 5 TAFY for the simulation and all analysis periods (<xref ref-type="table" rid="t16">table 16</xref>). Riparian underflow is a substantial inflow, with average values among analysis periods that range from 61 to 83 TAFY and an average of 74 TAFY over the simulation period. The average total pumpage over the simulation period is 97 TAFY and ranges between 81 and 106 TAFY among all analysis periods. The average pumpage-recharge fraction for the Upper Valley analysis region is 2.3 for the simulation period. The maximum average pumpage-recharge fraction among all analysis periods is 3.2 during the dry years of recent analysis, period D. The presence of substantial riparian underflow and minimal subbasin underflow (simulation period average of 4 TAFY) suggests that riparian underflow and groundwater storage are used to meet a portion of current pumping demands on an average basis, and reductions in Salinas River streamflow may contribute to storage loss. The cumulative groundwater storage change line plot shows an increase in analysis period A, substantial storage loss in analysis period B, recovery in analysis period C, and storage declines in the most recent analysis period D (<xref ref-type="fig" rid="fig38">fig. 38<italic>F</italic></xref>). Historical storage declines and increases (<xref ref-type="fig" rid="fig38">fig. 38<italic>F</italic></xref>) are supported by changes in groundwater levels. A steep decline in groundwater levels was observed in response to the dry period B and have recovered in many areas (<xref ref-type="fig" rid="fig33">figs. 33<italic>J</italic></xref>, <xref ref-type="fig" rid="fig33">33<italic>K</italic></xref>). Groundwater depletion ranged from 20 to 26 TAFY among all analysis periods, with an average of 4 TAFY over the simulation period (<xref ref-type="table" rid="t16">table 16</xref>; <xref ref-type="fig" rid="fig39">fig. 39<italic>F</italic></xref>).</p>
</sec>
</sec>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.SalinasValleyOperationalModel">
<title>Salinas Valley Operational Model</title>
<p>The SVOM was developed to simulate current projects and reservoir operations for the Lake San Antonio and Lake Nacimiento reservoirs, such as reservoir storage and releases, flood mitigation, and management of Salinas River flows to support habitat conservation, fish passage, and downstream diversions for the SRDF (<xref ref-type="bibr" rid="r122">Monterey County Water Resources Agency, 2018</xref>). The operational model is a hypothetical baseline model developed to examine the benefit of different reservoir operations for the availability of water resources. The operational model is only to be used for scenario evaluation under hypothetical conditions that are informed and driven by historical conditions. It is a baseline model that will be used to evaluate how different hypothetical reservoir operation frameworks affect hydrologic flows and budgets.</p>
<p>The notable differences between the integrated hydrologic models (SVIHM and SVOM) are the model time-step length, a few boundary conditions related to the implementation of current projects and land use, and the direct simulation of reservoir inflows to the surface-water drainage network. Specifically, the SVOM has (1) the same initial conditions, historical climate, and climate year types as the SVIHM; (2) time steps that range from 5 to 6 days for the temporal discretization instead of bimonthly time steps used in the historical model; (3) constant 2014 land use; (4) current reservoir operational rules for flood management, required ecological flow targets, and downstream demands; (5) operation of SVWP (that includes the SRDF and CSIP) for the simulated period; and (6) simulated reservoir releases instead of specified reservoir releases that are used in the historical model. The properties in the calibrated historical model provide the basis for the operational model.</p>
<sec>
<title>Reservoir Release Simulation</title>
<p>The reservoir releases for the operational model are dynamically simulated using the surface-water operations capabilities of MF-OWHM (<xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>; <xref ref-type="bibr" rid="r10">Boyce, 2023</xref>). The operations model reservoir operation decisions are defined in a set of rules that are based on current reservoir operation rules and legal constraints, allowing for reservoir releases into the surface-water drainage network to be simulated internally to account for changes in reservoir storage and reservoir releases for conservation, demands, and flood management. Each rule has a set of logic statements that determine the magnitude and volume of reservoir releases (<xref ref-type="bibr" rid="r85">Henson and others, 2022a</xref>). The operational model rules are based on WY condition and are categorized as either dry, normal, or wet (based on surface-water flow percentiles, as described in the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.Climate">Climate</xref>&#x201D; subsection of the &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.DescriptionofStudyArea">Description of Study Area</xref>&#x201D; section). Both juvenile and smolt fish passage rules have a year type condition. However, the logic only specifies the terms &#x201C;dry&#x201D; and &#x201C;wet&#x201D; as triggers.</p>
<p>To simulate reservoir releases for the operational model, reservoir storage changes are simulated using storage input parameters that describe climate, watershed inflows, and reservoir evaporation (<xref ref-type="fig" rid="fig40">fig. 40</xref>). After reservoir storage is computed, conditions for operations are evaluated using operational rule parameters. The reservoir operation rule parameters include streamflow at designated gages, current reservoir storage, and WY type. Reservoir operation rule parameters are evaluated using the operational model rules. For each rule, if conditions are met, a target reservoir release amount is calculated. Each release from both reservoirs is simulated internally to account for changes in reservoir storage and to compute reservoir releases for conservation, demands, and flood mitigation. Within the conservation, demand, and flood mitigation releases, there are several rules that apply: flood release, fish passage, water rights, reservoir release fractions, spillway release thresholds, and the SRDF (<xref ref-type="table" rid="t17">table 17</xref>). Each rule includes logic statements that evaluate the reservoir operation inputs to determine if the conditions for the rule are met.</p>
<fig id="fig40" position="float" fig-type="figure"><label>Figure 40</label><caption><p>Model implementation summary for the Salinas Valley Operational Model in Monterey and San Luis Obispo Counties of California showing storage parameters that are used to simulate reservoir storage and operational rule parameters that are used to evaluate operational rules for conservation, demand, and floods to generate a time series of reservoir releases.</p><p content-type="toc"><bold>40.</bold>	Graph showing a model implementation summary for the Salinas Valley Operational Model in Monterey and San Luis Obispo Counties of California showing storage parameters that are used to simulate reservoir storage and operational rule parameters that are used to evaluate operational rules for conservation, demand, and floods to generate a time series of reservoir releases</p></caption><long-desc>40. Simulated reservoir releases are the result of reservoir operational rules and hydrologic and climatic inputs.</long-desc><graphic xlink:href="sac23-0784_fig40"/></fig>
<table-wrap id="t17" position="float"><label>Table 17</label><caption>
<title>Description of Salinas Valley Operational Model (SVOM) operational rules that define reservoir releases triggered based on flow conditions and downstream water demands.</title>
<p content-type="toc"><bold>17.</bold>	Description of Salinas Valley Operational Model operational rules that define reservoir releases triggered based on flow conditions and downstream water demands</p></caption>
<table rules="groups">
<col width="16.39%"/>
<col width="83.61%"/>
<thead>
<tr>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Ruleset</td>
<td valign="middle" align="center" scope="col" style="border-top: solid 0.50pt; border-bottom: solid 0.50pt">Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)" scope="row">Fish passage</td>
<td valign="top" align="left" style="border-top: solid 0.50pt; background-color:rgb(217,217,217)">Flow requirements for managing steelhead trout in the Salinas River follow the National Marine Fisheries Service Requirements across the lifecycle, including the adult steelhead upstream migration, downstream migration of smolt steelhead, downstream migration of juvenile and post-spawn adult steelhead, and spawning and rearing habitat.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Water rights</td>
<td valign="top" align="left">The flow requirements related to water rights evaluate the storage for each reservoir for accumulation and release to comply with water rights in the basin and deliver water to coastal communities to mitigate seawater intrusion.</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Flood release</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">The flow requirements related to flood release evaluate the downstream streamflow and the reservoir release to minimize high streamflow and mitigate flood threats.</td>
</tr>
<tr>
<td valign="top" align="left" scope="row">Reservoir release fraction</td>
<td valign="top" align="left">The relative fraction of water that is released from each of the reservoirs. The reservoir release fraction rules verify the storage in each of the reservoirs and evaluate the release demand to determine the reservoir from which the water should be released. One of the reservoir release fraction rules checks the logic at each iteration before convergence and the other checks the logic at each iteration after convergence.</td>
</tr>
<tr>
<td valign="top" align="left" style="background-color:rgb(217,217,217)" scope="row">Spillway release thresholds</td>
<td valign="top" align="left" style="background-color:rgb(217,217,217)">Reservoir operation thresholds determine the spill calculation and maximum release changes based on the reservoir stage.</td>
</tr>
<tr>
<td valign="top" align="left" style="border-bottom: solid 0.50pt" scope="row">Salinas River diversion facility</td>
<td valign="top" align="left" style="border-bottom: solid 0.50pt">Conveyance and flow requirements to compute reservoir releases to meet diversion targets at the diversion facility.</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The fish passage rules describe flow requirements for managing steelhead (<italic>Oncorhynchus mykiss</italic>) in the Salinas River. The fish passage rules follow the National Marine Fisheries Service Requirements (<xref ref-type="bibr" rid="r130">National Marine Fisheries Service, 2007</xref>) across four stages of the steelhead lifecycle: the adult steelhead upstream migration, downstream migration of smolt steelhead, downstream migration of juvenile and post-spawn adult steelhead, and spawning and rearing in freshwater habitats. The adult steelhead upstream migration requires a minimum flow rate at the Salinas River near Chualar (USGS 11152300; <xref ref-type="fig" rid="fig20">fig. 20</xref>) for a minimum duration when the river mouth is open to the ocean. The downstream migration of smolt steelhead requires minimum streamflow at various streamflow locations for 10 days or until the lagoon closes to the ocean during normal WY classification. Downstream migration of juvenile and post-spawn adult steelhead flow requires a minimum lagoon streamflow delivery for a specified duration in normal and wet WY classifications and a smaller minimum lagoon delivery flow in dry WY classifications. For spawning and rearing habitat below the Nacimiento Dam, additional reservoir releases are triggered.</p>
<p>After the logic of operational rules is evaluated to determine if reservoir releases are triggered, the reservoir releases are calculated to meet the flow requirement. If multiple operational rules are initiated for the same time step, then reservoir releases are computed as the minimum release that attains all operational targets. The streamflow into the channel where reservoir discharges occur is simulated as the sum of flows estimated by the watershed model for the simulated period (from October 1, 1967, to September 30, 2018) and the reservoir releases from Lakes San Antonio or Nacimiento reservoirs. In the operational model, reservoir releases are dynamically simulated using reservoir data and operational rules. Reservoir releases are not explicitly represented in the historical model (SVIHM). In the historical model, a time series of historical releases is added to the surface-water drainage network at the downstream segment from each reservoir as part of the calculated inflow from the watershed model.</p>
</sec>
<sec>
<title>Baseline Reservoir Results</title>
<p>For the operational model (SVOM), reservoir releases are a function of the reservoir storage and operational rule parameters (<xref ref-type="fig" rid="fig03">fig. 3</xref>). Reservoir storage and releases in the operational model are not meant to replicate the historical conditions. The reservoirs were not operated by the rules throughout time. In addition, reservoir operation decisions in the real world are made based on daily assessment of conditions and forecasts. In the operational model, reservoir operation decisions are made based on model objectives and conditions in the Salinas River, such as 5&#x2013;6-day average flows and monthly mean inflows to the integrated hydrologic model area from Arroyo Seco. However, there is good monthly and annual agreement between simulated reservoir storage and releases and historical conditions, indicating that the reservoir operations for the operational model are within the reasonable range for operating and are producing flows within the system&#x2019;s capacity (<xref ref-type="fig" rid="fig41">fig. 41</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>). For reservoir storage, both Lake Nacimiento and Lake San Antonio follow the monthly and annual patterns of the historical conditions (<xref ref-type="fig" rid="fig41">figs. 41<italic>A</italic></xref>, <xref ref-type="fig" rid="fig41">41<italic>B</italic></xref>). This finding suggests that the operational model and the associated rules are using the climate and reservoir inputs to simulate reservoir levels within the expected ranges and variations. Reservoir releases for Lake Nacimiento tend to resemble the annual releases more closely for historical conditions than for Lake San Antonio, with the average simulated reservoir releases lower than historical releases (<xref ref-type="fig" rid="fig41">fig. 41<italic>C</italic></xref>). On average, reservoir releases for Lake San Antonio are higher than historical releases. One reason for these differences is that the reservoir operation rules for the operational model are trying to optimize water storage and releases, which were controlled manually under historical conditions.</p>
<fig id="fig41" position="float" fig-type="figure"><label>Figure 41</label><caption><p>Reservoir observed data (<xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>) and simulated equivalent values in Lake San Antonio and Lake Nacimiento reservoirs showing <italic>A</italic>, monthly storage; <italic>B</italic>, annual mean reservoir storage; and <italic>C</italic>, total annual mean reservoir releases for the Salinas Valley Operational Model (SVOM) in Monterey and San Luis Obispo Counties of California. Reservoir storage and releases in the SVOM are not intended to replicate historical conditions. The historical time series is shown to illustrate that the SVOM results reasonably reproduce flows and storage within the boundaries of historical conditions (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>41.</bold>	Time-series plots showing reservoir observed data and simulated equivalent values in Lake San Antonio and Lake Nacimiento reservoirs showing monthly storage, annual mean reservoir storage, and total annual mean reservoir releases for the Salinas Valley Operational Model in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>41. Simulated and observed reservoir storage and release trends generally match though some values differ.</long-desc><graphic xlink:href="sac23-0784_fig41"/></fig>
<p>Trends in reservoir releases differ between the two reservoirs, with Lake Nacimiento releases being overall greater than Lake San Antonio with greater peak releases. Lake Nacimiento releases range from 7 to 649 TAFY (<xref ref-type="fig" rid="fig41">figs. 41<italic>C</italic></xref>, <xref ref-type="fig" rid="fig42">42<italic>A</italic></xref>). Lake Nacimiento has a higher storage capacity and generally maintains a larger storage volume compared to Lake San Antonio (<xref ref-type="fig" rid="fig41">figs. 41<italic>A</italic></xref>, <xref ref-type="fig" rid="fig41">41B</xref>, <xref ref-type="fig" rid="fig42">42<italic>B</italic></xref>). Lake San Antonio releases range from 2 to 296 TAFY (<xref ref-type="fig" rid="fig41">figs. 41<italic>C</italic></xref>, <xref ref-type="fig" rid="fig42">42<italic>A</italic></xref>). The reservoir releases and gains and losses along the river network play a key role for determining the total streamflow downstream to meet fish flow requirements. For adult fish, the median days per year that meet flow requirements (overall 51 years of the historical simulation) is 17 days, with an upper quartile of 38 days (75th percentile) and a maximum of 59 days (<xref ref-type="fig" rid="fig42">fig. 42<italic>C</italic></xref>). For kelt fish, the median days per year that meet flow requirements is 15 days, the upper quartile is 35 days (75th percentile), and the maximum is 81 days (<xref ref-type="fig" rid="fig42">fig. 42<italic>C</italic></xref>). For smolt fish, the median days per year that meet flow requirements is 15 days, the upper quartile is 36 days (75th percentile), and the maximum is 41 days (<xref ref-type="fig" rid="fig42">fig. 42<italic>C</italic></xref>). For juvenile fish, flow requirements were met 0 days per year for each year in the historical simulation. When combined reservoir releases and streamflow meet a minimum threshold, the SRDF can divert water. The number of active SRDF days per year ranges from 0 to 42 days, with a median of 42 days per year (<xref ref-type="fig" rid="fig42">fig. 42<italic>D</italic></xref>).</p>
<fig id="fig42" position="float" fig-type="figure"><label>Figure 42</label><caption><p>Selected statistics related to reservoir operations describing <italic>A</italic>, total reservoir releases; <italic>B</italic>, mean annual reservoir storage; <italic>C</italic>, simulated days per year where specified streamflow values are met to support phases of steelhead (<italic>Oncorhynchus mykiss</italic>) life cycle; and <italic>D</italic>, total annual number of days the Salinas River Diversion Facility (SRDF) is active for the Salinas Valley Operational Model in Monterey and San Luis Obispo Counties of California. For each box plot, the shaded box represents the interquartile range, where 50 percent of the data occurs within the range. The lower portion of the shaded box represents the 25th&#x2013;50th percentile range, and the upper portion represents the 50th&#x2013;75th percentile range. The whiskers show the range that is within 1.5 times the interquartile range. All the data points are plotted on each box plot. Any data points outside of the whisker range are statistical outliers (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>).</p><p content-type="toc"><bold>42.</bold>	Box plots showing selected statistics related to reservoir operations describing total reservoir releases, mean annual reservoir storage, simulated days per year where specified streamflow values are met to support phases of steelhead life cycle, and total annual number of days the Salinas River Diversion Facility is active for the Salinas Valley Operational Model in Monterey and San Luis Obispo Counties of California</p></caption><long-desc>42. With similar reservoir releases for the two lakes, flow requirements for steelhead fish passage are also similar for each life cycle stage.</long-desc><graphic xlink:href="sac23-0784_fig42"/></fig>
</sec>
</sec>
</sec>
<sec id="sac23-0784_Final_20260508_kc.ModelUncertaintyLimitationsandPotentialImpr">
<title>Model Uncertainty, Limitations, and Potential Improvements</title>
<p>The integrated hydrologic models (SVIHM and SVOM) have been developed in cooperation with staff from the Monterey County Water Resources Agency and Salinas Valley Groundwater Sustainability Agency. Although the historical model was calibrated to available observations, model uncertainty exists because of the inherent uncertainty in some model properties; selected observations and inputs were not available to further constrain or delineate landscape processes. There is additional uncertainty due to the necessary simplifications and assumptions needed to represent a complex hydrologic system within a numerical model, which is especially true for the simulation of complex systems that have constraints on the movement and availability of water resources that are not governed by the physics of hydrological processes. The effect of potential uncertainties and errors in furnished data on model inputs or outputs was not directly evaluated in this study. Therefore, model results represent the best available data at the time of publishing.</p>
<sec>
<title>Data Uncertainty and Limitations</title>
<p>Model development benefited from the guidance of a Technical Advisory Committee representing agricultural stakeholders, Monterey County, the Monterey County Agricultural Commission, regional water utilities, and the National Oceanic and Atmospheric Administration National Marine Fisheries Service. Although considerable conceptual information was provided through the Technical Advisory Committee and our cooperators, there are limitations in the spatial and temporal distribution of necessary data for a regional model and measurement error and uncertainty. Model inputs are based on spatially and temporally distributed data for climate; surface-water flows, diversions, and recycled water; groundwater wells and levels; groundwater pumping; surface and subsurface hydraulic properties; and reservoir characteristics and operations. Specific details on the uncertainty of agricultural demands, the most substantial water budget category in the integrated hydrologic models, is presented in the next section, &#x201C;<xref ref-type="sec" rid="sac23-0784_Final_20260508_kc.FarmProcessSuitabilityandLimitations">Farm Process Suitability and Limitations</xref>.&#x201D;</p>
<p>Climate data were developed using all available climate stations in the Remote Automatic Weather Stations (RAWS; <xref ref-type="bibr" rid="r37">Desert Research Institute, 2020</xref>), COOP (<xref ref-type="bibr" rid="r132">National Oceanic and Atmospheric Administration, 2020</xref>), and CIMIS (<xref ref-type="bibr" rid="r30">California Irrigation Management Information System, 2020</xref>) networks. These data were supplemented with spatially distributed Parameter-elevation Relationships on Independent Slopes Model (<xref ref-type="bibr" rid="r35">Daly and others, 2008</xref>; <xref ref-type="bibr" rid="r139">PRISM Climate Group, 2020</xref>) data to generate monthly maps for precipitation and PET (<xref ref-type="bibr" rid="r89">Henson and others, 2022c</xref>; <xref ref-type="bibr" rid="r98">Hevesi and others, 2022</xref>). The discrete station data are interpolated to create a spatially distributed model input, a process which has associated uncertainty.</p>
<p>Surface-water flows include streamflows, reported reservoir releases, surface-water diversions, and recycled water. Daily streamflows were obtained from gages in the National Water Information System (<xref ref-type="bibr" rid="r168">U.S. Geological Survey, 2023</xref>) and aggregated to monthly mean values. Streamflows have uncertainty due to the measurement error of each observation associated with each gage and errors due to temporal averaging of daily streamflows to monthly values. Measurement error of each streamflow observation is classified into four groups ranging from 2-percent error to greater than 8-percent error. Reservoir releases, surface-water diversions, and recycled water deliveries were furnished by MCWRA (<xref ref-type="bibr" rid="r85">Henson and others, 2022a</xref>, <xref ref-type="bibr" rid="r87">2023</xref>) and assigned to the model.</p>
<p>An additional component of model uncertainty arises because of how well model-input values and features represent the actual hydrologic system. The accuracy of the calibrated model also is contingent on the accuracy of the specified inflows and of specified observed flows and groundwater levels used for model comparison. For example, observed surface-water flows may only be accurate to within 5&#x2013;20 percent. The accuracy of the integrated hydrologic models could benefit from additional observations of streamflow from other major ungaged drainages, especially if more constraints are needed to improve the overall hydrologic budget and estimates of local recharge and runoff.</p>
<p>Groundwater levels are measured in wells throughout the MCWRA well network, which includes both observation wells (non-pumping) and agricultural and M &amp; I supply wells (pumping wells). The properties of many wells, such as screened intervals and associated aquifers, had to be estimated in many cases. <xref ref-type="bibr" rid="r87">Henson and others (2023)</xref> provide a summary of the assumptions and development of wells simulated in the integrated hydrologic models. Groundwater levels used in this study were furnished by MCWRA and are included in the model archive (<xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). Groundwater level measurements are obtained from quarterly to annually depending on the well; therefore, groundwater levels between measurements are unknown. Groundwater level measurement procedures are not currently implemented to ensure that measurements are taken after well recovery from pumping in current and nearby wells, so measured groundwater levels in many wells are affected by pumping.</p>
<p>Groundwater pumpage data were classified by water use as M &amp; I or agricultural supply. There is some unreported domestic and agricultural pumping in the model domain because the reporting ordinances only apply to a portion of the Zone 2C Water Management Area within the integrated hydrologic model domain. Before directly reported data were available in November 1994, M &amp; I water demands were estimated using U.S. Census data, and agricultural supply was simulated and compared to long-term estimated values. After November 1994, monthly M &amp; I pumpage has been reported to MCWRA by municipalities, and monthly agricultural pumpage has been reported on a voluntary basis within much of the Zone 2C Water Management Area. Interpretation of groundwater and surface-water budgets before and after 1994 for the historical model should be considered with these data limitations.</p>
<p>Surface and subsurface hydraulic properties were developed for the integrated hydrologic models. These data include defining the surface-water drainage network topology and channel properties (<xref ref-type="bibr" rid="r88">Henson and others, 2022b</xref>), many of which are unknown and require estimation. Subsurface hydraulic properties were estimated based on prior published data and models and updated using parameter estimation (<xref ref-type="bibr" rid="r90">Henson and others, 2025a</xref>). Although properties were constrained by data where available, there is uncertainty in model properties that should be explored in future model development. For the parts of hydrogeologic units that represent areas of the aquifers that are unconfined, aquifer storage properties were developed to simulate the aquifers as confined. Although this approach has been widely used in complex regional models (<xref ref-type="bibr" rid="r76">Hanson and others 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>), the confined assumption results in the saturated thickness being held constant during declining or rising groundwater levels. This simplifying assumption allows for more reasonable model run times but warrants consideration for sustainability analyses that examine drawdowns in the upper aquifer.</p>
<p>Reservoir characteristics, such as storage, area, capacity, and operation rules, for the reservoirs in the operational model are defined (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r85">Henson and others, 2022a</xref>). However, the reservoirs are simulated as separate entities with their own mass balance and the only connection to the integrated hydrologic models is through reservoir releases to stream channels. Seepage through the bottom of the reservoir is not directly simulated. Reservoir operations are simulated using predefined rules that describe operations for flood release and required fish passage. These rules represent reservoir operations under ideal conditions and are limited by simulated water available in the model.</p>
</sec>
<sec id="sac23-0784_Final_20260508_kc.FarmProcessSuitabilityandLimitations">
<title>Farm Process Suitability and Limitations</title>
<p>The Salinas Valley has extensive agriculture with limited reporting of water use and a complex water supply portfolio with multiple environmental and operational constraints. In the Salinas Valley, it is assumed that irrigated lands are considered well managed, with soil moisture being maintained by irrigation so that it is essentially in a steady state during the growing season for the 2-week time steps implemented in the model. Irrigated agriculture occurs over periods of weeks to months. Thus, the historical model (SVIHM) evaluates water demands, supplies, and flows like other typical regional scale applications of MF-OWHM, with typical weekly to monthly time periods (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>).</p>
<p>In FMP, there is no explicit representation of soil moisture storage, and runoff and recharge are specified as fractions of excess precipitation and excess irrigation greater that actual irrigation evapotranspiration by crop type (<xref ref-type="bibr" rid="r143">Schmid and others, 2006</xref>; <xref ref-type="bibr" rid="r142">Schmid and Hanson, 2009</xref>; <xref ref-type="bibr" rid="r9">Boyce and others, 2020</xref>). For weekly to monthly time steps, the simplifying assumptions that near-surface soil moisture is well-managed and steady are reasonable. Moreover, the approximation that runoff and recharge can be considered as fractions of excess water after consumption at these time scales is reasonable because the model is evaluating the longer term monthly to seasonal responses, not individual events. Uncertainty analyses that focus on these fractions could clarify the validity of these assumptions. The estimation of runoff and runoff routing using more physically based methods that consider soil moisture and topology could improve the timing of streamflow response in the model.</p>
<p>The integrated hydrologic models are regional in scale with water supplies and demands aggregated to WBS. Although this is helpful because field-scale data are not available, simplifications must be made to facilitate the regional-scale analyses. The crop areas, crop rotations, and land management and irrigation practices of individual agricultural producers are not represented. Water demand calculations in the integrated hydrologic models rely on defining the aerial extent and properties of land uses, landscape consumptive use estimates for each land use, and other factors to estimate the additional water required to account for the efficiency of water management, estimated irrigation methods, and local conditions under variable climate conditions (wet or dry).</p>
<p>Land use data were estimated using a composite of multiple available land use datasets supplemented by information from the California Pesticide Use Reporting database (<xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation, 2018</xref>). Although new methods were developed in this study for semi-annual land-use input data, the data were only a regionally developed estimate. Growing periods and land use are estimated using the best available data. However, spatially discrete and temporally dense measurements of crop harvesting are limited to the data incorporated from <xref ref-type="bibr" rid="r18">California Department of Pesticide Regulation (2018)</xref>. In this study, the cropping patterns and changes were supplemented by Monterey County Agricultural Commissioner agricultural reports (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>) that are only provided at the county scale. These data gaps contribute to potential inaccuracy and uncertainty of growing periods and estimates of actual evapotranspiration that are used to simulate landscape consumptive use.</p>
<p>In addition to land use, simulation of landscape consumptive use requires data to characterize agricultural practices that are highly dynamic and changing. Data are not available to describe complex agricultural management practices at a monthly time scale for each approximately 6-acre grid cell, so there is some model error that would take substantial effort and outreach to quantify. Landscape consumptive use estimates represent the amount of water a land use requires under perfect conditions and depend on land use properties that are initially estimated based on published values and other regional studies with similarly constructed integrated hydrologic models (<xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>).</p>
<p>The water demand is the landscape consumptive use divided by the overall efficiency. The overall efficiency represents the additional water required to account for the efficiency of water management, estimated irrigation methods and sources, and local conditions under variable climate conditions (wet or dry). The efficiency of water management in each WBS (that is, OFE) was a factor applied to crop water demands to represent efficiencies that are affected by local conditions and irrigation type and includes the effects of seasonal activities and irrigation types on efficiency. Seasonal agricultural field preparation activities are not directly represented in the crop growth model and had to be included in overall WBS efficiency calculations. Regional data for irrigation methods and irrigation sources (such as farm storage ponds) were limited. Therefore, assumptions were made using available data from available literature (<xref ref-type="bibr" rid="r141">Sandoval&#x2010;Solis and others, 2013</xref>; <xref ref-type="bibr" rid="r155">Tindula and others, 2013</xref>) and models of comparable agricultural basins in this region (for example, <xref ref-type="bibr" rid="r76">Hanson and others, 2004</xref>, <xref ref-type="bibr" rid="r75">2014b</xref>, <xref ref-type="bibr" rid="r77">c</xref>, <xref ref-type="bibr" rid="r78">d</xref>; <xref ref-type="bibr" rid="r48">Faunt and others, 2009b</xref>, <xref ref-type="bibr" rid="r51">2024</xref>). In addition, landscape consumptive use and agricultural practices respond to climate stress (wet or dry conditions). Thus, to account for climate stress, Kc climate scale factors were used to try to match annual pumpage, and some of the initial land use parameter values were adjusted during parameter estimation. The integrated hydrologic models would benefit from refinements of these efficiency input data.</p>
<p>In sum, FMP provides a reasonable and defensible estimate of water demands, landscape water fluxes, and operations. Despite the limitations, voluntary reported agricultural pumping estimates provided valuable observations for simulating total delivery requirements for each WBS. These agricultural pumping estimates were consistent with the simulated water demands estimated using land use and climate.</p>
</sec>
<sec>
<title>Hydrologic Model Limitations</title>
<p>As with any model, the integrated hydrologic models are a simplification of the real flow system and, as such, have some inherent limitations. The accuracy of simulation results is related strongly to the quality and resolution (both spatial and temporal) of input data and of measurements of the system (such as precipitation, groundwater levels, streamflow, and pumpage) used to drive and constrain the simulation and related calibration. The inflows and outflows in the integrated hydrologic models were a combination of measured values, simulated flows from adjustments to parameters to represent conceptualizations of the system, estimated inflows provided by the watershed model, and values specified using MF-OWHM. Differences between simulated and actual hydrologic conditions arise from several sources and are collectively known as model error and model uncertainty. Whereas the historical model was designed with the capability to be accurate at the WBS and subregion scales, the conceptual and numerical models were developed based on assumptions and simplifications that may restrict the use of the historical model to regional and subregional levels of spatial analysis within seasonal to interannual temporal scales.</p>
<p>The historical model (SVIHM) was designed to evaluate annual to decadal patterns in regional water availability. Processes that vary at a spatial scale smaller than grid spacing (approximately 6 acres, with variably thick layers) and a temporal scale smaller than the stress periods (1 month) cannot be explicitly represented with the historical model. Model discretization in space and time can be a potential source of error and uncertainty. Models represent a hydrologic system as a series of discrete spatial units through which intrinsic properties and flows are assumed to be uniform. The use of a discretized model to represent a hydrologic system introduces limitations for features that occur at scales smaller than the current discretization. Transient models are further discretized into a series of discrete units of time, during which specified hydrologic inflows and outflows are held constant. The use of monthly stress periods and two biweekly time steps per month in the historical model assumes that the variations of inflows and outflows and changes in groundwater levels are piecewise linear changes. Changes at smaller time scales are not simulated and are not discernable in historical model results, which may contribute to some additional temporal uncertainty. For example, the distribution of daily precipitation and soil moisture within each monthly period used by the historical model can result in large variations in simulated recharge and runoff. For example, precipitation occurring as a large 1-day storm rather than as a series of smaller storms cannot be accounted for with the existing model. The temporal scale used in the historical model was expressly designed to separate the supply and demand components of water use and movement for agriculture within the model domain.</p>
<p>Model parameter estimation and history matching of observations from the historical model constrain the differences between the real-world and simulated volumetric flows. Thus, the degree to which a simulated condition provides a reasonable representation of the hydrologic system can be evaluated by comparing simulated hydrologic conditions with those observed and measured in the field, which, in turn, provides a volume-constrained calibration. Thus, the performance and accuracy of the integrated hydrologic models are constrained primarily by groundwater levels and surface-water flows, differences in surface-water flows (gains and losses), and to a lesser degree, by estimates in annual agricultural pumpage and vertical groundwater-level differences. For example, small sources of error and uncertainty in the integrated hydrologic models could result from not simulating delayed recharge that is potentially associated with unconfined conditions outside of the model domain, not representing selected faults as potential conduits for vertical flow, or not including layer-specific skin factors for multiple-aquifer wells that could further accentuate the vertical distribution of groundwater pumpage.</p>
<p>Differences between simulated and observed hydrologic features also arise from the numerical solution that attempts to provide a cell-by-cell mass balance of inflows and outflows. Mass-balance errors are minimized by ensuring the model solution reaches a reasonable state of mass balance within each biweekly period. The twice-per-month time steps were used to remain consistent with the assumptions of the current version of the FMP process. The cumulative mass balance of the historical model was less than 1 percent of the total flow over the 51 years of historical simulation (October 1967&#x2013;September 2018). It is also important to note that groundwater budget components vary substantially in scale. For example, the average agricultural supply pumpage is 454 TAFY, and the average seawater coastal inflow is 12 TAFY, which is approximately 3 percent of the average groundwater pumpage. Estimating seawater coastal inflow is important for sustainability assessments; however, uncertainty in groundwater pumpage may be greater than the estimated seawater coastal inflow, which underscores the importance of accurate groundwater pumpage estimates, specifically in the coastal region.</p>
<p>The operational model (SVOM) is a hypothetical baseline model used to evaluate water supply project alternatives and alternate reservoir operational rules by MCWRA. The intent of the operational model is not to directly represent historical conditions; the reservoirs and land use were not always as they were in 2014. The reservoir releases and storage are compared to the historical data for the purpose of evaluating if they are reasonable. There may be differences in groundwater levels, groundwater storage, and surface-water flows among the two integrated hydrologic models. The purpose of the operational model is to quantify potential benefits of water supply projects within a framework that considers historical climate and benefits from representation of the system using as much of the calibrated historical model input as feasible. Despite the differences among the purpose and implementation of the integrated hydrologic models, the operational model reasonably reproduces the historical conditions for which it was developed&#x2014;reservoir operations and reservoir-provided flows to downgradient diversions at the SRDF (to offset groundwater pumpage in the coastal region).</p>
<p>Despite these potential limitations, the integrated hydrologic models are sufficient for the intended purposes of simulating surface-water and groundwater interactions on annual to decadal scales at the subregional scale. Hydrologic budget analysis is needed for planning and evaluating alternatives for managing conjunctive use within the analysis regions evaluated in this study. Future efforts for sustainable water resource development may need detailed information about stream-aquifer interactions for planning.</p>
</sec>
<sec>
<title>Potential Improvements</title>
<p>The accuracy of the integrated hydrologic models could be improved if the input values of selected hydraulic properties, such as horizontal and vertical hydraulic conductivities and storages, could be adjusted based on additional field estimates. For example, aquifer tests combined with wellbore flow and temperature logs could be used to better assess the effects of multiple-aquifer wells on the vertical distribution of pumpage over multiple aquifers. Additional estimates of horizontal hydraulic conductivity to further constrain integrated hydrologic model properties could be obtained from aquifer tests combined with wellbore flow logs at selected supply-well sites or well specific-capacity tests at single-aquifer supply wells. In addition, there is uncertainty in the facies distributions that are based on borehole lithology, which are sparser with increasing depth. The facies subregions may need to be further subdivided using additional zones within facies and texture data estimated from lithologic data and drillers logs.</p>
<p>Potential future refinements and enhancements can continue to improve the level of resolution and model accuracy and reduce potential uncertainties. In general, proper design and parameter estimation of flow models is an ongoing process that, along with better spatial and temporal estimates of inflows, outflows, climate, and land use, can minimize some of the inherent model limitations. Limitations of the modeling software, assumptions made during model development, and results of model parameter estimation and sensitivity analysis are all factors that may further constrain the appropriate use of this model. In turn, these limitations can be used to identify where potential future improvements in the simulation of specific processes are needed or where new data are needed to improve the quality of the simulation.</p>
<p>Several of the processes within the integrated hydrologic models potentially could allow for refined simulation of selected flow features. Improved simulation of multiple-aquifer wells to account for partial penetration and better estimates of actual pumping capacities of all wells could increase the accuracy of simulated pumpage. Some WBSs required assumptions about well construction, so the location of wells or water conveyances that are used to service these properties would require additional investigation.</p>
<p>Future work could include data refinement and temporal updates of the integrated hydrologic models, additional calibration with additional model observations, and development of projections of alternative scenarios based on a new comprehensive basin management plan with use of the Surface-Water Operations Process in the operational model (<xref ref-type="bibr" rid="r53">Ferguson and Llewellyn, 2015</xref>; <xref ref-type="bibr" rid="r54">Ferguson and others, 2016</xref>). An expanded monitoring network would allow a better understanding of changes in surface-water flows, diversions, streamflow, and streamflow infiltration (seepage runs), which are the main sources of recharge in the valley. In particular, the monitoring of crop-specific annual land use, canal and diversion inflows, monthly well-by-well groundwater pumpage, and wellbore flow throughout the valley would help to better quantify the state of resources and provide valuable comparison to model performance.</p>
<p>The history matching of the historical model, based predominantly on groundwater levels and streamflows, could be supplemented with parcel-based observations of land use from remote-sensing estimates of evapotranspiration, which could improve model accuracy and embed more variability in the demand. Projections of water availability and sustainability of supply could include the analysis of alternative scenarios of land use, crops, irrigation practices, and additional capture of intermittent runoff from wet years (once climate and runoff are added to the model) for managed aquifer recharge or supplemental irrigation scenarios.</p>
<p>The integrated hydrologic models (SVIHM and SVOM) were developed using a &#x201C;self-updating model structure,&#x201D; where model data can be updated using spreadsheet software and processing scripts. Thus, the integrated hydrologic models are updated readily and can be refined periodically, including parameter and framework adjustments as needed to keep the historical and operational models available for operational and future analysis. This structure facilitates any upgrades, updates, and additional parameter estimation that may be needed to address marginal changes in the important components of the water budget relevant to the operation of the SVWP and reservoir management. It also assists in sustaining the groundwater resources without interfering with project deliveries and honoring related fish passage criteria for threatened steelhead.</p>
<p>During model development, potential improvements were identified that could be explored in future hydrologic models and data collection efforts.</p><list id="L1" list-type="order"><list-item><label>1.</label>
<p>Simulation of aquifer depletion and interactions among aquifers would be greatly improved with better resolution of well depths, pumping capacities, and screened intervals. These data were commonly unavailable and had to be estimated.</p></list-item><list-item><label>2.</label>
<p>Representation of groundwater storage and levels would benefit from improved information about spatial and vertical aquifer transmissivity with facies or texture-based distributions of hydraulic properties.</p></list-item><list-item><label>3.</label>
<p>Future evaluations of stream habitat and surface-water flows would benefit from reduced overestimation bias in simulation of low flows and improved representation of the surface-water drainage network, including irrigation canals.</p></list-item><list-item><label>4.</label>
<p>Understanding of groundwater and surface-water interactions gained from the model could be improved by evaluating the effects of near-river shallow well networks connected to the Salinas River and storage ponds in the Upper Valley analysis region. Such networks are observed in aerial imagery but are not currently represented in the models or input data.</p></list-item><list-item><label>5.</label>
<p>Estimation of agricultural demands could be enhanced using directly measured pumping data and validated field-scale land use mapping.</p></list-item><list-item><label>6.</label>
<p>Simulation of the groundwater system could be improved with (1) additional monitoring wells in the below dam and Upper Valley regions to better characterize hydraulic gradients and groundwater use, (2) additional monitoring wells along the slopes of the Salinas Valley to provide information about lateral hydraulic gradients, and (3) additional paired monitoring wells of the shallow and deep aquifers near the coast to improve the characterization of the coastal aquifers to mitigate seawater intrusion.</p></list-item><list-item><label>7.</label>
<p>Overall basin groundwater and surface-water budgets could be refined by improving data collection and extending the model analysis into areas outside the Zone 2C Water Management Area. National-scale mapping of irrigated lands has shown that there may be substantial agricultural development outside of the Zone 2C Water Management Area (<xref ref-type="fig" rid="fig06">fig. 6<italic>D</italic></xref>), where reporting of groundwater water use is not required. Agricultural pumpage was only simulated in the subareas within the Zone 2C Water Management Area where reporting of groundwater water use is required, and wells have been defined.</p></list-item><list-item><label>8.</label>
<p>Future model development could explore the effect of simulating completely unconfined conditions to understand the effect of this simplifying assumption on surface and groundwater budgets.</p></list-item><list-item><label>9.</label>
<p>The integrated hydrologic models would benefit from comparative evaluations with higher resolution models that have been developed to evaluate aquifer storage and recovery projects in the coastal area and integration of new information gathered as part of other model development in the region.</p></list-item><list-item><label>10.</label>
<p>Estimation of uncertainty for important model predictions, such as streamflow requirements, minimum water level thresholds, and seawater coastal inflow estimates, may help quantify the risk of management decisions more accurately.</p></list-item></list>
</sec>
</sec>
<sec>
<title>Summary and Conclusions</title>
<p>To evaluate the challenging water management issues in the Salinas Valley, the U.S. Geological Survey (USGS), Monterey County Water Resource Agency (MCWRA), and the Salinas Valley Basin Groundwater Sustainability Agency cooperatively developed a comprehensive suite of models that represent the Salinas Valley hydrogeologic system. The Salinas Valley surrounds the Salinas Valley groundwater basin in Monterey and San Luis Obispo Counties, California (<xref ref-type="fig" rid="fig01">fig. 1</xref>). The Salinas Valley study area covers about 4,200 square miles and is subdivided into five analysis regions&#x2014;the Riparian, Pressure, East Side-Langley, Forebay, and Upper Valley analysis regions (<xref ref-type="fig" rid="fig15">fig. 15</xref>). The Riparian analysis region represents the area surrounding the Salinas River. The Pressure, East Side-Langley, Forebay, and Upper Valley analysis regions correspond to Salinas Valley groundwater subbasins defined by the California Department of Water Resources (<xref ref-type="bibr" rid="r27">California Department of Water Resources, 2020</xref>). These groundwater subbasins are used to manage groundwater sustainability by groundwater sustainability agencies and water agencies within the Salinas Valley study area (<xref ref-type="fig" rid="fig11">fig. 11</xref>).</p>
<p>Agriculture has been a vital part of the local economy for more than a century (<xref ref-type="bibr" rid="r115">Manning, 1963</xref>). Increased agricultural development, which includes a shift toward more water-intensive crops (<xref ref-type="bibr" rid="r117">Monterey County Agricultural Commission, 2022</xref>), changes in population (<xref ref-type="bibr" rid="r157">U.S. Census Bureau, 2018</xref>), and climate variability, has increased demand on limited water resources. Sources of surface water to meet water demands include the Salinas River and its tributaries and two reservoirs (<xref ref-type="fig" rid="fig01">fig. 1</xref>). Surface water in the Salinas Valley study area is managed to meet agricultural diversions at Clark Colony and the Salinas River Diversion Facility (<xref ref-type="fig" rid="fig01">fig. 1</xref>) and to meet minimum environmental flows to support habitat for federally listed threatened steelhead (<italic>Oncorhynchus mykiss</italic>). A vast network of thousands of publicly and privately owned wells (<xref ref-type="fig" rid="fig24">figs. 24<italic>A</italic></xref>, <xref ref-type="fig" rid="fig24">24<italic>B</italic></xref>) is used to meet groundwater demands. Groundwater is used to meet agricultural, municipal, and industrial water demands and when surface-water supplies are limited or not suitable for the intended water use.</p>
<p>Substantial water management challenges have been documented. Valley-wide groundwater storage declines have been documented for almost 80 years (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>), as shown by persistent groundwater level declines, associated reductions in long-term groundwater storage observed in the Pressure and East Side-Langley analysis regions, and seawater intrusion into the 180-Foot Aquifer and 400-Foot Aquifer hydrogeologic units along the coast, resulting in water quality degradation. Additionally, widespread nitrate contamination throughout the Salinas Valley has occurred (<xref ref-type="bibr" rid="r83">Harter and others, 2012</xref>), further limiting the available groundwater supply. Although water quality is an important management concern, it was not evaluated specifically in this study.</p>
<p>Managing water resources to address local shortages from spatial and temporal variability in water availability is challenging (<xref ref-type="bibr" rid="r19">California Department of Public Works, 1946</xref>; <xref ref-type="bibr" rid="r113">Leedshill-Herkenhoff, Inc., 1985</xref>; <xref ref-type="bibr" rid="r118">Monterey County Water Resources Agency, 1995</xref>). Locations where water resources are needed are commonly long distances (as far as 100 miles in some cases) from where reservoir releases or substantial recharge occur. The variation among locations of areas with substantial withdrawals and recharge require conjunctive use of groundwater and surface water to meet water demands. Surface-water availability varies seasonally and year to year. Some sections of the Salinas River are intermittently dry, and surface water must be conveyed to meet water demands downstream. Variability in surface-water magnitude and challenges related to conveyance of surface water throughout the valley lead to substantial and primary use of groundwater to meet many water demands.</p>
<p>The Salinas River is a substantial contributor to groundwater recharge. Additional substantial sources of recharge occur from infiltration in areas with native vegetation and agricultural areas. Surface water travels from the Upper Valley analysis region along the Salinas River to the coastal areas and infiltrates into unconfined aquifers, resulting in substantial reductions in streamflow as it moves through the valley to the ocean. This flow reduction through recharge along the Salinas River is a constraint for delivery of surface water to coastal areas to offset groundwater pumpage and for managing required minimum environmental flows. Nonetheless, this groundwater recharge from the Salinas River also supports regional groundwater availability. This vital connection between infiltration of managed and natural surface-water flows as well as the importance of riparian underflow in every analysis region and the need for concurrent delivery of surface water to the coastal regions to reduce coastal seawater intrusion underscores the importance of integrated valley-wide water management.</p>
<p>The evaluation of the Salinas Valley hydrologic system involves an integrated approach that combines surface and subsurface analysis to simulate both natural and managed water flows. This evaluation was achieved through the development of a comprehensive Salinas Valley System Model, which incorporates various submodels and data related to geology, surface-water, groundwater, and operational factors. All submodels of the Salinas Valley System Model and associated data can be accessed at <ext-link ext-link-type="uri" xlink:href="https://www.sciencebase.gov/catalog/item/640770fed34e76f5f75e388b">https://www.sciencebase.gov/catalog/item/640770fed34e76f5f75e388b</ext-link>. The overarching goal of the Salinas Valley System Model is to produce a model that includes (1) a geologic framework and texture model (the Salinas Valley Geologic Framework; <xref ref-type="bibr" rid="r151">Sweetkind, 2023</xref>) to define aquifers as hydrogeologic units; (2) a model and analysis of watershed processes (Salinas Valley Watershed Model; <xref ref-type="bibr" rid="r96">Hevesi and others, 2025a</xref>); (3) a historical model (Salinas Valley Integrated Hydrologic Model; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>) and analyses of historical surface and groundwater availability; and (4) an operational model that simulates multi-objective reservoir operations using established operational rules or is configured to evaluate alternative rules (Salinas Valley Operational Model; <xref ref-type="bibr" rid="r86">Henson and Culling, 2025</xref>). The Salinas Valley System Model was developed with input and expertise from stakeholders; agriculture, surface-water, groundwater, geological, reservoir management specialists; and coordination with Federal, State, and local agencies. The Salinas Valley System Model provides a comprehensive suite of tools for analysis of water resources and evaluation of reservoir operations and water use sustainability projects.</p>
<p>This report documents and focuses on parts three and four listed above, the development of a historical surface-water and groundwater availability model integrated with an operations model. The simulation of historical conditions is accurate at scales relevant to water-supply analysis for the evaluation of water availability and sustainability, and interactions between groundwater and surface-water use in analysis regions of the Salinas Valley are evaluated. Several companion reports and data releases provide information on the input data, model representation of important processes, and connections between hydrologic models.</p>
<p>The integrated hydrologic models were designed to reproduce the natural and human components of the hydrologic system, including components dependent on variations in climate, permitting an accurate assessment of surface-water and groundwater conditions and processes that can inform water users and help to improve planning for future conditions. Model development included (1) a conceptual model of the flow system and the geologic framework, (2) a surface-water model that provided inflows from ungaged basins that are connected to but outside of the integrated hydrologic model domain, and (3) construction of integrated hydrologic flow models with the MODFLOW-One-Water Hydrologic Flow Model. The integrated hydrologic models have a uniform grid with a spatial resolution of approximately 6 acres. The historical model, the Salinas Valley Integrated Hydrologic Model, simulates historical conditions with monthly stress periods and semi-monthly time steps. The historical model was calibrated to match observations of streamflow, groundwater levels, and groundwater pumpage and was then used to assess the use and movement of water throughout the Salinas Valley.</p>
<p>The operational model provides a comprehensive representation of the current reservoir operations for Lake San Antonio and Lake Nacimiento. The operational model can support evaluations and scenario-testing to support habitat conservation, strategies to increase surface-water supply, and groundwater sustainability plans. The operational model is like the historical model but has a few differences: time steps are 5&#x2013;6 days instead of semi-monthly, land use is assumed to be equal to 2014 for the simulation, all current diversions and water supply projects are implemented (Salinas Valley Water Project, including the Salinas River Diversion Facility and the Castroville Seawater Intrusion Project), and reservoir releases are computed using operational rules instead of manually specified as they are in the historical model. The operational model uses historical information to simulate the Salinas Valley hydrologic system. Reservoir operations have changed substantially in the past 50 years. The Castroville Seawater Intrusion Project has been in operation since July 1998, and the Salinas River Diversion Facility project has been in operation since April 2010. In the operational model, these projects are implemented from the start of the simulation. Thus, the operational model is a hypothetical baseline model used to evaluate water supply project alternatives and alternate reservoir operational rules by the Monterey County Water Resources Agency (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r85">Henson and others, 2022a</xref>). Although the intent of the operational model is not to directly represent historical conditions, there is reasonable visual correspondence in the annual time series, which shows similar wet and dry period responses among average monthly storage (<xref ref-type="fig" rid="fig41">fig. 41<italic>A</italic></xref>), average annual storage (<xref ref-type="fig" rid="fig41">fig. 41<italic>B</italic></xref>), and average annual releases (<xref ref-type="fig" rid="fig41">fig. 41<italic>C</italic></xref>) among the Salinas Valley Operational Model and historical records.</p>
<p>The historical model, the Salinas Valley Integrated Hydrologic Model, reasonably represents historical conditions for surface water, agricultural water demands, and groundwater levels. The Salinas Valley Integrated Hydrologic Model also provides insights into groundwater budget components, such as recharge, pumping, the recharge to pumping ratio, and storage. Through model parameter estimation, the components of the historical model were calibrated to match historical observations, where available, using trial and error and computer-assisted techniques. The observation dataset used to evaluate history matching includes more than 104,000 annual, quarterly, and monthly observations and reported data for streamflows, streamflow differences between streamgages, groundwater levels, groundwater drawdowns, groundwater contours, reported groundwater pumpage, and diversions for the period from October 1, 1967, to December 31, 2014.</p>
<sec>
<title>Surface-Water Summary</title>
<p>The calibrated historical model reasonably reproduces monthly average surface-water flow observations. Comparison among streamgage data and simulated streamflows shows reasonable correspondence across the observed variability in mean monthly flows throughout the Salinas River that range from 0 to 18,750 cubic feet per second (ft<sup>3</sup>/s). Simulated flows reproduce historical flows in six gages along the Salinas River and its major tributary Arroyo Seco, with a minimum Nash-Sutcliffe model efficiency of 0.87 and maximum mean residual of 83 ft<sup>3</sup>/s. However, low flows at gages in the Forebay and Pressure analysis regions (USGS 11152300 and USGS 11152500; <xref ref-type="fig" rid="fig20">fig. 20</xref>) were overestimated by the historical model, which is evident in the overprediction of flows (negative residuals) at USGS 11152000, USGS 11151700, and USGS 11152500 (<xref ref-type="table" rid="t07">table 7</xref>).</p>
<p>Historical model results show that streamflow leakage into the groundwater system is a substantial source of recharge in all parts of the basin everywhere except for the East Side-Langley analysis region. Streamflow leakage is substantial in the Upper Valley and Forebay analysis regions, where older hydrogeologic units are present in the near surface (<xref ref-type="fig" rid="fig21">figs. 21</xref>, <xref ref-type="fig" rid="fig22">22</xref>). The East Side-Langley analysis region has the highest inflow of subbasin underflow (<xref ref-type="table" rid="t14">table 14</xref>) into all analysis regions (<xref ref-type="table" rid="t12">tables 12</xref>, <xref ref-type="table" rid="t13">13</xref>, <xref ref-type="table" rid="t15">15</xref>, <xref ref-type="table" rid="t16">16</xref>). The relatively substantial proportion of subbasin underflow to the East Side-Langley analysis region suggests that activities that alter storage or flow in upgradient basins will affect the East Side-Langley analysis region. The substantial portion of inflow represented by subbasin underflow and riparian underflow among analysis regions indicates substantial interconnectivity.</p>
</sec>
<sec>
<title>Agricultural Demand Summary</title>
<p>The simulation reasonably reproduces monthly agricultural pumpage that has been regionalized to multiple water balance subregions within each of the analysis regions. The mean monthly residual between reported and simulated agricultural pumpage for the history matching period is 29 acre-feet with a root mean square error (RMSE) of 775 acre-feet. The regionalization of agricultural supply and demand calculations within water balance subregions allows for a regional assessment of agricultural water use without needing to specify what each individual grower is doing on every agricultural field. Multi-year composite land use data are available at the subbasin scale but are not available to describe all cropping patterns and agricultural management practices at a monthly time scale for each approximately 6-acre grid cell; for this reason, some model error cannot be avoided. Despite the approximations, the historical model simulates within 99 percent the total cumulative volume of reported annual agricultural pumpage in Salinas Valley from November 1994 through September 2018 and has general agreement between annual reported and simulated pumpage spatially throughout the model domain (<xref ref-type="fig" rid="fig36">figs. 36<italic>A</italic>&#x2013;<italic>G</italic></xref>), with all scaled RMSE less than or equal to 9 percent for the domain and analysis regions.</p>
<p>Simulated agricultural pumpage varies from year to year with an average of approximately 481 thousand acre-feet per year (TAFY) for the period between 1970 and 1994, computed as the average of analysis periods A and B. Before when reliable pumpage data became available in November 1994, the annual agricultural pumpage was assumed to be variable but unknown. The average total pumpage for analysis periods A and B (1970&#x2013;1994; <xref ref-type="table" rid="t11">table 11</xref>), 469 TAFY and 578 TAFY, respectively, average to 524 TAFY, which is close to the previous groundwater budget tabulations of 519 TAFY for the period from 1970 to 1994 (<xref ref-type="bibr" rid="r125">Montgomery Watson, 1997</xref>). Agricultural pumpage was as much as 547 TAFY in 1997 and as low as 345 TAFY in 2011 (<xref ref-type="fig" rid="fig36">fig. 36<italic>B</italic></xref>). Municipal and industrial pumpage ranged from 38 to 67 TAFY over the four analysis subperiods, which is approximately 10 percent of agricultural pumpage (<xref ref-type="table" rid="t11">table 11</xref>).</p>
</sec>
<sec>
<title>Groundwater-Level Summary</title>
<p>The simulation reasonably reproduces observations of groundwater levels and drawdowns and reproduces groundwater level declines and reductions in groundwater storage over time. Groundwater levels show close correspondence with the 1:1 line with a few wells in the Upper Valley analysis region that were not well matched (<xref ref-type="fig" rid="fig33">fig. 33<italic>A</italic></xref>). Drawdowns throughout the basin are simulated with a mean residual less than 1 foot (ft) with RMSE of 15 ft (<xref ref-type="table" rid="t09">table 9</xref>). The mean drawdown residuals for all observation wells show most wells have drawdown residuals within 20 ft of observed values (<xref ref-type="fig" rid="fig34">fig. 34</xref>). Simulated patterns of groundwater levels generally replicate the patterns and drawdowns shown in MCWRA-estimated groundwater level contours (<xref ref-type="bibr" rid="r121">Monterey County Water Resources Agency, 2005</xref>, <xref ref-type="bibr" rid="r122">2018</xref>; <xref ref-type="bibr" rid="r87">Henson and others, 2023</xref>) for 1994, 2003, and 2011 (<xref ref-type="fig" rid="fig35">figs. 35<italic>A</italic>&#x2013;<italic>C</italic></xref>). Among all analysis regions, the absolute values of mean drawdown residuals are less than 3 ft, with maximum RMSE of 18 ft (<xref ref-type="table" rid="t09">table 9</xref>).</p>
<p>Groundwater level changes in some analysis regions (East Side-Langley, Pressure, and Forebay analysis regions) are more sensitive to dry conditions. Groundwater levels in some areas have still not recovered from the 1984&#x2013;94 dry period (East Side-Langley and Pressure analysis regions); the Upper Valley and Forebay analysis regions have had relatively more recovery of groundwater levels (<xref ref-type="fig" rid="fig13">figs. 13</xref>, <xref ref-type="fig" rid="fig33">33</xref>). Higher sensitivity of groundwater levels to dry periods in the analysis regions close to the coast (Pressure and East Side-Langley analysis regions) indicates that local recharge is insufficient to maintain groundwater levels with current groundwater use during these periods and indicates a dependence on regional recharge, especially during dry periods.</p>
</sec>
<sec>
<title>Groundwater Budget Summary</title>
<p>Groundwater budgets from the historical model provide valuable information about flows into and out of the Salinas Valley groundwater subbasins. Substantial inflows and outflows indicate major components of the budgets and include stream leakage and recharge. In all analysis regions, subbasin underflow from adjacent groundwater subbasins is a substantial inflow. In every analysis region but the East Side-Langley analysis region, groundwater flow from the riparian area of the main Salinas River channel (riparian underflow) is a substantial inflow. Important outflows in the groundwater budgets include simulated agricultural and municipal and industrial pumpage.</p>
<p>The pumpage-recharge fraction is the ratio of analysis region pumping to recharge and was evaluated for each analysis region to compare the relative magnitude of analysis region (groundwater subbasin) water use and water supply. The pumpage-recharge fraction is an indicator of analysis region dependence on riparian and subbasin underflow from adjacent analysis regions. Average pumpage-recharge fractions for the integrated hydrologic model domain are on average 0.9 but are as high as 1.2 in dry analysis period B (<xref ref-type="table" rid="t11">table 11</xref>). These fractions further support that local recharge is insufficient to maintain groundwater levels with current groundwater use under all climate conditions. Except for the Riparian analysis region, the average pumpage-recharge fractions of all analysis regions are greater than 1.6 for the simulation period. Moreover, values greater than 2 commonly occur among analysis periods even outside of dry periods (<xref ref-type="table" rid="t13">tables 13</xref>&#x2013;<xref ref-type="table" rid="t16">16</xref>). Pumpage-recharge fractions much greater than 1 indicate that a substantial portion of water demands are being met by subbasin and riparian underflow, further underscoring the substantial connectivity among groundwater subbasins. These results suggest that groundwater subbasin water supply is affected by changes in groundwater availability and use in upgradient groundwater subbasins and Salinas River streamflow; thus, groundwater sustainability efforts would be improved with regional coordination.</p>
<p>Storage change, the difference between inflows and outflows, provides insights into the drivers of regional changes in groundwater levels. Aquifer storage change varies considerably from year to year, depending on land use, pumpage, and climate conditions, ranging from an average of &#x2212;139 TAFY (out) to 158 TAFY (in) over the four analysis subperiods (<xref ref-type="table" rid="t11">table 11</xref>). Climate-driven factors can greatly affect inflows, outflows, and water use by as much as a factor of 2 between wet and dry years. Whereas inflows during inter-decadal wet years partly replenish groundwater in the basin, the long-term water use and storage depletion from pumping diminish the effects of these wetter periods and related recharge. Substantial withdrawals from storage generally were simulated not only during drier years, but also during the increase of the practice of multi-cropping throughout the simulation period. The long-term imbalance between inflows and outflows results in simulated average annual groundwater depletion of about 15 TAFY, which is made up primarily of an average of 15 TAFY of seawater coastal inflow over the 51-year period from water year 1968 to 2018.</p>
</sec>
<sec>
<title>Conclusions</title>
<p>The components of the Salinas Valley System Model, particularly the historical and operational model components documented in this report, allow for analysis of landscape, surface-water, and groundwater hydrologic budgets for water years 1970&#x2013;2018. These models support assessments of the effects of groundwater and surface-water use on surface and groundwater availability, evaluation of the reservoir operating agreements used to support management of surface flows and storage, and evaluation of new and existing water supply project performance to develop groundwater sustainability plans. Overall, the historical model provides a good representation of historical conditions and hydrologic budgets for seasonal to inter-decadal time frames and subregional to valley-wide spatial scales. The integrated hydrologic models adequately represent the movement and use of all water within the regional flow system for surface water and diversions, groundwater levels, and groundwater pumpage used to meet agricultural and municipal demands. In addition to the water management challenges in the Salinas Valley with respect to water quantity, there are water quality challenges. However, these were not addressed directly in this report. Although the water supply challenges documented in the 1940s remain, improvements in efficiency, surface-water supply and storage projects, and valley-wide sustainability coordination present opportunities to mitigate the undesirable effects of a variable climate on the integrated hydrologic system. Connectivity between analysis regions underscores the importance of using regional tools, such as the historical and operational integrated hydrologic models. Tools that encompass the Salinas Valley are essential for analyses of water availability and use under changing land use, agricultural practices, climate conditions, and reservoir operations.</p>
</sec>
</sec>
</body>
</book-part>
</book-body>
<book-back>
<ref-list><title>References Cited</title>
<ref id="r1"><mixed-citation publication-type="book">Allen, R.G., Pereira, L.S., Raes, D., and Smith, M., 1998, Crop evapotranspiration&#x2014;Guidelines for computing crop water requirements: Food and Agriculture Organization of the United Nations Irrigation and Drainage Paper 56, 300 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.fao.org/4/x0490e/x0490e00.htm">https://www.fao.org/4/x0490e/x0490e00.htm</ext-link>.]</mixed-citation></ref>
<ref id="r2"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Anderson</surname>, <given-names>M.P.</given-names></string-name>, <string-name><surname>Woessner</surname>, <given-names>W.W.</given-names></string-name>, and <string-name><surname>Hunt</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>1992</year>, <source>Applied groundwater modeling&#x2014;Simulation of flow and advective transport</source> (<edition>2d&#x00A0;ed.</edition>): <publisher-loc>New York</publisher-loc>, <publisher-name>Academic Press</publisher-name>, <size units="page">564</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r3"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Arcement</surname>, <given-names>G.J.</given-names></string-name></person-group>, Jr., and <person-group person-group-type="author"><string-name><surname>Schneider</surname>, <given-names>V.R.</given-names></string-name></person-group>, <year>1989</year>, <source>Guide for selecting Manning&#x2019;s roughness coefficients for natural channels and flood plains</source>: <series>U.S. Geological Survey Water Supply Paper</series> <volume>2339</volume>, <size units="page">38</size>&#x00A0;p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/wsp2339</pub-id>.]</mixed-citation></ref>
<ref id="r4"><mixed-citation publication-type="web">Baillie, M., Chau, L., and Turner, J. [prepared for the Monterey County Resource Management Agency], 2015, State of the Salinas River groundwater basin: Walnut Creek, Calif., Brown and Caldwell, 241 p., accessed December 30, 2017, at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/cgi/viewcontent.cgi?article=1020%26context=hornbeck_cgb_6_a">https://digitalcommons.csumb.edu/cgi/viewcontent.cgi?article=1020&amp;context=hornbeck_cgb_6_a</ext-link>.</mixed-citation></ref>
<ref id="r5"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Banta</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2000</year>, <article-title>MODFLOW-2000, the U.S. Geological Survey modular ground-water model&#x2014;Documentation of packages for simulating evapotranspiration with a segmented function (ETS1) and drains with return flow (DRT1)</article-title>: <series>U.S. Geological Survey Open-File Report</series> <volume>00&#x2013;466</volume>, <size units="page">127</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr00466</pub-id>.</mixed-citation></ref>
<ref id="r6"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Phillips</surname>, <given-names>S.P.</given-names></string-name>, and <string-name><surname>Gronberg</surname>, <given-names>J.M.</given-names></string-name></person-group>, <year>1993</year>, <source>Numerical simulation of ground-water flow in the central part of the western San Joaquin Valley, California</source>: <series>U.S. Geological Survey Water-Supply Paper</series> <volume>2396</volume>, <size units="page">69</size>&#x00A0;p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/wsp2396</pub-id>.] </mixed-citation></ref>
<ref id="r7"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, and <string-name><surname>Phillips</surname>, <given-names>S.P.</given-names></string-name></person-group>, <year>1995</year>, <article-title>Alternative to agricultural drains in California&#x2019;s San Joaquin Valley&#x2014;Results of a regional-scale hydrogeologic approach</article-title>: <source>Water Resources Research</source>, v. <volume>31</volume>, no. <issue>8</issue>, p. <fpage>1845</fpage>&#x2013;<lpage>1862</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1029/95WR01328</pub-id>.</mixed-citation></ref>
<ref id="r8"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Bicknell</surname>, <given-names>B.R.</given-names></string-name>, <string-name><surname>Imhoff</surname>, <given-names>J.C.</given-names></string-name>, <string-name><surname>Kittle</surname>, <given-names>J.L.</given-names>, <suffix>Jr</suffix></string-name>., <string-name><surname>Donigian</surname>, <given-names>A.S.</given-names>, <suffix>Jr</suffix></string-name>., and <string-name><surname>Johanson</surname>, <given-names>R.C.</given-names></string-name></person-group>, <year>1997</year>, <source>Hydrological simulation program&#x2014;Fortran, User&#x2019;s manual for version 11</source>: <publisher-loc>Athens, Ga.</publisher-loc>, <publisher-name>U.S. Environmental Protection Agency, National Exposure Research Laboratory</publisher-name>, <size units="page">770</size>&#x00A0;p., [Available at <ext-link ext-link-type="uri" xlink:href="https://ntrl.ntis.gov/NTRL/dashboard/searchResults/titleDetail/PB97193114.xhtml">https://ntrl.ntis.gov/NTRL/dashboard/searchResults/titleDetail/PB97193114.xhtml</ext-link>.]</mixed-citation></ref>
<ref id="r9"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Boyce</surname>, <given-names>S.E.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Ferguson</surname>, <given-names>I.</given-names></string-name>, <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Reimann</surname>, <given-names>T.</given-names></string-name>, <string-name><surname>Mehl</surname>, <given-names>S.M.</given-names></string-name>, and <string-name><surname>Earll</surname>, <given-names>M.M.</given-names></string-name></person-group>, <year>2020</year>, <article-title>One-water hydrologic flow model&#x2014;A MODFLOW based conjunctive-use simulation software</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A60</chapter-title>, <size units="page">435</size> p., accessed December 31, 2021, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6A60</pub-id>.</mixed-citation></ref>
<ref id="r10"><mixed-citation publication-type="data">Boyce, S.E., 2023, MODFLOW One-water hydrologic flow model (MF-OWHM) conjunctive use and integrated hydrologic flow modeling software, version 2.3.0: U.S. Geological Survey software release, accessed December 31, 2021, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9P8I8GS</pub-id>.</mixed-citation></ref>
<ref id="r11"><mixed-citation publication-type="other">Boyle Engineering Corporation, 1987, Salinas Valley ground water model, alternative analysis: Final report prepared for the Monterey County Flood Control and Water Conservation District.</mixed-citation></ref>
<ref id="r12"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Brandt</surname>, <given-names>J.T.</given-names></string-name>, <string-name><surname>Earll</surname>, <given-names>M.M.</given-names></string-name>, <string-name><surname>Sneed</surname>, <given-names>M.</given-names></string-name>, and <string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name></person-group>, <year>2021</year>, <article-title>Detection and measurement of land-surface deformation, Pajaro Valley, Santa Cruz and Monterey Counties, California, 2015&#x2013;18</article-title>: <series>U.S. Geological Survey Open-File Report</series> <volume>2021&#x2013;1101</volume>, <size units="page">16</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr20211101</pub-id>.</mixed-citation></ref>
<ref id="r13"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Brouwer</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Goffeau</surname>, <given-names>A.</given-names></string-name>, and <string-name><surname>Heibloem</surname>, <given-names>M.</given-names></string-name></person-group>, <year>1985</year>, <source>Irrigation water management&#x2014;Training manual no. 1&#x2014;Introduction to Irrigation</source>: <publisher-loc>Rome, Italy</publisher-loc>, <publisher-name>Food and Agriculture Organization of the United Nations, Land and Water Development Division</publisher-name>. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.fao.org/4/r4082e/r4082e00.htm">https://www.fao.org/4/r4082e/r4082e00.htm</ext-link>.] </mixed-citation></ref>
<ref id="r14"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Brouwer</surname>, <given-names>C.</given-names></string-name>, and <string-name><surname>Heibloem</surname>, <given-names>M.</given-names></string-name></person-group>, <year>1986</year>, <source>Irrigation water management&#x2014;Training manual no. 3&#x2014;Irrigation water needs</source>: <publisher-loc>Rome, Italy</publisher-loc>, <publisher-name>Food and Agriculture Organization of the United Nations, Land and Water Development Division</publisher-name>. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.fao.org/4/s2022e/s2022e00.htm">https://www.fao.org/4/s2022e/s2022e00.htm</ext-link>.] </mixed-citation></ref>
<ref id="r15"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Brush</surname>, <given-names>C.F.</given-names></string-name>, <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, and <string-name><surname>Phillips</surname>, <given-names>S.P.</given-names></string-name></person-group>, <year>2004</year>, <article-title>Estimation of a water budget for 1972&#x2013;2000 for the grasslands area, central part of the western San Joaquin Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2004&#x2013;5180</volume>, <size units="page">59</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20045180</pub-id>.</mixed-citation></ref>
<ref id="r16"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Burow</surname>, <given-names>K.R.</given-names></string-name>, <string-name><surname>Shelton</surname>, <given-names>J.L.</given-names></string-name>, <string-name><surname>Hevesi</surname>, <given-names>J.A.</given-names></string-name>, and <string-name><surname>Weissmann</surname>, <given-names>G.S.</given-names></string-name></person-group>, <year>2004</year>, <article-title>Hydrogeologic characterization of the Modesto area, San Joaquin Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2004&#x2013;5232</volume>, <size units="page">54</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20045232</pub-id>.</mixed-citation></ref>
<ref id="r17"><mixed-citation publication-type="book">California Department of Food and Agriculture, 2022, California Agricultural Statistics Review&#x2014;2021&#x2013;2022: Sacramento, Calif., Department of Food and Agriculture, Office of Public Affairs, 157 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.cdfa.ca.gov/Statistics/PDFs/2022_Ag_Stats_Review.pdf">https://www.cdfa.ca.gov/Statistics/PDFs/2022_Ag_Stats_Review.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r18"><mixed-citation publication-type="web">California Department of Pesticide Regulation, 2018, Pesticide use reporting&#x2014;An overview of California&#x2019;s unique full reporting system: California Department of Pesticide Regulation website, accessed January 1, 2018, at <ext-link ext-link-type="uri" xlink:href="https://www.cdpr.ca.gov/pesticide-use-in-california/#:~:text=An%20Overview%20of%20California's%20Unique%20Full">https://www.cdpr.ca.gov/pesticide-use-in-california/#:~:text=An%20Overview%20of%20California's%20Unique%20Full</ext-link>.</mixed-citation></ref>
<ref id="r19"><mixed-citation publication-type="book">California Department of Public Works, 1946, Salinas Basin investigation: California Department of Water Resources Bulletin 52-B, 252 p.</mixed-citation></ref>
<ref id="r20"><mixed-citation publication-type="web">California Department of Water Resources, 1968, Water well standards&#x2014;State of California: California Department of Water Resources Bulletin 74, 205 p., accessed December 1, 2022, at <ext-link ext-link-type="uri" xlink:href="https://archive.org/details/castatewaterwell00calirich/page/n7/mode/2up?ref=ol%26view=theater">https://archive.org/details/castatewaterwell00calirich/page/n7/mode/2up?ref=ol&amp;view=theater</ext-link>.</mixed-citation></ref>
<ref id="r21"><mixed-citation publication-type="other">California Department of Water Resources, 1971a, Nitrates in ground waters of the central coast area: San Joaquin District Office Memorandum Report, 16 p.</mixed-citation></ref>
<ref id="r22"><mixed-citation publication-type="book">California Department of Water Resources, 1971b, Land use in California&#x2014;An index to surveys conducted by the California Department of Water Resources 1950&#x2013;1970: California Department of Water Resources Bulletin 176, 22 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/hornbeck_usa_3_d/52">https://digitalcommons.csumb.edu/hornbeck_usa_3_d/52</ext-link>.]</mixed-citation></ref>
<ref id="r23"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>California Department of Water Resources</collab></person-group>, <year>1973</year>, <source>Seawater intrusion, lower Salinas Valley, Monterey County</source>: <publisher-name>California Department of Water Resources</publisher-name>, <size units="page">91</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r24"><mixed-citation publication-type="other">California Department of Water Resources, 1994, California water plan update&#x2014;Volume 1: California Department of Water Resources Bulletin 160-93, 397 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.waterboards.ca.gov/waterrights/water_issues/programs/bay_delta/wq_control_plans/1995wqcp/admin_records/part05/328.pdf">https://www.waterboards.ca.gov/waterrights/water_issues/programs/bay_delta/wq_control_plans/1995wqcp/admin_records/part05/328.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r25"><mixed-citation publication-type="web">California Department of Water Resources, 1997, Monterey County land use: California Department of Water Resources database, accessed December 1, 2016, at <ext-link ext-link-type="uri" xlink:href="https://data.cnra.ca.gov/dataset/i15-landuse-monterey1997">https://data.cnra.ca.gov/dataset/i15-landuse-monterey1997</ext-link>.</mixed-citation></ref>
<ref id="r26"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>California Department of Water Resources</collab></person-group>, <year>2014</year>, <source>Statewide crop mapping GIS geodatabase</source>, accessed January 1, 2018, at <ext-link ext-link-type="uri" xlink:href="https://data.cnra.ca.gov/dataset/statewide-crop-mapping/resource/04f89c79-59d1-4981-a3ab-853fdbc79d37">https://data.cnra.ca.gov/dataset/statewide-crop-mapping/resource/04f89c79-59d1-4981-a3ab-853fdbc79d37</ext-link>.</mixed-citation></ref>
<ref id="r27"><mixed-citation publication-type="web">California Department of Water Resources, 2020, California&#x2019;s groundwater update 2020: California Department of Water Resources Bulletin 118, accessed January 5, 2023, at <ext-link ext-link-type="uri" xlink:href="https://data.cnra.ca.gov/dataset/calgw_update2020">https://data.cnra.ca.gov/dataset/calgw_update2020</ext-link>.</mixed-citation></ref>
<ref id="r28"><mixed-citation publication-type="web">California Department of Water Resources, 2023, Sustainable Groundwater Management Act (SGMA): California Department of Water Resources web page, accessed November 24, 2023, at <ext-link ext-link-type="uri" xlink:href="https://water.ca.gov/Programs/Groundwater-Management/SGMA-Groundwater-Management">https://water.ca.gov/Programs/Groundwater-Management/SGMA-Groundwater-Management</ext-link>.</mixed-citation></ref>
<ref id="r29"><mixed-citation publication-type="other">California Division of Oil, Gas, and Geothermal Resources, 1982, Oil and gas prospect wells drilled in California through 1980: California Division of Oil, Gas and Geothermal Resources Report TR01, 258 p.</mixed-citation></ref>
<ref id="r30"><mixed-citation publication-type="web">California Irrigation Management Information System, 2020, Meteorological data: California Department of Water Resources and University of California at Davis, accessed December 1, 2022, at <ext-link ext-link-type="uri" xlink:href="https://cimis.water.ca.gov/">https://cimis.water.ca.gov/</ext-link>.</mixed-citation></ref>
<ref id="r31"><mixed-citation publication-type="other">Clark, J.C., Brabb, E.E., and Rosenberg, L.I., 2000, Geologic map and map database of the Spreckels 7.5-minute quadrangle, Monterey County, California: U.S. Geological Survey Miscellaneous Field Studies Map MF&#x2013;2349, scale 1:24,000. [Available at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/mf/2001/2349/">https://pubs.usgs.gov/mf/2001/2349/</ext-link>.]</mixed-citation></ref>
<ref id="r32"><mixed-citation publication-type="other">Clark, J.C., Dupr&#x00E9;, W.R., and Rosenberg, L.I., 1997, Geologic map of the Monterey and Seaside 7.5-minute quadrangles, Monterey County, California&#x2014;A digital database: U.S. Geological Survey Open-File Report 97&#x2013;30, 15 p., 2 sheets, scale 1:24,000, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr9730</pub-id>.</mixed-citation></ref>
<ref id="r33"><mixed-citation publication-type="other">Cleath and Associates, 1991, Hydrogeologic investigation&#x2014;Salinas Valley dispersed well system area: Consultants report to Monterey County Water Resources Agency, March 1991, [variously paged].</mixed-citation></ref>
<ref id="r34"><mixed-citation publication-type="book">Cook, T.D., 1978, Soil survey of Monterey County, California (vol. 22): United States Department of Agriculture, Soil Conservation Service, [variously paged; 435 p.]. [Available at <ext-link ext-link-type="uri" xlink:href="https://archive.org/details/usda-soil-survey-of-monterey-county-california/mode/2up">https://archive.org/details/usda-soil-survey-of-monterey-county-california/mode/2up</ext-link>.]</mixed-citation></ref>
<ref id="r35"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Daly</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Halbleib</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Smith</surname>, <given-names>J.I.</given-names></string-name>, <string-name><surname>Gibson</surname>, <given-names>W.P.</given-names></string-name>, <string-name><surname>Doggett</surname>, <given-names>M.K.</given-names></string-name>, <string-name><surname>Taylor</surname>, <given-names>G.H.</given-names></string-name>, <string-name><surname>Curtis</surname>, <given-names>J.</given-names></string-name>, and <string-name><surname>Pasteris</surname>, <given-names>P.P.</given-names></string-name></person-group>, <year>2008</year>, <article-title>Physiographically sensitive mapping of climatological temperature and precipitation across the conterminous United States</article-title>: <source>International Journal of Climatology</source>, v. <volume>28</volume>, no. <issue>15</issue>, p. <fpage>2031</fpage>&#x2013;<lpage>2064</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1002/joc.1688</pub-id>.</mixed-citation></ref>
<ref id="r36"><mixed-citation publication-type="other">Dartnell, P., Maier, K.L., Erdey, M.D., Dieter, B.E., Golden, N.E., Johnson, S.Y., Hartwell, S.R., Cochrane, G.R., Ritchie, A.C., Finlayson, D.P., Kvitek, R.G., Sliter, R.W., Greene, H.G., Davenport, C.W., Endris, C.A., and Krigsman, L.M., 2016, California State waters map series&#x2014;Monterey Canyon and vicinity, California: U.S. Geological Survey Open-File Report 2016&#x2013;1072, 48 p., 10 sheets, scale 1:24,000, accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr20161072</pub-id>.</mixed-citation></ref>
<ref id="r37"><mixed-citation publication-type="web">Desert Research Institute, 2020, Remote automatic weather stations USA climate archive: Desert Research Institute website, accessed December 16, 2020, at <ext-link ext-link-type="uri" xlink:href="https://raws.dri.edu:443/">https://raws.dri.edu:443/</ext-link>.</mixed-citation></ref>
<ref id="r38"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Dewitz</surname>, <given-names>J.</given-names></string-name>, and <collab>U.S. Geological Survey</collab></person-group>, <year>2021</year>, <data-title>National Land Cover Database (NLCD) 2019 products</data-title>: <series>U.S. Geological Survey data release</series>, accessed December 31, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9KZCM54</pub-id>.</mixed-citation></ref>
<ref id="r39"><mixed-citation publication-type="other">Dibblee, T.W., Jr., 1971, Geologic maps of seventeen 15-minute quadrangles (1:62,500) along the San Andreas fault in vicinity of King City, Coalinga, Panoche Valley, and Paso Robles, California, with index map. (Quadrangles are Adelaida, Bradley, Bryson, Coalinga, Greenfield, Hernandez Valley, Joaquin Rocks, King City, New Idria, Panoche Valley, Parkfield, Paso Robles, Polvadero Gap, Priest Valley, &#x201C;Reef Ridge&#x201D;, San Ardo, San Miguel.): U.S. Geological Survey Open-File Report 71&#x2013;87, 17 pls., 19.75 &#x00D7; 22.44 inches or smaller, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr7187</pub-id>.</mixed-citation></ref>
<ref id="r40"><mixed-citation publication-type="other">Dibblee, T.W., Jr., 1972, Geologic maps of fourteen 15-minute quadrangles along the San Andreas fault in the vicinity of Paso Robles and Cholame southeastward to Maricopa and Cuyama, California: U.S. Geological Survey Open-File Report 72&#x2013;89, 14 maps, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr7289</pub-id>.</mixed-citation></ref>
<ref id="r41"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Dimitrakopoulos</surname>, <given-names>R.</given-names></string-name>, and <string-name><surname>Desbarats</surname>, <given-names>A.J.</given-names></string-name></person-group>, <year>1993</year>, <article-title>Geostatistical modeling of grid block permeabilities for 3D reservoir simulators</article-title>: <source>SPE Reservoir Engineering</source>, v. <volume>8</volume>, no. <issue>1</issue>, p. <fpage>13</fpage>&#x2013;<lpage>18</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.2118/21520-PA</pub-id>.</mixed-citation></ref>
<ref id="r42"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Doherty</surname>, <given-names>J.</given-names></string-name></person-group>, <year>2024</year>, <source>PEST-HP for Windows</source>: <publisher-loc>Brisbane, Australia</publisher-loc>, <publisher-name>Watermark Numerical Computing</publisher-name>, <size units="page">59</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r43"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Doherty</surname>, <given-names>J.E.</given-names></string-name>, and <string-name><surname>Hunt</surname>, <given-names>R.J.</given-names></string-name></person-group>, <year>2010</year>, <article-title>Approaches to highly parameterized inversion&#x2014;A guide to using PEST for groundwater-model calibration</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2010&#x2013;5169</volume>, <size units="page">37</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20105169</pub-id>.</mixed-citation></ref>
<ref id="r44"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Durbin</surname>, <given-names>T.J.</given-names></string-name>, <string-name><surname>Kapple</surname>, <given-names>G.W.</given-names></string-name>, and <string-name><surname>Freckleton</surname>, <given-names>J.R.</given-names></string-name></person-group>, <year>1978</year>, <source>Two-dimensional and three-dimensional digital flow models of the Salinas Valley ground-water basin, California</source>: <series>U.S. Geological Survey Water Resources Investigations</series> <volume>78&#x2013;113</volume>, <size units="page">134</size>&#x00A0;p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri78113</pub-id>.]</mixed-citation></ref>
<ref id="r45"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Durham</surname>, <given-names>D.L.</given-names></string-name></person-group>, <year>1974</year>, <article-title>Geology of the southern Salinas Valley area, California</article-title>: <series>U.S. Geological Survey Professional Paper</series> <volume>819</volume>, <size units="page">111</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/pp819</pub-id>.</mixed-citation></ref>
<ref id="r46"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Edinger-Marshall</surname>, <given-names>S.</given-names></string-name>, and <string-name><surname>Letey</surname>, <given-names>J.</given-names></string-name></person-group>, <year>1997</year>, <article-title>Irrigation shifts toward sprinklers, drip and microsprinklers</article-title>: <source>California Agriculture</source>, v. <volume>51</volume>, no. <issue>3</issue>, p. <fpage>38</fpage>&#x2013;<lpage>40</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3733/ca.v051n03p38</pub-id>.</mixed-citation></ref>
<ref id="r47"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, and <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name></person-group>, <year>2009</year><comment>a</comment>, <article-title>Development of a three-dimensional model of sedimentary texture in valley-fill deposits of the Central Valley, California, USA</article-title>: <source>Hydrogeology Journal</source>, v.&#x00A0;<volume>18</volume>, no.&#x00A0;<issue>3</issue>, p.&#x00A0;<fpage>625</fpage>&#x2013;<lpage>649</lpage>. [Available at <pub-id pub-id-type="doi">https://doi.org/10.1007/s10040-009-0539-7</pub-id>.]</mixed-citation></ref>
<ref id="r48"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Predmore</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Rewis</surname>, <given-names>D.L.</given-names></string-name>, and <string-name><surname>McPherson</surname>, <given-names>K.</given-names></string-name></person-group>, <year>2009</year><comment>b</comment>, <chapter-title>Numerical model of the hydrologic landscape and groundwater flow in California&#x2019;s Central Valley</chapter-title>, chap. C <italic>of</italic> <person-group person-group-type="editor"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name></person-group>, ed., <source>Groundwater availability of California&#x2019;s Central Valley</source>: <series>U.S. Geological Survey Professional Paper</series> <volume>1766</volume>, p. <fpage>121</fpage>&#x2013;<lpage>212</lpage>. [Available at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/pp/1766/">https://pubs.usgs.gov/pp/1766/</ext-link>.]</mixed-citation></ref>
<ref id="r49"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name>, and <string-name><surname>Rogers</surname>, <given-names>L.</given-names></string-name></person-group>, <year>2009</year><comment>c</comment>, <article-title>California&#x2019;s Central Valley groundwater study&#x2014;A powerful new tool to assess water resources in California's Central Valley</article-title>: <series>U.S. Geological Survey Fact Sheet</series> <volume>2009&#x2013;3057</volume>, <size units="page">4</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/fs20093057</pub-id>.</mixed-citation></ref>
<ref id="r50"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Stamos</surname>, <given-names>C.L.</given-names></string-name>, <string-name><surname>Flint</surname>, <given-names>L.E.</given-names></string-name>, <string-name><surname>Wright</surname>, <given-names>M.T.</given-names></string-name>, <string-name><surname>Burgess</surname>, <given-names>M.K.</given-names></string-name>, <string-name><surname>Sneed</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Brandt</surname>, <given-names>J.T.</given-names></string-name>, <string-name><surname>Martin</surname>, <given-names>P.</given-names></string-name>, and <string-name><surname>Coes</surname>, <given-names>A.L.</given-names></string-name></person-group>, <year>2015</year>, <article-title>Hydrogeology, hydrologic effects of development, and simulation of groundwater flow in the Borrego Valley, San Diego County, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2015&#x2013;5150</volume>, <size units="page">135</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20155150</pub-id>.</mixed-citation></ref>
<ref id="r51"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Traum</surname>, <given-names>J.A.</given-names></string-name>, <string-name><surname>Boyce</surname>, <given-names>S.E.</given-names></string-name>, <string-name><surname>Seymour</surname>, <given-names>W.A.</given-names></string-name>, <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name>, <string-name><surname>Brandt</surname>, <given-names>J.T.</given-names></string-name>, <string-name><surname>Sneed</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Bond</surname>, <given-names>S.</given-names></string-name>, and <string-name><surname>Marcelli</surname>, <given-names>M.F.</given-names></string-name></person-group>, <year>2024</year>, <article-title>Groundwater sustainability and land subsidence in California&#x2019;s Central Valley</article-title>: <source>Water</source>, v. <volume>16</volume>, no. <issue>8</issue>, p. <fpage>1189</fpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3390/w16081189</pub-id>.</mixed-citation></ref>
<ref id="r52"><mixed-citation publication-type="web">Feeney, M.B., and Rosenberg, L.I., 2003, Deep aquifer investigation&#x2014;Hydrogeologic data inventory, review, interpretation and implications: Consultants technical memorandum to Monterey County Water Resources Agency, 40 p., accessed January 1, 2017, at <ext-link ext-link-type="uri" xlink:href="https://www.countyofmonterey.gov/home/showdocument?id=19614">https://www.countyofmonterey.gov/home/showdocument?id=19614</ext-link>.</mixed-citation></ref>
<ref id="r53"><mixed-citation publication-type="other">Ferguson, I.A., and Llewellyn, D., 2015, Simulation of Rio Grande project operations in the Rincon and Mesilla Basins&#x2014;Summary of model configuration and results: U.S. Bureau of Reclamation Technical Memorandum No. 86-68210-2015-05, 56 p.</mixed-citation></ref>
<ref id="r54"><mixed-citation publication-type="other">Ferguson, I.A., Llewellyn, D., Hanson, R.T., and Boyce, S.E., 2016, User guide to the surface water operations process&#x2014;Simulation of large-scale surface water management in MODFLOW-based hydrologic models: U.S. Bureau of Reclamation Technical Memorandum No. 86-68210-2015-XX, 79 p.</mixed-citation></ref>
<ref id="r55"><mixed-citation publication-type="book">Ferriz, H., 2001, Groundwater resources of northern California&#x2014;An overview: Engineering Geology Practice in Northern California, California Division of Mines and Geology Bulletin 210, 30 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://sitesreservoirproject.riptideweb.com/references/REF23/Volume%203/Ch04_ResponsesToComments/Ferriz_2001_Groundwater%20Resources%20of%20NorCal.pdf">https://sitesreservoirproject.riptideweb.com/references/REF23/Volume%203/Ch04_ResponsesToComments/Ferriz_2001_Groundwater%20Resources%20of%20NorCal.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r56"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Flint</surname>, <given-names>A.L.</given-names></string-name>, and <string-name><surname>Flint</surname>, <given-names>L.E.</given-names></string-name></person-group>, <year>2007</year>, <article-title>Application of the basin characterization model to estimate in-place recharge and runoff potential in the Basin and Range carbonate-rock aquifer system, White Pine County, Nevada, and adjacent areas in Nevada and Utah</article-title>: <source>U.S. Geological Survey Scientific Investigations Report</source>&#x00A0;<volume>2007&#x2013;5099</volume>, <size units="page">21</size> p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20075099</pub-id>.]</mixed-citation></ref>
<ref id="r57"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Flint</surname>, <given-names>L.E.</given-names></string-name>, and <string-name><surname>Flint</surname>, <given-names>A.L.</given-names></string-name></person-group>, <year>2012</year>, <article-title>Downscaling future climate scenarios to fine scales for hydrologic and ecological modeling and analysis</article-title>: <source>Ecological Processes</source>, v. <volume>1</volume>, article 2, <size units="page">15</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1186/2192-1709-1-2</pub-id>.</mixed-citation></ref>
<ref id="r58"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Flint</surname>, <given-names>L.E.</given-names></string-name>, <string-name><surname>Flint</surname>, <given-names>A.L.</given-names></string-name>, and <string-name><surname>Stern</surname>, <given-names>M.A.</given-names></string-name></person-group>, <year>2021</year>, <article-title>The basin characterization model&#x2014;A regional water balance software package</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>H1</chapter-title>, <size units="page">85</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6H1</pub-id>.</mixed-citation></ref>
<ref id="r59"><mixed-citation publication-type="web">Fugro West, Inc., and Cleath and Associates, 2002, Final report&#x2014;Paso Robles groundwater basin study: Consultants report to County of San Luis Obispo Public Works Department, 396 p., accessed November 18, 2021, at <ext-link ext-link-type="uri" xlink:href="https://www.slocounty.ca.gov/departments/groundwater-sustainability/forms-documents/paso-robles-groundwater-basin/archived-documents/2002-08-prgb-study,-phase-i">https://www.slocounty.ca.gov/departments/groundwater-sustainability/forms-documents/paso-robles-groundwater-basin/archived-documents/2002-08-prgb-study,-phase-i</ext-link>.</mixed-citation></ref>
<ref id="r60"><mixed-citation publication-type="web">GEOSCIENCE Support Services, Inc., 2013, Protective elevations to control sea water intrusion in the Salinas Valley: Consultants technical memorandum to Monterey County Water Resources Agency, 36 p., accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://www.countyofmonterey.gov/home/showdocument?id=19642">https://www.countyofmonterey.gov/home/showdocument?id=19642</ext-link>.</mixed-citation></ref>
<ref id="r61"><mixed-citation publication-type="book">GEOSCIENCE Support Services, Inc., 2016, Paso Robles groundwater basin model update 577: San Luis Obispo County Flood Control &amp; Water Conservation District, 142 p.</mixed-citation></ref>
<ref id="r62"><mixed-citation publication-type="other">Gibeault, V.A., Cocker-ham, S., Henry, J.M, and Meyer, J., 1989, California turfgrass&#x2014;It&#x2019;s use, water requirement, and irrigation: California Turfgrass Culture, University of California Cooperative Extension, v. 39, nos. 3&#x2013;4, 14 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://turfgrass.ucr.edu/sites/default/files/2023-08/ctc39_34.pdf">https://turfgrass.ucr.edu/sites/default/files/2023-08/ctc39_34.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r63"><mixed-citation publication-type="book"><person-group person-group-type="editor"><string-name><surname>Golden</surname>, <given-names>N.E.</given-names></string-name>, and <string-name><surname>Cochrane</surname>, <given-names>G.R.</given-names></string-name></person-group>, eds., <year>2013</year>, <article-title>California State waters map series data catalog</article-title>: <series>U.S. Geological Survey Data Series</series> <volume>781</volume>, accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ds781</pub-id>.</mixed-citation></ref>
<ref id="r64"><mixed-citation publication-type="book">Greene, H.G., 1970, Geology of southern Monterey Bay and its relationship to the ground water basin and salt water intrusion: U.S. Geological Survey Open-File Report 70&#x2013;141, 50 p., 5 plates. [Available at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/publication/ofr70141">https://pubs.usgs.gov/publication/ofr70141</ext-link>.] </mixed-citation></ref>
<ref id="r65"><mixed-citation publication-type="other">Greene, H.G., 1977, Geology of the Monterey Bay region: U.S. Geological Survey Open-File Report 77&#x2013;718, 347 p., 9 sheets, accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr77718</pub-id>.</mixed-citation></ref>
<ref id="r66"><mixed-citation publication-type="confproc">Greene, H.G., and Clark, J.C., 1979, Neogene paleogeography of the Monterey Bay area, California, <italic>in</italic> Armentrout, J.M., Cole, M.R., and Ter Best, H., Jr., eds., Cenozoic paleogeography of the western United States: Pacific Coast Paleogeography Symposium 3, p. 277&#x2013;296.</mixed-citation></ref>
<ref id="r67"><mixed-citation publication-type="book">Hall, P., 1992, Selected geological cross sections in the Salinas Valley using GEOBASE: Consultants report to Monterey County Water Resources Agency, 124 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/hornbeck_cgb_6_a/26/">https://digitalcommons.csumb.edu/hornbeck_cgb_6_a/26/</ext-link>.]</mixed-citation></ref>
<ref id="r68"><mixed-citation publication-type="other">Hanson, B., and Bendixen, W., 2004, Drip irrigation evaluated in Santa Maria Valley strawberries: California Agriculture, University of California, v. 58, no. 1, p. 48&#x2013;53, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3733/ca.v058n01p48</pub-id>.</mixed-citation></ref>
<ref id="r69"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name></person-group>, <year>1988</year>, <article-title>Aquifer-system compaction, Tucson basin and Avra Valley, Arizona</article-title>: <series>U.S. Geological Survey Water-Resources Investigation Report</series> <volume>88&#x2013;4172</volume>, <size units="page">69</size> p.</mixed-citation></ref>
<ref id="r70"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Anderson</surname>, <given-names>S.R.</given-names></string-name>, and <string-name><surname>Pool</surname>, <given-names>D.R.</given-names></string-name></person-group>, <year>1990</year>, <article-title>Simulation of ground-water flow and potential land subsidence, Avra Valley, Arizona</article-title>: <series>U.S. Geological Survey Water-Resources Investigation Report</series> <volume>90&#x2013;4178</volume>, <size units="page">41</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri904178</pub-id>.</mixed-citation></ref>
<ref id="r71"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, and <string-name><surname>Benedict</surname>, <given-names>J.F.</given-names></string-name></person-group>, <year>1994</year>, <article-title>Simulation of ground-water flow and potential land subsidence, upper Santa Cruz River Basin, Arizona</article-title>: <series>U.S. Geological Survey Water-Resources Investigation Report</series> <volume>93&#x2013;4196</volume>, <size units="page">47</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri934196</pub-id>.</mixed-citation></ref>
<ref id="r72"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Boyce</surname>, <given-names>S.E.</given-names></string-name>, <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Hughes</surname>, <given-names>J.D.</given-names></string-name>, <string-name><surname>Mehl</surname>, <given-names>S.M.</given-names></string-name>, <string-name><surname>Leake</surname>, <given-names>S.A.</given-names></string-name>, <string-name><surname>Maddock</surname>, <given-names>T.</given-names>, <suffix>III</suffix></string-name>, and <string-name><surname>Niswonger</surname>, <given-names>R.G.</given-names></string-name></person-group>, <year>2014</year><comment>a</comment>, <article-title>One-water hydrologic flow model (MODFLOW-OWHM)</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A51</chapter-title>, <size units="page">120</size> p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6A51</pub-id>.]</mixed-citation></ref>
<ref id="r73"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, and <string-name><surname>Leake</surname>, <given-names>S.A.</given-names></string-name></person-group>, <year>1999</year>, <source>Documentation for HYDMOD&#x2014;A program for time-series data from the U.S. Geological Survey&#x2019;s modular three-dimensional finite-difference ground-water flow model</source>: <series>U.S. Geological Survey Open-File Report</series> <volume>98&#x2013;564</volume>, <size units="page">57</size>&#x00A0;p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr98564</pub-id>.]</mixed-citation></ref>
<ref id="r74"><mixed-citation publication-type="other">Hanson, R.T., Everett, R.R., Newhouse, M.W., Crawford, S.M., Pimentel, M.I., and Smith, G.A., 2002, Geohydrology of a deep-aquifer system monitoring-well site at Marina, Monterey County, California: U.S. Geological Survey Water-Resources Investigation Report 2002&#x2013;4003, 73 p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri024003</pub-id>.</mixed-citation></ref>
<ref id="r75"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Flint</surname>, <given-names>L.E.</given-names></string-name>, <string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Gibbs</surname>, <given-names>D.R.</given-names></string-name>, and <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name></person-group>, <year>2014</year><comment>b</comment>, <article-title>Hydrologic models and analysis of water availability in Cuyama Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2014&#x2013;5150</volume>, <size units="page">150</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20145150</pub-id>.</mixed-citation></ref>
<ref id="r76"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>Z.</given-names></string-name>, and <string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name></person-group>, <year>2004</year>, <article-title>Documentation of the Santa Clara Valley regional ground-water/surface-water flow model, Santa Clara Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2004&#x2013;5231</volume>, <size units="page">85</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20045231</pub-id>.</mixed-citation></ref>
<ref id="r77"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Lockwood</surname>, <given-names>B.</given-names></string-name>, and <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name></person-group>, <year>2014</year><comment>c</comment>, <article-title>Analysis of projected water availability with current basin management plan, Pajaro Valley, California</article-title>: <source>Journal of Hydrology</source>, v.&#x00A0;<volume>519</volume>, p.&#x00A0;<fpage>131</fpage>&#x2013;<lpage>147</lpage>. [Available at <pub-id pub-id-type="doi">https://doi.org/10.1016/j.jhydrol.2014.07.005</pub-id>.]</mixed-citation></ref>
<ref id="r78"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, <string-name><surname>Lear</surname>, <given-names>J.</given-names></string-name>, and <string-name><surname>Lockwood</surname>, <given-names>B.</given-names></string-name></person-group>, <year>2014</year><comment>d</comment>, <article-title>Integrated hydrologic model of Pajaro Valley, Santa Cruz and Monterey Counties, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2014&#x2013;5111</volume>, <size units="page">166</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20145111</pub-id>.</mixed-citation></ref>
<ref id="r79"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Martin</surname>, <given-names>P.</given-names></string-name>, and <string-name><surname>Koczot</surname>, <given-names>K.M.</given-names></string-name></person-group>, <year>2003</year>, <article-title>Simulation of ground-water/surface-water flow in the Santa Clara-Calleguas ground-water basin, Ventura County, California</article-title>: <series>U.S. Geological Survey Water-Resources Investigation Report</series> <volume>02&#x2013;4136</volume>, <size units="page">157</size> p., accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/wri/wri024136/text.html">https://pubs.usgs.gov/wri/wri024136/text.html</ext-link>.</mixed-citation></ref>
<ref id="r80"><mixed-citation publication-type="book">Harbaugh, A.W., 2005, MODFLOW-2005&#x2014;The U.S. Geological Survey modular ground-water model&#x2014;the ground-water flow process: U.S. Geological Survey Techniques and Methods, book 6, chap. A16, [variously paged], accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6A16</pub-id>.</mixed-citation></ref>
<ref id="r81"><mixed-citation publication-type="other">Harding ESE, 2001, Final report&#x2014;Hydrogeologic investigation of the Salinas Valley basin in the vicinity of Fort Ord and Marina, Salinas Valley, California: Consultants report to Monterey County Water Resources Agency, 41 p.</mixed-citation></ref>
<ref id="r82"><mixed-citation publication-type="other">Hart, E.W., 1985, Rinconada fault (Espinosa and San Marcos segments), Monterey and San Luis Obispo Counties: California Division of Mines and Geology Fault Evaluation Report FER-175, 8 p., 2 sheets, scale 1:24,000.</mixed-citation></ref>
<ref id="r83"><mixed-citation publication-type="web">Harter, T., Lund, J.R., Darby, J., Fogg, G.E., Howitt, R., Jessoe, K.K., Pettygrove, S.G., Quinn, J.F., Viers, J.H., Boyle, D.B., Canada, H.E., DeLaMora, N., Dzurella, K.N., Fryjoff-Hung, A., Hollander, A.D., Honeycutt, K.L., Jenkins, M.W., Jensen, V.B., King, A.M., Kourakos, G., Liptzin, D., Lopez, E.M., Mayzelle, M.M., McNally, A., Medellin-Azuara, J., and Rosenstock, T.S., 2012, Addressing nitrate in California&#x2019;s drinking water with a focus on Tulare Lake Basin and Salinas Valley Groundwater: Report for the State Water Resources Control Board Report to the Legislature, 92 p., accessed December 31, 2022, at <ext-link ext-link-type="uri" xlink:href="https://ucanr.edu/sites/groundwaternitrate/files/138956.pdf">https://ucanr.edu/sites/groundwaternitrate/files/138956.pdf</ext-link>.</mixed-citation></ref>
<ref id="r84"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Helm</surname>, <given-names>D.C.</given-names></string-name></person-group>, <year>1975</year>, <article-title>One-dimensional simulation of aquifer system compaction near Pixley, California&#x2014;1, Constant parameters</article-title>: <source>American Geophysical Union, Water Resources Research</source>, v. <volume>11</volume>, no. <issue>3</issue>, p. <fpage>465</fpage>&#x2013;<lpage>478</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1029/WR011i003p00465</pub-id>.</mixed-citation></ref>
<ref id="r85"><mixed-citation publication-type="data">Henson, W.R., Boyce, S.E., Franklin, H., Woodrow, A., Baillie, M., and Jachens, E.R., 2022a, Salinas Valley operational model&#x2014;Input operational data (ver. 2.0, September 2023): U.S. Geological Survey data release, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9CWNHN3</pub-id>.</mixed-citation></ref>
<ref id="r86"><mixed-citation publication-type="data">Henson, W.R., and Culling, D.P., 2025, Salinas Valley Integrated Hydrologic and Reservoir Operations Model, Monterey and San Luis Obispo Counties, California: U.S. Geological Survey data release, available at <pub-id pub-id-type="doi">https://doi.org/10.5066/P13U6JPT</pub-id>.</mixed-citation></ref>
<ref id="r87"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Earll</surname>, <given-names>M.M.</given-names></string-name>, <string-name><surname>Bond</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name>, and <string-name><surname>Woodrow</surname>, <given-names>A.</given-names></string-name></person-group>, <year>2023</year>, <data-title>Lower Salinas Valley hydrologic models&#x2014;Agricultural and municipal water supply and groundwater data (ver. 2.1, August 2024)</data-title>: <series>U.S. Geological Survey data release</series>, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9U67MIQ</pub-id>.</mixed-citation></ref>
<ref id="r88"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Hevesi</surname>, <given-names>J.A.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Bittner</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Herbert</surname>, <given-names>D.M.</given-names></string-name>, and <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2022</year><comment>b</comment>, <data-title>Salinas Valley hydrologic models&#x2014;Surface water data (ver. 1.1, September 2024)</data-title>: <series>U.S. Geological Survey data release</series>, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P93COXL6</pub-id>.</mixed-citation></ref>
<ref id="r89"><mixed-citation publication-type="data">Henson, W.R., Hevesi, J.A., Hanson, R.T., Stern, M.A., and Jachens, E.R., 2022c, Lower Salinas Valley hydrologic models&#x2014;Climate data (ver. 2.0, March 2025): U.S. Geological Survey data release, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9GTQCCF</pub-id>.</mixed-citation></ref>
<ref id="r90"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Hevesi</surname>, <given-names>J.A.</given-names></string-name>, and <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2025</year><comment>a</comment>, <data-title>Lower Salinas Valley hydrologic models&#x2014;Input inflow data</data-title>: <series>U.S. Geological Survey data release</series>, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9HAG7ZI</pub-id>.</mixed-citation></ref>
<ref id="r91"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, and <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2022</year>, <data-title>Lower Salinas Valley hydrologic models&#x2014;Discretization data (ver. 1.2, August 2024)</data-title>: <series>U.S. Geological Survey data release</series>, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9850MAK</pub-id>.</mixed-citation></ref>
<ref id="r92"><mixed-citation publication-type="data"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, and <string-name><surname>Jachens</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2024</year>, <data-title>Lower Salinas Valley Hydrologic Models&#x2014;Land Use Data</data-title>: <series>U.S. Geological Survey data release</series>, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9KSNNUD</pub-id>.</mixed-citation></ref>
<ref id="r93"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Medina</surname>, <given-names>R.L.</given-names></string-name>, <string-name><surname>Mayers</surname>, <given-names>C.J.</given-names></string-name>, <string-name><surname>Niswonger</surname>, <given-names>R.G.</given-names></string-name>, and <string-name><surname>Regan</surname>, <given-names>R.S.</given-names></string-name></person-group>, <year>2013</year>, <article-title>CRT&#x2014;Cascade Routing Tool to define and visualize flow paths for grid-based watershed models</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>D2</chapter-title>, <size units="page">28</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6D2</pub-id>.</mixed-citation></ref>
<ref id="r94"><mixed-citation publication-type="data">Henson, W.R., and Voss, S.A., 2023, CalPUR-LUE, version 1.0: U.S. Geological Survey software release, <pub-id pub-id-type="doi">https://doi.org/10.5066/P9GUWKZZ</pub-id>.</mixed-citation></ref>
<ref id="r95"><mixed-citation publication-type="book">Henson, W., Hanson, R.T., Boyce, S.E., Hevesi, J., and Jachens, E.R., 2025b, Salinas Valley Integrated Hydrologic and Reservoir Operations Models, Monterey and San Luis Obispo Counties, California: Earth ArXiv, preprint posted April 5, 2025, 198 p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.31223/X5ZD9N</pub-id>.]</mixed-citation></ref>
<ref id="r96"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Hevesi</surname>, <given-names>J.A.</given-names></string-name>, <string-name><surname>Henson</surname>, <given-names>W.R.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Bond</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Earll</surname>, <given-names>M.M.</given-names></string-name>, <string-name><surname>Herbert</surname>, <given-names>D.</given-names></string-name>, and <string-name><surname>Jachens</surname>, <given-names>E.</given-names></string-name></person-group>, <year>2025</year><comment>a</comment>, <article-title>Application of hydrologic simulation program&#x2014;FORTRAN (HSPF) as part of an integrated hydrologic model for the Salinas Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2025&#x2013;5009</volume>, <size units="page">148</size> p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20255009</pub-id>.]</mixed-citation></ref>
<ref id="r97"><mixed-citation publication-type="data">Hevesi, J., Henson, W., Hanson, R.T., Earll, M.M., Herbert, D.M., and Jachens, E.R., 2025b, Salinas Valley watershed model&#x2014;Application of hydrologic simulation program-FORTRAN (HSPF): U.S. Geological Survey data release, accessed September 20, 2024, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9FJAWC4</pub-id>.</mixed-citation></ref>
<ref id="r98"><mixed-citation publication-type="data">Hevesi, J.A., Henson, W.R., Hanson, R.T., Stern, M.A., and Jachens, E.R., 2022, Salinas Valley hydrologic system&#x2014;Regional climate data: U.S. Geological Survey data release, accessed September 20, 2024, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P942J2BC</pub-id>.</mixed-citation></ref>
<ref id="r99"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Hill</surname>, <given-names>M.C.</given-names></string-name>, <string-name><surname>Banta</surname>, <given-names>E.R.</given-names></string-name>, <string-name><surname>Harbaugh</surname>, <given-names>A.W.</given-names></string-name>, and <string-name><surname>Anderman</surname>, <given-names>E.R.</given-names></string-name></person-group>, <year>2000</year>, <article-title>MODFLOW-2000, the U.S. Geological Survey modular ground-water model&#x2014;User guide to the observation, sensitivity, and parameter-estimation processes and three post-processing programs</article-title>: <series>U.S. Geological Survey Open-File Report</series> <volume>00&#x2013;184</volume>, <size units="page">209</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr00184</pub-id>.</mixed-citation></ref>
<ref id="r100"><mixed-citation publication-type="book">Hill, M.C., and Tiedeman, C.R., 2007, Effective groundwater model calibration&#x2014;With analysis of data, sensitivities, predictions, and uncertainty: New York, Wiley and Sons, 455 p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1002/0470041080</pub-id>.</mixed-citation></ref>
<ref id="r101"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Hsieh</surname>, <given-names>P.A.</given-names></string-name>, and <string-name><surname>Freckelton</surname>, <given-names>J.R.</given-names></string-name></person-group>, <year>1993</year>, <source>Documentation of a computer program to simulate horizontal-flow barriers using the U.S. Geological Survey&#x2019;s modular three-dimensional finite-difference ground-water-flow model</source>: <series>U.S. Geological Survey Open-File Report</series> <volume>92&#x2013;477</volume>, <size units="page">32</size>&#x00A0;p. [Available at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/publication/ofr92477">https://pubs.usgs.gov/publication/ofr92477</ext-link>.]</mixed-citation></ref>
<ref id="r102"><mixed-citation publication-type="other">Hydrometrics, LLC, 2009, Seaside groundwater basin modeling and protective groundwater elevations: Consultants report prepared for the Seaside Basin Watermaster, 210 p.</mixed-citation></ref>
<ref id="r103"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Jacob</surname>, <given-names>C.E.</given-names></string-name></person-group>, <year>1940</year>, <source>On the flow of water in an elastic artesian aquifer</source>: <source>Eos, Transactions American Geophysical Union</source>, v. <volume>21</volume>, no. <issue>2</issue>, p. <fpage>574</fpage>&#x2013;<lpage>586</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1029/TR021i002p00574</pub-id>.</mixed-citation></ref>
<ref id="r104"><mixed-citation publication-type="web">Jennings, C.W., with modifications by Gutierrez, C., Bryant, W., Saucedo, G., and Wills, C., 2010, Geologic map of California: California Geological Survey Geologic Data Map No. 2, scale 1:750,000, accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://ngmdb.usgs.gov/Prodesc/proddesc_96750.htm">https://ngmdb.usgs.gov/Prodesc/proddesc_96750.htm</ext-link>.</mixed-citation></ref>
<ref id="r105"><mixed-citation publication-type="other">Johnson, S.Y., Dartnell, P., Hartwell, S.R., Cochrane, G.R., Golden, N.E., Watt, J.T., Davenport, C.W., Kvitek, R.G., Erdey, M.D., Krigsman, L.M., Sliter, R.W., and Maier, K.L., 2016, California State waters map series&#x2014;Offshore of Monterey, California (Johnson, S.Y., and Cochrane, S.A., eds.): U.S. Geological Survey Open-File Report 2016&#x2013;1110, 44 p., 10 sheets, scale 1:24,000, accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ofr20161110</pub-id>.</mixed-citation></ref>
<ref id="r106"><mixed-citation publication-type="other">Kennedy/Jenks Consultants, 2004a, Final report&#x2014;Hydrostratigraphic analysis of the northern Salinas Valley: Consultants report to Monterey County Water Resources Agency, [variously paged.] [Available at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/hornbeck_cgb_5/29/">https://digitalcommons.csumb.edu/hornbeck_cgb_5/29/</ext-link>.]</mixed-citation></ref>
<ref id="r107"><mixed-citation publication-type="book">Kennedy/Jenks Consultants, 2004b, Hydrogeologic analysis of the northern Salinas Valley: Consultants report prepared for Monterey County Water Resources Agency, 98 p.</mixed-citation></ref>
<ref id="r108"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Konikow</surname>, <given-names>L.F.</given-names></string-name>, <string-name><surname>Hornberger</surname>, <given-names>G.Z.</given-names></string-name>, <string-name><surname>Halford</surname>, <given-names>K.J.</given-names></string-name>, and <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name></person-group>, <year>2009</year>, <article-title>Revised multi-node well (MNW2) package for MODFLOW ground-water flow model</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A30</chapter-title>, <size units="page">67</size> p. [Available at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/tm/tm6a30/">https://pubs.usgs.gov/tm/tm6a30/</ext-link>.]</mixed-citation></ref>
<ref id="r109"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Krause</surname>, <given-names>P.</given-names></string-name>, <string-name><surname>Boyle</surname>, <given-names>D.P.</given-names></string-name>, and <string-name><surname>B&#x00E4;se</surname>, <given-names>F.</given-names></string-name></person-group>, <year>2005</year>, <article-title>Comparison of different efficiency criteria for hydrological model assessment</article-title>: <source>Advances in Geosciences</source>, v. <volume>5</volume>, p. <fpage>89</fpage>&#x2013;<lpage>97</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.5194/adgeo-5-89-2005</pub-id>.</mixed-citation></ref>
<ref id="r110"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Kulongoski</surname>, <given-names>J.T.</given-names></string-name>, and <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name></person-group>, <year>2007</year>, <article-title>Ground-water quality data in the Monterey Bay and Salinas Valley Basins, California, 2005&#x2014;Results from the California GAMA Program</article-title>: <series>U.S. Geological Survey Data Series</series> <volume>258</volume>, <size units="page">84</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/ds258</pub-id>.</mixed-citation></ref>
<ref id="r111"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Lapham</surname>, <given-names>M.H.</given-names></string-name>, and <string-name><surname>Heileman</surname>, <given-names>W.H.</given-names></string-name></person-group>, <year>1901</year>, <source>Soil survey of the lower Salinas Valley</source>: <publisher-loc>California</publisher-loc>, <publisher-name>U.S. Department of Agriculture, Bureau of Soils</publisher-name>, <size units="page">519</size> p. [Available at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/hornbeck_usa_3_d/90/">https://digitalcommons.csumb.edu/hornbeck_usa_3_d/90/</ext-link>.]</mixed-citation></ref>
<ref id="r112"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Laudon</surname>, <given-names>J.</given-names></string-name>, and <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name></person-group>, <year>1991</year>, <article-title>Texture and depositional history of late Pleistocene-Holocene alluvium in the central part of the western San Joaquin Valley, California</article-title>: <source>Environmental &amp; Engineering Geoscience</source>, v. <volume>28</volume>, no. <issue>1</issue>, p. <fpage>73</fpage>&#x2013;<lpage>88</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.2113/gseegeosci.xxviii.1.73</pub-id>.</mixed-citation></ref>
<ref id="r113"><mixed-citation publication-type="other">Leedshill-Herkenhoff, Inc., 1985, Salinas Valley seawater intrusion study: Report prepared for the Monterey County Flood Control and Water Conservation District.</mixed-citation></ref>
<ref id="r114"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Leighton</surname>, <given-names>D.A.</given-names></string-name>, <string-name><surname>Fio</surname>, <given-names>J.L.</given-names></string-name>, and <string-name><surname>Metzger</surname>, <given-names>L.F.</given-names></string-name></person-group>, <year>1995</year>, <article-title>Database of well and areal data, South San Francisco Bay and Peninsula area, California</article-title>: <series>U.S. Geological Survey Water-Resources Investigations Report</series> <volume>94&#x2013;4151</volume>, <size units="page">47</size> p., accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/publication/wri944151">https://pubs.usgs.gov/publication/wri944151</ext-link>.</mixed-citation></ref>
<ref id="r115"><mixed-citation publication-type="book">Manning, J.C., 1963, Resume of ground water hydrology in Salinas Valley, California: Bakersfield, Calif., HydroDevelopment, Inc., 5 p.</mixed-citation></ref>
<ref id="r116"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Markstrom</surname>, <given-names>S.L.</given-names></string-name>, <string-name><surname>Niswonger</surname>, <given-names>R.G.</given-names></string-name>, <string-name><surname>Regan</surname>, <given-names>R.S.</given-names></string-name>, <string-name><surname>Prudic</surname>, <given-names>D.E.</given-names></string-name>, and <string-name><surname>Barlow</surname>, <given-names>P.M.</given-names></string-name></person-group>, <year>2008</year>, <article-title>GSFLOW&#x2014;Coupled ground-water and surface-water flow model based on the integration of the Precipitation-Runoff Modeling System (PRMS) and the Modular Ground-Water Flow Model (MODFLOW-2005)</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>D1</chapter-title>, <size units="page">240</size> p., accessed December 31, 2017, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6D1</pub-id>.</mixed-citation></ref>
<ref id="r117"><mixed-citation publication-type="web">Monterey County Agricultural Commission, 2022, Annual crop reports: Monterey County Agricultural Commission web page, accessed December 31, 2022, at <ext-link ext-link-type="uri" xlink:href="https://www.countyofmonterey.gov/government/departments-a-h/agricultural-commissioner/forms-publications/crop-reports-economic-contributions">https://www.countyofmonterey.gov/government/departments-a-h/agricultural-commissioner/forms-publications/crop-reports-economic-contributions</ext-link>.</mixed-citation></ref>
<ref id="r118"><mixed-citation publication-type="web">Monterey County Water Resources Agency, 1995, 1995&#x2014;Hydrogeology and water supply of Salinas Valley, White paper by Salinas Valley Ground Water Basin Hydrology Conference: Monterey County Water Resources Agency Water Reports, 18 p., accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://digitalcommons.csumb.edu/hornbeck_cgb_6_a/25">https://digitalcommons.csumb.edu/hornbeck_cgb_6_a/25</ext-link>.</mixed-citation></ref>
<ref id="r119"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>Monterey County Water Resources Agency</collab></person-group>, <year>1996</year>, <source>Summary report&#x2014;1995 groundwater extraction data and agricultural water conservation practices</source>: <publisher-name>Monterey County Water Resources Agency</publisher-name>, <size units="page">8</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r120"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>Monterey County Water Resources Agency</collab></person-group>, <year>2001</year>, <source>Draft environmental impact report/environmental impact statement for the Salinas Valley water project</source>: <publisher-name>Monterey County Water Resources Agency</publisher-name>, <size units="page">21</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r121"><mixed-citation publication-type="web">Monterey County Water Resources Agency, 2005, Salinas Valley water project flow prescription for Steelhead trout in the Salinas River: Salinas, Calif., [variously paged; 140 p.], accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://www.co.monterey.ca.us/home/showdocument?id=23311">https://www.co.monterey.ca.us/home/showdocument?id=23311</ext-link>.</mixed-citation></ref>
<ref id="r122"><mixed-citation publication-type="web">Monterey County Water Resources Agency, 2018, Nacimiento Dam operation policy: Monterey County Water Resources Agency, 31 p. plus appendixes, accessed December 31, 2018, at <ext-link ext-link-type="uri" xlink:href="https://www.co.monterey.ca.us/Home/ShowDocument?id=63151">https://www.co.monterey.ca.us/Home/ShowDocument?id=63151</ext-link>.</mixed-citation></ref>
<ref id="r123"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>Monterey County Water Resources Agency</collab></person-group>, <year>2020</year>, <source>Recommendations to address the expansion of seawater intrusion in the Salinas Valley groundwater basin&#x2014;2020 update</source>: <publisher-name>Monterey County Water Resources Agency</publisher-name>, <size units="page">96</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r124"><mixed-citation publication-type="web">Monterey County Water Resources Agency, 2023, Groundwater elevation contours: Monterey County Water Resources Agency data, accessed March 26, 2023, at <ext-link ext-link-type="uri" xlink:href="https://www.countyofmonterey.gov/government/government-links/water-resources-agency/documents/groundwater-elevation-contours">https://www.countyofmonterey.gov/government/government-links/water-resources-agency/documents/groundwater-elevation-contours</ext-link>.</mixed-citation></ref>
<ref id="r125"><mixed-citation publication-type="book">Montgomery Watson, 1997, Salinas River Basin water resources management plan task 1.09, 1994, Salinas Valley groundwater flow and quality model report: Report prepared for Monterey County Water Resources Agency, 189 p.</mixed-citation></ref>
<ref id="r126"><mixed-citation publication-type="other">Moran, J.E., Esser, B.K., Hillegonds, D., Holtz, M., Roberts, S.K., Singleton, M.J., and Visser, A., 2011, California GAMA special study&#x2014;Nitrate fate and transport in the Salinas Valley&#x2014;Final report for the California State Water Resources Control Board: Lawrence Livermore National Laboratory, California State University, East Bay, Report No. LLNL-TR-484186, 52 p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.2172/1122241</pub-id>.</mixed-citation></ref>
<ref id="r127"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Motz</surname>, <given-names>L.H.</given-names></string-name>, and <string-name><surname>Sedighi</surname>, <given-names>A.</given-names></string-name></person-group>, <year>2009</year>, <article-title>Representing the coastal boundary condition in regional groundwater flow models</article-title>: <source>Journal of Hydrologic Engineering</source>, v. <volume>14</volume>, no. <issue>8</issue>, p. <fpage>821</fpage>&#x2013;<lpage>831</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)HE.1943-5584.0000049</pub-id>.</mixed-citation></ref>
<ref id="r128"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Nalder</surname>, <given-names>I.A.</given-names></string-name>, and <string-name><surname>Wein</surname>, <given-names>R.W.</given-names></string-name></person-group>, <year>1998</year>, <article-title>Spatial interpolation of climatic normals&#x2014;Test of a new method in the Canadian boreal forest</article-title>: <source>Agricultural and Forest Meteorology</source>, v. <volume>92</volume>, no. <issue>4</issue>, p. <fpage>211</fpage>&#x2013;<lpage>225</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1016/S0168-1923(98)00102-6</pub-id>.</mixed-citation></ref>
<ref id="r129"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Nash</surname>, <given-names>J.E.</given-names></string-name>, and <string-name><surname>Sutcliffe</surname>, <given-names>J.V.</given-names></string-name></person-group>, <year>1970</year>, <article-title>River flow forecasting through conceptual models part I&#x2014;A discussion of principles</article-title>: <source>Journal of Hydrology</source>, v. <volume>10</volume>, no. <issue>3</issue>, p. <fpage>282</fpage>&#x2013;<lpage>290</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1016/0022-1694(70)90255-6</pub-id>.</mixed-citation></ref>
<ref id="r130"><mixed-citation publication-type="book">National Marine Fisheries Service, 2007, Biological opinion of the Salinas Valley water project: U.S. Department of Commerce, National Oceanic and Atmospheric Administration, Southwest Region, 123 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://www.fisheries.noaa.gov/s3/2023-05/nmfs-bo-salinas-valley-water-project-opinion-6-21-07.pdf">https://www.fisheries.noaa.gov/s3/2023-05/nmfs-bo-salinas-valley-water-project-opinion-6-21-07.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r131"><mixed-citation publication-type="web">National Oceanic and Atmospheric Administration, 2019, Tides &amp; currents&#x2014;Datums for 9413450 and 9414290, Monterey CA: National Oceanic and Atmospheric Administration data, accessed December 16, 2019, at <ext-link ext-link-type="uri" xlink:href="https://www.tidesandcurrents.noaa.gov">https://www.tidesandcurrents.noaa.gov</ext-link>.</mixed-citation></ref>
<ref id="r132"><mixed-citation publication-type="web">National Oceanic and Atmospheric Administration, 2020, Cooperative observer network climate data for sites within Monterey County: National Oceanic and Atmospheric Administration database, accessed December 16, 2020, at <ext-link ext-link-type="uri" xlink:href="https://www.ncdc.noaa.gov">https://www.ncdc.noaa.gov</ext-link>.</mixed-citation></ref>
<ref id="r133"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Niswonger</surname>, <given-names>R.G.</given-names></string-name>, and <string-name><surname>Prudic</surname>, <given-names>D.E.</given-names></string-name></person-group>, <year>2005</year>, <article-title>Documentation of the Streamflow-Routing (SFR2) Package to include unsaturated flow beneath streams&#x2014;A modification to SFR1</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A13</chapter-title>, <size units="page">50</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6A13</pub-id>.</mixed-citation></ref>
<ref id="r134"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Nutter</surname>, <given-names>E.H.</given-names></string-name></person-group>, <year>1901</year>, <article-title>Sketch of the geology of the Salinas Valley, California</article-title>: <source>The Journal of Geology</source>, v. <volume>9</volume>, no. <issue>4</issue>, p. <fpage>330</fpage>&#x2013;<lpage>336</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1086/620913</pub-id>.</mixed-citation></ref>
<ref id="r135"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Orang</surname>, <given-names>M.N.</given-names></string-name>, <string-name><surname>Matyac</surname>, <given-names>J.S.</given-names></string-name>, and <string-name><surname>Snyder</surname>, <given-names>R.L.</given-names></string-name></person-group>, <year>2008</year>, <article-title>Survey of irrigation methods in California in 2001</article-title>: <source>Journal of Irrigation and Drainage Engineering</source>, v. <volume>134</volume>, no. <issue>1</issue>, p. <fpage>96</fpage>&#x2013;<lpage>100</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)0733-9437(2008)134:1(96)</pub-id>.</mixed-citation></ref>
<ref id="r136"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Orgaz</surname>, <given-names>F.</given-names></string-name>, <string-name><surname>Fern&#x00E1;ndez</surname>, <given-names>M.D.</given-names></string-name>, <string-name><surname>Bonachela</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Gallardo</surname>, <given-names>M.</given-names></string-name>, and <string-name><surname>Fereres</surname>, <given-names>E.</given-names></string-name></person-group>, <year>2005</year>, <article-title>Evapotranspiration of horticultural crops in an unheated plastic greenhouse</article-title>: <source>Agricultural Water Management</source>, v. <volume>72</volume>, no. <issue>2</issue>, p. <fpage>81</fpage>&#x2013;<lpage>96</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1016/j.agwat.2004.09.010</pub-id>.</mixed-citation></ref>
<ref id="r137"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Phillips</surname>, <given-names>S.P.</given-names></string-name>, and <string-name><surname>Belitz</surname>, <given-names>K.</given-names></string-name></person-group>, <year>1991</year>, <article-title>Calibration of a texture-based model of a ground-water flow system, western San Joaquin Valley, California</article-title>: <source>Groundwater</source>, v. <volume>29</volume>, no. <issue>5</issue>, p. <fpage>702</fpage>&#x2013;<lpage>715</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1111/j.1745-6584.1991.tb00562.x</pub-id>.</mixed-citation></ref>
<ref id="r138"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Phillips</surname>, <given-names>S.P.</given-names></string-name>, <string-name><surname>Green</surname>, <given-names>C.T.</given-names></string-name>, <string-name><surname>Burow</surname>, <given-names>K.R.</given-names></string-name>, <string-name><surname>Shelton</surname>, <given-names>J.L.</given-names></string-name>, and <string-name><surname>Rewis</surname>, <given-names>D.L.</given-names></string-name></person-group>, <year>2007</year>, <article-title>Simulation of multiscale ground-water flow in part of the northeastern San Joaquin Valley, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2007&#x2013;5009</volume>, <size units="page">43</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20075009</pub-id>.</mixed-citation></ref>
<ref id="r139"><mixed-citation publication-type="web">PRISM Climate Group, 2020, Parameter-elevation Relationships on Independent Slopes Model (PRISM): PRISM Climate Group digital data, accessed December 16, 2020, at <ext-link ext-link-type="uri" xlink:href="https://prism.oregonstate.edu">https://prism.oregonstate.edu</ext-link>.</mixed-citation></ref>
<ref id="r140"><mixed-citation publication-type="web">Python Software Foundation, 2021, Python language reference, version 2.7, accessed July 3, 2021, at <ext-link ext-link-type="uri" xlink:href="http://www.python.org">http://www.python.org</ext-link>.</mixed-citation></ref>
<ref id="r141"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Sandoval&#x2010;Solis</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Orang</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Snyder</surname>, <given-names>R.L.</given-names></string-name>, <string-name><surname>Orloff</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Williams</surname>, <given-names>K.E.</given-names></string-name>, and <string-name><surname>Rodriguez</surname>, <given-names>J.M.</given-names></string-name></person-group>, <year>2013</year>, <source>Spatial analysis of application efficiencies in irrigation for the State of California&#x2014;Final report&#x2014;Water Management Research Group</source>: <publisher-name>University of California, Davis</publisher-name>, <size units="page">115</size>&#x00A0;p.</mixed-citation></ref>
<ref id="r142"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, and <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name></person-group>, <year>2009</year>, <article-title>The farm process version 2 (FMP2) for MODFLOW-2005&#x2014;Modifications and upgrades to FMP1</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A32</chapter-title>, <size units="page">102</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/tm6A32</pub-id>.</mixed-citation></ref>
<ref id="r143"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Schmid</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name>, <string-name><surname>Maddock</surname>, <given-names>T.M.</given-names>, <suffix>III</suffix></string-name>, and <string-name><surname>Leake</surname>, <given-names>S.A.</given-names></string-name></person-group>, <year>2006</year>, <article-title>User guide for the Farm Process (FMP1) for the U.S. Geological Survey&#x2019;s modular three-dimensional finite-difference ground-water flow model, MODFLOW-2000</article-title>: <series>U.S. Geological Survey Techniques and Methods</series>, book <source>6</source>, chap. <chapter-title>A17</chapter-title>, <size units="page">127</size> p., accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="https://pubs.usgs.gov/tm/2006/tm6A17">https://pubs.usgs.gov/tm/2006/tm6A17</ext-link>.</mixed-citation></ref>
<ref id="r144"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Showalter</surname>, <given-names>P.</given-names></string-name>, <string-name><surname>Akers</surname>, <given-names>J.P.</given-names></string-name>, and <string-name><surname>Swain</surname>, <given-names>L.A.</given-names></string-name></person-group>, <year>1984</year>, <article-title>Design of a ground-water quality monitoring network for the Salinas River Basin, California</article-title>: <series>U.S. Geological Survey Water Resources Investigation Report</series> <volume>83&#x2013;4049</volume>, <size units="page">74</size> p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri834049</pub-id>.]</mixed-citation></ref>
<ref id="r145"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Smukler</surname>, <given-names>S.M.</given-names></string-name>, <string-name><surname>Jackson</surname>, <given-names>L.E.</given-names></string-name>, <string-name><surname>Murphree</surname>, <given-names>L.</given-names></string-name>, <string-name><surname>Yokota</surname>, <given-names>R.</given-names></string-name>, <string-name><surname>Koike</surname>, <given-names>S.T.</given-names></string-name>, and <string-name><surname>Smith</surname>, <given-names>R.F.</given-names></string-name></person-group>, <year>2008</year>, <article-title>Transition to large-scale organic vegetable production in the Salinas Valley, California</article-title>: <source>Agriculture, Ecosystems &amp; Environment</source>, v. <volume>126</volume>, nos. <issue>3&#x2013;4</issue>, p. <fpage>168</fpage>&#x2013;<lpage>188</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1016/j.agee.2008.01.028</pub-id>.</mixed-citation></ref>
<ref id="r146"><mixed-citation publication-type="book">Snyder, R.L., Lanini, B.J., Shaw, D.A., and Pruitt, W.O., 1987a, Using reference evapotranspiration (ETo) and crop coefficients to estimate crop evapotranspiration (ETc) for agronomic crops, grasses, and vegetable crops: Cooperative Extension of the University of California Division of Agriculture and Natural Resources, Leaflet 21427, 12 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://cimis.water.ca.gov/Content/PDF/21427-KcAgronomicGrassandVeg.pdf">https://cimis.water.ca.gov/Content/PDF/21427-KcAgronomicGrassandVeg.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r147"><mixed-citation publication-type="book">Snyder, R.L., Lanini, B.J., Shaw, D.A., and Pruitt, W.O., 1987b, Using reference evapotranspiration (ETo) and crop coefficients to estimate crop evapotranspiration (ETc) for trees and vines: Cooperative Extension of the University of California, Division of Agriculture and Natural Resources, Leaflet 21428, 8 p. [Available at <ext-link ext-link-type="uri" xlink:href="https://cimis.water.ca.gov/Content/PDF/21428-KcTreesandVines.pdf">https://cimis.water.ca.gov/Content/PDF/21428-KcTreesandVines.pdf</ext-link>.]</mixed-citation></ref>
<ref id="r148"><mixed-citation publication-type="book">Snyder, R.L., and Schullbach, K.F., 1992, Central coast crop coefficients for field and vegetable crops: California Department of Water Resources, Water Conservation Office, Drought Tips No. 92-45, 12 p.</mixed-citation></ref>
<ref id="r149"><mixed-citation publication-type="other">Staal, Gardner, and Dunne, Inc., 1993, Hydrogeologic study&#x2014;Salinas Valley groundwater basin seawater intrusion delineation/monitoring well construction program&#x2014;180-foot aquifer, Salinas area, California: Consultants report to Monterey County Water Resources Agency, 41 p.</mixed-citation></ref>
<ref id="r150"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Sweetkind</surname>, <given-names>D.S.</given-names></string-name></person-group>, <year>2017</year>, <article-title>Three-dimensional hydrogeologic framework model of the Rio Grande transboundary region of New Mexico and Texas, USA, and northern Chihuahua, Mexico</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2017&#x2013;5060</volume>, <size units="page">49</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20175060</pub-id>.</mixed-citation></ref>
<ref id="r151"><mixed-citation publication-type="data">Sweetkind, D.S., 2023, Digital data for the Salinas Valley Geologic framework, California: U.S. Geological Survey data release, accessed September 20, 2024, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9IL8VBD</pub-id>.</mixed-citation></ref>
<ref id="r152"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Sweetkind</surname>, <given-names>D.S.</given-names></string-name>, <string-name><surname>Faunt</surname>, <given-names>C.C.</given-names></string-name>, and <string-name><surname>Hanson</surname>, <given-names>R.T.</given-names></string-name></person-group>, <year>2013</year>, <article-title>Construction of 3-D geologic framework and textural models for Cuyama Valley groundwater basin, California</article-title>: <series>U.S. Geological Survey Scientific Investigations Report</series> <volume>2013&#x2013;5127</volume>, <size units="page">46</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/sir20135127</pub-id>.</mixed-citation></ref>
<ref id="r153"><mixed-citation publication-type="book">Thorup, R.R., 1983, Hydrogeologic report on the deep aquifer, Salinas Valley, Monterey County, California: Consultants report to Monterey County Board of Supervisors, 40 p.</mixed-citation></ref>
<ref id="r154"><mixed-citation publication-type="other">Thorup, R.R., 1985, Summary hydrogeological report on the relationship of the 4 recently completed water wells on Fort Ord military reservation to the Salinas Valley 180 and 400 foot aquifers: Consultants report to Monterey County Board of Supervisors, [variously paged].</mixed-citation></ref>
<ref id="r155"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>Tindula</surname>, <given-names>G.N.</given-names></string-name>, <string-name><surname>Orang</surname>, <given-names>M.N.</given-names></string-name>, and <string-name><surname>Snyder</surname>, <given-names>R.L.</given-names></string-name></person-group>, <year>2013</year>, <article-title>Survey of irrigation methods in California in 2010</article-title>: <source>Journal of Irrigation and Drainage Engineering</source>, v. <volume>139</volume>, no. <issue>3</issue>, p. <fpage>233</fpage>&#x2013;<lpage>238</lpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)IR.1943-4774.0000538</pub-id>.</mixed-citation></ref>
<ref id="r156"><mixed-citation publication-type="thesis">Tinsley, J.C., III, 1975, Quaternary geology of northern Salinas Valley, Monterey County, California: Stanford, Calif., Stanford University, Ph.D. dissertation, 213 p.</mixed-citation></ref>
<ref id="r157"><mixed-citation publication-type="web">U.S. Census Bureau, 2018, Published population estimates for Monterey County: U.S. Department of Commerce data, accessed November 2018 at <ext-link ext-link-type="uri" xlink:href="https://www.census.gov/data.html">https://www.census.gov/data.html</ext-link>.</mixed-citation></ref>
<ref id="r158"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Department of Agriculture</collab></person-group>, <year>2016</year>, <data-title>USGS EROS archive-aerial photography-national agriculture imagery program</data-title>: <series>U.S. Geological Survey database</series>, accessed December 16, 2016, at <pub-id pub-id-type="doi">https://doi.org/10.5066/F7QN651G</pub-id>.</mixed-citation></ref>
<ref id="r159"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2000</year>, <data-title>National Land Cover Database (NLCD) 1992 land cover conterminous United States</data-title>: <series>U.S. Geological Survey data release</series>, accessed December 31, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P92G34R9</pub-id>.</mixed-citation></ref>
<ref id="r160"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2003</year>, <data-title>National Land Cover Database (NLCD) 2001 land cover conterminous United States</data-title>: <series>U.S. Geological Survey data release</series>, accessed December 31, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9MZGHLF</pub-id>.</mixed-citation></ref>
<ref id="r161"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2011</year>, <data-title>National Land Cover Database (NLCD) 2006 land cover conterminous United States</data-title>: <series>U.S. Geological Survey data release</series>, accessed December 31, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P9HBR9V3</pub-id>.</mixed-citation></ref>
<ref id="r162"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2013</year>, <article-title>National Elevation Dataset (USGS NED) n35w121 1/3 arc-second 2013 1 x 1 degree ArcGrid</article-title>: <series>U.S. Geological Survey dataset</series>, accessed March 8, 2016, at <ext-link ext-link-type="uri" xlink:href="https://apps.nationalmap.gov/viewer/">https://apps.nationalmap.gov/viewer/</ext-link>.</mixed-citation></ref>
<ref id="r163"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2014</year>, <data-title>National Land Cover Database (NLCD) 2011 land cover conterminous United States</data-title>: <series>U.S. Geological Survey data release</series>, accessed December 31, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/P97S2IID</pub-id>.</mixed-citation></ref>
<ref id="r164"><mixed-citation publication-type="web">U.S. Geological Survey, 2017, The national map&#x2014;Data delivery, accessed October 5, 2017, at <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/the-national-map-data-delivery">https://www.usgs.gov/the-national-map-data-delivery</ext-link>.</mixed-citation></ref>
<ref id="r165"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2018</year>, <data-title>USGS water data for the Nation</data-title>: <series>U.S. Geological Survey National Water Information System</series>, accessed December 23, 2018, at <pub-id pub-id-type="doi">https://doi.org/10.5066/F7P55KJN</pub-id>.</mixed-citation></ref>
<ref id="r166"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2019</year><comment>a</comment>, <article-title>3D elevation program 1-meter resolution digital elevation model</article-title>: <series>U.S. Geological Survey dataset</series>, accessed October 23, 2019, at <ext-link ext-link-type="uri" xlink:href="https://apps.nationalmap.gov/3depdem/">https://apps.nationalmap.gov/3depdem/</ext-link>.</mixed-citation></ref>
<ref id="r167"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2019</year><comment>b</comment>, <article-title>National hydrography dataset</article-title>: <series>U.S. Geological Survey web page</series>, accessed January 3, 2020, at <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/national-hydrography/national-hydrography-dataset">https://www.usgs.gov/national-hydrography/national-hydrography-dataset</ext-link>.</mixed-citation></ref>
<ref id="r168"><mixed-citation publication-type="data"><person-group person-group-type="author"><collab>U.S. Geological Survey</collab></person-group>, <year>2023</year>, <data-title>USGS water data for the Nation</data-title>: <series>U.S. Geological Survey National Water Information System database</series>, accessed October 1, 2023, at <pub-id pub-id-type="doi">https://doi.org/10.5066/F7P55KJN</pub-id>.</mixed-citation></ref>
<ref id="r169"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>U.S. Geological Survey and California Geological Survey</collab></person-group>, <year>2021</year>, <article-title>Quaternary fault and fold database for the United States</article-title>: <series>U.S. Geological Survey database</series>, accessed November 19, 2021, at <ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/programs/earthquake-hazards/faults">https://www.usgs.gov/programs/earthquake-hazards/faults</ext-link>.</mixed-citation></ref>
<ref id="r170"><mixed-citation publication-type="web">Wagner, D.L., Greene, H.G., Saucedo, G.J., and Pridmore, C.L., 2002, Geologic map of the Monterey 30' x 60' quadrangle and adjacent areas, California: California Geological Survey Regional Geologic Map Series, scale 1:100,000, accessed December 31, 2017, at <ext-link ext-link-type="uri" xlink:href="http://ngmdb.usgs.gov/Prodesc/proddesc_63084.htm">http://ngmdb.usgs.gov/Prodesc/proddesc_63084.htm</ext-link>.</mixed-citation></ref>
<ref id="r171"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Watt</surname>, <given-names>J.T.</given-names></string-name>, <string-name><surname>Morin</surname>, <given-names>R.L.</given-names></string-name>, and <string-name><surname>Langenheim</surname>, <given-names>V.</given-names></string-name></person-group>, <year>2010</year>, <article-title>Using potential fields to refine basin and fault geometry in Salinas Valley, California</article-title>: <source>Geological Society of America Abstracts with Programs</source>, v. <volume>42</volume>, no. <issue>4</issue>, <size units="page">78</size> p.</mixed-citation></ref>
<ref id="r172"><mixed-citation publication-type="other"><person-group person-group-type="author"><string-name><surname>White</surname>, <given-names>J.T.</given-names></string-name>, <string-name><surname>Hemmings</surname>, <given-names>B.</given-names></string-name>, <string-name><surname>Fienen</surname>, <given-names>M.N.</given-names></string-name>, and <string-name><surname>Knowling</surname>, <given-names>M.J.</given-names></string-name></person-group>, <year>2021</year>, <article-title>Towards improved environmental modeling outcomes&#x2014;Enabling low-cost access to high-dimensional, geostatistical-based decision-support analyses</article-title>: <source>Environmental Modelling &amp; Software</source>, v. <volume>139</volume>, article <fpage>105022</fpage>, accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.1016/j.envsoft.2021.105022</pub-id>.</mixed-citation></ref>
<ref id="r173"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Williamson</surname>, <given-names>A.K.</given-names></string-name>, <string-name><surname>Prudic</surname>, <given-names>D.E.</given-names></string-name>, and <string-name><surname>Swain</surname>, <given-names>L.A.</given-names></string-name></person-group>, <year>1989</year>, <article-title>Ground-water flow in the Central Valley, California</article-title>: <series>U.S. Geological Survey Professional Paper</series> <volume>1401&#x2013;D</volume>, <size units="page">127</size> p., accessed December 31, 2022, at <pub-id pub-id-type="doi">https://doi.org/10.3133/pp1401D</pub-id>.</mixed-citation></ref>
<ref id="r174"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Xie</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Lark</surname>, <given-names>T.J.</given-names></string-name>, <string-name><surname>Brown</surname>, <given-names>J.F.</given-names></string-name>, and <string-name><surname>Gibbs</surname>, <given-names>H.K.</given-names></string-name></person-group>, <year>2019</year>, <article-title>Mapping irrigated cropland extent across the conterminous United States at 30 m resolution using a semi-automatic training approach on Google Earth Engine</article-title>: <source>ISPRS Journal of Photogrammetry and Remote Sensing</source>, v.&#x00A0;<volume>155</volume>, p.&#x00A0;<fpage>136</fpage>&#x2013;<lpage>149</lpage>. [Available at <pub-id pub-id-type="doi">https://doi.org/10.1016/j.isprsjprs.2019.07.005</pub-id>.]</mixed-citation></ref>
<ref id="r175"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Yates</surname>, <given-names>E.B.</given-names></string-name></person-group>, <year>1988</year>, <source>Simulated effects of ground-water management alternatives for the Salinas Valley, California</source>: <series>U.S. Geological Survey Water-Resources Investigations Report</series> <volume>87&#x2013;4066</volume>, <size units="page">79</size>&#x00A0;p. [Available at <pub-id pub-id-type="doi">https://doi.org/10.3133/wri874066</pub-id>.]</mixed-citation></ref>
</ref-list>
<notes notes-type="colophon">
<sec>
<p>For more information concerning the research in this report, contact the</p>
<p content-type="indent">Director, California Water Science Center</p>
<p content-type="indent">U.S. Geological Survey</p>
<p content-type="indent">6000 J Street, Placer Hall</p>
<p content-type="indent">Sacramento, California 95819</p>
<p content-type="indent"><ext-link ext-link-type="uri" xlink:href="https://www.usgs.gov/centers/california-water-science-center">https://www.usgs.gov/centers/california-water-science-center</ext-link></p>
<p>Publishing support provided by the USGS Science Publishing Network,</p>
<p content-type="indent">Sacramento Publishing Service Center</p>
</sec></notes>
</book-back>
</book>
