<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20240919</CreaDate>
<CreaTime>14470300</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">VA_SMM_v6_Final_wm</itemName>
<itemSize Sync="TRUE">0.000</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">-8578570.065000</westBL>
<eastBL Sync="TRUE">-8490432.112100</eastBL>
<southBL Sync="TRUE">4436569.790100</southBL>
<northBL Sync="TRUE">4618513.711600</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;WGS_1984_Web_Mercator_Auxiliary_Sphere&amp;quot;,GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Mercator_Auxiliary_Sphere&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,0.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,0.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,0.0],PARAMETER[&amp;quot;Auxiliary_Sphere_Type&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,3857]]&lt;/WKT&gt;&lt;XOrigin&gt;-20037700&lt;/XOrigin&gt;&lt;YOrigin&gt;-30241100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102100&lt;/WKID&gt;&lt;LatestWKID&gt;3857&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</projcsn>
</coordRef>
</DataProperties>
<SyncDate>20250929</SyncDate>
<SyncTime>20214200</SyncTime>
<ModDate>20250929</ModDate>
<ModTime>20214200</ModTime>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<scaleRange>
<minScale>50000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>ISO19115_3</ArcGISProfile>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<rpIndName>Tami Rudnicky</rpIndName>
<rpOrgName>Virginia Institute of Marine Science (VIMS)</rpOrgName>
<rpPosName>GIS Programmer/Analyst</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">804-684-7181</voiceNum>
</cntPhone>
<cntAddress addressType="physical">
<delPoint>Virginia Institute of Marine Science, P.O. Box 1346, 1375 Greate Rd</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>tamia@vims.edu</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20250929</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distTranOps>
<onLineSrc>
<linkage>https://www.vims.edu/ccrm/advisory/ccrmp/bmp/smm/</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</onLineSrc>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
<distFormat>
<formatVer>ArcGIS 10.6</formatVer>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">Shoreline Management Model v.6.0 - Preferred Shoreline Best Management Practices</resTitle>
<date>
<pubDate>2024-08-19T00:00:00</pubDate>
</date>
<otherCitDet>Center for Coastal Resources Management. 2024. Shoreline Management Model, version 6.0. Center for Coastal Resources Management, Virginia Institute of Marine Science, College of William and Mary, Gloucester Point, Virginia.</otherCitDet>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
<citRespParty>
<rpIndName>Karinna Nunez</rpIndName>
<rpOrgName>Virginia Institute of Marine Science </rpOrgName>
<rpPosName>CCRM Geospatial Modeling Manager</rpPosName>
<role>
<RoleCd value="008"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>PO Box 1346 | 1208 Greate Road, Gloucester Point, VA 23062</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>karinna@vims.edu</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty=""> (804) 684-7273</voiceNum>
</cntPhone>
</rpCntInfo>
</citRespParty>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;In 2011, the Virginia General Assembly adopted a policy into law that specifies living shorelines as the preferred management practice for erosion control in Virginia waters. In accordance with the law, the Commonwealth defines a living shoreline as&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt; "...&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN STYLE="text-decoration:underline;"&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;a shoreline management practice that provides erosion control and water quality benefits; protects, restores or enhances natural shoreline habitat; and maintains coastal processes through the strategic placement of plants, stone, sand fill, and other structural and organic materials". The Center for Coastal Resources Management (CCRM) at the Virginia Institute of Marine Science (VIMS) has been developing tools for many years to guide local governments in shoreline management. In particular, they have focused on the use of ecologically preferred alternatives for erosion control and have conducted research into refining the appropriate uses for a large suite of possible treatments based on existing shoreline conditions. A series of Decision Trees were developed to determine shoreline best management practices (BMPs) when conducting onsite inspections. These were developed to support integrated guidance at the management and regulatory level. This body of work has been expanded and re-developed as a GIS spatial model known as the Shoreline Management Model (SMM) to determine appropriate shoreline BMPs from the desk-top using available spatial data and the decision tree logic. The assessment is conducted at parcel level scale, but the output represents a reach based or cumulative approach to shoreline management. &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;In 2023, CCRM began an update of the SMM. Version 6.0 continues to use fetch, nearshore bathymetry, bank height, marsh presence, beach presence, presence of submerged aquatic vegetation (SAV), roads and permanent structures within the riparian zone, and existing shoreline erosion control structures. To enhance the model’s capabilities for evaluating best management practices and determining where erosion control practices may impact ecologically sensitive areas, version 6.0 adds federal navigation channels, presence of RTE species via predicted suitable habitat, bank slope, and narrow creeks. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Most appropriate for desk-top reviews, regulatory compliance and comprehensive planning, the recommendations derived from the SMM may be altered due to lot size, shoreline length along a single parcel, proximity of primary buildings to the shoreline, type of existing erosion control structures, land use practices, and local biota. The output of the SMM is delivered to the end user in two ways: interactive map viewer, and digital ArcGIS file geodatabase.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>To provide a recommended preferred approach for shoreline erosion control via a geospatial Shoreline Management Model that identifies where living shorelines are suitable.</idPurp>
<resMaint>
<maintFreq>
<MaintFreqCd value="010"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Virginia, Chesapeake Bay, City of Poquoson, City of Hampton, Westmoreland County, City of Virginia Beach, Northumberland County, Gloucester County, Lancaster County, Mathews County, Middlesex County, York County</keyword>
</placeKeys>
<themeKeys>
<keyword>Shoreline Management Model, Preferred Shoreline Best Management Practices, Living Shorelines, Shoreline Conditions, Shoreline Structures, Shoreline Inventory, Erosion Control, Shoreline Treatments</keyword>
</themeKeys>
<searchKeys>
<keyword>shoreline</keyword>
<keyword>water interface shoreline</keyword>
<keyword>Shoreline Inventory</keyword>
<keyword>Shoreline Management Model</keyword>
<keyword>Virginia</keyword>
<keyword>living shoreline</keyword>
<keyword>shoreline erosion control</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 6 48;"&gt;&lt;SPAN STYLE="font-size:12pt"&gt;These data should be used to guide the decision making process on how best to manage an erosion problem. Recommendations are made without consideration of property length, ownership, or value. Treatment recommendations are based on models that utilize best available data which may not reflect the actual conditions present on the shoreline. The Center for Coastal Resources Management (CCRM) provides these data with the understanding that they are not guaranteed to be correct or complete, and conclusions drawn from the data set are the sole responsibility of the user. Every attempt has been made to ensure that these data and the documentation are reliable and accurate. CCRM, the Virginia Institute of Marine Science (VIMS), and Virginia Department of Environmental Quality, Virginia Coastal Zone Management Program (VA-DEQ, VCZMP) assume no liability for any damages caused by inaccuracies in the data or documentation; and make no warranty, express or implied, as to the accuracy, completeness, or utility of this information, nor does the fact of distribution constitute a warranty.&lt;/SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN STYLE="font-size:12pt"&gt;CCRM, VIMS, and VA-DEQ -VCZMP do not endorse trade names or recommend the use of commercial products mentioned in this document.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<envirDesc Sync="FALSE"> Esri ArcPro 3.1.3</envirDesc>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<idCredit>This project has been funded wholly or in part by The Virginia Department of Environmental Quality, Virginia Coastal Zone Management Program Grant # NA24NOSX419C0026.</idCredit>
<dataScale>
<scaleDist>
<value uom="[mi_br]"/>
</scaleDist>
</dataScale>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL>37.100650</westBL>
<eastBL>37.169617</eastBL>
<southBL>76.293836</southBL>
<northBL>76.413772</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idPoC>
<rpIndName>Tami Rudnicky</rpIndName>
<rpOrgName>Virginia Institute of Marine Science (VIMS)</rpOrgName>
<rpPosName>GIS Programmer/Analyst</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">804-684-7181</voiceNum>
</cntPhone>
<cntAddress addressType="physical">
<delPoint>Virginia Institute of Marine Science, P.O. Box 1346, 1375 Greate Rd</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>tamia@vims.edu</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
<displayName>Tami Rudnicky</displayName>
</idPoC>
<idPoC>
<rpIndName>Karinna Nunez</rpIndName>
<rpOrgName>Virginia Institute of Marine Science </rpOrgName>
<rpPosName>CCRM Geospatial Modeling Manager</rpPosName>
<role>
<RoleCd value="008"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>PO Box 1346 | 1208 Greate Road, Gloucester Point, VA 23062</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>karinna@vims.edu</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty=""> (804) 684-7273</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Karinna Nunez</displayName>
</idPoC>
<tpCat>
<TopicCatCd value="007"/>
</tpCat>
<tpCat>
<TopicCatCd value="002"/>
</tpCat>
<tpCat>
<TopicCatCd value="006"/>
</tpCat>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="010"/>
</maintFreq>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report dimension="" type="DQConcConsis">
<measDesc>Topology has been checked. There are no overlapping arcs. All arcs are greater than 1.5 meters in length.</measDesc>
</report>
<dataLineage>
<dataSource type="">
<srcDesc>Imagery 2021 from the Virginia Base Map Program (VBMP) was used as the primary remotely sensed data source for delineating shorelines, determining marsh and beach boundaries, locating erosion control structures and recreational structures, and other shoreline inventory data. Google Earth Imagery 1986-2024 was also used to augment the VBMP imagery.</srcDesc>
<srcCitatn>
<resTitle>Virginia Base Map Program Orthoimagery</resTitle>
<citRespParty>
<rpOrgName>Virginia Geographic Information Network (VGIN)</rpOrgName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="">
<city>Richmond</city>
<adminArea>Virginia</adminArea>
<eMailAdd>Gerard.Bernhardt@VDEM.Virginia.gov </eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">804-773-0780</voiceNum>
</cntPhone>
</rpCntInfo>
<rpIndName>Gerard Bernhardt</rpIndName>
<rpPosName>Geospatial Program Manager</rpPosName>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
<resAltTitle>VBMP 2021</resAltTitle>
<citOnlineRes>
<linkage>https://vgin.vdem.virginia.gov/pages/orthoimagery</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>The Tidal Marsh Inventory is produced by the Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. The Shoreline Management Model obtains marsh information from this source.</srcDesc>
<srcCitatn>
<resTitle>Tidal Marsh Inventory</resTitle>
<resAltTitle>Tidal Marsh Inventory</resAltTitle>
</srcCitatn>
<srcExt>
<exDesc>In 2023, a third iteration of the Virginia Tidal Marsh Inventory began in conjunction with the shoreline inventory update. This latest phase employs advanced remote sensing techniques, utilizing the most recent VBMP imagery and ESRI ArcGIS Pro software to map marsh boundaries (updated marsh extent and distribution). While historical plant community data was retained for existing marshes, newly identified marshes were initially classified as having an "undetermined" plant community type. This classification was only updated if high-resolution aerial imagery or drone-based photography provided conclusive evidence of the specific plant communities present.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2009-06-09T00:00:00</tmBegin>
<tmEnd>2018-08-16T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Fetch data is an unpublished data source created by the Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. This dataset provides information on shoreline exposure to potential wave energy via a distance model that measures distance to nearest water shoreline along compass rose. Measurements are taken at 25-meter increments along the shoreline.</srcDesc>
<srcCitatn>
<resTitle>Virginia Shoreline Fetch</resTitle>
<resAltTitle>Virginia Shoreline Fetch</resAltTitle>
</srcCitatn>
<srcExt>
<exDesc>Virginia Shoreline Fetch</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2007-01-01T00:00:00</tmBegin>
<tmEnd>2017-05-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>The Virginia Shoreline Inventory is produced by the Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. The inventory provides information on bank height, beach presence, and the location of shoreline structures such as riprap and bulkhead. There are six feature classes that combine to completer the updated Shoreline Inventory (in progress 2023-2026). Five of these datasets are used to inform the Shoreline Management Model (Bank Height and Slope, Erosion Control Structures, Tidal Marsh Inventory, Beaches and Dunes, and Recreational Structures).</srcDesc>
<srcCitatn>
<resTitle>Virginia Digital Shoreline Inventories</resTitle>
<resAltTitle>Virginia Digital Shoreline Inventories</resAltTitle>
<citRespParty>
<rpIndName>Karinna Nunez</rpIndName>
<rpOrgName>Virginia Institute of Marine Science </rpOrgName>
<rpPosName>CCRM Geospatial Modeling Manager</rpPosName>
<role>
<RoleCd value="008"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>PO Box 1346 | 1208 Greate Road, Gloucester Point, VA 23062</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>karinna@vims.edu</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty=""> (804) 684-7273</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Karinna Nunez</displayName>
</citRespParty>
<citOnlineRes>
<linkage>https://www.vims.edu/ccrm/research/inventory/virginia/</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>Each county has its own shoreline inventory that is generated in the lab by viewing high resolution imagery from the Virginia Base Mapping Program (VBMP), Bing maps, and Google Earth. Temporal period extent includes aerial image dates.</exDesc>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>The most recent 5 years of Submerged Aquatic Vegetation (SAV) was merged together to show SAV presence. This layer is unpublished, however single year SAV data can be downloaded from the VIMS SAV Monitoring Program website: https://www.vims.edu/research/units/programs/sav/reports/index.php</srcDesc>
<srcCitatn>
<resTitle>SAV Habitat 5 Years (2018-2022)</resTitle>
<citOnlineRes>
<linkage>https://www.vims.edu/research/units/programs/sav/reports/</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
<citRespParty>
<rpOrgName>Virginia Institute of Marine Science (VIMS)</rpOrgName>
<rpPosName>SAV Data Administrator</rpPosName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="">
<delPoint>Rt. 1208, Greate RD </delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>savadmin@vims.edu</eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">804-684-7088</voiceNum>
</cntPhone>
</rpCntInfo>
</citRespParty>
<otherCitDet>Localities publish in 2024 used 2018-2022 SAV Habitat data.
Localities publish in 2025 used 2019-2023 SAV Habitat data.</otherCitDet>
</srcCitatn>
<srcExt>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2018-10-01T00:00:00</tmBegin>
<tmEnd>2022-10-14T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Roads are obtained from the U.S. Department of Commerce, U.S. Census Bureau, Geography Division. The most recent TIGER/Line shapefile for the county is used. This dataset provides the location of roads and rails near the shoreline.</srcDesc>
<srcCitatn>
<resTitle>TIGER/Line Shapefile, {year}, county, {County Name}, VA, All Lines County-based Shapefile</resTitle>
<otherCitDet>The year of the TIGER/Line shapefile used for each county is one year prior to the county's Shoreline Management Model v 6.0 publication year..</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>Publication date for Poquoson TIGER/Line data is 2023-10</exDesc>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Data from the Shoreline Studies Program, Virginia Institute of Marine Science, Gloucester Point, Virginia is referenced when coding for beach.</srcDesc>
<srcCitatn>
<resTitle>Non-Jurisdictional Beach Assessment</resTitle>
<resAltTitle>Non-Jurisdictional Beach Assessment</resAltTitle>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>Building Footprints are obtained from VGIN. This layer is used to locate buildings near the shoreline.</srcDesc>
<srcCitatn>
<resTitle>Virginia Building Footprints</resTitle>
<citOnlineRes>
<linkage>https://vgin.vdem.virginia.gov/datasets/virginia-building-footprints/about</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>VIMS-CCRM Coastal Management Decision Tools created by the Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science, Gloucester Point, Virginia provides the framework for the GIS Shoreline Management Model.</srcDesc>
<srcCitatn>
<resTitle>Self-Guided Decision Support Tools</resTitle>
<citOnlineRes>
<linkage>https://www.vims.edu/ccrm/advisory/ccrmp/bmp/decision_tools/</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>The USGS Seamless Topobathymetric Elevation Model for the Chesapeake Bay (2016) for bathymetry is used to extract the 1-meter bathymetric contour for delineating shallow water.</srcDesc>
<srcCitatn>
<resTitle>2016 USGS CoNED Topobathymetric Model (1859 - 2015): Chesapeake Bay Region</resTitle>
<citOnlineRes>
<linkage>https://www.usgs.gov/special-topics/coastal-national-elevation-database-applications-project/science/hurricane-sandy-1</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>This Dataset utilizes data regarding Federal Channels, The dataset in question is the National Channel Framework. This dataset is uploaded by the U.S Army Corp of Engineers (USACE). From U.S. Army Corps of Engineers Geospatial:
This service shows all navigation channels maintained by USACE districts that have completed all or portions of the National Channel Framework through eHydro.
The National Channel Framework (NCF) is an enterprise Geographic Information System (eGIS) database providing information about congressionally authorized navigation channels maintained by the US Army Corps of Engineers. This service includes channel details based on district-managed GIS polygons rather than on CAD-based linework, and is maintained through the eHydro hydrographic survey application. Details include reaches, channel areas, quarters, centerlines, and stationing.</srcDesc>
<srcCitatn>
<resTitle>ChannelReach</resTitle>
<resAltTitle>ChannelReach</resAltTitle>
<citOnlineRes>
<linkage>https://geospatial-usace.opendata.arcgis.com/maps/9227967a2748410983352b501c0c7b39/about?layer=0</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>Dataset from the Virginia Natural Heritage Program. 2024. Predicted Suitable Habitat Summary. Virginia Department of Conservation and Recreation - Division of Natural Heritage, Richmond, VA. outlines polygon features describing where most suitable areas for certain species of Fauna and Flora.</srcDesc>
<srcCitatn>
<resTitle>Species lookup table for Predicted Suitable Habitat Summary</resTitle>
</srcCitatn>
</dataSource>
<prcStep>
<stepDesc>Completed localities are appended to one feature class and edge matched. Processing dates: 2024 - 2025</stepDesc>
</prcStep>
<prcStep>
<stepDesc>All processing steps occur in ArcPro version 3.x. ArcPy scripts have been created for use with each step, however after each script tool is run, a manual check of the results is necessary for accuracy. The water interface shoreline (developed referencing VBMP 2021 imagery) serves as the base shoreline and all information needed to run the Shoreline Management Model (SMM) is added onto this shoreline. The one-meter bathymetric contour is used to determine if the nearshore is suitable for marsh planting. If the 1-meter bathymetric contour is within 10 meters of the shoreline then the bathymetry field is coded as 'deep', otherwise it is coded as 'shallow'. Processing date: 2024-2025.</stepDesc>
<stepDateTm>2024-02-19T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Updated tidal marsh (TMI) presence is transferred from the polygon feature class to the linear water interface shoreline feature class. Processing date: 2024-2025.</stepDesc>
<stepDateTm>2024-02-22T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The most recent 5 years of SAV data was combined to create an SAV "habitat" layer. Only SAV polygons with density greater than zero were coded as "sav". The polygons were dissolved on the "sav" field to create a general sav habitat layer. The shoreline is coded for SAV presence if SAV is within 30 feet of the shoreline.</stepDesc>
<stepDateTm>2024-02-26T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>To add roads and permanent structures (physical structures near the shoreline that would prohibit bank grading), the shoreline is buffered based on 3 times the maximum height in the bank height category plus 20 feet. Tiger roads and rails are buffered according to road/rail type. The general rule is one lane = 12 ft and shoulder = 12 ft, rail lines = 30 ft, bike paths/walkways = 8 ft, vehicular trails = 12 ft with no shoulder. Where transportation buffers and shoreline buffers intersect, the resulting polygon vertices are converted to points. The ArcGIS NEAR tool is used to find the shortest distance from the point to the shoreline, adding x,y coordinates, distance, and direction to the point attribute table. Points that have a near distance less than or equal to the bank buffer width are retained. Near_x &amp; near_y coordinates are converted to points (these points overlay the shoreline). The POINTS TO LINE tool converts points with the same rd_id to individual lines. The lines are buffered and the IDENTITY tool is used to place the road coding on the shoreline. Building Footprints downloaded from VGIN Clearinghouse are used to help find Permanent Structures within the shoreline bank buffer. A similar technique (describe above) is used to code the shoreline for Permanent Structure. The shoreline is also visually inspected for any permanent structures (houses, swimming pools, sheds, etc) within the shoreline buffer, that may not have been captured by using building footprints. Shoreline is coded for permanent structures when encountered. Processing dates: 2024-2025</stepDesc>
<stepDateTm>2024-04-22T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Fetch is determined by creating 16 arcs based on the compass rose, radiating from points evenly spaced every 25 meters along the shoreline. The average arc length over water is calculated for the NE, SE, SW, and NW quadrants. The quadrant with the longest average fetch distance determines the fetch for the associated shoreline arc segment. Fetch is classified as low = 0-0.5 mile, moderate = 0.5-2 miles, and high = &gt; 2 miles.</stepDesc>
<stepDateTm>2024-06-10T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The shoreline must be visually scanned to determine if there are any man-made navigable canals. If there are, the corresponding shoreline is coded canal = 'yes'. Sand spits are noted in the SMM. If a sandspit is present, then sandspit = 'Yes'. Scripts are run to code for narrow waterways (&lt; 8 meters wide), sheltered waters (waters with average fetch less than or equal to 1.25 miles), and proximity of Federal Channels and habitat suitability for RTE species. Processing date: 2024-2025
</stepDesc>
<stepDateTm>2024-06-12T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Shoreline structures from the Virginia Shoreline Inventory Shoreline Protection Structures and Living Shoreline Treatments are added to the base shoreline. Offshore structures (groin, coir log, breakwater, sill, oyster structure) are listed under the field "offshorest". All other structures (bulkhead, dilapidated bulkhead, revetment, unconventional) are listed under "Structure". Processing dates: 2024-2025.</stepDesc>
<stepDateTm>2024-06-24T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The shoreline is given one last check for missing coding, errors, etc. Arcs less than or equal to 2 meters are dissolved into the larger adjacent arc. Topology is check for dangles and overlaps, and corrections made. Shoreline Management Model v 6.0 - Preferred Shoreline Best Management Practices model is run and the shoreline is coded with treatment recommendations. The SMM model queries a variety of spatial data and presents the preferred approach for erosion control. General preferred shoreline best management practices are recommended for all stretches of shoreline. Fetch, bank height and slope, marsh presence, beach presence, SAV and RTE habitat, nearshore water depth, permanent structures close to shoreline, sheltered waterways, federal channels, and existing shoreline erosion protection structures feed into the resulting recommendations.
The classification for the preferred shoreline best management practices provides recommendations across defended and undefended shorelines. There are 21 classifications that are grouped into 4 general groups: Living Shoreline
• Install Breakwater with Beach Nourishment
• Install Marsh-based Living Shoreline
• Maintain Breakwater with Beach Nourishment
• Maintain Sill / Add Sand and/or Plants OR Breakwater with Beach Nourishment
• Maintain Sill / Plant Marsh
• Protect/Enhance Beach or Breakwater with Beach Nourishment
• Protect/Enhance Beach or Breakwater with Beach Nourishment Channelward of Existing Structure
• Protect/Enhance Marsh add Sill/Toe
• Protect/Enhance Marsh / Marsh-based Living Shoreline
• Protect/Enhance Marsh with Structure (Sill/Oyster)
Add Living Shoreline - Remove Structure
• Breakwater with Beach Nourishment / Remove Bulkhead
• Breakwater with Beach Nourishment / Remove Existing Structures
• Breakwater with Beach Nourishment / Remove Revetment • Install Marsh-based Living Shoreline / Remove Bulkhead
• Install Marsh-based Living Shoreline / Reuse Stone
• Protect/Enhance Beach or Breakwater with Beach Nourishment / Remove Groins
Traditional Structure
• Maintain Revetment
• Revetment
• Revetment/Bulkhead Toe Revetment
• Revetment / Reuse Stone
No Action
• No Action Needed
</stepDesc>
<stepDateTm>2024-08-16T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
<report dimension="" type="DQCompOm">
<measDesc>All water interface shoreline is classified with either a shoreline best management practice or a ‘no action needed’ recommendation listed in the SMMv6Class field, and a definition listed in the SMMv6Def field. Note that shoreline inventory data collection and publication dates vary by locality and may not reflect the actual condition present on the shoreline.</measDesc>
</report>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="VA_SMM_v6_Final_wm">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="">
<refSysID>
<identCode Sync="TRUE" code="3857"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.18.3(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="VA_SMM_v6_Final_wm">
<enttyp>
<enttypl Sync="TRUE">VA_SMM_v6_Final_wm</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="FALSE">2095</enttypc>
<enttypd>Shoreline Management Model version 6.0 attributes</enttypd>
<enttypds>Processor</enttypds>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">riparianLU</attrlabl>
<attalias Sync="TRUE">riparianLU</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">beach</attrlabl>
<attalias Sync="TRUE">beach</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">BankSlope_Mean_Cat</attrlabl>
<attalias Sync="TRUE">BankSlope_Mean_Cat</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">512</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">bnk_height</attrlabl>
<attalias Sync="TRUE">bnk_height</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">canal</attrlabl>
<attalias Sync="TRUE">canal</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SandSpit</attrlabl>
<attalias Sync="TRUE">SandSpit</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">tidalMarsh</attrlabl>
<attalias Sync="TRUE">tidalMarsh</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SAV</attrlabl>
<attalias Sync="TRUE">SAV</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">narrowWtr</attrlabl>
<attalias Sync="TRUE">narrowWtr</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">shelterWtr</attrlabl>
<attalias Sync="TRUE">shelterWtr</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Structure</attrlabl>
<attalias Sync="TRUE">Structure</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">LS_Treat</attrlabl>
<attalias Sync="TRUE">LS_Treat</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Groin</attrlabl>
<attalias Sync="TRUE">Groin</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">512</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">offshorest</attrlabl>
<attalias Sync="TRUE">offshorest</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">mrnaWharf</attrlabl>
<attalias Sync="TRUE">mrnaWharf</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PublicRamp</attrlabl>
<attalias Sync="TRUE">PublicRamp</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FedChannel</attrlabl>
<attalias Sync="TRUE">FederalChannel</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">roads</attrlabl>
<attalias Sync="TRUE">roads</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PermStruc</attrlabl>
<attalias Sync="TRUE">PermStruc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">marshIsland</attrlabl>
<attalias Sync="TRUE">marshIsland</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">marshCreek</attrlabl>
<attalias Sync="TRUE">marshCreek</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Exposure</attrlabl>
<attalias Sync="TRUE">Exposure</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">rd_pstruc</attrlabl>
<attalias Sync="TRUE">rd_pstruc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">strcNrWtr</attrlabl>
<attalias Sync="TRUE">structureNearWater</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">shlDefend</attrlabl>
<attalias Sync="TRUE">shlDefend</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">bathymetry</attrlabl>
<attalias Sync="TRUE">bathymetry</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">bnkHgtSlpT</attrlabl>
<attalias Sync="TRUE">bankHeightSlopeType</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">bnkHgtSlpC</attrlabl>
<attalias Sync="TRUE">bankHeightSlopeComment</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">StrucList</attrlabl>
<attalias Sync="TRUE">StructureList</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">scHiMod</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_HighlyModified</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Defines if the feature is within a Highly Modified Area. Highly Modified Areas are
shoreline segments that are coded as canals, marinas, wharves, paved land use with roads near the shoreline, within 150 feet of federal navigation channels, or commercial/industrial sites with bulkhead or revetment shoreline erosion control structures. Management options may be limited due to the presence of highly developed upland (e.g. commercial wharfs) or infrastructure directly adjacent to the shoreline (e.g. road) and will depend on the need for and limitations posed by navigation access and erosion control. Seek expert advice on the design of your project. </attrdef>
<attrdefs>Glossary - SMM v6.0 Recommendations</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scEcoCon</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_EcologicalConflict</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Defines if the feature is in proximity to an Ecological Conflict. Ecological conflicts include the presence of Submerged Aquatic Vegetation (SAV) or Predicted Suitable Habitat (PSH) for RTE species. Management options for this shoreline may be limited, seek advice from the Virginia Marine Resources Commission Habitat Management Division and/or the Virginia Department of Conservation and Recreation – Natural Heritage Program. </attrdef>
<attrdefs>Glossary - SMM v6.0 Recommendations</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scAg</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_Agriculture</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Feature has Agriculture or Pastureland within 100 feet of the shoreline. The proximity of Agriculture and Pastureland increases the potential for non-point nutrient pollution.</attrdef>
<attrdefs>Processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scSand</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_Sandspit</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Special Consideration for a Sandspit. A Sandspit is constantly evolving deposition of Sand from the current of a water feature. Usually seen at the point of undefended peninsulas or peninsulas with a lack of vegetation where sand is able to move and collect freely.
</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scLU</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_LandUse</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Defines if the feature has a bank height greater than 30 feet and a bank slope that is moderate to very steep (slope greater than 10 degrees), or a bank height 15-30 feet and a very steep slope (slope greater than 45 degrees. Shorelines with tall banks greater than 30 feet limit possible solutions to address bank erosion. Forces other than tidal erosion, such as over-land runoff, upland development, and vegetation management are likely also having effect on bank conditions. Assessment of all factors and modifications to address causes for bank erosion are recommended. This may include changes to vegetation management, implementation of projects to address storm water, relocating buildings, utilities, and other infrastructure. All new construction should be located 100 feet or more from the top of the bank. Actions may also include requesting zoning variances for relief from setback and other land use requirements or restrictions that may increase erosion risk. Seek expert advice to inform management options
</attrdef>
<attrdefs>Glossary - SMM v6.0 Recommendations</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scNoAct</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_NoAction</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>No specific management actions are suitable for shoreline protection, e.g. boat ramps, marsh island, marsh creeks, narrow creeks, and barrier islands. </attrdef>
<attrdefs>Glossary - SMM v6.0 Recommendations</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scHiModDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_HighlyModified_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>If the feature fulfills the requirement for the Highly Modified Special Consideration the field will populate with the definition of the Highly Modified Special Consideration as defined by the Glossary of the SMM v6.0 Recommendations</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scEcoConDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_EcologicalConflict_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>If the feature fulfills the requirement for the Ecological Conflict Special Consideration the field will populate with the definition of the Ecological Conflict Special Consideration as defined by the Glossary of the SMM v6.0 Recommendations.</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scAgDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_Agriculture_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The Definition for Agriculture Special Considerations, defined as either Nutrient Reduction Potential or no.</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scSandDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_Sandspit_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>If sandspit features exist within the dataset the field will be populated with the Special Geomorphic Feature Definition. This is defined as:
Maintain the natural condition of this shoreline to allow for unimpeded sediment movement and the corresponding response of wetlands, beach, and/or dune. If primary structures are present and threatened, seek expert advice on the design of your project. </attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scLUDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_LandUse_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>If the feature fulfills the requirement for the Land Use Special Consideration, the field will populate with the definition of the Land Use Special Consideration as defined by the Glossary of the SMM v6.0 Recommendations</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">scNoActDef</attrlabl>
<attalias Sync="TRUE">SpecialConsideration_NoAction_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>If the No Action Special Consideration is met the field will populate with "No Action Needed" otherwise the field will remain as "no"</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SMMv6Class</attrlabl>
<attalias Sync="TRUE">SMM_v6_Classification</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">600</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Revised SMM v6.0 preferred shoreline BMP classifications</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
<attrdomv>
<edom>
<edomv>Install Breakwater with Beach Nourishment: </edomv>
<edomvd>Install a breakwater with sand nourishment to create a beach or enhance an existing beach. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Install Marsh-based Living Shoreline: </edomv>
<edomvd>Install marsh. Plant marsh vegetation at appropriate elevations. Use clean sand or native sediment to achieve proper elevation to plant marsh. A sill may be necessary for local wave conditions including boat wakes. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Maintain Breakwater with Beach Nourishment: </edomv>
<edomvd>Maintain existing breakwater with sand nourishment to create a beach or enhance an existing beach. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Maintain Sill / Add Sand and/or Plants OR Breakwater with Beach Nourishment:</edomv>
<edomvd>Maintain existing sill. Add sand to achieve appropriate elevations for marsh planting. Plant marsh vegetation between mean high water and to an elevation where the upland starts. Or use sill material to install a breakwater and include sand nourishment. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Maintain Sill / Plant Marsh: </edomv>
<edomvd>Maintain existing sill. Plant marsh vegetation between mean high water and to an elevation where the upland starts. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Beach or Breakwater with Beach Nourishment: </edomv>
<edomvd>Manage beach to ensure persistence. Add beach nourishment sand. Consider offshore breakwaters or another type of wave attenuation device with beach nourishment. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Beach or Breakwater with Beach Nourishment Channelward of Existing Structure: </edomv>
<edomvd>Manage beach and breakwater system to ensure persistence. May require adding additional sand nourishment and breakwater material. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Marsh add Sill/Toe </edomv>
<edomvd>Manage marsh for persistence by adding a marsh sill or toe channelward of the marsh. Marsh width may be increased by adding sand fill and planting to provide additional erosion protection. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Marsh / Marsh-based Living Shoreline: </edomv>
<edomvd>Manage marsh for persistence. Maintenance includes actions like removal of storm debris, including large wracks of vegetation, to minimize smothering of the marsh vegetation. Avoid application of fertilizers and insecticides in or near the marsh and stop mowing landward of the marsh. A sill may be necessary for local wave conditions including boat wakes. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Marsh with Structure (Sill/Oyster): </edomv>
<edomvd>Manage marsh for persistence. Existing marsh can be protected with the placement of a marsh toe. The existing marsh can be widened channelward with planting vegetation at proper elevations and placing a structure (sill/toe/oysters) to protect the leading edge of the planted marsh. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Breakwater with Beach Nourishment / Remove Bulkhead: </edomv>
<edomvd>Install a breakwater with sand nourishment to create a beach or enhance an existing beach. Remove bulkhead. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Breakwater with Beach Nourishment / Remove Existing Structures: </edomv>
<edomvd>Install a breakwater with sand nourishment to create a beach or enhance an existing beach. Remove extra existing structures. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Breakwater with Beach Nourishment / Remove Revetment: </edomv>
<edomvd>Install a breakwater with sand nourishment to create a beach or enhance an existing beach. Remove existing revetment. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Install Marsh-based Living Shoreline / Remove Bulkhead: </edomv>
<edomvd>Install marsh. Plant marsh vegetation at appropriate elevations. Use clean sand or native sediment to achieve proper elevation to plant marsh. Remove existing bulkhead. A sill may be necessary for local wave conditions including boat wakes. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Install Marsh-based Living Shoreline / Reuse Stone: </edomv>
<edomvd>Install marsh. Plant marsh vegetation at appropriate elevations. Use clean sand or native sediment to achieve proper elevation to plant marsh. Reuse revetment materials for marsh toe or sill. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Protect/Enhance Beach or Breakwater with Beach Nourishment / Remove Groins: </edomv>
<edomvd>Manage beach and breakwater system to ensure persistence. May require adding additional sand nourishment and breakwater material. Remove existing groins. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Maintain Revetment: </edomv>
<edomvd>Maintain existing revetment. Repair as needed. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Revetment: </edomv>
<edomvd>Construct new revetment as far landward as possible; grade the bank and plant vegetation buffers where possible. If grading is not possible, construct or repair existing revetment in the same alignment. Consider shoreline enhancement such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Revetment/Bulkhead Toe Revetment: </edomv>
<edomvd>If possible, remove the failed bulkhead and replace it with a revetment landward of the current bulkhead. If not possible, (re)construct bulkhead in the same alignment and add a toe revetment. Consider a shoreline enhancement project such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>Revetment / Reuse Stone: </edomv>
<edomvd>Construct new revetment, using existing material, as far landward as possible. Consider shoreline enhancement such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
<edom>
<edomv>No Action </edomv>
<edomvd>No specific management actions are suitable for shoreline protection, e.g. boat ramps, marsh island, marsh creeks, narrow creeks, and barrier islands. </edomvd>
<edomvds>SMM v6.0 Recommendations Glossary</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SMMv6ClsDef</attrlabl>
<attalias Sync="TRUE">SMMv6ClsDef</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">768</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The definition of each of the SSM Version 6.0 Classes</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">GenClass</attrlabl>
<attalias Sync="TRUE">GenClass</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Higher level classification of the SMM v6.0 preferred shoreline BMP classifications contains four categories: Living Shoreline, Replace Structure with Living Shoreline, Traditional Structure, and No Action.</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">County</attrlabl>
<attalias Sync="TRUE">County</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Virginia county or city name</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">StrucState</attrlabl>
<attalias Sync="TRUE">ObservedShorelineStructureStatement</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Describes whether a shoreline is or is not defended by a shoreline structure. If so the Shoreline protection structure is defined.</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Locality</attrlabl>
<attalias Sync="TRUE">Locality</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The City/County in which the feature is located.</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">pubDate</attrlabl>
<attalias Sync="TRUE">pubDate</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The year that the dataset was published</attrdef>
<attrdefs>CCRM</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Miles</attrlabl>
<attalias Sync="TRUE">Miles</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Length of the feature in Miles. Calculation is done using the NAD83 UTM18 N projection</attrdef>
<attrdefs>Center for Coastal Resources Management (CCRM)</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SpecCount</attrlabl>
<attalias Sync="TRUE">SpecialAreaCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Count of the number and type of Special Area designations for each arc segment</attrdef>
<attrdefs>Shoreline Management Model (SMM), Center for Coastal Resources Management, VIMS 2024</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
<overview>
<eaover>Six feature classes combine to complete the updated Shoreline Inventory (in progress 2023-2026). • {localityName}_BankHeightSlope_{publicationYear} - a polyline feature class contains bank height category and slope for segments of the upland shoreline.
• {localityName}_RecreationalStructures_{publicationYear} - a polygon feature class with locations of docks, community docks, dilapidated docks, private and public boat ramps, jetties, marinas (&lt; 50 and &gt; 50 slips), and wharves. • {localityName}_ErosionControlStructures_{publicationYear} (Shoreline Protection Structures &amp; Living Shoreline Treatments) - a polygon feature class delineating hardened shoreline structures that are used for erosion control (i.e., revetment, sill, bulkhead, breakwaters, groins, unconventional, oyster structures, and dilapidated bulkhead), as well as living shoreline treatments (breakwater with beach nourishment, marsh with sill, marsh with oyster structures [oyster bags, manufactured, natural materials], constructed oyster reef and coir logs).
• {localityName}_BeachesAndDunes_{publicationYear} - a polygon feature class that delineates the location of beaches and dunes.
• {localityName}_TMI_{publicationYear} (tidal marsh inventory) - a polygon feature class that shows the location, size, and community type of tidal marshes. In 2023, the update of tidal marsh inventory update began in conjunction with the shoreline inventory update. Marsh boundaries (updated marsh extent and distribution) were identified and mapped remotely using high-resolution color imagery from the Virginia Base Map Program (VBMP). Plant community types and other historical data from the previous inventory were maintained for marshes that intersected the same geographic location. New marshes were initially classified as having an "undetermined" plant community type. This classification was only updated if high-resolution aerial imagery or drone-based photography provided conclusive evidence of the specific plant communities present.
• {localityName}_MarshMigrationCorridors_{publicationYear} – a polygon feature class that shows the potential area of the current upland expected to become marsh under a selected sea level rise scenario. This layer is the result of combining the outputs from four existing marsh migration models into a single marsh migration corridor envelope.
For detailed information on a particular county, please visit the GIS Data and Maps: Shoreline Inventories website at https://www.vims.edu/ccrm/research/inventory/virginia/
</eaover>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="VA_SMM_v6_Final_wm">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">TRUE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
