Sensitivity of Coastal Environments and Wildlife to Spilled Oil: New Hampshire: ESI (Environmental Sensitivity Index Shoreline Types - Polygons and Lines)

This data set contains vector lines and polygons representing the shoreline and coastal habitats of New Hampshire classified according to the Environmental Sensitivity Index (ESI) classification system. This data set comprises a portion of the ESI for New Hampshire. 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.

This data was collected, mapped, and digitized to provide environmental data for the New Hampshire Department of Environmental Services and the New Hampshire Estuaries Project response plans for immediate and effective protection of sensitive resources.

1988

Prepared by Research Planning, Inc., Columbia, South Carolina for the New Hampshire Department of Environmental Services, Concord, New Hampshire and the New Hampshire Estuaries Project, Portsmouth, New Hampshire. Formatted to national Environmental Sensitivity Index standards by National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington.

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 ARC export, MOSS and Shape files, and MARPLOT map folders. An ArcView ESI project and 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 8.3) and SQL SERVER(r) (version 7.0). 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: bio_lut.e00, birds.e00, biofile.e00, biores.e00, breed.e00, breed_dt.e00, esi.e00, fish.e00, habitats.e00, hydro.e00, index.e00, invert.e00, m_mammal.e00, mgt.e00, nests.e00, reptiles.e00, seasonal.e00, soc_dat.e00, soc_lut.e00, socecon.e00, sources.e00, species.e00, status.e00, t_mammal.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, socecon, 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.

The ESI data set was developed from pre-existing digital sources and reflects the positional accuracy of these original data. The horizontal positional accuracy of the 1:24,000 USGS topographic quads should conform to National Map Accuracy Standards at scales of 1:24,000. The minimum mapping unit (MMU) of the actual shoreline classification segments is estimated at 50 meters when mapping is conducted using 1:24,000 hardcopy fieldmaps. Field verification has shown that the absolute positional accuracy of breaks between shoreline ESI types with a 95-percent error bound is approximately 58 meters. 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 coastal shorelines and habitats classified according to the Environmental Sensitivity Index (ESI) classification system.

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 node, 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.