Data Management Plan
GUID: gov.noaa.nmfs.inport:65959 | 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
Product: Lidar based digital elevation model (DEM) data tiles for ground classified points.
Geographic Extent: Approximately 21,453 square miles across South Carolina;
Block 1 (Lot 6 QL2) - approximately 3,583 square miles in Anderson, Cherokee, Greenville, Laurens, Newberry, Oconee, Pickens, Spartanburg, and Union counties
Block 2 (Lot 7 QL1) - approximately 950 square miles in Greenville and Lexington counties
Block 3 (Lot 7 QL2) - approximately 3435 square miles in Abbeville, Aiken, Anderson, Edgefield, Greenwood, Laurens, McCormick, Newberry, Oconee, and Saluda counties
Block 4 (Lot 8 QL1) - approximately 135 square miles in Aiken and Edgefield counties
Block 5 (Lot 8 QL2) - approximately 5,775 square miles in Aiken, Allendale, Bamberg, Barnwell, Calhoun, Chester, Chesterfield, Clarendon, Colleton, Edgefield, Fairfield, Hampton, Kershaw, Lancaster, Lee, Lexington, McCormick, Newberry, Orangeburg, Richland, Saluda, and Sumter counties
Block 6 (Lot 9 QL2) - approximately 7,255 square miles in Bamberg, Beaufort, Berkeley, Charleston, Chesterfield, Clarendon, Colleton, Darlington, Dillon, Dorchester, Florence, Georgetown, Hampton, Horry, Jasper, Kershaw, Lee, Marion, Marlboro, Orangeburg, Sumter, and Williamsburg counties
Block 7 (Lot 9 QL1) - approximately 689 square miles in Beaufort, Berkeley, Charleston, Colleton, Darlington, Dorchester, Florence counties
Dataset Description: The SC Savannah Pee Dee 2019 B19 lidar project called for the planning, acquisition, processing, and production of derivative products of QL 1 and QL2 lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 and 0.71 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal datum/projection of NAD83 (2011) State Plane South Carolina (FIPS 3900) International Feet (EPSG 6570), and a vertical datum of NAVD88 (GEOID18) US Survey Feet. Lidar data was delivered as processed LAS 1.4 files formatted to individual 5,000-Int'l. foot x 5,000-Int'l. foot tiles.
Ground Conditions: Lidar was collected January through March 2020 while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Woolpert established ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. Additional independent accuracy checkpoints were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
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):
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Cloud Optimized GeoTIFF files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the DEM as it resides on AWS under the prd-tnm bucket.
- 2020-09-04 00:00:00 - Lidar Point Cloud Classification: The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Processed, but Unclassified (Class 1), Bare Earth Ground (Class 2), Low Noise (Class 7), Water (Class 9), Bridge Decks (Class 17), High Noise (Class 18), and Ignored Ground (Class 20). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through a semi-automated process. All ground (Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (Class 9) using TerraScan/LP360 macro functionality. A buffer of 0.7 meters was also used around each hydro-flattened feature to classify these ground (Class 2) points to Ignored Ground (Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. 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. GeoCue was then used to create the deliverable industry-standard LAS files. Woolpert proprietary software and LP360 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.
- 2020-09-01 00:00:00 - Hydro-Flattened Digital Elevation Models (DEMs): Class 2 (ground) lidar points in conjunction with the hydro breaklines as well bridge breaklines were used to create a 2-foot hydro-flattened bare-earth raster DEM. Using automated scripting routines within ArcMap, a GeoTIFF file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface.
- 2021-12-15 00:00:00 - The NOAA Office for Coastal Management (OCM) extracted the tiff file URL references and ingested them into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the DEM as it resides on Amazon Web Services (AWS) under the pr-tnm container. (Citation: USGS GeoTiff files on AWS)
(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 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 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.