Data Management Plan
GUID: gov.noaa.nmfs.inport:65369 | 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
Critical habitat in bays and estuaries includes tidally influenced areas as defined by the elevation of mean higher high water (MHHW). The boundary between coastal marine areas and bays and estuaries is delineated by the COLREGS lines (33 CFR 80). Critical habitat in coastal marine areas is defined by the zone between the 60 fathom (fm) depth bathymetry line and the line on shore reached by mean lower low water (MLLW), or to the COLREGS lines.No areas were deemed ineligible for designation. No unoccupied areas were designated. 14 areas based on economic impacts and 5 areas based on national security impacts were excluded from this critical habitat designation and clipped out of the data. The following tribal lands were excluded from this designation, but were not clipped out of the data:(1) Cachil DeHe Band of Wintun Indians of the Colusa Indian Community, California(2) Cher-Ae Heights Trinidad Rancheria, California(3) Confederated Tribes of the Coos, Lower Umpqua, and Siuslaw, Oregon(4) Coquille Indian Tribe, Oregon(5) Hoh Tribe, Washington(6) Jamestown S'Klallam Tribe, Washington(7) Lower Elwha Tribe, Washington(8) Makah Tribe, Washington(9) Quileute Tribe, Washington(10) Quinault Tribe, Washington(11) Shoalwater Bay Tribe, Washington(12) Wiyot Tribe, California(13) Yurok Tribe, California
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):
- 2009-01-20 00:00:00 - Marine polygons were created using data from NOAA Office of Coast Survey for the shoreline along with Terra Logic bathymetry lines at the 110 meter depth contour. The final rule states that the 60 fathom depth line should be considered the most westerly boundary but the GIS producers were not aware of the availability of a reliable Pacific Coast continous 60 fathom bathymetry line at the time these data were created. Because the difference between the 110 meter depth and the 60 fathom depth is a minimal .1487 fathoms or .272 meters, the GIS producers along with the NMFS Critical Habitat Review Team (CHRT) decided for GIS purposes only to use the 110 meter bathymetric contour line. The eastern boundary was created using the NOAA Electronic Nautical Charts (ENC) Shoreline Feature Class which represent the Mean Lower Low Water (MLLW) for the Pacific Coast. One continuous MLLW shoreline was created by merging the individual charts shoreline data. ENCs used to create the MLLW are listed below: US3CA14M US3CA15M US3CA52M US3CA69M US3CA70M US3CA85M US3OR01M US3OR02M US3OR03M US3WA01M US3WA02M US3WA03M Only the mainland shoreline was used; islands were removed. The marine zone was clipped at numerous west coast estuary mouths to create a marine zone-only layer. Estuaries considered for critical habitat designation were clipped out based on COLREG lines as found on NOAA nautical charts. The coastal bathymetry polygons did not extend to Strait of Juan de Fuca. To create a polygon for that area, a 10m DEM was used to create the 110m bathymetry line. Using the RasterToPolygon tool, a polygon was created for the area between the coastline and the 110m-depth bathymetry line. The coastline to 110m marine zone for the Strait of Juan de Fuca was merged with the 110m marine zone for the rest of the Pacific Coast to create a single polygon describing marine waters within 110m depth from Monterey Bay, California, north to Cape Flattery, Washington, and east to include areas in the Strait of Juan de Fuca, Washington, to the U.S.-Canada boundary. Edited the resulting polygon by dividing it into specific areas as defined by NMFS biologists developing the critical habitat designation.
- 2009-10-05 00:00:00 - Yolo and Sutter Bypass boundaries were modified according to where members of the NMFS critical habitat review team determined green sturgeon to be present.
- 2009-10-05 00:00:00 - Marsh areas were created using aerial imagery as a basemap and performing on-screen digitizing of polygons.
- 2009-10-05 00:00:00 - Navy areas excluded from designation were created through the input of coordinates, that were provided by the Department of Defense, and clipped out. Polygon filename: GreenSturgeonCHDepartmentofDefense.shp (1) Mare Island U.S. Army Reserve Center, San Pablo Bay, CA; (2) Strait of Juan de Fuca naval air-to-surface weapon range, restricted area, WA; (3) Strait of Juan de Fuca and Whidbey Island naval restricted area, WA; (4) Admiralty Inlet naval restricted area, Strait of Juan de Fuca, WA; and (5) Navy 3 operating area, Strait of Juan de Fuca, WA.
- 2009-10-05 00:00:00 - Estuary polygons were selected and exported from NOAA's Medium resolution digital Vector Pacific Coast Shoreline. They represent the best available information to depict the specific estuarine areas occupied by the Southern DPS of green sturgeon. Estuary polygons were modified to depict areas downstream from the head of tide (where determinable). In the case where green sturgeon presence extended further upstream than where the estuary boundary was depicted, polyline data were used to depict head of tide and stream lines to the extent of tidal influence. The original estuary polygons were modified as needed to align the estuary-ocean boundary consistent with the Pacific Coast COLREG Demarcation lines. Head of tide extents in estuaries were compiled (originally as point data - GreenSturgeonCHHeadofTide.shp) from visual inspection of 1:24,000 USGS topographic maps, aerial photographs, as well as various sources. For a listing of these sources and additional information regarding each of the head of tide locations and the sources or rationale for each point, see Appendix A in the final biological report for the final green sturgeon critical habitat rule (NMFS. 2009. Designation of Critical Habitat for the Threatened Southern Distinct Population Segment of North American Green Sturgeon: Final Biological Report, prepared by the National Marine Fisheries Service, Southwest Region, Long Beach, CA).
- 2020-05-21 00:00:00 - 2009 source data converted to NMFS ESA critical habitat national standard 2020. Geometry was merged but boundaries were not edited. Attributes were edited. Metadata was compiled from 7 source files: 5 polygon files GreenSturgeonCHBypassAreas.shp GreenSturgeonCHEstuaries.shp GreenSturgeonCHMarineCoastalZones.shp GreenSturgeonCHMarshAreas.shp GreenSturgeonCHDepartmentofDefense.shp 1 point file GreenSturgeonCHHeadofTide.shp 1 line file GreenSturgeonCHTribalExclusions.shp
(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.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.