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 Oahu, Hawaii Elevation Data Task Order involves collecting and delivering topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements on the island of Oahu in Hawaii. The Statement of Work (SOW) for the area covering the northern 2/3 of Oahu was developed by the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management. A separate but related task order was issued by the USGS National Geospatial Technical Operations Center (NGTOC), under their Geospatial Products and Services Contract (GPSC), to leverage the same resources committed to the NOAA LiDAR project for the acquisition of LiDAR data in the southern 1/3 portion of Oahu. The combined task orders yielded one study area covering the entire island of Oahu. The data collected for the island of Oahu will exhibit Hydro Flattened DEMs for inclusion into the NED. The purpose of the data is for use in coastal management decision making, including applications such as flood plain mapping and water rights management. The point density for this data set was specified in the SOW at 1.15 pts/m2. The NOAA Office for Coastal Management tested the NPS (nominal pulse spacing) for this data set in April 2015. The NPS was determined to be 0.84 m. The data used in the NPS determination were the first returns of classes 1,2,9, and 10.
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):
- 2013-01-01 00:00:00 - Applanix software was used in the post processing of the airborne GPS and inertial data that is critical to the positioning and orientation of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for Optech's post processor to develop the point cloud from the LiDAR missions. The point cloud is the mathematical three dimensional collection of all returns from all laser pulses as determined from the aerial mission. At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above ground features are removed from the data set. The point cloud was manipulated within the Optech or Leica software; GeoCue, TerraScan, and TerraModeler software was used for the automated data classification, manual cleanup, and bare earth generation from this data. Project specific macros were used to classify the ground and to remove the side overlap between parallel flight lines. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Class 2 LIDAR was used to create a bare earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers. Inland Ponds and Lakes of 2 acres or greater were also collected. Elevation values were assigned to all Inland Ponds and Lakes using TerraModeler functionality. Elevation values were assigned to all Inland Streams and Rivers using Photo Science proprietary software. All Class 2 LIDAR data falling inside of the collected breaklines were then classified to Class 9 and Class 2 LIDAR data falling within a proximity of one meter will be classified to Class 10 using TerraScan macro functionality. The breakline files were translated to ESRI Shapefile format using ESRI conversion tools. Data was then run through additional macros to ensure deliverable classification levels matching LAS ASPRS Classification structure. GeoCue functionality was used to ensure correct LAS Version. In house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. Tiles were run through automated scripting within ArcMap and were combined with the Hydro Flattened Breaklines to create the 1 meter DEM. Final DEM tiles were clipped to the tile boundary in order to provide a seamless dataset. A manual QA review of the tiles was completed in ArcMap and Global Mapper to ensure full coverage with no gaps or slivers within the project area. (Citation: LiDAR)
- 2014-05-02 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in laz format via hard drive from PhotoScience, Inc. The data arrived referenced to the Universal Transverse Mercator (UTM) Zone 4 projection and vertical elevations were in ellipsoidal values. 1. The data were converted from projected coordinates to geographic coordinates. 2. Originally delivered as class 25 points (Overlap water) were merged into class 9. (Citation: LiDAR)
- 2015-03-15 00:00:00 - After review by USGS, a revised version of the data was delivered to OCM. The data were revised to change classifications in bridge/culvert locations. 1. Data were updated to change bridge/culvert from Class 2 (ground) to Class 1 (unclassified).
(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.6. Type(s) of data
- 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: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3655
The data set is dynamically generated based on user-specified parameters.;
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.