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
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the United States Forest Service (USFS) in the Elk Creek watershed between July 13-15, 2005. The survey area is located inside the Siuslaw National Forest and encompasses all of Spout Creek (northern extent), Feagles Creek (southern extent), the confluence of these streams with Elk Creek (western extent), and up the headwaters of Elk Creek (eastern extent). The initial study area (~23,454 acres) was buffered by 200 meters, extending the contracted survey area to 26,385 acres.
Laser points were collected over the study area using an Optech ALTM 3100 LiDAR system set to acquire points at an average spacing of >8 points per square meter. The system also recorded individual return intensities (per laser return) that are used to create models that display surface reflectivity.
No metadata record for this data set was provided to the NOAA Office for Coastal Management (OCM). This record was created with information from the data report. A link to the data report is provided in the URL section of this metadata record.
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):
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the United States Forest Service (USFS) in the Elk Creek watershed between July 13-15, 2005. NOAA OCM received the data and ingested it into the Digital Coast Data Access Viewer for distribution.
- 2017-01-01 00:00:00 - Acquisition. The Optech 3100 system was set to a 71kHz laser repetition rate and flown at 1,000 meters above ground level (AGL), capturing a 20o scan width (10 o from NADIR). These settings yielded points with an average density of > 8.0 per square meter, with an average spot spacing of 32cm. The entire area was surveyed with opposing flight line overlap of 50% to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all were processed for the output datasets. The data stream from the IMU was stored independently during the flight, and was differentially corrected and integrated with LiDAR pulse data during post processing. Throughout the survey, a dual frequency DGPS base station recorded fast static (1 Hz) data. The station was located at the eastern edge of the study area, near Marys Peak, Oregon.
- Two differential GPS units were deployed and used to process kinematic solutions to the onboard GPS and inertial measurement unit (IMU) using PosPAC v4.2. Points were computed per flight line using the REALM Survey Suite v3.5.2. Microstation V8 and TerraScan were used to import the points into bins, remove pits and birds, and compute the bare earth model. TerraModeler was then used to create TINs and output ARCINFO ASCII lattice models, which were then imported into ArcMap to render one-meter mosaics of first returns, vegetation and ground models.
- 2019-11-27 00:00:00 - The NOAA Office for Coastal Management (OCM) received 230 lidar point cloud files in laz format from DOGAMI. The files contained lidar elevation and intensity measurements. The data were in UTM 10N coordinates and NAVD88 (Geoid03) elevations, with all units in meters. The data were classified as: 1-Unclassified, 2-Ground. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 03 model, to convert from UTM 10N NAD83 coordinates in meters, to geographic coordinates, to assign the geokeys, and to sort the data by gps time for better compression. (Citation: processed 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 and 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.