Federal Emergency Management Agency
20201021
Digital Flood Insurance Rate Map (DFIRM) in the State of Florida - 500 Year Floodplain - October 2020
NFHL Florida Data Product ID: NFHL_12_20201021, ESRI FGDB
raster digital data
500 C Street SW, Washington, DC, 20472, US
Federal Emergency Management Agency
State of Florida
https://msc.fema.gov/portal/advanceSearch
This is a raster data set with a 10-meter cell size based on the DFIRM_FLDHAZ vector layer. This layer represents area within or outside 500 year floodplain.
This raster layer is based off the vector layer DFIRM_FLDHAZ and is used to increase performance with ETDM analysis.
What Is an LFD? A Letter of Final Determination (LFD) is a letter the Federal Emergency Management Agency (FEMA) sends to the Chief Executive Officer of a community stating that a new or updated Flood Insurance Rate Map (FIRM) or Digital Flood Insurance Rate Map (DFIRM) will become effective in 6 months. The letter also notifies each affected flood prone community participating in the National Flood Insurance Program (NFIP) that it must adopt a compliant floodplain management ordinance by the map effective date to remain participants in good standing in the NFIP. DFIRM [S_FIRM_Pan] Panel Summary Table of Effective Date
--------------------------------------------------------------------------------
DFIRM_ID EFF_DATE COUNTY PANEL_CNT NOTES
12001C, 11/2/18, ALACHUA COUNTY, 12 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12001C, 6/16/06, ALACHUA COUNTY, 100 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12003C, 6/17/08, BAKER COUNTY, 75
12005C, 6/2/09, BAY COUNTY, 168
12007C, 11/2/18, BRADFORD COUNTY, 16 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12007C, 5/2/12, BRADFORD COUNTY, 23 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12009C, 3/17/14, BREVARD COUNTY, 143
12011C, 8/18/14, BROWARD COUNTY, 103
12013C, 6/18/13, CALHOUN COUNTY, 62
12015C, 5/5/03, CHARLOTTE COUNTY, 123
12017C, 9/26/14, CITRUS COUNTY, 154
12019C, 3/17/14, CLAY COUNTY, 60
12021C, 5/16/12, COLLIER COUNTY, 156
12023C, 11/2/18, COLUMBIA COUNTY, 35 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12023C, 2/4/09, COLUMBIA COUNTY, 84 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12027C, 11/6/13, DESOTO COUNTY, 88
12029C, 1/18/19, DIXIE COUNTY, 80 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12029C, 4/18/18, DIXIE COUNTY, 26 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12029C, 9/29/06, DIXIE COUNTY, 29 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12029C, 9/9/99, DIXIE COUNTY, 1 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12031C, 11/2/18, DUVAL COUNTY, 104 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12031C, 6/3/13, DUVAL COUNTY, 76 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12033C, 9/29/06, ESCAMBIA COUNTY, 104
12035C, 6/6/18, FLAGLER COUNTY, 67
12037C, 2/5/14, FRANKLIN COUNTY, 59
12039C, 2/4/09, GADSDEN COUNTY, 87
12041C, 1/19/18, GILCHRIST COUNTY, 28 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12041C, 9/29/06, GILCHRIST COUNTY, 45 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12043C, 3/6/20, GLADES COUNTY, 44 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12043C, 9/26/14, GLADES COUNTY, 41 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12045C, 4/16/09, GULF COUNTY, 8 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12045C, 9/28/07, GULF COUNTY, 85 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12047C, 6/4/10, HAMILTON COUNTY, 41 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12047C, 8/28/18, HAMILTON COUNTY, 5 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12047C, 9/4/20, HAMILTON COUNTY, 21 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12049C, 11/6/13, HARDEE, 96
12051C, 5/15/20, HENDRY COUNTY, 15 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12051C, 7/6/15, HENDRY COUNTY, 45 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12053C, 2/2/12, HERNANDO COUNTY, 151
12055C, 11/18/15, HIGHLANDS COUNTY, 159
12057C, 8/28/08, HILLSBOROUGH COUNTY, 234 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12057C, 9/27/13, HILLSBOROUGH COUNTY, 4 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12059C, 12/17/10, HOLMES COUNTY, 44
12061C, 12/4/12, INDIAN RIVER COUNTY, 70
12063C, 12/17/10, JACKSON COUNTY, 70
12065C, 2/5/14, JEFFERSON COUNTY, 21
12067C, 10/5/17, LAFAYETTE COUNTY, 18 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12067C, 9/29/06, LAFAYETTE COUNTY, 56 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12069C, 12/18/12, LAKE COUNTY, 94
12071C, 12/7/18, LEE COUNTY, 20 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12071C, 8/28/08, LEE COUNTY, 156 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12073C, 8/18/09, LEON COUNTY, 86
12075C, 1/18/19, LEVY COUNTY, 52 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12075C, 11/2/12, LEVY COUNTY, 61 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12075C, 2/3/17, LEVY COUNTY, 5 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12075C, 9/9/99, LEVY COUNTY, 2 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12077C, 6/18/13, LIBERTY COUNTY, 26
12079C, 2/3/17, MADISON COUNTY, 5 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12079C, 5/3/10, MADISON COUNTY, 72 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12079C, 9/4/20, MADISON COUNTY, 32 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12081C, 3/17/14, MANATEE COUNTY, 137
12083C, 3/17/14, MARION COUNTY, 6 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12083C, 4/19/17, MARION COUNTY, 64 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12083C, 8/28/08, MARION COUNTY, 148 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12085C, 2/19/20, MARTIN COUNTY, 46 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12085C, 3/16/15, MARTIN COUNTY, 32 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12086C, 9/11/09, MIAMI-DADE COUNTY, 251
12087C, 2/18/05, MONROE COUNTY, 183
12089C, 12/17/10, NASSAU COUNTY, 62 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12089C, 8/2/17, NASSAU COUNTY, 61 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12091C, 12/6/02, OKALOOSA COUNTY, 74
12093C, 7/16/15, OKEECHOBEE COUNTY, 42
12095C, 6/20/18, ORANGE COUNTY, 6 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12095C, 9/25/09, ORANGE COUNTY, 56 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12097C, 6/18/13, OSCEOLA COUNTY, 66
12099C, 10/5/17, PALM BEACH COUNTY, 218
12101C, 6/5/20, PASCO COUNTY, 31 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12101C, 9/26/14, PASCO COUNTY, 145 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12103C, 5/17/05, PINELLAS COUNTY, 6 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12103C, 8/18/09, PINELLAS COUNTY, 6 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12103C, 9/3/03, PINELLAS COUNTY, 123 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12105C, 12/22/16, POLK COUNTY, 108 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12105C, 9/28/12, POLK COUNTY, 16 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12107C, 2/2/12, PUTNAM COUNTY, 105
12109C, 12/7/18, ST. JOHNS COUNTY, 128
12111C, 2/16/12, ST. LUCIE COUNTY, 38 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12111C, 2/19/20, ST. LUCIE COUNTY, 43 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12113C, 12/19/06, SANTA ROSA COUNTY, 143
12115C, 11/4/16, SARASOTA COUNTY, 141
12117C, 9/28/07, SEMINOLE COUNTY, 38
12119C, 6/5/20, SUMTER COUNTY, 40 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12119C, 9/27/13, SUMTER COUNTY, 115 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12121C, 2/3/17, SUWANNEE COUNTY, 10 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12121C, 4/16/13, SUWANNEE COUNTY, 12 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12121C, 8/28/18, SUWANNEE COUNTY, 3 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12121C, 9/28/07, SUWANNEE COUNTY, 113 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12123C, 2/1/19, TAYLOR COUNTY, 79 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12123C, 5/4/09, TAYLOR COUNTY, 50 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12125C, 11/2/18, UNION COUNTY, 8 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12125C, 2/4/09, UNION COUNTY, 34 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12127C, 2/19/14, VOLUSIA COUNTY, 59 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12127C, 9/29/17, VOLUSIA COUNTY, 66 (COUNTY WITH MULTIPLE EFFECTIVE DATES)
12129C, 9/26/14, WAKULLA COUNTY, 29
12131C, 9/29/10, WALTON COUNTY, 157
12133C, 7/4/11, WASHINGTON COUNTY, 37
Please Note: This table was created by adding the Study_info table's CNTY_NM field to the S_FIRM_Pan field via a table join based on DFIRM_ID. EFF_DATE_SUM = [DFIRM_ID] & " " & [EFF_DATE] & " " & [CNTY_NM]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
** What is a "100-year flood" and how is it different from a "1-percent-annual-chance flood" or a "base flood?" ** The term "100-year flood" is misleading. It is not the flood that will occur once every 100 years. Rather, it is the flood that has a 1-percent chance of being equaled or exceeded each year. Thus, the 100-year flood could occur more than once in a relatively short period of time or even within the same month. Because this term is misleading, FEMA has also defined it as the "1-percent-annual-chance flood." The "1-percent-annual-chance flood" is the term that is now used by most federal and state agencies and by the National Flood Insurance Program. SOURCE: https://www.fema.gov/frequently-asked-questions/insurance-professionals-lenders-frequently-asked-questions
--------------------------------------------------------------------------------
** The following FEMA DFIRM information is from the frm_gsalb.pdf ** Table: S_Fld_Haz_Ar This table is required for all draft Digital Flood Insurance Rate Map data. The S_Fld_Haz_Ar table contains information about the flood hazards within the study area. A spatial file with locational information also corresponds with this data table. These zones are used by the federal Emergency Management Agency (FEMA) to designate the Special Flood Hazard Area (SFHA) and for insurance rating purposes. These data are the flood hazard areas that are or will be depicted on the Flood Insurance Rate Map (FIRM). A spatial file with locational information also corresponds with this data table. The spatial elements representing the flood zones are polygons. The entire area of the jurisdiction(s) mapped by the FIRM should have a corresponding flood zone polygon. There is one polygon for each contiguous flood zone designated. This is a modified Standard DFIRM Database table that includes Standard DFIRM Database items and Enhanced Database items. All items after SOURCE_CIT are Enhanced. Table: D_Zone Where the 1-percent-annual-chance flood or the 0.2-percent-annual-chance flood is contained in a culvert or channel, a corresponding feature appears in the S_Fld_Haz_Ar table only if an SFHA or 0.2-percent-annual-chance flood zone is shown on the FIRM in this area. In general, these culverts and channels are to be represented in the general structure table regardless of how the flood insurance risk zones are depicted. So, if these structures are shown on the FIRM as a dashed line passing through a Zone X, no corresponding flood insurance risk zone is shown in S_Fld_Haz_Ar table in the DFIRM database. If a narrow SFHA or 0.2-percent-annual-chance flood zone is shown on the FIRM, then a narrow polygon must be included in the DFIRM database. If the width of this flood insurance risk zone is accurately known and represented in the spatial data, the normal flood insurance risk zone is applied. If the width of the flood insurance risk zone is not accurately known and represented because of scale limitations, then the zone is designated as 1-percent-annual-chance flood contained in channel or 0.2-percent-annual-chance flood contained in channel as appropriate. ZONE_LID FLD_ZONE 1000 A 1001 AE 1002 AH 1003 AO 1004 AR 1005 1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL 1006 1 PCT FUTURE CONDITIONS 1007 A99 1008 V 1009 VE 2000 0.2 PCT ANNUAL CHANCE FLOOD HAZARD 2001 0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL 3000 AREA NOT INCLUDED 4000 D 4001 X PROTECTED BY LEVEE 4002 X 5000 OPEN WATER Flood Zone. This is the flood insurance risk zone designation. These zones are used by the Federal Emergency Management Agency (FEMA) to designate Special Flood Hazard Areas (SFHAs) and for insurance rating purposes. Some older FEMA FIRMs were prepared in the Standard format that uses Zones B, C and numbered A and V zones. Newer FIRMs use the Map Initiatives format where the B corresponds to 0.2 pct ANNUAL CHANCE FLOOD HAZARD; C corresponds to Zone X; numbered A zones (e.g., A1, A2, A3) correspond to Zone AE; and numbered V zones (e.g., V1, V2, V3) correspond to Zone VE. All Digital Flood Insurance Rate Maps (DFIRMs) should use the Map Initiatives zone designations. See Volume 1, Subsection 1.4.6.1.5 of these Guidelines for details on the flood insurance risk zones. (NOTE: The symbol '%' is a reserved symbol in most software packages so the word 'percent' was abbreviated to 'pct'.) Table: D_Floodway FLDWAY_LID FLOODWAY 1000 FLOODWAY 1010 COLORADO RIVER 1020 FLOODWAY CONTAINED IN CHANNEL 1030 FLOWAGE EASEMENT BOUNDARY 1040 STATE ENCROACHMENT 1050 AREA OF SPECIAL CONSIDERATION Table: D_Length_Units LEN_LID LEN_UNIT 1000 CENTIMETERS 1010 FEET 1020 INCHES 1030 KILOMETERS 1040 METERS 1050 MILES 1060 MILLIMETERS Table: D_Velocity_Units VEL_LID VEL_UNIT 1000 CENTIMETERS / DAY 1010 CENTIMETERS / HOUR 1020 FEET / SECOND 1030 INCHES / DAY 1040 INCHES / HOUR 1050 METERS / SECOND 1060 MICROMETERS / SECOND 1070 MILLIMETERS / DAY 1080 MILLIMETERS / HOUR
--------------------------------------------------------------------------------
20010606
20201021
publication date
As needed
-87.639269
-79.870652
31.042672
24.472142
None
FEMA Flood Hazard Zone
NFIP
inlandWaters
Digital Flood Insurance Rate Map
Riverine flooding
Special Flood Hazard Area
Flood Insurance Rate Map
FLOOD
SFHA
DFIRM Database
DFIRM
FEMA
environment
FLOOD HAZARD
Floodway
FIRM
ISO 19115 Topic Category
inlandWaters
None
Florida
None
20201021
2020
None
FEMA Disclaimer: No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty. FEMA will warrant the delivery of this product in a computer-readable format, and will offer appropriate adjustment of credit when the product is determined unreadable by correctly adjusted computer input peripherals, or when the physical medium is delivered in damaged condition. Requests for adjustment of credit must be made within 90 days from the date of this shipment from the ordering site. The hardcopy FIRM and FIRM Database and the accompanying FIS are the official designation of SFHAs and Base Flood Elevations (BFEs) for the NFIP. For the purposes of the NFIP, changes to the flood risk information published by FEMA may only be performed by FEMA and through the mechanisms established in the NFIP regulations (44 CFR Parts 59-78). These digital data are produced in conjunction with the hardcopy FIRMs and generally match the hardcopy map exactly. Acknowledgement of FEMA would be appreciated in products derived from these data.
Federal Emergency Management Agency
Federal Insurance and Mitigation Administration
mailing
500 C Street SW
Washington
DC
20472
US
(202) 646-2500
www.msc.fema.gov
FEMA
Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595
Federal Emergency Management Agency
20201021
NFHL Data-State (FL)
vector digital data
500 C Street SW, Washington, DC, 20472, US
Federal Emergency Management Agency
FEMA Flood Map Service Center https://msc.fema.gov/portal/advanceSearch FEMA FIRM Database Technical Reference (available in the FEMA Library at https://www.fema.gov/media-library/assets/documents/34519).
GeoPlan relied on the integrity of the attribute information within the original data.
When FEMA revises an FIS, adjacent studies are checked to ensure agreement between flood elevations at the boundaries. Likewise flood elevations at the confluence of streams studied independently are checked to ensure agreement at the confluence. The FIRM and the FIS are developed together and care is taken to ensure that the elevations and other features shown on the flood profiles in the FIS agree with the information shown on the FIRM. However, the elevations as shown on the FIRM are rounded whole-foot elevations. They must be shown so that a profile recreated from the elevations on the FIRM will match the FIS profiles within one half of one foot.
Data contained in the NFHL reflects the content of the source materials. Features may have been eliminated or generalized on the source graphic, due to scale and legibility constraints. With new mapping, FEMA plans to maintain full detail in the spatial data it produces. However, older information is often transferred from existing maps where some generalization has taken place. Flood risk data are developed for communities participating in the NFIP for use in insurance rating and for floodplain management. Flood hazard areas are determined using statistical analyses of records of river flow, storm tides, and rainfall; information obtained through consultation with the communities; floodplain topographic surveys; and hydrological and hydraulic analysis. Generally, regulatory water surface elevations and/or regulatory floodways are published only for developed or developing areas of communities. For areas where little or no development is expected to occur, FEMA may generate flood risk data without published water surface elevations. Typically, only drainage areas that are greater than one square mile and with an average of one foot of flood depth or greater are studied. Note: The NFHL reflects the most current information available when the distribution data set was created. Currently, not all areas of a State or Territory have effective FIRM Database data. As a result, users may need to refer to the effective FIRM for effective flood hazard information.
The NFHL consists of vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and FIRM Database are issued as the official designation of the SFHAs. As such they are adopted by local communities and form the basis for administration of the NFIP. For these purposes they are authoritative. Provisions exist in the regulations for public review, appeals and corrections of the flood risk information shown to better match real world conditions. As with any engineering analysis of this type, variation from the estimated flood heights and floodplain boundaries is possible. Details of FEMA's requirements for the FISs and flood mapping process that produces these data are available in the Guidelines and Standards for Flood Risk Analysis and Mapping. Horizontal accuracy was tested by manual comparison of source graphics with hardcopy plots and a symbolized display on an interactive computer graphic system. Independent quality control testing of the individual FIRM Database components of the NFHL was also performed.
The NFHL consists of vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and FIRM Database are issued as the official designation of the SFHAs. As such they are adopted by local communities and form the basis for administration of the NFIP. For these purposes they are authoritative. Provisions exist in the regulations for public review, appeals and corrections of the flood risk information shown to better match real world conditions. As with any engineering analysis of this type, variation from the estimated flood heights and floodplain boundaries is possible. Details of FEMA's requirements for the FISs and flood mapping process that produces these data are available in the Guidelines and Standards for Flood Risk Analysis and Mapping. The reliability of the floodplain boundary delineation is quantified by comparing the computed flood elevation to the ground elevation at the mapped floodplain boundary. The tolerance for how precisely the flood elevation and the ground elevation must match varies based on the flood risk class, which is a function of population, population density, and/or anticipated growth in floodplain areas. A horizontal accuracy of +/- 38 feet is used to determine the compliance with the vertical tolerances defined for each risk class. The range of differences between the ground elevation (defined from the topographic data used for the Flood Risk Project) and the computed flood elevation is between +/- 1.0 foot at the 95% confidence interval for areas with high population within the floodplain and/or high anticipated growth and Special Flood Hazard Areas (SFHAs) with high flood risk to +/- one-half the contour interval at the 85% confidence interval for areas with low population and densities within the floodplain and small or no anticipated growth and SFHAs with low flood risk. Independent quality control testing of the individual FIRM Database components of the NFHL was also performed.
Federal Emergency Management Agency
20201021
Digital Flood Insurance Rate Map
vector digital data
Washington, D.C.
Federal Emergency Management Agency
National Flood Hazard Layer
https://msc.fema.gov
12000
onLine
20201021
USA
FEMA
Spatial and Attribute Information
The NFHL dataset is a compilation of effective FIRM Databases (a collection of the digital data that are used in GIS systems for creating new Flood Insurance Rate Maps) and Letters of Map Change (Letters of Map Amendment and Letters of Map Revision only) that create a seamless GIS data layer for a State or Territory. It is updated on a monthly basis. The FIRM Databases are compiled in conjunction with the hardcopy FIRMs and the final FIS reports. The specifics of the hydrologic and hydraulic analyses performed are detailed in the FIS reports available for each jurisdiction. The results of these studies are submitted in digital format to FEMA. These data and unrevised data from effective FIRMs are compiled onto the base map used for FIRM publication and checked for accuracy and compliance with FEMA standards. As new FIRM Databases are received the individual FIRM layers are sewn into the nationwide layers of the NFHL. LOMRs for the FIRM Databases in the NFHL are cut directly into the NFHL data layers as they are being produced and finalized.
FEMA
20201021
The GeoPlan Center downloaded the Statewide National Flood Hazard Layer from the following FEMA website on October 30th, 2020.
FEMA Flood Map Service Center
https://msc.fema.gov/portal Search All Products https://msc.fema.gov/portal/advanceSearch
Choose one of the three search options below and optionally enter a posting date range.
https://msc.fema.gov/portal/advanceSearch
State -FLORIDA
County - ALACHUA
Community - ALACHUA
Search Effective Products
NFHL Data-State(1) Product ID
Product ID: NFHL_12_20201021
Latest Study Effective Date: 09/04/2020
Latest LOMR Effective Date: 10/22/2020
Size Download: 2425MB
DL:Download Product NFHL_12_20201021
NFHL_12_20201021.zip
NFHL_12_20201021.gdb
Feature Layer: S_Fld_Haz_Ar
The S_Fld_Haz_Ar was originally in the following projection: GCS_North_American_1983 WKID: 4269 Authority: EPSG Angular Unit: Degree (0.0174532925199433) Prime Meridian: Greenwich (0.0) Datum: D_North_American_1983 Spheroid: GRS_1980 Semimajor Axis: 6378137.0 Semiminor Axis: 6356752.314140356 Inverse Flattening: 298.257222101
The dataset was projected to the FGDL Albers HARN projection using the following Transformation:
NAD_1983_To_HARN_Florida
The dataset was renamed to dfirm_fldhaz_oct20.
Next the following fields were added and populated:
PRODUCT_ID = "NFHL_12_20201021"
FLOODPLAIN = See Crosswalk Table Below
RISK_LEVEL = See Crosswalk Table Below
FHZ_LABEL = See Crosswalk Table 2 Below
DESCRIPT = [SFHA_TF] field Description [SFHA_TF] = "T" : INSIDE SPECIAL FLOOD HAZARD AREA [SFHA_TF] = "F" : OUTSIDE SPECIAL FLOOD HAZARD AREA
FGDLAQDATE = "10/30/2020"
AUTOID = OBJECTID
Crosswalk Table
This crosswalk table was used to populate the FLOODPLAIN and
RISK_LEVEL fields.
The crosswalk table / shapefile join was based on the FLDZ field
in the table and the FLDZONE field within the shapefile.
FLDZ FDLZ_DSCPT FLOODPLAIN
B MODERATE TO LOW RISK AREAS OUTSIDE FLOODPLAIN
C MODERATE TO LOW RISK AREAS OUTSIDE FLOODPLAIN
X MODERATE TO LOW RISK AREAS OUTSIDE FLOODPLAIN
A HIGH RISK AREAS 100-YEAR FLOODPLAIN
AE HIGH RISK AREAS 100-YEAR FLOODPLAIN
A1 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A2 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A3 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A4 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A5 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A6 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A7 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A8 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A9 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A10 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A11 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A12 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A13 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A14 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A15 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A16 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A17 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A18 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A19 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A20 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A21 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A22 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A23 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A24 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A25 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A26 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A27 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A28 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A29 HIGH RISK AREAS 100-YEAR FLOODPLAIN
A30 HIGH RISK AREAS 100-YEAR FLOODPLAIN
AH HIGH RISK AREAS 100-YEAR FLOODPLAIN
AO HIGH RISK AREAS 100-YEAR FLOODPLAIN
AR HIGH RISK AREAS 100-YEAR FLOODPLAIN
A99 HIGH RISK AREAS 100-YEAR FLOODPLAIN
D UNDETERMINED UNDETERMINED
V HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
VE HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V1 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V2 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V3 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V4 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V5 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V6 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V7 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V8 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V9 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V10 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V11 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V12 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V13 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V14 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V15 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V16 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V17 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V18 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V19 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V20 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V21 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V22 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V23 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V24 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V25 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V26 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V27 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V28 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V29 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
V30 HIGH RISK - COASTAL AREAS 100-YEAR FLOODPLAIN
OPEN WATER OPEN WATER OPEN WATER
A second calculation was done for the following where FLD_ZONE = X and field ZONE_SUBTY combinations existed, see below.
0.2 PCT* MODERATE RISK AREAS 500-YEAR FLOODPLAIN
1 PCT DEPTH LESS THAN 1 FOOT MODERATE RISK AREAS 500-YEAR FLOODPLAIN
AREA WITH REDUCED FLOOD RISK DUE TO LEVEE MODERATE RISK AREAS 500-YEAR FLOODPLAIN
Crosswalk Table 2
This crosswalk table was used to populate the FHZ_LABEL field.
Text description of flood zones for map legends based on the FLD_ZONE and ZONE_SUBTY fields
Calculated Zone Descriptions for field FLD_ZONE = A, AE, AH, AO, AR, A99, V and VE as 1% ANNUAL CHANCE FLOOD HAZARD
Calculated Zone Descriptions for field FLD_ZONE = AREA NOT INCLUDED as AREA NOT INCLUDED
Calculated Zone Descriptions for field FLD_ZONE = D as AREA OF UNDETERMINED FLOOD HAZARD
Calculated Zone Descriptions for field FLD_ZONE = OPEN WATER as OPEN WATER
Next
Calculated Zone Descriptions for field ZONE_SUBTY =
0.2 PCT ANNUAL CHANCE FLOOD HAZARD as 0.2% ANNUAL CHANCE FLOOD HAZARD
0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL as 0.2% ANNUAL CHANCE FLOOD HAZARD
1 PCT DEPTH LESS THAN 1 FOOT as 0.2% ANNUAL CHANCE FLOOD HAZARD
AREA OF MINIMAL FLOOD HAZARD as AREA OF MINIMAL FLOOD HAZARD
AREA WITH REDUCED FLOOD RISK DUE TO LEVEE as AREA WITH REDUCED RISK DUE TO LEVEE
FLOODWAY as REGULATORY FLOODWAY
RIVERINE FLOODWAY SHOWN IN COASTAL ZONE as REGULATORY FLOODWAY
- It was noted that sliver polygons existed (primarily in Charlotte County). However, no methodology was performed by GeoPlan to correct for these issues. For more information on FEMA's Final Data Structure concerning sliver polygons please see below. The FEMA report frm_gsal.pdf states the following regarding sliver polygons. L.3.5.2 Topology Vector data files must meet the following data structure requirements: * Area spatial features for a given theme must cover the entire study area without overlaps, underlaps or sliver polygons between adjacent polygons.
- Next Deleted the following 3 features due to spatial errors:
* 12059C_235984 (Duplicate Polygon),
* 12111C_1676 (Zero Area),
* 12097C_1170 (Negative Area).
- It was noted that over 100 features had vertex counts greater than 350,000.
Features with large vertex counts are known to cause database analysis crashes and errors. The ArcGIS Dice Tool subdivides a feature into smaller features based on a specified vertex limit. This tool is intended as a way to subdivide extremely large features that cause issues with drawing, analysis, editing, and/or performance but are difficult to split up with standard editing and geoprocessing tools. This tool should not be used in any cases other than those where tools are failing to complete successfully due to the size of features.
Source: https://desktop.arcgis.com/en/arcmap/latest/tools/data-management-toolbox/dice.htm
-The features were subdivided using the ArcGIS Dice Tool with a vertex limit of 350,000.
- Duplicate features/records were found in the following county; Brevard County, this duplication impacted the following datasets; BFE, FLDHAZ & PANEL.
- First GeoPlan reviewed the duplicate features where the dataset specific unique id count was greater than 1.
- Dataset specific unique ids are as follows: - BFE = BFE_FN_ID - CBRS = CBRS_ID - FLDHAZ = FLD_AR_ID - PANEL = FIRM_ID
- Summarized on Dataset specific unique ids with MAX and Min boxes check for AUTOID and AREA.
- Exported the duplicates and checked to make sure the areas of each suspect duplicate matched (they did).
- Joined this table back to the full dataset on the Max AUTOID field.
- Ran a selection to grab just these records where the Max AUTOID matched.
- Ran Switch selection set and exported out the full dataset without the extra duplicate records.
- This process was used to clean all three datasets impacted.
GeoPlan
20201030
Raster
GT-polygon composed of chains
413504
Grid Cell
coordinate pair
0.000000004429812072714868
0.000000004429812072714868
meter
D North American 1983 HARN
GRS 1980
6378137.0
298.257222101
DFIRM_FLDHAZ_OCT20
DFIRM_FLDHAZ_OCT20.DBF
FEMA
Table6
OIDOIDOID400Internal feature number.EsriSequential unique whole numbers that are automatically generated.
VALUE
VALUEInteger10100
COUNT
COUNTDouble19188
REDREDDouble19188GREENGREENDouble19188BLUEBLUEDouble19188OPACITYOPACITYDouble19188
The DFIRM Database is made up of several data themes containing both spatial
and attribute information. These data together represent the current flood risk for the
subject area as identified by FEMA. The attribute tables include SFHA locations,
flood zone designations, BFEs, political entities, cross-section locations, FIRM panel
information, and other data related to the NFIP.
Table containing attribute information associated with the data set.
FEMA FIRM Database Technical Reference
(available in the FEMA Library at http://www.fema.gov/media-library/assets/documents/34519).
Appendix L of FEMA's Guidelines and Specifications for FEMA Flood Hazard
Mapping Partners contains a detailed description of each attribute code and a
reference to other relevant information. The following tables are included in this data
set: l_comm_info l_stn_start study_info s_bfe s_base_index s_firm_pan
s_fld_haz_ar s_fld_haz_ln s_gen_struct s_label_ld s_perm_bmk s_pol_ar s_pol_ln
s_quad_index s_wtr_ln s_xs s_label_pt
Attribute Definition Information can be found in the following reference:
FEMA FIRM Database Technical Reference (available in the FEMA Library at
http://www.fema.gov/media-library/assets/documents/34519)
Florida Geographic Data Library (FGDL)
mailing
431 Architecture PO Box 115706
Gainesville
Florida
32611-5706
US
Web site: https://www.fgdl.org
FGDL Frequently Asked Questions: https://www.fgdl.org/metadataexplorer/help.html
Technical Support: data@fgdl.org
Software Support: https://www.geoplan.ufl.edu/software/
DOWNLOADABLE DATA
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: https://www.geoplan.ufl.edu/
Vector Digital Data Set (Polygon)
www.fgdl.org
DOWNLOADABLE DATA
Contact Distributor
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
20210209
Federal Emergency Management Agency
Flood Map Service Center
Federal Insurance and Mitigation Administration
mailing
500 C Street SW
Washington
DC
20472
US
1-800-358-9616
www.msc.fema.gov
FGDC Content Standard for Digital Geospatial Metadata
FGDC-STD-001-1998
local time
Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362dfirm_500_oct20.tif1-87.639272-79.87064931.04276224.472142dfirm_500_oct20.tiffile://D:\FGDL\fk_fgdl_id\to_resolve\rasters\rasters_need_meta\DFIRM_2020\dfirm_500_oct20.tifLocal Area Network00252663.337344794143.33734458526.197344781596.1973441ProjectedGCS_North_American_1983_HARNLinear Unit: Meter (1.000000)NAD_1983_HARN_Florida_GDL_Albers<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.8'><WKT>PROJCS["NAD_1983_HARN_Florida_GDL_Albers",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Albers"],PARAMETER["False_Easting",400000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-84.0],PARAMETER["Standard_Parallel_1",24.0],PARAMETER["Standard_Parallel_2",31.5],PARAMETER["Latitude_Of_Origin",24.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3087]]</WKT><XOrigin>-19550100</XOrigin><YOrigin>-7526400</YOrigin><XYScale>225743210.67916927</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>3087</WKID><LatestWKID>3087</LatestWKID></ProjectedCoordinateSystem>8TRUELZW1TIFFTRUEdiscreteunsigned integer25620230105160127002023010516012700Raster DatasetdatasetEPSG6.13(9.2.0)21052663.337344 58526.19734452663.337344 781596.197344794143.337344 781596.197344794143.337344 58526.197344423403.337344 420061.1973447414810.0000007230710.000000Band_15.0000000.000000820230105