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
Hudson River Estuary Shallow Water Surveys. Subbottom Profile Points. Subbottom data was collected November 5 to December 15, 2009, in the estuary north from Saugerties to Troy.
Data Collection and Processing: Subbottom Data - Fugro utilized the EdgeTech SB216 Chirp subbottom profiler system for seismic data collection. This system was operated using a swept frequency range of 2-16 KHz, maximizing subsurface resolution within the very shallow near-surface material (1- 5 m beneath seafloor).
Subbottom data was processed and interpreted using Discover and SMT Kingdom software. The intent of the processing was to provide the NYSDEC with SEG-Y files that were properly filtered and spatially oriented to allow for near-surface interpretation of sediments in the Hudson River. Processing steps for the subbottom data included swell filtering to compensate for sea conditions during survey operations, compiling correct shotpoint navigation, and adjusting data gains for optimal interpretation. Subbottom data was used to assist in selecting sediment sampling locations.
Points were created every 300th trace (approximately 100 meters).
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-04-28 00:00:00 - Ship GPS data were acquired using a Trimble AG332 GPS receiver, operating at 1 Hz. The GPS position of the sub bottom fish was calculated in the Discover software on the XStar topside processor by applying a layback (the offset of the towfish from the GPS antenna). The raw GPS data were viewed in ArcGIS for any outliers, and the processed data were applied to the SEGY files in Kingdom. Final corrected positions are accurate to <+/- 1 meter. For each line, every 300th trace was extracted from the *.sgy file along with the first and last trace to create the SBP_Points shapefile. The position recorded in the header of the SEG-Y file comes from the GPS navigation system interfaced to the sub bottom profiler computer, whereas the time comes from the sub bottom profiler computer clock. It has been determined that the time of the sub bottom profiler PC clock was offset from GPS time (as collected by the side scan sonar system). The positions found in the SEG-Y file headers and the SBP_points attribute tables represent the position of the subbottom profiler source at the GPS times for that position found in the XTF headers and the Sidescan Sonar ping shape file attribute table. Users should not use time but rather geographic positions to compare the sub bottom profile and side scan sonar datasets.
- 2010-01-01 00:00:00 - The point shapefile was brought into ArcGIS along with the subbottom tracklines file. The data was qc'd for accuracy. A spatial join was created between the subbottom point shapefile and the SSS trackline shapefile, so that the user can determine the corresponding sidescan .xtf file to a particular SBP point. If a side scan sonar line was not run concurrently with the subbottom line, the SSS_Line field in the attribute table was filled with 'xxx'. In the case where the subbottom data may have collected for a longer distance than the side scan data, the SSS_Line field may be populated with 'xxx'.
(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.