Outer Coast of Washington and Oregon 2014 ESIL (Environmental Sensitivity Index Shoreline Types - Lines)

This data set contains vector lines representing the shoreline and coastal habitats of the Outer Coast of Washington and Oregon classified according to the Environmental Sensitivity Index (ESI) classification system. This data set comprises a portion of the ESI data for Outer Coast of Washington and Oregon. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. See also the ESIP data layer, part of the larger Outer Coast of Washington and Oregon ESI database, for additional ESI information.

The ESI data were collected, mapped, and digitized to provide environmental data for oil spill planning and response. The Clean Water Act with amendments by the Oil Pollution Act of 1990 requires response plans for immediate and effective protection of sensitive resources.

2197

Prepared by Research Planning, Inc., Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Emergency Response Division, Seattle, Washington.

Data content is considered static once published. However, if issues with the Geodatabase linkages or table contents are identified, the Geodatabase and/or the associated Map Document may be updated. Assure most current data is being used by downloading from https://response.restoration.noaa.gov/esi_download and/or comparing modification dates provided at this site.

In addition to the geographic data layers, one relational attribute or data table, SOURCES, is used to store the source data information in the ESI data structure. The geographic data layer containing resource information (in this case, ESIL) is linked to the SOURCES table using the SOURCE_ID. The entity-relationship diagram describes relationships between attribute tables in the ESI data structure.

NOAA ESI Guidelines

Although these data have been processed and used successfully on a computer system at the National Oceanic and Atmospheric Administration, no warranty, expressed or implied, is made by NOAA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. NOAA warrants the delivery of this product in computer-readable format, and will offer a replacement copy of the product when the product is determined unreadable by computer input peripherals, or when the physical medium is delivered in damaged condition.

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

None

DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES. Management boundaries are not to be considered legal boundaries. Edges may have been altered for cartographic processes. Note that the ESI database should not be used to the exclusion of other pertinent data or information held by state or federal agencies or other organizations. Likewise, information contained in the database cannot be used in place of consultations with environmental, natural resource, and cultural resource agencies, or in place of field surveys. Recognize that the information contained in the ESI database represents known concentration areas or occurrences of natural, cultural, and human-use resources, but does not necessarily represent the full distribution or range of each species or resource. This is particularly important to recognize when considering potential impacts to protected resources, such as endangered species, wetlands, etc. Besides the above warnings, there are no use constraints on these data. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data.

The software packages used to develop the atlas are Environmental Systems Research Institute's ArcGIS for Desktop 10.2(R) and SQL SERVER(R) (version 2005). The hardware configuration is PC's with Windows Operating System 7.

A multi-stage error checking process is used to verify both attribute accuracy and logical consistency throughout data production. The process includes a standardized data entry methodology, data review by in-house and external resource experts, a final Quality Assurance/Quality Control (QA/QC) process, and multiple automated logical consistency checks. Quantitative data (such as densities, counts, abundances, or concentrations) provided by resource experts for inclusion in the data set may vary widely in attribute accuracy, depending upon the methodology used to collect and compile such data. For a more detailed evaluation of source data attribute accuracy, contact the sources listed in the Lineage section.

The spatial location of the ESI shoreline was developed from pre-existing digital sources and reflects the positional accuracy of these original data. The minimum mapping unit (MMU) of the actual shoreline classification segments is estimated at 50 meters where mapping is conducted using 1:24,000 hardcopy fieldmaps. Field verification has shown that the absolute positional accuracy of breaks between shoreline ESI types with a 95-percent error bound is approximately 58 meters. See the Lineage and Process_Description sections for more information on the original source data and how these data were integrated or manipulated to create the final data set.

These data represent coastal shorelines and habitats classified according to the Environmental Sensitivity Index (ESI) classification system. See also the ESIP data layer, part of the larger Outer Coast of Washington and Oregon ESI database, for additional ESI information.

A multi-stage error checking process, described in the above Attribute Accuracy Report, is used to verify both attribute accuracy and logical consistency throughout data production. This process includes multiple automated logical consistency checks that test the files for missing or duplicate data, rules for proper coding, GIS topological consistencies, and SQL SERVER(R) to ArcGIS(R) consistencies. A final review is made by the GIS manager, before the final Geodatabase and metadata are created. After the data are delivered to NOAA, they are again subjected to a several consistency checks, and processed into the final delivery format.