Data Management Plan
GUID: gov.noaa.nmfs.inport:49473 | 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
WSI collected Light Detection and Ranging (LiDAR) data for the Oregon LiDAR Consortium (OLC) Wasco County, WA, study area. The Oregon LiDAR Consortium's Wasco County 2014-2015 project area of interest (AOI) encompasses 1,020,680 acres. The collection of high resolution geographic data is part of an ongoing pursuit to amass a library of information accessible to government agencies as well as the general public. Settings for LiDAR data capture produced an average resolution of at least eight pulses per square meter. Collections for the six deliveries were done from July 15, 2014 - August 5, 2015.
Final products created include RGB extracted (from NAIP imagery) LiDAR point cloud data, three-foot digital elevation models of highest hit and bare earth ground models, one-meter density rasters, 1.5-foot intensity rasters, study area vector shapes, and corresponding statistical data. All final deliverables were projected to Washington State Plane South, using the NAD83(2011) horizontal datum and the NAVD88 (Geoid 12A) vertical datum, with units in US Survey Feet. NOAA OCM changed the vertical units to meters for ingest into the Digital Coast. This metadata was created for the bare earth digital elevation models.
Original contact information:
Contact Name: Jacob Edwards
Contact Org: DOGAMI
Phone: 971-673-1557
Email: jacob.edwards@oregon.gov
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-01-01 00:00:00 - The LiDAR survey occurred between July 15, 2014 and August 5, 2015 utilizing a Leica ALS70 sensor mounted in a Cessna Grand Caravan. The system was programmed to emit single pulses at a rate of 198 kilohertz and flown around 1,400 meters above ground level (AGL), capturing a scan angle of +/-15 degrees from nadir (field of view equal to 30 degrees). These settings were developed to yield points with an average native density of greater than eight pulses per square meter over terrestrial surfaces. The study area was surveyed with opposing flight line side-lap of greater than 60 percent with at least 100 percent overlap to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all discernible laser returns were processed for the output dataset. To solve for laser point position, an accurate description of aircraft position and attitude is vital. Aircraft position is described as x, y, and z and was measured twice per second (two hertz) by an onboard differential GPS unit. Aircraft attitude is described as pitch, roll, and yaw (heading) and was measured 200 times per second (200 hertz) from an onboard inertial measurement unit (IMU).
- 2017-07-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 using gdal_translate from GDAL version 2.1.1. Vertical units were changed to meters in that process. (Citation: DEM files)
- Files were converted to cloud optimized geotiff format to support streaming and the vertical units were reverted to feet to match the horizontal units.
(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.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.
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/OLC_wasco_6342/index.html
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.