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 feature classes reside within the BIOLOGY Feature Data Set of the St Lawrence River - 2021 ESI Geodatabase. It contains vector polygons and points representing FISH data for the Great Lakes St Lawrence River.
The study area includes the St. Lawrence River from the headwaters of Lake Ontario, northeast to the western portion of L'Ile-Saint-Regis Island (CA). These data sets contain sensitive biological resource data for freshwater and anadromous fish species in the St. Lawrence River. Vector polygons in this data set represent fish distribution, concentration areas, and spawning areas. Vector points in this data set represent fish spawning and nursery areas.
Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described in Entity Attribute Overview below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for the Great Lakes St. Lawrence River.
As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
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.
Bounding box for the Great Lakes St. Lawrence River study region.
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):
- 2021-07-01 00:00:00 - Four main sources of data were used to depict fish distribution and seasonality for these data layers: 1) personal interviews with resource experts from the New York State Department of Environmental Conservation (NYSDEC), U.S. Fish and Wildlife Service (USFWS), and the State University of New York College of Environmental Science and Forestry (SUNY ESF); 2) hardcopy maps from NYSDEC and New York Power Authority (NYPA); 3) vector digital data from New York Natural Heritage Program (NY NHP) and New York State Department of State; and 4) vector and tabular digital data from Great Lakes Aquatic Habitat Framework (GLAHF) and SUNY ESF. Fish species depicted in this atlas include species of conservation interest, or species of commercial, recreational, or ecological importance. Fish polygons and spawning points were created based on digital data, publications, and expert opinion provided by resource experts at NYSDEC and USFWS.
- 2021-07-01 00:00:00 - General distributions – Fish general distributions were mapped using expert knowledge collected during workshops. Species included were determined by the experts in the study area. The main stem of the St. Lawrence River was divided into three segments for fish general distributions: Thousand Islands to Brockville, Brockville to Lake St. Lawrence, and Lake St. Lawrence. These divisions are often used by local resource managers as well. Concentration areas and tributaries – Concentrations areas of various species were mapped using expert knowledge collected in workshops and from the New York Department of State Significant Coastal Fish and Wildlife Habitats dataset. Experts also provided species lists and concentration areas present in the tributaries of the St. Lawrence River.
- 2021-07-01 00:00:00 - Spawning locations – All fish that spawn in the study area were mapped with spawning months included in the seasonalities for all locations in the study area, per expert recommendation. Fish spawning can occur throughout the system, and different species utilize different habitats for spawning. The user should refer to the table in the atlas introduction that shows the spawning habitat(s) for each mapped species. Specific spawning locations were not available for many of the mapped species, so use of this table in conjunction with the spatial data informs the user of the areas used for spawning by each species. Spawning months in this atlas include months when any sensitive reproductive life history stage is present (spawning, eggs, and larvae). Point locations of spawning and nursery sites for muskellunge, northern pike, and smallmouth bass were provided by John Farrell (SUNY ESF). Additional spawning point locations for burbot, cisco, lake trout, lake whitefish, smallmouth bass, walleye, and yellow perch were provided by Great Lakes Aquatic Habitat Framework (GLAHF). Spawning months in this atlas include months when any sensitive reproductive life history stage is present (spawning, eggs, and larvae).
- 2021-07-01 00:00:00 - Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:40,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the FISH & FISHPT data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
(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)
- 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.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
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.