Sensitivity of Coastal Environments and Wildlife to Spilled Oil: South Florida: MGT_FISH (Fishery Management Area Polygons)

This data set contains commercial fisheries in South Florida. Vector polygons in this data set represent statistical reporting grids used to aggregate commercial fishing data. Species-specific landings, catch per unit effort (CPUE), value, fishing seasons, and fishery types are stored in a relational data table designed to be used in conjunction with this spatial data layer. This data set comprises a portion of the ESI data for South Florida. 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 data layers Fish (Fish Polygons), MGT (Management Area Polygons), and SOCECON (Socioeconomic Resource Points and Lines), part of the larger South Florida ESI database, for additional fisheries and human-use information.

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.

1748

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.

Three relational attribute or data tables, SOC_DAT, MGT_FISH_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_FISH) is linked to the Management Fish Resources table (MGT_FISH_DAT) using the unique ID and the lookup table MGT_FISH_LUT, or it can be linked directly using FMANUM. FMANUM is a unique reference number concatenated with the atlas number (for South Florida, the number is 221). ID is a unique combination of the atlas number (221), an element specific number (MGT_FISH = 11), and a unique record number. MGT_FISH_DAT and the other relational data tables are described in the Detailed_Description sections. 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.

A complete description of entity types, attributes, and attribute values for ESI atlases can be found in the NOAA ESI Guidelines (http://response.restoration.noaa.gov/esi_guidelines).

Although these data have been processed 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.

Contact NOAA if you require the ESI data be provided to you on CD/DVD (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 files, Shapefiles, and a file Geodatabase (the recommended format). 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 10.0) and SQL SERVER(R) (version 2005). The hardware configuration is PCs with Windows Operating System 7.

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: benthic.e00, birds.e00, esil.e00, esip.e00, fish.e00, habitats.e00, hydro.e00, index.e00, invert.e00, m_mammal.e00, mgt.e00, mgt_fish.e00, nests.e00, reptiles.e00, socecon.e00, and t_mammal.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, mgt_fish_dat.e00, mgt_fish_lut.e00, seasonal.e00, soc_dat.e00, soc_lut.e00, sources.e00, species.e00, and status.e00.

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 human-use data layers can come from expert interviews, hardcopy, or digital sources. Most of the spatial components of the human-use data layers are developed from pre-existing digital or hardcopy sources and reflect the positional accuracy of these original data. Some of the spatial components of the human-use data layers are compiled on hardcopy base maps with a scale of 1:24,000. 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 information on commercial landings and fishing seasons based on the marine fisheries management database maintained by Florida Fish and Wildlife Conservation Commission (FWC). Please note that this information is based on fishing information and is meant to portray a socioeconomic dataset and not areas biologically important to a species. The following fisheries are included in this dataset (listed by common name of the fishery): Almaco jack, Ballyhoo, Banded coral shrimp, Beaugregory, Bicolor damselfish, Bigeye scad, Bigeye tuna, Black drum, Black grouper, Blackear wrasse, Blackfin tuna, Blue angelfish, Blue chromis, Blue crab, Blue runner, Blue tang, Bluefish, Bluehead, Brown chromis, Caribbean spiny lobster, Cero, Cherubfish, Clown wrasse, Cobia, Cocoa damselfish, Cottonwick grunt, Creole wrasse, Crevalle jack, Dolphinfish, Dusky damselfish, Dwarf seahorse, Florida pompano, French angelfish, French grunt, Gag, Golden deepsea crab, Gray angelfish, Gray snapper, Great barracuda, Greater amberjack, King mackerel, Lane snapper, Lined seahorse, Little tunny, Longfin damselfish, Lookdown, Mojarras, Mutton snapper, Peppermint shrimp, Pink shrimp, Porkfish, Puddingwife, Purple reeffish, Queen angelfish, Red grouper, Rock beauty, Rock shrimp, Royal red shrimp, Sandbar shark, Sergeant major, Sheepshead, Slippery dick, Snowy grouper, Spanish mackerel, Stone crab, Sunshinefish, Swordfish, Threespot damselfish, Tilefish, Tomtate, Tricolor hermit, Triggerfishes, Wahoo, Yellowedge grouper, Yellowfin tuna, Yellowhead jawfish, Yellowhead wrasse, Yellowtail damselfish, Yellowtail reeffish, Yellowtail snapper. See also the data layers Fish (Fish Polygons), MGT (Management Area Polygons), and SOCECON (Socioeconomic Resource Points and Lines), part of the larger South Florida ESI database, for additional fisheries and human-use information.

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