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
This data set contains lines depicting emergency evacuation routes in the event of a tsunami, and points showing locations of airports, beaches, campgrounds, EPA facilities, heliports, historical sites, and wash overs found along 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, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Points, Lines; and NATURAL HAZARD Polygons.
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.
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.
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):
- 2015-10-01 00:00:00 - 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: 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 - Access Sites, Beaches, Boat Ramps, Marinas, Hoists, and Recreational Fishing Sites: In Washington, access sites, recreational beaches, boat ramps, marinas, and recreational fishing sites were identified through attributes in WDFW Water Access Sites database, WECY Public Beach Access Points database, and WRCO Boat facilities database. In compiling these databases, features' names and locations were compared to eliminate duplicated features. In Oregon, access sites and recreational beaches were retrieved from the OPRD Coastal Beach Access Sites database with specific ESI types distinguished through database attributes and details in Google Earth imagery. Oregon boat ramp and hoist locations were downloaded from Oregon State Marine Board (OSMB) Boating Access Sites database. Oregon marina locations were identified using both the above OPRD and OSMB databases. Airports/Heliports - Information on the locations of airports and heliports was downloaded from the National Transportation Atlas Databases maintained by the FAA. Aquaculture - Pacific oyster aquaculture sites were provided by ODFW. Campground sites - Campground sites were included for the Olympic National Park and the Makah and Quileute Tribes and were provided by NPS and OCNMS staff. USCG units - USCG station and facility locations were derived from the USCG Units dataset hosted by U.S. Geological Survey and the USACE Port and Waterway Facilities Database. Environmental Protection Agency Facility - EPA Facility (EPAF) locations represent facilities that maintain a risk management plan describing its hazards and prevention activities as required by the EPA Risk Management Plan Rule (RMP), facilities that manufacture, process, or use certain chemicals in amounts above established levels regulated by the EPA Toxic Release Inventory System (TRIS) program, facilities with permits from the National Pollutant Discharge Elimination System (NPDES), and facilities that the EPA has identified and monitors for storing certain quantities of oil (OIL). The data were provided by the EPA Facility Registration System (EPA-FRS) and EPA staff. Overlapping EPAF points were combined to a single entry where the names field is used to indicate the EPA System the facility or facilities are monitored and/or regulated.
- 2015-10-01 00:00:00 - Hatcheries: Hatchery locations for Washington and Oregon were provided by the WDFW Facilities and Structures database and the Oregon Water Right Points of Diversion database, respectively. Archaeological/Historic sites - Historic sites were depicted from sites in the NPS National Register of Historic Places (2007) for both states and from the Washington Department of Archaeology and Historic Preservation (WDAHP) Register for additional sites in Washington. Locks and dams - Dam sites in both states were mapped using the Fish Passage Barrier Inventory from WDFW and ODFW, StreamNet's Dams database, and the OWRD Dams database. In compiling these databases, feature names and locations were used to eliminate duplicated features. Ports - Major and minor port locations were compiled from the WRCO Boat Facilities database, OSMB Boating Access Sites database, OPRD Beach Access Sites database, and the USACE Port and Waterway Facilities Database. Repeated Measurement Site and Tide Gauge - Repeated measurement site (RMS) locations for marine observation sites and tide gauges were obtained through NOAA's National Data Buoy Center (NDBC) and the Center for Operational Oceanographic Products and Services (CO-OPS). Mussel Watch program RMS locations were obtained from the NOAA Chemical Impacts Team. RMS locations and site names from the Partnership for Interdisciplinary Studies of Coastal Oceans (PISCO) were provided by staff at OSU and University of California, Santa Cruz. RMS locations within OCNMS were provided through personal communication with OCNMS staff. River Miles - Locations of sequential river mile markers were derived from the USACE Waterway Mile Marker database. Subsistence Fishing - WA Pacific Coast Treaty Tribes' utilize the shoreline, marine waters, and upland areas within and surrounding Reservation lands for subsistence harvest of invertebrates, fish, birds, and other species. These areas are also of high cultural importance and sensitivity. A shoreline buffer was added along the Reservation/marine waters boundary for each of the five Pacific Coast Treaty Tribes to represent these 'culturally significant harvest areas.' This demarcation in no way implies that these areas are the only zones in which subsistence harvests take place, rather they serve as a reminder/flag to responders to contact the Treaty Tribes for more detailed information on cultural significance and harvest practices in the case of an incident. Washover - A washover, or washover fan, is a relatively flat surface on the top of a barrier spit complex that slopes gently landward. It is usually created when water forced landward by breaking waves flows across the top of the barrier spit during high spring tides or storms. This process creates a flattened-off surface along which sand is transported across the top of the spit into the standing water (lagoon) or marsh landward of the spit. The resulting deposit usually has a fan-like shape. Washover locations are represented by points that were generated by Research Planning, Inc. at a scale of 1:8,000. Water Intakes - Water intakes were derived from the WDOH Washington Drinking Water GIS data and StreamNet Dams database.
- 2015-10-01 00:00:00 - The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECONPT data layer. 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 SOCECONPT data layer 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.