Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Data Set Info
Support Roles
Extents
Spatial Info
Access Info
URLs
Activity Log
Tech Environment
Data Quality
Lineage
Child Items
Catalog Details

Summary

Short Citation
Office of Response and Restoration, 2024: Columbia River ESI: M_MAMMAL (Marine Mammal Polygons), https://www.fisheries.noaa.gov/inport/item/40268.
Full Citation Examples

Abstract

This data set contains sensitive biological resource data for Steller sea lions, harbor seals, and California sea lions in Columbia River. Vector polygons in this data set represent locations of marine mammal distribution and haul-out sites. Species-specific abundance, seasonality, status, life history, and source information are 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 M_MAMPT (Marine Mammal Points) data layer, part of the larger Columbia River ESI database, for additional marine mammal information.

Distribution Information

No Distributions available.

Access Constraints:

None

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.

Controlled Theme Keywords

environment, oceans

Child Items

Type Title
Entity BIORES
Entity BIO_LUT
Entity BREED
Entity M_MAMMAL.PAT
Entity SEASONAL
Entity SOURCES
Entity SPECIES
Entity STATUS

Contact Information

Point of Contact
ESI Program Manager
orr.esi@noaa.gov

Metadata Contact
ESI Program Manager
orr.esi@noaa.gov

Extents

Geographic Area 1

-124.125° W, -120.67375° E, 46.375° N, 45.3° S

Time Frame 1
1984 - 2004

Item Identification

Title: Columbia River ESI: M_MAMMAL (Marine Mammal Polygons)
Short Name: Columbia_river_WA_OR_m_mammal
Status: Completed
Publication Date: 2004-11
Abstract:

This data set contains sensitive biological resource data for Steller sea lions, harbor seals, and California sea lions in Columbia River. Vector polygons in this data set represent locations of marine mammal distribution and haul-out sites. Species-specific abundance, seasonality, status, life history, and source information are 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 M_MAMPT (Marine Mammal Points) data layer, part of the larger Columbia River ESI database, for additional marine mammal 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:

1670

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
ISO 19115 Topic Category
environment
ISO 19115 Topic Category
oceans
UNCONTROLLED
NOS Topic Category Environmental Monitoring
None Coastal resources
None Coastal Zone Management
None ESI
None Marine Mammal
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, six relational attribute or data tables, BIORES, BREED, SEASONAL, SOURCES, SPECIES, and STATUS, are used to store the complex biological data in the ESI data structure. The geographic data layer containing biological resource information (in this case, M_MAMMAL) is linked to the Biological Resources table (BIORES) using the unique ID and the lookup table BIO_LUT, or it can be linked directly using RARNUM. The ID is a unique combination of the atlas number (for the Columbia River atlas, the number is 41), an element/layer specific number (BIRDS are layer 1, FISH are layer 2, etc.), and a unique record number. The RARNUM represents a unique combination of species, seasonalities, concentrations, and source information. For each of these groupings, a number is generated. That number is concatenated with the atlas number to create a "resource at risk" number that is unique across atlases. BIORES 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.Due to the complexity of the relational database model, the data items are also post-processed into a flat file format. This table, called BIOFILE, may be used in place of the relational files described below to ease simple data queries. The items in the flat file are ELEMENT, SUBELEMENT, NAME, GEN_SPEC, S, F, NHP, DATE_PUB, CONC, JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, BREED1, BREED2, BREED3, BREED4, BREED5, RARNUM, G_SOURCE, S_SOURCE, and BREED. All of these items are the same as their counterparts in the individual data tables described below, except the BREED1-BREED5 and BREED items. BREED is a newly generated variable used to link to the BREED_DT data table, a modified, more compact version of the relational BREED data table. BREED1-BREED5 give a text summary of when each life stage occurs within the associated map object. The life stages referred to are the same as those listed in the Detailed_Description of the BREED data table. The link to the BIOFILE may be made through the BIO_LUT, using ID to link to RARNUM, or BIOFILE may be linked directly to the RARNUM in each of the geographic layer's attribute data tables. As mentioned, BREED_DT is an auxiliary support data table to the flat file structure, which allows the user to do searches based on month for seasonal breeding activities. The link from the flat file to BREED_DT is the BREED item.A second supporting data table is SOURCES. This is the same as the source file described above, and the link from the flat file is both G_SOURCE and S_SOURCE. It should be noted that although the flat file eases data query, it is not a normalized database structure, and actual updates performed by the states and other responsible agencies should be done using the relational data tables. The entity-relationship diagram, describing relationships between attribute tables in the ESI data structure, does NOT include the BIOFILE data table, and this data table is NOT described in detail below.

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: 505640
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: 505642
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: 505643
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: 505641
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 biological data were compiled during 2003-2004. The currentness dates for these data range from 1984 to 2004 and are documented in the Lineage section.

