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
Digital Elevation Model from Light Detection and Ranging data (lidar) of the Colville National Forest Study Area. The requested lidar area of interest (AOI) totals approximately 400 square miles, or 256,155 acres. This area was buffered to ensure data coverage, resulting in a total area flown (TAF) of 282,901 acres.
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):
- 2012-10-09 00:00:00 - Airborne acquisition was conducted between 10:00am and 2:00pm each day. The LiDAR survey utilized a Leica ALS50 sensor mounted in a Cessna Caravan. The system was set to acquire greater than 114,600 laser pulses per second and flown at 2000 meters above ground level (AGL), capturing a scan angle of Â±14 degrees from nadir. These settings are developed to yield points with an average native pulse density of 2 points per square meter over terrestrial surfaces. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude is described as pitch, roll, and yaw (heading) and was measured 200 times per second (200 Hz) from an onboard inertial measurement unit (IMU). The study area was surveyed with opposing flight line side-lap of at least 60% (greater than 100% overlap) to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all discernable laser returns were processed for the output dataset.
- 2012-11-20 00:00:00 - Resolve GPS kinematic corrections for aircraft position data using kinematic aircraft GPS (Collected at 2 Hz) and static ground GPS (1 Hz) data collected over geodetic controls using POSGNSS v. 5.3, Trimble Business Center v. 2.81, PosPacMMS v 5.4 Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor heading, position, and attitude are calculated throughout the survey using POSGNSS v. 5.3, PosPacMMS v5.4 Calculate laser point position by associating SBET information to each laser point return time, with offsets relative to scan angle, intensity, etc. included. This process creates the raw laser point cloud data for the entire survey in *.las (ASPRS v1.2) format, in which each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z information. These data are converted to orthometric elevation (NAVD88) by applying a Geoid 12 correction using OPTECH LiDAR Mapping Suite (LMS) v. 2.1 Import raw laser points into subset bins (less than 500 MB, to accommodate file size constraints in processing software). Filter for noise and perform manual relative accuracy calibration. Ground points are then classified for individual flight lines to be used for relative accuracy testing and calibration using TerraScan v.12, Custom Watershed Sciences software Test relative accuracy using ground classified points per each flight line. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations are performed on ground classified points from paired flight lines. Every flight line is used for relative accuracy calibration using TerraMatch v.12, TerraScan v.12, Custom Watershed Sciences software. Assess Fundamental vertical accuracy via direct comparisons of ground classified points to ground RTK survey data with TerraScan v.12
- 2012-01-01 00:00:00 - The TerraScan software suite was used to generate digital elevation models from the point clouds. The processing sequence began with removal of all points not near the earth based on geometricconstraints used to evaluate multi-return points. The resulting bare earth (ground) model was visually inspected and additional ground point modeling was performed in site-specific areas (over a 50-meter radius) to improve ground detail. This was only done in areas with known ground modeling deficiencies, such as bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, ground point classification included known vegetation (i.e., understory, low/dense shrubs, etc.) and these points were manually reclassified as non-grounds.
- 2023-02-09 00:00:00 - Digital Elevation Models were received by NOAA OCM from USFS. Data were converted from ESRI grid format to Cloud Optimized Geotiff. (Citation: Digital elevation models)
(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.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.2. Data storage facility prior to being sent to an archive facility
- 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.
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.
Office for Coastal Management
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.