Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2024: Suwannee River Water Management District Lidar: Falmouth (FL),

Item Identification

Title: Suwannee River Water Management District Lidar: Falmouth (FL)
Short Name: fl2013_srwmd_falmouth_m4887_metadata
Status: Completed
Publication Date: 2015-05

The Light Detection and Ranging (LiDAR) dataset is a survey of the Suwannee River G12PD00242 1.0 Meter LiDAR Survey area 5 in north-central Florida and encompasses 65 square miles. The LiDAR point cloud was flown at a nominal post spacing of 1.0 meters for unobscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 1. The flight lines were acquired by Digital Aerial Solutions, LLC. between Jan 19, 2013 and Jan 20, 2013. Derivative products from the aerial acquisition include: Raw point cloud data in LAS v1.2, classified point cloud data in LAS v1.2, bare earth surface tiles (raster DEM ESRI float GRID format), bare earth surface DEMs mosaic (raster DEM MrSID format), control points, project report, and FGDC compliant XML metadata.


The purpose of collecting this LIDAR data to improve the SRWMD district-wide elevation data set for mapping, spatial analysis, and other SRWMD tasks and applications. This LIDAR data is replacing the digital USGS Topographic 7.5 Minute Map 5 foot contours that we have relied on for over 20 years. In addition the SRWMD wants to cooperate with Federal and State agencies to meet accepted LIDAR standards in order to produce the highest quality and consistent data possible. In addition, we collected this LIDAR data as part of a district, state, and national goal to have complete 100 percent LIDAR data coverage of the entire State of Florida. And last the SRWMD wants these data to become part of the USGS National Elevation Data program (NED) and NOAA Digital Coast for public use and distribution.



Supplemental Information:

Reports for this project are available at:

A footprint of this data set may be viewed in Google Earth at:


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
None Ground
None Terrain

Temporal Keywords

Thesaurus Keyword
None 2013
None Fall

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: Unknown
Entity Attribute Overview:

LAS 1.2 format (classes 1,2,7,9,10,15,17,18)

Entity Attribute Detail Citation:


Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of Digital Aerial Solutions, SRWMD, NOAA, the Office for Coastal Management or its partners.

Support Roles

Data Steward

CC ID: 673508
Date Effective From: 2015-05
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


CC ID: 673510
Date Effective From: 2015-05
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Metadata Contact

CC ID: 673511
Date Effective From: 2015-05
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Point of Contact

CC ID: 673509
Date Effective From: 2015-05
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1136815
W° Bound: -83.281184
E° Bound: -82.877849
N° Bound: 30.382894
S° Bound: 29.814971

Extent Group 1 / Time Frame 1

CC ID: 1136813
Time Frame Type: Discrete
Start: 2013-01-19

Extent Group 1 / Time Frame 2

CC ID: 1136814
Time Frame Type: Discrete
Start: 2013-01-20

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL:

The data set is dynamically generated based on user-specified parameters.;

Data Access Constraints:


Data Use Constraints:

The data depicts the elevations at time of survey and are accurate only for that time. Exercise professional judgment in using this data.

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. These data depict the heights at the time of the survey and are only accurate for that time.

Distribution Information

Distribution 1

CC ID: 740877
Download URL:
File Name: Customized Download

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

Distribution 2

CC ID: 740878
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 740880
URL Type:
Online Resource


CC ID: 740881
URL Type:
Online Resource


CC ID: 740882
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz

This graphic shows the lidar coverage for the 2013 lidar project Falmouth, FL.

Activity Log

Activity Log 1

CC ID: 673533
Activity Date/Time: 2016-05-23

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 673532
Activity Date/Time: 2017-11-14

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

Activity Log 3

CC ID: 718258
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 740879
Activity Date/Time: 2018-03-13

Partial upload to move data access links to Distribution Info.

Data Quality


There is not a systematic method of testing when testing horizontal accuracy in LiDAR. The horizontal accuracy is checked by collecting building corners during the survey. Lines are then digitized representing the building outline and the differences are measure from each individual survey point to the corner of the building outline. Stats are calculated to ensure horizontal tolerances are met. These measurements resulted in an RMSE of .42 meters and equals a .73 meter horizontal accuracy at the 95 % confidence level.

Horizontal Positional Accuracy:

Horizontal accuracy assessments of LiDAR data require the presence of vertical targets such as buildings within in the survey area. Field check points are surveyed at the corners of the building roofs, and the surveyed locations compared to the estimated corner locations in the LiDAR point cloud. The Suwannee Management survey area did not present any accessible buildings for use as vertical targets.

From the manufacturer's specifications, the estimated horizontal accuracy at one sigma, based on flying height for the project, is between 10 cm and 20 cm.

Vertical Positional Accuracy:

Absolute vertical accuracy assessments for the point cloud data are made against ground check point data. For the Suwannee Management Area 5 survey, ground check point data consisted of the ground GPS base station, and real-time kinematic (RTK) GPS techniques. Check point locations were collected at 1 - second intervals during the RTK survey. Points collected during the static pre-initialization and post-initialization were removed from the assessment so as not to bias the assessment.

Local TIN models of the elevation points are built around each ground check points. The tin model elevation is sampled at the horizontal position of the ground check point. The TIN model elevation and ground check point survey elevation values were used to calculate the fundamental vertical accuracy (FVA) of the swath point clouds as described in NDEP Elevation Guidelines Version 1. The FVA of the TIN tested RMSEz 0.095 Feet (2.9 cm) and 0.183 Feet at the 95% confidence level in open terrain. FVA of the DEM tested at an RMSEz of 0.095 Feet and 0.187 Feet at the 95% confidence level in open terrain.; Quantitative Value: 0.029 meters, Test that produced the value: 2.9 cm RMSE

Completeness Report:

Ground Truth data was collected of the three major land cover classes dispersed within the area of interest. 30 points were collected in each of the three predominate vegetation classes tall weed vegetation, brushland vegetation, and forested vegetation. Pair of points was surveyed using the Trimble VRS network once completed the total station is used to collect the high vegetation ground class. A Topcon 7000 total station was used to collect all the shots collected in the high vegetation class, due to the limited GPS signal when working in and around tree canopy.

Conceptual Consistency:

The GPS survey was tied into the Trimble VRS Now Network located in Florida. The Trimble VRS Now network is a network of continuously operating GPS reference stations that provides Real Time Kinematic (RTK) capabilities within a Real Time Network (RTN). This allows corrections to be applied to the points as they are being collected, eliminating the need for an adjustment. Several existing control monuments listed in the NSRS database were used as checks within the Trimble VRS Now Network. This confirmed network accuracies were being met during the field survey as well as providing a redundancy check on the Trimble VRSnetwork. The Specified local network accuracy of 5cm at the 95% confidence level was met or exceeded. Data analysis was accomplished by comparing ground truth checkpoints with LIDAR points from the edited data set, which were within 3.3 feet horizontally from the ground truth points. Based on the number of returns and the density of points in this project, it was not necessary to compare to anything further away than 3.3 feet horizontally from the ground truth points. Note that the edited LIDAR points are simply a subset of the raw LIDAR points. The points that fell above the ground surface on vegetation canopies, buildings, or other obstructions were removed from the data set. Comparisons were also made between the survey points and the LIDAR derived terrain surface. These comparisons provide an additional verification of the LIDAR data against the survey data.


Process Steps

Process Step 1

CC ID: 1136806

The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area.

Process Date/Time: 2013-01-22 00:00:00

Process Step 2

CC ID: 1136807

The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Leica and delivered with the Leica System. The resultant file is in a LAS binary file format. The LAS version 1.2 file 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 number, intensity value, xyz, etc.). The resultant points are produced in the NAD83 UTM zone17 Coordinate System, with units in meters and referenced to the NAVD88 datum. The LiDAR mass points were processed in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as defined by the LAS 1.2 specification. The datasets were divided into a 1500 m by 1500 m tiling scheme, based on the US National grid network. The tiles are contiguous, do not overlap, and are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles include numeric column and row designations and all files utilize the LAS file extension

Process Date/Time: 2013-01-24 00:00:00

Process Step 3

CC ID: 1136808

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 elevation models (DEMs). 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.

Process Date/Time: 2013-01-28 00:00:00

Process Step 4

CC ID: 1136809

Filtered and edited data are subjected to rigorous QA/QC, DAS Quality Control Plan and procedures. A series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by DASand GPS-derived ground control points (GCPs) in various areas of dominant and prescribed land cover. These points are coded according to land cover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment, as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA), according to Federal Geographic Data Committee (FGDC) specifications.

Process Date/Time: 2013-04-02 00:00:00

Process Step 5

CC ID: 1136810

The Bare Earth DEM was extracted from the raw LIDAR products and attributed with the bare earth elevation for each cell of the DEM. Bare Earth DEMs do not include buildings, vegetation, bridges or overpass structures in the bare earth model. Where abutments were clearly delineated, this transition occurred at the junction of the bridge and abutment. Where this junction was not clear, the extractor used their best estimate to delineate the separation of ground from elevated bridge surface. In the case of bridges over water bodies, if the abutment was not visible, the junction was biased to the prevailing stream bank so as not to impede the flow of water in a hydrographic model. Bare earth surface includes the top of water bodies not underwater terrain, if visible.

Process Date/Time: 2013-04-15 00:00:00

Process Step 6

CC ID: 1136811

The NOAA Office for Coastal Management (OCM) received the files in las format from SRWMD. The files contained lidar elevation, intensity measurements, and some imagery. The data were in State Plane Zone 903, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. The data were converted from State Plane coordinates to geographic coordinates.

2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 09.

3. The LAS data were sorted by latitude and the headers were updated.

4. Duplicate/erroneous points were removed.

5. Data was retiled to remove buffer.

6. Class 11 points (withheld) were reclassed to Class 15.

Process Date/Time: 2015-04-19 00:00:00

Catalog Details

Catalog Item ID: 49709
GUID: gov.noaa.nmfs.inport:49709
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:21+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16