Data Management Plan
GUID: gov.noaa.nmfs.inport:69598 | 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
Digital Elevation Model generated from aerial lidar collected over the Sycan Marsh in Lake and Klamath Counties, OR in 2020. The project area covers approximately 182 square miles. The project was flown with an Optech Galaxy PRIME lidar sensor at an approximate altitude of 5,249 feet above ground level (AGL). Lidar acquisition was planned with 60% side overlap and an aggregate point density of 8 points per square meter throughout the project area. The settings used for collection consisted of a pulse rate frequency (PRF) of 400 kHz, a scan frequency of 67.5 Hz, and a scan angle of +/- 20 degrees from the nadir position (full scan angle 40 degrees).
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):
Lineage Statement:
Data were collected and processed by Aero-Graphics, Inc, for the U.S. Forest Service. The U.S. Forest Service transferred the data to NOAA for distribution on the Digital Coast.
Process Steps:
- 2020-07-10 00:00:00 - LiDAR and imagery acquisition for the Sycan USFS R6 project was performed with an Optech Galaxy PRIME LiDAR sensor. The LiDAR sensor was placed in a customized mount to minimize error and increase accuracy. Aero-Graphics flew at an approximate altitude of 5,249 ft above ground level (AGL) and made appropriate adjustments to compensate for topographic relief over the projectâs over 71 flightlines. LiDAR acquisition was planned with 60% side overlap and an aggregate point density of 8 points per square meter throughout the project area. The settings used for collection consisted of a pulse rate frequency (PRF) of 400 kHz, a scan frequency of 67.5 Hz, and a scan angle of +/- 20 degrees from the nadir position (full scan angle 40 degrees).
- The absolute sensor calibration was adjusted for the difference in roll, pitch, heading, and scale between the raw laser point cloud from the sensor and surveyed control points on the ground. Differentially corrected the 1/5-second airborne GPS positions with ground base station; combined and refined the GPS positions with 1/200-second IMU (roll-pitch-yaw) data through development of a smoothed best estimate of trajectory (SBET). SBET was combined with raw LiDAR range data and solved for real-world position for each laser point. Point cloud data was produced by flight strip in ASPRS v1.4 .LAS format and output in the local coordinate system. Relative calibration was performed by correcting for roll, pitch, heading, and scale discrepancies between adjacent flightlines and the results were tested for accuracy. Data was cut into project-specified tiles and grossly long and short returns were filtered out. Classification algorithms were run on points in each tile, separating them into bare earth and unclassified points. Manually corrected areas that were not completely classified by the automated algorithms.
- 2023-03-13 00:00:00 - Data were received by NOAA Office for Coastal Management from the U.S. Forest Service in USFS region 6 Albers coordinates. Data were ingested into the Data Access Viewer system after reformatting to cloud optimized geotiffs. (Citation: DEM Tiffs)
(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.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 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.
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_SycanMarsh_2020_9806/index.html
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.
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.