Data Management Plan (Deprecated)

The LiDAR data acquisition was executed in 5 sessions, from March 7 to March 9, 2007.

The airborne GPS (ABGPS) base stations supporting the LiDAR acquisition consisted of the bases set up by the flight crews at the Anderson Airport (KAND). Dual Frequency data was logged continuously for the duration of each LiDAR flight mission at a one-second sampling rate or better.

Process Steps:

• 2007-03-01 00:00:00 - The LiDAR data acquisition was executed in 5 sessions, from March 7 to March 9, 2007. The airborne GPS (ABGPS) base stations supporting the LiDAR acquisition consisted of the bases set up by the flight crews at the Anderson Airport (KAND). Dual Frequency data was logged continuously for the duration of each LiDAR flight mission at a one-second sampling rate or better. The flight plan for LiDAR consisted of parallel flights in a north-south extent across the site. Fifty-four (54) flight lines of LiDAR data were acquired. In this process, Woolpert employed GPS differential processing and Kalman filtering techniques to derive an aircraft trajectory solution at 1-second intervals for each base station within the project limits. Statistics for each solution (base station) were generated and studied for quality. The goal for each solution is to have: maintained satellite lock throughout the session position standard deviation of less than 5 centimeters low ionospheric noise few or no cycle slips a fixed integer ambiguity solution throughout the trajectory a maximum number of satellites for a given constellation a low (3.0 or less) Position Dilution of Precision (PDOP) Often times a solution for a given base station will meet all of the above parameters in certain portions of the trajectory while the other base station might meet the above conditions in different portions of the trajectory solution. In this case, further processing was done to form different combinations of base station solutions and/or satellites to arrive at the optimal trajectory. For additional information please view the survey report:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4822/supplemental/sc2006_DNR_aiken_m4822surveyreport.pdf
• 2007-10-10 00:00:00 - LiDAR QA/QC verification will be provided by SCDNR through their contractor URS Corporation. The complete LiDAR data set for the entire project area was delivered to URS on August 15, 2007. URS conducted a data assessment. URS provided the review comments on October 10, 2007. URS indicated the LiDAR data met the vertical and horizontal accuracy requirements for the project and would not require any additional work.
• 2015-02-21 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in laz format from SCDNR via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane, 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 03. 3. The LAS data were sorted by latitude and the headers were updated.

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

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

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