Keywords
Theme:
Map Flood Hazard Area, Floodplain Boundaries, 100 Year Flood, 500 Year Flood, 1% annual chance flood hazard, 0.2% annual chance flood hazard, DFIRM, Digital Flood Insurance Rate Map, FIRM, Flood Insurance Rate Map, Floodway, Riverine flooding, Special Flood Hazard Area, Coastal flooding
Place:
Union County, City of Monroe, City of Monroe Extraterritorial Jurisdiction, Town of Fairview, Town of Hemby Bridge, Town of Indian Trail, Town of Marshville, Town of Mineral Springs, Town of Mint Hill, Town of Stallings, Town of Unionville, Town of Waxhaw, Town of Weddington, Town of Wingate, Village of Lake Park, Village of Marvin, North Carolina
Description
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.
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.
_________________
Status of the data
Complete
Data update frequency: As needed
Data update frequency: As needed
Time period for which the data is relevant
Date and time:
20081016
Description:
publication date
Publication Information
Who created the data: North Carolina Floodplain Mapping Program, North Carolina Division of Emergency Management
Date and time:
20081016
Publisher and place:
North Carolina Floodplain Mapping Program, North Carolina Division of Emergency Management, Raleigh, NC
_________________
Data storage and access information
File name: gis_data.SDE.FEMA_2008
Type of data: vector digital data
Server=gis1; Service=5151; Database=gis_data; User=sde; Version=sde.DEFAULT
Data processing environment: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.3.1.1850
Type of data: vector digital data
Location of the data:
Accessing the data
Data format: ASCII
Data transfer size: 2.0-4.0 MB MB
How to decompress the file: PC-based PKZip compatible products (WinZip, unzip) may be used to decompress the dataset.
(To be determined)
Data transfer size: 2.0-4.0 MB MB
How to decompress the file: PC-based PKZip compatible products (WinZip, unzip) may be used to decompress the dataset.
Network location:
Constraints on accessing and using the data
Access constraints:
None
Use constraints:
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.
Details about this document
Contents last updated: 20090113
at time 17230400
Who completed this document
David Key
Watershed Concepts
mailing and physical address:
919-460-6895 (voice)
919-460-6896 (fax)
Watershed Concepts
mailing and physical address:
3333 Regency Parkway, Suite 120
Cary, NC 27511
919-460-6895 (voice)
919-460-6896 (fax)
Standards used to create this document
Standard name: FGDC Content Standards for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention used in this document: local time
Metadata profiles defining additonal information
ESRI Metadata Profile: http://www.esri.com/metadata/esriprof80.html
ESRI Metadata Profile: http://www.esri.com/metadata/esriprof80.html
Standard version: FGDC-STD-001-1998
Time convention used in this document: local time
Metadata profiles defining additonal information
Horizontal coordinate system
Projected coordinate system name: NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
Geographic coordinate system name: GCS_North_American_1983
Details
Map Projection Name: Lambert Conformal Conic
Standard Parallel: 34.333333
Standard Parallel: 36.166667
Longitude of Central Meridian: -79.000000
Latitude of Projection Origin: 33.750000
False Easting: 2000000.002617
False Northing: 0.000000
Standard Parallel: 36.166667
Longitude of Central Meridian: -79.000000
Latitude of Projection Origin: 33.750000
False Easting: 2000000.002617
False Northing: 0.000000
Planar Coordinate Information
Planar Distance Units: survey feet
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000244
Ordinate Resolution: 0.000244
Geodetic Model
Horizontal Datum Name: North American Datum of 1983
Ellipsoid Name: Geodetic Reference System 80
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257222
Altitude System Definition
Resolution: 1.000000
Encoding Method: Explicit elevation coordinate included with horizontal coordinates
_________________
Bounding coordinates
Horizontal
In decimal degrees
West:
-80.844755
East:
-80.271402
North:
35.208141
South:
34.808301
In projected or local coordinates
Left: 1448948.369718
Right: 1618409.145837
Top: 533135.010518
Bottom: 390259.473854
_________________
Lineage
FGDC lineage
Process step 1
Process description: 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.
For coastal floodplains, after analyzing wave heights along each transect, wave elevations were interpolated between transects. Various source data were used in the interpolation, including topographic data described above. Controlling features affecting the elevations were identified and considered in relation to their positions at particular transect and their variation between transects.
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.
Process date: Unknown
Process date: Unknown
Process step 2
Process description: Metadata imported.
Source used: C:\DOCUME~1\ebilici\LOCALS~1\Temp\xml1DD.tmp
Process date: 20090113 at time 15474100
Source used: C:\DOCUME~1\ebilici\LOCALS~1\Temp\xml1DD.tmp
Process date: 20090113 at time 15474100
Sources
Source 1:
MapFldHazAr
(MapFldHazAr)
Media: Shapefile
Contribution: 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. For coastal floodplains, after analyzing wave heights along each transect, wave elevations were interpolated between transects. Various source data were used in the interpolation, including topographic data described above. Controlling features affecting the elevations were identified and considered in relation to their positions at particular transect and their variation between transects. 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.
Contribution: 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. For coastal floodplains, after analyzing wave heights along each transect, wave elevations were interpolated between transects. Various source data were used in the interpolation, including topographic data described above. Controlling features affecting the elevations were identified and considered in relation to their positions at particular transect and their variation between transects. 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.
Currentness of this source
Date and time:
20081016
ESRI geoprocessing history
1. Process
Date and time:
20090113
at time 164936
Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\FeatureClassToFeatureClass
Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\FeatureClassToFeatureClass
Command issued
FeatureClassToFeatureClass "U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008" "Database Connections\Connection to gis1.sde\gis_data.SDE.Environmental" FEMA_2008 # "FLD_AR_ID 'FLD_AR_ID' true true false 25 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,FLD_AR_ID,-1,-1;HYDROID 'HYDROID' true true false 25 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,HYDROID,-1,-1;ZONE_LID 'ZONE_LID' true true false 5 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,ZONE_LID,-1,-1;FLDWAY_LID 'FLDWAY_LID' true true false 5 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,FLDWAY_LID,-1,-1;SFHA_TF 'SFHA_TF' true true false 2 Short 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,SFHA_TF,-1,-1;V_DATM_LID 'V_DATM_LID' true true false 5 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,V_DATM_LID,-1,-1;LEN_LID 'LEN_LID' true true false 5 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,LEN_LID,-1,-1;VEL_LID 'VEL_LID' true true false 5 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,VEL_LID,-1,-1;AR_REVERT 'AR_REVERT' true true false 6 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,AR_REVERT,-1,-1;CST_MDL_ID 'CST_MDL_ID' true true false 25 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,CST_MDL_ID,-1,-1;BFE_REVERT 'BFE_REVERT' true true false 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,BFE_REVERT,-1,-1;DEPTH 'DEPTH' true true false 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,DEPTH,-1,-1;DEP_REVERT 'DEP_REVERT' true true false 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,DEP_REVERT,-1,-1;STATIC_BFE 'STATIC_BFE' true true false 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,STATIC_BFE,-1,-1;VELOCITY 'VELOCITY' true true false 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,VELOCITY,-1,-1;METAID 'METAID' true true false 25 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,METAID,-1,-1;SHAPE_Length 'SHAPE_Length' false true true 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,SHAPE_Length,-1,-1;SHAPE_Area 'SHAPE_Area' false true true 8 Double 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,SHAPE_Area,-1,-1;Label 'Label' true true false 50 Text 0 0 ,First,#,U:\environmental\PrelimFEMA\Data\1_12_09 Revised by GIS\Union_Final_Effective_PGDB.mdb\MAPPING\FEMA2008,Label,-1,-1" # "Database Connections\Connection to gis1.sde\gis_data.SDE.Environmental\gis_data.SDE.FEMA_2008"
_________________
Spatial data description
Vector data information
ESRI description
gis_data.SDE.FEMA_2008
ESRI feature type: Simple
Geometry type: Polygon
Topology: FALSE
Feature count: 737
Spatial Index: TRUE
Linear referencing: FALSE
Geometry type: Polygon
Topology: FALSE
Feature count: 737
Spatial Index: TRUE
Linear referencing: FALSE
SDTS description
gis_data.SDE.FEMA_2008:
G-polygon, 737
Feature class: SDTS feature type, feature count
Details for gis_data.SDE.FEMA_2008
Type of object: Feature Class
Number of records: 737
Description
Polygon Geometry file that is the physical representation of the Flood Mapping Boundaries that are calculated from the Engineering Models
Source: NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)
Source: NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)
Attributes
OBJECTID
Alias: OBJECTID
Data type: OID
Width: 4
Precision: 10
Scale: 0
Definition:
Data type: OID
Width: 4
Precision: 10
Scale: 0
Definition:
Internal feature number.Definition Source:
ESRI
Shape
Alias: Shape
Data type: Geometry
Width: 4
Precision: 0
Scale: 0
Definition:
Data type: Geometry
Width: 4
Precision: 0
Scale: 0
Definition:
Feature geometry.Definition Source:
ESRI
FLD_AR_ID
Alias: FLD_AR_ID
Data type: String
Width: 25
Precision: 0
Scale: 0
Data type: String
Width: 25
Precision: 0
Scale: 0
HYDROID
Alias: HYDROID
Data type: String
Width: 25
Precision: 0
Scale: 0
Data type: String
Width: 25
Precision: 0
Scale: 0
ZONE_LID
Alias: ZONE_LID
Data type: String
Width: 5
Precision: 0
Scale: 0
Data type: String
Width: 5
Precision: 0
Scale: 0
FLDWAY_LID
Alias: FLDWAY_LID
Data type: String
Width: 5
Precision: 0
Scale: 0
Data type: String
Width: 5
Precision: 0
Scale: 0
SFHA_TF
Alias: SFHA_TF
Data type: SmallInteger
Width: 2
Precision: 5
Scale: 0
Data type: SmallInteger
Width: 2
Precision: 5
Scale: 0
V_DATM_LID
Alias: V_DATM_LID
Data type: String
Width: 5
Precision: 0
Scale: 0
Data type: String
Width: 5
Precision: 0
Scale: 0
LEN_LID
Alias: LEN_LID
Data type: String
Width: 5
Precision: 0
Scale: 0
Data type: String
Width: 5
Precision: 0
Scale: 0
VEL_LID
Alias: VEL_LID
Data type: String
Width: 5
Precision: 0
Scale: 0
Data type: String
Width: 5
Precision: 0
Scale: 0
AR_REVERT
Alias: AR_REVERT
Data type: String
Width: 6
Precision: 0
Scale: 0
Data type: String
Width: 6
Precision: 0
Scale: 0
CST_MDL_ID
Alias: CST_MDL_ID
Data type: String
Width: 25
Precision: 0
Scale: 0
Data type: String
Width: 25
Precision: 0
Scale: 0
BFE_REVERT
Alias: BFE_REVERT
Data type: Double
Width: 8
Precision: 38
Scale: 8
Data type: Double
Width: 8
Precision: 38
Scale: 8
METAID
Alias: METAID
Data type: String
Width: 25
Precision: 0
Scale: 0
Definition:
Data type: String
Width: 25
Precision: 0
Scale: 0
Definition:
Foreign key, link to Metadata table should be the same as for the flood hazard linesDefinition Source:
NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)
DEP_REVERT
Alias: DEP_REVERT
Data type: Double
Width: 8
Precision: 38
Scale: 8
Data type: Double
Width: 8
Precision: 38
Scale: 8
STATIC_BFE
Alias: STATIC_BFE
Data type: Double
Width: 8
Precision: 38
Scale: 8
Data type: Double
Width: 8
Precision: 38
Scale: 8
VELOCITY
Alias: VELOCITY
Data type: Double
Width: 8
Precision: 38
Scale: 8
Data type: Double
Width: 8
Precision: 38
Scale: 8
DEPTH
Alias: DEPTH
Data type: Double
Width: 8
Precision: 38
Scale: 8
Definition:
Data type: Double
Width: 8
Precision: 38
Scale: 8
Definition:
Depth value. For AO zones, shown beneath the zone label on the FIRM. Usually a whole number between 1 - 3 feet.Definition Source:
NC-FMIS Database Design Review and Physical Model (State of North Carolina, North Carolina Floodplain Mapping Program, September 2002)
Label
Alias: Label
Data type: String
Width: 50
Precision: 0
Scale: 0
Data type: String
Width: 50
Precision: 0
Scale: 0
Shape.area
Alias: Shape.area
Data type: Double
Width: 0
Precision: 0
Scale: 0
Data type: Double
Width: 0
Precision: 0
Scale: 0
Shape.len
Alias: Shape.len
Data type: Double
Width: 0
Precision: 0
Scale: 0
Data type: Double
Width: 0
Precision: 0
Scale: 0