North Carolina 2016 ESI FISH Polygons, Lines

This data set contains sensitive biological resource data for marine, estuarine, anadromous, and freshwater fish species in North Carolina. Vector polygons (FISH POLYS) in this data set represent fish distributions, spawning and nursery areas, concentration areas, migration areas, anadromous fish runs, and harvest areas. Vector lines (FISH LINES) represent spawning runs that extend beyond the water features in the ESI hydrographic layer (HYDROP). Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for North Carolina. 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 ESI data are intended to provide baseline 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. The ESI data may be appropriate for many other coastal management efforts, though the original intent should be kept in mind.

1962

Prepared by Quantum Spatial Inc., Corvallis, Oregon 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.

The primary attribute tables associated with the ESI biology data are BIOFILE, SOURCES, and BREED_DT. The geographic data layer containing biological resource information (in this case, FISH POLYS and LINES) is linked to the BIOFILE using the RARNUM field. There is a many-to-many relationship from the data layer to the BIOFILE, as an RARNUM may be repeated in several geographic features. Likewise, in the BIOFILE, the same RARNUM may appear in multiple records, representing a unique combination of species found in that region. To be represented by the same RARNUM, these species groups must also share the same seasonality, concentration, mapping qualifier, and source information. The items in the BIOFILE are ELEMENT, SUBELEMENT, NAME, GEN_SPEC, S, F, STATE, S_DATE, F_DATE, GRANK, GRANKDATE, MAPPING_QUALIFIER, 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. The G_SOURCE and S_SOURCE fields provide links to the SOURCES table, where object level source information is available. The BREED field is the link to the BREED_DT table, where searchable breed information is provided. The links to both of these tables are also many-to-many. During the collection of the ESI data, six relational data tables are used to store the attribute data. These are the BIORES, BREED, SEASONAL, SOURCES, SPECIES, and STATUS tables. When we create new ESI data, we populate these tables to maintain the integrity of the data collected. Once completed, all information populating these tables is collapsed into the BIOFILE to ease data queries and general usability of the final product.

NOAA ESI Guidelines

Although these data have been processed and used successfully on a computer system at the National Oceanic and Atmospheric Administration (NOAA), 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. If problems are encountered in downloading the ESI data or with file corruption, contact NOAA (see Distributor). These data represent a snapshot in time and temporal changes may have occurred. The data are not intended to include all biological or human-use resources present in an area; they focus on species and resources particularly sensitive to oiling. In the event of a spill, they should be used for a first assessment only. The data providers are the experts with regard to individual resources. They should be contacted to confirm if more current data exist or if in-depth information is needed about a particular resource.

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 package used to develop the atlas is Environmental Systems Research Institute's ArcGIS for Desktop 10.2(R). The hardware configuration is PCs 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.

