Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2024: 2011 Suwannee River Water Management District Lidar: Upper Suwannee (FL), https://www.fisheries.noaa.gov/inport/item/49698.

Item Identification

Title: 2011 Suwannee River Water Management District Lidar: Upper Suwannee (FL)
Short Name: fl2011_srwmd_uppersuwannee_m4889_metadata
Status: Completed
Publication Date: 2015-05
Abstract:

The Light Detection and Ranging (LiDAR) dataset is a survey of the Suwannee River project area in Florida. The entire survey area encompasses 1,151 square miles. The LiDAR point cloud was flown at a nominal post spacing of 1.4 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 13-ILMF 2010. The flightlines were acquired by Digital Aerial Solutions, which required 9 subsequent missions between the dates of January 3, 2011, and January 30, 2011. Derivative products from the aerial aquisition include: Raw point cloud data in LAS v1.2, classified point cloud data in LAS v1.2, bare earth surface (raster DEM ERDAS IMG format), hydro-flattened breaklines, control points, and FGDC compliant XML metadata.

Purpose:

This regional LiDAR elevation mapping was obtained under the American Recovery and Reinvestment Act (ARRA) of 2009.

Notes:

10342

Supplemental Information:

A report for this project is available at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4889/supplemental/fl2011_srwmd_uppersuwannee_m4889_surveyreport.pdf

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

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4889/supplemental/fl2011_srwmd_uppersuwannee_m4889.kmz

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None Ground
None Terrain

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 2011
None January

Physical Location

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

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: Unknown
Data Presentation Form: las
Entity Attribute Overview:

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

Entity Attribute Detail Citation:

none

Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of Merrick and Co, SRWMD, NOAA, the Office for Coastal Management or its partners.

Support Roles

Data Steward

CC ID: 672972
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: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Distributor

CC ID: 672974
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: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 672975
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: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Point of Contact

CC ID: 672973
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: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Extents

Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1136846
W° Bound: -83.436518
E° Bound: -82.444044
N° Bound: 30.645743
S° Bound: 30.056185

Extent Group 1 / Time Frame 1

CC ID: 1136845
Time Frame Type: Range
Start: 2011-01-03
End: 2011-01-30

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:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4889

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

Data Access Constraints:

None

Data Use Constraints:

The data depicts the elevations at time of survey and are accurate only for that time. Exercise professional judgement 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: 740811
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4889
Distributor:
File Name: Customized Download
Description:

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

Distribution 2

CC ID: 740812
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4889/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 740814
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 740815
URL: https://coast.noaa.gov
URL Type:
Online Resource

URL 3

CC ID: 740816
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4889/supplemental/fl2011_srwmd_uppersuwannee_m4889.kmz
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for the 2011 lidar project covering the Upper Suwannee River, Florida.

Activity Log

Activity Log 1

CC ID: 672993
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 672992
Activity Date/Time: 2017-11-14
Description:

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.

Activity Log 3

CC ID: 718247
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 740813
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Accuracy:

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 .30 meters and equals a .51 meter horizontal accuracy at the 95 % confidence level.

Horizontal Positional Accuracy:

There is not a systematic method of testing when testing horizontal accuracy in LiDAR. However this is tested during calibration of the sensor and is rechecked during the comparing of parallel and perpendicular flight lines. Additionally 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 .30 meters and equals a .51 meter horizontal accuracy at the 95 % confidence level. Accuracy defined by NSSDA at the 95 % confidence level would be multiplier by 1.7308 times the RMSE.; Quantitative Value: 1.14 meters, Test that produced the value: There is not a systematic method of testing when testing horizontal accuracy in LiDAR. However this is tested during calibration of the sensor and is rechecked during the comparing of parallel and perpendicular flight lines. Additionally 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 .66 meters and equals a 1.14 meter horizontal accuracy at the 95 % confidence level. Accuracy defined by NSSDA at the 95 % confidence level would be multiplier by 1.7308 times the RMSE.

Vertical Positional Accuracy:

The accuracy assessment was performed using the NSSDA standard method to compute the root mean square error (RMSE) based on a comparison of ground control points (GCP) and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represent bare earth elevations.

Testing was performed prior to gridding of the filtered LiDAR data points and construction of the 32-bit ESRI float grid format bare earth tiles. The RMSEz figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size.

The specification for the National Standard for Spatial Data Accuracy is a minimum of 20 points to conduct a statistically significant accuracy evaluation. The intent of the NSSDA is to reflect the geographic area of interest and the distribution of error in the data set Data collected under this task order exceeds the required National Standards for Spatial Database Accuracy (NSSDA) accuracy standards.

The Fundamental Vertical Accuracy (FVA) of the TIN: 16.76cm (.55 ft.) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 24.5cm (0.8 ft.) in the "Urban" land cover category.

The Supplemental Vertical Accuracy (SVA) RMSEz classes collected and tested, results as follows, Urban = 16.76cm (.55 ft.) Low Veg. = 12.80cm (.42 ft.), Medium Veg. = 31.39cm (1.03 ft.) , and High Veg.= 16.46cm (.54 ft.) at a 95th percentile, derived according to ASPRS Guidelines, i.e., based on RMSE of 36.3cm (.8 ft.).

The Consolidated Vertical Accuracy (CVA) RMSEz results for this task order = 17.98cm (.59 ft.) at a 95th percentile, derived according to ASPRS Guidelines, i.e., based on RMSE of 36.3cm (1.19 ft.).; Quantitative Value: 0.855 meters, Test that produced the value: The Fundamental Vertical Accuracy (FVA) of the TIN: 16.76cm (.55 ft.) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 24.5cm (0.8 ft.) in the "Urban" land cover category, RMSEz in open terrain would be 8.55 cm

Completeness Report:

Ground Truth data was collected of the three major vegetative cover classes and "urban" dispersed within the area of interest. 158 points were collected in each of the four classes urban, low vegetation, medium vegetation, and high vegetation, points collected in high vegetation were collected with a Total Station. 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.

Lineage

Process Steps

Process Step 1

CC ID: 1136838
Description:

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: 2011-01-09 00:00:00

Process Step 2

CC ID: 1136839
Description:

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/HARN State Plane Florida North Coordinate System, with units in U.S. Survey Feet and referenced in Geoid09 Orthometric heights. 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 5000 foot by 5000 foot tiling scheme. 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: 2011-02-09 00:00:00

Process Step 3

CC ID: 1136840
Description:

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: 2011-02-09 00:00:00

Process Step 4

CC ID: 1136841
Description:

Filtered and edited data are subjected to rigorous QA/QC, according to the Merrick & Co. 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 Digital Aerial Solutions, LLC and 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: 2011-03-11 00:00:00

Process Step 5

CC ID: 1136842
Description:

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: 2011-04-04 00:00:00

Process Step 6

CC ID: 1136843
Description:

The NOAA Office for Coastal Management (OCM) received the files in las format from SRWMD. The files contained lidar elevation and intensity measurements. The data were in State Plane Florida North Zone 903, NAVD88 (orthometric) heights in meters. 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 meters to GRS80 (ellipsoid) heights in meters using Geoid 09.

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

4. Data were retiled to remove buffer.

5. Erroneous elevations were removed.

Process Date/Time: 2015-01-10 00:00:00

Catalog Details

Catalog Item ID: 49698
GUID: gov.noaa.nmfs.inport:49698
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