Short Citation:
Office for Coastal Management, 2021: 2010 Coastal Georgia Elevation Project Lidar Data, https://www.fisheries.noaa.gov/inport/item/48167.

Item Identification

Title: 2010 Coastal Georgia Elevation Project Lidar Data
Short Name: coastalga2010_m577_metadata
Status: Completed
Publication Date: 2011-04
Abstract:

Between January and March 2010, lidar data was collected in southeast/coastal Georgia under a multi-agency partnership between the Coastal Georgia

Regional Development Center, USGS, FEMA, NOAA and local county governments. Data acquisition is for the full extent of coastal Georgia,

approximately 50 miles inland, excluding counties with existing high-resolution lidar derived elevation data. The data capture area consists

of an area of approximately 5703 square miles. This project is within the Atlantic Coastal Priority Area as defined by the National Geospatial

Program (NGP) and supports homeland security requirements of the National Geospatial-Intelligence Agency (NGA). This project also supports

the National Spatial Data Infrastructure (NSDI) and will advance USGS efforts related to The National Map and the National Elevation Dataset.

The data were delivered in LAS format version 1.2 in 5000 x 5000 foot tiles. The data are classified according to ASPRS LAS 1.2 classification

scheme:

Class 1 - Unclassified

Class 2 - Bare Earth

Class 7 - Low Point (Noise)

Class 9 - Water

Class 10 - Land below sea level

Class 12 - Overlap

Purpose:

The purpose of this project is to provide professional surveying and mapping services to collect and deliver topographic elevation data derived

from multiple return light detection and ranging (lidar) measurements for areas in southeast / coastal Georgia. These data are intended for use

in coastal management decision making, including applications such as sea level rise and coastal flood mapping.

Lifts were planned to meet project specifications and were flown under cloud-free conditions in order to collect LiDAR points at an average

of 1.0 meter point spacing. This allows the user to create Intensity Images, Break Lines, and fully Classified LiDAR LAS files.

Notes:

10190

Supplemental Information:

All flights for the project were accomplished with customized aircraft outfitted with state of the art navigation systems and the latest in LiDAR

sensor technology. The LiDAR sensors used for this project consisted of Leica ALS 50-II's and ALS 60 and Optech Gemini. Each was configured to meet

or exceed the project specifications which included:

1. Multiple Discrete Return, capable of at least 3 returns per pulse with Intensity values for each return.

2. Nominal Pulse Spacing (NPS) no greater than 1 meter with distribution of geometrically usable points expected to be uniform and free from

clustering.

3. Scan Angle (total Field-of-View (FOV)) should not exceed 40 degrees. Quality assurance on collections performed using scan angles wider than 34 degrees

will be particularly rigorous in the edge-of-swath areas.

4. Accuracy, The National Standard for Spatial Data Accuracy (NSSDA) of 95% confidence level, equal to (RMSEZ * 1.96) in a set of errors assumed

to be normally distributed. Fundamental Vertical Accuracy (FVA) of NSSDA RMSEZ = 18cm (NSSDA AccuracyZ 95% = 36 cm) or better; assessment

procedures to comply with FEMA guidelines.

5. Horizontal accuracy of 4 feet RMSE or better. Additionally, the Consolidated Vertical Accuracy (computed using NDEP and ASPRS methodology

in five (5) separate land cover classes (TBD)) shall meet ASPRS Class 1 (or National Map Accuracy Standard) guidelines for the generation

of 2 foot contours (Accuracyz = 36 cm). LiDAR data from different flight lines shall be consistent across flight lines, i.e., there is minimal

vertical offset within the noise level of the LiDAR system between adjacent flightlines. Maximum vertical offset between flightlines should be

no more than 6 cm.

6. Flightline overlap 20% or greater, as required to ensure there are no data gaps between the usable portions of the swaths.

7. Base stations for GPS surveys shall be based on first or second order survey control stations that are part of the National Geodetic Survey's

Spatial Reference System.

8. Collection Area: Defined Project Area, buffered by a minimum of 200*NPS.

9. Tide: +/- 2 hours of low tide.

Brantley and Wayne Counties were flown using an Optech Sensor. Bryan, Bulloch, Charlton, Effingham, Long, McIntosh, and Screven Counties were flown

using a Leica Sensor. Both sensors were used on Camden County.

Keywords

