Data Management Plan
GUID: gov.noaa.nmfs.inport:64345 | 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
In October 2018, Quantum Spatial (QSI) was contracted by the United States Geological Survey (USGS) to collect high resolution topobathymetric Light Detection and Ranging (LiDAR) data in the winter of 2018 for the USGS Gulf Coast sites in the Gulf of Mexico. The USGS Gulf Coast project area covers approximately 174 square miles and is comprised of three main areas of interest; Chandeleur Island, Dauphin Island, and the Gulf Islands off the coast of Louisiana, Alabama, and Florida, respectively.
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 2,272 500 m x 500 m tiles.
Geographic Extent: This dataset and derived products encompass an area covering approximately 471 square kilometers of south Florida, Louisiana, and Alabama.
Traditional near-infrared (NIR) LiDAR was fully integrated with green wavelength (bathymetric) LiDAR in order to provide a seamless topobathymetric LiDAR dataset.
Dataset Description: RAW flight line swaths were processed to create 2,272 classified LAS 1.4 files delineated in 500 m x 500 m tiles. Tile naming is based on the easting/northing location of the lower left corner of each tile. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. From the classified point cloud additional derived products include green and NIR intensity images, hydro-flattened breaklines, hydro-flattened DEMs, interpolated topobathymetric DEMs, clipped topobathymetric DEMs, and highest hit surface models of the study area. Ground Control Points were acquired and calibrated by Quantum Spatial, Inc.
Data acquisition was coordinated by Quantum Spatial and all lidar data calibration, and follow-on processing was completed by Quantum Spatial
Ground Conditions: Acquisition below aircraft free of smoke, fog and cloud cover.
NOAA OCM retrieved the processed lidar point cloud from the USGS rockyftp repository and processed it to the Digital Coast.
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.
4. Resources
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):
Process Steps:
- 2019-03-28 00:00:00 - LiDAR Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a geoid correction. 5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.
- 2019-03-28 00:00:00 - LiDAR Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate final NVA, VVA, and TBVA for the project using ground control quality check points.
- 2021-03-09 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the laz files from these USGS sites and processed the data to the Data Access Viewer (DAV) and to https. The total number of files downloaded and processed was 23,054. ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_FL_GulfCoast_Topography_2018/ Number of files: 2272 The data were in UTM Zone 16 (NAD83 2011), meters, coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water Surface, 17 - Bridge Decks, 20 - Ignored Ground, 40 - Bathymetric Bottom, 41 - Green Scanner Water Surface, 45 - Water Column. OCM processed all classifications of 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. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. This script found spurious values in the noise classifications (> 150m above and below the ground and bathymetric bottom surfaces) that were clipped to ensure valid representation of remaining elevation values. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from UTM Zone 16 (NAD83 2011) coordinates in meters 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.
Missing/invalid information:
- 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.
None
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.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9117/index.html
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.