<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>North Carolina Floodplain Mapping Program, North Carolina Division of Emergency Management</origin>
<pubdate>200802</pubdate>
<title Sync="TRUE">MAPBFE</title>
<geoform Sync="TRUE">vector digital data</geoform>
<onlink Sync="FALSE">withheld</onlink>
<ftname Sync="TRUE">MAPBFE</ftname>
</citeinfo>
</citation>
<descript>
<abstract>MapBFE is a GIS shapefile containing information about the Base Flood Elevations (BFE) within a study area. BFE lines indicate the approximate water surface elevation of the 1% annual chance flood hazard.</abstract>
<purpose>These data were collected and derived by the North Carolina Floodplain Mapping Program (www.ncfloodmaps.com) as part of its effort to modernize FEMA Flood Insurance Rate Maps (FIRM) statewide. The North Carolina Floodplain Mapping Program was established through a Cooperating Technical State (CTS) agreement with FEMA in response to the extensive damage caused by Hurricane Floyd in 1999.</purpose>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>200802</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-82.680856</westbc>
<eastbc Sync="TRUE">-82.113150</eastbc>
<northbc Sync="TRUE">36.089289</northbc>
<southbc Sync="TRUE">35.169278</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">912458.114583</leftbc>
<rightbc Sync="TRUE">1069970.005208</rightbc>
<bottombc Sync="TRUE">536476.656250</bottombc>
<topbc Sync="TRUE">866150.348958</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Base Flood Elevation</themekey>
<themekey>Map Base Flood Elevation</themekey>
<themekey>BFE</themekey>
<themekey>Water surface elevation</themekey>
</theme>
<place>
<placekt>North Carolina Atlas &amp; Gazetteer (Yarmouth, Maine: DeLorme, 2001).</placekt>
<placekey>Yancey County, Burnsville, Green Mountain, Swiss, North Carolina</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>These data were created with the highest consideration of accuracy and data integrity. However, as with all other geospatial datasets, users must take into consideration the consequences of using the data for specific applications, business processes, decisions, and map display. For example, surface conditions may have changed in some areas since the initial data was captured. A full metadata record is provided to help the user understand the date, map scale and accuracy standard applied in the collection and data development process. The data should not be used without full review and comprehension of the metadata. Acknowledgement of the North Carolina Floodplain Mapping Program is appreciated when using the data set. Data further derived from this data set should be fully documented using the federal metadata standard and listed via the NC Geospatial Data Clearinghouse.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Greenhorne &amp; O'Mara, Inc.</cntorg>
<cntper>James Huffines</cntper>
</cntorgp>
<cntpos>Technical Director</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>5565 Centerview Dr. Suite 107</address>
<city>Raleigh</city>
<state>NC</state>
<postal>27606</postal>
</cntaddr>
<cntvoice>919-532-2332</cntvoice>
<cntfax>919-851-8393</cntfax>
</cntinfo>
</ptcontac>
<native Sync="FALSE">ESRI ArcCatalog 9.2.4.1420</native>
<crossref>
<citeinfo>
<origin>Federal Emergency Management Agency</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Flood Insurance Study, YANCEY COUNTY, NC</title>
<geoform>document</geoform>
<pubinfo>
<pubplace>Washington, DC</pubplace>
<publish>FEMA</publish>
</pubinfo>
<onlink>withheld</onlink>
</citeinfo>
</crossref>
<crossref>
<citeinfo>
<origin>Federal Emergency Management Agency</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Flood Insurance Study, YANCEY COUNTY, NC</title>
<geoform>raster digital data</geoform>
<pubinfo>
<pubplace>Washington, DC</pubplace>
<publish>FEMA</publish>
</pubinfo>
<onlink>withheld</onlink>
</citeinfo>
</crossref>
<crossref>
<citeinfo>
<origin>Federal Emergency Management Agency</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Flood Insurance Study, YANCEY COUNTY, NC</title>
<geoform>map</geoform>
<pubinfo>
<pubplace>Washington, DC</pubplace>
<publish>FEMA</publish>
</pubinfo>
<onlink>withheld</onlink>
</citeinfo>
</crossref>
<natvform Sync="TRUE">Personal GeoDatabase Feature Class</natvform>
</idinfo>
<dataqual>
<logic>None</logic>
<complete>None</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Watershed Concepts</origin>
<pubdate>200802</pubdate>
<title>MapBFE</title>
</citeinfo>
</srccite>
<typesrc>Shapefile</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>200802</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>MapBFE</srccitea>
<srccontr>
For the streams studied by detailed methods, water-surface elevations of floods of the selected recurrence intervals were computed through use of the U.S. Army Corps of Engineers' HEC-RAS step-backwater computer program version 3.0 (USACE, 2001). The hydraulic analyses were based on unobstructed flow. The flood elevations shown on the profiles are thus considered valid only if hydraulic structures remain unobstructed, operate properly, and do not fail. The computer models were calibrated using historic high water data collected during field investigations. The cross section geometries were obtained from a combination of digital elevation data obtained using Light Detection and Ranging (LIDAR) data and field surveys. All bridges, dams, and culverts were field surveyed to obtain elevation data and structural geometry. Natural floodplain cross sections were surveyed approximately every 4000&#146; along the detail study reaches to obtain the channel geometry between bridges and culverts. Overbank cross-section data for the backwater analyses were obtained from recently flown LIDAR data.
For flooding sources studied by limited detailed methods in the county, standard hydrologic and hydraulic study methods were used to determine the flood hazard data required for this report and the FIRM panels. This method entails developing a HEC-RAS hydraulic model, resulting in the calculation of BFEs and the delineation of the 1% annual chance floodplain (designated as Zone AE). Cross sections for the flooding sources studied by limited detailed methods were obtained using digital elevation data obtained with LIDAR technology developed as part of the North Carolina Statewide Floodplain Mapping Program. The hydraulic model is prepared using this digital elevation data, without surveying bathymetric or structural data. Where bridge or culvert data are readily available, such as from the North Carolina Department of Transportation, these data have been reflected in the hydraulic model. If these structural data are not readily available, field measurements of these structures were made to approximate their geometry in the hydraulic models. In addition, this method does not include field surveys that determine specifics on channel and floodplain characteristics. A limited detailed study is a "buildable" product that can be upgraded to a fully detailed study at a later date by verifying stream channel characteristics, bridge and culvert opening geometry, and by analyzing multiple recurrence intervals.
Each jurisdiction within Yancey County had previously printed FIS Reports describing each community's hydraulic analyses. Those analyses have been compiled and are summarized below. These analyses remain valid for those flooding sources listed below under "Redelineated streams."
</srccontr>
</srcinfo>
<procstep>
<procdesc>
For the streams studied by detailed methods, water-surface elevations of floods of the selected recurrence intervals were computed through use of the U.S. Army Corps of Engineers' HEC-RAS step-backwater computer program version 3.1.2 (USACE, 2001). The hydraulic analyses were based on unobstructed flow. The flood elevations shown on the profiles are thus considered valid only if hydraulic structures remain unobstructed, operate properly, and do not fail. The computer models were calibrated using historic high water data collected during field investigations. The cross section geometries were obtained from a combination of digital elevation data obtained using Light Detection and Ranging (LIDAR) data and USGS Quads and field surveys. All bridges, dams, and culverts were field surveyed to obtain elevation data and structural geometry. Surveyed cross sections are placed based off aerial photos and topographic data with a maximum of one cross section every mile along the detail study reaches to obtain the channel geometry between bridges and culverts. Overbank cross-section data for the backwater analyses were obtained from recently flown LIDAR data.
For flooding sources studied by limited detailed methods in the county, standard hydrologic and hydraulic study methods were used to determine the flood hazard data required for this report and the FIRM panels. This method entails developing a HEC-RAS hydraulic model, resulting in the calculation of BFEs and the delineation of the 1% annual chance floodplain (designated as Zone AE). Cross sections for the flooding sources studied by limited detailed methods were obtained using digital elevation data obtained with LIDAR technology developed as part of the North Carolina Statewide Floodplain Mapping Program. The hydraulic model is prepared using this digital elevation data, without surveying bathymetric or structural data. Where bridge or culvert data are readily available, such as from the North Carolina Department of Transportation and NC Dam Safety, these data have been reflected in the hydraulic model. If these structural data are not readily available, field measurements of these structures were made to approximate their geometry in the hydraulic models. In addition, this method does not include field surveys that determine specifics on channel and floodplain characteristics. A limited detailed study is a "buildable" product that can be upgraded to a fully detailed study at a later date by verifying stream channel characteristics, bridge and culvert opening geometry, and by analyzing multiple recurrence intervals.
Each jurisdiction within Yancey County, had previously printed FIS Reports describing each community's hydraulic analyses. Those analyses have been compiled and are summarized below. These analyses remain valid for those flooding sources listed below under "Redelineated streams."
</procdesc>
<procdate>Unknown</procdate>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080225</date>
<time Sync="TRUE">13391900</time>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="MAPBFE">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<coordrep>
<absres Sync="TRUE">0.005208</absres>
<ordres Sync="TRUE">0.005208</ordres>
</coordrep>
<plandu Sync="TRUE">survey feet</plandu>
</planci>
</planar>
<geodetic>
<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
<semiaxis Sync="TRUE">6378137.000000</semiaxis>
<denflat Sync="TRUE">298.257222</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres Sync="TRUE">0.000010</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="MAPBFE">
<enttyp>
<enttypl Sync="TRUE">MAPBFE</enttypl>
<enttypd>Base Flood Elevations</enttypd>
<enttypds>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<edom>
<edomv>Polyline</edomv>
<edomvd>A type of shape made up of two or more segments.</edomvd>
<edomvds>ESRI</edomvds>
</edom>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">MAPBFEID</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">MAPBFEID</attrlabl>
<attalias Sync="TRUE">LEN_LID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">LEN_LID</attrlabl>
<attalias Sync="TRUE">V_DATM_LID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">V_DATM_LID</attrlabl>
<attalias Sync="TRUE">ELEV</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ELEV</attrlabl>
<attalias Sync="TRUE">METAID</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">METAID</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 Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">Geometry</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</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 Sync="TRUE">SHAPE</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">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE_Length</attrlabl>
<attalias Sync="TRUE">SHAPE_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>North Carolina Center for Geographic Information and Analysis</cntorg>
</cntorgp>
<cntpos>Production Services</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>301 N. Wilmington Street, Suite 700</address>
<city>Raleigh</city>
<state>NC</state>
<postal>27601-2825</postal>
<country>USA</country>
</cntaddr>
<cntvoice>919) 733-2090</cntvoice>
<cntfax>(919) 715-0725</cntfax>
<cntemail>dataq@ncmail.net</cntemail>
<hours>8:30 AM to 5:30 PM EST</hours>
<cntinst>Phone and email preferred. For current price information visit www.cgia.state.nc.us/cost.html</cntinst>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>NCCGIA is charged with the development and maintenance of the State's corporate geographic database and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information about the state. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop the corporate database may be reflected in the data supplied. The client must be aware of data conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this data. The use of trade names or commercial products does not constitute their endorsement by the NCCGIA or North Carolina State Government.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>ASCII</formname>
<formcont>line dataset and metadata</formcont>
<filedec>PC-based PKZip compatible products (WinZip, unzip) may be used to decompress the dataset.</filedec>
<transize>2.0-4.0 MB</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>withheld</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>For current price information visit www.cgia.state.nc.us/cost.html</fees>
</stdorder>
<custom>Custom data creation and analysis work is available by contract. Contact Production Services at (919) 733-2090.</custom>
<techpreq>Data are supplied in ArcInfo and ASCII formats. Format compatibility is the user's responsibility. For more information visit www.cgia.state.nc.us/cost.html</techpreq>
</distinfo>
<metainfo>
<metd Sync="TRUE">20080225</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Greenhorne &amp; O'Mara, Inc.</cntorg>
<cntper>Kristel Whitson</cntper>
</cntorgp>
<cntpos>GIS Technician</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>5565 Centerview Dr. Suite 107</address>
<city>Raleigh</city>
<state>NC</state>
<postal>27606</postal>
</cntaddr>
<cntvoice>919-532-2331</cntvoice>
</cntinfo>
</metc>
<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
<mettc Sync="TRUE">local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
<langmeta Sync="TRUE">en</langmeta>
</metainfo>
<Esri>
<MetaID>{EF5E2CD9-26A4-4B3A-BBEB-811A7F577C79}</MetaID>
<CreaDate>20080225</CreaDate>
<CreaTime>13391900</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20220620</SyncDate>
<SyncTime>10153900</SyncTime>
<ModDate>20220620</ModDate>
<ModTime>10153900</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">MAPBFE</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
</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_North_Carolina_FIPS_3200_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/10.6'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_North_Carolina_FIPS_3200_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;,2000000.002616666],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-79.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,34.33333333333334],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,36.16666666666666],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,33.75],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2264]]&lt;/WKT&gt;&lt;XOrigin&gt;-121841900&lt;/XOrigin&gt;&lt;YOrigin&gt;-93659000&lt;/YOrigin&gt;&lt;XYScale&gt;1536&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;8000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;8000&lt;/MScale&gt;&lt;XYTolerance&gt;0.010416666666666666&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.002&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.002&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102719&lt;/WKID&gt;&lt;LatestWKID&gt;2264&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
</Esri>
<dataIdInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9270</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">MAPBFE</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">912458.114583</westBL>
<eastBL Sync="TRUE">1069970.005208</eastBL>
<northBL Sync="TRUE">866150.348958</northBL>
<southBL Sync="TRUE">536476.65625</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-82.680856</westBL>
<eastBL Sync="TRUE">-82.11315</eastBL>
<northBL Sync="TRUE">36.089289</northBL>
<southBL Sync="TRUE">35.169278</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="TRUE">Personal GeoDatabase Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2264">NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.12(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="MAPBFE">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="TRUE">20220620</mdDateSt>
</metadata>
