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 surface model (DSM), digital terrain model (DTM), and intensity model of Mount Juneau, Southeast Alaska, during near snow-free ground conditions on September 6, 2019. The survey provides snow-free surface elevations for deriving snow depth distribution models with repeat surveys during snow-covered conditions. Ground control data were collected on September 5, 2019, and aerial lidar were collected on September 6, 2019, and subsequently processed in a suite of geospatial processing software. These products are released as a Raw Data File with an open end-user license. All files can be downloaded from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30731).
The NOAA Office for Coastal Management (OCM) downloaded this data set from this AK DGGS site:
This file was 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.
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).
- 2019-09-06 00:00:00 - Aerial photogrammetric 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 can collect up to 820,000 points per second at a range of up to 150 m. The scanner operated with a pulse refresh rate of 50,000 pulses per second in the alpine areas and 400,000 pulses per second over forested areas at a scan rate between 80 and 220 lines per second. We used a Bell 206 JetRanger to survey from an elevation of ~130 m above ground level, at a ground speed of ~30 m/s, and with a scan angle set from 80 to 280 degrees. The total survey area covers ~14 km2. We flew the aerial survey on September 6, 2019, with departure at 12:20 pm from Juneau International Airport, Alaska, and landed back at Juneau International Airport at 4:30 pm. The second part of the survey, covering Mount Juneau, started at 2:30 pm from Mount Anderson on Douglas Island. The weather throughout the survey was clear with no wind.
- 2019-01-01 00:00:00 - Lidar dataset processing - We processed point data in SDCimport software for initial filtering and multiple-time-around (MTA) disambiguation. MTA errors, corrected in this process, are the result of ambiguous interpretations of received pulse time intervals and occur more frequently with higher pulse refresh rates. We processed Inertial Measurement Unit (IMU) and Global Navigation Satellite System (GNSS) data in Inertial Explorer and we used Spatial Explorer software to integrate flightline information with the point cloud. We calibrated the point data at an incrementally precise scale of sensor movement and behavior, incorporating sensor velocity, roll, pitch, and yaw fluctuations throughout the survey. We created macros in Terrasolid software and classified points in accordance with American Society for Photogrammetry and Remote Sensing (ASPRS) 2014 guidelines. We gave careful attention 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, we applied a geometric transformation and converted the points from ellipsoidal heights to GEOID12B (Alaska) orthometric heights. We used ArcMap to derive raster products from the point cloud. The DSM was interpolated from maximum return values from the ground, vegetation and building classes using a binning method. The DTM was interpolated from all ground class returns also using a binning method and minimum values. In ArcMap, we produced an intensity image using closest-to-mean binning.
- 2022-10-11 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 8N NAD83 (2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The bare earth raster file was at a 0.5 meter grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used an internal script to assign the EPSG codes (Horizontal EPSG: 6337 and Vertical EPSG: 5703) to the GeoTiff formatted file. 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.