<?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>200611</pubdate>
<title>FloodZones</title>
<geoform Sync="TRUE">vector digital data</geoform>
<pubinfo>
<pubplace>Raleigh, NC</pubplace>
<publish>North Carolina Floodplain Mapping Program, North Carolina Division of Emergency Management</publish>
</pubinfo>
<onlink Sync="FALSE">withheld</onlink>
<ftname Sync="FALSE">Floodzones_Randolph</ftname>
</citeinfo>
</citation>
<descript>
<abstract>MapFldHazAr is a GIS shapefile representing the area within the flood mapping boundaries defined by the engineering models for the 100 year, 500 year and floodway. The MapFldHazAr spatial table contains information about the flood hazard within the study area. These zones are used by FEMA to designate the Special Flood Hazard Area (SFHA), identify areas of coastal high hazard flooding, and for insurance rating purposes. These data are the flood hazard areas that are or will be depicted on the FIRM. Imported to ArcSDE 04/23/08.</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>
<supplinf>Imported into ArcSDE 04/23/08.</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>200611</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-80.072307</westbc>
<eastbc Sync="TRUE">-79.539124</eastbc>
<northbc Sync="TRUE">35.923982</northbc>
<southbc Sync="TRUE">35.505844</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">1682505.707912</leftbc>
<rightbc Sync="TRUE">1839558.318019</rightbc>
<bottombc Sync="TRUE">640735.562881</bottombc>
<topbc Sync="TRUE">791664.457873</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Map Flood Hazard Area</themekey>
<themekey>Floodplain Boundaries</themekey>
<themekey>100 Year Flood</themekey>
<themekey>500 Year Flood</themekey>
<themekey>1% annual chance flood hazard</themekey>
<themekey>0.2% annual chance flood hazard</themekey>
<themekey>DFIRM</themekey>
<themekey>Digital Flood Insurance Rate Map</themekey>
<themekey>FIRM</themekey>
<themekey>Flood Insurance Rate Map</themekey>
<themekey>Floodway</themekey>
<themekey>Riverine flooding</themekey>
<themekey>Special Flood Hazard Area</themekey>
<themekey>Coastal flooding</themekey>
</theme>
<place>
<placekt>North Carolina Atlas &amp; Gazetteer (Yarmouth, Maine: DeLorme, 2001).</placekt>
<placekey>Randolph County, City of Archdale, City of Archdale Extraterritorial Jurisdiction, City of Asheboro, City of Asheboro Extraterritorial Jurisdiction, Town of Franklinville, Town of Franklinville Extraterritorial Jurisdiction, City of High Point, City of High Point Extraterritorial Jurisdiction, Town of Liberty, Town of Liberty Extraterritorial Jurisdiction, Town of Ramseur, Town of Ramseur Extraterritorial Jurisdiction, City of Randleman, City of Randleman Extraterritorial Jurisdiction, Town of Seagrove, Town of Staley, Town of Trinity, 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>
<cntpos>GIS Coordinator</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>725 McDowell Rd</address>
<city>Asheboro</city>
<state>NC</state>
<postal>27205</postal>
</cntaddr>
<cntvoice>336-318-6312</cntvoice>
<cntfax>336-318-6398</cntfax>
<cntperp>
<cntper>Linda Smith</cntper>
<cntorg>Randolph County, IT</cntorg>
</cntperp>
</cntinfo>
</ptcontac>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.1850</native>
<crossref>
<citeinfo>
<origin>Federal Emergency Management Agency</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Flood Insurance Study, RANDOLPH 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, RANDOLPH 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, RANDOLPH COUNTY, NC</title>
<geoform>map</geoform>
<pubinfo>
<pubplace>Washington, DC</pubplace>
<publish>FEMA</publish>
</pubinfo>
<onlink>withheld</onlink>
</citeinfo>
</crossref>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<dataqual>
<logic>None</logic>
<complete>None</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Watershed Concepts</origin>
<pubdate>200611</pubdate>
<title>MapFldHazAr</title>
</citeinfo>
</srccite>
<typesrc>Shapefile</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>200611</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>MapFldHazAr</srccitea>
<srccontr>
For streams restudied by detailed and limited detail methods, the 1% and 0.2% annual chance floodplains were delineated using flood elevations determined at each cross section. Between cross sections, the boundaries were interpolated using topographic data acquired using airborne LIDAR. This LIDAR data was acquired during the winter 2000-2001 flying season.
The topographic data satisfies a vertical root-mean-square error (RMSE) accuracy standard of 20cm (1.3 feet accuracy at the 95% confidence limit) for the Outer Banks and 25 cm (1.6 feet accuracy at the 95% confidence limit) for those portions of the basin lying west of the Outer Banks. These data could be contoured at roughly a 2-foot vertical contour interval. All elevations were referenced to the NAVD 88 and reflect orthometric heights. Variably spaced, bare-earth digital topographic data in ASCII point file format were combined with imagery (either flown concurrently with the LIDAR data or using existing digital orthophotos) to establish a Triangulated Irregular Network (TIN) of digital elevation points, which include selected breaklines to be used for hydraulic modeling. Furthermore, a uniformly spaced sampling of the TIN resulted in uniformly spaced Digital Elevation Models (DEMs), with 20 ft x 20 ft post spacing, which was generated in multiple file formats.
The 1% annual chance floodplain boundary corresponds to the boundary of the areas of special flood hazards (Zones VE, AO, AH, A99, AR, A, and AE), and the 0.2% annual chance floodplain boundary corresponds to the boundary of areas of moderate flood hazards. In cases where the 1% and 0.2% annual chance floodplain boundaries are close together, only the 1% annual chance floodplain boundaries have been shown.
The floodways were computed for certain stream segments on the basis of equal conveyance reduction from each side of the floodplain. Floodway widths were
computed at cross sections. Between cross sections, the floodway boundaries were interpolated. The computed floodway is shown on the FIRM. In cases where the floodway and 1% annual chance floodplain boundaries are either close together or collinear, only the floodway boundary is shown.
</srccontr>
</srcinfo>
<procstep>
<procdesc>
For streams restudied by detailed and limited detail methods, the 1% and 0.2% annual chance floodplains were delineated using flood elevations determined at each cross section. Between cross sections, the boundaries were interpolated using topographic data acquired using airborne LIDAR. This LIDAR data was acquired during the winter 2000-2001 flying season.
The topographic data satisfies a vertical root-mean-square error (RMSE) accuracy standard of 20cm (1.3 feet accuracy at the 95% confidence limit) for the Outer Banks and 25 cm (1.6 feet accuracy at the 95% confidence limit) for those portions of the basin lying west of the Outer Banks. These data could be contoured at roughly a 2-foot vertical contour interval. All elevations were referenced to the NAVD 88 and reflect orthometric heights. Variably spaced, bare-earth digital topographic data in ASCII point file format were combined with imagery (either flown concurrently with the LIDAR data or using existing digital orthophotos) to establish a Triangulated Irregular Network (TIN) of digital elevation points, which include selected breaklines to be used for hydraulic modeling. Furthermore, a uniformly spaced sampling of the TIN resulted in uniformly spaced Digital Elevation Models (DEMs), with 20 ft x 20 ft post spacing, which was generated in multiple file formats.
The 1% annual chance floodplain boundary corresponds to the boundary of the areas of special flood hazards (Zones VE, AO, AH, A99, AR, A, and AE), and the 0.2% annual chance floodplain boundary corresponds to the boundary of areas of moderate flood hazards. In cases where the 1% and 0.2% annual chance floodplain boundaries are close together, only the 1% annual chance floodplain boundaries have been shown.
The floodways were computed for certain stream segments on the basis of equal conveyance reduction from each side of the floodplain. Floodway widths were
computed at cross sections. Between cross sections, the floodway boundaries were interpolated. The computed floodway is shown on the FIRM. In cases where the floodway and 1% annual chance floodplain boundaries are either close together or collinear, only the floodway boundary is shown.
</procdesc>
<procdate>Unknown</procdate>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20070720</date>
<time Sync="TRUE">13465000</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080105</date>
<time Sync="TRUE">18013600</time>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="Floodplain_100Yr_Poly">
<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>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<coordrep>
<absres Sync="TRUE">0.000328</absres>
<ordres Sync="TRUE">0.000328</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">1.000000</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="Floodplain_100Yr_Poly">
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<edom>
<edomv>Polygon</edomv>
<edomvd>Polygons represent area features and are made up of arcs which define the boundary.</edomvd>
<edomvds>ESRI</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">FLOODZONE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FLOODZONE</attrlabl>
<attrdef>FIRM zone designation</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<attrdomv>
<codesetd>
<codesetn>D_FldZn</codesetn>
<codesets>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</codesets>
</codesetd>
</attrdomv>
<attalias Sync="TRUE">VERDATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<enttyp>
<enttypl Sync="FALSE">Floodplain_100Yr_Poly</enttypl>
<enttypd>Polygon Geometry file that is the physical representation of the Flood Mapping Boundaries that are calculated from the Engineering Models</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>VERDATE</attrlabl>
<attrdef>Data creation date; contractor enters this date</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<attrdomv>
<edom>
<edomv>20061117</edomv>
<edomvd>Creation date</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attalias Sync="TRUE">PERCYRFLD</attalias>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PERCYRFLD</attrlabl>
<attalias Sync="TRUE">PAN</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<attrdef>Percent chance of year flood.</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PAN</attrlabl>
<attalias Sync="TRUE">SCALE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<attrdef>Panel Number</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SCALE</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<attrdef>Map Scale</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">MAPNO</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</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">MAPNO</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attrdef>Map Number</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE</attrlabl>
<attalias Sync="TRUE">AREA_</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">EFFDATE</attrlabl>
<attalias Sync="TRUE">publication.LOADER.Floodzones_Randolph.len</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attrdef>Effective Date</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AREA_</attrlabl>
<attalias Sync="TRUE">EFFDATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</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>
<distinfo>
<distrib>
<cntinfo>
<cntpos>Applications Analyst GIS</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>336-318-6312</cntvoice>
<cntfax>336-318-6398</cntfax>
<cntemail>lrsmith@co.randolph.nc.us</cntemail>
<hours>8:00 AM to 5:00 PM EST</hours>
<cntinst>Phone and email preferred. </cntinst>
<cntperp>
<cntper>Linda Smith</cntper>
<cntorg>Randolph County, IT</cntorg>
</cntperp>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>All information contained herein was created for the County's internal use. Randolph County, its agents and employees make no warranty as to the correctness or accuracy of the information set forth in this data whether express or implied, in fact or in law, including without limitation the implied warranties of merchantability and fitness for a particular use. Any resale of this data is strictly prohibited in accordance with North Carolina General Statute 132-10.
Orginal data was provided by NCCGIA as part of the State of North Caroline's corporate geographic database. 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>polygon dataset and metadata</formcont>
<filedec>PC-based PKZip compatible products (WinZip, unzip) may be used to decompress the dataset.</filedec>
<transize Sync="TRUE">38.168</transize>
<dssize Sync="TRUE">38.168</dssize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>withheld</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>$25.00</fees>
<ordering>Call or e-mail contact person and request data.</ordering>
<turnarnd>2 week</turnarnd>
</stdorder>
<custom>Data is available on magnetic media (CD). Data can be ordered via telephone. All data is reproduced at a charge of $25.00 per hour plus the cost of the media.</custom>
<techpreq>Data can be reproduced in Arcview shapefile format(.shp), Arc/Info Export format (.e00) and Autocad dxf format.</techpreq>
</distinfo>
<metainfo>
<metd>01/22/2008</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Randolph County</cntorg>
<cntper>Linda Smith</cntper>
</cntorgp>
<cntpos>Applications Analyst GIS</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>725 McDowell Rd</address>
<city>Asheboro</city>
<state>NC</state>
<postal>27205</postal>
</cntaddr>
<cntvoice>336-318-6312</cntvoice>
<cntfax>336-318-6312</cntfax>
</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>
<metac>none</metac>
<metuc>none</metuc>
</metainfo>
<Esri>
<CreaDate>20170410</CreaDate>
<CreaTime>14075200</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20220818</SyncDate>
<SyncTime>10463100</SyncTime>
<ModDate>20220818</ModDate>
<ModTime>10463100</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">Floodplain_100Yr_Poly</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">1682505.707912</westBL>
<eastBL Sync="TRUE">1839558.318019</eastBL>
<southBL Sync="TRUE">640735.562881</southBL>
<northBL Sync="TRUE">791664.457873</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_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/2.9.0'&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;3048.0060960121928&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;102719&lt;/WKID&gt;&lt;LatestWKID&gt;2264&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 12.9.0.32739</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Floodplain_100Yr_Poly</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">1682505.707912</westBL>
<eastBL Sync="TRUE">1839558.318019</eastBL>
<northBL Sync="TRUE">791664.457873</northBL>
<southBL Sync="TRUE">640735.562881</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-80.072307</westBL>
<eastBL Sync="TRUE">-79.539124</eastBL>
<northBL Sync="TRUE">35.923982</northBL>
<southBL Sync="TRUE">35.505844</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-80.072307</westBL>
<eastBL Sync="TRUE">-79.539124</eastBL>
<northBL Sync="TRUE">35.923982</northBL>
<southBL Sync="TRUE">35.505844</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</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>
</onLineSrc>
<transSize Sync="TRUE">38.168</transSize>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2264" value="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="Floodplain_100Yr_Poly">
<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">20220818</mdDateSt>
</metadata>
