Data Management Plan
GUID: gov.noaa.nmfs.inport:68536 | 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
The Alaska Division of Geological & Geophysical Surveys (DGGS) used aerial lidar to produce a digital terrain model (DTM), surface model (DSM), and intensity image for an area in and around the community of Haines, Alaska, as part of emergency operations in response to the December 2, 2020, landslide that claimed the lives of two residents. Airborne data were collected December 8 - 12, 2020, and subsequently processed in Terrasolid and ArcGIS. Ground control were collected December 15-16, by the DMLW. This data collection is released as a Raw Data File with an open end-user license. All files can be downloaded free of charge from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30595).
The NOAA Office for Coastal Management (OCM) downloaded this data set from this AK DGGS site:
These files were processed to the NOAA Digital Coast Data Access Viewer (DAV) and AWS S3. The total number of files downloaded was 209, but only 203 of the 209 files were processed.
In addition to the lidar point data, the bare earth Digital Elevation Model (DEM) data at a 1 meter grid spacing, created from the lidar point data are also available from the NOAA Digital Coast. Links to these data are 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 data were collected for the Alaska Division of Geological and Geophysical Surveys (DGGS) and made available on the AK DGGS Elevation Portal (https://elevation.alaska.gov/). The NOAA Office for Coastal Management (OCM) downloaded the data from this site to make the data available for custom downloads from the NOAA Digital Coast Data Access Viewer and for bulk downloads from the AWS S3 bucket.
- 2020-12-12 00:00:00 - Airborne survey - DGGS operates a Riegl VUX1-LR laser scanner integrated with a GNSS and Northrop Grumman IMU system. The integration was designed by Phoenix LiDAR systems. The sensor is capable of collecting up to 820,000 points per second over a distance of 150 m. This survey was flown with a pulse refresh rate between 200,000 and 400,000 pulses per second at a scan rate between 80 and 150 lines per second. This survey was flown with an average elevation of 400 m above ground level and a ground speed of approximately 40 m/s, using a Bell 206 helicopter. The scan angle was set from 55 to 305 degrees. The total area surveyed was approximately 73 km2. The airborne survey was flown December 8-12, 2020, using a Bell 206 helicopter. The weather throughout the survey was sub-optimal, with strong winds, light precipitation, and low-hanging clouds.
- 2020-12-16 00:00:00 - Ground survey - The DMLW collected 67 points using a Trimble R10 GNSS instrument. Of these points, 31 were used as control points, while 36 were used as checkpoints.
- 2020-01-01 00:00:00 - Lidar dataset processing - Point data were processed in SDCimport software for initial filtering and multiple-time-around (MTA) disambiguation. MTA errors, corrected in this process, are the result of imprecise interpretations of received pulse time intervals and occur more frequently with higher pulse refresh rates. IMU and GPS data were used to integrate flightline information with the point cloud in Spatial Explorer software. The point data were calibrated at an incrementally precise scale of sensor movement and behavior, incorporating sensor velocity, roll, pitch, and yaw fluctuations throughout the survey. Points were classified in accordance with American Society for Photogrammetry and Remote Sensing (ASPRS) 2014 guidelines, using macros designed in Terrasolid software. Careful attention was given to the interpolation of the project's ground surface to compensate for inconsistent penetration through low vegetation as a function of the scan angle. Once classified, points underwent a geometric transformation and were converted from ellipsoidal heights to GEOID12B (Alaska) heights. Raster products were derived from the point cloud using ArcMap. The DTM was interpolated from all ground class returns using a tin-based method. The DSM was likewise interpolated from only the first returns for all classes. An intensity image was produced in ArcMap, using closest-to-mean binning.
- 2022-11-23 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 209 laz files from the Alaska Division of Geological and Geophysical Surveys Elevation Portal (https://elevation.alaska.gov/). The files contained classified elevation and intensity measurements for the 2020 Haines, Alaska project. The data were in UTM Zone 8 NAD83 (2011), meters coordinates and NAVD88 (GEOID12B) elevations in meters. During processing, OCM noted that there are some points classified as buildings, that don't appear to fall on buildings and also that 6 of the 209 laz files failed to process to the NOAA Digital Coast Data Access Viewer database. These files were: pt000005.laz pt000025.laz pt000067.laz pt000068.laz pt000069.laz pt000070.laz The data had the following classifications: 1 - Unclassified, 2 - Ground, 3- Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Building, 7 - Noise. OCM processed all 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. Internal OCM scripts were 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 UTM Zone 8 NAD83 (2011), meters coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12B model, to filter out elevation values less than -50 meters, to assign the geokeys, to sort the data by gps time, zip the data to database, and to create Cloud Optimized Point Cloud (COPC) version laz files that are available from the AWS S3 bucket.
(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.