Data Management Plan
GUID: gov.noaa.nmfs.inport:67548 | 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 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 July 2018, Quantum Spatial (QSI) was contracted by the Washington State Department of Natural Resources (WADNR) to collect Light Detection and Ranging (LiDAR) data in the summer of 2018 for the Yakima Basin Wildfire Division site in Washington State. This project serves as an add-on to the previously delivered Yakima Basin D2 dataset, delivered on August 31, 2018, with seamlessly calibrated overlapping data existing between the two deliveries. The areas of interest include 319 square miles of WA DNR Wildfire lands and 20 square miles of lands owned and operated by the Yakama Nation. Data were collected to aid WADNR in assessing the topographic and geophysical properties of the study area to support emergency response and watershed management within the wildfire division of WADNR lands.
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.
- Planning: In preparation for data collection, QSI reviewed the project area and developed a specialized flight plan to ensure complete coverage of the contracted Yakima Basin Wildfire Division LiDAR study area at the target point density of greater than or equal to 8.0 points/m2 (0.74 points/ft2). Acquisition parameters including orientation relative to terrain, flight altitude, pulse rate, scan angle, and ground speed were adapted to optimize flight paths and flight times while meeting all contract specifications. A data gap approximately 3 acres in size exists within the buffered boundary but outside the contracted boundary at the location of 121 degrees 4 minutes, 27.104 seconds W, 47 degrees 23 minutes 27.322 seconds N. This data gap within the buffer resulted from a reduction in the dynamic field of view to ensure a seamless and accurate dataset inside the contracted project area. Factors such as satellite constellation availability and weather windows must be considered during the planning stage. Any weather hazards or conditions affecting the flights were continuously monitored due to their potential impact on the daily success of airborne and ground operations. In addition, logistical considerations including private property access and potential air space restrictions were reviewed.
- Ground Survey Points Ground control surveys, including base stations and ground survey points (GSPs) were conducted to support the airborne acquisition. Ground control data were used to geospatially correct the aircraft positional coordinate data and to perform quality assurance checks on final LiDAR data. Ground survey points were collected using real time kinematic (RTK), post-processed kinematic (PPK), and fast-static (FS) survey techniques. A Trimble R7 base unit or the Washington State Reference Network broadcasted a kinematic correction to a roving Trimble R8 GNSS receiver. All GSP measurements were made during periods with a Position Dilution of Precision (PDOP) of less than or equal to 3.0 with at least six satellites in view of the stationary and roving receivers. When collecting RTK and PPK data, the rover records data while stationary for five seconds, then calculates the pseudorange position using at least three one-second epochs. FS surveys record observations for up to fifteen minutes on each GSP in order to support longer baselines for post-processing. Relative errors for any GSP position must be less than 1.5 cm horizontal and 2.0 cm vertical in order to be accepted. GSPs were collected in areas where good satellite visibility was achieved on paved roads and other hard surfaces such as gravel or packed dirt roads. GSP measurements were not taken on highly reflective surfaces such as center line stripes or lane markings on roads due to the increased noise seen in the laser returns over these surfaces. GSPs were collected within as many flightlines as possible; however the distribution of GSPs depended on ground access constraints and monument locations and may not be equitably distributed throughout the study area. Base Stations Base stations were used for collection of ground survey points using real time kinematic (RTK), post processed kinematic (PPK), and fast static (FS) survey techniques. Base station locations were selected with consideration for satellite visibility, field crew safety, and optimal location for GSP coverage. QSI utilized four permanent base stations from the Washington State Reference Network (WSRN), and established two new temporary RTK monuments for the Yakima Basin Wildfire Division LiDAR project. New monumentation was set using 6 inch nails marked with a high visibility washer. QSI's professional land surveyor, Evon Silvia (WAPLS#53957) oversaw and certified the ground survey network. QSI collected multiple static Global Navigation Satellite System (GNSS) occupations (1 Hz recording frequency) for the base station locations. During post-processing, the static GNSS data were triangulated with nearby Continuously Operating Reference Stations (CORS) using the Online Positioning User Service (OPUS) for precise positioning to ensure alignment with the National Spatial Reference System (NSRS). Multiple independent sessions for each position were processed to confirm antenna height measurements and to refine position accuracy. Monuments were established according to the national standard for geodetic control networks, as specified in the Federal Geographic Data Committee (FGDC) Geospatial Positioning Accuracy Standards for geodetic networks. This standard provides guidelines for classification of monument quality at the 95% confidence interval as a basis for comparing the quality of one control network to another. For the Yakima Basin Wildfire Division LiDAR project, the monument coordinates contributed no more than 2.8 cm of positional error to the geolocation of the final ground survey points and LiDAR, with 95% confidence.
- Airborne Survey The LiDAR survey was accomplished using Leica ALS80 and Optech Galaxy Prime laser systems mounted in a Cessna Caravan. The settings were used to yield an average pulse density of greater than or equal to 8 pulses/m2 over the Yakima Basin Wildfire Division project area. The Optech laser system can record up to eight range measurements (returns) per pulse, whereas the Leica laser system can record unlimited range measurements per pulse. 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 greater than or equal to 50% (greater than or equal to 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.
- Upon completion of data acquisition, QSI processing staff initiated a suite of automated and manual techniques to process the data into the requested deliverables. Processing tasks included GPS control computations, smoothed best estimate trajectory (SBET) calculations, kinematic corrections, calculation of laser point position, sensor and data calibration for optimal relative and absolute accuracy, and LiDAR point classification. Processing methodologies were tailored for the landscape. Lidar Processing Steps Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. Software used - POSPac v.8.2, Waypoint Inertial Explorer v.8.7 Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.4) format. Convert data to orthometric elevations by applying a geoid correction. Software used - Optech LMS v.4.2, Waypoint Inertial Explorer v.8.7 Leica CloudPro v. 1.2.4 Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. Software used - TerraScan v.18 Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. Software used - TerraMatch v.18 Classify resulting data to ground and other client designated ASPRS classifications. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground control survey data. Software used - TerraScan v.18, TerraModeler v.18 Generate bare earth models as triangulated surfaces. Generate highest hit models as a surface expression of all classified points. Export all surface models as ESRI GRIDs at a 3.0 foot pixel resolution. Software used - Las Monkey 2.3.5 (QSI proprietary), LAS Product Creator v. 3.1 (QSI proprietary), ArcMap v. 10.3.1
- 2022-07-19 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 22 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. 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.