Data Management Plan (Deprecated) | ID: 24279 | Multibeam Mapping of the South Atlantic Bight: South Carolina 2005, a Proposed MPA on the Continental Shelf

Deprecated Version
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:

Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:

Multibeam Mapping of the South Atlantic Bight: South Carolina 2005, a Proposed MPA on the Continental Shelf

Taken From: Item Identification | Title

1.2. Summary description of the data:

The NOAA Fisheries laboratory in Panama City, Florida coordinated an acoustic survey at the new proposed Marine Protected Areas in the South Atlantic Bight area June 20- July 7th, 2005. This metadata record is the parent record for the multi-beam echosounder (MBES) survey at the South Carolina A proposed MPA, which includes the following products: 1) XYZ ascii table created from the grid, 2) colored coded shaded geotiffs from the grid, 3) backscatter mosaic, 4) XYA (amplitude) ascii table created from the mosaic, and 5) geotif of backscatter draped on the bathymetric grid. All products are available contacting the distributor. Some data sets are also posted on NOAA's Coral Reef Information System (CoRIS) at www.coris.noaa.gov. Another product that will not be distributed, but will be used as input to habitat classification software (QTC MultiView (website)), are raw data files logged to disk using the Simrad EM3002 MBES data acquisition software. These raw files contain packets of information (depth soundings, navigation, attitude, sound velocity profiles, UTC time) that the acquisition software logged sequentially in time. The raw data format is available from Kongsberg-Simrad (website). The MBES system was provided by Seafloor Systems Inc. and the support vessel was UNCW's 70-ft. R/V Cape Fear. This survey is part of an on-going partnership effort funded by the NOAA Coral Reef Conservation Program (CRCP). This survey was funded by a CRCP grant to Andrew David, NOAA Fisheries - Panama City, and Andrew Shepard, NURC/UNCW (The National Oceanographic and Atmospheric Administration's Undersea Research Center at the University of North Carolina at Wilmington). In addition to partners above, other partners include UNCW's Spatial Analysis Lab, US Geological Survey, and the S. Atlantic fishery Management Council.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.

1.3. Is this a one-time data collection, or an ongoing series of measurements?

One-time data collection

Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.

1.4. Actual or planned temporal coverage of the data:

2005-06-28 to 2005-07-07

Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.

1.5. Actual or planned geographic coverage of the data:

W: -78, E: -77, N: 34, S: 32

South Atlantic Bight: South Carolina

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.

1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)

Image (digital)

Taken From: Data Set Information | Data Presentation Form

1.7. Data collection method(s):
(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.)

No information found

Taken From: Acquisition Information | Instruments, Platforms

1.8. If data are from a NOAA Observing System of Record, indicate name of system:

Always left blank due to field exemption

1.8.1. If data are from another observing system, please specify:

Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:

Andrew David

Taken From: Support Roles (Metadata Contact) | Person
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.

2.2. Title:

Metadata Contact

Always listed as "Metadata Contact"

2.3. Affiliation or facility:

Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.

2.4. E-mail address:

andy.david@noaa.gov

Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.

2.5. Phone number:

850-234-6541 x208

Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:

Andrew David

Taken From: Support Roles (Data Steward) | Person
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.

3.2. Position Title:

Data Steward

Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?

No

Taken From: Data Management | Have resources for management of these data been identified?

4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

Unknown

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

2005-07-07 00:00:00 - The bathymetry and backscatter data were collected along a continuous swath perpendicular to the direction of the ship using a Simrad EM 3002 multibeam sonar system. The data were collected in the raw format .all Simrad file. The data are cleaned of bad navigation and depth readings in CARIS HIPS 5.4 swath editor. The depth readings are gridded into a common grid. The gridded data are converted to an XYZ ASCII format file (Longitude, Latitude, Attribute). The raw backscatter was saved during the survey. The multi-beam system was mated to a Differential GPS unit, APPLANIX POS/MV (quantified heave, pitch, roll, and yaw heading). HYPACK navigation system was used to maintain vessel course throughout the survey. Sensor data were compiled in SIS Shipboard Data Acquisition and Image Processing System and initially logged to .all Simrad data files. Files were post-processed using CARIS HIPS 5.4 software to remove outliers, correct for sound velocity and tidal stage. HIPS was also used to mosaic backscatter and produce XYA files.

Taken From: Lineage | Lineage Statement, Process Steps (Process Date/Time, Source Citation Title, Description)

5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:

Always left blank

5.2. Quality control procedures employed
(describe or provide URL of description):

None listed.

Taken From: Data Quality | Quality Control Procedures Employed

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.

6.1. Does metadata comply with EDMC Data Documentation directive?

No

Notes: All required DMP fields must be populated and valid to comply with the directive.

6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

1.7. Data collection method(s)
7.2. Name of organization of facility providing data access

Notes: Required DMP fields that are not populated or invalid are listed here.

6.2. Name of organization or facility providing metadata hosting:

NMFS Office of Science and Technology

Always listed as "NMFS Office of Science and Technology"

6.2.1. If service is needed for metadata hosting, please indicate:

Always left blank

6.3. URL of metadata folder or data catalog, if known:

https://www.fisheries.noaa.gov/inport/item/24279

Always listed as the URL to the InPort Data Set record

6.4. Process for producing and maintaining metadata
(describe or provide URL of description):

Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf

Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?

No

Taken From: Data Management | Do these data comply with the Data Access directive?

7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?

No

Taken From: Data Management | Is access to the data limited based on an approved waiver?

7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

There are no constraints for use of geotiff files, which are available online and from the P.O.C.

Taken From: Access Info | Data Access Constraints

7.2. Name of organization of facility providing data access:

No information found

Taken From: Support Roles (Distributor) | Organization
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.

7.2.1. If data hosting service is needed, please indicate:

Data hosting service is needed

Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.

7.2.2. URL of data access service, if known:

http://data.nodc.noaa.gov/coris/data/NOAA/nmfs/sefsc/bathymetry/SAB/southcarolina/bathymetry2005
http://data.nodc.noaa.gov/coris/data/NOAA/nmfs/sefsc/bathymetry/SAB/southcarolina/bathymetry2005

Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.

7.3. Data access methods or services offered:

Follow this URL:

http://data.nodc.noaa.gov/coris/data/NOAA/nmfs/sefsc/bathymetry/SAB/southcarolina/bathymetry2005

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

unknown

Taken From: Data Management | Approximate delay between data collection and dissemination

7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

Taken From: Data Management | If delay is longer than latency of automated processing, indicate under what authority data access is delayed
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.

8.1. Actual or planned long-term data archive location:
(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)

TO_BE_DETERMINED

Taken From: Data Management | Actual or planned long-term data archive location

8.1.1. If World Data Center or Other, specify:

Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.

8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:

Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.

8.2. Data storage facility prior to being sent to an archive facility (if any):

Panama City Laboratory - Panama City, FL

Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.

8.3. Approximate delay between data collection and submission to an archive facility:

unknown

Taken From: Data Management | 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?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

Data is located on a personal computer.

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank