Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
2023 AK DGGS Lidar DEM: Wrangell Island, AK
1.2. Summary description of the data:

Lidar-derived elevation data for Wrangell Island, Southeast Alaska, collected July 2023, Raw Data File 2023-28, provides lidar-derived classified point cloud, a digital surface model (DSM), a digital terrain model (DTM), and an intensity model of Wrangell Island, Southeast Alaska, during leaf-on ground conditions. The survey provides snow-free surface elevations for use in shoreline development, resource quantification, hydrographic mapping, and slope stability modeling. Ground control data were collected June 26-30, 2023, and aerial lidar data were collected July 7-11, 2023, and subsequently merged and processed using a suite of geospatial processing software. All files can be downloaded from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/31098).

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV).

The NOAA Office for Coastal Management (OCM) downloaded 1 GeoTiff data file from the AK DGGS (Alaska Division of Geological and Geophysical Surveys) from https://dggs.alaska.gov/webpubs/data/rdf2023_028_lidar-wrangell-2023-dtm-merged-only.zip . The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for bulk and custom downloads.

In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from are also available from the NOAA Digital Coast. A link to these data is provided in the URL section of this metadata record.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2023-07-07 to 2023-07-11
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -132.396167, E: -131.920007, N: 56.494219, S: 56.115756
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Model (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
No information found
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(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:

  • 2023-06-30 00:00:00 - Ground survey - Ground control points were collected June 26-30, 2023, by the Alaska Division of Mining, Land and Water (DMLW). They deployed a Trimble R12 GNSS receiver to provide a base station occupation and real-time kinematic (RTK) corrections to points they surveyed with a rover Trimble R12i GNSS receiver/TSC5 controller. Benchmark HH-2 (PID BBDX58), located on the Heritage Harbor breakwater in Wrangell, served as the base station location. DMLW collected 43 ground control points and 214 checkpoints to use for calibration and assess the vertical accuracy of the point cloud. Checkpoints were collected in forest, shrubland, grassland, sphagnum bog, bare earth, and paved surfaces. We processed and delivered all data in NAD83 (2011) UTM8N and vertical datum NAVD88 GEOID12B.
  • 2023-07-11 00:00:00 - Aerial photogrammetric survey - DGGS used a Riegl VUX1-LR22 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 a maximum of 1,500,000 points per second at a range of 150 m, or a minimum of 50,000 points per second at a range of 640 m. The scanner operated with a pulse refresh rate of 600,000 pulses per second over forested terrain, and 200,000 pulses per second over alpine terrain, with a scan rate between 50 and 200 lines per second. We used a Cessna 180 fixed-wing platform to survey from an elevation of approximately 150-350 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 565 km2. The survey area was accessed by air from Wrangell Airport. See table 1 of the accompanying report for data collection start and end times, and weather conditions.
  • 2023-01-01 00:00:00 - Lidar dataset processing - We processed point data in Spatial Explorer 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 IMU and GNSS data in Inertial Explorer, and flightline information was integrated with the point cloud in Spatial Explorer. 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 the American Society for Photogrammetry & Remote Sensing (ASPRS) 2019 guidelines (ASPRS, 2019). 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 ground, vegetation, bridge deck, and building classes using a binning method and maximum values. A 50-cm DTM was interpolated from all ground class returns using a binning method and minimum values. We also produced an intensity image for the entire area using average binning in ArcGIS Pro, with no normalization or corrections applied.
  • 2024-02-02 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) for the Wrangell Island, AK project. The bare earth raster file was at a 0.5 m grid spacing. The data were in UTM Zone 8N NAD83 (2011), meters coordinates and NAVD88 (Geoid12b) elevations in meters. The single large file was retiled to 55 smaller tiles using gdal_retile.py. OCM assigned the appropriate EPSG codes (Horiz - 6337, Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

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
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
Yes
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

Data is available online for bulk and custom downloads.

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
NCEI_NC
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office for Coastal Management - Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
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.

Always left blank