Data Management Plan
GUID: gov.noaa.nmfs.inport:67488 | 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: Bare earth Digital Elevation Model (DEM) data.
Geographic Extent: Nantucket county Massachusetts, covering approximately 91 square miles.
Dataset Description: The Nantucket project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane, Feet and vertical datum of NAVD88 (GEOID12B), Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1,577 individual 1250 ft x 1250 ft tiles, as tiled Intensity Rasters, and as tiled bare-earth DEM; all tiled to the same 1250 ft x 1250 ft schema.
Ground Conditions: Lidar was collected in early to mid 2018, 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, Sanborn Map Company, Inc. established a total of 20 ground control points that were used to calibrate and validate the lidar to known ground locations established throughout the project area.
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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):
This data was provided by Mass GIS to the NOAA OCM for custom distribution by the NOAA Digital Coast Data Access Viewer (DAV) and bulk distribution via https.
- 2018-01-01 00:00:00 - The following steps describe the Raw Data Processing and Calibration process: 1) Technicians processed the raw data to LAS format flight lines using the ABGNSS/IMU solution. 2) Technicians use TerraSolid TerraMatch to calculate initial calibration adjustment angles by mission and/or block. This is accomplished by identifying ground and above ground feature observations between flight-lines and calculating the offsets. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable. 3) Once the angle calculation was completed the adjusted settings were applied to all of the flight-lines of the mission and/or block and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight-line overlaps match and adjusted as necessary until the results met the project specifications. 4) 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 RMSDz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the calibrated point cloud 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 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.
- 2018-10-12 00:00:00 - LAS Point Classification: The point classification is performed as described below. The bare-earth surface is manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is edited and QC'd, 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 River Pond hydro flattening breaklines were then classified to water (ASPRS Class 9) using LP360 functionality. A buffer of 0.5 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and River Stream 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 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. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper is used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for the Classified Point Cloud Data. LAStools, LP360 and TerraScan software was used to perform statistical analysis of the classes in the LAS files, on a per tile level to verify classification metrics and full LAS header information.
- Hydro Flattened Raster DEM Process: Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 2 foot hydro-flattened Raster DEM. Using automated scripting routines within ArcMap, an GeoTIFF TIF 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.
- 2022-06-30 00:00:00 - The NOAA Office for Coastal Management (OCM) was provided this data set from the office of Mass GIS. The total number of files received and processed was 1619. The data were in Massachusetts Island State Plane NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster files were at a 2 feet grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 6490 and Vertical EPSG: 6360) to the GeoTiff formatted files. 2. Copied the files 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 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.