Data Management Plan
Office for Coastal Management
Data Set (DS) | Cat ID: 48181 | Published / External
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
This data set is the topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements for four
counties in Georgia. These counties are: Burke, Columbia, Lincoln, and Richmond. 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).
LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of
laser range finding, GPS positioning, and inertial measurement technologies. The LiDAR systems collect data point clouds that are used to
produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The LiDAR data acquisition
and processing for Burke, Lincoln, and Richmond County was performed in the Winter of 2011. The LiDAR data was provided to NOAA OCM,
as part of the 4 GA Counties of Elevation Data task order. The 4 GA Counties of Elevation Data task order AOI encompassed approximately
1,739 square miles. The area of interest acquired and processed for Burke, Lincoln, and Richmond County is approximately 1,386 square miles.
The task order required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 1.0 meter. 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 North American Datum 1983, Georgia State Plane Coordinate System, East Zone, and expressed
in US Survey Feet. For data storage and Digital Coast provisioning purposes, the NOAA OCM converted the data to geographic coordinates
and ellipsoid heights in meters. Special Note: Temporal changes of water levels will be observed in any data from Richmond and Lincoln
counties overlapping any previously delivered data from Columbia County.
The final products include full classified LAS, hydrologically flattened four (4) foot pixel raster DEM's of the bare earth surface in
ESRI Floating Point Grid Format (ArcGRID DEMs), and hydrologically flattened breaklines.
The data were collected on the following dates:
Burke and Richmond Counties: December 13, 14, 17, 2011
Columbia County February 26, 2011
Lincoln County December 18, 2011
The data contains las points with the following classifications:
Class 0 No Classification
Class 2 Ground
Class 7 Low Point (Noise)
Class 9 Water
Class 10 Land below sea level
Class 12 Overlap
Original contact information:
Contact Org: NOAA Office for Coastal Management
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)
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.
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):
- 2011-12-13 00:00:00 - Using a Leica LiDAR system, 100 flight lines of high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected over Burke, Lincoln and Richmond Counties, GA (approximately 1,386 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of six (6) missions were flown on December 13, 14, 17, and 18 in 2011. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. The horizontal datum used for this survey is North American Datum 1983, Georgia State Plane Coordinate System, East Zone, 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. System Parameters: Type of Scanner = Leica Data Acquisition Height = 6,500-feet AGL Scanner Field of View = 40 degrees The Scan Frequency = 41.8 Hertz Pulse Repetition Rate - 115.6 Kilohertz Aircraft Speed = 130 Knots Swath Width = 4,732-feet Number of Returns Per Pulse = Maximum of 4 Distance Between Flight Lines = 3,289-feet
- 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.
- 2011-12-18 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.
- 2011-12-19 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.
- 2012-01-12 00:00:00 - Breaklines defining lakes, greater than two acres, and double-line streams, wider than 100 feet (30.5 meters), were compiled using digital photogrammetric techniques as part of the hydrographic flattening process and provided as a geodatabase containing ESRI Polyline Z and Polygon Z feature classes. Breaklines defining water bodies and streams were compiled for this task order. The breaklines were used to perform the hydrologic flattening of water bodies, and gradient hydrologic flattening of double line streams. Lakes, reservoirs and ponds, at a nominal minimum size of two (2) acres or greater, were compiled as closed polygons. The closed water bodies were collected at a constant elevation. Rivers and streams, at a nominal minimum width of 100 feet (30.5 meters), were compiled in the direction of flow with both sides of the stream maintaining an equal gradient elevation. The hydrologic flattening of the LiDAR data was performed for inclusion in the National Elevation Dataset (NED). For this specific project, NOAA requested that Woolpert define the Strom Thurmond Reservoir using a contour set to match the water level used for the portion of the reservoir located in Columbia County. This elevation is 323.55 survey feet. The Columbia county data was acquired several months prior to the Burke, Richmond, and Lincoln Counties. Due to this, the water levels in the reservoir were different. Woolpert set the contour to 325.55 survey feet and classified the las and produced the required products using the contour derived Strom Thurmond Reservoir.
- 2012-08-01 00:00:00 - The NOAA Office for Coastal Management (OCM) 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 survey feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 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 Geoid09. 3. The data were converted from vertical units of survey feet to meters. 4. Elevation outliers were removed.
(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.6. Type(s) of data
- 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.
This data can be obtained on-line at the following URL:
The data set is dynamically generated based on user-specified parameters.
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.