Data Management Plan
GUID: gov.noaa.nmfs.inport:72862 | Published / External
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
These data identify the critical habitat designated (March 19, 2003, Federal Register Vol. 68, No. 53, Rules and Regulations) under the Endangered Species Act for the Atlantic sturgeon, Gulf subspecies (Acipenser oxyrinchus desotoi). The official NMFS critical habitat (SturgeonAtlantic_GulfSubspecies_20030319) for this sturgeon is comprised of both riverine critical habitat (line) data, Units 1 through 7, and marine/estuarine critical habitat (polygon) data, Units 8 through 14. Together the polygons and lines represent the entire final critical habitat designation.Critical habitat constitutes areas considered essential for the conservation of a listed species. These areas provide notice to the public and land managers of the importance of the areas to the conservation of this species. Special protections and/or restrictions are possible in areas where Federal funding, permits, licenses, authorizations, or actions occur or are required. The purpose of these data is to visually represent the critical habitat areas for GIS analysis and display. Omissions of river distributaries may be possible due to the extent of source data (NHD) and because a number of the smaller streams are not named and easily identifiable. Based on the legal narrative unit descriptions in the Federal Register, all distributaries are included; however, they may not be graphically represented in this dataset.
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.
W: -90.394986, E: -82.681569, N: 32.39704, S: 29.279473
W: -90.394986, E: -82.681569, N: 32.39704, S: 29.279473
W: -90.432865, E: -82.755527, N: 30.677579, S: 28.969139
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.
4. Resources
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):
Process Steps:
- 2002-11-26 00:00:00 - This data set was created using ArcView 3.2a The process steps for creating the final Gulf sturgeon riverine critical habitat units were: 1. NHD arc and route.reach files were brought into the view for each basin covered by the final critical habitat. 2. Records in the route.reach files were selected by querying on the name field. Additional unnamed records (mainly distributaries) were selected within the view using the selector tool. 3. Records in the arc files were selected using the "Select by theme..." command, choosing all records that were completely within the route.reach files. The selected records were visually checked to ensure that only river centerlines were included. 4. Using the X-Tools extension "merge themes" command, all selected records from the NHD arc files were combined into the stg_ch_final.shp file. 5. Distributaries that were not included in the NHD arc files but were included in the Federal Register maps or DeLorme state gazetteers were added to the shapefile with on-screen digitizing. 6. Using the narrative unit descriptions from the Federal Register, some arcs were spilt and parts were removed. This only occurred in units where the highest river reach included stopped at a road crossing. The roads layer used to determine this stopping point is from the ESRI Sample Data and Maps, CD Volume 5, Southern U.S., August 1999.
- 2023-12-15 00:00:00 - As described above, this species’ HUC-based critical habitat dataset was modified from the line- and polygon-based species “agency-official” NMFS critical habitat data. This HUC-based critical habitat file represents the HUC-12 watersheds (USGS Watershed Boundary Dataset; https://www.usgs.gov/national-hydrography/watershed-boundary-dataset) that intersect with the “agency-official” critical habitat line-based and polygon-based data. The data were reviewed and revised to add any additional HUC-12 watersheds that were determined to have hydrologic connectivity to the critical habitat.
(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.
Missing/invalid information:
- 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)
- 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.
Panama City, Fl
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.