2012 GA DNR Lidar DEM: Floyd, Paulding, Oconee, and Polk Counties
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:58141 | Updated: January 10, 2024 | Published / External
Item Identification
Title: | 2012 GA DNR Lidar DEM: Floyd, Paulding, Oconee, and Polk Counties |
---|---|
Short Name: | 2012 Floyd Paulding Oconee Polk m8919 |
Status: | Completed |
Creation Date: | 2012 |
Publication Date: | 2012-09-23 |
Abstract: |
The PSFY12 GADNR Elevation Data Task Order involves: collecting and delivering topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements for portions of 4 counties in Georgia. The Statement of Work (SOW) was developed by the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management (referred to as the Center) in partnership with the Georgia Department of Natural Resources (GADNR) Environmental Protection Division (EPD). The counties included Floyd, Polk, Paulding and Oconee. The purpose of the data is for use in coastal management decision making, including applications such as flood plain mapping and water rights management. LiDAR was collected at 1.0 points per square meter (1.0m GSD) for the portions of Floyd, Polk, Paulding and Oconee Counties. This area was flown during snow free and leaf-off conditions. TASK NAME:FY 2012 GEORGIA DNR ELEVATION DATA NOAA Contract No. EA133C11CQ0010 Requisition No. NCNP0000-11-02615 Woolpert Order No. 71511 CONTRACTOR: Woolpert, Inc. |
Purpose: |
This task order consisted of LiDAR data acquisition and processing for the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management (OCM) four Counties in Georgia: Floyd, Oconee, Paulding and Polk. The LiDAR data acquisition and processing for Floyd, Oconee, Paulding and Polk Counties was performed in the Spring of 2012. The LiDAR data was provided to NOAA OCM, as part of the FY 2012 Georgia Elevation Data task order. The task order area for Floyd, Polk, and Paulding Counties was approximately 460.6 square miles, and the task order area for Oconee County was approximately 233.6 square miles The LiDAR data was collected to meet Fundamental Vertical Accuracy (FVA) Root Mean Square Error (RMSE) of 18.0 cm or better at a 95% confidence level, so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data was delivered in 5,000' x 5,000' tiles using NAD 1983 (NSRS2007), Georgia State Plane Coordinate System, West Zone 1002. |
Supplemental Information: |
The reflective surface data represents the DEM created by the laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface, to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor. The bare earth model is created by identifying the returns that fall on the ground surface and by interpolating a surface between these points. In this manner, buildings and vegetation are removed from the bare earth model. This data set does not include bridges and overpasses in the bare earth model as the delineation point for these structures is not reliably discernable in the LiDAR data. The third-party QA report for this data set may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/1420/supplemental/2012_gadnr_lidar_Acquisition_Report.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/1420/supplemental/2012_NOAA_Georgia_LiDAR_Footprints.kmz |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category |
elevation
|
UNCONTROLLED | |
None | DEM |
Physical Location
Organization: | Office for Coastal Management |
---|---|
City: | Charleston |
State/Province: | SC |
Data Set Information
Data Set Scope Code: | Data Set |
---|---|
Maintenance Frequency: | As Needed |
Data Presentation Form: | las |
Entity Attribute Overview: |
LiDAR points in LAS 1.2 format |
Entity Attribute Detail Citation: |
none |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of Woolpert, NOAA, GADNR, the Office for Coastal Management or its partners. |
Support Roles
Data Steward
Date Effective From: | 2012-09-23 |
---|---|
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
Date Effective From: | 2012-09-23 |
---|---|
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
Date Effective From: | 2012-09-23 |
---|---|
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
Date Effective From: | 2012-09-23 |
---|---|
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
W° Bound: | -85.26314 | |
---|---|---|
E° Bound: | -83.249536 | |
N° Bound: | 34.367865 | |
S° Bound: | 33.681195 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2012-03-06 |
Extent Group 1 / Time Frame 2
Time Frame Type: | Discrete |
---|---|
Start: | 2012-03-19 |
Extent Group 1 / Time Frame 3
Time Frame Type: | Discrete |
---|---|
Start: | 2012-03-20 |
Extent Group 1 / Time Frame 4
Time Frame Type: | Discrete |
---|---|
Start: | 2012-03-25 |
Extent Group 1 / Time Frame 5
Time Frame Type: | Discrete |
---|---|
Start: | 2012-03-26 |
Spatial Information
Spatial Resolution
Horizontal Distance: | 4.0 Foot |
---|
Spatial Representation
Representations Used
Grid: | Yes |
---|
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reference System 2
Coordinate Reference System |
|||||||||||||||||||||||
|
Access Information
Security Class: | Unclassified |
---|---|
Security Classification System: |
Unclassified |
Security Handling Description: |
Unclassified |
Data Access Procedure: |
This data can be obtained through the online application https://coast.noaa.gov/dataviewer. Custom processing can be done for small areas or there is a bulk download link to get the full dataset. |
Data Access Constraints: |
None |
Data 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. |
Distribution Information
Distribution 1
Start Date: | 2012-09-03 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8919 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2012-09-23 - Present) |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2012-09-03 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/GA_Floyd_Polk_Paulding_Oconee_2012_8919/index.html |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2012-09-23 - Present) |
File Name: | Bulk Download |
Description: |
Simple download of data files. |
File Type (Deprecated): | GeoTIFF |
Distribution Format: | GeoTIFF |
URLs
URL 1
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/1420/breaklines/GA_Flyod_Paulding_Oconee.zip |
---|---|
Name: | Breaklines |
URL Type: |
Online Resource
|
File Resource Format: | zip |
Description: |
Breaklines for the counties in GDB format. Breaklines have not been evaluated by NOAA. |
URL 2
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/1420/supplemental/2012_gadnr_lidar_Acquisition_Report.pdf |
---|---|
Name: | Acquistion Report |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Report from the lidar contractor. |
URL 3
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/1420/supplemental/2012_NOAA_Georgia_LiDAR_Footprints.kmz |
---|---|
Name: | Browse Graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | kmz |
Description: |
This graphic shows the lidar coverage for Polk County, Paulding County, Floyd County and Oconee County in Georgia. |
URL 4
URL: | https://coast.noaa.gov/dataviewer |
---|---|
Name: | Data Access Viewer |
URL Type: |
Online Resource
|
Description: |
Application to provide custom processing of datasets. |
Activity Log
Activity Log 1
Activity Date/Time: | 2016-05-23 |
---|---|
Description: |
Date that the source FGDC record was last modified. |
Activity Log 2
Activity Date/Time: | 2017-11-14 |
---|---|
Description: |
Converted from FGDC Content Standards 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
Activity Date/Time: | 2018-02-08 |
---|---|
Description: |
Partial upload of Positional Accuracy fields only. |
Activity Log 4
Activity Date/Time: | 2018-03-13 |
---|---|
Description: |
Partial upload to move data access links to Distribution Info. |
Data Quality
Accuracy: |
The LiDAR collected for this task order was collected to meet a Fundamental Vertical Accuracy (FVA) of NSSDA RMSEZ = 18cm (NSSDA AccuracyZ 95% = 30cm) or better; assessment procedures to comply with FEMA, NSSDA, NDEP, and ASPRS guidelines. |
---|---|
Horizontal Positional Accuracy: |
Horizontal accuracy is +/- 4 foot at the 95% confidence level using RMSE(r) x 1.7308 when compared to the classified lidar, as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA. LiDAR system calibration is available in the project report. |
Vertical Positional Accuracy: |
The LiDAR data vertical accuracy RMSE is 5.7 cm (0.188 ft) when compared to the classified lidar. The data collected under this Task Order meets the FEMA, NSSDA, NDEP, and ASPRS guidelines for accuracy standards. These standards specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy. (http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html). 46 survey control points were used for lidar processing The Fundamental Vertical Accuracy (FVA) of the TIN: 11.2 cm (0.368 ft) at a 95% confidence level, derived according to NSSDA. Forty-Six (46) control points were were surveyed by Woolpert survey crews and used for the lidar processing and accuracy reporting. The control points and their coordinates can be found in section 6 of the lidar processing report. Vertical Accuracy Statistics Floyd, Polk and Paulding Counties, Georgia: Tested 0.399 feet fundamental vertical accuracy at 95 percent confidence level when compared to the classified lidar in open terrain using RMSE(z) x 1.9600. Vertical Accuracy Statistics Oconee County, Georgia: Tested 0.352 feet fundamental vertical accuracy at 95 percent confidence level when compared to the classified lidar in open terrain using RMSE(z) x 1.9600 OVERALL Vertical Accuracy Statistics Floyd, Polk, Paulding and Oconee Counties, Georgia: Tested 0.368 feet fundamental vertical accuracy at 95 percent confidence level when compared to the classified lidar in open terrainusing RMSE(z) x 1.9600. |
Completeness Report: |
The LiDAR data is visually inspected for completeness to ensure that are no gaps between flight lines. |
Conceptual Consistency: |
All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery. |
Lineage
Lineage Statement: |
Data were collected and processed by Woolpert for Georgia DNR through a NOAA contract vehicle. Data are made available through the NOAA Digital Coast. |
---|
Sources
FY 2012 GEORGIA DNR ELEVATION DATA
Publish Date: | 2012-09-23 |
---|---|
Extent Type: | Discrete |
Extent Start Date/Time: | 2012-03-06 |
Source Contribution: |
The LiDAR data collected for this task order. | Source Geospatial Form: vector digital data | Type of Source Media: disc |
Process Steps
Process Step 1
Description: |
Using a Leica LiDAR system, 84 flight lines of high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected over Floyd, Oconee, Paulding and Polk Counties, GA (approximately 694.2 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of five (5) missions were flown on March 6, 19, 20, 25 and 26 in 2012. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. The horizontal datum used for this survey is NAD 1983 NSRS2007, Georgia State Plane Coordinate System, West Zone 1002, and expressed in US Survey Feet. The vertical datum used for this survey is North American Vertical Datum 1988 (NAVD88), and expressed in US Survey Feet. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The aerial LiDAR was collected at the following sensor specifications for the Oconee County Project: Post Spacing (Minimum): 3.28 ft / 1.0 m AGL (Above Ground Level) average flying height: 6,500 ft / 1,981 m MSL (Mean Sea Level) average flying height: 6,940 ft / 2,115 m Average Ground Speed: 130 knots / 149 mph Field of View (full): 40 degrees Pulse Rate: 115.6 kHz Sensor Scan Rate: 41.8 Hz Side Lap (Minimum): 25% Flight Lines Flown at these specifications: 1 - 27 (All) The aerial LiDAR was collected at two different sensor specifications for the Floyd, Polk, and Paulding Counties Project: Those LIDAR flight lines that entered the Atlanta Class B Airspace restriction area were flown at a lower altitude specification in order to maintain an altitude of 6500 feet MSL. These instructions were mandated by Atlanta Tracon. Post Spacing (Minimum): 3.28 ft / 1.0 m AGL (Above Ground Level) average flying height: 6,500 ft / 1,981 m MSL (Mean Sea Level) average flying height: 7,075 ft / 2,156 m Average Ground Speed: 130 knots / 149 mph Field of View (full): 40 degrees Pulse Rate: 115.6 kHz Sensor Scan Rate: 41.8 Hz Side Lap (Minimum): 25% Flight Lines Flown at these specifications: 1 - 20 Post Spacing (Minimum): 3.28 ft / 1.0 m AGL (Above Ground Level) average flying height: 5,925 ft / 1,825 m MSL (Mean Sea Level) average flying height: 6,500 ft / 1,981 m Average Ground Speed: 130 knots / 149 mph Field of View (full): 44 degrees Pulse Rate: 124.0 kHz Sensor Scan Rate: 43.1 Hz Side Lap (Minimum): 25% Flight Lines Flown at these specifications 21 - 57 |
---|---|
Process Date/Time: | 2012-03-06 00:00:00 |
Process Step 2
Description: |
The Leica ALS50/60 LiDAR systems calibration and performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles. |
---|---|
Process Date/Time: | 2011-12-13 00:00:00 |
Process Step 3
Description: |
Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the task order. |
---|---|
Process Date/Time: | 2012-03-26 00:00:00 |
Process Step 4
Description: |
The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), noise (Class 7), water (Class 9) ignored ground (Class 10), unclassified data (Class 1), and overlap points (Class 12). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset. |
---|---|
Process Date/Time: | 2012-09-01 00:00:00 |
Source: | FY 2012 GEORGIA DNR ELEVATION DATA |
Process Step 5
Description: |
The NOAA Office for Coastal Management (OCM) received topographic DEM files in ERDAS Imagine format. The files were converted to GeoTiff format for distribution in the Digital Coast Data Access Viewer and to conform to the Open Data Policy. Georeferencing was added to indicate the vertical reference system was NAVD88 in survey feet. The geoid model of GEOID09 was not changed. |
---|---|
Process Date/Time: | 2019-11-04 00:00:00 |
Process Contact: | NOAA Office for Coastal Management (NOAA/OCM) |
Phone (Voice): | (843) 740-1202 |
Email Address: | coastal.info@noaa.gov |
Source: | FY 2012 GEORGIA DNR ELEVATION DATA |
Catalog Details
Catalog Item ID: | 58141 |
---|---|
GUID: | gov.noaa.nmfs.inport:58141 |
Metadata Record Created By: | Kirk Waters |
Metadata Record Created: | 2019-11-04 07:24+0000 |
Metadata Record Last Modified By: | Kirk Waters |
Metadata Record Last Modified: | 2024-01-10 19:09+0000 |
Metadata Record Published: | 2024-01-10 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2022-03-16 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2023-03-16 |