2007 Florida Division of Emergency Management (FDEM) Lidar: Herbert Hoover Dike Project
Area (Southeastern Florida, Lake Okeechobee Surrounding Area)
This kmz file shows the extent of coverage for the 2007 FDEM Herbert Hoover Dike (Lake
Okeechobee), FL lidar data set.
LiDAR data was collected by Merrick & Company from September through December of 2007
for the Florida Division of Emergency Management (FDEM). The project area is located
in the southeastern part of Florida, in parts of the counties surrounding Lake Okeechobee.
LiDAR was collected over approximately 2289 square miles in parts of the following
counties: Broward, Glades, Hendry, Highlands, Martin, Okeechobee, and Palm Beach.
The maximum point spacing is 4 ft in unobscured areas. This data set is a classified
data set and has a classification for sugar cane.
Cite this dataset when used as a source.
|Search and Download
|| Distributor information not available
| Point of Contact
||Florida Division of Emergency Management (FDEM)
Lidar Dataset Supplemental Information
- Florida Division of Emergency Management (FDEM)
|Data Presentation Form:
|| Digital image
|Dataset Progress Status
|Data Update Frequency:
|| As needed
||Class 1 = Unclassified, includes vegetation, buildings, etc.; Class 2 = Ground; Class
3 = Sugar Cane; Class 7 = Noise; Class 9 = Water; Class 12 = Overlap
||To produce accurate, high-resolution data for planning and analysis to support the
Florida Division of Emergency Management (FDEM) development and maintenance of regional
evacuation studies, which include vulnerability assessments and to assist disaster
response personnel in understanding threats to Florida's citizens and visitors.
||2007-09-08 to 2007-12-19
|Spatial Reference System:
|Spatial Bounding Box Coordinates:
|Spatial Coverage Map:
- Herbert Hoover Dike
- Lake Okeechobee
- Broward County
- Glades County
- Hendry County
- Highlands County
- Martin County
- Okeechobee County
- Palm Beach County
| Use Constraints
|| No constraint information available
|| Fee information not available.
|| Lineage statement not available.
- Merrick & Co
- DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
| Processing Steps
- The ABGPS, IMU, and raw Leica ALS50 Phase 2 Plus LiDAR data are integrated with Leica
Incorporated's ALS Post Processor software. The resultant file is in a LAS binary
file format. The LAS file version 1.1 format can be easily transferred from one file
format to another. It is a binary file format that maintains information specific
to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are
produced in the geodetic coordinates referenced to the NAD83 HARN horizontal datum
and NAVD88 vertical datum. The date and time for each flight line can be determined
using the Julian date and time. The Julian date is a continuous count of days and
fractions since noon Universal Time on January 1, 4713 BCE on the Julian calendar.
- The unedited data are classified to facilitate the application of the appropriate
feature extraction filters. A combination of proprietary filters are applied as appropriate
for the production of bare earth digital terrain models (dtms). Interactive editing
methods are applied to those areas where it is inappropriate or impossible to use
the feature extraction filters, based upon the design criteria and/or limitations
of the relevant filters. These same feature extraction filters are used to produce
elevation height surfaces. The LiDAR mass points were delivered in American Society
for Photogrammetry and Remote Sensing LAS 1.1 format. The header file for each dataset
is complete as defined by the LAS 1.1 specification. In addition the following fields
are included: Flight Date Julian, Year, and Class. The LAS files do not contain overlap
(class 12). The data was classified as follows: Class 1 = Unclassified. This class
includes vegetation, buildings, etc. Class 2 = Ground Class 3 = Sugarcane (Job specific
classification, not used in contour generation) Class 7 = Noise Class 9 = Water Class
12 = Overlap Sugarcane points (class 3) were added to this project at the request
of the US Army Corps of Engineers. The lidar sensor could not adequately penetrate
sugarcane fields. A method was developed to define the location of sugarcane. Points
inside of the sugar_cane feature class in the HHD geodatabase were either classified
as unclassified (class = 1) or sugarcane (class = 3). There are no ground (class =
2) points inside of the sugar_cane feature class.
- The NOAA Coastal Services Center (CSC) received files in LAS format. The files contained
LiDAR intensity and elevation measurements. CSC performed the following processing
on the data to make it available within Digital Coast: 1. The data were converted
from State Plane Florida East coordinates to geographic coordinates. 2. The data were
converted from NAVD88 heights to ellipsoid heights using Geoid03. 3. The LAS header
fields were sorted by latitude and updated.
- The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp
transfer from the NOAA Coastal Services Center. The data are
currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/.
The data can be used to re-populate the system. The data are archived in LAS
or LAZ format. The LAS format is an industry standard for LiDAR data developed by
the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless
compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The
data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data
are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for
the ability to apply the most up to date geoid model when transforming to orthometric
Metadata Last Modified: 2013-06-07
For questions about the information on this page, please email: