Slide Menu
Search Help Show/Hide Menu
Short Citation:
Office of Response and Restoration, 2022: Columbia River ESI: MGT (Management Area Polygons), https://www.fisheries.noaa.gov/inport/item/40264.

Item Identification

Title: Columbia River ESI: MGT (Management Area Polygons)
Short Name: Columbia_river_WA_OR_mgt
Status: Completed
Publication Date: 2004-11
Abstract:

This data set contains sensitive human-use data for Wildlife Refuges, National Forests, and State Parks for the Columbia River area. Vector polygons in this data set represent the management areas. Location-specific type and source information is stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer.This data set comprises a portion of the Environmental Sensitivity Index (ESI) data for Columbia River. 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 SOCECON (Socioeconomic Resource Points and Lines) data layer, part of the larger Columbia River ESI database, for additional human-use information.

Purpose:

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.

Notes:

1682

Other Citation Details:

Prepared by Research Planning, Inc., Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington; Coastal Storms Initiative; U.S. Fish and Wildlife Service; NOAA Fisheries; State of Oregon; and State of Washington.

Supplemental Information:

Resource Description - ESI Atlas for Columbia River

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
ISO 19115 Topic Category environment
ISO 19115 Topic Category oceans
NOS Topic Category Environmental Monitoring
None Coastal resources
None Coastal Zone Management
None ESI
None Management Area
None Oil spill planning
None Sensitivity maps
None Wildlife

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None Columbia River

Physical Location

Organization: Office of Response and Restoration
City: Silver Spring
State/Province: MD

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: None Planned
Data Presentation Form: vector digital data
Entity Attribute Overview:

In addition to the geographic data layers, two relational attribute or data tables, SOC_DAT and SOURCES, are used to store the complex socioeconomic data in the ESI data structure. The geographic data layer containing socioeconomic data resource information (in this case, MGT) is linked to the Socioeconomic Resources table (SOC_DAT) using the unique ID and the lookup table SOC_LUT, or it can be linked directly using HUNUM. HUNUM is a unique reference number concatenated with the atlas number (the Columbia River atlas number is 41). ID is a unique combination of the atlas number (41), an element specific number (MGT=11), and a unique record number. SOC_DAT and the other relational data tables are described below in detail. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way these tables relate to the geographic data layers and other attribute tables in the ESI data structure.

Entity Attribute Detail Citation:

Unknown

Distribution Liability:

Although these data have been processed 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 Set Credit: This project was supported by the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington; Coastal Storms Initiative; U.S. Fish and Wildlife Service; NOAA Fisheries; State of Oregon; and State of Washington.

Support Roles

Data Steward

CC ID: 505512
Date Effective From: 2004-11
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address: orr.esi@noaa.gov

Distributor

CC ID: 505514
Date Effective From: 2004-11
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address: orr.esi@noaa.gov

Metadata Contact

CC ID: 505515
Date Effective From: 2004-11
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address: orr.esi@noaa.gov

Point of Contact

CC ID: 505513
Date Effective From: 2004-11
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address: orr.esi@noaa.gov

Extents

Currentness Reference: The MGT data were compiled during 2003-2004. The currentness dates for the data range from 1981 to 2004 and are documented in the Lineage section.

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 505518
W° Bound: -124.125
E° Bound: -120.67375
N° Bound: 46.375
S° Bound: 45.3

Extent Group 1 / Time Frame 1

CC ID: 505517
Time Frame Type: Range
Start: 1981
End: 2004

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Vector Representation 1

CC ID: 588231
Complex Object Present?: Yes
Complex Object Count: 78
Curve Object Present?: Yes
Curve Object Count: 18495
Point Object Present?: Yes
Point Object Count: 78
Surface Object Present?: Yes
Surface Object Count: 104

Access Information

Security Class: Unclassified
Data Access Procedure:

Contact NOAA for distribution options (see Distributor). ESI data are processed into multiple formats to make them useful to a wider community of GIS/mapping users. Distribution formats include ARC export, MOSS and Shape files, and MARPLOT map folders. An ArcView ESI project and ESI_Viewer product are also included on the distribution CDs for ease of use of the ESI data. The database files are distributed both in the NOAA standard relational database format (see NOAA Technical Memorandum NOS ORCA 115) and in a simplified desktop flat file format. This metadata document includes information on both of these database formats.;

Data Access Constraints:

None

Data Use Constraints:

DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES.Besides the above warning, there are no use constraints on these data. 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. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data.

URLs

URL 1

CC ID: 505510
URL: http://response.restoration.noaa.gov/esi
URL Type:
Online Resource

Activity Log

Activity Log 1

CC ID: 505531
Activity Date/Time: 2004-11
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 505530
Activity Date/Time: 2017-04-05
Description:

Converted from Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 588229
Activity Date/Time: 2017-09-13
Description:

Partial upload of Spatial Info section only.

Activity Log 4

CC ID: 602899
Activity Date/Time: 2017-11-01
Description:

Replaced entire Lineage section to populate new Source Contribution field.

Activity Log 5

CC ID: 719088
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Technical Environment

Description:

The software packages used to develop the atlas are Environmental Systems Research Institute's ARC/INFO(r) (version 8.3) and SQL SERVER(r) (version 7.0). The hardware configuration is PC's with Windows Operating System (NT4.0/2000).The Spatial_Data_Organization_Information section refers only to the source files in the ARC export format. The following files are included in that data set: birds.e00, esi.e00, fish.e00, fishl.e00, habitats.e00, hydro.e00, index.e00, invert.e00, m_mammal.e00, m_mampt.e00, mgt.e00, nests.e00, nwi.e00, reptiles.e00, socecon.e00, t_mammal.e00. Associated relational and desktop data tables provided in Arc export and text format are bio_lut, biofile, biores, breed, breed_dt, runs_dat, seasonal, soc_dat, soc_lut, sources, species, and status.

Data Quality

Accuracy:

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, hardcopy 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.

Horizontal Positional Accuracy:

The MGT data set was developed from pre-existing digital sources and reflects the positional accuracy of these original data. See the Lineage and Process_Description sections for more information on the original data source and how these data were integrated or manipulated to create the final data set.

Completeness Report:

These data represent a synthesis of digital boundaries for management areas. These data do not necessarily represent all management area sites in the Columbia River region. See also the SOCECON (Socioeconomic Resource Points and Lines) data layer, part of the larger Columbia River ESI database, for additional human-use information.

Conceptual Consistency:

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 (such as dangles, unnecessary nodes, etc.), and SQL SERVER(r) to ARC/INFO(r) consistencies. A final review is made by the GIS manager, where the data are written to CD-ROM and the metadata are written.After the data are delivered to NOAA, they are again subjected to a number of quality and consistency checks. In the process of checking for topological and database consistencies, new ID's and RARNUM's or HUNUM's are also generated. The new ID's are a combination of atlas number, element number, and record number. In addition, the value used to represent the element is modified to reflect the type of feature being mapped. In the case of an element that is normally represented by a point or polygon, a value of 20 is added to the standard element value for mapping of linear features. In the case where an element usually mapped as a polygon is represented by a point, a value of 30 is added to the regular element value. The RARNUM's are also modified to include the atlas number, so multiple atlases can be combined and RARNUM's remain unique. RARNUM's are redefined on an element basis, so "resource at risk" groupings will contain only a single element. HUNUM's are also modified to include the atlas number.

Lineage

Sources

Distribution of Fish, Birds, Plants, and Mammals in the Columbia River

CC ID: 602901
Contact Name: Clark, A., U.S. Fish and Wildlife Service (USFWS)
Publish Date: 2004-02-01
Extent Type: Discrete
Extent Start Date/Time: 2004-02
Source Contribution:

