Data Management Plan
GUID: gov.noaa.nmfs.inport:64330 | 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
Product: QL1 LAS 1.4
Geographic Extent: This NIR Lidar dataset and derived products encompass an area covering approximately 473,860 acres of South East Alaska. The Quality Level 1 (QL1) project area encompased 130,339 acres of the total area.
Dataset Description :The Glacier Bay 3DEP Lidar project called for the planning, acquisition, and processing of Lidar data collected at an aggregate nominal pulse spacing (ANPS) of 0.31 meters for all QL1 areas. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on the NAD83(2011) horizontal datum and NAVD88 (GEOID12B) vertical datum. Data was projected in UTM Zone 8N. All units are in meters. RAW flight line swaths were processed to create 2,390 classified LAS 1.4 files delineated in 1,000 m x 1,000 m tiles. Please note that tiles GB_03743 and GB_05552 do not include valid point return data as they are entirely over areas of open water and thus have not been included in this submission. Each LAS file contains Lidar point information, which has been calibrated, controlled, and classified. Additional derived products include hydro-flattened DEMs, Highest Hit DSMs, Intensity Images, DZ Orthos, Flightline Shapes, Swath Coverage Shapes, Ground Survey Shapes and 3D breaklines of rivers and lakes within the study area.
Ground Conditions: Lidar was collected in summer 2019, while the presence of snow on the ground was at a minimum and rivers were at or below normal levels. In order to post process the Lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, DOWL on behalf of QSI established a total of 194 ground control points distributed throughout the Glacier Bay Delivery 1 project area. Lidar data was calibrated to these known ground locations. An additional 115 independent accuracy checkpoints, 33 in Bare Earth and Urban landcovers (NVA points) and 82 in Shrub, Tall Grass, and Forest categories (VVA points) were used to assess the vertical accuracy of the project data. These checkpoints were not used to calibrate or post process the data.
Note: currently only Delivery 1 of 2 has been released (Blocks 2 & 3, collected in 2019). When the second and final delivery is made available NOAA OCM will incorporate the data and update 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):
- 2020-05-04 00:00:00 - Lidar Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. 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. 4. 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 format. Convert data to orthometric elevations by applying a geoid correction. 5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. 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. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.
- 2020-05-04 00:00:00 - Lidar Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate NVA and VVA, and density information for the project using ground control quality check points. For Ql1 areas single swath nominal pulse spacing (NPS) was designed to be 0.50 at nadir and the aggregate Nominal Pulse Spacing (ANPS) was calculated to be 0.31 using all valid first return points.
- The NOAA Office for Coastal Management (OCM) downloaded this data set from the USGS rockyweb collection. See the URL section for the specific location. The data were in UTM Zone 8 North (NAD83 2011) coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground, 22 - Temporal Exclusion. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12B model, to convert from UTM Zone 8 North (NAD83 2011) coordinates in meters to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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 or 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.