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
Raw XTF files. Sonar data were collected November 6 to December 15, 2009, in the estuary north from Saugerties to Troy. Data Collection and Processing: The interferometric system used to measure acoustic reflectivity, provided a quantitative measure of reflectivity for every square meter of the survey area. Fugro's system measured and recorded acoustic reflectivity that has a high dynamic range such that the full range of reflectivity's encountered in the estuary environment can be recorded while maintaining a constant gain setting on the system receiver. Reflectivity data from the GeoSwath was used to produce a normalized as well as a classified image of the bottom. Additionally, Fugro provided slope, aspect and hillshade models as additional acoustic parameters. Backscatter data processing was completed with CARIS 7.0. Raw XTF files were created by converting Hypack format (*.HSX) into Triton format (*.XTF) using Hypack 2009a.
Original contact information:
Contact Name: John Ladd
Contact Org: Hudson River National Estuarine Research Reserve, NYS DEC
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):
- 2010-01-01 00:00:00 - For seabed classification, the industry standard is to not change gains during a survey. Test lines were run to determine the optimum gain settings for the actual bottom backscatter values. Selected gain settings remained unchanged over the course of the project. The following parameters were used when collecting the data - GeoSwath Transmit Power = 2, GeoSwath Pulse Length = 2, GeoSwath SSS Frequency = 250kHZ
- 2010-01-01 00:00:00 - Using a data converter in Hypack 2009a (HSX2XTF), raw side scan sonar files were converted from Hypack's HSX format to Triton's XTF format.
- 2010-01-01 00:00:00 - For export of .tif files. Once the side scan was cleaned and edited, this non-normalized data was converted into a series of GeoTIFF mosaics. Mosaics are geographically referenced, and presented in one meter resolution. For ease of integration with previous benthic mapping products, all GeoTIFF images (including those listed below) were broken into panels coinciding with the boundaries and naming convention of the Hudson River Survey Index. With Caris 7.0 Mosaic Editor, the data was normalized by applying Auto TVG (Time-Varying Gain), which applies gains to individual pings, and AVG (Angle-Varying Gain) utilizing the Trend Method. AVG was used to normalize mean angular intensities with a moving average filter applied to a window of pings. According to Caris, the Trend Method defines how to weigh the samples when doing the AVG. Backscatter curves can usually be modeled with a line for those samples between 30 and 60 degrees from nadir. This method will do a line of best fit for data between 30 and 60 degrees and give a high weight to those samples that fit the line the closest. Samples outside this 30-60 degree range will all be weighted equally. Once side scan data was normalized, GeoBars (Geo-referenced Backscatter Raster) were created. From the GeoBars, the data were exported into GeoTIFF images portraying the normalized orthorectified mosaics in one meter resolution. On Charts 5a-5c, the normalized orthorectified mosaics created from the current sonar reflectivity dataset were laid over top of the data previously collected by SUNY.
(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.