Data Management Plan

Digital Aerial Solution (DAS) collected 921 square miles over 3 Areas of Interest (AOIs) to include portions of Baker, Alachua and Levy Counties in Florida. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity, 17- Bridge Decks, 18-High Noise. Dewberry produced 3D breaklines and combined these with the final ground classified lidar data to produce seamless bare earth, hydro flattened DEMs for the project area. The data was formatted according to the Florida State Grid tile naming convention with each tile covering an area of 5,000 feet by 5,000 ft. A total of 1378 DEM tiles were produced for the entire project.

The NOAA Office for Coastal Management (OCM) received the DEM files from the Suwannee River Water Management District and processed the files to the Digital Coast.

The breaklines were also downloaded and are available for download at the link provided in the URL section of this metadata record. Please note that this product has not been reviewed by OCM and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.

Lineage Statement:
NOAA OCM received the bare earth DEM files from the SRWMD.

Process Steps:

• 2017-02-01 00:00:00 - Data for the FL Suwannee River Lidar Project was acquired by Digital Aerial Solutions (DAS). The project area included approximately 921 contiguous square miles or 2385.38 square kilometers for the counties of Baker, Alachua, and Levy in Florida. Lidar sensor data were collected with the Leica ALS80 HP lidar system. The data was delivered in the State Plane coordinate system, US Survey Feet, Florida North, horizontal datum NAD83 (2011), vertical datum NAVD88, Geoid 12B. Deliverables for the project included a raw (unclassified) calibrated lidar point cloud, survey control, and a final acquisition/calibration report. The calibration process considered all errors inherent with the equipment including errors in GPS, IMU, and sensor specific parameters. Adjustments were made to achieve a flight line to flight line data match (relative calibration) and subsequently adjusted to control for absolute accuracy. Process steps to achieve this are as follows: Rigorous lidar calibration: all sources of error such as the sensor's ranging and torsion parameters, atmospheric variables, GPS conditions, and IMU offsets were analyzed and removed to the highest level possible. This method addresses all errors, both vertical and horizontal in nature. Ranging, atmospheric variables, and GPS conditions affect the vertical position of the surface, whereas IMU offsets and torsion parameters affect the data horizontally. The horizontal accuracy is proven through repeatability: when the position of features remains constant no matter what direction the plane was flying and no matter where the feature is positioned within the swath, relative horizontal accuracy is achieved. Absolute horizontal accuracy is achieved through the use of differential GPS with base lines shorter than 25 miles. The base station is set at a temporary monument that is 'tied-in' to the CORS network. The same position is used for every lift, ensuring that any errors in its position will affect all data equally and can therefore be removed equally. Vertical accuracy is achieved through the adjustment to ground control survey points within the finished product. Although the base station has absolute vertical accuracy, adjustments to sensor parameters introduces vertical error that must be normalized in the final (mean) adjustment. The withheld and overlap bits are set and all headers, appropriate point data records, and variable length records, including spatial reference information, are updated in GeoCue software and then verified using proprietary Dewberry tools.
• 2017-03-01 00:00:00 - Dewberry utilizes a variety of software suites for inventory management, classification, and data processing. All lidar related processes begin by importing the data into the GeoCue task management software. The swath data is tiled according to project specifications (5,000 ft x 5,000 ft). The tiled data is then opened in Terrascan where Dewberry identifies edge of flight line points that may be geometrically unusable with the withheld bit. These points are separated from the main point cloud so that they are not used in the ground algorithms. Overage points are then identified with the overlap bit. Dewberry then uses proprietary ground classification routines to remove any non-ground points and generate an accurate ground surface. The ground routine consists of three main parameters (building size, iteration angle, and iteration distance); by adjusting these parameters and running several iterations of this routine an initial ground surface is developed. The building size parameter sets a roaming window size. Each tile is loaded with neighboring points from adjacent tiles and the routine classifies the data section by section based on this roaming window size. The second most important parameter is the maximum terrain angle, which sets the highest allowed terrain angle within the model. As part of the ground routine, low noise points are classified to class 7 and high noise points are classified to class 18. Once the ground routine has been completed, bridge decks are classified to class 17 using bridge breaklines compiled by Dewberry. A manual quality control routine is then performed using hillshades, cross-sections, and profiles within the Terrasolid software suite. After this QC step, a peer review is performed on all tiles and a supervisor manual inspection is completed on a percentage of the classified tiles based on the project size and variability of the terrain. After the ground classification and bridge deck corrections are completed, the dataset is processed through a water classification routine that utilizes breaklines compiled by Dewberry to automatically classify hydrographic features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. During this water classification routine, points that are within 1x NPS or less of the hydrographic features are moved to class 10, an ignored ground due to breakline proximity. A final QC is performed on the data. All headers, appropriate point data records, and variable length records, including spatial reference information, are updated in GeoCue software and then verified using proprietary Dewberry tools. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7 = Low Noise Class 9 = Water Class 10 = Ignored Ground due to breakline proximity Class 17 = Bridge Decks Class 18 = High Noise The LAS header information was verified to contain the following: Class (Integer) Adjusted GPS Time (0.0001 seconds) Easting (0.003 m) Northing (0.003 m) Elevation (0.003 m) Echo Number (Integer) Echo (Integer) Intensity (16 bit integer) Flight Line (Integer) Scan Angle (degree)
• 2020-09-21 00:00:00 - The final bare-earth lidar points are used to create a terrain. The final 3D breaklines collected for the project are also enforced in the terrain. The terrain is then converted to raster format using linear interpolation. For most projects, a single terrain/DEM can be created for the whole project. For very large projects, multiple terrains/DEMs may be created. The DEM(s) is reviewed for any issues requiring corrections, including remaining lidar mis-classifications, erroneous breakline elevations, poor hydro-flattening or hydro-enforcement, and processing artifacts. After corrections are applied, the DEM(s) is then split into individual tiles following the project tiling scheme. The tiles are verified for final formatting and then loaded into Global Mapper to ensure no missing or corrupt tiles and to ensure seamlessness across tile boundaries.
• NOAA OCM received the bare earth digital elevation model files from the SRWMD. The data were in ESRI GRID format, Florida State Plane North projection and NAVD88 vertical datum using geoid12b, with all units in US survey feet. OCM used internal scripts to convert the files to cloud-optimized geoTIFF format (COGs) and assign the geokeys.

Data is available online for bulk and custom downloads.

Data is backed up to tape and to cloud storage.