<?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>200602</pubdate>
<title Sync="TRUE">stokes_vector.STOKES.flood_zones</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>withheld</onlink>
<ftname Sync="TRUE">stokes_vector.STOKES.flood_zones</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.</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>200602</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-80.454963</westbc>
<eastbc Sync="TRUE">-80.024406</eastbc>
<northbc Sync="TRUE">36.554148</northbc>
<southbc Sync="TRUE">36.253161</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">1572571.749829</leftbc>
<rightbc Sync="TRUE">1697953.625146</rightbc>
<bottombc Sync="TRUE">914180.249842</bottombc>
<topbc Sync="TRUE">1022210.375126</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>Stokes County, Brook Cove, Dalton, Danbury, Fulp, Germanton, Hartman, Harts Store, King, Lawsonville, Meadow, Perch, Pine Hall, Pinnacle, Sandy Ridge, Shoal, Walnut Cove, 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</cntorg>
<cntper>James Huffines</cntper>
</cntorgp>
<cntpos/>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>5565 Centerview Drive, 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.2.1350</native>
<crossref>
<citeinfo>
<origin>Federal Emergency Management Agency</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Flood Insurance Study, STOKES 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, STOKES 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, STOKES 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>200506</pubdate>
<title>MapFldHazAr</title>
</citeinfo>
</srccite>
<typesrc>Shapefile</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>200506</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.
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">20061221</date>
<time Sync="TRUE">15550900</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20070926</date>
<time Sync="TRUE">08423300</time>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="flood_zones">
<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.000651</absres>
<ordres Sync="TRUE">0.000651</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="flood_zones">
<attr>
<attrlabl>VERNO</attrlabl>
<attrdef>Generated during data loading, state determines versioning. A single VerNo may include records with different VerDates</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>0</edomv>
<edomvd>Generated during data loading, state determines versioning. A single VerNo may include records with different VerDates</edomvd>
<edomvds>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<attalias Sync="TRUE">VERNO</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<enttyp>
<enttypl Sync="TRUE">flood_zones</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>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>
<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>FLOODARID</attrlabl>
<attrdef>Primary key. Defined by mapping contractor using the formula: STFIPS + COFIPS + DATE + SEQUENTIAL NUMBER (where DATE=YYYYMMDD)</attrdef>
<attrdefs>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</attrdefs>
<attrdomv>
<rdom>
<rdommin>37157200506171</rdommin>
<rdommax>371572005061778</rdommax>
</rdom>
</attrdomv>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<attalias Sync="TRUE">FLOODARID</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>METAID</attrlabl>
<attrdef>Foreign key, link to Metadata table should be the same as for the flood hazard lines</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>9999</edomv>
<edomvd>Temporary value</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<attalias Sync="TRUE">METAID</attalias>
<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>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">55</attwidth>
<attalias Sync="TRUE">FLOODZONE</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ARREVERT</attrlabl>
<attrdef>If Zone AR, what zone it reverts to. Only populated if Zone = AR (currently only in California)</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>Null</edomv>
<edomvd>If Zone AR, what zone it reverts to. Only populated if Zone = AR (currently only in California)</edomvd>
<edomvds>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<attalias Sync="TRUE">ARREVERT</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SFHATF</attrlabl>
<attrdef>1 for zones A, AE, AO, AH, AR, A99, V, VE, 1pct in channel, 1pct in culvert. 0 for X, 0.2pct in channel, 0.2pct in culvert, D, Area not included, X levee, 1pct future conditions</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>True or False</edomv>
<edomvd>True for zones A, AE, AO, AH, AR, A99, V, VE, 1pct in channel, 1pct in culvert. False for X, 0.2pct in channel, 0.2pct in culvert, D, Area not included, X levee, 1pct future conditions</edomvd>
<edomvds>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<attalias Sync="TRUE">SFHATF</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>STATICBFE</attrlabl>
<attrdef>Static Base Flood Elevation value. For areas of constant base flood elevation (usually lakes and coastal zones), the BFE is shown beneath the zone label rather than on a BFE line. For these areas, the BFE value from the FIRM should be entered.</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>9999</edomv>
<edomvd>No static elevation</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attalias Sync="TRUE">STATICBFE</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>DEPTH</attrlabl>
<attrdef>Depth value. For AO zones, shown beneath the zone label on the FIRM. Usually a whole number between 1 - 3 feet.</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>9999</edomv>
<edomvd>No depth</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attalias Sync="TRUE">DEPTH</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>VEL</attrlabl>
<attrdef>Velocity. For Alluvial Fan areas, (some AO zones), shown beneath the zone label</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>9999</edomv>
<edomvd>No Velocity value</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attalias Sync="TRUE">VEL</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>VELUNITS</attrlabl>
<attrdef>Velocity units for Alluvial Fans and other OA zones</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>Null</edomv>
<edomvd>Velocity units for Alluvial Fans and other AO zones</edomvd>
<edomvds>NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<attalias Sync="TRUE">VELUNITS</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<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>20050617</edomv>
<edomvd>Creation date</edomvd>
<edomvds>Watershed Concepts</edomvds>
</edom>
</attrdomv>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attalias Sync="TRUE">VERDATE</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<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 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">Shape_Area</attrlabl>
<attalias Sync="TRUE">Shape_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Area of feature in internal units squared.</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>polygon 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>
<dssize Sync="TRUE">11.590</dssize>
</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">20070926</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Greenhorne &amp; O'Mara</cntorg>
<cntper>Kristel Whitson</cntper>
</cntorgp>
<cntpos>GIS Technician</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>5565 Centerview Drive, Suite 107</address>
<city>Raleigh</city>
<state>NC</state>
<postal>27606</postal>
</cntaddr>
<cntvoice>919-532-2331</cntvoice>
<cntfax>919-851-8393</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>
</metainfo>
<Esri>
<CreaDate>20200602</CreaDate>
<CreaTime>12564100</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20200605</SyncDate>
<SyncTime>15444900</SyncTime>
<ModDate>20200605</ModDate>
<ModTime>15444900</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">flood_zones</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.7'&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;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.020833333333333332&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="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">flood_zones</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">1572571.749829</westBL>
<eastBL Sync="TRUE">1697953.625146</eastBL>
<northBL Sync="TRUE">1022210.375126</northBL>
<southBL Sync="TRUE">914180.249842</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-80.454963</westBL>
<eastBL Sync="TRUE">-80.024406</eastBL>
<northBL Sync="TRUE">36.554148</northBL>
<southBL Sync="TRUE">36.253161</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>
<transSize Sync="TRUE">11.590</transSize>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">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="flood_zones">
<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">20200605</mdDateSt>
</metadata>
