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 depicts the river lengths along which Critical Habitat has been designated (82 FR 39160, August 17, 2017) for the Chesapeake Bay distinct population segment (DPS) of Atlantic Sturgeon. Critical habitat includes all of the river along the specified segment, from the ordinary high water mark of one riverbank to the ordinary high water mark of the opposing riverbank of the mainstem of the river, to the downstream limit at the bank-to-bank transect of the specified segment. For clarification of the critical habitat definition, please refer to the maps and narrative descriptions in the CFR. It is a product of the NOAA Fisheries Serviceâs Greater Atlantic Regional Fisheries Office (GARFO). This dataset includes boundaries for the following Regulated Areas: - Critical Habitat for Chesapeake Bay Distinct Population Segment of Atlantic Sturgeon: Nanticoke River, Potomac River, Rappahannock River, York River, and James River. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate representations and are NOT an OFFICIAL record for the exact Area boundaries. For information on the official legal definition refer to the Use Constraints metadata section.
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):
- [Get Definition Text] The spatial definition (text and map) for Critical Habitat was copied from the Federal Register.
- 2017-01-01 00:00:00 - [Check Geometry] The ESRI ArcGIS Check Geometry tool was run on the feature class to identify any geometry problems. If problems were encountered, they were reviewed and corrected.
- 2017-01-01 00:00:00 - [Policy Review] The Critical Habitat spatial definition text, shapefile geometry and attribute values were reviewed with policy staff to verify that the feature class accurately depicted and described the intended boundaries.
- 2017-01-01 00:00:00 - [Downstream Limits] Some downstream limits to Critical Habitat are located where river mouths are ambiguous, or where rivers flow into other water bodies not included in the Critical Habitat designation. To clarify the downstream limits of Critical Habitat we delineated bank-to-bank transects at the end of each river length feature, in consultation with NOAA biologists.
- 2017-01-01 00:00:00 - [Metadata] A GARFO Regulated Area shapefile metadata template was developed using the EPA Metadata Editor v3.2. This template was applied and customized to reflect the specific characteristics of the given shapefile. The metadata was validated for FGDC CSDGM compliance.
- 2017-01-01 00:00:00 - [Final Review] The shapefile was reviewed by members of the GARFO GIS Committee, policy experts from the GARFO Division responsible for the Regulated Area, and General Counsel, according to the GARFO GIS Data Distribution Policy.
- 2017-01-01 00:00:00 - [Extract features] To generate the Critical Habitat river lengths, we extracted relevant river lines segments from the NHDFlowline feature class. Flowlines through relevant major tributaries or bays/estuaries were also included. We merged flowlines into a single feature for each Critical Habitat unit. We used the location of NID dams and Major Highways to clip the features at the appropriate upstream limits. We clipped flowline features at their downstream limit based on consultation with NOAA biologists. The lines represent the length of the river along which bank-to-bank Critical Habitat was designated.
- 2017-09-28 00:00:00 - [Publication] The shapefile, with accompanying metadata, was uploaded for public download on the NOAA NMFS GARFO GIS website.
(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)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.
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.