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
This metadata record describes the unclassified, last return, point cloud data for the 2011 USGS North Slope of Alaska lidar project. This record was created by the NOAA Office for Coastal Management (OCM) because no metadata record or data report were available for the data. Information to create this record was found here: https://topotools.cr.usgs.gov/posters/arctic_coast_alaska.pdf and from the tile metadata for AK_NORTHSLOPE_UTM4_2011_000001 at USGS EarthExplorer.
This 2011 data set is part of the USGS assessment of coastal change hazards, over 11,000 km2 of airborne lidar elevation data were collected along the Arctic coast of Alaska between 2009 and 2012. Data coverage includes the barrier islands and mainland coast between Icy Cape and the U.S.–Canadian border, from the shoreline to ~1.5 km inland. Data coverage extends further inland to around 3 km on the Barrow Peninsula and along the coast of the Teshekpuk Lake Special Area (TLSA) where coastal erosion rates are among the highest in the world (> 18 m/yr). Nominal point density is 1.5 m and vertical accuracy is better than 30 cm. Data were not collected over most river deltas or large embayments, with the exception of Admiralty Bay, Smith Bay (Ikpikpik Delta), Kogru River, and the Fish Creek portion of Colville River Delta. The primary use of the lidar data is to establish a modern shoreline position to be used for change analyses with historical shoreline positions. However, the lidar DEM provides a wealth of topographic and intensity data that can be used for morphological mapping of the remote arctic coast.
This is one of the first comprehensive lidar datasets collected in a continuous permafrost environment. Many periglacial landscape features, such as patterned ground, ice-wedge polygons, and thermokarst lakes and former lake basins (recent and relict) are discernible in the dataset. Traditional coastal landscape features including shoreline position, beach width, slope, and bluff height and morphology are also distinct.
Acquired by Aerometric, Alaska; Funded by USGS National Geospatial Program, Coastal and Marine Geology Program, Alaska Science Center; U.S. Fish and Wildlife Service, Arctic Landscape Conservation Cooperative; U.S. Bureau of Land Management
The NOAA Office for Coastal Management (OCM) downloaded this lidar data from the AK DGGS site (https://elevation.alaska.gov/) and processed the data to be available on the Digital Coast Data Access Viewer (DAV).
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):
- 2018-05-21 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 500 laz files from the Alaska Division of Geological and Geophysical Surveys data Portal (https://elevation.alaska.gov/). The files contained unclassified (last return) elevation and intensity measurements for the 2011 North Slope AK data set. The data were in UTM Zones 4 and 5 coordinates and ellipsoid (GRS80) elevations in meters. The data were unclassified last returns. The NOAA Office for Coastal Management 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. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from UTM Zone 4 and 5 coordinates to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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 custom or bulk 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.