NY/NJ Metro Area, Hudson River, and South Long Island 2016 INVERT Polygons

This data set contains sensitive biological resource data for marine, estuarine, and freshwater invertebrates, and federally and/or state endangered, threatened, or rare insects in the New York/New Jersey Metro Area, Hudson River, and South Long Island region. Vector polygons in this data set represent invertebrate distributions, spawning areas, migration areas, concentration areas, and harvest areas. 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 the the NY/NJ Metro Area, Hudson River, and South Long Island region. 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.

Loaded by FGDC Metadata Uploader, batch 10339, 01-25-2018 16:29 by D.M. Nelson. Lineage Processing Step exceeded 4000 character limit, so the narrative in the xml file was parsed into several steps.

The following FGDC sections are not currently supported in InPort, but were preserved and will be included in the FGDC export:

- Spatial Reference Information (FGDC:spref),

- Spatial Data Organization Information (FGDC:spdoinfo)

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, INVERT) 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.

This reflects the extent of all land and water features included in the overall New York, New Jersey, Hudson River, and South Long Island ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.

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.

None

None

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.

These data represent a synthesis of digital data, expert knowledge, survey data, maps, and unpublished reports on invertebrate distributions, spawning areas, migration areas, concentration areas, and harvest areas. These data do not necessarily represent all invertebrate occurrences in the NY/NJ Metro Area, Hudson River, and South Long Island region. The following species are included in this data set: (Species_ID, Common Name, Scientific Name or n/a if not applicable): 19, Blue mussel, Mytilus edulis; 25, Softshell clam, Mya arenaria; 41, Bay scallop, Argopecten irradians; 42, Northern quahog, Mercenaria mercenaria; 43, Eastern oyster, Crassostrea virginica; 44, Horseshoe crab, Limulus polyphemus; 45, American lobster, Homarus americanus; 46, Channeled whelk, Busycon canaliculatum; 49, Blue crab, Callinectes sapidus; 73, Longfin squid, Loligo pealeii; 285, Northeastern beach tiger beetle, Cicindela dorsalis dorsalis; 286, Ocean quahog, Arctica islandica; 287, Atlantic surfclam, Spisula solidissima; 377, Tidewater mucket, Leptodea ochracea; 378, Rare insect, n/a; 505, Monarch butterfly, Danaus plexippus; 543, Alewife floater, Anodonta implicata; 554, Eastern elliptio, Elliptio complanata; 575, Rare, LT, or LE invertebrate, n/a; 585, Coastal barrens buckmoth, Hemileuca maia ssp. 5; 586, Pine Barrens underwing, Catocala herodias gerhardi; 588, Atlantic razor, Siliqua costata; 658, Sandplain heterocampa, Heterocampa varia; 659, Checkered white, Pontia protodice; 660, Frosted elfin, Callophrys irus; 661, Gray petaltail, Tachopteryx thoreyi; 662, Hairy-necked tiger beetle, Cicindela hirticollis; 663, Hessel's hairstreak, Callophrys hesseli; 664, Eastern buckmoth, Hemileuca maia maia; 665, Jersey jair underwing, Catocala jair ssp. 2; 666, Leonard's skipper, Hesperia leonardus; 667, Little bluet, Enallagma minusculum; 668, Myrina Fritillary, Boloria selene myrina; 669, Pine Barrens bluet, Enallagma recurvatum; 670, Scarlet bluet, Enallagma pictum; 675, Whelk, 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, 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.