Sensitivity of Coastal Environments and Wildlife to Spilled Oil: Hudson River: FISH (Fish Polygons)

This data set contains sensitive biological resource data for marine, estuarine, anadromous, and freshwater fish species in the Hudson River. Vector polygons in this data set represent fish distribution, concentration areas, and spawning areas. 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 the Hudson 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.

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.

1819

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 and the Department of Homeland Security, U.S. Coast Guard, Office of Response Plans & Preparedness Division, Washington, D.C.

Resource Description - ESI Atlas for the Hudson River

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, FISH) 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 Hudson River atlas, the number is 52), 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.

Unknown

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.

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 a 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 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.;

None

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.

The software packages used to develop the atlas are Environmental Systems Research Institute's ARC/INFO(r) (version 9.1) and SQL SERVER(r) (version 2000). 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, habitats.e00, hydro.e00, index.e00, invert.e00, m_mammal.e00, mgt.e00, reptiles.e00, rvrmiles.e00, sensitiv.e00, socecon.e00, staging.e00, t_mammal.e00, wetlands.e00. Associated relational and desktop data tables provided in Arc export and text format are bio_lut, biofile, biores, breed, breed_dt, seasonal, soc_dat, soc_lut, sources, species, and status.

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.

Spatial components for the biological data layers can come from expert interviews, hardcopy, or digital sources. Most of the spatial components of the biological data layers 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 or hardcopy 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.

These data represent a synthesis of expert knowledge, digital data, survey data, and hardcopy reports and maps. These data do not necessarily represent all fish occurrences in the Hudson River. The following species are included in this data set: (Species_ID, Common Name, Scientific Name [n/a if not applicable]): 65, Bluefish, Pomatomus saltatrix; 84, Rainbow smelt, Osmerus mordax; 85, Alewife, Alosa pseudoharengus; 86, Blueback herring, Alosa aestivalis; 87, American shad, Alosa sapidissima; 88, Winter flounder, Pleuronectes americanus; 91, Threespine stickleback, Gasterosteus aculeatus; 92, Fourspine stickleback, Apeltes quadracus; 97, Tautog, Tautoga onitis; 98, American eel, Anguilla rostrata; 99, Atlantic tomcod, Microgadus tomcod; 101, Shortnose sturgeon, Acipenser brevirostrum; 102, Atlantic sturgeon, Acipenser oxyrinchus; 104, Striped bass, Morone saxatilis; 108, Summer flounder, Paralichthys dentatus; 113, Bay anchovy, Anchoa mitchilli; 115, Atlantic menhaden, Brevoortia tyrannus; 116, Striped mullet, Mugil cephalus; 145, White perch, Morone americana; 152, Yellow perch, Perca flavescens; 162, Common carp, Cyprinus carpio; 168, Spottail shiner, Notropis hudsonius; 173, White mullet, Mugil curema; 179, Largemouth bass, Micropterus salmoides; 180, Smallmouth bass, Micropterus dolomieu; 182, Bluegill, Lepomis macrochirus; 188, Walleye, Stizostedion vitreum vitreum; 201, Channel catfish, Ictalurus punctatus; 211, Brown bullhead, Ameiurus nebulosus; 212, Pumpkinseed, Lepomis gibbosus; 283, Killifish, Fundulus spp.; 335, Silversides, n/a; 353, Golden shiner, Notemigonus crysoleucas; 366, Hogchoker, Trinectes maculatus; 482, Northern pipefish, Syngnathus fuscus; 506, White catfish, Ameiurus catus; 604, Weakfish, Cynoscion squamipinnis; 824, Northern hog sucker, Hypentelium nigricans; 891, Central mudminnow, Umbra limi; 986, Tessellated darter, Etheostoma olmstedi; 997, American brook lamprey, Lampetra appendix; 998, Bridle shiner, Notropis bifrenatus; 1029, Gobies, n/a.

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.