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 lidar data are processed Classified LAS 1.4 files, formatted to 128 individual 1500 m x 1500 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
Geographic Extent: York County in Maine, covering approximately 92 total square miles.
Dataset Description: The ME_SouthCoastal_2_2020 Work Unit 212010 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. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 128 individual 1500 m x 1500 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1500 m x 1500 m schema. Continuous breaklines were produced in Esri file geodatabase format.
Ground Conditions: LiDAR was collected in spring 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, NV5 Geospatial, powered by Quantum Spatial utilized a total of 64 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 151 independent accuracy checkpoints, 86 in Bare Earth and Urban landcovers (86 NVA points), 65 in Tall Weeds categories (65 VVA points), were 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 Entwine Point Tiles (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
- 2021-01-01 00:00:00 - Raw Data and Boresight Processing: 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 NV5 Geospatial, powered by Quantum Spatial 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 technicians then analyzed the results and made any necessary additional adjustment until it was 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 matched 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 7 cm RMSEz within individual swaths and less than or equal to 10 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 checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met.
- 2021-01-01 00:00:00 - LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was 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-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter 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 overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes. 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 through numerous conference calls and pilot study areas. All data were 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 for both the All Point Cloud Data and the Bare Earth. NV5 Geospatial, powered by Quantum Spatial 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. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zone 19N, Meter and vertical datum of NAVD88 Geoid 18, Meter.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were reprojected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical (NAVD88 GEOID18 meters).
- 2021-11-30 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. This is the AWS URL being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/ME_SouthCoastal_2_2020/ept.json The data reports, metadata, and breaklines were downloaded from this USGS site: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/ME_SouthCoastal_2020_A20/
(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.