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
Terrapoint collected LiDAR for over 177 square kilometers of the Bombay Hook National Wildlife Refuge in Kent County, Delaware.
The nominal pulse spacing for this project was no greater than 0.75 meters. This project was collected with a sensor which collects
waveform data and provides an intensity value for each discrete pulse extracted from the waveform. GPS Week Time, Intensity, Flightline
and echo number attributes were provided for each LiDAR point. Dewberry used proprietary procedures to classify the LAS according to
project specifications: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 12-Overlap. Once the data was received by NOAA OCM, all of the
class 7 (noise) points were removed from the data set. Dewberry produced classified LAS and DEMs for the 99 tiles (1700 m x 1700 m) that
cover the project area.
Original contact information:
Contact Org: NOAA Office for Coastal Management
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):
- 2011-04-01 00:00:00 - Terrapoint used their Optech ALTM 3100EA LiDAR sensor to collect the data for the Bombay Hook project. Three flight missions were required to obtain data over the entire project area. Flightlines were flown in a North-South orientation to optimize flying time in regards to the project layout. A combination of Sokkia GSR 2600 and NovAtel DL-4+ dual-frequency GPS receivers were used to support the airborne operations of this survey and to establish the GPS control network. Terrapoint used three existing published survey monuments and one newly established control station to control all flight missions and kinematic and static ground surveys. Airborne GPS kinematic data was processed on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13 degrees above the horizon) and with a PDOP of better than 4. Distances from base station to aircraft were kept to a maximum of 40 km. For all flights, the GPS data can be classified as excellent, with GPS residuals of 3 cm average or better but no larger than 10 cm being recorded. The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Optech's Dashmap, initially with default values from Optech or the last mission calibrated for system. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS kinematic validation points for absolute vertical accuracy purposes. On a project level, a supplementary coverage check is carried out, to ensure no data voids unreported by Field Operations are present.
- 2011-05-01 00:00:00 - Dewberry utilizes a variety of software suites for inventory management, classification, and data processing. All LiDAR related processes begin by importing the data into the GeoCue task management software. The swath data is tiled into the client provided tiling schema (1700 m x 1700 m). The tiled data is then opened in Terrascan where Dewberry uses proprietary ground classification routines to remove any non-ground points and generate an accurate ground surface. The first part of the ground routine is to classify all points with a scan angle greater than 20 degrees to class 12, overlap. These points have the highest potential to cause issues in the ground surface. Therefore, they are classified to class 12 immediately where they will not be available for the remaining ground routine. The ground routine consists of three main parameters (building size, iteration angle, and iteration distance); by adjusting these parameters and running several iterations of this routine an initial ground surface is developed. The building size parameter sets a roaming window size. Each tile is loaded with neighboring points from adjacent tiles and the routine classifies the data section by section based on this roaming window size. The second most important parameter is the maximum terrain angle, which sets the highest allowed terrain angle within the model. The ground routine also identifies extremely low or high points that should be excluded from the ground surface and classifies them as class 7, noise. Once the ground routine has been completed a manual quality control routine is done using hillshades, cross-sections, and profiles within the Terrasolid software suite. After this QC step, a peer review and supervisor manual inspection is completed on a percentage of the classified tiles based on the project size and variability of the terrain. After the ground classification corrections were completed, the dataset was processed through a water classification routine that utilizes breaklines compiled by Dewberry to automatically classify hydrographic features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. The fully classified dataset is then processed through Dewberry's comprehensive quality control program. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7= Noise (These points were removed from the data set by NOAA OCM during processing for data storage and Digital Coast provisioning). Class 9 = Water Class 12= Overlap Points with a scan angle greater than 20 degrees The LAS header information was verified to contain the following: Class (Integer) GPS Week Time (0.0001 seconds) Easting (0.01 foot) Northing (0.01 foot) Elevation (0.01 foot) Echo Number (Integer 1 to 4) Echo (Integer 1 to 4) Intensity (8 bit integer) Flight Line (Integer) Scan Angle (Integer degree)
- 2012-04-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained LiDAR elevation as well as intensity values. The data were in Delaware State Plane, NAD83 coordinates and NAVD88 heights. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from Delaware State Plane, NAD83 coordinates to geographic coordinates. 2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid09. 3. Data points that were classified as 7 (noise) were removed from the data set. 4. The data were sorted and converted to LAZ format.
(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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL:
This 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.