<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20230802</CreaDate>
<CreaTime>12532000</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">SupplementalFloodZone</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<itemSize Sync="TRUE">4.590</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">2503473.423144</westBL>
<eastBL Sync="TRUE">2718459.018918</eastBL>
<southBL Sync="TRUE">652948.073478</southBL>
<northBL Sync="TRUE">878660.724908</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet</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/2.8.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,1999996.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-81.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,32.5],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,34.83333333333334],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,31.83333333333333],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;Esri&amp;quot;,102733]]&lt;/WKT&gt;&lt;XOrigin&gt;-122907300&lt;/XOrigin&gt;&lt;YOrigin&gt;-92800500&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121918&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&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;102733&lt;/WKID&gt;&lt;LatestWKID&gt;102733&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20210713</SyncDate>
<SyncTime>15124100</SyncTime>
<ModDate>20210713</ModDate>
<ModTime>15124100</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>ItemDescription</ArcGISProfile>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 12.8.0.29751</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">SupplementalFloodZone</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-79.345877</westBL>
<eastBL Sync="TRUE">-78.622720</eastBL>
<northBL Sync="TRUE">34.237178</northBL>
<southBL Sync="TRUE">33.605427</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idCredit>Western Carolina University, Program for the Study of Developed Shorelines, Cullowhee, NC, 28723</idCredit>
<idPurp>This Supplemental Flood Zone (SFZ) was created by Western Carolina University at the request of Horry County. This SFZ methodology goes beyond FEMA’s probability-based maps (e.g., percent-annual chance), creating hazard zones based on recorded, historic flood exposure. The resulting data could be used for informational or academic purposes, or to reduce the vulnerability of future development through appropriate regulations and policy. The primary objectives of this mapping exercise were to utilize field-collected, post-storm data (high water marks) of flood elevations from Hurricane Florence within Horry County to: 1) delineate a SFZ independent of the FEMA SFHA, which approximates the actual extent of flooding during Florence (the storm of record); and 2) create subzones (within the SFZ), each with an adjusted Base Flood Elevation (BFE) that is based on the flood elevations recorded from Florence. This metatdata was created on 10/8/2020, and may have since been updated. See this link for updates: http:///shoreline2.wcu.edu/Katie/HorrySFZ_Metadata.pdf
</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;P STYLE="font-weight:bold;margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Data Utilized &amp;amp; Consulted &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;USGS Florence flood elevation data (sensor, high water mark, and peak summary) - &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A href="https://stn.wim.usgs.gov/FEV/#FlorenceSep2018"&gt;&lt;SPAN&gt;&lt;SPAN&gt;https://stn.wim.usgs.gov/FEV/#FlorenceSep2018&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;&lt;SPAN&gt;. The majority of the flood elevation data used in this study are from high water marks, which are defined as post-flood evidence that marks the highest elevation of floodwaters (e.g., seed, mud, or debris lines stranded as water recedes.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Florence building flood damage data– from Horry County. Removed damage points with 0% damage. Was a rapid assessment of damage percent for buildings in the county, commonly containing an estimate of water height within the structure. Building height above grade was estimated from photographs taken during the rapid assessment.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;2017 Digital Elevation Model (DEM) – obtained from Horry County. 2020 DEM was not available until after the digitization was complete. The 2017 DEM served as the primary base map for the SFZ digitization and analysis, as it was the elevation dataset acquired closest to the date of Florence (2018). &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Preliminary FEMA data – 2019 digital FEMA maps obtained from Horry County, including BFE transects. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Other reference GIS data from Horry County – e.g., roads, hydrology (rivers), buildings, communities, county boundary&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P STYLE="font-weight:bold;margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Methods&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt;Creating transition points &amp;amp; subzones boundaries.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; Before the SFZ could be digitized, the Florence Flood elevations (high water marks) were used to create the transition points that would serve as the “boundaries” between the different subzones. This process began in the east portion of the county, where the Waccamaw River enters Horry County. Each subzone is assigned an adjusted BFE, using one foot intervals. For example, the BFE subzone 26 represents a flood elevation of 26 feet (above NAVD88), and all areas within this subzone have an adjusted BFE of 26 feet. In addition, all high-water marks that are between 26 and 27 feet (above NAVD88) are included within the 26 subzone, which means each subzone is a relatively conservative estimate of the flooding during Florence.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt;Symbolizing &amp;amp; interpreting the subzone elevations.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; For each subzone, the approximate Florence flood elevation contour was symbolized by shading the DEM to the appropriate whole number elevation. For example, in the 27-foot subzone, the DEM was symbolized to highlight elevation values near 27 feet; the resulting shaded DEM was used to interpret an approximate 27-foot flood contour.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt;Digitizing the SFZ &amp;amp; subzones.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; Each subzone was digitized using the polygon feature in ArcMap at 1-foot flood intervals. The stepwise interpretation of subzones using flood contours continued for areas affected by Florence and where flood elevation data existed (downstream along the Waccamaw River and its major tributaries, into the ICW near Socastee, and north along the Little Pee Dee River). &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P STYLE="font-weight:bold;margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Notes &amp;amp; Caveats&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;The BFE values were rounded down to the nearest whole number within each subzone. Therefore, each subzone represents the area that would be inundated by a flood level equivalent to the assigned BFE. This means that the SFZ is a relatively conservative depiction of the flooding during Florence (as a location that has a high-water mark of 26.8 feet is included in the 26-foot subzone). &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;In some cases, (along the Little Pee Dee Watershed) HWMs immediately outside the Horry County boundary were utilized to estimate location of SFZ subzones. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;The SFZ was only digitized within the boundaries of Horry County, even when the floodplain and flood elevations extended beyond the county line.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;The SFZ is not continuously mapped within Horry County. In a few areas, there is a lack of data control (no high-water marks exist nearby) and therefore the SFZ was not interpreted. This is true along the Waccamaw River near the southern boundary of Horry County (southern portions of subzones 11 and 15, near the confluence of Bull Creek and the Waccamaw), as well as several stretches along the Little Pee Dee River between Bucksport and Pee Dee Crossroads, Pee Dee Crossroads and Dog Bluff, Dog Bluff and Galivants Ferry, and north of Floyds Crossroad. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;In some of the locations along the Little Pee Dee where the SFZ could not be interpreted (due to lack of high water marks), additional subzones were digitized using less reliable flood elevation data. This separate file can be viewed in conjunction with the primary SFZ, but there is less confidence in the boundaries between these subzones due to the method of obtaining flood elevations. In these areas, flood elevations were estimated using the building damage data (rapid, post-storm, damage assessments obtained by Horry County, which estimate the amount of flooding in a building), the DEM (to get a ground elevation), and damage photos (to estimate building height above grade). &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI STYLE="margin:0 0 0 48;"&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;This SFZ (and associated subzones) represent the raw and highly detailed results of the digitization of flood&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;elevations, interpreted using Florence flood data and a DEM. More practical generalized “zones” may need to be created for the regulation of development. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="font-weight:bold;margin:0 0 11 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>Flood zone</keyword>
<keyword>BFE</keyword>
<keyword>FEMA</keyword>
</searchKeys>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">4.590</transSize>
</distTranOps>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="102733"/>
<idCodeSpace Sync="TRUE">Esri</idCodeSpace>
<idVersion Sync="TRUE">8.0.1</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="SupplementalFloodZone">
<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="SupplementalFloodZone">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<eainfo>
<detailed Name="SupplementalFloodZone">
<enttyp>
<enttypl Sync="FALSE">SupplementalFloodZone</enttypl>
<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">10</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 Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Comment</attrlabl>
<attalias Sync="TRUE">Comment</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">BFESubzone</attrlabl>
<attalias Sync="TRUE">BFESubzone</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Watershed</attrlabl>
<attalias Sync="TRUE">Watershed</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">Shape.STArea()</attrlabl>
<attalias Sync="TRUE">Shape.STArea()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STLength()</attrlabl>
<attalias Sync="TRUE">Shape.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<mdDateSt Sync="TRUE">20210713</mdDateSt>
</metadata>
