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 U.S. Geological Survey (USGS) contracted with Hawaii-based Aerial Surveying, Inc. to collect lidar-derived elevation data over the low-lying areas within the northwestern Hawaiian Islands (NWHI) during the summer of 2010. A separate contract issued to Aerial Surveying, Inc. by the National Oceanic and Atmospheric Administration (NOAA) funded the lidar data processing and elevation data product development phases of the project. Lidar data provide high resolution digital elevation models that are used for many applications, including but not limited to sea level rise modeling, habitat assessments, and tsunami inundation modeling. In April 2011, NOAA Papahanaumokuakea Marine National Monument and NOAA Office for Coastal Management deployed a survey crew to the NWHI to collect high accuracy point data to validate the 2010 lidar data. The survey crew used survey-grade Global Positioning System (GPS) receivers to collect high accuracy elevation points.
This metadata covers the information for French Frigate Shoals.
This dataset contains lidar point clouds in LAS 1.2 format, classified according to the ASPRS LAS 1.2 class table.
The following are the equipment used to create the lidar data sets.
Aircraft: Beechcraft Queen Air
Lidar Systems: Riegl 140 and 240
Accuracy statements are based on areas of open terrain, with points classified as ground. The accuracy of each point is expected to meet the vertical accuracy standard, derived products may be less accurate in areas of extreme terrain and dense vegetation due to a lesser number of points defining the ground in these areas.
Classified data sets such as this one may have varying posting due to some pulses not reaching the ground.
This work was conducted under permit number PMNM-2010-033 as approved by NOAA, the U.S. Fish and Wildlife Service (USFWS), and the State of Hawaii, and acknowledged by Dr. Charles L. Littnan of NOAA's Pacific Islands Fisheries Science Center.
Original contact information:
Contact Name: Lidar Manager
Contact Org: Aerial Surveying Inc.
Title: Lidar Manager
Phone: (808) 327-9439
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.
French Frigate Shoals. Tern Island and smaller outer islands.
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):
- 2014-04-17 00:00:00 - Data were received by NOAA Office for Coastal Management (OCM) and NOAA Papahanaumokuakea Marine National Monument (PNMN) from Aerial Surveying Inc. and tested for accuracy nine months after lidar collection. Full metadata was not received. Data were not originally classified for ground points and a separate contract had been done to classify the points. (Citation: lidar data)
- 2021-05-20 00:00:00 - LAS files for French Frigate Shoals could not be located. ASCII text versions of the point clouds did exist with x, y, z, intensity, class, return number, and GPS seconds of the week. For Tern island, the ITRF00 ellipsoid heights text file existed. For the smaller islands, only the ITRF00 EGM96 orthometric heights text file existed. The smaller islands were converted to ellipsoid heights by reversing EGM96. All data was converted from UTM zone 3 to geographic coordinates. The data was converted from ASCII to LAZ format with LAStools txt2las. The GPS seconds of the week were converted to adjusted GPS time using LAStools las2las -week_to_adjusted 1593. (Citation: lidar data)
(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.
This data can be obtained on-line at the following URL:
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.