2007 Florida Division of Emergency Management (FDEM) Lidar: Herbert Hoover Dike Project Area (Southeastern Florida, Lake Okeechobee Surrounding Area)

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Simple download of data files.

This kmz file shows the lidar footprint for the FDEM Herbert Hoover Dike project.

Date that the source FGDC record was last modified.

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Partial upload of Positional Accuracy fields only.

Partial upload to move data access links to Distribution Info.

network of GPS'ed checkpoints | Type of Source Media: disc

The LiDAR dataset was used to create the multipoint file consisting of ground only points. | Source Geospatial Form: LAS data | Type of Source Media: disc

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 Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements.

OCM 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.