NCEI (formerly NGDC)
EMMA logo
Back to Collection NOAA/NESDIS/NGDC/MGG/Lidar
View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2007 Florida Division of Emergency Management (FDEM) Lidar Project: Wakulla County

browse graphicThis kmz file shows the extent of coverage for the 2007 FDEM Wakulla County, FL lidar data set.
This report pertains to a Specific Purpose Lidar Survey of Wakulla County, Florida, conducted in the summer of 2007 for the Florida Division of Emergency Management (FDEM). The Lidar dataset was prepared by the Program and Data Solutions (PDS) team under FDEM contract 07-HS-34-14-00-22-469, Task Order 20070525-492718a (PDS Task Order B). The Lidar dataset of Wakulla County was acquired by Terrapoint USA in the summer of 2007. The Lidar dataset was delivered as a point cloud in LAS 1.1 format.
Cite this dataset when used as a source.
Other Access Online access information not available.
Distribution Formats
  • LAZ
Distributor DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Dataset Point of Contact Florida Division of Emergency Management (FDEM)
  • publication: 2008-01-01
Data Presentation Form: Digital image
Dataset Progress Status Complete
Data Update Frequency: As needed
Purpose: The Lidar dataset is used in conjunction with breaklines to determine a DTM surface. These data support the Florida Division of Emergency Management's (FDEM) development and maintenance of Regional Evacuation Studies, which include vulnerability assessments and assist disaster response personnel in understanding threats to Florida's citizens and visitors.
Use Limitations
  • These data depict the elevations at the time of the survey and are only accurate for that time. Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
  • While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • Florida Division of Emergency Management (FDEM)
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
Time Period: 2007-07-05 to 2008-05-04
Spatial Reference System: urn:ogc:def:crs:EPSG::4269
Spatial Bounding Box Coordinates:
N: 30.306085
S: 29.962285
E: -84.083405
W: -84.748705
Spatial Coverage Map:
Theme keywords None
  • Bathymetry/Topography
  • Lidar
  • Elevation
  • DTM
Place keywords None
  • US
  • Florida
  • Wakulla County
Use Constraints No constraint information available
Fees Fee information not available.
Lineage information for: dataset
  • Terrapoint USA
  • Terrapoint USA
  • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
  • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
Processing Steps
  • 2008-01-01T00:00:00 - The ABGPS, IMU, and raw Optech 3100ea Lidar scans are integrated using Optech Incorporated's DASHMap, version 1.1 software, Terrascan software and Microstation 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 referenced to the NAD83 horizontal datum and GRS80 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.
  • 2008-01-01T00:00:00 - 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 define by the LAS 1.1 specification. In addition the following fields are included (Precision reported in brackets): Class (Integer); GPS Week Time (0.0001 seconds); Easting (0.01 meter); Northing (0.01 meter); Elevation (0.01 meter); Echo Number (Integer 1 to 4); Echo (Integer 1 to 4); Intensity (8 Bit Integer); Flightline (Integer); Scan Angle (Integer Degree). The LAS files do not include overlap. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7= Noise Class 9 = Water
  • 2010-12-07T00:00:00 - The NOAA Coastal Services Center (CSC) received the files in las format. The files contained Lidar elevation and intensity measurements. The data were in projected in Florida State Plane Coordinates (North Zone, NAD83/HARN), and referenced to the orthometric datum of NAVD88 utilizing Geoid 03. CSC performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from State Plane Coordinates (NAD83/HARN) coordinates to geographic coordinates (NAD83). 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated.
  • 2011-09-09T00:00:00 - 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 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 ( 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 heights.
Source Datasets
  • Lidar
    • Description of Source: Source Contribution: Lidar dataset was used to create intensity stereopairs for 3D breakline compilation and for contour generation.Source Type: online
    • Temporal extent used: 2007-05-04 to 2007-08-16
Last Modified: 2013-06-07
For questions about the information on this page, please email: