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 Digital Elevation Models (DEM) were generated at a 3.125 foot resolution as rasters, using the ground (Class 2) points and the hydro flattened breaklines as inputs from the project. The DEMs were produced specific to the 2016 Phase Four project area consisting of 20 North Carolina counties. LiDAR data for the project and the validation site was collected by a single aerial vendor on ESP team between February 27, 2016 and April 17, 2016 and between December 9, 2016 and February 21 of 2017 using Geiger-mode Avalanche Photodiode (GmAPD) sensors. The aerial vendor on the ESP team was Harris Corporation (Harris).Two GmAPD (Geiger-mode) sensors (serial numbers 002 and 003) were used for the data collection of LiDAR data at a 0.35 meter nominal post spacing (NPS). The following counties or portions of counties were collected in the February through April, 2016 mobilization: Alleghany, Stokes, Surry, Cleveland, Gaston, Mecklenburg, Cabarrus, Stanly, Union, and Anson. The following counties or portions of counties we collected in the December, 2016 through February, 2017 mobilization: Cleveland, Gaston, Mecklenburg, Cabarrus, Stanly, Wilkes, Yadkin, Forsyth, Alexander, Catawba, Iredell, Davie, Rowan, and Davidson. All data was collected during leaf-off conditions. Ground survey support for the project included the establishment of GPS base stations and the collection of control points used for calibration. All data was delivered in the North Carolina State Plane Coordinate System, with a horizontal datum of NAD83 (2011), vertical datum of NAVD88 (Geoid 12B), in US Survey Feet. Data was delivered tiled to a 2,500 foot by 2,500 foot tiling scheme unless otherwise specified in this product description. All LiDAR was delivered in LASer (LAS) version 1.4 standard format. Products for this project derived from the source LiDAR included: intensity images in GeoTIFF format, hydro-flattening breaklines in ESRI File Geodatabase format, Digital Elevation Models (DEMs) in TIF format, ESRI Terrain Datasets (by county) in ESRI File Geodatabase format, product and project-level metadata, and project reports to include the Report of Survey, Post-Acquisition Report, and Project Report. All LiDAR and derivative products for this project met the specifications stipulated in Delivery Order 22, the NC LiDAR Standard, and the USGS minimum standards for QL1 LiDAR data. This project was a joint effort between NC Emergency Management, NC Geodetic Survey, and the NCDOT. The following people served as the main representatives for each stakeholder: NC Emergency Management- Hope Morgan (primary contact) and John Dorman; NC Geodetic Survey- Gary Thompson and Watson Ross; NCDOT- Keith Johnston and Marc Swartz, and the United States Geological Survey (USGS.
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):
- 2017-01-01 00:00:00 - Hydro Flattened Raster DEMs were generated using the Class 2 (ground) lidar points in conjunction with the hydro breaklines to create a 3.125 foot hydro-flattened Raster DEM. Using automated batch routines in ESP Utilities, an TIF file was created for each tile of the project. DEM surface was reviewed using ESP Analyst to check for any surface anomalies or incorrect elevations found within the surface (Citation: Lidar Point cloud: NC 2016 Phase 4)
- 2022-01-25 00:00:00 - Data were downloaded from the USGS, unzipped, and converted to cloud optimized Geotiff format. They were ingested into the Digital Coast Data Access Viewer for custom download. (Citation: DEM zip files)
(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.
Data is available online for bulk or custom downloads
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.