<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<CreaDate>20230920</CreaDate>
<CreaTime>16080900</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20230424</SyncDate>
<SyncTime>14382700</SyncTime>
<ModDate>20230424</ModDate>
<ModTime>14382700</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">SMM_040623_diss_wm</itemName>
<itemSize Sync="TRUE">0.000</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">365619.233900</westBL>
<eastBL Sync="TRUE">389607.144800</eastBL>
<southBL Sync="TRUE">4125363.789500</southBL>
<northBL Sync="TRUE">4148416.990000</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>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</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;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>
</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
gAooooAKKKKACiiigAoqC9uGtLGe5SIzNFGz+Wp5bAzge9C3UMtiLtJUWFovNEj8KFIzk+2KfK7X
AkSVJGkVWy0bbXHocA/yIp9Z2hrnR7a4ZXE1zEk0pkOWLlRnP04H4Vo05KzsAUUUVIBRRRQAUUUU
AFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQBzeq3uuW00WYraOHfuSVJch3KsFhYMBjL
EYfIGccCq+k+DtJe0huJJJbpGRfLCzyrF5IQKsZTdhlwBkEYJ7DpTpdRudUv3iez+xDTTI8zXSAJ
nBEbLJnBRhvDALnB5K8btnQlZdEtQ6zqdnCzjDqM8AjJ7Y6kn15zXXKUqcNNH5E7svu6xozuwVFB
LMxwAPU0qsGUMpBBGQR3rB8XxJNopG4+akiSpHvwH2urHKkgMoxkg9hVyw1u3u9M0+9mH2UagQLd
JWBLbgWQHHAJUZx+HWsPZvkUkO+pdu1neznW1cJcGNvKYjIDY4z+NYk/i2208INWsb7T5GXdiSMS
LjODh4yy8dcZzgZxXQ1y3iXWnjkn0uMW+2WJR5rTgbXLAFHXIIyHTB/2ie3N0YqcuVq/4AzT0PU3
1YX1xtb7Ot08UDcFXRPl3Ke4LBjn3xzjNa1U9O02HTIGhgeVkZy+JHLbSeyjoo9hgVYmnitoXmnk
SOJBlnc4AH1rOdnL3dgRJRSKwdAwzgjIyCD+RpagYUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAhZV
KgsAWOACep6/0NY3ibxNp3hfTDdX04R3DLBHsZjI4UnGFBOOOT0FaOoWlpe2UkN9bJcW5BLRvHvz
9B6/TmuJsU+HOk6j5kN7ZpMLZrcRXF0zqIyQGQK5IB4UbRyBjjFdFCnCWsk3bol+vT7hNnbWGoWm
qWaXdjcRz2752yIcg460t1IhjkhF2LeXYWDAruQf3sHt9eK5vwibOwjNtbFFgnVGUq4KeaqKrhe3
PytkZ3Esc5zWtqelaV4osUhudlzbxzBwY3/iU9Mj8jSnCMKltbBfQxtHuRrF7eW2pXthfxlRFG9t
CyCTBLc5JG5cZGCcZyOhNaF1L4ot9OZba3sLq+3fKxJSPbtPXnIbODxkHp8ucjUXStPSCKBbK3EU
P+rTyxheNuQPXHGfSue0dNUvNX1CSB7jTtKiHkW8ToDuZTjcFYttUEMMDbkbcAYydOaM25LZd/8A
gdxE11A2pSINbhktrm0uxNZTWSPIAuBtJbaVzkspBHYHGCK57+wZZNc06W2mmtZctaNvg8ry0T5j
5BKZAZGf5jk/w7ga6yx1PURq7afqNvbqJC7W08UmPORVTLbMnAy+PvZ46d6Z4qM0NlBd2txbW13C
7GKe6UmJAY23FsdPlB59QPWrp1JRkorr81/XcGjeri9cF1pfiI3qCCKCdY/KnKKoSfdtAc4AIYPt
yW3fMdoGCT2gzjnrUF1Bbzxq1zbpOIWEyBow5V16Mo/vDsRzXNSqcktVdDaucxHfanf+KNKuWu4b
PS5Ld/KiUiUXbnachlJUDb0J5OTwe0c10PE3i+0tbadLjRrSEXE6qpw824GPJ6EDAI4659DilDf6
dqen6nd2ERisr0qDFcNtD3D4MjMucfIoBIBHR85GCOr0HT7TTdPNvaSpKiyyAyKiqSQ5yp2gD5Tl
eAAMYwMV1VGqavazWi/rv/XkktTUooorgKIWu7dHZDKhdCisoOSpY4XIHIyapajrK2kj21tA95er
GX8mPOF4yN7YIQHBxnr2BqpdeGk1a6NzqlxOwIZBbwuEQIc4G5QHzjBOGAJA9BVO90C002O4u3uw
8jnzI5r+UMRMAFVckYKsBgjr6dsdEIUrpN3YtTW8OahNqnh+zvriEwyzJuaMtuK8kYJwMn1OBWpW
T4f1G31S0nuLbJjNw3z4xuyAwP5MB9Qe9a1ZVVab0sC2CiiioGFFFFABRRRQAUUUUAFRtBE+d8SN
uOTlQcnGP5cfSpKKAMW+0t0TybG2jkgmDC4gmnKRkBCFwQGZTnaBjoB7Cs+DVf8Aic/YIx/ZtxL8
vkS2+VdkyN6tuG5CFA4XOMdCa2Y9aspddl0dHJu4oRM3TbjOMZz1GQSOwYeoqDVrNNTv7SzlgUxD
9+0u8g4UjKYHUNkA54Izx0rpjJ7TXT+vUXoWdLnna2EF7LG95EzJIyLtD4x8wH0K/iauSq7wusbB
XKkKxBIB9eCD+orPv9NabUrO/gSMy25ckGRo95IwMlRzjnggjnpUGrw6/e6bPBp8trYXLcRz+YZc
Dv8AKUHPpzwcHnoc+VSaadr/AIAYPg7TNW0bWJ7TVjJMjrK9k7S+YIlBj3gE8gNuTC/w7GGTnJ3/
ABXpi6t4avLYxpI6qJo0eISBmQhgpU8EHGCO4JFQR3E8viOxvT5cdpcWTxskrMHjlDAlRztz1DDA
PydSAcdBWlWrL2iqdRJaWKVtd2CLa2lvLAA8O6GOLG3y12r8uOABuUfjVmeCO5gkgmRXjkUqysoY
EfQ8GuevvCcRvJL7TnEU8ksUksbk7ZPLfeqhuSgLYJwD0Axiq2i3d7pN/fL4i1RmYNbQQAj90xZd
oKcZLMwOcnrngDGV7OMlzQlr26jv3Kdppy6Vq0+iT280+h3RCh54kBe4ZRkpgjgBeSqAAnI6E1JZ
R6zoevW2lQl72xQARpDAkEcKE/NJKy5y3JAUAZwWPcifWrW21bxno6eZ5/2aVzLE0MRWNkVXH7wj
zFbLIcA4YDBwM067019V8WTIkuowQQ7DPLb3TRqXAQqhAA4K7gdrE88gDbnp57r3uqu/yv6+hJ1t
FAGBimTO8cEjxxGV1UlY1IBc44AJ459684sJJY4tvmSIm5gq7jjJPQD3rgfEWtSX8v2O6lSyhsLu
M6hFtMhmUfOPKI5xtwW3KByAOuaNU1jTvEU1qlyhWwng2SW9xEonhkfBRkODyQcbQx3AjA/vU9Y1
jUtL8PPczXG/UQsTWU0E6SSFmbLxMq/eUBR6g5PPevRoYdxkm1q/6/4ftuQ2d/YX32m4vrYwiI2c
wiC7s5XYrBsds7uOvT1yBerhPhNDPH4SnlupWkuZ72R5d0jOVYKiYJbnI29D0ru65MRTVOq4LoUn
dBRRRWIwooooAKKKKACiiigAooooA4PxNemw8ZWF9HdWMk0SFBC2A0Uf8bud3Aw2AcAAkZPNWtJ1
ePUteutXGnbpYLUQO0MpcxxFyw4wA5br8ucbOC24A9LHpemQSzeVZWsctyfMlKRKGlIP3j3OCevv
VnyIwkioojMhJZkGCSRjP19663XhyKNtbWuTYpaxrVto2iy6rMry28YVj5QySpIGR9Ac/QVfjkSa
JJY2DI6hlYdwehrjvEvhlbbw/atpVqZpNOCD7PtJa6jwEZXcfOSVycjOcchq07m7j8LWsl5cpHFp
e3zJgkgxbyEgEIDjcrE8ADOc4BLYEOlBwXI7tt/p/X4Dv3Lt9o6XUdxHG6xx3Kss0bJvVicYYDOA
wx19+c4GNOkUhlBGcEZ5GKWsXJtWYwrP1LRrPU13SRRrcBkZJ/KRnUo25fvA8Zz+Z6VoUUoycXdA
ZGk6J9guZb66nS61CaNY5LgQiPcF74ycE8ZxgHavHFZ3hiylj1zXL9rZEgupVMUhxvfqT09CccnO
VIIAxXUVzHiq6vdF02a6st2yWWLJXcfJcyLk4UMdrDIOAeecHccb05yqNw6yshPQbrulaxBqc+q6
JeJF59v5VxDIrsNw6SqAG+fAC8LzgZzjjEg8T6/aaa7XMM8t+Jt8aTWrRxSRrEilXYL+7YsS4454
AHzAV18mv2EGmR3k03zSQiVIQpWWXPQLG2GJJ4Ax3FYcOmWXinTbbWNKil0qa4uPOkuNmyZ0/iAI
P8W0AHkY5Fb0p+7+9jotL2/DuJ+QzVfEGlX2k3ltHpaXe9il9bzYhwnlFncntgApkkYbjI4zk67p
2j+IdAitdMgkjlub+BbsQxLK0LuEY7yT0UBT8hxkDqAa2L3WjY+LLXw2mLyC7gKvHcumEPJIOQC5
Zc92J2secHPR2+j2dteSXSRLvJUxrtG2LCBPkHb5RgnrjjoAKftPY2kk11Wv9f13Fa4aPpFpoemx
2NlEscSksdqgbmJyTx7mr9FFcEpOTu9ywooopAFFFFABRRRQAUUUUAFQ3U0kFrJLFbyXEirlYoyo
Zz6AsQP1qaihAcO58VQzDVpbK1VLOOdF8+bdM8TEHDhAF4KK2Qc4GME9er0nUV1SwW5AVW3NHIik
nY6sVZckDOCMZxj04qLWYdTubMLo99Ha3SSqS0iB0K/xBhgnocjBHOOcVyeh6imiQ3yXKwQ3UzRw
WbMTvmkWPYUbP91lyTwMMGOM5rs5fbU7pK67f18ydmdNq/iTT9HJ8+QHy5YEuMEDyVlYqjtngDcO
ckYGT9b7TWd3LNYmWGWRUVpYQwLKrZ2kjqAcHB9q5DTvC9prI+16811JeXSHdbzSlVKh95CDO4IG
fjPK5x0xUGnWutabr5vU069lRoFSdUeJBKyF1XjAGFVtvG3dtRuRTdGnZqMtV/X+f4BdieJNTuPA
2lW0dteNdWdo1uTAXX7RHCu4Nkn76tsI6ZBzjPGOs8P69a+JNHi1OzjnjglJCiZQrHHfgmubhktt
W8VxX32Dz/tNmtvNH9neOa0P3iWYqOOSM7gQQQozursrS0hsbSK1t1KxRLtQMxYgfU8n8aWIcVBR
a97e4LcmooorjKCiiigDz6/8Of2Qtjomj2Vxchwzie4vZUAXzFeSPcinYrABScYOQOea7iwgt7W0
W3toLe3WP70MAAVGPzEYHTls/jnvSXtq9wIZIZBHPDJvRiuQeCCp9iCfocHtXKRpP4d8Rapq1/58
VlMqSsLcNOjcuCXbYNoQHP0IAztwetydeNm9V+LuTsJqXiGY3kipp0Vxcx6lFDZlnCfuyVViSefv
hhwDjch9DXbVw+lC+See60y2gsLd5ZPtdsx81kug3Cj5sDeZMsQB0OOoY9xU4hRVkhoKKKK5hhRR
RQAUUUUAFFFFABRRRQAUUUUAcOvhu51jVLtLiXVbPTAUZ4biVHNzJtZGPBPyhdowSdx6jgE6Vx4a
aK6gTTtXmsLZnDTxLtZ5MDACMwJTIJBI5xgAgAY6SRBJGyMWAYYO1ip/AjkV5xq/wysra4k1WzvI
lSNldo9SXzooIlYs20n5hjkjkck888d1Kr7R2nLl7aXRLVipcJqdn4xttLtIriGyjEcUWoS2AaWW
43HLF8qXULuJIyMZyCDmu0m8S2WkmKyur03t4rES+VGAwARpC20cHCgEgZOCOORnBg1O6jsY7jSd
B04TwWjSTlABInMigoBnIbyWx8xyWXkjJpfBmhy22i3GqXti7am8rSJBLbmEoy5C8End7Mcn5mwf
mIraqoyjep006Xb8xLyN/wD4TTw5/Zkuorq0D28RIbZkv97b9wDceSO3fPSsC4+JPl6o0cOjzy6d
GgeS53jIGSGIAyMqR90kE845GDvnQotN0WVLOCWe+MLRmeNkjmkLMXY7zgLl2ZuOhORzXl+majaD
W5ZvEER1OEf6NeTX8XzxiFWLOYQTgcjDMpY8j5c4pYehRmpNJu3nr+n9dAbaPa4ZkuII5om3RyKH
U4xkEZFPrO0bWINbsWurcFVWV48E88Hg+2V2tjrhhWjXnSi4tplhRRRUgFNdFkRkdQyMCGVhkEeh
p1FAGDLH5Wstp0KpHFOYLlQFAx5Z+fA9AI4V9t455AreppjjaVZSimRQQrEcgHGQD74H5U6rlLms
AUUUVABRRRQAUUUUAFFFFABRRRQAUUUUAMmkaKF3WJ5SoyETG5vYZIH61y2o6d4j19X3SxaTCofy
o1dnkkyMBZCrBQOhIGemASOvWUVpTqOGqWomrnF3GmXfhbWYtT03yZbO5a2tb1Z3JmfLldyADAI3
7to68gAcV2lFFFSo52vuCViC8tVvLZ4Glni3D78EhRh9CK5HWNNs9L8P3dtBY3EqxXLXbzEDLTZ8
wM0j7jwMDcQRwFJAzjoPEOjHXdJexEscO8nMjIzMoKkZUqylW5656ZBBBrJP/CS21pa2V1a2+ous
A8ySFfvOu3DFpGABz82MN90+1bUHZK0uu2wmcT8M9VNnrdzbvCwfUrkNLNMZZHyEkZlZ2RQGVyox
yfm753V7AGBJAIJBwfauD0DR9ZgtLJdOkFlbTD7S83lbfnYJ5gkiYAsxIO04GBkkk4B6iz0ZdMnu
pbEQLJduZbiaSIb3fnBO3AI59u/JzWuNlCpUck/68+wRukatFQ2trDZWsVtbqViiUKgLFiAPc8n6
mpq4H5FBRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQ
AUUUUAFFFFABRRRQAUUUUAFFFFAH/9k=</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/portals/index.php</linkage>
</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 - Mobjack Bay, Virginia</resTitle>
<date>
<pubDate>2018-11-30T00:00:00</pubDate>
<reviseDate>2023-04-06T00: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;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN&gt;Mobjack Bay has been pulled out from the original SMM v5.1 run in 2019 and rerun to provide reccommendations in areas previously classified as 'Ecological Conflicts'. Original classification is still provided.&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>Marcia Berman</rpIndName>
<rpOrgName>Virginia Institute of Marine Science</rpOrgName>
<rpPosName>Director Comprehensive Coastal Inventory Program</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(804) 684-7188</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 1346</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<country>US</country>
<eMailAdd>marcia@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, 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>Gloucester</keyword>
<keyword>Mathews</keyword>
<keyword>Mobjack Bay</keyword>
<keyword>geoscientificInformation</keyword>
<keyword>biota</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&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>
<idCredit>Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science (VIMS),</idCredit>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.0.41833</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-76.519719</westBL>
<eastBL Sync="TRUE">-76.245065</eastBL>
<northBL Sync="TRUE">37.476058</northBL>
<southBL Sync="TRUE">37.265155</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<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 type="DQConcConsis">
<measDesc>Topology has been checked. There are no overlapping arcs. All arcs are greater than 1m in length.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>All 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>
</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>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>
</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 has been collected during the summer since 2009.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2009-06-01</tmBegin>
<tmEnd>2018-08-16</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 http://web.vims.edu/bio/sav/gis_data.html</srcDesc>
<srcCitatn>
<resTitle>SAV Habitat 10 Years (2007-2016)</resTitle>
<resAltTitle>SAV Habitat 10 Years (2007-2016)</resAltTitle>
</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: http://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 2018.</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 present.</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 present.</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 present.</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</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 present.</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 has been restructured to provide clear and concise recommendations across defended and undefended shorelines. There are now 11 classifications: 1. Non-Structural Living Shoreline (was Maintain/Enhance/Create Marsh, Option 1, and uplandBMPs Land Use Management, Maintain/Enhance/Restore Riparian Buffer).
2. Plant Marsh with Sill (was Plant Marsh with Sill, Option 2 and 5)
3. Groin Field with Beach Nourishment (was Groin Field with Beach Nourishment, and Option 6)
4. Maintain Beach or Offshore Breakwater with Beach Nourishment (wasMaintain Beach or Offshore Breakwater with Beach Nourishment, Options B8, B9, R7, and R8)
5. Revetment (was Revetment, Options R0, R3, R4, and B0)
6. Revetment/Bulkhead Toe Revetment (was Options B3, B4, and B7)
7. Highly Modified Area (no change)
8. Ecological Conflicts (no change)
9. Special Geomorphic Feature (no change)
10. No Action Needed (no change)
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 present.</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 present.</stepDesc>
<stepDateTm>2019-10-08T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Mobjack Bay area was extracted from 'SMM_v5_1_Preferred_BMPs_Virginia_Final_utm18_Feb_2_2022' for use in the NOAA Oyster Structures SMM Upgrade project (2023). It was reprocessed to add shoreline recommendations for all areas coded as 'Ecological Conflict'. New feilds were added to hold the original classification, updated classification, and final classification. The updated classification gives recommendations for areas previously classified as 'Ecological Conflict', 'Highly Modified Area', and 'Special Geomorphic Feature'. The final classification keeps the later two classifications and only updates the 'Ecological Conflicts' with new coding.</stepDesc>
<stepDateTm>2023-04-06T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<eainfo>
<detailed Name="SMM_040623_diss_wm">
<enttyp>
<enttypl Sync="TRUE">SMM_040623_diss_wm</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 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">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>
<attr>
<attrlabl Sync="TRUE">SMMv51ClsF</attrlabl>
<attalias Sync="TRUE">SMMv51ClsF</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Final revised SMM v5.1 preferred shoreline BMP classifications where shoreline previously classified as 'Ecological Conflict' are now given preferred shoreline BMP recommendations.</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<edom>
<edomv>Non-Structural Living Shoreline</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Plant Marsh with Sill</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Groin Field with Beach Nourishment</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Maintain Beach or Offshore Breakwater with Beach Nourishment</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Revetment</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Revetment/Bulkhead Toe Revetment</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Highly Modified Area</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>Special Geomorphic Feature</edomv>
<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>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</edom>
<edom>
<edomv>No Action Needed</edomv>
<edomvd>No specific management actions are suitable for shoreline protection, e.g. boat ramps, undeveloped marsh, and barrier islands.</edomvd>
<edomvds>Shoreline Management Model v5.1 Glossary</edomvds>
</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>
</detailed>
</eainfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<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>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="SMM_040623_diss_wm">
<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="SMM_040623_diss_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">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<mdDateSt Sync="TRUE">20230424</mdDateSt>
</metadata>