Spatial components for the biological data layers can come from expert interviews, hardcopy, or digital sources. Some of the spatial components of the biological data layers may have been 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 digital base maps with a scale of 1:24,000 or larger. Some of the spatial components of the biological data sets are developed from pre-existing digital or hardcopy sources and reflect the positional accuracy of these original data. 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. 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 a synthesis of digital data, expert knowledge, survey data, scientific articles, published academic text, and state and federal agency reports on general fish distributions, spawning and nursery areas, concentration areas, migration areas, and anadromous fish runs. These data do not necessarily represent all fish occurrences in North Carolina. The following species are included in this data set: (Species_ID, Common Name, Scientific Name or n/a if not applicable): 65, Bluefish, Pomatomus saltatrix; 85, Alewife, Alosa pseudoharengus; 86, Blueback herring, Alosa aestivalis; 87, American shad, Alosa sapidissima; 93, Striped killifish, Fundulus majalis; 97, Tautog, Tautoga onitis; 98, American eel, Anguilla rostrata; 101, Shortnose sturgeon, Acipenser brevirostrum; 102, Atlantic sturgeon, Acipenser oxyrinchus; 103, Threadfin shad, Dorosoma petenense; 104, Striped bass, Morone saxatilis; 105, Hickory shad, Alosa mediocris; 107, Spotted seatrout, Cynoscion nebulosus; 108, Summer flounder, Paralichthys dentatus; 109, Red drum, Sciaenops ocellatus; 110, Black sea bass, Centropristis striata; 111, Southern flounder, Paralichthys lethostigma; 112, Gulf flounder, Paralichthys albigutta; 113, Bay anchovy, Anchoa mitchilli; 114, Florida pompano, Trachinotus carolinus; 115, Atlantic menhaden, Brevoortia tyrannus; 116, Striped mullet, Mugil cephalus; 117, Pinfish, Lagodon rhomboides; 119, Silver perch, Bairdiella chrysoura; 121, Spot, Leiostomus xanthurus; 122, Black drum, Pogonias cromis; 123, Atlantic croaker, Micropogonias undulatus; 124, Southern kingfish, Menticirrhus americanus; 126, King mackerel, Scomberomorus cavalla; 127, Spanish mackerel, Scomberomorus maculatus; 134, Cobia, Rachycentron canadum; 136, Dolphinfish, Coryphaena hippurus; 137, Sheepshead, Archosargus probatocephalus; 138, Weakfish, Cynoscion regalis; 140, Ladyfish, Elops saurus; 143, Tarpon, Megalops atlanticus; 145, White perch, Morone americana; 150, Scup, Stenotomus chrysops; 151, Northern puffer, Sphoeroides maculatus; 152, Yellow perch, Perca flavescens; 153, Northern kingfish, Menticirrhus saxatilis; 157, Goosefish, Lophius americanus; 158, Butterfish, Peprilus triacanthus; 160, Windowpane, Scophthalmus aquosus; 163, Gizzard shad, Dorosoma cepedianum; 173, White mullet, Mugil curema; 179, Largemouth bass, Micropterus salmoides; 181, Black crappie, Pomoxis nigromaculatus; 182, Bluegill, Lepomis macrochirus; 201, Channel catfish, Ictalurus punctatus; 203, Warmouth, Lepomis gulosus; 204, Redear sunfish, Lepomis microlophus; 212, Pumpkinseed, Lepomis gibbosus; 218, Bowfin, Amia calva; 271, Inland silverside, Menidia beryllina; 278, Little tunny, Euthynnus alletteratus; 292, Chain pickerel, Esox niger; 294, Spotted hake, Urophycis regia; 310, Atlantic spadefish, Chaetodipterus faber; 311, Atlantic bonito, Sarda sarda; 312, Harvestfish, Peprilus alepidotus; 321, Atlantic cutlassfish, Trichiurus lepturus; 331, Sharks, n/a; 353, Golden shiner, Notemigonus crysoleucas; 356, Greater amberjack, Seriola dumerili; 366, Hogchoker, Trinectes maculatus; 378, Atlantic needlefish, Strongylura marina; 464, Longnose gar, Lepisosteus osseus; 707, Hammerhead shark, Sphyrna spp.; 710, Triggerfish, Balistes spp.; 791, Sailfish, Istiophorus platypterus; 967, Sandbar shark, Carcharhinus plumbeus; 984, Bluespotted sunfish, Enneacanthus gloriosus; 985, Redbreast sunfish, Lepomis auritus; 998, Bridle shiner, Notropis bifrenatus; 999, Redfin pickerel, Esox americanus americanus; 1127, Swamp darter, Etheostoma fusiforme; 1130, Dusky shark, Carcharhinus obscurus; 1145, Western mosquitofish, Gambusia affinis; 1146, Bluefin tuna, Thunnus thynnus; 1148, Bank sea bass, Centropristis ocyurus; 1160, Blacknose shark, Carcharhinus acronotus; 1238, Thresher shark, Alopias vulpinus.

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 several consistency checks, and processed into the final delivery format.