Extent Group 1

Extent Group 1 / Geographic Area 1

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

Extent Group 1 / Time Frame 1

CC ID: 505645
Time Frame Type: Range
Start: 1984
End: 2004

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Vector Representation 1

CC ID: 588243
Complex Object Present?: Yes
Complex Object Count: 10
Curve Object Present?: Yes
Curve Object Count: 6293
Point Object Present?: Yes
Point Object Count: 10
Surface Object Present?: Yes
Surface Object Count: 19

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: 505638
URL: http://response.restoration.noaa.gov/esi
URL Type:
Online Resource

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 505658
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: 588241
Activity Date/Time: 2017-09-13
Description:

Partial upload of Spatial Info section only.

Activity Log 4

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

Replaced entire Lineage section to populate new Source Contribution field.

Activity Log 5

CC ID: 719092
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:

Most of the spatial components of the biological data sets are developed using regional experts who estimate concentration areas. It is difficult to estimate the positional accuracy of such data, except to state that they are compiled on hardcopy base maps with a scale of 1:24,000. Some of the spatial components of the biological data sets are developed from pre-existing digital sources and reflect 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. Note that biological resource data by their very nature are considered "fuzzy", and this should be understood when considering the positional accuracy of vector digital objects representing these resources.

Completeness Report:

These data represent a synthesis of expert knowledge and available hardcopy reports and digital data on marine mammal distribution. Information on marine mammal haulouts and concentrations was also adapted from Washington Priority habitat data. Contact Washington Department of Fish and Wildlife (WDFW) for more information on these data. See also the M_MAMPT (Marine Mammal Points) data layer, part of the larger Columbia River ESI database, for additional marine mammal information. These data do not necessarily represent all marine mammal occurrences in Columbia River. The following species are included in this data set: (Species_ID, Common Name, Scientific Name, if applicable): 1, Steller sea lion, Eumetopias jubatus; 2, Harbor seal, Phoca vitulina; 22, California sea lion, Zalophus californianus.

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

Fish, Bird, and Mammal Distributions along the Columbia River

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

Distribution information for marine mammals | Source Geospatial Form: Expert knowledge | Type of Source Media: Personal communication

Marine Mammal Abundance and Distribution in the Columbia River Estuary

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

Distribution and abundance information for marine mammals | Source Geospatial Form: Expert knowledge | Type of Source Media: Personal communication

Marine Mammal Haulout Sites in the Columbia River

CC ID: 602939
Contact Name: Washington Department of Fish and Wildlife (WDFW)
Publish Date: 2004-03-01
Extent Type: Discrete
Extent Start Date/Time: 2004-03
Scale Denominator: 24000
Source Contribution:

Location of marine mammal haulout sites adapted from WDFW data | Source Geospatial Form: vector digital data | Type of Source Media: CD-ROM

The Columbia River Estuary Atlas of Physical and Biological Characteristics

CC ID: 602938
Contact Name: Columbia River Estuary Data Development Program
Publish Date: 1984-01-01
Extent Type: Discrete
Extent Start Date/Time: 1984
Scale Denominator: 250000
Source Contribution:

Seasonality information for marine mammals | Source Geospatial Form: Hardcopy atlas | Type of Source Media: paper

Process Steps

Process Step 1

CC ID: 602940
Description:

Three main sources of data were used to depict marine mammal distributions and haulout sites for this data layer: (1) personal interviews with resource experts from Oregon Department of Fish and Wildlife (ODFW), Washington Department of Fish and Wildlife (WDFW), and U.S. Fish and Wildlife Service (USFWS); (2) numerous published and unpublished reports; and (3) information adapted from Washington Priority Habitat data. (Contact WDFW for more information regarding the Washington Priority Habitat data.) Information gathered during initial interviews and from hardcopy sources was compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles.The compiled data were digitized off of the base maps into an ArcInfo system to create the M_MAMMAL data layer. All ESI, biology, and human-use data were plotted onto hardcopy draft maps. Following the delivery of draft maps to the participating resource experts, a second set of interviews was conducted to review the maps. Edits to the M_MAMMAL data layer were made 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 BIORES
Entity BIO_LUT
Entity BREED
Entity M_MAMMAL.PAT
Entity SEASONAL
Entity SOURCES
Entity SPECIES
Entity STATUS

Catalog Details

Catalog Item ID: 40268
GUID: gov.noaa.nmfs.inport:40268
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: 2023-05-30 18:09+0000
Metadata Record Published: 2018-02-08
Owner Org: ORR
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2018-02-08
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2019-02-08