<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<CreaDate>20240628</CreaDate>
<CreaTime>14142800</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20230920</SyncDate>
<SyncTime>15083500</SyncTime>
<ModDate>20230920</ModDate>
<ModTime>15083500</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Suitable_Living_Shoreline_Areas</itemName>
<itemSize Sync="TRUE">0.000</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">283956.019900</westBL>
<eastBL Sync="TRUE">471284.500200</eastBL>
<southBL Sync="TRUE">4045344.129000</southBL>
<northBL Sync="TRUE">4307847.916100</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_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">NAD_1983_UTM_Zone_18N</projcsn>
<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.1.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_UTM_Zone_18N&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-75.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26918]],VERTCS[&amp;quot;NAVD88 height&amp;quot;,VDATUM[&amp;quot;North American Vertical Datum 1988&amp;quot;],PARAMETER[&amp;quot;Vertical_Shift&amp;quot;,0.0],PARAMETER[&amp;quot;Direction&amp;quot;,1.0],UNIT[&amp;quot;Metre&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,5703]]&lt;/WKT&gt;&lt;XOrigin&gt;-5120900&lt;/XOrigin&gt;&lt;YOrigin&gt;-9998100&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;26918&lt;/WKID&gt;&lt;LatestWKID&gt;26918&lt;/LatestWKID&gt;&lt;VCSWKID&gt;5703&lt;/VCSWKID&gt;&lt;LatestVCSWKID&gt;5703&lt;/LatestVCSWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISProfile>FGDC</ArcGISProfile>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<Binary>
<Thumbnail>
<Data EsriPropertyType="PictureX">/9j/4AAQSkZJRgABAQEAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACFAMgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iii
gAooooAKKKKACiiigAooooAKaZEEixl1DsCwXPJAxk49sj8xTqy7kibxFZRDymaCJ52/e4dAfkGU
7hsnB7bCO9VFXA1KKKKkAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKK
Kq6jcTWlhLcQQGd4wG8terKCN2PfGcU0ruwGDrdxqWo6vHpujybPLgaS4kckQyKW2GPcvzBxgnII
Ix3yRWloOhW+i2MUYRHugmJbgjLyEnccseeSScdMkmoPC8dtNaXGqwXBuWv5mczsiqWVCUUEBV6A
dxnJIPSt2t6s3FeyWy/MSXUKKKK5xhRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFF
ABRRRQAVnahfpayGG5uPscM0eI7vKgK/ORlgVBxgjIOcH0rRoIBGCMg04tJ6gc1olm9gk1nY+IYb
xZy12nnKski7ycsu1gNhbkcYyW7EAZMk99pPjqAXcdwdKjjx/aFw+9nJVy3C42xjK5OMZC57EbF/
4aaPVv7a0Nre11HDCRHhUxzlyu4uQN2cKOQew9SDj3Wrrqq3eh+LxBoybNwAu4it7Hlt3ysCygbQ
eOcMOa76b5m5LVNa916Lr/VyGd3RWRJJrOn2Mz7LfUXQO6Zk8hyMkhTwVJxxu+UewrE0T4k6RrWo
WdkkF3BJeb/IeVAEbbkEbs9cqwAGc/y5Y0Kkk5RV0iro7KiiisRhRRRQAUUUUAFFFFABRRRQAUUU
UAFFFFABRRRQAUUUUAFFFFABRRRQAVR1fSbXWtNnsbuJHjlUqdw/wIPbsRV6mpJHJu8t1baxVtpz
gjsfenFuL5l0A888DeIbq3i0bwvJEZ5oEkjnneRV2LGv3cMQxZSVQhVIxg5Aro9c0IS+FLqy0W1s
muGj/wBG+0jfGhzkEZz06gdAQO1UtZ8JTtql5ren6hcRTGJWW2jQMDIuSWGerY+6OACWzkOwNHwh
rVtpRttEu4dlzMimO5ijLrfyEnfIpQFQACuSxDdcgAZPoTtN+2o77tee7/pELTRjvDHjhF/4lHiG
KTTbu2CQi4un/dzybASu/AUP6AncwG7Aziu6VgyhlIIIyCO9c74qsbt9OmmsbHTLxAVmntLyPaJm
UqQ3mbgAQFH3gRgDpjnmfhXcatey6pdvFc22hyFWsbadlkCMcl9kg5cA5GT7dTmonShVpuvDS26v
+XXz7efQadnY9JopkkgiUMVdssq4VSTyQM/Tnk9hT64SihqerQaWbVZY5pZLqYQRRwpuJYgnPYAA
Akk0l1q0dvqtrpyQSz3E4LHy9uIUBGWfJyBzxwckYrGhs7U+MZpLaN1t7ONmuppW3IJW+cKhJypw
7M38J3L1PSvZWlx4oN3cXditppt8iiXbIwkuYwAUwy4IUgnJPJBC8bTXUqUErva357afj/kTc66G
aK4hSaGRJYnGVdGDKw9QR1p9R28EVrbRW8KBIokCIo/hUDAH5VJXM7X0KCiiikAUUUUAFFFFABRR
RQAUUUUAFFFFABRRUDTst9Fb+XlXidzJu6FSoxj33H8vemlcCWVzHE7hC5VSdqkAn2GSB+ZrnLTz
tQsk17w5cRob+NZ3tbpt0UmRgHKklG4AyMjjlSeR0tcjrfhC5ku21Hw7qEmm3zljLGZpPs8zE53v
Gp5YHnIxnPORwdqLje0nb8vmJmvoWurq4uIJoGtdQtGCXNsxzsJ6MpwNynqDgZrnfGcD2msaXMEY
WN5crFcSPho4JjjypdpOQwYJyMDaGyeQax9XsfEukeJLHVGMMshnVZr2KJVM0fAZCBjJIxtVu6AB
snntr2G28QW6NYajH5qokqEqJoipY4LRk4OdrDPBGDzxXTyxozVSL91/h/XQndWPNrDxbr2hR37a
z51vELW6u7Ym2ZTeTKCDHJI+dpTaAuMFgoJzkbu8+HdqbTwLpiOYmmdWklaOQSEuzEncwGC3IB9w
RziuT1S28QWkkqN4dgaVkfzpluFbT3hHO8xPuZGGQCAD3xu7dh4J1HT9Q0Imyk055opSl3/Z8Bii
87AJwp56Ecn/AOtWuLalR5opatXt8+23z/DZKO50lcT421q+luLXw3oV0IdSvGIeZNxMIAB2kqDs
JGTu7KCfSuxurmKztJrqdtsUMbSO3ooGSfyFeT6FrNzpGjX/AInlksdT1LU7k2ltJCzO885YhIVJ
GBGp3fdzkLx0GefCUrt1LXtsvN/5blSfQ6a402M3dr4PsIU/s9o/P1WQHJZcAbWGMBpCATyCQWOO
prtlUKoVQAAMADtWT4d0u407TQ+oSpcarcYkvbhUC75MYwAAPlUYUewz1JrXrGtPmfKne34vq/66
DSCiiisBhRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABXO+J/tNk9jq1ldWVq8U6w3El67CNoXyNuB1
beUx07/Q9FWbqWiWuq3+m3Vyqt9gmM8alQfnxgHPbHXj0HvnSlJRneWwmcp4O8cfarC5TXbqBZLW
VYVuERws/wAqkvkqBjLdP4QOfWunOt2d/b3EGmalare7ZFh87puUfe25BZQepHHvT7rw9pN4sgms
LdmklErP5Y3FwQc569VX8q5iLwKdN1prnRUt7TErXRnlVpGdtuxYt2/dt5kZic/fG3px0t4eo3Je
6/wFqh/g7WJPF+i3+m68m6/tbpkuRCrJHgPuj2upIIxjox4Hfqa+hi38C397bXaNDYXU+8TtGOHP
CklRgK3TGPlbPQOqjFt7S8+Hs8w0m2kvtU1Rg7wXKqiNISNxEivsXOGIUgE+pwBV7ybLWJ7KLVHg
tdUuXktpbnTot0dyQRvjk3pypVgQfundnqFrqlTjeXL/AA5dvzt2Jv8AeUb59a1zxvrOn2OrCO9t
7doYQGCfLgtGTtViuC5Y5xv2Rj1I2fhpJLPca7KLAWcCywwyKcAvdLHmdio4GSy9hk59K55tEs9H
+I2nvrMtxHdszyRX6ypHGsUattJbaWC7SUILDtkn5SfYAqqWIUAsckgdT0/oKnF1YwpqEVdSS19P
z2+Q4rW5zfjyRn8Kz6fDKiXWoulnArSiPezsAVyeOV3euemD0PF3F9DB4v0+T7daW+neHI0t3tZe
A7OSjSpgjBUqy/MoACkjIbjt/EtgLrUdBupPs/k2l75j+eOFOxsMDg4IPAzgZYd8V5N8N5Jb/wAV
3elGN3a5u5LrV4JMSwxhQpAPGGdpCep+XaQM5JNYOK9hKXZNv56P8F+IpbnrnhSyuIbGa+uru5uJ
L5/NQTyl/Lix8ijgAZHzHgcsR2Fb9FFeXObnJyZogoooqACiiigAooooAKKKKACiiigAooooAKKK
KACiiigAooooAbJGksbRyKGRwVZT0IPUV5vqHhjRpZxoo1RrC+h1ETaeyJuWNdkTbNoOAAEABJBz
gg/Ng+lVwXxG8KaTeafP4ge0jOo2iBo2ACeawZcB2GG7YHzDqfauvBztU5eZq/bv0JktDO+Iehxa
54Ma+1C3iGr2MUcdy2wLjJGSpIb5Mkt8vJAIznIrpfh294/gyzN5PHPtZ0hdGLZjVioySTnoeemM
YrkNH8d2s3h3StY1KzHnwL9ne9mmAjaRchSu5h5jHONy52lpOgBzq+EdZ1jUoIUtJgjn948WouJh
LH8hMkMkeMKA4G0jgkD5SDnsrU6qoOlJaJ/0kSmr3Oy13TptW0W6sbe6FrLMoCTmPzNhBBztyM9P
WmaLoFhoUU4s4gJbiTzZ5jy8repPXgcD/EknjfD/AMVYte1uG1/s2W3tZZ/sscxBcPJgkfNxjIwR
kcjPIIAPo1cNaFagvZT0vqWmnqgooormGFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQA
UUVDdyvBZTyxxvJIkbMqIMsxAyAB600r6ATVz/jHRZ/EOiR6bCEMcl1A8+99o8tHDt2OfugY465z
xW1apLHZwJM5eVY1Dsf4mxyamqoTdOalHdC3OY1/w9pm6LVmtEkmsg5trUgCIzO4O/aFOZC+MH1P
ua5bwBoVtDDHe6/oNyuvRTylrk2rY+Z3YEMudxw+D34AP3a9GvUaRrWMBijTguV7BQWH/jyrVqui
OKnGk6ffz9dPxdxcutzzvxBrljp1jqtxYwfafJurWUxCN1aB1KoAVx8oGxCAeDuPbmvQIJ47m3iu
IWDRSoHRh3BGQa8v1uzum1zWNP1Gxv49LuriCVX06Fm3AxuC+UUElZUhY5JIyecE11/gMyL4WitX
WQJaSPBEXgeLdGp+XAcA7QDgew9citcTTiqKkt9PuaX4qwk9TpaKKK88sKKKKACiiigAooooAKKK
KACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAP/2Q==</Data>
</Thumbnail>
</Binary>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Tamia Rudnicky</rpIndName>
<rpOrgName>Comprehensive Coastal Inventory Program, Center for Coastal Resources Management, Virginia Institute of Marine Science</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>(804) 684-7181</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 1346</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distTranOps>
<onLineSrc>
<linkage>https://www.vims.edu/ccrm/ccrmp/index.php</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">Shoreline Management Model v.5.1 - Preferred Shoreline Best Management Practices - Virginia</resTitle>
<date>
<pubDate>2018-11-30T00:00:00</pubDate>
<reviseDate>2022-02-03T00:00:00</reviseDate>
</date>
<citRespParty>
<rpOrgName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress>
<delPoint>PO Box 1346 </delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<delPoint>1375 Greate Road</delPoint>
</cntAddress>
</rpCntInfo>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>Center for Coastal Resources Management. 2019. Shoreline Management Model, version 5.1. Center for Coastal Resources Management, Virginia Institute of Marine Science, College of William and Mary, Gloucester Point, Virginia.</otherCitDet>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:7 0 7 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 ... "... 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".&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN /&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;The Center for Coastal Resources Management (CCRM) at the Virginia Institute of Marine Science (VIMS) has been developing tools for several 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 when conducting onsite inspections. These were developed to support integrated guidance at the management and regulatory level.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN /&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;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 best management practices 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. The variables used in the SMM include fetch, nearshore bathymetry, bank condition, bank height, marsh presence, beach presence, tree canopy presence, and permanent structures within the riparian zone. Version 5 adds existing shoreline erosion control structures, and the presence of submerged aquatic vegetation (SAV) to enhance the models capabilities for evaluating best management practices along shorelines that have already been hardened or where erosion control practices may impact SAV.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN /&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&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 shape file.&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>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Karinna Nunez</rpIndName>
<rpOrgName>Virginia Institute of Marine Science</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(804) 684-7273</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>1375 Greate Road, P.O. Box 1346</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<eMailAdd>karinna@vims.edu</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Virginia, Chesapeake Bay, Accomack, Arlington, Caroline, Charles City, Chesterfield, City of Chesapeake, City of Colonial Heights, City of Fredericksburg, City of Hampton, City of Hopewell, City of Petersburg, City of Richmond, Essex, Fairfax, Gloucester, Hanover, Henrico, Isle of Wight, James City, King George, Kiing and Queen, King William, Lancaster, Mathews, Middlesex, New Kent, Newport News, Norfolk, Northampton, Northumberland, Poquoson, Portsmouth, Prince George, Prince William, Richmond, Spotsylvania, Stafford, Suffolk, Surry, Virginia Beach, Westmoreland, Williamsburg, York</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Categories</resTitle>
</thesaName>
<keyword>environment</keyword>
<keyword>elevation</keyword>
<keyword>planningCadastre</keyword>
<keyword>geoscientificInformation</keyword>
<keyword>biota</keyword>
</themeKeys>
<themeKeys>
<keyword>Shoreline Management Model, Preferred Shoreline Best Management Practices, Living Shorelines, Shoreline Conditions, Shoreline Structures, Riparian Land Use, Shoreline Inventory, Erosion Control, Shoreline Treatments</keyword>
</themeKeys>
<searchKeys>
<keyword>environment</keyword>
<keyword>Shoreline Management Model</keyword>
<keyword>Preferred Shoreline Best Management Practices</keyword>
<keyword>Living Shorelines</keyword>
<keyword>Shoreline Conditions</keyword>
<keyword>Shoreline Structures</keyword>
<keyword>Riparian Land Use</keyword>
<keyword>Shoreline Inventory</keyword>
<keyword>Erosion Control</keyword>
<keyword>Shoreline Treatments</keyword>
<keyword>elevation</keyword>
<keyword>planningCadastre</keyword>
<keyword>Virginia</keyword>
<keyword>Chesapeake Bay</keyword>
<keyword>Accomack</keyword>
<keyword>Arlington</keyword>
<keyword>Caroline</keyword>
<keyword>Charles City</keyword>
<keyword>Chesterfield</keyword>
<keyword>City of Chesapeake</keyword>
<keyword>City of Colonial Heights</keyword>
<keyword>City of Fredericksburg</keyword>
<keyword>City of Hampton</keyword>
<keyword>City of Hopewell</keyword>
<keyword>City of Petersburg</keyword>
<keyword>City of Richmond</keyword>
<keyword>Essex</keyword>
<keyword>Fairfax</keyword>
<keyword>Gloucester</keyword>
<keyword>Hanover</keyword>
<keyword>Henrico</keyword>
<keyword>Isle of Wight</keyword>
<keyword>James City</keyword>
<keyword>King George</keyword>
<keyword>King and Queen</keyword>
<keyword>King William</keyword>
<keyword>Lancaster</keyword>
<keyword>Mathews</keyword>
<keyword>Middlesex</keyword>
<keyword>New Kent</keyword>
<keyword>Newport News</keyword>
<keyword>Norfolk</keyword>
<keyword>Northampton</keyword>
<keyword>Northumberland</keyword>
<keyword>Poquoson</keyword>
<keyword>Portsmouth</keyword>
<keyword>Prince George</keyword>
<keyword>Prince William</keyword>
<keyword>Richmond</keyword>
<keyword>Spotsylvania</keyword>
<keyword>Stafford</keyword>
<keyword>Suffolk</keyword>
<keyword>Surry</keyword>
<keyword>Virginia Beach</keyword>
<keyword>Westmoreland</keyword>
<keyword>Williamsburg</keyword>
<keyword>York</keyword>
<keyword>geoscientificInformation</keyword>
<keyword>biota</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV STYLE="font-size:12pt"&gt;&lt;P&gt;&lt;SPAN&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.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-77.489078</westBL>
<eastBL>-75.320864</eastBL>
<southBL>36.529093</southBL>
<northBL>38.862369</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>ground condition and currentness of associated datasets.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1998-01-01T00:00:00</tmBegin>
<tmEnd>2017-08-31T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.3.41833</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-77.491055</westBL>
<eastBL Sync="TRUE">-75.320864</eastBL>
<northBL Sync="TRUE">38.919070</northBL>
<southBL Sync="TRUE">36.529093</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idCredit>Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science (VIMS),</idCredit>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;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 the Commonwealth of Virginia 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;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
<tpCat>
<TopicCatCd value="007"/>
</tpCat>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="002"/>
</tpCat>
<tpCat>
<TopicCatCd value="017"/>
</tpCat>
<tpCat>
<TopicCatCd value="006"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</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 1m in length.</measDesc>
</report>
<report dimension="" type="DQCompOm">
<measDesc>Shoreline coded for Riparian Land Use (RiparianLU) will have a shoreline best management practice recommendation listed in the SMMv5Class field and a definition listed in the SMMv5Def field. Note that shoreline inventory data collection and publication dates vary by locality and may not reflect the actual conditon present on the shoreline.</measDesc>
</report>
<dataLineage>
<dataSource type="">
<srcDesc>The Tidal Marsh Inventory is produced by the Comprehensive Coastal Inventory, 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>
<date>
<pubDate>2015-12-31T00:00:00</pubDate>
<reviseDate>2022-01-12T00:00:00</reviseDate>
</date>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>Tidal Marsh Inventory information for individual counties can be found with the Shoreline Inventory: https://www.vims.edu/ccrm/research/inventory/virginia/index.php</otherCitDet>
<citOnlineRes>
<linkage>https://www.vims.edu/ccrm/research/inventory/virginia/index.php</linkage>
</citOnlineRes>
<citRespParty>
<rpOrgName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress>
<delPoint>PO Box 1346 </delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<delPoint>1375 Greate Road</delPoint>
</cntAddress>
</rpCntInfo>
<displayName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</displayName>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>Marsh boundaries are digitized from high resolution aerial imagery. Field collection of marsh data is primarily performed from a small shallow-draft vessel, navigating at slow speeds parallel to the shoreline. Data was collected during the summer from 2009 to 2018.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2009-06-01T00: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 Comprehensive Coastal Inventory, 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 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>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<citRespParty>
<rpOrgName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress>
<delPoint>PO Box 1346 </delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<delPoint>1375 Greate Road</delPoint>
</cntAddress>
</rpCntInfo>
<displayName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</displayName>
<displayName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</displayName>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>Fetch uses the shoreline developed for the shoreline inventory. Shoreline is digitized using the most recent VBMP high resolution imagery available at the time of the inventory.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2007-01-01</tmBegin>
<tmEnd>2017-05-01</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>The Shoreline Inventory is produced by the Comprehensive Coastal Inventory, 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 forested shoreline in addition to the location of shoreline structures such as riprap and bulkhead.</srcDesc>
<srcCitatn>
<resTitle>Virginia Digital Shoreline Inventories</resTitle>
<resAltTitle>Virginia Digital Shoreline Inventories</resAltTitle>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>Each county has its own shoreline inventory. Please see http://www.vims.edu/ccrm/research/inventory/virginia/index.php for more information pertaining to the Shoreline Inventory for individual counties.</otherCitDet>
<citOnlineRes>
<linkage>http://www.vims.edu/ccrm/research/inventory/virginia/index.php</linkage>
</citOnlineRes>
<citRespParty>
<rpOrgName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress>
<delPoint>PO Box 1346 </delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<delPoint>1375 Greate Road</delPoint>
</cntAddress>
</rpCntInfo>
<displayName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</displayName>
<displayName>Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)</displayName>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>Each county has its own shoreline inventory. Between 2009 - 2015 shoreline inventoriy data was field collected by 2-3 person field crews using hand-held Trimble GeoExplorers GPS Units, while navigating by boat along the shoreline. Inventories published after 2015 are generated in the lab by viewing high resoultion imagery from the Virginia Base Mapping Program (VBMP), Bing maps, and Google Earth. Temporal period extent includes field days and aerial image dates.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2008-06-06</tmBegin>
<tmEnd>2018-08-16</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>The most recent 10 years of SAV merged together to show SAV presence. This layer is unpublished. SAV data can be downloaded from the VIMS website https://www.vims.edu/research/units/programs/sav/reports/index.php</srcDesc>
<srcCitatn>
<resTitle>SAV Habitat 10 Years (2007-2016)</resTitle>
<resAltTitle>SAV Habitat 10 Years (2007-2016)</resAltTitle>
<otherCitDet>King and Queen and King William Counties SMM used SAV data from 2015-2019.</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>Time period of SAV data.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2007-05-23</tmBegin>
<tmEnd>2016-11-17</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Virginia Base Map Program Imagery from the Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN) is used to locate permanent structures, confirm road location, and identify wide beaches.</srcDesc>
<srcCitatn>
<resTitle>Virginia Base Map Program Imagery 2017</resTitle>
<resAltTitle>Virginia Base Map Program Imagery 2017</resAltTitle>
<otherCitDet>Basemap imagery used could be VBMP 2009, 2011, 2013, or 2017</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>Virginia Base Map Program provides high resolution aerial imagery for the Commonealth of Virginia. The best aerial coverage for Virginia's coastal plain occur in the VBMP products for 2006/2007, 2009, 2011, 2013, and 2017.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2009-05-01</tmBegin>
<tmEnd>2017-05-01</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>
<date>
<pubDate>2015-05-01T00:00:00</pubDate>
</date>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>The year of the TIGER/Line shapefile used for each county is the same as the year the county's Shoreline Management Model was first puplished.</otherCitDet>
<citOnlineRes>
<linkage>https://www.census.gov/geo/maps-data/data/tiger-line.html</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>The year of the TIGER/Line shapefile used for each county is the same as the year the county's Shoreline Management Model was first puplished.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2010-01-01</tmBegin>
<tmEnd>2018-01-01</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Data from the Shoreline Studies Program, Virginia Institute of Marine Science, Gloucester Point, Virginia is used to identify wide beaches.</srcDesc>
<srcCitatn>
<resTitle>Non-Jurisdictional Beach Assessment</resTitle>
<resAltTitle>Non-Jurisdictional Beach Assessment</resAltTitle>
<date>
<pubDate>2006-01-01</pubDate>
</date>
</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>
<resAltTitle>Virginia Building Footprints</resAltTitle>
<citOnlineRes>
<linkage>https://vgin.maps.arcgis.com/home/item.html?id=994d0afa44c046498f9774613671ce9a</linkage>
</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. Online Linkage: https://www.vims.edu/ccrm/ccrmp/bmp/decision_tools/index.php</srcDesc>
</dataSource>
<dataSource type="">
<srcDesc>Shoreline Management Models processed prior to July 2016 used bathymetry that originated from the Special Projects Office of the National Ocean Service, NOAA. Beginning in July 2016, the USGS Seamless Topobathymetric Elevation Model for the Chesapeake Bay (2016) is used for bathymetry. The datasets provide the 1 meter bathymetric contour to delineate shallow water.</srcDesc>
<srcCitatn>
<resTitle>One and Two Meter Low Water Contours of the Chesapeake Bay</resTitle>
<resAltTitle>One and Two Meter Low Water Contours of the Chesapeake Bay</resAltTitle>
<date>
<pubDate>1998-01-01</pubDate>
</date>
</srcCitatn>
</dataSource>
<statement>This data set is a composite of Shoreline Management Models with base shoreline inventory data published beginning in 2009.</statement>
<prcStep>
<stepDesc>Tidal marsh presence is transferred from the polygon shapefile (TMI) to the linear shoreline shapefile. Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2016-02-05T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>All processing steps occur in ArcMap, ArcGIS version 10.x. Models have been created for use with each step, however after each model run, a manual check of the results is necessary for accuracy. The SHLINV coded shoreline serves as the base shoreline and contains information on bank height, presence of beach, and forest cover. All other data layer information is added to this shoreline. Shoreline created prior to mid 2015 is delineated along the water edge. After mid-2015, the shoreline is delineated as the upland interface (the interface between the upland and water or marsh). 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 dates: 2012 to 2022.</stepDesc>
<stepDateTm>2016-02-05T00: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 = 'Canal'. Sand spits are noted in the shoreline inventory. If a sand spit is present, then sandspit = 'Yes'. Forestshl is coded 'Yes' if the landuse is forested or if there is a wide (&gt;100 feet) tree fringe. Processing dates: 2012 to present.</stepDesc>
<stepDateTm>2016-02-05T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>All linear shoreline structures (except dilapidated bulkhead and jetty) from the SHLINV are added to the base shoreline. Offshore structures (groin, breakwater, marsh toe revetment) are listed under the field "offshorest". All other structures are listed under "Structure". Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2016-02-09T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The Shoreline Studies Program's beach layer (where available) is used to identify potential wide beaches. If the layer is unavailable, shoreline coded as beach is manually inspected with imagery in the background to determine if the area is a wide beach. A wide beach is a sandy beach with visible beach area above the regular tide. Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2016-02-18T00: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, shoreline should be coded for roads. Imagery along the shoreline is inspected for any permanent structures (houses, swimming pools, sheds, etc) that are within the shoreline buffer. Shoreline is coded for permanent structures when encountered. Processing dates: 2012 - 2017 Beginning with the 2018 shoreline inventory localities, a new technique was used to transfer roads and building footprints to the base shoreline. Where transportation buffer and shoreline buffer 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 VITA 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: 2018-2019</stepDesc>
<stepDateTm>2016-02-18T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>A tributary designation is assigned to the shoreline. Shoreline on the main stem of rivers is coded as major tributary, while small creeks are coded as tidal creek. Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2016-02-22T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The most recent 10 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 ft of the shoreline.</stepDesc>
<stepDateTm>2018-11-09T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The classification for the preferred shoreline best management practices provide recommendations across defended and undefended shorelines. There are 11 classifications: 1. Non-Structural Living Shoreline
2. Plant Marsh with Sill
3. Groin Field with Beach Nourishment 4. Maintain Beach or Offshore Breakwater with Beach Nourishment 5. Revetment
6. Revetment/Bulkhead Toe Revetment
7. Highly Modified Area
8. Ecological Conflicts
9. Special Geomorphic Feature
10. No Action Needed
11. Land Use Management</stepDesc>
<stepDateTm>2019-04-25T00: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. Fetch is re-analyzed onto 100 meter segments along the shoreline by determining the most common fetch classification within each 100 meter segment. Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2019-05-30T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The shoreline is given one last check for missing coding, errors, etc. Arcs less than or equal to 1m are dissolved into the larger adjacent arc. Topology is check for dangles and overlaps, and corrections made. Shoreline Management Model v.5.1 - 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. Forested shoreline, bank height, marsh presence, fetch, beach presence, SAV, nearshore water depth, and existing structures feed into the resulting recommendations. Processing dates: 2012 to 2022.</stepDesc>
<stepDateTm>2019-10-08T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<eainfo>
<detailed Name="Suitable_Living_Shoreline_Areas">
<enttyp>
<enttypl Sync="TRUE">Suitable_Living_Shoreline_Areas</enttypl>
<enttypd>Shoreline Management Model version 5.1 attributes</enttypd>
<enttypds>Processor</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl>rd_pstruc</attrlabl>
<attrdef>road or permanent structure is present within the shoreline buffer</attrdef>
<attrdefs>Shoreline Management Model, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>yes</edomv>
<edomvd>road or permanent structure is present within the shoreline buffer</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>a road or permanent structure is present (yes) within a certain distance of the shoreline</udom>
</attrdomv>
<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>Structure</attrlabl>
<attrdef>erosion control structure: riprap, bulkhead, unconventional, etc</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>Riprap</edomv>
<edomvd>Generally composed of large rock to withstand wave energy, riprap revetments are constructed along shores to protect eroding fastland.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Marina &lt; 50 slips</edomv>
<edomvd>Marinas are denoted as line features in the shoreline inventory. The infrastructure associated with the marina (e.g. bulkheading, docks, wharfs, etc) are not digitized individually. The survey estimates the number of slips within the marina and classifies marinas as those with less than 50 slips and those with more than 50 slips.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Bulkhead</edomv>
<edomvd>Bulkheads are traditionally treated wood or steel “walls” constructed to offer protection from wave attack. More recently, plastics are being used in the construction. Bulkheads are vertical structures built slightly seaward of the problem area and backfilled with suitable fill material. They function like a retaining wall, as they are designed to retain upland soil, and prevent erosion of the bank from impinging waves.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Debris</edomv>
<edomvd>Debris represents nonconforming materials and rubble dumped along the shoreline as shoreline protection. Debris can include tires, bricks, broken concrete rubble, and railroad ties as examples.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Marina &gt; 50 slips</edomv>
<edomvd>Marinas are denoted as line features in the shoreline inventory. The infrastructure associated with the marina (e.g. bulkheading, docks, wharfs, etc) are not digitized individually. The survey estimates the number of slips within the marina and classifies marinas as those with less than 50 slips and those with more than 50 slips.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Unconventional</edomv>
<edomvd>Unconventional features represent segments along the shore where unconventional material has been placed to protect a section of shore.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>list of shoreline protection structures that occur on the shoreline</udom>
</attrdomv>
<attalias Sync="TRUE">STRUCTURE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>invPubYr</attrlabl>
<attrdef>shoreline inventory publication year</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">invPubYr</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>2009</edomv>
<edomvd>Shoreline Inventories Published in 2009: Mathews County and Westmoreland County</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2010</edomv>
<edomvd>Shoreline Inventories Published in 2010: Alexandria, Fairfax, and Prince William</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2011</edomv>
<edomvd>Shoreline Inventories Published in 2011: Hampton, and Northampton</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2012</edomv>
<edomvd>Shoreline Inventories Published in 2012: Virginia Beach</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2013</edomv>
<edomvd>Shoreline Inventories Published in 2013: Charles City, Poquoson, Suffolk, and York</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2014</edomv>
<edomvd>Shoreline Inventories Published in 2014: Gloucester, James City and Williamsburg, Newport News, Norfolk, and Northumberland</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2015</edomv>
<edomvd>Shoreline Inventories Published in 2015: Lancaster and Middlesex Counties</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2016</edomv>
<edomvd>Shoreline Inventories Published in 2016: Accomack County, City of Chesapeake, Prince George County and the City of Hopewell</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2017</edomv>
<edomvd>Shoreline Inventories Published in 2017: Chesterfield and the Cities of Colonial Heights, Petersburg, and Richmond, City of Fredericksburg, Hanover County, Henrico County, Isle of Wight, King George, and Surry County</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2018</edomv>
<edomvd>Shoreline Inventories Published in 2018: Arlington, Caroline, Essex, New Kent, Richmond Counties</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>2019</edomv>
<edomvd>Shoreline Inventories Published in 2019: King and Queen, King William Counties</edomvd>
<edomvds>processor</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>marsh_all</attrlabl>
<attrdef>marsh is present or absent</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>no</edomv>
<edomvd>no marsh present</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>marsh present</edomv>
<edomvd>marsh is present</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>values can be "marsh present" or "no".</udom>
</attrdomv>
<attalias Sync="TRUE">marsh_all</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>HEIGHT</attrlabl>
<attrdef>Bank height is a visual inspection of the height of the bank from the base to the top. We estimate height from imagery, field inspection, videography or a combination of all three data sources. Bank height: 0-5 feet, 5-30 feet, or &gt;30 feet.</attrdef>
<attrdefs>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>Bank height: 0-5 feet, 5-30 feet, or &gt;30 feet.</udom>
</attrdomv>
<attalias Sync="TRUE">HEIGHT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>tribs</attrlabl>
<attrdef>shoreline is classified as tidal creek, major tributary, or bay front.</attrdef>
<attrdefs>Shoreline Management Model</attrdefs>
<attrdomv>
<edom>
<edomv>major tributary</edomv>
<edomvd>large stream or river that drains into an estuary like Chesapeake Bay or the Atlantic Ocean.</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>tidal creek</edomv>
<edomvd>small stream or river that is tidally influenced and drains into a major tributary, an estuary like Chesapeake Bay, or the Atlantic Ocean. A tidal creek has limited shoreline exposure to fetch &gt; 2 miles.</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>shoreline is classified as being part of a tidal creek or a major tributary.</udom>
</attrdomv>
<attalias Sync="TRUE">tribs</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>BarrierIsl</attrlabl>
<attrdef>Barrier Islands are found in Northampton County</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">BarrierIsl</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Tree_Fring</attrlabl>
<attrdef>When the dominant riparian land use is not forested, but a line of trees is maintained along the bank edge, the land use is noted to include a tree fringe. When the tree fringe is between 100 and 500 feet, it is considered a wide tree fringe. When the tree fringe is greater than 500 feet, it would be labled "forested" in land use.</attrdef>
<attrdefs>VIMS Shoreline &amp; Tidal Marsh Inventory Glossary, Center for Coastal Resources Management</attrdefs>
<attrdomv>
<edom>
<edomv>Yes</edomv>
<edomvd>Tree fringe is present</edomvd>
<edomvds>VIMS Shoreline &amp; Tidal Marsh Inventory Glossary, Center for Coastal Resources Management</edomvds>
</edom>
<edom>
<edomv>Yes w</edomv>
<edomvd>Tree fringe is between 100 -500 feet</edomvd>
<edomvds>VIMS Shoreline &amp; Tidal Marsh Inventory Glossary, Center for Coastal Resources Management</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">Tree_Fring</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ShlType</attrlabl>
<attrdef>shoreline defended or undefended based on time of survey</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>Undefended</edomv>
<edomvd>shoreline is not defended by a structure listed in the "Structures" or "offshorest" attributes.</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Defended</edomv>
<edomvd>Shoreline is protected by a structure listed in the "Structures" or "offshorest" attributes</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>shoreline is classified as defended or undefended</udom>
</attrdomv>
<attalias Sync="TRUE">ShlType</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>WideBeach</attrlabl>
<attrdef>A wide beach is a sandy beach with visible beach area above the regular tide.</attrdef>
<attrdefs>Shoreline Management Model</attrdefs>
<attrdomv>
<udom>wide beach is present (yes) or absent</udom>
</attrdomv>
<attalias Sync="TRUE">WideBeach</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>forestshl</attrlabl>
<attrdef>forested shoreline is "yes" if riparian land use is coded "forested" or Tree_fring = "Yes w"</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<udom>forested shoreline is "yes" if riparian land use is coded "forested" or if tree fringe is wide.</udom>
</attrdomv>
<attalias Sync="TRUE">forestshl</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PubYear</attrlabl>
<attrdef>Publication year of shoreline inventory</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">PubYear</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>canal</attrlabl>
<attrdef>man-made navigable canal</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>canal</edomv>
<edomvd>man-made navigable canal is present</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>canal is present (canal) or absent</udom>
</attrdomv>
<attalias Sync="TRUE">canal</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Shape_Length</attrlabl>
<attrdef>Length of feature in internal units.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Positive real numbers that are automatically generated.</udom>
</attrdomv>
<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>
</attr>
<attr>
<attrlabl>FIPSCode</attrlabl>
<attrdef>Federal Information Processing Standard code for Virginia cities and counties. Same as FIPS but represented as a text field.</attrdef>
<attalias Sync="TRUE">FIPSCode</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl>SURVEYED</attrlabl>
<attrdef>Year data collected and/or updated</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">SURVEYED</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Exposure</attrlabl>
<attrdef>from the shoreline exposure model. Fetch is determined by creating 16 arcs based on the compass rose, radiating from points evenly spaced 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. Arcs were aggregated into 100 meter segments and the most common fetch classification is used.</attrdef>
<attrdefs>Shoreline Management Model, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>moderate</edomv>
<edomvd>maximum average fetch is 0.5 - 2.0 miles</edomvd>
<edomvds>Shoreline Management Model</edomvds>
</edom>
<edom>
<edomv>low</edomv>
<edomvd>maximum average fetch is 0 - 0.5 mile</edomvd>
<edomvds>Shoreline Management Model</edomvds>
</edom>
<edom>
<edomv>high</edomv>
<edomvd>maximum average fetch is &gt; 2 miles</edomvd>
<edomvds>Shoreline Management Model</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>Fetch values are represented by low, moderate, or high.</udom>
</attrdomv>
<attalias Sync="TRUE">Exposure</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>HiModArea</attrlabl>
<attrdef>Highly Modified Area includes marinas, canals, paved riparian land use with roads adjacent to shoreline, and commercial or industrial areas with hardened shoreline.</attrdef>
<attrdefs>Shoreline Management Model, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>Highly Modified Area</edomv>
<edomvd>Highly Modified Area includes marinas, canals, paved riparian land use with roads adjacent to shoreline, and commercial or industrial areas with hardened shoreline.</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>a value used when processing the model</udom>
</attrdomv>
<attalias Sync="TRUE">HiModArea</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">75</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>RiparianLU</attrlabl>
<attrdef>current riparian land use: agriculture, bare, commercial, forested, grass, paved, residential, scrub-shrub</attrdef>
<attrdefs>Shoreline Inventory</attrdefs>
<attrdomv>
<edom>
<edomv>Paved</edomv>
<edomvd>Paved areas represent roads which run along the shore and generally are located at the top of the banks. Paved also includes parking areas such as parking at boat landing, or commercial facilities.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Residential</edomv>
<edomvd>Residential land use includes single and multi-family dwellings</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Grass</edomv>
<edomvd>Grasslands include large unmanaged fields, managed grasslands adjacent to large estates, agriculture tracts reserved for pasture, and grazing. While a general rule of thumb will classify a tract as “grass” if a home sits behind a large tract of grass, a designation of “residential” may be made if there are similar tracts adjacent to each other. This designation can be determined using best professional judgment.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Bare</edomv>
<edomvd>Land use defined as bare includes areas void of any vegetation or obvious land use. Bare areas include those that have been cleared for construction.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Agriculture</edomv>
<edomvd>Land use defined as agricultural includes farm tracts that are cultivated and crop producing. This designation is not applicable for pastureland.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Forested</edomv>
<edomvd>Forest cover includes deciduous, evergreen, and mixed forest stands greater than 18 feet high. The riparian zone is classified as forested if the tree stand extends at least 30 feet inland of the seaward limit of the riparian zone. If the forest cover is less than 30 feet wide from the shoreline than some other primary land use designation is made.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Commercial</edomv>
<edomvd>Commercial is a land use classification denoting small commercial operations such as shops, restaurants, as well as campgrounds. These operations are not necessarily water dependent businesses.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Industrial</edomv>
<edomvd>Industrial operations are larger commercial businesses and can include areas where power plants, pulp mills, refineries, etc, are in operations along the coast.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Scrub-shrub</edomv>
<edomvd>Scrub-shrub is a land use class that includes trees less than 18 feet high, and is usually dominated by shrubs and bushy plants.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>current riparian land use: agriculture, bare, commercial, forested, grass, paved, residential, scrub-shrub, timbered</udom>
</attrdomv>
<attalias Sync="TRUE">RiparianLU</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>defended</attrlabl>
<attrdef>shoreline is defended by an erosion control structure</attrdef>
<attrdefs>Shoreline Management Model, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>yes</edomv>
<edomvd>shoreline is defended by an erosion control structure that is listed in the attributes "Structures" and "offshorest"</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">defended</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>shoreline</attrlabl>
<attrdef>Shoreline is digitized while viewing high resolution imagery as the background layer. This field indicates the date of the Virginia Base Map Program (VBMP) imagery used.</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">Shoreline</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PublicRamp</attrlabl>
<attrdef>Paved Public Ramp is present</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">PublicRamp</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FIPS</attrlabl>
<attrdef>Federal Information Processing Standards (FIPS) are numeric codes assigned by the National Institute of Standards and Technology (NIST).</attrdef>
<attalias Sync="TRUE">FIPS</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdefs>ESRI</attrdefs>
</attr>
<attr>
<attrlabl>bathymetry</attrlabl>
<attrdef>water depth</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>shallow</edomv>
<edomvd>1 m bathymetric contour is greater than 10 m from shoreline</edomvd>
<edomvds>author</edomvds>
</edom>
<edom>
<edomv>deep</edomv>
<edomvd>1 meter bathymetric contour is within 10 m of shoreline</edomvd>
<edomvds>author</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>water depth is classified as either deep or shallow for use in the model.</udom>
</attrdomv>
<attalias Sync="TRUE">bathymetry</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SAV</attrlabl>
<attrdef>Indicates if Submerged Aquatic Vegetation (SAV ) is present within 30 feet of the shoreline. A 10 year composite of SAV presence is used.</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">SAV</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SandSpit</attrlabl>
<attrdef>A narrow coastal landform tied to the upland shoreline at one end resulting from the deposition of sand moved by tides and currents. Spit features are generally sandy and may be dominated by beach, dune, and/or marsh habitats. For inventory purposes, this definition does not include spit features that are developed or have developable upland.</attrdef>
<attrdefs>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>Sandspit is present ("yes") or absent.</udom>
</attrdomv>
<attalias Sync="TRUE">SandSpit</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Inventory</attrlabl>
<attrdef>Yesr of shoreline inventory or description of imagery used to create the shoreline inventory.</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">Inventory</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">150</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>COVER</attrlabl>
<attrdef>Bank cover is a classification based on a visual inspection of the bank. “Cover” can include either vegetative or structural cover.</attrdef>
<attrdefs>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>total</edomv>
<edomvd>&gt; 75% vegetative/structural cover</edomvd>
<edomvds>Shoreline Inventory definition, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>partial</edomv>
<edomvd>25-75% vegetative/structural cover</edomvd>
<edomvds>Shoreline Inventory definition, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>bare</edomv>
<edomvd>&lt; 25% vegetative/structural cover</edomvd>
<edomvds>Shoreline Inventory definition, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">COVER</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>BEACH</attrlabl>
<attrdef>Beaches are persistent sandy shores that are visible during high tides. These features can be wide or thin lenses of sand. Beaches are coded as linear features at the wet/dry line to portray their location only. If a beach does not have a visible wet/dry line, then the line feature is located at the seaward edge of the beach. ‘Wide’ beaches have at least 10 feet of dry sand persistently visible above high tides. Beach features coded along tidal marsh shorelines are persistent, sandy features located on the water side of tidal marsh vegetation. Sand washed into tidal marshes is not coded as a beach if the marsh vegetation &amp;/or marsh edge is still clearly visible. This classification of beaches along tidal marsh shorelines can include professional judgment.</attrdef>
<attrdefs>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>Yes</edomv>
<edomvd>beach is present</edomvd>
<edomvds>Shoreline Inventory definition, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>No</edomv>
<edomvd>beach is not present</edomvd>
<edomvds>Shoreline Inventory definition, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>beach is either present (yes) or absent</udom>
</attrdomv>
<attalias Sync="TRUE">BEACH</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>roads</attrlabl>
<attrdef>roads are present within shoreline buffer</attrdef>
<attrdefs>Shoreline Management Model, Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>roads are present (roads) or absent</udom>
</attrdomv>
<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>PermStruc</attrlabl>
<attrdef>permanent structures (houses, swimming pools, etc) are within the shoreline buffer</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>Permanent Structure</edomv>
<edomvd>permanent structures (houses, swimming pools, etc) are within the shoreline buffer</edomvd>
<edomvds>Shoreline Management Model, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>permanent structures (permanent structure) are present or absent</udom>
</attrdomv>
<attalias Sync="TRUE">PermStruc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">cntyName</attrlabl>
<attalias Sync="TRUE">cntyName</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Virginia county or city name.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">FetchUpdat</attrlabl>
<attalias Sync="TRUE">FetchUpdat</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Fetch calculation based on the most common fetch classification within a 100 meter arc segment. (Original fetch was calulated every 25 meters.)</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PrevExpo</attrlabl>
<attalias Sync="TRUE">PrevExpo</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Fetch calculation based on one point within a 100 meter arc segment.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl>bnk_height</attrlabl>
<attrdef>bank height: 0-5 feet, 5-30 feet, or &gt;30 feet</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<udom>bank height: 0-5 feet, 5-30 feet, or &gt;30 feet</udom>
</attrdomv>
<attalias Sync="TRUE">bnk_height</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">lowBnkStrc</attrlabl>
<attalias Sync="TRUE">lowBnkStrc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Shoreline has a low bank height (0-5 ft) and there is a road or permanent structure present that might impede bank grading.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl>StrucList</attrlabl>
<attrdef>list of shoreline structures present</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<udom>combines the structures listed in the "Structure" and "offshorest" attributes into one attribute list</udom>
</attrdomv>
<attalias Sync="TRUE">StrucList</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</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>County</attrlabl>
<attrdef>Virginia county or city name.</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">County</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>offshorest</attrlabl>
<attrdef>offshore erosion control structure: breakwater, groins, marsh toe revetment.</attrdef>
<attrdefs>author</attrdefs>
<attrdomv>
<edom>
<edomv>Groins</edomv>
<edomvd>Groins are low profile structures that sit perpendicular to the shore. They are generally positioned at, or slightly above, the mean low water line. They can be constructed of rock, timber, or concrete. They are frequently set in a series known as a groinfield, which may extend along a stretch of shoreline for some distance. Unless only a single groin can be detected, this inventory does not delineate individual groins in a groinfield. The groinfield is mapped as one linear feature parallel to the shoreline running along the length of the groin series.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Marsh Toe</edomv>
<edomvd>A marsh toe revetment is a low profile revetment, typically constructed of stone, placed along the eroding edge of an existing tidal marsh.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Breakwater</edomv>
<edomvd>Breakwaters are structures that sit parallel to the shore, and generally occur in a series along the shore. Their purpose is to attenuate and deflect incoming wave energy, protecting the fastland behind the structure. The Shoreline Inventory does not map individual breakwaters. A breakwater “system” is delineated and depicted as a line parallel to the series of breakwaters.</edomvd>
<edomvds>Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS</edomvds>
</edom>
</attrdomv>
<attrdomv>
<udom>list of shoreline protection structures that commonly extend into the water.</udom>
</attrdomv>
<attalias Sync="TRUE">offshorest</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">SMMv5Class</attrlabl>
<attalias Sync="TRUE">SMMv5Class</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Revised SMM v5.1 preferred shoreline BMP classifications</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<edom>
<edomv>Non-Structural Living Shoreline</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>Remove existing shoreline structure if present; grade bank if necessary and install a non-structural living shoreline which may include riparian buffer planting along the bank, and/or marsh plants, coir logs, or oyster reefs along the shoreline. Best choice for low energy environments.</edomvd>
</edom>
<edom>
<edomv>Plant Marsh with Sill</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>In moderate energy environments a sill may be required to establish a living shoreline. Remove any existing shoreline structure if present and grade the bank if possible. Stabilize bank with riparian vegetation and plant a marsh with a sill. If the bank cannot be graded, repair existing shoreline structure with a minimal footprint and consider incorporating a marsh with a sill or some other shoreline enhancement (e.g. oyster castles).</edomvd>
</edom>
<edom>
<edomv>Groin Field with Beach Nourishment</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>Maintain existing wide beach between groins. Remove unnecessary structures at the backshore (e.g. bulkheads) and stabilize the bank with grading and riparian plants. Repair/replace existing groins, add beach nourishment and plant beach vegetation.</edomvd>
</edom>
<edom>
<edomv>Maintain Beach or Offshore Breakwater with Beach Nourishment</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>If shoreline exceeds 200 feet in length, remove existing shoreline structure, add beach nourishment sand, consider offshore breakwaters or another type of wave attenuation device with beach nourishment; consider adding plantings to the nourished areas. When the shoreline length is less than 200 feet an offshore breakwater may not be practical. In this case, remove failed shoreline structures and repair or construct a revetment 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>
</edom>
<edom>
<edomv>Revetment</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>Remove existing failing or failed shoreline structure, if present. 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. A bulkhead should be considered only if previously present and the site is limited by navigation. 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. In high energy settings where shoreline extends more than 200 feet see option for Offshore Breakwater with Beach Nourishment.</edomvd>
</edom>
<edom>
<edomv>Revetment/Bulkhead Toe Revetment</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>If grading is possible, remove the failed bulkhead and replace with a revetment landward of the current bulkhead. When grading not possible, (re)construct bulkhead in the same alignment and/or 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>
</edom>
<edom>
<edomv>Highly Modified Area</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>Management options for this shoreline 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.</edomvd>
</edom>
<edom>
<edomv>Ecological Conflicts</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>Management options for this shoreline may be limited by the presence of Submerged Aquatic Vegetation (SAV) or Mangroves (Florida and Gulf coast shorelines). For Virginia shorelines, seek advice from the Virginia Marine Resources Commission Habitat Management Division http://www.mrc.virginia.gov/. If you live in another state, seek advice from your local marine regulatory agency.</edomvd>
</edom>
<edom>
<edomv>Special Geomorphic Feature</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>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.</edomvd>
</edom>
<edom>
<edomv>No Action Needed</edomv>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
<edomvd>No specific management actions are suitable for shoreline protection, e.g. boat ramps, undeveloped marsh, and barrier islands.</edomvd>
</edom>
<edom>
<edomv>Land Use Management. Seek expert advice</edomv>
<edomvd>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 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.</edomvd>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SMMv5Def</attrlabl>
<attalias Sync="TRUE">SMM_v5_Definition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Definitions for the preferred shoreline BMPs listed in the SMMv5Class field.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">DefDate</attrlabl>
<attalias Sync="TRUE">Definition Date</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Date of SMMv5Def update</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
<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>
</attr>
</detailed>
</eainfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="26918"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.11(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Suitable_Living_Shoreline_Areas">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Suitable_Living_Shoreline_Areas">
<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">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<mdDateSt Sync="TRUE">20230920</mdDateSt>
</metadata>
