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
Elevations were collected using an underwater laser scanner (lidar) in Lake Huron, MI from November 16 to 18, 2020. Data were geospatially adjusted to match a multibeam survey conducted at the same time. Positional accuracy was not accessed. Data represent the best estimate of the bottom surface.
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.
In Lake Huron.
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):
- 2020-11-18 00:00:00 - Multiple locations were tried to test the ROV and laser system. The Detroit River, St. Clair River, and Lake Erie shoreline were found to lack the necessary water clarity. Lake Huron was tried in locations identified using navigation charts. A target was located that appeared to be a large cargo shipwreck. The City of Genoa was a grain freighter that sunk in 1911. The basic structure of the wreck remains on the bed of Lake Huron heavily deteriorated. The ROV was launched at the site and successfully collected laser data of the wreck. Ambient light in the water limited the usable range of the laser, so passes were collected over some areas only.
- 2020-11-18 00:00:00 - A review of the data collected during the inspections was completed in the ASI office. The 3D files were converted to point clouds and erroneous noise was removed. The LiDAR files were adjusted in position to best file the sonar data collected of the wreck. The assembly of this report was then completed. The report includes documentation methodology, equipment descriptions, observations, observation images, and 3D dataset. Data files are provided of the various areas survey by MBES in meters located in UTM zone 17 as collected and in elevation referenced to NAVD88 and adjusted using Geoid 2018-CONUS. The laser data is provided in LAS format as collected as well as in cleaned XYZ files that have been best-fit positioned to match the MBES data. (Citation: Raw data)
- 2021-05-20 00:00:00 - Data were delivered to the Great Lakes Observing System (GLOS) and subsequently passed to NOAA Digital Coast for distribution. Both the cleaned text files and the raw LAS files were received. The raw LAS files did not have sufficient information to do the geometric corrections that had been done to the cleaned text files and were not further processed. The cleaned text files were converted to LAS/LAZ format using LAStools txt2las. The points are all tagged as class 2 (ground) as it is presumed that the cleaning step removed non-ground/bathymetry. This metadata record was created from the report delivered by ASI Group to GLOS. No other metadata was received. GLOS was consulted regarding any accuracy assessments or contractual spatial accuracy requirements. There were none. The accuracy is assumed to be on par with the multi-beam echo sounder data collected at the same time, but that also does not appear to have an accuracy assessment. (Citation: cleaned data)
- Data were converted from UTM zone 17 NAD83(2011) orthometric NAVD88 coordinates to NAD83(2011) ellipsoid heights in geographic coordinates. This allows the distribution through the NOAA Digital Coast Data Access Viewer, which may do further coordinate system changes.
(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
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(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.
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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.