FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: BASE FLOOD ELEVATION (BFE) LINES OF THE DIGITAL FLOOD INSURANCE RATE MAP (DFIRM) IN THE STATE OF FLORIDA - JUNE 2013 Geodataset Name: DFIRM_BFE_JUN13 Geodataset Type: SHAPEFILE Geodataset Feature: Polyline Feature Count: 29944 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): Federal Emergency Management Agency SCALE OF ORIGINAL SOURCE MAPS: 12000 GEODATASET EXTENT: Florida Counties: Alachua County, Baker County, Bay County, Bradford County, Calhoun County, Charlotte County, Collier County, Columbia County, Dixie County, Duval County, Escambia County, Flagler County, Gadsden County, Gilchrist County, Gulf County, Hamilton County, Hernando County, Hillsborough County, Holmes County, Indian River County, Jackson County, Lafayette County, Lake County, Lee County, Leon County, Levy County, Liberty County, Madison County, Marion County, Nassau County, Okaloosa County, Osceola County, Orange County, Pinellas County, Polk County (Partial Coverage), Putnam County, Santa Rosa County, Seminole County, St. Johns County, St. Lucie County, Suwannee County, Taylor County, Union County, Volusia County, Walton County, and Washington County. |
FEATURE ATTRIBUTE TABLES:
Datafile Name: DFIRM_BFE_JUN13.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
BFE_LN_ID
|
11 | String |
ELEV
|
8 | Double |
LEN_UNIT
|
20 | String |
V_DATUM
|
6 | String |
SOURCE_CIT
|
11 | String |
COUNTY
|
20 | String |
DESCRIPT
|
30 | String |
SOURCEDATE
|
36 | Date |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
SHAPE.LEN
|
0 | Double |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
BFE_LN_ID |
Primary key for table lookup. Assigned by table creator. |
|
ELEV |
BFE. The rounded, whole-foot elevation of the 1-percent-annual-chance flood. This is the value of the BFE that is printed next to the BFE line on the FIRM. |
|
LEN_UNIT |
BFE Units. This unit indicates the measurement system used for the BFEs. Normally this would be feet. Acceptable values for this field are listed in the D_Length_Units table. |
|
V_DATUM |
Vertical Datum. The vertical datum indicates the reference surface from which the flood elevations are measured. Normally this would be North American Vertical Datum of 1988 for new studies. Acceptable values for this field are listed in the D_V_Datum table. |
|
SOURCE_CIT |
Source Citation. Abbreviation used in the metadata file when describing the source information for the S_BFE table. |
|
COUNTY |
The county name. |
|
DESCRIPT |
Based on fields [ELEV] and [LEN_UNIT]. |
|
SOURCEDATE |
The date the Source created the data or the Effective Date. |
|
FGDLAQDATE |
The date FGDL acquired the data from the Source. |
|
AUTOID |
Unique ID added by GeoPlan |
|
SHAPE.LEN |
Length in meters |
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. |
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 DFIRM Database files reflect 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. Both detailed and approximate analyses are employed. Generally, detailed analyses are used to generate flood risk data only for developed or developing areas of communities. For areas where little or no development is expected to occur, FEMA uses approximate analyses to generate flood risk data. Typically, only drainage areas that are greater than one square mile are studied. |
GeoPlan relied on the integrity of the attribute information within the original data. |
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. Letter of Final Determination (LFD) and FIRM Effective Date per County Alachua County: LFD Date: 12/16/2005, FIRM Effective Date: 06/16/2006 Baker County: LFD Date: 12/17/2007, FIRM Effective Date: 06/17/2008 Bay County: LFD Date: 12/02/2008, FIRM Effective Date: 06/02/2009 Bradford County: LFD Date: 12/02/2011, FIRM Effective Date: 05/02/2012 Calhoun County: LFD Date: 12/18/2012, FIRM Effective Date: 06/18/2013 Charlotte County: LFD Date: 11/05/2002, FIRM Effective Date: 05/05/2003 Collier County: LFD Date: 11/16/2011, FIRM Effective Date: 05/16/2012 Columbia County: LFD Date: 08/04/2008, FIRM Effective Date: 02/04/2009 Dixie County: LFD Date: 09/18/2007, FIRM Effective Date: 03/18/2008 Duval County: LFD Date: 12/03/2012, FIRM Effective Date: 06/03/2013 Escambia County: LFD Date: 03/29/2006, FIRM Effective Date: 09/29/2006 Flagler County: LFD Date: 01/17/2006, FIRM Effective Date: 07/17/2006 Gadsden County: LFD Date: 08/04/2008, FIRM Effective Date: 02/04/2009 Gilchrist County: LFD Date: 03/29/2006, FIRM Effective Date: 09/29/2006 Gulf County: LFD Date: 10/16/2008, FIRM Effective Date: 04/16/2009 Hamilton County: LFD Date: 12/04/2009, FIRM Effective Date: 06/04/2010 Hernando County: LFD Date: 08/02/2011, FIRM Effective Date: 02/02/2012 Hillsborough County: LFD Date: 02/28/2008, FIRM Effective Date: 08/28/2008 Holmes County: LFD Date: 06/17/2010, FIRM Effective Date: 12/17/2010 Indian River County: 06/04/2012, FIRM Effective Date: 12/04/2012 Jackson County: LFD Date: 06/17/2010, FIRM Effective Date: 12/17/2010 Lafayette County: LFD Date: 03/29/2006, FIRM Effective Date: 09/29/2006 Lake County: LFD Date: 01/03/2002, FIRM Effective Date: 07/03/2002 Lee County: LFD Date: 02/28/2008, FIRM Effective Date: 08/28/2008 Leon County: LFD Date: 02/18/2009, FIRM Effective Date: 08/18/2009 Levy County: LFD Date: 05/02/2011, FIRM Effective Date: 11/02/2011 Liberty County: LFD Date: 12/18/2012, FIRM Effective Date: 06/18/2013 Madison County: LFD Date: 11/03/2009, FIRM Effective Date: 05/03/2010 Marion County: LFD Date: 02/28/2008, FIRM Effective Date: 08/28/2008 Miami-Dade County: LFD Date: 03/11/2009, FIRM Effective Date: 09/11/2009 Monroe County: LFD Date: 08/18/2004, FIRM Effective Date: 02/18/2005 Nassau County: LFD Date: 06/17/2010, FIRM Effective Date: 12/17/2010 Okaloosa County: LFD Date: 06/06/2002, FIRM Effective Date: 12/06/2002 Osceola County: LFD Date: 12/06/2000, FIRM Effective Date: 06/06/2001 Orange County: LFD Date: 03/25/2009, FIRM Effective Date: 09/25/2009 Pinellas County: LFD Date: 02/18/2009, FIRM Effective Date: 08/18/2009 Polk County: LFD Date: 03/28/2012, FIRM Effective Date: 09/28/2012 Putnam County: LFD Date: 08/02/2011, FIRM Effective Date: 02/02/2012 Santa Rosa County: LFD Date: 06/19/2006, FIRM Effective Date: 12/19/2006 Seminole County: LFD Date: 03/28/2007, FIRM Effective Date: 09/28/2007 St. Johns County: LFD Date: 03/02/2004, FIRM Effective Date: 09/02/2004 St. Lucie County: LFD Date: 08/16/2011, FIRM Effective Date: 02/16/2012 Suwannee County: LFD Date: 03/28/2007, FIRM Effective Date: 09/28/2007 Taylor County: LFD Date: 11/04/2008, FIRM Effective Date: 05/04/2009 Union County: LFD Date: 08/04/2008, FIRM Effective Date: 02/04/2009 Volusia County: LFD Date: 08/19/2002, FIRM Effective Date: 02/19/2003 Walton County: LFD Date: 03/29/2010, FIRM Effective Date: 09/29/2010 Washington County: LFD Date: 01/04/2011, FIRM Effective Date: 07/04/2011 Source: http://www.floodmaps.fema.gov/lfd_map/index.html ** The following FEMA DFIRM information is from the frm_gsalb.pdf ** Table: S_BFE The Base Flood Elevation (BFE) table is required for any digital data where BFE lines will be shown on the corresponding Flood Insurance Rate Map (FIRM). Normally if there are any riverine AE zones, BFE lines are required. The S_BFE table contains information about the BFEs within a study area. A spatial file with locational information also corresponds with this data table. BFE lines indicate the rounded whole-foot water surface elevation of the 1-percent-annual-chance flood. The spatial elements representing BFE features are lines extending from Special Flood Hazard Area (SFHA) boundary to SFHA boundary. The BFE lines will have no visible gaps or overshoots between the SFHA boundary and the end of the BFE line at the publication scale of the DFIRM. However, the ends of the BFE lines are not necessarily snapped precisely to the SFHA boundary. Each BFE is represented by a single line. While BFE lines are depicted as wavy lines on the hardcopy FIRM, they should be primarily straight lines in the spatial data, although they may bend consistent with procedures described in Volume 1 of these Guidelines. Table: D_Length_Units LEN_LID LEN_UNIT 1000 CENTIMETERS 1010 FEET 1020 INCHES 1030 KILOMETERS 1040 METERS 1050 MILES 1060 MILLIMETERS |
The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards," Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS. |
The DFIRM Database consists of countywide vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and DFIRM 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 Specifications for Flood Hazard Mapping Partners. 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 FEMA's DFIRM database was also performed. |
The DFIRM Database consists of countywide vector files and associated attributes produced in conjunction with the hardcopy FEMA FIRM. The published effective FIRM and DFIRM maps 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 Specifications for Flood Hazard Mapping Partners. Vertical 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 FEMA's DFIRM database was also performed. |
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 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 Map Service Center http://msc.fema.gov ** What are you looking for? **** DFIRM Databases Guidelines and Specifications for Flood Hazard Mapping Partners http://www.fema.gov/library/viewRecord.do?id=2206 ** Appendix L: Guidance for Preparing Draft Digital Data and DFIRM Database ** Appendix L: Part 1 ** Appendix L: Part 2 |
The DFIRM Database is compiled in conjunction with the hardcopy FIRM and the final FIS report. The specifics of the hydrologic and hydraulic analyses performed are detailed in the FIS report. 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 DFIRM publication and checked for accuracy and compliance with FEMA standards. Process Date: 20060616 |
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: |
Federal Emergency Management Agency FEMA 500 C Street, S.W. Washington, District of Columbia 20472 1-800-358-9616 |
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