National Geophysical Data Center (NGDC), NOAA Satellite and Information Service

View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2010 Coastal Georgia Elevation Project Lidar Data

browse graphicThis kmz file shows the extent of coverage for the 2010 Coastal Georgia lidar data set.
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 - Reserved Class 12 - Overlap

Cite this dataset when used as a source.

Search and Download
    Distribution Formats
    • LAZ
    Distributor DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Point of Contact DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    843-740-1200
    csc.info@noaa.gov
    Associated Resources
    • Lidar QA/QC Report
    • Lidar Survey Final Report
    Originator
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Publisher
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Date(s)
    • publication: 2011-04-01
    Data Presentation Form: Digital image
    Dataset Progress Status Complete
    Data Update Frequency: Unknown
    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?. Quality assurance on collections performed using scan angles wider than 34? 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. All deliverables meet specifications in contract- LAS 1.2 files (ASPRS Classes (1,2,7,9,10,12); Breakline File Geodatabase; 4' ESRI Grid Files, Raw LiDAR Flightlines. LAS Files meet ASPRS Classification Standards.
    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.
    Use Limitations
    • These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
    Time Period: 2010-01-28  to  2010-03-19
    Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
    Spatial Bounding Box Coordinates:
    N: 33.045639
    S: 30.369369
    E: -81.119648
    W: -82.284621
    Spatial Coverage Map:
    Themes
    • Bathymetry/Topography
    • Digital Elevation Model
    • LiDAR
    • DEM
    • Raster
    • Breaklines
    • LAS
    • elevation
    Places
    • US
    • Georgia
    • Charlton County
    • Camden County
    • Brantley County
    • Wayne County
    • McIntosh County
    • Long County
    • Bryan County
    • Effingham County
    • Bulloch County
    • Screven County
    Use Constraints No constraint information available
    Fees Fee information not available.
    Lineage Statement Lineage statement not available.
    Processor
    • DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
    Processing Steps
    • 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.
    • The NOAA Coastal Services Center (CSC) 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. CSC 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.
    • The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.

    Metadata Last Modified: 2013-05-09

    For questions about the information on this page, please email: mike.sutherland@noaa.gov