gov.noaa.csc.maps:2010_CoastalGA_m577 Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) Photo Science and Fugro EarthData, Inc. 201104 LAS Files Charleston, SC NOAA's Ocean Service, Coastal Services Center (CSC) http://csc-s-maps-q.csc.noaa.gov/dataviewer/viewer.html?missions=577&aoi=-82.2846212998267,-81.1196476999222,30.3693690002025,33.0456389999036 http://www.csc.noaa.gov/lidar http://www.csc.noaa.gov 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 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. 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. The Final QA/QC Quantitative Assessment Report for this data set may be viewed at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ga/CoastalGA_Final_QAQC_Report.pdf Additionally, the Final Project Report (including sensor information, collection parameters, etc.) for this data set may be viewed at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ga/CoastalGA_Final_Project_Report.pdf A footprint of this data set may be viewed in Google Earth at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ga/2010_CoastalGA_Elevation_Project_Lidar.kmz 20100128 20100319 Ground Condition Complete Unknown -82.284621 -81.119648 33.045639 30.369369 ISO 19115 Topic Category elevation None Bathymetry/Topography Digital Elevation Model LiDAR DEM Raster Breaklines LAS elevation None US Georgia Charlton County Camden County Brantley County Wayne County McIntosh County Long County Bryan County Effingham County Bulloch County Screven County None 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. Photo Science, Inc. acquired Brantley, Camden, Charlton, and Wayne Counties. Fugro EarthData, Inc. acquired Bryan, Bulloch, Effingham, Long, McIntosh, and Screven Counties. 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 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. 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. Datasets contain complete coverage of tiles. Compiled to meet a horizontal accuracy of 1.2 meters (4 ft) RMSE or better. 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. 0.196 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 . Photo Science and Fugro EarthData, Inc. 2010 digital data Hard Drive 20100128 20100319 ground condition LiDAR LiDAR points were used to produce the deliverables. 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. LiDAR 2010 LiDAR post-processed data DEM Hydro Flattening Break Lines 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. 20110420 NOAA Coastal Services Center Clearinghouse Manager mailing and physical

2234 South Hobson Ave.

Charleston SC 29405-2413 843-740-1210 clearinghouse@noaa.gov The NOAA National Geophysical Data Center (NGDC) received Lidar data files on external harddrive. The disk contains LiDAR data from the NOAA Coastal Services Center. The data are currently being served via Digital Coastl at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are provided on this disk in LAS format. LAS format is an industry standard for serving LiDAR data. The data are exclusively in geographic coordinates, however, the datums used vary. Most are NAD 83, however some are in ITRF. Vertical systems include both ellipsoid (ITRF and NAD 83) and NAVD 88. For NAVD 88 values, Geiod 03 is primarily used; however, data received in NAVD 88 prior to 2003 was processed using Geoid 99. 20111031 DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce Pamela Grothe Mailing and Physical Address

NOAA/NESDIS/NGDC E/GC1 325 Broadway

Boulder CO 80305-3328 USA (303) 497-6120 (303) 497-6958 (303) 497-6513 pamela.grothe@noaa.gov 7:30-5:00 Mountain Contact Data Center 0.0000001 0.0000001 Decimal degrees North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 Ellipsoid 0.001 meters Explicit elevation coordinate included with horizontal coordinates LAS 1.2 files (ASPRS Classes (1,2,7,9,10,12); Breakline File Geodatabase; 4' ESRI Grid Files, Raw LiDAR Flightlines All deliverables meet specifications in contract. LAS Files meet ASPRS Classification Standards. NOAA Coastal Services Center Clearinghouse Manager mailing and physical

2234 South Hobson Ave.

Charleston SC 29405-2413 843-740-1210 clearinghouse@noaa.gov Downloadable Data Any conclusions drawn from the analysis of this information are not the responsibility of the Coastal Services Center or its partners. This data can be obtained on-line at the following URL: http://www.csc.noaa.gov/lidar DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce Pamela Grothe Mailing and Physical Address

NOAA/NESDIS/NGDC E/GC1 325 Broadway

Boulder CO 80305-3328 USA (303) 497-6120 (303) 497-6958 (303) 497-6513 pamela.grothe@noaa.gov 7:30-5:00 Mountain Contact Data Center Disclaimer While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty. The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from NOAA Coastal Services Center. 20111119 20111119 20121119 NOAA Coastal Services Center Clearinghouse Manager mailing and physical Charleston SC 29405-2413 843-740-1210 clearinghouse@noaa.gov FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998