Data Management Plan
GUID: gov.noaa.nmfs.inport:74381 | 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
Lidar-derived elevation data for the Twentymile River watershed, Southcentral Alaska, collected August-October 2022, Raw Data File 2023-3, uses aerial lidar to produce a classified point cloud, digital surface model (DSM), digital terrain model (DTM), and intensity model of the Twentymile River watershed, Southcentral Alaska, during snow-free ground conditions from August to October 2022. The survey provides snow-free surface elevations for trail planning and assessing avalanche hazards, among other objectives. Ground control data were collected on August 31, 2022, and aerial lidar data were collected on multiple days from August 29 to October 14, 2022, 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/30959).
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.
4. Resources
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):
Lineage Statement:
Data were collected by the Alaska Division of Geological and Geophysical Surveys (AK DGGS). The data were downloaded by the NOAA Office for Coastal Management (OCM) and processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from S3 AWS.
Process Steps:
- 2022-10-14 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) 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 200,000-400,000 pulses per second over forested terrain, and 50,000-100,000 pulses per second over alpine terrain, with a scan rate between 80 and 220 lines per second. We used a Cessna 180 fixed-wing aircraft to survey from an elevation of approximately 60-600 m above ground level, at a ground speed of approximately 40 m/s, and with a scan angle set from 80 to 280 degrees. The total survey area covers approximately 488 km2. The survey area was accessed by air from the Girdwood-Alyeska and Merrill Field airports in Girdwood and Anchorage. See table 1 for departure and return times and weather conditions.
- 2022-08-31 00:00:00 - Ground survey - The Alaska Division of Mining, Land, and Water (DMLW) collected ground control points on August 31, 2022. They deployed a Trimble R12 GNSS receiver at an unnamed survey marker (0.5 in steel rod in a 4 in pipe casing) offset from the south side of the Alaska Railroad Portage Depot parking lot. It provided a two-hour base station occupation and real-time kinematic (RTK) corrections to points they surveyed with a rover Trimble R12i GNSS receiver (internal antenna). DMLW collected 24 ground control points and check points to use for calibration and to assess the vertical accuracy of the point cloud. Most points were collected on bare earth or paved surfaces. However, ground control points 9, 17, 18, and 24 were collected in forest and shrubland.
- 2022-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, result from 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 per the American Society for Photogrammetry and Remote Sensing (ASPRS) 2019 guidelines. Once classified, we applied a geometric transformation and converted the points from ellipsoidal heights to GEOID12B (Alaska) orthometric heights. We used ArcGIS Pro to derive raster products from the point cloud. A 50 cm DSM was interpolated from maximum return values from the ground, vegetation, bridge deck, and building classes using a binning method. A 50 cm DTM was interpolated from all ground class returns using a binning method and minimum values. An additional 20 cm DTM was produced for the scientific priority area using a triangulation interpolation. We produced an intensity image using average binning in ArcGIS Pro.
- 2025-01-22 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1 GeoTiff data file from the Alaska Division of Geological and Geophysical Surveys (AK DGGS). The data were in UTM Zone 6 (NAD83 2011), meters coordinates and NAVD88 (Geoid12b) elevations in meters. The bare earth raster files were at a 0.5 meter grid spacing. 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 file. 2. Copied the file 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.
Missing/invalid information:
- 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.
This report, map, and/or dataset is available directly from the State of Alaska, Department of Natural Resources, Division of Geological & Geophysical Surveys
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.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10246/details/10246
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 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.