Data Management Plan
DMP Template v2.0.1 (2015-01-01)Please provide the following information, and submit to the NOAA DM Plan Repository.
Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
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.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Data were collected and processed by Woolpert for Georgia DNR through a NOAA contract vehicle. Data are made available through the NOAA Digital Coast.
- 2012-03-06 00:00:00 - 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
- 2011-12-13 00:00:00 - 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.
- 2012-03-26 00:00:00 - 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.
- 2012-09-01 00:00:00 - 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. (Citation: FY 2012 GEORGIA DNR ELEVATION DATA)
- 2019-11-04 00:00:00 - 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. (Citation: FY 2012 GEORGIA DNR ELEVATION DATA)
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
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.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.