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 was provided with the data. This record is populated with information from the Quantum Spatial, Inc. technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal. The technical report is available for download from the link provided in the URL section of this metadata record.
In September 2018, Quantum Spatial (QSI) was contracted by the Washington Department of Natural Resources (WADNR) to collect Light Detection and Ranging (LiDAR) data in the fall of 2018 for the Chelan site in central Washington. Data were collected to aid WADNR in assessing the topographic and geophysical properties of the study area to support natural resources planning and management for Chelan County, Washington. A total of 335,876 acres of 8 pulses per square meter LIDAR were acquired between 10/18/2018 and 10/27/2018. .
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 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 NOAA Office for Coastal Management (OCM) downloaded the GeoTiff files from the Washington Lidar Portal.
- Airborne Survey The LiDAR survey was accomplished using a Riegl VQ-1560i sensor system mounted in a Cessna Caravan. Settings were used to yield an average pulse density of 8 pulses/m2 over the Chelan project area. The Riegl laser system can record unlimited range measurements (returns) per pulse, though it is not uncommon for some types of surfaces (e.g., dense vegetation or water) to return fewer pulses to the LiDAR sensor than the laser originally emitted. The discrepancy between first return and overall delivered density will vary depending on terrain, land cover, and the prevalence of water bodies. All discernible laser returns were processed for the output dataset. All areas were surveyed with an opposing flight line side-lap of â¥50% (â¥100% overlap) in order to reduce laser shadowing and increase surface laser painting. To accurately solve for laser point position (geographic coordinates x, y and z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Position of the aircraft was measured twice per second (2 Hz) by an onboard differential GPS unit, and aircraft attitude was 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 and sensor position and attitude data are indexed by GPS time.
- Once the LiDAR data arrived in the laboratory, QSI employed a suite of automated and manual techniques for processing tasks. Processing tasks included: GPS, kinematic corrections, calculation of laser point position, relative accuracy testing, classification of ground and non-ground points, and assessments of statistical absolute accuracy. The general workflow for calibration of the LiDAR data was as follows: Resolve GNSS kinematic corrections for aircraft position data using kinematic aircraft GNSS (collected at 2Hz) and IMU (collected at 200Hz) data with Trimble CenterPoint PP-RTX methodologies. Used POSGNSS, PosPac MMS Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor heading, position, and attitude are calculated throughout the survey. Used POSGNSS, PosPac MMS Calculate laser point position by associating SBET position to each laser point return time, with offsets relative to scan angle, intensity, etc. This process creates the raw laser point cloud data for the entire survey in *.las (ASPRS v 1.2) format, in which each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z information. These data are converted to orthometric elevation (NAVD88 & NGVD29) by applying a Geoid correction. Used RiProcess and RiWorld Test relative accuracy using ground classified points per each flight line. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale), and GNSS/IMU drift. Calibrations are performed on ground classified points from paired flight lines. Every flight line is used for relative accuracy calibration. Used TerraMatch, TerraScan, QSI Proprietary Software Assess NVA via direct comparisons of ground classified points to ground RTK survey data. Point classifications are assigned for features of interest via a combination of QSI custom algorithms and manual inspection. Used TerraScan, TerraMatch, Trimble Business Center
- 2022-05-20 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 33 raster DEM files in GeoTiff format from the Washington Lidar Portal. The data were in Washington State Plane South NAD83(HARN), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster files were at a 3 feet grid spacing. No metadata record was provided with the data. This record is populated with information from the Quantum Geospatial, Inc. technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal. That report is linked within this metadata record, please see it for additional information. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 2927 and Vertical EPSG: 6360) to the GeoTiff formatted files. 2. Copied the files to https.
(describe or provide URL of description):
QSI has high standards and adheres to best practices in all efforts. In the laboratory, quality checks are built in throughout processing steps, and automated methodology allows for rapid data processing. QSI's innovation and adaptive culture rises to technical challenges and the needs of clients like Washington DNR. Reporting and communication to our clients are prioritized through regular updates and meetings.
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
- 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.