gov.noaa.nmfs.inport:49728 eng UTF8 dataset OCM Partners resourceProvider NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact 2026-04-30T00:00:00 ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data ISO 19115-2:2009(E) 2010 ARC Dekalb County Georgia Lidar ga2010_arc_dekalbcounty_m2527_metadata 2012-08-13 publication NOAA/NMFS/EDM 49728 https://www.fisheries.noaa.gov/inport/item/49728 WWW:LINK-1.0-http--link Full Metadata Record View the complete metadata record on InPort for more information about this dataset. information https://coast.noaa.gov/dataviewer WWW:LINK-1.0-http--link Citation URL Online Resource download https://coast.noaa.gov WWW:LINK-1.0-http--link Citation URL Online Resource download This metadata record describes the DTM comprised of classified aerial lidar elevation points, photogrammetrically compiled breaklines and the derived TIN for Dekalb County, GA Original contact information: Contact Name: Stacy Grear Contact Org: Dekalb County GIS Department Title: Acting Director Phone: 404-371-3619 Email: scgrear@dekalbcountyga.gov will change to scgrear@dekalbcountyga.gov on July 1, 2010 The lidar DEM data was collected for the Dekalb County, GA area. All lidar returns were classified using the default classes of Terrascan processing software for Unclassified Points (class 1), Ground points (class 2), Water points (class 9), Overlap points (class 12). The lidar ground points are supplemented with photogrammmetrically compiled breaklines from digital imagery collected during the same project time frame as the lidar. The ground class points, often refered to as "bald earth" are then used as an input to proprietary and publicly available processing software to generate a Triangulated Irregular Network (TIN) model. Classified lidar DEMs and derived TIN models are useful for a variety of applications, such as aiding in contour generation, development of digital surface models, 3D modeling, flood plane mapping, viewshed analysis and the production of orthophotos. Please credit the Deklab County GIS Department Puget with support from the Atlanta Regional Commission with this data. completed NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information custodian unknown https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty.KMZ This graphic shows the lidar coverage for the 2010 Dekalb County Lidar Survey in Georgia. kmz TIN Triangulated Irregular Network mapping theme Lidar - partner (no harvest) project InPort otherRestrictions Cite As: OCM Partners, [Date of Access]: 2010 ARC Dekalb County Georgia Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49728. NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. otherRestrictions Access Constraints: None otherRestrictions Use Constraints: 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. These data depict the heights at the time of the survey and are only accurate for that time. otherRestrictions Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Kucera International, ARC, USGS, NOAA, the Office for Coastal Management or its partners. unclassified vector eng; US elevation -84.35091417 -84.02334971 33.61447836 33.97061816 | Currentness: Ground Condition 2010-01-02 | Currentness: Ground Condition 2010-01-03 A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty.KMZ A Lidar Report from the vendor for this data set may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty_QC_Report.pdf false eng false none NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information distributor https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2527 WWW:LINK-1.0-http--link Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/index.html WWW:LINK-1.0-http--link Bulk Download Simple download of data files. download dataset Accuracy Attribute accuracy is tested in the LiDAR processing stage. After classification of the LiDAR data, the 'bald earth' point class is compared to ground control collected within the project area. Horizontal Positional Accuracy Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy are less than 1 meter.; Quantitative Value: 1 meters, Test that produced the value: This value is computed by comparing ground control to an intensity based image derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. Vertical Positional Accuracy Vertical positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The vertical accuracy for this project was tested with a resultant RMSE of 0.057 meter (0.188 feet).; Quantitative Value: 0.057 meters, Test that produced the value: This value is computed by comparing ground control elevation to the classified LiDAR ground surface and represents the RMSE of residuals on controls within the project area. Units = meters. Completeness Report LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. The ground class points are then compared to surveyed ground control to develop an accuracy measure of the laser terrain data. Conceptual Consistency LiDAR data is collected within the project area, processed and verified against control. At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. 2010-01-01T00:00:00 New LiDAR data is captured for the project area using a Leica ALS60 LiDAR instrument in conjunction with a POSAV Applanix GPS/INS system mounted within a Piper Navajo twin engine airplane. 2010-01-01T00:00:00 New aerial digital imagery with airborne GPS/IMU data is acquired for the project area. 2010-01-01T00:00:00 The airborne GPS data is processed in Terratec TerraPos software and then combined with the IMU data in Applanix PosPAC software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey. The same GPS/IMU processing is performed for the digital imagery to define the orientation parameters of the images to be used in stereo compilation of terrain breaklines. 2010-01-01T00:00:00 LiDAR data is processed using the GPS/INS solution. Data is classified to produce: Class 1: unclassified points Class 2: ground points Class 9: water points Class 12: overlap points 2010-01-01T00:00:00 The ground class of the processed lidar data is then compared to the ground control and elevation differences between the lidar surface and surveyed elevation are recorded in tabular form. Vertical accuracy statistices are then developed to produce vertical RMSE and overall accuracy estimates and reports. 2010-01-01T00:00:00 Photogrammetrically compiled breaklines are compiled to supplement the lidar ground points. 2010-01-01T00:00:00 Water polygons are buffered to remove any lidar points within the polygon to flatten these surfaces. 2010-01-01T00:00:00 Breaklines are buffered to remove lidar surface points on or near the breakline. 2010-01-01T00:00:00 The Traingulated Irregular Network is generate with ESRI ArcGIS software. 2010-01-01T00:00:00 The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in projected Georgia State Plane West Zone 1002 coordinates and were vertically referenced to NAVD88. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were processed through a lastools program known as LASGround, where an algorithm further processes any unclassified points to the ground class, ignoring pre-exisint ground points. 2. All files were then horizontally shifted from the projected GA_W (1002) state place coordinates (in feet) to geographic NAD83 coordinates (decimal degrees) 3. All files were then vertically shifted from from orthometric NAVD88 heights (feet) to ellipsoidal NAD83 (meters) using GEOID09 (assumed based on processing date) 2013-08-09T00:00:00 Source Contribution: New digital aerial imagery and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc Aerial Digital Imagery 2010-02-18 Source Contribution: Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted. | Source Geospatial Form: tabular digital data | Type of Source Media: disc Ground control 2010-01-01 publication 2010 Source Contribution: Aerial LiDAR and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc LiDAR Data 2010-01-02 Source Contribution: Using the lidar elevation points and compiled breaklines as inputs, a Triangulated Irregular Network (TIN) is generated using ESRI ArcGIS software. | Source Geospatial Form: Vector digital data | Type of Source Media: disc Triangulated Irregular Network 2010-01-01 publication 2010