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
The National Oceanic and Atmospheric Administration (NOAA) has the statutory mandate to collect hydrographic data in support of nautical chart compilation
for safe navigation and to provide background data for engineers, scientific, and other commercial and industrial activities. Hydrographic survey data
primarily consist of water depths, but may also include features (e.g. rocks, wrecks), navigation aids, shoreline identification, and bottom type information.
NOAA is responsible for archiving and distributing the source data as described in this metadata record.
This data set is located in the Mississippi Sound, between Waveland and Pass Christian. The date of collection was July 23, 2006 - June 8, 2007. The
vessels used to collect this data were the High Roller, Beach Surveyor, Arlen, and Hydro Surveyor. Soundings were collected by an Odom Hydrotrac
Echosounder. The data were originally collected in meters, referenced to MLLW. The data were later converted to feet. The tidal data were processed
using the 1983-2001 epoch.
The NOAA Office for Coastal Management (OCM) downloaded the depth data for this survey from the NGDC website (http://www.ngdc.noaa.gov/mgg/bathymetry/hydro.html)
as x,y,z points. The points were converted from MLLW depths to NAVD88 depths (using grid LAmobile02_8301;Louisiana/Mississippi - Eastern Louisiana
to Mississippi Sound, Version 02 (1983-2001);0;1983-2001) using NOAA's Vertical Datum Transformation tool,
VDatum (http://vdatum.noaa.gov/). The NAVD88 depths were then converted to ellipsoid depths (using the Geoid12a model), converted from x,y,z format
to las format and classified as 11 (OCM bathymetry). Finally, the las files were zipped to laz format.
Original contact information:
United States Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Environmental Satellite, Data,
and Information Service (NESDIS), National Geophysical Data Center (NGDC)
United States Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Environmental
Satellite, Data, and Information Service (NESDIS), National Geophysical Data Center (NGDC), National Ocean Service Hydrographic Database Manager
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):
- 2013-03-01 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the water depth data from the NGDC NOS Hydrographic Survey Data website (http://www.ngdc.noaa.gov/mgg/bathymetry/hydro.html). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1.The data were converted from MLLW depths to NAVD88 depths (using grid LAmobile02_8301;Louisiana/Mississippi - Eastern Louisiana to Mississippi Sound, Version 02 (1983-2001);0;1983-2001) using NOAA's Vertical Transformation tool, VDatum. 2.The data were converted from NAVD88 depths to ellipsoid depths using Geoid 12a model. 3.The data were converted from x,y,z format to las format. 4.The data were classified as 11 (OCM bathy). 5.The data were zipped to laz format.
(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.6. Type(s) of data
- 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.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.
This data can be obtained on-line at the following URL:
This data set is dynamically generated based on user-specified parameters.
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.