Sensitivity of Coastal Environments and Wildlife to Spilled Oil: Hudson River: SENSITIV (Sensitive Area Points)

Metadata also available as - [Parseable text] - [SGML]

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
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.
Publication_Date: 200604
Title:
Sensitivity of Coastal Environments and Wildlife to Spilled Oil: Hudson River: SENSITIV (Sensitive Area Points)
Edition: First
Geospatial_Data_Presentation_Form: Vector digital data
Series_Information:
Series_Name: None
Issue_Identification: Hudson River
Publication_Information:
Publication_Place: Seattle, Washington
Publisher:
National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington.
Other_Citation_Details:
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.
Description:
Abstract:
This data set contains human-use resource data for sensitive areas along the Hudson River. Vector points in this data set represent sensitive areas. This data set comprises a portion of the Environmental Sensitivity Index (ESI) data for 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. See also the SOCECON (Socioeconomic Resource Points and Lines) and MGT (Management Area Polygons) data layers, part of the larger Hudson River ESI database, for additional human-use information.
Purpose:
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.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2005
Currentness_Reference:
The data were compiled during 2005. The currentness date for this data is 2005 and is documented in the Lineage section.
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None Scheduled
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -74.05800
East_Bounding_Coordinate: -73.62500
North_Bounding_Coordinate: 42.75000
South_Bounding_Coordinate: 40.87500
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: ESI
Theme_Keyword: Sensitivity maps
Theme_Keyword: Coastal resources
Theme_Keyword: Oil spill planning
Theme_Keyword: Coastal Zone Management
Theme_Keyword: Wildlife
Theme_Keyword: Socioeconomic
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Hudson River
Access_Constraints: None
Use_Constraints:
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.
Browse_Graphic:
Browse_Graphic_File_Name: datafig.jpg
Browse_Graphic_File_Description:
Depicts the relationships between spatial data layers and attribute data tables for the Hudson River ESI data.
Browse_Graphic_File_Type: JPEG
Data_Set_Credit:
This project was supported by 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.
Native_Data_Set_Environment:
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 the 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.


Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
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.
Logical_Consistency_Report:
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.
Completeness_Report:
These data represent a synthesis of digital data of sensitive areas. See also the SOCECON (Socioeconomic Resource Points and Lines) and MGT (Management Area Polygons) data layers, part of the larger Hudson River ESI database, for additional human-use information. These data do not necessarily represent all human-use sites in the Hudson River area.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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 data source and how these data were integrated or manipulated to create the final data set.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
ED LEVINE, NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION (NOAA)
Publication_Date: 2005
Title: HRSITES_NEW
Geospatial_Data_Presentation_Form: VECTOR DIGITAL DATA
Other_Citation_Details: NEW YORK/NEW JERSEY AREA CONTINGENCY PLAN
Type_of_Source_Media: EMAIL
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2005
Source_Currentness_Reference: DATE OF COMMUNICATION
Source_Citation_Abbreviation: NONE
Source_Contribution: SENSITIVE AREAS
Process_Step:
Process_Description:
The main source of data used to depict sensitive areas was a digital dataset received from Ed Levine, NOAA Scientific Support Coordinator (SSC). It was originally produced for the New York/New Jersey Area Contingency Plan. In some cases, vector points with incorrect lat-longs where moved to their correct spatial location as specified during the review process with the original data providers. Some minor attribute modifications were made as part of the same review.
Process_Date: 200602
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: NOAA, Office of Response and Restoration
Contact_Person: Jill Petersen
Contact_Address:
Address_Type: Physical address
Address: 7600 Sand Point Way N.E.
City: Seattle
State_or_Province: Washington
Postal_Code: 98115-6349
Contact_Voice_Telephone: (206) 526-6944
Contact_Facsimile_Telephone: (206) 526-6329
Contact_Electronic_Mail_Address: Jill.Petersen@noaa.gov

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity Point
Point_and_Vector_Object_Count: 89

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.0000001
Longitude_Resolution: 0.0000001
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1927
Ellipsoid_Name: Clark 1866
Semi-major_Axis: 6378206.400000
Denominator_of_Flattening_Ratio: 294.978698

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: SENSITIV.PAT
Entity_Type_Definition:
The SENSITIV.PAT table contains attribute information for the vector points representing sensitive areas. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the relationships between attribute tables in the ESI data structure.
Entity_Type_Definition_Source: Research Planning, Inc.
Attribute:
Attribute_Label: SITE_NAME
Attribute_Definition: The area name.
Attribute_Definition_Source: Research Planning, Inc.
Attribute_Domain_Values:
Unrepresentable_Domain: Acceptable values change from atlas to atlas.
Attribute:
Attribute_Label: ID
Attribute_Definition:
An identifier that links vector objects in the SENSITIV data layer to a table in the atlas introductory text.
Attribute_Definition_Source: NOAA
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 201
Range_Domain_Maximum: 1505

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: John Kaperick
Contact_Organization: NOAA, Office of Response and Restoration
Contact_Address:
Address_Type: Physical Address
Address: 7600 Sand Point Way N.E.
City: Seattle
State_or_Province: Washington
Postal_Code: 98115-6349
Contact_Voice_Telephone: (206) 526-6400
Contact_Facsimile_Telephone: (206) 526-6329
Resource_Description: ESI Atlas for the Hudson River
Distribution_Liability:
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.
Custom_Order_Process:
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.

Metadata_Reference_Information:
Metadata_Date: 200604
Metadata_Review_Date: 200604
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Jill Petersen
Contact_Organization: NOAA, Office of Response and Restoration
Contact_Position: GIS Manager
Contact_Address:
Address_Type: Physical Address
Address: 7600 Sand Point Way N.E.
City: Seattle
State_or_Province: Washington
Postal_Code: 98115-6349
Contact_Voice_Telephone: (206) 526-6944
Contact_Facsimile_Telephone: (206) 526-6329
Contact_Electronic_Mail_Address: Jill.Petersen@noaa.gov
Metadata_Standard_Name: Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998

Generated by mp version 2.8.21 on Sun May 14 19:35:25 2006