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
This dataset represents proposed modifications to mandatory speed restriction areas (50 CFR Part 224.105) established to reduce the threat of vessel collisions with endangered North Atlantic right whales. Since the implementation of speed restrictions in 2008, the distribution of right whales has shifted, resulting in a misalignment between areas of high vessel strike risk and the spatial and temporal bounds of the mandatory speed restriction areas. To maximize the reduction of vessel strike risk, the National Marine Fisheries Service (NMFS) have proposed modifications to the existing speed restriction areas using a coast-wide vessel strike mortality risk model, North Atlantic right whale visual sighting and acoustic detection data, recent vessel traffic Automatic Identification System (AIS) data, and information on other relevant planned ocean activities, including offshore wind development. While the offshore boundaries of the proposed speed restriction areas are fixed, the majority of the coastal boundary is represented by shoreline data. Because shorelines are highly dynamic, the dataset used to represent the shoreline, while contemporary, will likely become quickly outdated in a number of locations. In addition, GIS projection and topology functions can often change or generalize coordinates. For these reasons, the spatial features contained in this dataset are considered to be approximate representations and are NOT an OFFICIAL record for the exact regulated area boundaries.
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):
- 2022-07-29 00:00:00 - North Atlantic right whale visual sighting and acoustic detection data, recent vessel traffic Automatic Identification System (AIS) data, and information on other relevant planned ocean activities, including offshore wind development were used to identify offshore and coastal control points to define the offshore boundary and coastal divisions for proposed speed restriction areas.
- 2022-08-10 00:00:00 - COLREGS Demarcation Lines and NOAA NGS Continually Updated Shoreline Product (CUSP) line features were merged into a single dataset.
- 2022-08-10 00:00:00 - Linear features in the merged COLREGS Demarcation Lines and NOAA NGS Continually Updated Shoreline Product (CUSP) feature class were edited to remove out-of-habitat features (e.g. inland waters, barrier islands, etc.) or features that were determined to introduce an unnecessary degree of complexity to the boundaries (e.g. seawalls, jetties, groins, offshore breakwaters, etc.). Hand digitized features guided by ESRIâs World Imagery Basemap were added to connect shoreline features to COLREGS features where the speed zone boundaries transitioned between shoreline and COLREGS linear features and to bridge gaps where shoreline data was unavailable or where breaks in shoreline features occurred due to the removal of out-of-habitat waters. The linear features in this dataset were merged to create a single, contiguous coastal boundary for the regulated portion of the U.S. Atlantic seaboard.
- 2022-08-11 00:00:00 - Coordinate values belonging to the offshore and coastal control points to define the offshore boundary and coastal divisions for proposed speed restriction areas were converted from degrees-minutes-seconds to decimal degrees and used to create a line feature class delineating the offshore boundaries and divisions between the proposed speed restriction areas.
- 2022-08-12 00:00:00 - Polygons were created using the linear feature class representing the offshore boundaries and proposed area divisions and the feature class containing the contiguous coastal boundary for the regulated portion of the U.S. Atlantic seaboard.
(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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 1.7. Data collection method(s)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 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.2. Data storage facility prior to being sent to an archive facility
- 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.
Silver Spring, MD
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.