Wildlife Refuge boundaries | Source Geospatial Form: Expert Knowledge | Type of Source Media: Personal communication

Distribution of Wildlife on Sauvie Island and Surrounding Areas

CC ID: 602902
Contact Name: Nebeker, M., Oregon Department of Fish and Wildlife (ODFW)
Publish Date: 2004-02-01
Extent Type: Discrete
Extent Start Date/Time: 2004-02
Source Contribution:

Sauvie Island Wildlife Area boundary | Source Geospatial Form: Expert Knowledge | Type of Source Media: Personal communication

Hoquiam Washington-Oregon, Pacific Coast Ecological Inventory

CC ID: 602900
Contact Name: U.S. Fish and Wildlife Service (USFWS)
Publish Date: 1981-01-01
Extent Type: Discrete
Extent Start Date/Time: 1981
Scale Denominator: 250000
Source Contribution:

Regional park boundaries | Source Geospatial Form: Hardcopy Map | Type of Source Media: paper

Oregon Atlas and Gazetteer

CC ID: 602903
Contact Name: DeLorme
Publish Date: 2001-01-01
Extent Type: Discrete
Extent Start Date/Time: 2001
Scale Denominator: 150000
Source Contribution:

Oregon state park boundaries | Source Geospatial Form: Hardcopy atlas | Type of Source Media: paper

Ridgefield National Wildlife Complex Boundaries

CC ID: 602906
Contact Name: Anderson, E., U.S. Fish and Wildlife Service (USFWS)
Publish Date: 2004-01-01
Extent Type: Discrete
Extent Start Date/Time: 2004
Scale Denominator: 24000
Source Contribution:

Ridgefield National Wildlife Complex boundaries | Source Geospatial Form: vector digital data | Type of Source Media: electronic mail system

USGS Digital Raster Graphics

CC ID: 602904
Contact Name: University of Washington
Scale Denominator: 24000
Source Contribution:

Oregon state park boundaries | Source Geospatial Form: raster digital data | Type of Source Media: online

Washington State Park Boundaries

CC ID: 602905
Contact Name: Washington State Parks and Recreation Commission
Publish Date: 2004-01-01
Extent Type: Discrete
Extent Start Date/Time: 2004
Scale Denominator: 24000
Source Contribution:

Washington state park boundaries | Source Geospatial Form: vector digital data | Type of Source Media: electronic mail system

Process Steps

Process Step 1

CC ID: 602907
Description:

Digital vector lines used to depict management areas (State Parks) for Washington in this data layer were provided by Washington Department of Parks and Recreation. Boundaries for the Ridgefield National Wildlife Refuge complex (Washington) were provided by U.S. Fish and Wildlife Service (USFWS). Management boundaries for the state of Oregon were digitized from U.S. Geological Survey (USGS) Digital Raster Graphics (DRGs). The MGT data layer was incorporated into an ArcInfo system along with the SOCECON and biology data layers, and hardcopy draft maps were created using U.S. Geological Survey 1:24,000 topographic quadrangles as base maps. Following the creation of draft maps, a second set of interviews were conducted with the resource experts. Participants who were unable to attend the meetings were sent a set of maps to review. Edits to the MGT data layer were based on the recommendations of the resource experts, and final hardcopy maps were created.

Process Date/Time: 2004-08-01 00:00:00

Child Items

Rubric scores updated every 15m

Rubric Score Type Title
Entity MGT.PAT
Entity SOC_DAT
Entity SOC_LUT
Entity SOURCES

Catalog Details

Catalog Item ID: 40264
GUID: gov.noaa.nmfs.inport:40264
Metadata Record Created By: Tyler Christensen
Metadata Record Created: 2017-04-05 14:50+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2019-06-04 13:14+0000
Metadata Record Published: 2018-02-08
Owner Org: ORR
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Review Frequency: 1 Year