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
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.
Geographic Extent: OLC Grass Valley Project Area, covering approximately 228,146 acres.
Dataset Description: Quantum Spatial, Inc. (QSI) acquired and processed lidar data describing the Oregon Lidar Consortium's (OLC) Grass Valley Study Area. Lidar data acquisition occurred between April 22 and May 4, 2017. Settings for lidar data capture produced an average resolution of at least 8 points per square meter.
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link 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):
- The lidar survey utilized a Leica ALS 80 sensor mounted in a Cessna Grand Caravan. The system settings were developed to yield points with an average native density of greater than 8 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 data set.
- Ground control points and ground survey points were collected using real time kinematic (RTK), post-processed kinematic (PPK), and fast static (FS) survey techniques. For RTK surveys, a base receiver was positioned at a nearby monument to broadcast a kinematic correction to a roving receiver, for PPK and FS surveys, however, these corrections were post-processed. RTK and PPK surveys recorded observations for a minimum of 5 seconds, while FS surveys recorded observations for up to 15 minutes on each GCP/GSP in order to support longer baselines for post-processing. All GCP and GSP measurements were made during periods with a Position Dilution of Precision (PDOP) no greater than 3.0 and in view of at least 6 satellites for both receivers. Relative errors for the position were required to be less than 1.5 centimeters horizontal and 2.0 centimeters vertical in order to be accepted. In order to facilitate comparisons with high quality lidar data, GCP and GSP measurements were not taken on highly reflective surfaces such as center line stripes of lane markings on roads. GCPs and GSPs were taken no closer than one meter to any nearby terrain breaks such as road edges or drop offs. GCPs and GSPs were collected within as many flight lines as possible: however, the distribution depended on ground access constraints and may not be equitably distributed throughout the study area.
- 2019-10-17 00:00:00 - The NOAA Office for Coastal Management (OCM) received 854 lidar point cloud files in laz format from DOGAMI. The files contained lidar elevation and intensity measurements. The data were in Oregon Lambert (NAD83 2011), international feet coordinates and NAVD88 (Geoid12B) elevations in international feet. The data were classified as: 1-Unclassified, 2-Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2. 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 12B model, to convert from Oregon Lambert (NAD83 2011), international feet coordinates to geographic coordinates, to convert from vertical units feet to meters, to assign the geokeys, to sort the data by gps time, and zip the data to database and to http.
(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.