Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:74801 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
Product:
These are Digital Elevation Model (DEM) data for the required deliverables for the LA Coastal Louisiana Lidar project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM.
Geographic Extent:
LA_CoastalLouisiana_1 (Work Unit 197958) covering approximately 2,200 square miles in Jefferson, Orleans, Plaquemines, and St. Bernard Parishes
LA_CoastalLouisiana_2 (Work Unit 228382) covering approximately 734 square miles in Jefferson, Lafourche, Plaquemines, and St. Charles Parishes
Dataset Description:
The LA Coastal Louisiana Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data were developed based on a horizontal datum/projection of NAD83 (2011) UTM Zone 15N (LA_CoastalLouisiana_2 (Work Unit 228382)) and 16N (LA_CoastalLouisiana_1 (Work Unit 197958)), Universal Transverse Mercator, meters and a vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1,000 m x 1,000 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1,000 m x 1,000 m schema.
Ground Conditions:
Lidar was collected in early 2021 and late 2021, while no snow was on the ground and rivers were at or below normal levels.
LA_CoastalLouisiana_1
In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Dewberry, established a total of 34 ground control points that were used to calibrate the LA_CoastalLouisiana_1 (Work Unit 197958) lidar to known ground locations established throughout the LA Coastal Louisiana project area. An additional 111 independent accuracy checkpoints, 62 in Bare Earth and Urban landcovers (62 NVA points), 49 in Tall Grass and Brushland/Low Trees categories (49 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
LA_CoastalLouisiana_2
In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Dewberry, established a total of 17 ground control points that were used to calibrate the LA_CoastalLouisiana_2 (Work Unit 228328) lidar to known ground locations established throughout the LA Coastal Louisiana 2020 project area. An additional 48 independent accuracy checkpoints, 31 in Bare Earth and Urban landcovers (31 NVA points), 17 in Tall Grass and Brushland/Low Trees categories (17 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the GeoTIFF files hosted by USGS on Amazon Web Services.
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.
LA_CoastalLouisiana_1 (Work Unit 197958)
W: -90.37, E: -89.99, N: 29.9, S: 29.06LA_CoastalLouisiana_2 (Work Unit 228382)
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS.
Process Steps:
- 2022-07-01 00:00:00 - The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2.1, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.
- 2022-07-06 00:00:00 - LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.7 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. The withheld bit was set on the withheld points previously identified in TerraScan before the ground classification routine was performed. The withheld bit was set on class 7 and class 18 in TerraScan after all classification was complete. Dewberry proprietary software was then used to create the deliverable industry-standard LAS files for both the Point Cloud Data and the Bare Earth. Dewberry proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.
- 2022-07-06 00:00:00 - Data was tested at 0.31 meter nominal pulse spacing and 10.6 points per square meter (ppsm). The average density was tested on the LAS data using geometrically reliable (withheld and noise points excluded) first-return points. (A)NPD was tested using rasters which produce the average number of points within each cell.
- 2022-07-31 00:00:00 - Hydro Flattened Raster DEM Process: Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM. Using LP360, a TIFF file was created for each tile. Each surface is reviewed using ArcMap to check for any surface anomalies or incorrect elevations found within the surface.
- 2025-01-29 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTIFF files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the raster data as it resides on Amazon Web Services (AWS). These are the GeoTIFF files that are being accessed: https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/LA_CoastalLouisiana_2020_D20/LA_CoastalLouisiana_1_2020/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/LA_CoastalLouisiana_2020_D20/LA_CoastalLouisiana_2_2020/TIFF/
(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://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/LA_CoastalLouisiana_2020_D20/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and 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 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.