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 classified point cloud, digital terrain model (DTM), surface model (DSM), and intensity model of land areas in northern Barry Arm, northwest Prince William Sound, Alaska, during near snow-free ground conditions on June 26, 2020. The goal of the survey is to provide high quality, modern topographic data in the recently deglacierized part of Barry Arm where significant landslide hazards exist. Aerial lidar and ground control data were collected on June 26, 2020, and subsequently processed in Terrasolid and ArcGIS. Ground control was collected on June 26, 2020, as well. All files can be downloaded free of charge from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30589).
The NOAA Office for Coastal Management (OCM) downloaded this data set from this AK DGGS site:
These files were processed to make the data available for custom and bulk download from the NOAA Digital Coast Data Access Viewer (DAV) . The total number of files downloaded and processed was 1. NOAA OCM noted that there are artifact areas along some of the borders of the data set.
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):
Data were collected by the Alaska Division of Geological and Geophysical Surveys (AK DGGS). OCM downloaded the data from the Alaska DGGS Elevation Portal and processed the data to be available for custom and bulk download from the NOAA Digital Coast Data Access Viewer (DAV).
- 2020-06-26 00:00:00 - Airborne survey - DGGS used a Riegl VUX1-LR laser scanner integrated with a global navigation satellite system (GNSS) and Northrop Grumman LN-200C inertial measurement unit (IMU). The lidar integration system 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 600,000 pulses per second at a scan rate between 80 and 150 lines per second. This survey was flown with an average elevation of 200 m above ground level and a ground speed of approximately 36 m/s with a fixed-wing aircraft configuration, using a Cessna 180 aircraft. The scan angle was set from 80 to 280 degrees. The total area surveyed was approximately 40 km2. Flight take-off occurred at 10:15am from Merrill Field airport in Anchorage, Alaska, and landing occurred at 4:00 pm. The aircraft landed at the airstrip in Girdwood, Alaska, once during the survey.
- 2020-06-26 00:00:00 - Ground survey - Ground control and check points were collected on June 26, 2020. A Trimble R10-2 GNSS receiver with internal antenna was deployed on the ridge near the center of the study and provided a base station occupation and real-time kinematic (RTK) corrections to points surveyed with a rover Trimble R10-2 GNSS receiver (internal antenna). A total of 106 ground control points and check points were collected to be used for calibration and assessment of the vertical accuracy of the point cloud. All points were collected on bare earth or minimally vegetated surface.
- 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. Inertial Measurement Unit (IMU) and Global Navigation Satellite System (GNSS) data were processed in Inertial Explorer and 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) orthometric 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 DTM was also used to produce a separate hydro-enforced raster based on a digitized shoreline. The DSM was likewise interpolated from only the first return points using a TIN-based method. An intensity image was also produced in ArcMap, using closest-to-mean binning.
- 2022-09-06 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1 raster DEM file in GeoTiff format from the Alaska DGGS Elevation Portal. The data were in UTM Zone 6 NAD83 (2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The bare earth raster file was at a 1 meter grid spacing. NOAA OCM noted that there are artifact areas along some of the borders of the data set. 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: 6335 and Vertical EPSG: 5703) to the GeoTiff formatted files. 2. Copied the files to https.
(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
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.