Data Management Plan
GUID: gov.noaa.nmfs.inport:63018 | Published / External
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 NOAA Hurricane Irma Project area data were collected by Quantum Spatial, Inc. (QSI) using three Riegl systems: a Riegl VQ-880-G+, a Riegl VQ-880-GII, and a Riegl VQ-880-GH. The project acquisition dates spanned from 20181120-20190323 in 85 missions. The final classified LiDAR data were transformed from WGS80 ellipsoid elevations to Geoid12b orthometric elevations and were then used to create topobathymetric bare earth digital elevation models (DEMs) in ERDAS Imagine (*.img) format with a 1m pixel resolution. Ground (2), bathymetric bottom (40), and submerged objects (43) classified points were used in the bare earth DEM creation. The NOAA Hurricane Irma Project digital elevation model (DEM) dataset consists of a bathymetric void clipped bare earth model and an interpolated bare earth model. The 100 meter buffered project area consists of approximately 1,381,270 acres and stretches from the eastern coast of Miami south and westward to the Marquesas Keys. DEM files were compiled in 5,000 m x 5,000 m tiles and clipped to the project boundary. The full project dataset is comprised of 300 - 5,000 m x 5,000 m DEM tiles.
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):
- 2020-09-15 00:00:00 - Data for the NOAA Hurricane Irma project area was acquired by Quantum Spatial (QSI) using Riegl VQ-880-GII, Riegl VQ-880-GH, and Riegl VQ-880-G+ Topobathy LiDAR systems. All derived DEM data is referenced to: Horizontal Datum-NAD83(2011) epoch: 2010.00 Projection-UTM Zone 17N Horizontal Units-meters Vertical Datum-NAVD88 (Geoid12b) Vertical Units-meters The collected LiDAR data were immediately processed in the field by QSI to a level that will allow QA\QC measures to determine if the sensor is functioning properly and assess the coverage of submerged topography. An initial SBET was created in POSPAC MMS 8.3 SP3 and loaded into RiProcess which applies pre-calibrated angular misalignment corrections of scanner position to extract the raw point cloud into geo-referenced LAS files. These files were inspected for sensor malfunctions and then passed through automated raster generation using LAStools to develop an initial assessment of bathymetric coverage. QSI reviewed all acquired flight lines to ensure complete coverage and positional accuracy of the laser points. These rasters were also used to create an initial product - Quick Look Coverage Maps. These Quick Look files are not fully processed data or final products but provide rapid assessment of approximate coverage and depth penetration. QSI resolved kinematic corrections for aircraft position data using aircraft GNSS and Applanix' proprietary PP-RTX solution. When PP-RTX was not used QSI conducted static Global Navigation Satellite System (GNSS) ground surveys (1 Hz recording frequency) using base stations over known monument locations during flights. After the airborne survey, static GPS data were triangulated with nearby Continuously Operating Reference Stations (CORS) using the Online Positioning User Service (OPUS) for precise positioning. Multiple independent sessions over the same base station were performed to confirm antenna height measurements and to refine position accuracy. This data was used to correct the continuous onboard measurements of the aircraft position recorded throughout the flight. A final smoothed best estimate trajectory (SBET) was developed that blends post-processed aircraft position with attitude data. Using the SBETs, sensor head position and attitude were then calculated throughout the survey.PosPac MMS 8.3 SP3 was used for these processes.
- 2020-09-15 00:00:00 - Following final SBET creation, QSI used RiProcess 1.8.5 to calculate laser point positioning by associating SBET positions to each laser point return time, scan angle, and intensity. Terra 19 and LasTools were used to classify water surface and create a water surface model. They are created for single swaths to ensure temporal differences and wave or water surface height variations between flight lines do not impact the refraction of the bathymetric data. These models are used in QSI's LasMonkey refraction tool to determine the accurate positioning of bathymetric points. All LiDAR data below water surface models were classified as water column to be refracted. Light travels at different speeds in air versus water and its direction of travel or angle is changed or refracted when entering the water column. The refraction tool corrects for this difference by adjusting the depth (distance traveled) and horizontal positioning (change of angle/direction) of the LiDAR data. Using raster-based QC methods, the output data is verified to ensure the refraction tool functioned properly. Once all data was refracted by flight line data was exported to LAS 1.4 format and combined into 500 m x 500 m tiles. Data were then further calibrated using TerraMatch. QSI used custom algorithms in TerraScan to classify the initial ground/submerged topography surface points. Relative accuracy of overlapping swaths was compared and verified through the use Delta-Z (DZ) orthos created using QSI's Las Product Creator. Absolute vertical accuracy of the calibrated data was assessed using ground survey data and complete coverage was again verified.
- 2020-09-15 00:00:00 - Post automated classification QSI then performed manual editing to review all classification and improve the final topobathymetric surface. QSI's LasMonkey was used to update LAS header information, including all projection and coordinate reference system information. The final LiDAR data are in LAS format 1.4 and point data record format 6. The final classification scheme is as follows: 1 - Unclassified 2 - Ground 7 - Noise 40 - Bathymetric Bottom or Submerged Topography 41 - Water Surface 43 - Submerged feature 45 - Water Column 46 - Temporal Bathymetric Bottom 71 - Overlap Default 72 - Overlap Ground 81 - Overlap Water Surface 85 - Overlap Water Column 1-Overlap - Edge Clip
- 2020-09-15 00:00:00 - QSI transformed the final LiDAR data from ellipsoid heights to orthometric heights referenced to NAVD88, Geoid12B to create the final topobathymetric DEMs. The topobathymetric bare earth DEMs were output at 1 meter resolution in IMG format into 300 5,000 m x 5,000 m tiles. The NOAA Hurricane Irma Project rasters are clipped to the extent of the project boundary and named according to project specifications. A bathymetric void shapefile was created to indicate areas where there was a lack of bathymetric returns. This shape was created by triangulating bathymetric bottom points with an edge length maximum of 4.56m to identify all areas greater then 9 square meters without bathymetric returns. This shapefile was used to clip and exclude interpolated elevation data from these areas in the bathymetric void clipped topobathymetric bare earth model.
- The NOAA Office for Coastal Management (OCM) received img format files from Quantum Spatial. Horizontal positions were provided in UTM Zone 17 NAD83(2011), meters coordinates. Vertical positions were provided in NAVD88 (Geoid12b) elevations and in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted to GeoTiff format and the projection and vertical datum EPSG codes were assigned.. 2. The data were copied to https
(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
- 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
(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 bulk or custom 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
Data is backed up to tape and 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.