FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: FEMA FLOOD INSURANCE RATE MAPS 1996 GAP COVERAGE FOR DFIRM FLDHAZ - MAY 2016 Geodataset Name: FEMA96_GAP_MAY16 Geodataset Type: SHAPEFILE Geodataset Feature: Polygon Feature Count: 10462 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): FEDERAL EMERGENCY MANAGEMENT AGENCY (FEMA) SCALE OF ORIGINAL SOURCE MAPS: 24000 GEODATASET EXTENT: State of Florida Counties: Palm Beach, Polk, and Sarasota. |
FEATURE ATTRIBUTE TABLES:
Datafile Name: FEMA96_GAP_MAY16.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
FIRM_PANEL
|
11 | String |
ZONE
|
5 | String |
FLOODWAY
|
5 | String |
COBRA
|
9 | String |
SFHA
|
3 | String |
GCID
|
4 | Integer |
DESCRIPT
|
25 | String |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
SHAPE.AREA
|
0 | Double |
SHAPE.LEN
|
0 | Double |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
FIRM_PANEL |
Eleven-digit alpha-numeric code identifies portion of community covered or not covered by a FIRM panel. Code comprises a unique alpha-numeric sequence based on FIPS and FEMA Community and Panel identification. |
|
ZONE |
Flood hazard zone designation. Multiple Codes refer to"Q3 Flood Data Specifications"
|
|
FLOODWAY |
Channel, river or watercourse reserved for flood discharge. Multiple Codes refer to "Q3 Flood Data Specifications". |
|
COBRA |
Undeveloped Coastal Barrier Area. Multiple Codes refer to "Q3 Flood Data Specifications". |
|
SFHA |
In/Out of flood zone designation, determined from data topology.
|
|
GCID |
Based on FEMA96 field: AUTOID |
|
DESCRIPT |
Field added by GeoPlan based on ZONE |
|
FGDLAQDATE |
Date GeoPlan downloaded the DFIRM_FLDHAZ _MAY16 layer from the Source. |
|
AUTOID |
Unique ID added by GeoPlan |
|
SHAPE.AREA |
Area in meters |
|
SHAPE.LEN |
Perimeter in meters |
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." |
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." |
GeoPlan relied on the integrity of the attribute information within the original data. |
|
These data are designed to provide a guidance and a general proximity of the locations of Special Flood Hazard Areas(SFHA) and zones of possible risks associated with food inundation. In addition to locational and topological information, features contained in the data set include 1%(100 year) and 0.2% (500 year) annual chance flood plain boundaries, flood insurance zone designations (including Velocity zones), flood way boundaries(when available), political boundaries(State, county and community), community and map panel identification number, FIRM panel neat lines, USGS 7.5-minute (1:24,000 scale) topographic map quadrangle neat lines, and Coastal Barrier Resource Act(COBRA) areas. |
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan |
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
NONE |
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html |
FEMA Flood Map Service Center https://msc.fema.gov/portal/advanceSearch |
The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers (2) Set Precision to DOUBLE (3) Set Tolerances to FGDL Standards (4) Added DESCRIPT based on ZONE Process Date: 20000000 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
FEMA 500 C Street, S.W. Washington, DC 20472 1-800-358-9691 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html