Data Management Plan
GUID: gov.noaa.nmfs.inport:67860 | 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 State of Alaska Division of Geological & Geophysical Surveys (DGGS) used lidar to produce a digital terrain model (DTM) and digital surface model (DSM) of Turnagain Pass, southcentral Alaska, during snow-free ground conditions. This dataset includes point cloud data, a 32-bit digital terrain model and digital surface model, and an intensity image covering Turnagain Pass located southeast of Anchorage within the Chugach National Forest on the Kenai Peninsula in southcentral Alaska. The lidar and Global Navigation Satellite System (GNSS) data were collected on September 2, 2018, and processed using Terrasolid. 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/30567).
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 229.
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.
- 2018-09-02 00:00:00 - Airborne survey - This lidar survey was flown at an average elevation of 200 m above ground level and a ground speed of approximately 40 meters per second with a fixed-wing Cessna 180. Elevation data were acquired with a Riegl VUX1-LR laser scanner integrated with a GNSS and Northrop Grumman IMU system. The integration was designed by Phoenix LiDAR systems. Lidar data were acquired at a pulse rate ranging from 50,000 pulses per second in the alpine areas to 400,000 pulses per second over forested areas, a scan rate of 200 revolutions per second, and a scan angle range of 80-280 degrees. The accompanying report provides additional detail regarding flight conditions.
- 2018-09-02 00:00:00 - Ground survey - Ground control and check points were collected on September 2, 2018. A Trimble R7 GNSS receiver with Zephyr-2 antenna was deployed near the center of the study area and provided a base station occupation and real-time kinematic (RTK) corrections to points surveyed with a rover Trimble R8-4 GNSS receiver (internal antenna). 78 total 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 a paved road surface.
- 2019-01-01 00:00:00 - Lidar dataset processing - Raw data were processed using Terrasolid software to produce integrated files for navigation correction and a point cloud for calibration. The navigation was corrected using Inertial Explorer software, where the GNSS and IMU data are integrated to establish correct flight path and orientation of the lidar sensor. Internal consistency of the dataset was improved by calibrating the point cloud data using global, flight line, and fluctuation (within individual flightlines) tielines in Terrasolid software. The point cloud was classified for ground points as well as low, medium, and high vegetation (0.01-0.5 m, 0.5-3 m, and 3-60 m heights above the ground, respectively, in accordance with ASPRS lidar classification codes). Some manual processing was required to eliminate erratically placed points and misclassified ground points. All low points and air points were eliminated from the dataset. A LAS dataset was created in ArcMAP, from which a 50 cm DTM, DSM, and intensity image were produced. The DTM was derived from elevation values of ground-classified points only, and built using the binning technique of minimum elevation and linear void fill. The DSM was derived from elevation values from first returns from all point classes, and built using the binning technique of average elevation values and linear void fill. The intensity image was derived from intensity values of first return points.
- 2022-09-08 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 229 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 2018 Turnagain Pass project. The data were in UTM Zone 6 NAD83 (2011), meters coordinates and NAVD88 (GEOID12B) elevations in meters. The data had the following classifications: 1 - Unclassified, 2 - Ground, 3- Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 7 - Noise, 8 - Model Key Point. 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 6 NAD83 (2011) meters coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12B model, to assign the geokeys, to sort the data by gps time and zip the data to database and to 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.