Slide Menu
Maintenance Notice: Tuesday, May 30 @ 8-9:30am Eastern. InPort and its associated services will be under maintenance and unavailable for the deployment of InPort Release 5.2.6. Downtime Schedule Tuesday, May 30, 2023 2:00pm - 3:30pm Eastern / 10:00am - 11:30am Pacific / 8:00am - 9:30am Hawaii Impacted Areas - InPort Website: - InPort WAF: https...
View All
Search Help Show/Hide Menu
Short Citation:
Office of Response and Restoration, 2023: Sensitivity of Coastal Environments and Wildlife to Spilled Oil: North Carolina: INDEX (Index Polygons),

Item Identification

Title: Sensitivity of Coastal Environments and Wildlife to Spilled Oil: North Carolina: INDEX (Index Polygons)
Short Name: North_Carolina_index
Status: Completed
Publication Date: 2011-07

This data set contains vector polygons representing the boundaries of all hardcopy cartographic products produced as part of the Environmental Sensitivity Index (ESI) for North Carolina. This data set comprises a portion of the ESI data for North Carolina. 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.


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.



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, Emergency Response Division, Seattle, Washington.


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category biota
ISO 19115 Topic Category environment
NOS Data Explorer Topic Category Environmental Monitoring
None Coastal resources
None Coastal Zone Management
None Environmental Monitoring
None ESI
None Oil spill planning
None Sensitivity maps
None Wildlife

Spatial Keywords

Thesaurus Keyword
None North Carolina

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, relational attribute or data tables are used to store information in the ESI data structure. The entity-relationship diagram describes relationships between attribute tables in the ESI data structure. This particular geographic data layer (INDEX) does not link to other ESI tables.

Entity Attribute Detail Citation:

