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 of the Ashland study area in the Rogue River-Siskiyou National Forest on July 1st-4th, 2006 (Julian Days 182-185). The survey area encompassed the city of Ashland as well as the Ashland Creek Watershed, resulting in a delivered LiDAR area of 46,253 acres.
Laser points were collected over the study area using an Optech ALTM 3100 LiDAR system. Full overlap (i.e. 50% sidelap) ensured complete coverage and
minimized laser shadows created by buildings and tree canopies. A real-time kinematic (RTK) survey was conducted throughout the study area for quality assurance purposes.
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 of the Ashland study area for the United States Forest Service (USFS) in the Rogue River-Siskiyou National Forest from July 1st to July 4th, 2006. NOAA OCM received the data and ingested it into the Digital Coast Data Access Viewer for distribution.
- 2006-07-04 00:00:00 - Acquisition. The LiDAR survey utilized an Opetch ALTM 3100 mounted in the belly of a Cessna Grand Caravan 208B. The survey was conducted on July 1st-4th, 2006 (Julian Days 182-185). Quality control (QC) pre-mission flights were performed based on manufacturerâs specifications prior to the survey. The QC flight was conducted at the Ashland, Oregon Airport using known surveyed control points. The positional accuracy of the LiDAR (x, y, z) returns are checked against these known locations to verify the calibration and to report base accuracy. Operational settings included: Laser pulse repetition rate: 70 kHz Operating altitude: 1100 m above ground level Flight speed: 105 knots Scan Angle: +/- 14 degrees from Nadir Scan Pattern: Sawtooth Laser Footprint diameter on ground: 30 cm Number of returns per laser pulse: up to 4 Multi-swath pulse density: at least 7.5 pulses per square meter
- Applications and work flow overview: 1. POSGPS: Monument static GPS data are processed with aircraft GPS data to resolve kinematic corrections. 2. POSProc: Aircraft attitude data are incorporated with post processed aircraft kinematic GPS data. 3. REALM: Laser point data are calculated for the entire survey in *.las format. 4. TerraScan: Data are imported, manually calibrated and filtered for pits/birds. 5. TerraMatch: Internal consistencies derived from GPS and IMU drift are measured and corrected. 6. TerraScan: Develop ground models, statistical accuracy assessments, Geoid03 application, projection changes and transformations. Aircraft Kinematic GPS and IMU Data LiDAR survey datasets are referenced to 1Hz static ground GPS that are set up prior to the LiDAR aircraft survey flight. While surveying, the aircraft collects 2Hz kinematic GPS data. The onboard inertial measurement unit (IMU) collects 200 Hz aircraft attitude data. POSGPS v. 4.2 is used to process the kinematic corrects for the aircraft. The static and kinematic GPS data are then post-processed after the survey to obtain accurate GPS solution and aircraft positions during times of the survey. POSProc v. 4.2 is used to develop a trajectory file that includes corrected aircraft position and attitude information. The trajectory data for the entire flight survey session is incorporated into a final trajectory file that contains accurate and continuous aircraft positions and attitudes.
- Laser Point Processing Laser point coordinates were computed using the REALM v. 3.5.2 software suite based on independent data from the LiDAR system (pulse time, scan angle), aircraft attitude, and aircraft position. Laser point returns (first through fourth) are assigned an associated (x, y, z) coordinate, along with unique intensity values (1-255). The data are output into one very large LAS v. 1.0 file format; each point has a corresponding scan angle, return number (echo), intensity, and x,y,z (easting, northing, and elevation) information. The initial laser point file is too large to process. To facilitate laser point processing, bins (polygons) were created to divide the dataset into manageable sizes (less than 500 MB and approximately 1 km2 each). Flight lines and LiDAR data were then reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. These processing bins were ultimately aggregated into areas of 0.9375-minute quadrangles (1/64th of a standard USGS 7.5-minute quadrangle). Once the laser point data are imported into bins in TerraScan, a manual calibration test is performed to assess the system offsets for pitch, roll, yaw and scale. Using a geometric relationship developed by Watershed Sciences, each of these offsets is resolved and corrected if necessary. The LiDAR points are then filtered for noise, pits and birds by screening for absolute elevation limits, isolated points and height above ground. Each bin is then inspected for pits and birds manually, and spurious points are removed. For a bin measuring 1 km2, an average of 20-40 points are found to be artificially low or high. The internal calibration is refined using TerraMatch. Points from overlapping lines are tested for internal consistency and final adjustments are made for system misalignments (i.e. pitch, roll, yaw and scale offsets). Once these misalignments are corrected, GPS drift can then be resolved and removed. The resulting dataset is internally calibrated using both manual and automated routines. At this point in the workflow, remaining data have passed initial screening and are deemed accurate. The TerraScan software suite is designed specifically for classifying near-ground laser points (Soinenen, 2004). 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 is only done in areas with known ground modeling deficiencies, such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation.
- 2023-05-09 00:00:00 - The NOAA Office for Coastal Management (OCM) received lidar point cloud files in laz format from the U.S. Forest Service. 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 converted the data from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 03 model and converted from UTM 10N NAD83 coordinates in meters, to geographic coordinates. Geokeys were also assigned. These conversions were done to ingest the data into the Digital Coast Data Access Viewer. (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.