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 United States Forest Service, Region 6, (USFS) required leaf-on airborne LiDAR surveys to be collected over approximately 4,141 square miles of national forestry in Oregon and Washington State. The following areas were requested to be covered: Fremont-Winema National Forest (FRE-WINNF) in Lakeview, Oregon; Malheur National Forest (MALNF) in John Day, Oregon; Willamette National Forest (WILNF) in Bend, Oregon; Okanogan-Wenatchee National Forest (OKA-WENNF) in Wenatchee, Washington; and Rogue River-Siskiyou National Forest (RR-SNF) in Medford, Oregon. Table 1 below details the Areas of Interest (AOIs) requested for 2020 reflight.
Aerial LiDAR data for this task order was planned, acquired, processed and produced at an aggregate nominal pulse spacing (ANPS) of 0.35 meters and in compliance with USGS National Geospatial Program LiDAR Base Specification version 1.3.
Area No. Forest AOI Square Miles
AOI-1 WILBRE Breitenbush 16
AOI-2 MBSMFS Middle Fork 124
AOI-3 MTHNCZ North Clackamas/Zig Zag 223
AOI-4 WILNFM NFMF 22
AOI-5 MTHSCL South Clackamas 430
AOI-6 WILCMP Willamette 942
This dataset is a subset of the total flown, covering only the Middle Fork and Clackamas areas (North and South).
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.
Middle Fork SiteW: -122.09427, E: -121.98112, N: 45.648061, S: 45.608655
North ClackamasW: -122.68988, E: -121.7768388, N: 44.8495, S: 43.556866
Detroit Middle ForkW: -122.25318499, E: -121.7283273, N: 45.17222218, S: 44.76329079
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):
- 2020-09-20 00:00:00 - Aircraft and Sensor Information and Flight Plan Execution Atlantic operated a PACDV (N750DV) outfitted with an Optech Galaxy Prime LiDAR system during the collection of the project area. Atlantic acquired 1588 passes of the AOI as a series of perpendicular and/or adjacent flight-lines executed in 44 flight missions conducted between June 29, 2018 and January 24, 2019. Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view.
- 2018-09-19 00:00:00 - Ground Control Survey A total of 198 ground survey points were collected in support of this project. Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas. A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided. Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a GCP. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The GCP value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded. The GCP value is a requirement that must be met, regardless of any allowed 'busts' in the VVA(s) for individual land cover types within the project. Checkpoints for the assessment are required to be well-distributed throughout the land cover type, for the entire project area
- 2021-04-12 00:00:00 - LiDAR Point Cloud Generation Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds.
- 2021-04-12 00:00:00 - LiDAR Calibration Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. 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 missions, was reduced to no more than 2cm. A final analysis of the calibrated lidar is preformed using a TerraMatch tie line report for an overall statistical model of the project area. Upon completion of the data calibration, a complete set of elevation difference intensity rasters (dZ Orthos) are produced. A user-defined color ramp is applied depicting the offsets between overlapping swaths based on project specifications. The dZ orthos provide an opportunity to review the data calibration in a qualitative manner. Atlantic assigns green to all offset values that fall below the required RMSDz requirement of the project. A yellow color is assigned for offsets that fall between the RMSDz value and 1.5x of that value. Finally, red values are assigned to all values that fall beyond 1.5x of the RMSDz requirements of the project
- 2021-04-12 00:00:00 - LiDAR Classification Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Classified point clouds were cut to match the tile index and its corresponding tile names and delivered in .laz format.
- 2021-04-12 00:00:00 - Digital Coast Processing Data were received from the USFS Region 6 in LAZ format with a projection of NAD83(2011) USFS Region 6 Albers meters and vertically in NAVD88 meters using Geoid12b. Data were in LAS 1.4 format (the data report has conflicting information regarding the LAS version). For ingestion in the Data Access Viewer, data were reverted to NAD83(2011) geographic coordinates and ellipsoid heights (EPSG:6319). The time of collection listed in process step 1 is noted to be incorrect, but was left as the original metadata record from Atlantic, Inc. Based upon the time stamps in the lidar records, the collection appears to be from July 29, 2020 to August 20, 2020. This suggests that some of the process steps were copied from a different metadata records and may not reliably describe the collection and processing of this dataset. Due to the possibility that parts of the metadata were copied from earlier projects, there may be some question regarding the correct GEOID model. The metadata received states Geoid12b. At the time of the project, the current NGS Geoid was Geoid18. (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.
- 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.
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
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.