A complete description of entity types, attributes, and attribute values for ESI atlases can be found in the NOAA ESI Guidelines (

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 (NOS), Office of Response and Restoration (OR&R), Emergency Response Division (ERD), Seattle, Washington; the U.S. Environmental Protection Agency, Region 4: Southeast, Atlanta, Georgia; and the Department of Homeland Security, U.S. Coast Guard, Office of Incident Management and Preparedness, Washington, D.C.

Support Roles

Data Steward

CC ID: 513251
Date Effective From: 2011-07
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address:


CC ID: 513253
Date Effective From: 2011-07
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address:

Metadata Contact

CC ID: 513254
Date Effective From: 2011-07
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address:

Point of Contact

CC ID: 513252
Date Effective From: 2011-07
Date Effective To:
Contact (Position): ESI Program Manager
Address: 7600 Sand Point Way NE
Seattle, WA 98115
Email Address:


Currentness Reference: The data were compiled during 2010-2011. The currentness dates for the data range from 1949 to 2010 and are documented in the Lineage section.

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 513257
W° Bound: -78.625
E° Bound: -75.399
N° Bound: 36.625
S° Bound: 33.75

Extent Group 1 / Time Frame 1

CC ID: 513256
Time Frame Type: Range
Start: 1949
End: 2010

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Vector Representation 1

CC ID: 589008
Complex Object Present?: Yes
Complex Object Count: 152
Curve Object Present?: Yes
Curve Object Count: 3365
Point Object Present?: Yes
Point Object Count: 153
Surface Object Present?: Yes
Surface Object Count: 214

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 the widest community of GIS/mapping users. Distribution formats include Geodatabase; ARC export, MOSS, and Shape files; and MARPLOT map folders. An ArcMap .mxd file, an ArcView 3.x ESI project, and an ESI_Viewer product for use with the MARPLOT data are also included on the distribution CDs/DVDs 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:


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.



CC ID: 513249
URL Type:
Online Resource

Activity Log

Activity Log 1

CC ID: 513270
Activity Date/Time: 2011-10-15

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 513269
Activity Date/Time: 2017-04-05

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

Activity Log 3

CC ID: 589006
Activity Date/Time: 2017-09-13

Partial upload of Spatial Info section only.

Activity Log 4

CC ID: 604703
Activity Date/Time: 2017-11-01

Replaced entire Lineage section to populate new Source Contribution field.

Activity Log 5

CC ID: 719327
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Technical Environment


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

Data Quality


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 index polygons in this data layer were generated in ArcInfo from the coordinates of the USGS 1:24,000 topographic map corners. Some small amount of positional error may be present along the arcs forming the boundaries of these polygons, particularly away from the polygon corners. Some boundaries were developed from pre-existing digital and hardcopy sources and reflect the positional accuracy of these original data. 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.

Completeness Report:

These data represent the boundaries of all hardcopy cartographic products and digital data extents produced as part of the North Carolina ESI atlas.

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/DVD and the metadata are written. After the data are delivered to NOAA, they are again subjected to a number of quality and consistency checks.




CC ID: 604704
Publish Date: 2010-01-01
Extent Type: Discrete
Extent Start Date/Time: 2010
Scale Denominator: 24000
Source Contribution:

INDEX INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: DIGITAL


CC ID: 604705
Publish Date: 2010-01-01
Extent Type: Range
Extent Start Date/Time: 1949
Extent End Date/Time: 1993
Scale Denominator: 24000
Source Contribution:

ARAPAHOE, N.C. (1993); ASKIN, N.C. (1983); ATLANTIC, N.C. (1949); AURORA, N.C. (1993); BARCO, N.C. (1982); BATH, N.C. (1993); BEAUFORT, N.C. (1987); BELHAVEN, N.C. (1974); BLOUNTS BAY, N.C. (1993); BLUFF POINT, N.C. (1951); BROAD CREEK, N.C. (1980); BROWNS INLET, N.C. (1988); BUFFALO CITY, N.C. (1980); BUXTON, N.C. (1983); CALABASH, N.C.-S.C. (1990); CAMDEN POINT, N.C. (1982); CAMP LEJEUNE, N.C. (1971); CAPE FEAR, N.C. (1970); CAPE HATTERAS, N.C. (1983); CAPE LOOKOUT, N.C. (1951); CAROLINA BEACH, N.C. (1970); CASTLE HAYNE, N.C. (1970); CHERRY POINT, N.C. (1983); COINJOCK, N.C. (1982); COLUMBIA EAST, N.C. (1974); COLUMBIA WEST, N.C. (1974); CORE CREEK, N.C. (1983); COROLLA, N.C. (1982); CREEDS, VA.-N.C. (1986); CURRITUCK, N.C. (1982); DAVIS, N.C. (1983); EAST LAKE SE, N.C. (1987); EAST LAKE, N.C. (1975); EDENHOUSE, N.C. (1982); EDENTON, N.C. (1981); ELIZABETH CITY, N.C. (1982); ENGELHARD EAST, N.C. (1983); ENGELHARD NE, N.C. (1980); ENGELHARD NW, N.C. (1987); ENGELHARD WEST, N.C. (1983); FAIRFIELD NE, N.C. (1974); FAIRFIELD NW, N.C. (1983); FAIRFIELD, N.C. (1983); FORT LANDING, N.C. (1974); FRYING PAN, N.C. (1974); GREAT ISLAND, N.C. (1951); GREEN ISLAND, N.C. (1983); HAMPSTEAD, N.C. (1970); HARKERS ISLAND, N.C. (1983); HARVEY NECK, N.C. (1982); HATTERAS, N.C. (1987); HAVELOCK, N.C. (1983); HERTFORD, N.C. (1982); HOLDEN BEACH, N.C. (1990); HOLLY RIDGE, N.C. (1970); HORSEPEN POINT, N.C. (1950); HOWARD REEF, N.C. (1980); HUBERT, N.C. (1988); JACKSONVILLE SOUTH, N.C. (1988); JARVISBURG, N.C. (1982); JONES BAY, N.C. (1993); KITTY HAWK, N.C. (1982); KNOTTS ISLAND, VA.-N.C. (1971); KURE BEACH, N.C. (1979); LEONARDS POINT, N.C. (1974); LITTLE FISHING POINT, N.C. (1974); LITTLE KINNAKEET, N.C. (1983); LITTLE RIVER, S.C.-N.C. (1990); LOCKWOODS FOLLY, N.C. (1990); LONG BAY, N.C. (1987); LONG SHOAL POINT, N.C. (1951); LOWLAND, N.C. (1993); MANNS HARBOR, N.C. (1974); MANSFIELD, N.C. (1983); MANTEO, N.C. (1983); MARTIN POINT, N.C. (1982); MERRIMON, N.C. (1983); MIDDLETOWN ANCHORA

Process Steps

Process Step 1

CC ID: 604706

Primarily, 1:24,000 USGS topographic maps were used to provide boundaries for cartographic products. In some cases the polygons represent USGS topographic maps that were re-tiled, moved, or extended to provide better cartographic coverage of the study area.

Process Date/Time: 2011-07-01 00:00:00

Child Items

Rubric scores updated every 15m

Rubric Score Type Title

Catalog Details

Catalog Item ID: 40505
GUID: gov.noaa.nmfs.inport:40505
Metadata Record Created By: Tyler Christensen
Metadata Record Created: 2017-04-05 14:52+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+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