<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20221005</CreaDate>
<CreaTime>12153000</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Maryland_Year3_5Counties_SSM_Combined_Oct_5_2022_wm</itemName>
<itemSize Sync="TRUE">1.928</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">-8533275.798800</westBL>
<eastBL Sync="TRUE">-8415198.730900</eastBL>
<southBL Sync="TRUE">4611615.541000</southBL>
<northBL Sync="TRUE">4781038.227500</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.6'&gt;&lt;WKT&gt;PROJCS[&amp;quot;WGS_1984_Web_Mercator_Auxiliary_Sphere&amp;quot;,GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Mercator_Auxiliary_Sphere&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,0.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,0.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,0.0],PARAMETER[&amp;quot;Auxiliary_Sphere_Type&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,3857]]&lt;/WKT&gt;&lt;XOrigin&gt;-20037700&lt;/XOrigin&gt;&lt;YOrigin&gt;-30241100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102100&lt;/WKID&gt;&lt;LatestWKID&gt;3857&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</projcsn>
</coordRef>
</DataProperties>
<SyncDate>20221208</SyncDate>
<SyncTime>14245300</SyncTime>
<ModDate>20221208</ModDate>
<ModTime>14245300</ModTime>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<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
gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA
CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK
KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooqOaeK2iaWaRY0UZJ
Y4/z1FG4ElFZ2hI66TC0tqbeZhlwxy7n+83uevPPPPPFaNOSs2gCiiikAUUUUAFFFFABRRRQAUUU
UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAVr+8TT9PuLt0eQQxl/LTG5yBwq57k8AepFcvD4c1LW
9YbU9auHt7UqjQWVvIY5UI5xJIhB4yRtBIJJPtXRai0q3WmbFBQ3WJMtgBfKkx+u2qPifxRZ+GbF
JZ8yTyuEihQbm5zlioy20AEnAJwOATXRRc1aNNasTt1NxQFUAZwBjk5pa4u/8Tf2xaRxWMdxDFJe
HbdBTg28DRtLJkcrySoB646c4rtAQRkHINZzpSglzdQTuFQXd0lnD50qv5QPzuoyIx/ePt9M4znp
kies3X9On1XQruytrtrWaWMqkoXdg47juPapgk5JS2GaVFUNF1B9T0i3uZojDclALiBgQYpQPmU5
9D37jBHBFX6UouLswCiiikAUUUUAFFFFABRRRQAUUUUAFFFUb7WNP0ywa+u7lY7VZBG0uCyq27Zg
46fNxk9DTUXJ2SAvUVnaRrum69A8+mXInjQrltjL95Qw+8BkEMDmtGiUXF2krMAooopAFFFFAFW/
gkmijaEAywyrIoZsA4PI/wC+ScZ74Pas28tzrFrc2kNtPa/bIxHdXDrsdVxgqvctgkAj5RkkE9Du
UVcZuIrFWz0+CyMjR7mkkOWkc5Y+2fTqfqSepJrnbyx1S+09ItIv/s+oaZdPD+9yEkiK8I2OT8jR
kH+8oNdZXP8AiTRbm6hN9oqWsGtx4Ed1IgJ2fxKfXjIGSMZ6itKM/f1f3/r5Ax0PiMQ3H2PUoJYr
kyGOPyomcSEAEjC7tpwynkkYPXhgu9XA22rrB4kuZ5Y2tltdsk6zRnMSS7RL94DA3hGypIwH64q7
rnjGLQ/G2n2E9xB9hmgZbn58tA/BVmGPlBHHJ5yTxt+bWeGlKSUFra/6iudBd6fJ5zXmnyrBeEAP
vUtHKozwy5HPJ+Ycj3HFV9I8Q2+o311pcrwJqlnj7RBFLvAB6MDgHB9CAfwwTJouuR6ybxUhKfZp
fLMgcPHKCMqyMOoII7DnjnGaqatoEj6zBr+lsqapEqwyrI5CXMAJJjJ528nIYDqOeKzSV3Cpo+n/
AAfIfmjoKKw7C81yTxDcW13Hp4so4g37kyGRGJ4BLABgeegGNvvgblYzg4uzGFFFFSAUUVFcXMFp
A01xKkUSkAs5wMk4A+pJAHuaEr6ICWiqVhqIvgd1rc2z7Q6pcKAWU9CME/l1HGQM1dptNOzAKKKK
QBXlHjfTm0i/jtxrmoCx1eRo7mGSJZ1i8wkB0XaAqglicAsc9QTur1SSVIl3OwA6DJ6n0FcPZ+I3
8W3c+nw2gktPOMa3Do0bRfISxKnncmQmRxuYHIxiuzBuUJOaWi3/AKZMuxteE44Ggv763mE8Vzc7
UlUEBhEiwnA9N0bHjg5yOK6GobS0gsbOG0toxHBCgSNB/CoGAKmrmqS5pNoaCiiioGFFFFABRRRQ
AUUUUAVr7T7TU7SS1vIFmhkGGU9/xHIrnrLwHplvJM1xJdXbNJuieaclkTbwgxgBQTIQAP4z611V
FaQrTgrRdhWRivp+pabbs2lXEc+0Li0uUVEIBJIVkA2E56kMOBx1NUZPE6alo82oaPdxRPaSlZor
2MosgX74G7afUBumc59uorgda+HVrPryava+fM1xcot5AzoE8nzFZsAjkZBypPIYjsBW9B05v967
P+tGJ36HQ2eqpdw22tIpjgmRYbiN2UmI5+RiQT/e6ejg8YxW7Xld1YeJtHtta0HTdOt44boK2lCB
QBIRInmmRsdWViSHPIDAcAmvSdKXZpFmvntPiFP3rAAvwOcCliKUYpSi9Ht6f1p8vIEy3RRXK+MP
GC+F7jR4SsQF9eJDJLMSFjj3DcQP4mweg6dT6HCnTlUlyR3G3Y09W8R2Wk3MVrJvkuZcbY0wNoJI
DMSQFUkEZPfjqRXFxadqfiHxTbeIoZHsLcxFSJ7uNpoAQpAUbHVTtLEqOfmBLA8LqeKPh9D4u8U2
t5qcobS4rby3gQsjyNvDbSwP3ePqOcdQRxstnpsuoanZ6Xq1xaaXo2Fv9Quld1aTYYFjRUKr8igL
nbk89ed3pYaFLkvB+9bXS6V9Lf0iJXvqeqQ6nFBfW+km5a9vcnz2VP8AVDaWBfaNqZ+UAHBOeM4N
atcj4Pi0eeJJLC8tdQECAxytZiOeMMT1OAcEhsDaD7muqmnhtoWmnlSKJfvO7BQPqTXBWgoz5V/X
yLQTTJbwvLJkIgyxAzgetVLfU0vNTkt7UrLDDHmWZOVDnGEB6ZxyR1GV9ea07Xet28kdhdS2NsQV
F0sYMkmQeY933QDj5iOcHGOGqdn0zw1o8aARWllAAkaA457AZ6kn8+SaSikrby7AZev6dBrms2Wl
3CSPblDPcqJ5FV0VgVUoPlbLYOeo2kdGqfwz4XtfDdq0UJ3uXkIPO1FZy21VJO3qM46kAnoMHhq7
/teG41hoZoxcyfuFn27kh2rgAAnAJBbrkk59AN6rqVJxj7G+nX1BLqFFFFc4wooooAKKKKACiiig
AooooAKKKKACiiigCjqulW+sWf2a5MigOJEkifa6MOhB7dx7gkd6fpll/ZulWlj5zzC3iWISPjcw
UYBOO/FW6Krnly8vQAri/iJ4r/4RjT7QjSotRaVmkKSsuESPDOwB+8wBJAHoT2rtK5Lxz4Cs/HUN
jFe3c0CWjuw8oA7twA5z9K2wrpKtF1vh6ile2hv6PqtvreiWeq2wdYLqFZkEgwygjOD7ivJNE0aw
8d3lxJY6NpWn2EF9cD7ah8+a5dWBydxDbCJD9CVxjAr1K5s49O8ITWSQyXMdvYNEIo8q0oWPGBtw
QTjtzzxXmngjwzruu2//ABObC70bSRcSXKxLdkSTiTA8rGN4j4YsWbcSUI6ZHZhXGEKlSLtrpr69
L6smXRHc6L4gt71tOtdLjtbWzmguBEoQgI8bKAgTC9iSQPTj1pPD8cd3KW1yIya7ZFUmkmjXaCFB
BjZQAV/eA+oLcgHgFv8ADzw9Z3M9zawXENzMWPni5dpE3KVbDMSeQT1z7YwMdDY2a2VsIg5kkJ3S
yt1kc9WP19Og6DgVzVKlJJ+zvr9/36jSfUlnlaGIusTykEDamM4JAJ59Bz+HFY/iTSbzWVs7a2lh
t40lMss8kQlwNpUqFPB3BmBz0BPXpW5RXPCbg+ZblENraw2kIihXA6sx+857sx7k9yeTU1FFS3fV
gFFFFIAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA
KKKKAP/Z</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>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">Maryland Living Shoreline Suitability Model (LSSM)</resTitle>
<date>
<createDate>2021-06-26T00:00:00</createDate>
<pubDate>2022-02-28T00:00:00</pubDate>
</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. 2022. Maryland Shoreline Stabilization Model. Center for Coastal Resources Management, Virginia Institute of Marine Science, College of William and Mary, Gloucester Point, Virginia.</otherCitDet>
<citRespParty>
<rpIndName>Tammy K. Roberson</rpIndName>
<rpOrgName>Maryland Department of the Environment</rpOrgName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>1800 Washington Boulevard</delPoint>
<city>Baltimore</city>
<adminArea>Maryland</adminArea>
<postCode>21230</postCode>
<eMailAdd>tammy.roberson@maryland.gov</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>410-537-3522</voiceNum>
</cntPhone>
</rpCntInfo>
</citRespParty>
</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;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;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&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 height, marsh presence, beach presence, and permanent structures within the riparian zone. Also included are 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;/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;Data presented here has been developed for the Maryland Department of the Environment (MDE) utilizing the Virginia SMM with adaptations to reflect conditions and policies in Maryland. This includes the addition of buffered habitat areas for rare, threatened, and endangered (RTE) species, and federal navigation chanels, and modification to the output recommendations and definitions.&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;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>To provide a recommended preferred approach for shoreline erosion control via a geospatial Shoreline Stabilization Model that identifies where living shorelines are suitable.</idPurp>
<idStatus>
<ProgCd value="004"/>
</idStatus>
<resMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Maryland, Chesapeake Bay, Charles County, Somerset County, St Mary's County, Worcester County</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>Maryland Shoreline Stabilization Model, Shoreline Management Model, Preferred Shoreline Best Management Practices, Living Shoreline Suitability Model, Living Shorelines, Shoreline Conditions, Shoreline Structures, Riparian Land Use, Shoreline Inventory, Erosion Control, Shoreline Treatments</keyword>
</themeKeys>
<searchKeys>
<keyword>environment</keyword>
<keyword>Shoreline Stabilization</keyword>
<keyword>Shoreline Management Model</keyword>
<keyword>Living Shoreline Suitability 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>Maryland</keyword>
<keyword>Chesapeake Bay</keyword>
<keyword>Charles County</keyword>
<keyword>Somerset County</keyword>
<keyword>St Mary's County</keyword>
<keyword>Worcester County</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 STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&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;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:7 0 7 0;"&gt;&lt;SPAN&gt;The Center for Coastal Resources Management (CCRM) at VIMS performs a service by distributing data generated by either CCRM or public agencies, which offer data without restriction or charge. CCRM assumes no responsibility for data accuracy or precision, metadata completeness or correctness for digital information. CCRM assumes no liability for misuse of any data which may arise as a result of any alteration, conversion, or combination with other data sources. As well, the timeliness and scale of these products must be considered when evaluating appropriate use. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;Maryland Department of the Environment (MDE) disclaimer&lt;/SPAN&gt;&lt;SPAN&gt;: The Mapping Services provided herein are for reference only. The user of this information understands and acknowledges that the map data may be inaccurate or contain errors or omissions, and the user assumes the full responsibility for any risks or damages resulting from any use of or reliance upon this data. Maryland Department of the Environment (MDE) and its Agents or Affiliates do not guarantee the accuracy or reliability of the data generated from this service.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Use of the mapping tool is strongly encouraged for preliminary planning purposes, however, its use does not guarantee the approval of any authorization or shoreline project. Please contact the MDE Tidal Wetlands Division at (410) 537-3837 for coordination on specific projects.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;This project has been funded wholly or in part by the United States Environmental Protection Agency under assistance agreements. The contents of this document do not necessarily reflect the views and policies of the Environmental Protection Agency, nor does the EPA endorse trade names or recommend the use of commercial products mentioned in this document.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P&gt;&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>
<exDesc>ground condition and currentness of associated datasets.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2016-10-01T00:00:00</tmBegin>
<tmEnd>2018-10-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idCredit>This project has been funded wholly or in part by the United States Environmental Protection Agency under assistance agreement CD-963623-01-1 to the Maryland Department of the Environment.
These data have been produced by the Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science (VIMS) for Maryland Department of the Environment (MDE).</idCredit>
<idPoC>
<rpIndName>Karinna Nunez</rpIndName>
<rpOrgName>Comprehensive Coastal Inventory, Center for Coastal Resources Management, Virginia Insitute of Marine Science (VIMS)</rpOrgName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>1375 Greate Road, P.O. Box 1346</delPoint>
<city>Gloucester Point</city>
<adminArea>Virginia</adminArea>
<postCode>23062</postCode>
<eMailAdd>karinna@vims.edu</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>804-684-7273</voiceNum>
</cntPhone>
</rpCntInfo>
</idPoC>
<idPoC>
<rpIndName>Tammy K. Roberson</rpIndName>
<rpOrgName>Maryland Department of the Environment</rpOrgName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>1800 Washington Boulevard</delPoint>
<city>Baltimore</city>
<adminArea>Maryland</adminArea>
<postCode>21230</postCode>
<eMailAdd>tammy.roberson@maryland.gov</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>410-537-3522</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Tammy K. Roberson</displayName>
</idPoC>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9270</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-76.655721</westBL>
<eastBL Sync="TRUE">-75.595016</eastBL>
<northBL Sync="TRUE">39.413237</northBL>
<southBL Sync="TRUE">38.227511</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 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>All shoreline has a recommended shoreline practice listed in the MSSM_Classification_Final (MSSMClsF) field and a definition listed in the MSSM_Classification_Final_Definition (MSSMClsDef) field. Note that data feeding this model may have different publication dates and may not reflect the actual conditon present on or near the shoreline.</measDesc>
</report>
<dataLineage>
<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>Charles County, Maryland - Shoreline Fetch</resTitle>
<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>
<date>
<createDate>2020-07-31T00:00:00</createDate>
</date>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>The Maryland Shoreline Inventory is produced county by county by the Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. The inventory provides information on bank height, marsh presence, beach presence, riparian land cover, and public boat ramps in addition to the location of shoreline structures such as riprap and bulkhead. The shoreline used to create the Maryland shoreline inventory is used as the base shoreline for the Shoreline Suitability Model</srcDesc>
<srcCitatn>
<resTitle>Charles County, Maryland Shoreline Inventory</resTitle>
<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>
<date>
<createDate>2020-06-08T00:00:00</createDate>
<pubDate>2020-11-27T00:00:00</pubDate>
</date>
<citOnlineRes>
<linkage>https://scholarworks.wm.edu/data/431/</linkage>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>The most recent 5 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 5 Years (2015-2019)</resTitle>
<citOnlineRes>
<linkage>https://www.vims.edu/research/units/programs/sav/reports/index.php</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>Time period of SAV data.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2014-05-20T00:00:00</tmBegin>
<tmEnd>2018-10-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Maryland's Six Inch Imagery is used to locate permanent structures, confirm road location, and identify wide beaches.</srcDesc>
<srcCitatn>
<resTitle>MD_SixInchImagery</resTitle>
<resAltTitle>Maryland Six Inch Imagery</resAltTitle>
<otherCitDet>Six Inch resolution aerial imagery for the State of Maryland. Depending upon when a locatlity was processed, imagery referenced was either flown in 2016 or 2019 for the Eastern Shore, or 2017 or 2020 for the Western Shore.</otherCitDet>
<citOnlineRes>
<linkage>https://geodata.md.gov/imap/rest/services/Imagery/MD_SixInchImagery/MapServer</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>State of Maryland imagery was flown in 2016 (Eastern Shore) and 2017 (Western Shore).</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2016-05-01T00:00:00</tmBegin>
<tmEnd>2017-10-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Roads are obtained from the U.S. Department of Commerce, U.S. Census Bureau, Geography Division. TIGER/Line Shapefile, 2019, Series Information for the All Roads County-based Shapefile for each locality processed is used. This dataset provides the location of roads and rails near the shoreline.</srcDesc>
<srcCitatn>
<resTitle>TIGER/Line Shapefile, {2019}, county, {Anne Arundel}, MD, All Lines County-based Shapefile</resTitle>
<date>
<pubDate>2019-06-01T00:00:00</pubDate>
</date>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<citOnlineRes>
<linkage>https://www.census.gov/geo/maps-data/data/tiger-line.html</linkage>
</citOnlineRes>
<resAltTitle>tl_2019_24003_rds</resAltTitle>
</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>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>USGS CoNED Topobathymetric Model (1859 - 2015)</resTitle>
<date>
<pubDate>2016-05-02T00:00:00</pubDate>
</date>
<citOnlineRes>
<linkage>https://www.fisheries.noaa.gov/inport/item/55321</linkage>
<orFunct>
<OnFunctCd value="002"/>
</orFunct>
</citOnlineRes>
</srcCitatn>
</dataSource>
<statement>A variety of data sets are compiled onto a polyline base shoreline. These attributes are used to determine the shoreline best management practice for erosion control.</statement>
<dataSource type="">
<srcDesc>Channel data was obtained from the U.S Army Corps of Engineers (USACE) Geospatial website's National Channel Framework (NCF) database. Navagation channels are maintained by USACE. Channels within Maryland were extracted from the entire dataset.</srcDesc>
<srcCitatn>
<resTitle>Channel Reach</resTitle>
<otherCitDet>Channel data was downloaded Feb 15, 2021.</otherCitDet>
<citOnlineRes>
<linkage>https://geospatial-usace.opendata.arcgis.com/datasets/9227967a2748410983352b501c0c7b39_2</linkage>
</citOnlineRes>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>The RTE layer was provided as a restricted distribution for use only with the Maryland Living Shoreline Suitability Model. Data was obtained from the Maryland Department of Natural Resources, Wildlife and Heritage Services.</srcDesc>
<srcCitatn>
<resTitle>MDDNR_OtherRTE_MDE_LShoreTool</resTitle>
</srcCitatn>
</dataSource>
<dataSource type="">
<srcDesc>Tiger Beetle Habitat layer was provided as a restricted distribution for use only with the Maryland Living Shoreline Suitability Model. Data was obtained from the U.S. Fish and Wildlife Service, Chesapeake Bay Field Office; Maryland Department of Natural Resources, Wildlife and Heritage Service.</srcDesc>
<srcCitatn>
<resTitle>MDDNR_TBeetle_MDE_LShoreTool</resTitle>
</srcCitatn>
</dataSource>
<prcStep>
<stepDesc>Fetch is determined by creating 16 arcs based on the compass rose, radiating from points evenly spaced every 25 meters along the shoreline. The average arc length over water is calculated for the NE, SE, SW, and NW quadrants. The quadrant with the longest average fetch distance determines the fetch for the associated shoreline arc segment. Fetch is classified as low = 0-0.5 mile, moderate = 0.5-2 miles, and high = &gt; 2 miles. </stepDesc>
<stepDateTm>2020-07-31T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>All processing steps occur in ArcMap, ArcGIS version 10.6. 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, presence of marsh, presence of sand spits, and riparian land cover. All other data layer information is added to this shoreline. Shoreline is delineated along the water edge. The one meter bathymetric contour is used to determine if the nearshore is suitable for marsh planting. If the 1 meter bathymetric contour is within 10 meters of the shoreline then the bathymetry field is coded as 'deep', otherwise it is coded as 'shallow'. Processing date: 2020.</stepDesc>
<stepDateTm>2020-09-24T00: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'.</stepDesc>
<stepDateTm>2020-09-25T00: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". </stepDesc>
<stepDateTm>2020-09-29T00: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.</stepDesc>
<stepDateTm>2020-10-01T00: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. </stepDesc>
<stepDateTm>2020-10-14T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Buffered Tiger Beetle Habitat and Rare, Threatened, and Endangered (RTE) species habitat layers are used to "flag" locations along the shoreline for Ecological Considerations. Federal Channels were buffered 150 feet. Shoreline intersecting the buffer or within 30 feet of the channel buffer are flagged as Highly Modified Areas. </stepDesc>
<stepDateTm>2021-02-17T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The most recent 5 years of SAV data was combined to create an SAV "habitat" layer. Only SAV polygons with density greater than zero were coded as "sav". The polygons were dissolved on the "sav" field to create a general sav habitat layer. The shoreline is coded for SAV presence if SAV is within 30 ft of the shoreline.</stepDesc>
<stepDateTm>2021-05-28T00: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. Maryland Shoreline Management Model 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. Land use, bank height, marsh presence, fetch, beach presence, SAV, nearshore water depth, and existing structures feed into the resulting recommendations. </stepDesc>
<stepDateTm>2021-06-25T00:00:00</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>The shoreline management model outputs for Anne Arundel, Calvert, Dorchester, and Talbot Counties where merged together. Any newly completed Maryland county SMM output will be appended to this file.</stepDesc>
<stepDateTm>2021-07-06T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<eainfo>
<detailed Name="Maryland_Year3_5Counties_SSM_Combined_Oct_5_2022_wm">
<enttyp>
<enttypl Sync="TRUE">Maryland_Year3_5Counties_SSM_Combined_Oct_5_2022_wm</enttypl>
<enttypd>Maryland Shoreline Stabilization Model attributes</enttypd>
<enttypds>Processor</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">31849</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>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>
<edom>
<edomv>no</edomv>
<edomvd>road or permanent structure was not observed 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>Maryland Shoreline Inventory</attrdefs>
<attrdomv>
<edom>
<edomv>Riprap</edomv>
<edomvd> Revetments are sloped structural shoreline stabilization measures comprised of stone, broken concrete, or other similar material. Revetments are typically parallel to the shoreline and designed to prevent erosion and stabilize an embankment. Riprap is also used next to failing bulkheads (bulkhead toe revetments) to fortify the structure. Riprap is mapped as a linear feature along the shoreline. The inventory maps only riprap when this type of structure is co-located with bulkheads.</edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), 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 structural shoreline stabilization measures comprised of a vertical retaining wall composed of wood, stone, concrete, plastic, steel, or other similar material that offer protection from wave attack. Bulkheads are vertical structures built slightly channelward of the problem area and backfilled with suitable fill material. They function like a retaining wall, as they are placed parallel to the shoreline and are designed to retain upland soil, and prevent erosion of the bank from impinging waves. </edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), 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 alternative material has been deliberately placed for shoreline protection. Unconventional features may include unique materials placed in a similar manner as riprap or bulkheads, such as engineered pre-cast concrete products. It may also include unique placement or arrangement of conventional materials like riprap that does not fit other structure definitions. Moreover, segments along the shoreline are coded unconventional when nonconforming materials and rubble are dumped along the shoreline in a haphazard manner with the purpose of stabilizing the shoreline (e.g., tires, bricks, broken concrete rubble, and railroad ties). </edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Wharf</edomv>
<edomvd>Typically describes a shore parallel structure where boats are tied. In this inventory, Wharf is generally associated with large industrial, public or commercial facilities.</edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Not observed</edomv>
<edomvd>Shoreline protection structure not observed.</edomvd>
<edomvds>processor</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>marsh_all</attrlabl>
<attrdef>Tidal Marsh that is found along coasts and estuaries of which the flooding characteristics are determined by the tidal movement of the adjacent estuary, sea or ocean and dominated by dense stands of salt-tolerant plants such as herbs, grasses, or low shrubs.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</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">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Marsh</attrlabl>
<attalias Sync="TRUE">Marsh</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>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">50</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 at least 10 feet of dry sand persistently visible above high tides.</attrdef>
<attrdefs>Shoreline Management Model</attrdefs>
<attrdomv>
<udom>wide beach is present (Yes) or absent (No).</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>canal</attrlabl>
<attrdef>Navigable man-made excavated waterway.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</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 (No)</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>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">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>RiparianLU</attrlabl>
<attrdef> Land Use refers to the predominant condition in the immediate riparian area within 100 feet of the adjacent shoreline. While the actual assessment of land use is defined by a distance, the classification can include best professional judgment; particularly when development or other land use activity is setback on the parcel.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</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">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PublicRamp</attrlabl>
<attrdef>Paved Public Boat Ramp is present.</attrdef>
<attrdefs>processor</attrdefs>
<attalias Sync="TRUE">PublicRamp</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Values are "Yes" if present or "No" if absent.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>bathymetry</attrlabl>
<attrdef>Nearshore water depth. The location of the 1 meter (3.28 feet) bathymetric contour line determines the nearshore water depth. When the 1-meter bathymetric contour is greater than 10 meters (32.8 feet) offshore, nearshore depth is considered “Shallow”, otherwise it is classified as “Deep”. Water depth is used to determine if the nearshore is suitable for marsh planting.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</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">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SAV</attrlabl>
<attrdef>The presence of SAV is noted when SAV has been mapped within 30 feet of the shoreline at least once in the 5-year period (2015 – 2019).</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</attrdefs>
<attalias Sync="TRUE">SAV</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>SAV present (within 30 feet of shoreline) = Yes
SAV absent (within 30 feet of shoreline) = No</udom>
</attrdomv>
</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 Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>Sandspit is present ("Yes") or absent ("No").</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>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 channelward edge of the beach. 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 Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), 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 (No)</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 located close to the shoreline can impede bank grading that may be needed to install a shoreline protection feature. Roads include paved roadways, and parking lots.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>roads are present (roads) or absent (No)</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 located close to the shoreline can impede bank grading that may be needed to install a shoreline protection feature. Permanent structures are upland structures such as houses, swimming pools, or power stanchions.</attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</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 ("Not observed")</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>bnk_height</attrlabl>
<attrdef>Bank height is the height of the bank from the base to the top. Height is estimated from imagery, field inspection, videography, LIDAR or a combination of all data sources. Bank height categories are low = 0-5 feet, 5-30 feet, and &gt;30 feet. </attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<udom>bank height: 0-5, 5-30, or &gt;30</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">lowBankAndPermStruc</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Shoreline has a low or moderate bank height (0-5 ft) or (5-30 ft) and there is a road or permanent structure present that might impede bank grading.</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<udom>Values are "Yes" if conditions are met, otherwise it is "No".</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">FedChannel</attrlabl>
<attalias Sync="TRUE">FederalChannel</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Navigation channels are maintained by the U.S Army Corps of Engineers (USACE). Shorelines within a 150-foot buffer of a Federally maintained navigation channel are flagged for special consideration in the LSSM. </attrdef>
<attrdefs>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</attrdefs>
<attrdomv>
<edom>
<edomv>Federal Channel nearby</edomv>
<edomvd>Shoreline is intersected by a150 ft buffer around a Federal Channel</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>No</edomv>
<edomvd>Federal navigation channel is not nearby.</edomvd>
<edomvds>processor</edomvds>
</edom>
</attrdomv>
</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 structures that sit perpendicular to the shore and are designed to trap sand and reduce erosion. They can be constructed of rock, timber, vinyl, steel, concrete, or other similar material. 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. When effective, groins will trap sediment moving alongshore. </edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Marsh Toe</edomv>
<edomvd>A continuous low-profile breakwater structure placed offshore from an existing marsh or new planted marsh. The structure may include tidal openings to allow for the easy exchange of free-swimming organisms during tidal cycles. Sills are mapped as offshore linear features running along the length of the shoreline. (aka Low Profile Sill, Marsh Sill, or Marsh Toe Revetment)</edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), Center for Coastal Resources Management, VIMS</edomvds>
</edom>
<edom>
<edomv>Breakwater</edomv>
<edomvd>Breakwaters are structures that sit offshore and generally occur in a parallel series along the shore. Some breakwaters are attached to the land and are referred to as headland breakwaters. Their purpose is to attenuate and deflect incoming wave energy, protecting the area behind and between the structures. The Shoreline Inventory does not map individual breakwaters. A breakwater “system” is delineated and depicted as a line parallel to the series of breakwaters. The classification can include best professional judgement.</edomvd>
<edomvds>Glossary of Shoreline Feature Reference Layers for Maryland Living Shoreline Suitability Model (LSSM), 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">defended</attrlabl>
<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>
<attrdef>Shoreline has an erosion control structure in place.</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<edom>
<edomv>Yes</edomv>
<edomvd>An erosion control structure is present</edomvd>
<edomvds>processor</edomvds>
</edom>
<edom>
<edomv>No</edomv>
<edomvd>Shoreline is not defended (i.e. no erosion control structure is present)</edomvd>
<edomvds>processor</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">StrucList</attrlabl>
<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>
<attrdef>list of shoreline structures present (includes structures on shore and offshore)
</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<udom>combines the structures listed in the "Structure" and "offshorest" fields into one attribute list</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SpecialArea</attrlabl>
<attalias Sync="TRUE">SpecialConsideration</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Areas of special consideration that may require advice from regulatory agencies and expert due to ecological or highly modified conditions.</attrdef>
<attrdefs>processor</attrdefs>
<attrdomv>
<edom>
<edomv>Ecological Consideration</edomv>
<edomvd>Management options for this shoreline may be limited by the presence of Submerged Aquatic Vegetation (SAV), Rare, Threatened, or Endangered (RTE) species/habitat. Seek advice from the Tidal Wetlands Division of MDE.</edomvd>
<edomvds>Maryland Living Shoreline Suitability Model - Recommended Shoreline Best Management Practices Glossary </edomvds>
</edom>
<edom>
<edomv>Highly Modified Area</edomv>
<edomvd>Management options for this shoreline may be limited due to the presence of Federal navigation channels, highly developed upland (e.g. commercial wharfs), channel modifications (e.g. canals) or infrastructure directly adjacent to the shoreline (e.g. road). Seek expert advice on the design of your project.</edomvd>
<edomvds>Maryland Living Shoreline Suitability Model - Recommended Shoreline Best Management Practices Glossary </edomvds>
</edom>
<edom>
<edomv>Land Use Management</edomv>
<edomvd>This shoreline has unique features and shoreline management considerations. Forces other than tidal erosion, such as over-land runoff, upland development, and vegetation management are likely also having an effect on bank conditions. Assessment of all factors and modifications to address causes for bank erosion are recommended. Seek advice from the Tidal Wetlands Division of MDE. May require consultation with multiple agencies.</edomvd>
<edomvds>Maryland Living Shoreline Suitability Model - Recommended Shoreline Best Management Practices 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>Maryland Living Shoreline Suitability Model - Recommended Shoreline Best Management Practices Glossary </edomvds>
</edom>
</attrdomv>
</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 the definition creation or revision.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SpecCount</attrlabl>
<attalias Sync="TRUE">SpecialAreaCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Special Area count tallies the number of times a section of shoreline is flagged for a special area designation.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HMACount</attrlabl>
<attalias Sync="TRUE">HighModAreaCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Highly Modified Area Count tallies the number of times a section of shoreline is flagged for as a Highly Modified Area.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HMAType</attrlabl>
<attalias Sync="TRUE">HMAType</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">150</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Highly Modified Area Type lists each cause that triggers the Highly Modified Area designation.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">EcoCount</attrlabl>
<attalias Sync="TRUE">EcologicalConflictCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Ecological Conflict Count tallies the number of times a section of shoreline is flagged for an Ecological Conflict.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">LUMCount</attrlabl>
<attalias Sync="TRUE">LUManagemntCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Land Use Management Count tallies the number of times a section of shoreline is flagged for Land Use Management. Values should be 0 or 1.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">LUMType</attrlabl>
<attalias Sync="TRUE">LUMType</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Landuse Management Type lists each cause that triggers the Land Use Management designation. List values should be "none" or "Land Use Management - high bank".</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SpitCount</attrlabl>
<attalias Sync="TRUE">SandSpitCount</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Sand Spit Count tallies the number of times a section of shoreline is flagged as a Special Geomorphic Area. Values should be 0 or 1.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SpitType</attrlabl>
<attalias Sync="TRUE">SandSpitType</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Sand Spit Type lists each cause that triggers the Special Geomorphic Area designation. List values should be "none" or "Special Geomorphic Feature - Sandspit".</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">County</attrlabl>
<attalias Sync="TRUE">County</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Maryland County name</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">StrucState</attrlabl>
<attalias Sync="TRUE">ObservedShorelineStructureStatement</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">200</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>A sentence about whether or not the shoreline was observed to have an erosion control structure present. This field can be used in the popup in a web app.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SenSpecies</attrlabl>
<attalias Sync="TRUE">SensitiveSpecies</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Sensitive species buffer area overlaps shoreline.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">mdeLink</attrlabl>
<attalias Sync="TRUE">mdeLink</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>url to Maryland Department of the Environment Wetlands and Waterways Program Directory. This link provides users with a way to contact experts for information about potential special consideration areas (ecological conflicts, highly modified areas, etc) that could impact a shoreline erosion control project.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SpecAreaCopy</attrlabl>
<attalias Sync="TRUE">SpecialConsiderationAreaCopy</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>This field is a copy of the SpecialConsiderations field. Some attribute names have been shortened. This field is used for display and popup information.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MSSMClsF</attrlabl>
<attalias Sync="TRUE">MSSM_Classification_Final</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">600</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Maryland Shoreline Stabilization final recommendations.</attrdef>
<attrdefs>Maryland Shoreline Stabilization Mapper (MSSM) - Recommended Shoreline Practices Glossary, 2021</attrdefs>
<attrdomv>
<edom>
<edomv>Living Shoreline</edomv>
<edomvd>Installation of an approach that uses plants and sand, rock, oyster shell, or other natural materials to protect shoreline and to create, maintain, and enhance habitat may be appropriate where a structural shoreline stabilization measure is not present or is non-functional.</edomvd>
<edomvds>Maryland Shoreline Stabilization Mapper (MSSM) - Recommended Shoreline Practices Glossary, 2022</edomvds>
</edom>
<edom>
<edomv>Undetermined</edomv>
<edomvd>In order to make an appropriate shore erosion control measure determination the property owner should coordinate a pre-application site visit with an MDE Project Manager assigned to the territory and complete a Living Shoreline Waiver request form. </edomvd>
<edomvds>Maryland Shoreline Stabilization Mapper (MSSM) - Recommended Shoreline Practices Glossary, 2022</edomvds>
</edom>
<edom>
<edomv>Structural Shoreline Stabilization Measure</edomv>
<edomvd>A predetermined decision by MDE that a person is not required to construct a living shoreline but can construct an erosion control measure that uses devices to armor and stabilize an area landward of the measure from further erosion. The measure may include the use of a bulkhead, revetment, groin, breakwater, jetty, sand, beach nourishment, and any other similar structure.</edomvd>
<edomvds>Maryland Shoreline Stabilization Mapper (MSSM) - Recommended Shoreline Practices Glossary, 2022</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">MSSMClsDef</attrlabl>
<attalias Sync="TRUE">MSSM_Classification_Final_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 MSSM_Classification_Final field. Please see MSSMClsF attribute for list of categories and definitions</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">SpecConDef</attrlabl>
<attalias Sync="TRUE">SpecialConsiderationDefinition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Definitions for Areas of Special Consideration. Please see MSSMClass attribute for list of categories and definitions. Special Consideration Categories: Ecological Considerations, Highly Modified Area, Land Use Management, and Special Geomorphic Area.</attrdef>
<attrdefs>processor</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">replace</attrlabl>
<attalias Sync="TRUE">replace</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<distInfo>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3857"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.8(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Maryland_Year3_5Counties_SSM_Combined_Oct_5_2022_wm">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">31849</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Maryland_Year3_5Counties_SSM_Combined_Oct_5_2022_wm">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">31849</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<mdDateSt Sync="TRUE">20221208</mdDateSt>
</metadata>
