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
GeoTerra, Inc. was selected by Oregon Department of Forestry to provide Lidar remote sensing data including LAZ files of the classified Lidar points and surface models for approximately 591 square miles over five (5) sites in Northwest Oregon. Airborne Lidar mapping technology provides 3D information for the surface of the Earth which includes terrain surface models, vegetation characteristics and man-made features. Lidar technology is capable of penetrating gaps in forest canopies and to reach the ground below allowing for creation of accurate bare earth and vegetation surfaces.
Lidar point clouds were projected back to geographic coordinates for storage in the Digital Coast Data Access Viewer.
Original contact information:
Contact Name: Jacob Edwards
Contact Org: DOGAMI
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):
- 2015-01-01 00:00:00 - GeoTerra, Inc. acquired Lidar sensor data with Optech Orion H300 mounted in Cessna 180 on following dates: - Salmonberry site - April 19th and April 20th 2015 - Wilkerson/Wilark site - May 30th, June 5th and June 6th 2015 - McGregor site - June 6th, June 8th 2015 - Columbia site - June 8th, June 9th 2015 For the Abiqua site, GeoTerra Inc. used the Optech Galaxy Lidar system to acquire the areas. The Optech Galaxy emits higher pulse rate of 35 - 550 kHz and can record up to 8 range measurements per laser pulse emitted. A pulse rate of 450KHz was used and data was collected on March 30, 2016.
- 2016-01-01 00:00:00 - Processing. Relative and absolute adjustment of all strips was accomplished using Optech LMS software and TerraMatch. Optech LMS performs automated extraction of planar surfaces from the cloud of points according to specified parameters per project. Tie plane determination then establishes the correspondence between planes in overlapping flight lines. All plane centers of all lines that form a block are sorted into a grid. Plane surfaces from overlapping flight lines are used, co-located to within an acceptable tolerance, and are then tested for correspondence. A set of appropriate tie planes is selected for the self-calibration. Selection criteria are size and shape, number of laser points, slope, orientation with respect to flight direction, location within the flight line and fitting error. All these criteria have an effect as they determine the geometry of the adjustment. Self-Calibration parameters are then calculated and used to re-calculate the laser point coordinates (X,Y,Z). The planar surfaces are re-calculated as well for a final adjustment. Additionally each mission was further reviewed and adjusted in TerraMatch using tie lines approach. The software measures the difference between lines (observations) in overlapping strips. These observed differences are translated into correction values for the system orientation - easting, northing, elevation, heading, roll, pitch and mirror scale.
- 2016-01-01 00:00:00 - Point Classification: Once the point cloud adjustment was achieved with desired relative accuracy, all strips were exported from Optech LMS into LAS format. Data in LAS format was first automatically classified followed by strict QC procedures. Each site was evaluated for size and was cut into working tiles of a manageable size and manually checked and edited using TerraSolid and LP360. Following classes were delineated in the process of classification: - 01_Unclassified (temporary) - 02_Ground - 03_Low Vegetation - 04_Medium Vegetation - 05_High Vegetation - 06_Buildings and Associated Structures - 09_Water - points reflected off water bodies - 10_Unclassified (Permanent)
- 2016-01-01 00:00:00 - DEM creation: Three-foot floating point Ground and First Return ESRI raster grids were generated using the Lidar points as input to the LAS Dataset to Raster tool and converting an ESRI terrain dataset of the Lidar ground surface into File Geodatabase raster. Class 2 lidar points were used.
- 2017-09-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in the proprietary ESRI grid format. The files were converted to floating point GeoTIFF format in vertical meters using gdal_translate from GDAL version 2.1.1.
(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: https://coast.noaa.gov/dataviewer
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.