Data Management Plan
GUID: gov.noaa.nmfs.inport:57767 | 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
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 USDA Forest Service on September 19-23, 2007. The Areas of Interest (AOIs) collectively cover 36,837 acres (6 sites) within the Biscuit Fire region of Southwest Oregon. The overriding objective of the LiDAR acquisition was to provide accurate vegetation and bare earth terrain models to be used in the evaluation of landscape patterns on forestland affected by the fire of July 2002.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, 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.
Biscuit Fire project area.
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., collected Light Detection and Ranging (LIDAR) data in the Biscuit Fire project area for the USDA Forest Service. NOAA OCM received the data from DOGAMI and ingested it into the Digital Coast Data Access Viewer for distribution.
- 2007-09-23 00:00:00 - Acquisition. The full survey was conducted on September 19-23, 2007 (Julian Days 262-266). The LiDAR survey uses a Leica ALS50 Phase II laser mounted in a Cessna Caravan 208B. The sensor scan angle was ±14o from nadir1 with a pulse rate designed to yield an average native density (number of pulses emitted by the laser system) of ≥ 4 points per square meter over terrestrial surfaces. The Leica ALS50 Phase II system allows up to four range measurements (returns) per pulse, and all discernable laser returns are processed for the output dataset. It is not uncommon for some types of surfaces (e.g. dense vegetation or water) to return fewer pulses than the laser originally emitted. These discrepancies between ‘native’ and ‘delivered’ density will vary depending on terrain, land cover and the prevalence of water bodies. To accurately solve for laser point position (geographic coordinates x, y, z), the positional coordinates of the airborne sensor and the attitude of the aircraft are recorded continuously throughout the LiDAR data collection mission. Aircraft position is measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude is measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time.
- Ground Survey Simultaneous with the airborne data collection mission, we conduct a static (1 Hz recording frequency) survey of the horizontal and vertical positions of one or more survey control base stations established over monuments with known coordinates. Indexed by time, these GPS data are used to correct the continuous onboard measurements of aircraft position recorded throughout the mission. Multiple sessions are processed over the same monument to confirm antenna height measurements and reported position accuracy. After the airborne survey, these static GPS data are processed using triangulation with Continuously Operating Reference Stations (CORS) stations, and checked against the Online Positioning User Service (OPUS2) to quantify daily variance. Controls are located within 13 nautical miles of the mission area. Ground truth points are collected using a GPS based real-time kinematic (RTK) survey. For an RTK survey, the ground crew uses a roving unit to receive radio-relayed corrected positional coordinates for all ground points from a GPS base unit set up over a survey control monument. The roving unit records precise location measurements with an error (σ) of ≤ 1.5 cm (0.6 in). 673 RTK ground points were collected in the Biscuit Fire Study Area.
- Laser Point Processing Laser point coordinates are computed using the IPAS and ALS Post Processor software suites based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) are assigned x, y, z coordinates along with unique intensity values (0-255). The data are output into large LAS v. 1.1 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z (easting, northing, and elevation) information. These initial laser point files are too large for subsequent processing. To facilitate laser point processing, bins (polygons) are created to divide the dataset into manageable sizes (< 500 MB). Flightlines and LiDAR data are then reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. Laser point data are imported into processing bins in TerraScan, and manually calibrated to assess the system offsets for pitch, roll, heading and scale (mirror flex). Using a geometric relationship developed by Watershed Sciences, each of these offsets is resolved and corrected if necessary. LiDAR points are then filtered for noise, artificial low points (‘pits’) or non-terrestrial high points (e.g., birds, clouds, vapor, haze) by screening for absolute elevation limits, isolated points and height above ground. Each bin is then inspected for remaining spurious points which are then manually removed. In a bin containing approximately 7.5-9.0 million points, an average of 50-100 points are typically found to be artificially low or high. Where there is dense vegetation and/or at breaks in terrain, steep slopes and at bin boundaries, the delivered density can be significantly less than the native density. In areas where it is determined that the ground surface model has failed, supervised classifications are performed by ‘reseeding’ the ground surface model with ground points. 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, heading offsets and scale). Automated sensor attitude and scale corrections yield 3-5 cm improvements in the relative accuracy. Once system misalignments are corrected, vertical GPS drift is then resolved and removed per flight line, yielding a slight improvement (<1 cm) in relative accuracy. The TerraScan software suite is designed specifically for classifying near-ground points (Soininen, 2004). The processing sequence begins by ‘removing’ all points that are not ‘near’ the earth based on geometric constraints used to evaluate multi-return points. The resulting bare earth (ground) model is visually inspected and additional ground point modeling is performed in site-specific areas to improve ground detail. This manual editing of ground occurs in areas with known ground modeling deficiencies, such as bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, automated ground point classification includes known vegetation (i.e., understory, low/dense shrubs, etc.). These points are manually reclassified as non-ground. Where it is determined that the ground model has failed (usually under dense vegetation and/or at breaks in terrain, steep slopes and at bin boundaries), supervised classifications are performed by ‘reseeding’ the ground model. Ground surface rasters are developed from triangulated irregular networks (TINs) of ground points.
- 2019-09-25 00:00:00 - The NOAA Office for Coastal Management (OCM) received 23 bare earth DEM files in Arc Grid format from DOGAMI. The data were in UTM Zone 10N, NAD83, meters, coordinates and NAVD88 (Geoid03) elevations in meters. The EPSG codes (Vertical - 5703, Horizontal - 26910) were assigned. For ingest into the Digital Coast Data Access Viewer, and to adhere to the Open Data Policy, data were converted to GeoTiff format. (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.