InPort Release 5.2.0 Downtime: Thursday, May 19 @ 2:00pm - 3:30pm Eastern. InPort and its associated services will be under maintenance and unavailable for the deployment of InPort Release 5.2.0. Downtime Schedule Thursday, May 19, 2022 1:00pm - 2:30pm Eastern / 10:00am - 11:30am Pacific / 7:00am - 8:30am Hawaii Impacted Areas - InPort Website: https://www.fisheries.noaa.gov/inpor...
View All
Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
Outer Coast of Washington and Oregon 2014 ESI RESOURCE MANAGEMENT Polygons, Points
1.2. Summary description of the data:

This data set contains vector polygons depicting boundaries for commercial fishing, critical habitats, fishery areas, recreational fishing, scenic rivers and subsistence areas; vector points depict locations of aquacultures, repeated measurement sites, and water intakes found on the outer coast of Washington and Oregon.

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. The entirety of the ESI Human-Use data layers for this region consists of: PARKS-MANAGED AREAS Polygons; NAVIGATION-MARINE Points; POLITICAL-JURISDICTIONAL Polygons, Lines, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Points, Lines; and NATURAL HAZARD Polygons.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2013 to 2014
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -125.6817, E: -123.5192, N: 48.5059, S: 41.9968

This reflects the extent of all land and water features included in the overall Outer Coast of Washington and Oregon ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Map (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
ESI Program Manager
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
orr.esi@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
No information found
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
ESI Program Manager
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

  • 2015-10-01 00:00:00 - Steps 1, 2, 3, and 6 apply to vector polygons found in any of the feature data layers in the SOCECON feature dataset. Step 4 applies to linear features, and step 5 applies to point features that appear in the SOCECON feature dataset. The sources cited above apply specifically to the polygons found in the PARKS-MANAGED AREAS data layer. The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. Sources of data used to depict human-use resources in this data layer include expert knowledge from Washington Treaty Tribes: Hoh Tribe, Makah Tribe, Quileute Tribe, Quinault Tribe, Shoalwater Bay Tribe; and digital datasets provided by the U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Fish and Wildlife Service (USFWS), NOAA, National Park Service (NPS), U.S. Census Bureau (USCB), U.S. Forest Service (USFS), U.S. Bureau of Land Management (BLM), Washington Department of Ecology (WECY), Washington Department of Transportation (WDOT), Washington Department of Health (WDOH), Washington Department of Fish and Wildlife (WDFW), Washington Department of Natural Resources (WDNR), Oregon Department of Fish and Wildlife (ODFW), Oregon Parks and Recreation Department (OPRD), Portland State University - Institute of Natural Resources (PSU-INR), Oregon Department of Agriculture (ODA) and Oregon Department of Geology and Mineral Institutes (DOGAMI).
  • 2015-10-01 00:00:00 - Army Corps of Engineers - USACE regulatory boundaries were downloaded from the USACE geoplatform. Coast Guard - USCG district boundaries were downloaded from the U.S. Geological Survey (USGS) ScienceBase catalog. Commercial fishing - Commercial fishing areas show ODA Commercial Shellfish Management Areas (CSMA) where shellfishing is approved, approved conditionally, or unclassified. Critical Habitat - Designated Critical Habitat was mapped for chum salmon, Chinook salmon, Coho salmon, Pacific euchalon, sockeye salmon, steelhead salmon, leatherback sea turtle, green sturgeon with data downloaded from NOAA Fisheries. Bull trout, Steller sea lion, killer whale, western snowy plover, marbled murrelet, northern spotted owl, streaked horned lark, and Oregon silverspot butterfly were mapped with data downloaded through the USFWS Critical Habitat Portal. Critical Habitat for mammals, birds, and insects were mapped "as is". Fishery Area - Fishery areas provided by WDOH and ODFW represent recreational and commercial shellfishing areas where shellfishing is either permitted, conditionally permitted, or unclassified. Salmon Catch and Management Reporting Areas were provided by WDFW. Recreational shellfishing beaches in Washington designated with approved, approved conditionally, or unclassified shellfishing were selected and buffered with a 50 m onshore/offshore buffer. Usual and Accustomed Fishing Areas were mapped for Washington Treaty Tribes when boundaries of these marine areas were made available by the Tribes.
  • 2015-10-01 00:00:00 - Tribal Lands - Oregon tribal lands were downloaded from the USCB MAF/TIGER geographic database. Boundaries for tribal lands in Washington were downloaded from the WDOT. The Hoh Tribe provided their own digital reservation boundaries. Management Areas - Boundaries for Areas of Critical Environmental Concern were downloaded from BLM. Wilderness Areas were obtained from the USFS Automated Lands Program. Habitat Areas of Particular Concern (HAPC) show Groundfish HAPC for all Washington state waters (3 nm), canopy kelp, rocky reefs, and seagrass. HAPCs were downloaded from NOAA's National Marine Protected Areas Center (NMPAC) and merged into a single feature. Wildlife Areas and Natural Conservation Areas and Area Preserves were provided by the WDNR. Marine Gardens, Conservation Areas were downloaded from PSU-INR. Research Reserves, Habitat Refuges, and Shellfish Preserves in Oregon were provided by USGS Pacific Coast Fisheries GIS database and originally published by NOAA, NMPAC. Marine Reserves, Marine Protected Areas, and Seabird Protection Areas were downloaded from the OregonInfo Data Catalog. OPRD supplied the boundaries for Western Snowy Plover Recovery Areas. Marine Sanctuary - The Olympic Coast National Marine Sanctuary (OCNMS) boundary was provided by NOAA's National Marine Sanctuaries Program. National Estuarine Research Reserve (NERR) - Boundary data was provided by the South Slough NERR System. National Park - Boundaries for the Lewis and Clark National Historical Park were used from the National Park boundaries dataset downloaded from Data.gov. Olympic National Park boundaries were provided by Olympic National Park staff. Nature Conservancy - Nature Conservancy lands were downloaded from PSU-INR and USGS Gap Analysis Program for Oregon and Washington, respectively. Repeated Measurement Site - Tso'yess Beach and Greenville Beach intertidal repeated measurement sites were mapped as 50 m onshore/offshore buffer of the ESI shoreline between north/south coordinates provided by OCNMS staff. Scenic River - Boundaries for Wild and Scenic Rivers were obtained from USFS GeoData catalog. Subsistence -culturally significant harvest areas for shoreline associated resources were mapped along shorelines where WA Treaty Tribe reservation boundaries intersected with the ocean. Tsunami Inundation Areas - Data were provided by WDNR and DOGAMI and represent the maximum extent of possible tsunami inundation from various tsunami model scenarios. Wildlife Refuge - USFWS National Wildlife Refuge (NWR) data were downloaded from the USFWS National Cadastral Data. Oregon Islands NWR and Flattery Rocks NWR were edited to include those emergent rocks reflected in the updated ESI shoreline.
  • 2015-10-01 00:00:00 - Sources of data used to depict the linear features in the SOCECON feature dataset include: 1) Washington Department of Natural Resources (WDNR), Division of Geology and Earth Resources for tsunami evacuation routes; and 2) Environmental Systems Research Institute (ESRI) for U.S. State boundaries.
  • 2015-10-01 00:00:00 - Sources of the data used to create the point features in the SOCECON dataset include: 1) expert knowledge from the National Park Service (NPS), NOAA Olympic Coast National Marine Sanctuary (OCNMS), Oregon Department of Fish and Wildlife (ODFW), the Hoh Tribe, the Makah Tribe, the Quileute Tribe, the Quinault Tribe, the Shoalwater Bay Tribe; and 2) datasets provided by the Federal Aviation Administration (FAA), U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Fish and Wildlife Service (USFWS), NOAA, U.S. Environmental Protection Agency (EPA), NPS, StreamNet, Washington Department of Ecology (WECY), Washington Department of Archaeology and Historic Preservation (WDAHP), Washington Department of Health (WDOH), Washington Recreation and Conservation Office (WRCO), Washington Department of Fish and Wildlife (WDFW), Washington Department of Natural Resources (WDNR), Oregon Parks and Recreation Department (OPRD), Oregon State Marine Board (OSMB), Oregon Water Resources Department (OWRD), and Oregon State University (OSU).
  • 2015-10-01 00:00:00 - The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCEON data layers. 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:24,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. See the Lineage section for additional information on the type of source data for this data layer. 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 SOCECON data are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
Office of Response and Restoration (ORR)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

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).

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office of Response and Restoration - Seattle, WA
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank