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:

2019 AK DGGS Lidar DEM: Utqiagvik - Atqasuk, Alaska

Taken From: Item Identification | Title

1.2. Summary description of the data:

Lidar-derived elevation data for the Utqiagvik-Atqasuk region, Alaska, collected August 2019, Raw Data File 2022-10, provides classified point cloud, digital terrain model (DTM), surface model (DSM), and intensity model data for the communities of Utqiagvik and Atqasuk and surrounding areas. The data were collected in support of the Alaska Strategic Transportation and Resources (ASTAR) program for the purpose of investigating the potential for future road infrastructure connecting the communities. Aerial lidar data were collected between August 19 and 23, 2019, and subsequently processed using 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/30870).

The NOAA Office for Coastal Management (OCM) downloaded this data set from this AK DGGS site:

https://elevation.alaska.gov/

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.

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. These data are available for custom download at the link 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:

2019-08-19 to 2019-08-23

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: -157.730747, E: -156.233342, N: 71.345557, S: 70.479988

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)

Taken From: Data Set Information | Data Presentation Form

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

Taken From: Acquisition Information | Instruments, Platforms

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?

No information found

Taken From: Data Management | Have resources for management of these data been identified?

4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

No information found

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

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). 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).

Process Steps:

2019-09-23 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 over a distance of 150 m. This survey was flown with a pulse refresh rate of 400,000 pulses per second, at a scan rate between 80 and 220 lines per second. This survey was flown with an average elevation of 200 m above ground level and a ground speed of approximately 30 m/s with a fixed-wing configuration, using a Cessna 180. The scan angle was set from 80 to 280 degrees. The total area surveyed was approximately 1,595 km^2. Aerial lidar was collected between August 19 and 23, 2019. Seven flightlines collected on the evening of August 22 yielded too large a file for our software to process and the points from those lines are not represented in our final product.
2018-09-01 00:00:00 - Ground survey - Ground survey points from an UMIAQ, LLC, collection in September 2018, were used as control and checkpoint data for this dataset. These survey data were originally gathered in support of a USGS 3DEP funded lidar project, headed by Quantum Spatial (now NV5 Geospatial).
2022-01-01 00:00:00 - Photogrammetric 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. 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 ArcGIS Pro. The DTM was interpolated from all ground class returns using a TIN-based method. The DSM was likewise interpolated from only the first return points. An intensity image was also produced in ArcGIS Pro, using closest-to-mean binning.
2022-09-28 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 4 NAD83 (2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The bare earth raster file was at a 1 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: 6333 and Vertical EPSG: 5703) to the GeoTiff formatted files. 2. Copied the files to https.

Taken From: Lineage | Lineage Statement, Process Steps (Process Date/Time, Source Citation Title, Description)

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

Taken From: Data Quality | Quality Control Procedures Employed

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
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?

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:

https://www.fisheries.noaa.gov/inport/item/67940

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?

No information found

Taken From: Data Management | Do these data comply with the Data Access directive?

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

Taken From: Data Management | Is access to the data limited based on an approved waiver?

7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

Taken From: Access Info | Data Access Constraints

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:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9615/details/9615
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/AK_Utqiagvik_DEM_2019_9615/index.html

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.

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

No information found

Taken From: Data Management | Approximate delay between data collection and dissemination

7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

Taken From: Data Management | If delay is longer than latency of automated processing, indicate under what authority data access is delayed
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.

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)

No information found

Taken From: Data Management | Actual or planned long-term data archive location

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

Taken From: Data Management | 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?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

No information found

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

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