Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:67360 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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.
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the Klamath Tribes over a seven day span in November, 2004. Conditions included leaf off and a normal fall low flow condition. The survey area encompassed the Sprague River, the lower Sycan River, and the lower reaches of the North and South Forks of the Sprague River. The study area was buffered by 500 meters to ensure complete coverage of important areas.
A total of 1,469,351,015 laser points were collected over the study area using an Optech ALTM 3100 LiDAR system set to acquire points at average spacing of less than 0.68 meters (greater than 2 points per square meter). The system also recorded individual return intensities (per laser return) that are used to create combined elevation models that display both elevation and surface reflectivity. These data were used to create this Digital Elevation Model (DEM) at 1m grid spacing, in UTM Zone 10, NAVD88 using Geoid03.
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:
Watershed Sciences, LLC collected Light Detection and Ranging (LIDAR) data in the Union Baker project area for DOGAMI. NOAA OCM received the data and ingested it into the Digital Coast Data Access Viewer for distribution.
Process Steps:
- 2012-01-01 00:00:00 - Lidar Collection: The LiDAR system was mounted in the belly of a Cessna Caravan 208. Quality control (QC) flights were performed based on manufacturer's specifications prior to the survey. The QC flight was conducted at the Ashland Airport using known surveyed control points. The positional accuracy of the LiDAR (x, y, z) returns were checked against these known locations to verify the calibration and to report base accuracy. The Optech 3100 system was set to a 50kHz laser repetition rate and flown at 1,000 meters AGL, capturing a 36 o scan width (18 o from NADIR). These settings yielded points with an average spacing of less than 0.68 meters (greater than 2 points per square meter). The entire area was surveyed with opposing flight line overlap of 30% to reduce laser shadowing and increase surface laser painting. While the system allows up to four range measurements per pulse, only the first and last returns were processed in the output. 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, two dual frequency DGPS Trimble 5700 base stations recorded fast static (1 Hz) data. Two stations were located at National Geodetic Survey (NGS) monuments in Chiloquin and Bly to minimize kinematic solution baselines and increase GPS data accuracy. Data Processing: Laser point return coordinates were computed using the REALM software suite based on independent data from the LiDAR system (pulse time, scan angle), IMU (aircraft attitude), and aircraft position (differentially corrected and optimized using the multiple DGPS base stations data). The inertial measurement data were used to calculate the kinematic corrections for the aircraft trajectories using PosPAC v4.1. Flight lines and LiDAR data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. TerraScan Processing: To facilitate laser point processing, the first step is to create bins (polygons) that divide the data set into manageable sizes. The entire buffered study area was divided into 465 individual bins with a maximum size of 2.25 km2, capturing all 111 flight lines (see Project Report). Laser point returns (first and last) are assigned an associated (x, y, z) coordinate, along with unique intensity values. The raw LiDAR points were filtered for noise, pits and birds by screening for absolute elevation limits, isolated points and height above ground. These data have passed initial screening and are deemed accurate; however, ground modeling processing has not been completed on these laser points. The TerraScan software suite is designed specifically for developing a standard bare earth model to remove buildings, vegetation, and other features. The initial bare earth model retains bridges and overpasses, and these artifacts are removed manually. The high point density and multiple returns result in uncomplicated identification of vegetated and obscured areas using first and last returns. The processing sequence begins by removing all points that are not near the earth based on evaluation of the multi-return layers. The resulting bare earth (ground) model is visually inspected and additional ground modeling is performed in site specific areas (over a 50 meter radius) to improve ground detail. This was only done in areas with known ground modeling deficiencies, such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation.
- 2005-01-01 00:00:00 - Description of Processing Steps: Units: Meters Projection: UTM Zone 10, NAD83 NAVD88, Geoid03 1. Import point data into 465 bins 2. Perform relative accuracy testing. 3. Removing False LiDAR Points: False high and low points were removed by establishing thresholds for point removal that are above and below the known terrain elevations. 4. Calculate bare ground model from last return points, with the maximum building size of 100 m2 and maximum terrain angle of 88o . The challenge is to remove buildings and vegetation, but leave rock outcrops and cliffs. Important: Water points are left in the bare earth model because it is unclear which points are water and which are mud flat, river bed, rocks, etc. 5. Manual removal of bridges and highway spans. 6. Generate TINs within all bins (including points 100 m outside) and export ASCII lattice files for first return and ground points. 7. No weeding or superfluous point removal was performed. The intent of a LiDAR survey is to accurately place points on targets, not remove points. If laser noise is low and internally consistent, aside from pits and birds, it assumed that the remaining laser returns are from targets within the survey area. 8. Create ESRI 1 meter GRIDs 9. Create ý meter QTViewer GRIDs and point data.) before triangulation.
- 2022-06-08 00:00:00 - The NOAA Office for Coastal Management (OCM) received 19 bare earth DEM files in ArcGRID format from DOGAMI. The data were in UTM 10N (NAD 83 HARN), meters coordinates and NAVD88 (Geoid03) elevations in meters. The grid spacing was 1m. OCM performed the following processing for Digital Coast storage and provisioning purposes: 1. Data were converted to GeoTiff format using GDAL 2.4.0 to comply with the open data policy (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.
Missing/invalid information:
- 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.
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/OR_SpragueRiver_DEM_2004_9513/index.html
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.