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
Critical habitat for the Western DPS of Steller sea lions includes:(a) Alaska rookeries, haulouts, and associated areas. In Alaska, all major Steller sea lion rookeries identified in Table 1 and major haulouts identified in Table 2 and associated terrestrial, air, and aquatic zones. Critical habitat includes a terrestrial zone that extends 3,000 feet (0.9 km) landward from the baseline or base point of each major rookery and major haulout in Alaska. Critical habitat includes an air zone that extends 3,000 feet (0.9 km) above the terrestrial zone of each major rookery and major haulout in Alaska, measured vertically from sea level. Critical habitat includes an aquatic zone that extends 3,000 feet (0.9 km) seaward in State and Federally managed waters from the baseline or basepoint of each major rookery and major haulout in Alaska that is east of 144Â° W. longitude. Critical habitat includes an aquatic zone that extends 20 nm (37 km) seaward in State and Federally managed waters from the baseline or basepoint of each major rookery and major haulout in Alaska that is west of 144Â° W. longitude.(b) California and Oregon rookeries and associated areas. In California and Oregon, all major Steller sea lion rookeries identified in Table 1 and associated air and aquatic zones. Critical habitat includes an air zone that extends 3,000 feet (0.9 km) above areas historically occupied by sea lions at each major rookery in California and Oregon, measured vertically from sea level. Critical habitat includes an aquatic zone that extends 3,000 feet (0.9 km) seaward in State and Federally managed waters from the baseline or basepoint of each major rookery in California and Oregon.(c) Three special aquatic foraging areas in Alaska. Three special aquatic foraging areas in Alaska, including the Shelikof Strait area, the Bogoslof area, and the Seguam Pass area.ESA timeline:Steller sea lions were originally listed (55 FR 49204, November 26, 1990) under the ESA throughout their range and critcal habitat was designated in 1993 (58 FR 45269, August 27, 1993). The critical habitat designation was amended (59 FR 30715, June 15, 1994) to correct data errors in Table 2 (Major Steller Sea Lion Haulout sites in Alaska) to Part 226 in the CFR.Steller sea lions were reclassified and listed as 2 DPSs: the Western DPS and Eastern DPS (62 FR 24345, May 5, 1997).The Eastern DPS of Steller sea lions was delisted (78 FR 66140, November 4, 2013). In the delisting final rule, NMFS clarified that the 1993 critical habitat designation remains in effect for the Western DPS of Steller sea lions.
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):
- 2007-07-31 00:00:00 - Data creation process - 2007 Alaska sites west of 144 degrees W only. SSL_226_Critical_Habitat_AK.shp (NAD_1983_Alaska_Albers) The 131 sites from PART 226 - Designated [SSL] Critical Habitat as included are 20nm buffers from either points or lines. Points are small rookeries or haulouts. Lines are larger rookery/haulouts that follow the shoreline at mean lower low water. See 226/223 for additional information. Since these points were identified before the advents of GPS units and unclear datums, some sites sit off in open water - as far as a 1/4 mile from the projected coastline. The intent of making the points and lines shapefile was to follow 226 as close as possible. When 226 could not be followed due to a line that was supposed follow the shore at mean lower low water (when the points defining the start and end point of line was in open water), the intent of the regulation was followed as closely as possible. This was done in coordiation with the AKRO PRD SSL Coordinator. SSL CH Foraging Areas overlap 20nm CH.
- 2009-04-14 00:00:00 - Data creation process 2009 - Oregon sites only. StellerSLionCritHabAll4OR.shp (NAD_1983_Albers) In the Code of Federal Regulations (50 CFR Part 226), the Appendix Table 1 to Part 226 - Major Steller Sea Lion Rookery Sites provides latitude / longitude basepoints along with the region and site names for the Steller sea lion rookeries used for critical habitat designations. However, the coordinates listed did not match up accurately with the data delineations from a number of sources for those rookery sites or the rocks or islands on which they are sited. Therefore, rather than using those basepoints to develop this data set, more accurate data was used to represent Pyramid Rock near Rogue Reef, and Long Brown Rock and Seal Rock, both in the vicinity of Orford Reef. The Pinniped Haulout data from Oregon Department of Fish and Wildlife (2007) was used to locate the rookeries themselves. The Oregon Islands National Wildlife Refuge Boundary data from U.S. Fish and Wildlife Service (2004) was used to delineate the shoreline of these islands and rocks. These 2 data sets were in agreement in that the rookeries were located within the shorelines of the islands / rocks. A 3,000 foot buffer was generated around the shorelines of these 3 islands or rocks to represent the critical habitat.
- 2016-10-14 00:00:00 - Data creation process 2016 - California sites only. StellerSLionCritHab_OR_CA.shp (GCS_North_American_1983) California sites appended to the Oregon data and shapefile renamed.
- 2020-05-14 00:00:00 - OR and CA source data converted to NMFS ESA critical habitat national standard 2020. StellerSLionCritHab_OR_CA.shp (GCS_North_American_1983) geographic transformation -> SeaLionSteller_WesternDPS_19930827 (GCS_WGS_1984). Geometry was not edited, attributes were edited. Copied metadata from source file and filled in additional metadata from final rule. Combined old fields Region, Site_Name, AreaType into new field Unit. Edited Units for clarity, to match final rule, and to provide more accurate feature labels.
- 2020-10-23 00:00:00 - Data creation process - Alaska sites east of 144 degrees W only. Southeast Alaska features were copied from Alaska Region's REST service https://alaskafisheries.noaa.gov/arcgis/rest/services/ESA_data/MapServer/6. Original source shapefile unknown.
- 2021-05-25 00:00:00 - All AK source data converted to NMFS ESA critical habitat national standard 2020.
- 2021-06-16 00:00:00 - AK data merged with OR/CA feature class (SeaLionSteller_WesternDPS_19930827) and renamed to SeaLionSteller_WesternDPS_19940615 because a technical amendment was found. Merge was necessary to follow main gdb business rule "each listed entity has a single ch feature class." Edited Unit values by filling in "Island" for "I." Edited the attributes (FRN, Publication Date, Effective Date) for 10 features that had data amended in 1994. CFR notes: the 1999 amendment (64 FR 14067, Mar. 23, 1999) only changed the CFR section number for the Steller ch designation, the 1994 technical amendment (59 FR 30716, June 15, 1994) changed haulout data in Table 2 (pg 30715 says "The technical amendment revises regulations by changing the name of one designated haulout site from Ledge Point to Gran Point and by correcting the longitude and latitude of 12 haulout sites, including Gran Point. The purpose of this action is to correct errors in the published regulations.") Note for future data development: In AK, there is a "3,000 ft landward zone" that's missing from the spatial data for Forrester Island and all the islands within the 20 nautical mile buffer. Flag: review Hazy Islands geometry.
(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
- 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.