Theme Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Science Keywords Earth Science > Land Surface > Topography > Terrain Elevation > Topographical Relief Maps
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Bathymetry/Seafloor Topography > Seafloor Topography
Global Change Master Directory (GCMD) Science Keywords Earth Science > Oceans > Coastal Processes > Coastal Elevation
ISO 19115 Topic Category elevation
None Bathymetry/Topography
None Breaklines
None DEM
None Digital Elevation Model
None elevation
None LAS
None LiDAR
None Raster

Spatial Keywords

Thesaurus Keyword
Global Change Master Directory (GCMD) Location Keywords Continent > North America > United States Of America > Georgia
None Brantley County
None Bryan County
None Bulloch County
None Camden County
None Charlton County
None Effingham County
None Georgia
None Long County
None McIntosh County
None Screven County
None US
None Wayne County

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 Files
Entity Attribute Overview:

LAS 1.2 files (ASPRS Classes (1,2,7,9,10,12); Breakline File Geodatabase; 4' ESRI Grid Files, Raw LiDAR Flightlines

Entity Attribute Detail Citation:

All deliverables meet specifications in contract. LAS Files meet ASPRS Classification Standards.

Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of the Office for Coastal Management

or its partners.

Data Set Credit: Photo Science, Inc. acquired Brantley, Camden, Charlton, and Wayne Counties. Fugro EarthData, Inc. acquired Bryan, Bulloch, Effingham, Long, McIntosh, and Screven Counties.

Support Roles

Data Steward

CC ID: 623261
Date Effective From: 2011-04
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: 623263
Date Effective From: 2011-04
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: 623264
Date Effective From: 2011-04
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: 623262
Date Effective From: 2011-04
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: 1046987
W° Bound: -82.284621
E° Bound: -81.119648
N° Bound: 33.045639
S° Bound: 30.369369

Extent Group 1 / Time Frame 1

CC ID: 1046986
Time Frame Type: Range
Start: 2010-01-28
End: 2010-03-19

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;

Data Access Constraints:

None

Data Use Constraints:

None. However, users should be aware that temporal changes may have occurred since this data set was collected and that some parts of the data may

no longer represent actual surface conditions. Users should not use the data for critical applications without a full awareness of its limitations.

Distribution Information

Distribution 1

CC ID: 743737
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=577
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: 743738
Download URL: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/577
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

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

URL 2

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

URL 3

CC ID: 754988
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/577/supplemental/CoastalGA_Final_QAQC_Report.pdf
URL Type:
Online Resource
Description:

Link to the The Final QA/QC Quantitative Assessment Report.

URL 4

CC ID: 754989
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/577/supplemental/CoastalGA_Final_Project_Report.pdf
URL Type:
Online Resource
Description:

Link to the Final Project Report (including sensor information, collection parameters, etc.).

URL 5

CC ID: 754990
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/577/supplemental/2010_CoastalGA_Elevation_Project_Lidar.kmz
Name: Browse graphic
URL Type:
Browse Graphic
Description:

Link to the data set footprint.

URL 6

CC ID: 754991
URL: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/577/breaklines/
URL Type:
Online Resource
Description:

Link to the breaklines.

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

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

Converted from FGDC Content Standard 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: 717637
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Technical Environment

Description:

MicroStation Version 8; TerraScan Version 10; Optech DASHMap 4.1801; TerraModeler Version 10; GeoCue Version 6.1.21.4; ESRI ArcGIS 9.3.1;

Global Mapper Version 11.02; ALS Post Processor 2.70 Build #15; Windows XP Operating System

Data Quality

Accuracy:

The project area requires LiDAR to be collected on average of 1.0 meter point spacing or better and vertical accuracy of 18.0 centimeters RMSE

or better to support 2' contour generation when combined with breaklines.

Horizontal Positional Accuracy:

Compiled to meet a horizontal accuracy of 1.2 meters (4 ft) RMSE or better.

Vertical Positional Accuracy:

Compiled to meet National Standards for Spatial Data Accuracy; For this project, vertical accuracy at the 95% confidence interval must be 36cm

or less based on an RMSEz of 18cm x 1.96.

; Quantitative Value: 0.196 meters, Test that produced the value:

The vertical accuracy assessment compares the measured survey checkpoint elevations with those of the TIN as generated from the bare-earth LiDAR.

The X/Y locations of the survey checkpoints are overlaid on the TIN and the interpolated Z values of the LiDAR are recorded. These interpolated

Z values are then compared with the survey checkpoint Z values and this difference represents the amount of error between the measurements.

Once all the Z values are recorded, the Root Mean Square Error (RMSEz) is calculated and the vertical accuracy scores are interpolated from

the RMSE value. The RMSEz equals the square root of the average of the set of squared differences between the dataset coordinate values and the

coordinate values from the survey checkpoints.

Based on the vertical accuracy testing conducted by Dewberry using NSSDA and FEMA methodology, fundamental vertical accuracy (FVA) at the 95%

confidence level (called Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for CGEP satisfies the criteria outlined in project

specifications and tested 0.196 m in open terrain, based on RMSEz (0.10 m) x 1.9600 .

Completeness Report:

Datasets contain complete coverage of tiles.

Conceptual Consistency:

Deliverables were tested by both Photo Science and Fugro EarthData for both vertical and horizontal accuracy. All data are seamless from one

tile to the next, no gaps or no data areas.

Lineage

Sources

LiDAR

CC ID: 1046982
Publish Date: 2010-01-01
Extent Type: Range
Extent Start Date/Time: 2010-01-28
Extent End Date/Time: 2010-03-19
Source Contribution:

LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: Hard Drive

Process Steps

Process Step 1

CC ID: 1046983
Description:

Applanix software was used in the post processing of the airborne GPS and inertial data that is critical to the positioning and orientation

of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for Optech's post

processor to develop the point cloud from the LiDAR missions. The point cloud is the mathematical three dimensional collection of all returns

from all laser pulses as determined from the aerial mission. At this point this data is ready for analysis, classification, and filtering to

generate a bare earth surface model in which the above ground features are removed from the data set. The point cloud was manipulated within

the Optech or Leica software; GeoCue, TerraScan, and TerraModeler software was used for the automated data classification, manual cleanup,

and bare earth generation from this data. Project specific macros were used to classify the ground and to remove the side overlap between

parallel flight lines.

All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler.

Class 2 LIDAR was used to create a bare earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland

streams and rivers. The National Elevation Dataset (1/3 arc-second) was used as a supplement to calculate streams with a contributing

drainage area of greater than 1 square mile.

Inland Ponds, Lakes, and Mudflats of 0.5 acres or greater were also collected along with the Coastal Shoreline.

Elevation values were assigned to all Inland Ponds, Lakes, and Shorelines using TerraModeler functionality.

Elevation values were assigned to all Inland streams, rivers, and mudflats using Photo Science proprietary software.

All Class 2 LIDAR data inside of the collected breaklines were then classified to Class 9 using TerraScan macro functionality.

The breakline files were then translated to ESRI Shapefile format using ESRI conversion tools.

Data was then run through additional macros to ensure deliverable classification levels matching LAS ASPRS Classification structure.

GeoCue functionality was then used to ensure correct LAS Version. In house software was used as a final QA/QC check to provide LAS Analysis

of the delivered tiles.

Buffered LAS files were created in GeoCue to provide overedge to the DEM creation. These tiles were then run through automated scripting

within ArcMap and were combined with the Hydro Flattened Breaklines to create the 4' DEM. Final DEM tiles were clipped to the tile boundary

in order to provide a seamless dataset.

A manual QA review of the tiles was completed in ArcMap to ensure full coverage with no gaps or slivers within the project area.

Process Date/Time: 2010-01-01 00:00:00

Process Step 2

CC ID: 1046984
Description:

The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained lidar elevation and intensity measurements.

The data were in State Plane projection (NAD83, Georgia East), and vertically referenced to NAVD88 using the Geoid 09 model. Both horizontal

and vertical units were in feet. OCM performed the following processing to the data to make it available within the Digital Coast:

1. The data were converted from Georgia State Plane coordinates to geographic (NAD83) coordinates.

2. The data were converted from orthometric (NAVD88) heights to ellipsoidal heights (GRS80) using Geoid 09.

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

Process Date/Time: 2011-04-20 00:00:00

Catalog Details

Catalog Item ID: 48167
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-14 14:19+0000
Metadata Record Last Modified By: Kirk Waters
Metadata Record Last Modified: 2021-03-02 13:54+0000
Metadata Record Published: 2021-03-02
Owner Org: OCM
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2022-03-03