Data Management Plan
GUID: gov.noaa.nmfs.inport:69409 | 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 digital elevation model (DEM) was created from a classified lidar point cloud encompassing the Colville National Forest project area, approximately 742 square miles. Each LAS/LAZ file contains LiDAR point information, which has been calibrated, controlled, and classified.
Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off
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.
4. Resources
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):
Process Steps:
- 2015-07-25 00:00:00 - Aerial LiDAR Acquisition: Aerial LiDAR was acquired, in sixteen (16) missions, using an ALS070HP SN7225 at an altitude of 2926 MSL to support a 8ppm^2 LiDAR point cloud. Airborne GPS and IMU data was collected during the acquisition and supported by LEICA SR530 GPS stations on NGS monuments K24, G483, and Z264. Data acquisition was completed between 8th of July through 25th of July 2015. Ground Control Survey: A survey was performed to support the acquisition of LiDAR collection. Ground GPS collection consists of collection NVA and VVA points for LiDAR validation in addition to control point GPS collection for flight support. All field survey observations were conducted between July 5, 2015 through July 25, 2015 using Leica SR530 and Topcon HiperV Dual Frequency GPS equipment, both configured to log data at 1 Hz, and at 10 degrees mask.
- 2015-07-31 00:00:00 - LiDAR Pre-processing: Airborne GPS and IMU data were merged to develop a Smoothed Best Estimate Trajectory (SBET) of the LiDAR system trajectory for each lift. LiDAR ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed check points. Swath overage points were identified and tagged within each swath file
- 2015-08-11 00:00:00 - Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and CloudPro software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the surveyed test points.
- 2015-08-16 00:00:00 - LiDAR Post-Processing: The calibrated and controlled LiDAR swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced LiDAR analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified LiDAR swath files were delivered to the client.
- 2015-08-23 00:00:00 - LiDAR Classification: The calibrated LiDAR data was run through automated classification routines and then manually checked and edited. The data was classified into the following classes: Class Code:1 Class Item:Undetermined/Unclassified Class Code:2 Class Item:Bare EarthNoise
- 2015-08-25 00:00:00 - Bare-Earth DEM Creation: Bare-Earth Digital Elevation Models (DEMs) were derived using bare-earth (ground) LiDAR points. All DEMs were created with a grid spacing of 1 meter. The DEMs were cut to 7.5 quads index provided by client.
- 2023-02-15 00:00:00 - Digital elevation models were received from US Forest Service by NOAA Office for Coastal Management in ERDAS Imagine format. The files were converted to cloud optimized GeoTiffs for distribution in the Digital Coast Data Access Viewer. (Citation: Classified lidar 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.
Missing/invalid information:
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
None
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.
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/USFS_Colville_NF_2015_9771/index.html
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
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.