NY_Protection_ScenariosAlb

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Environmental Protection Agency
Publication_Date: 2006
Title: NY_Protection_ScenariosAlb
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Data delineating the likelihood of shoreline protection for the use of participants in Climate Change Science Program Synthesis and Assessment Product 4.1. Data underlying the analysis reported in "Assessment of Sea Level Rise Response Scenarios in New York." Draft Manuscript available to CCSP collaborators from Jim Titus.

Subsequently published in Titus, J.G., D.E. Hudgens, D.L. Trescott, M. Craghan, W.H. Nuckols, C.H. Hershner, J. M. Kassakian, C.J. Linn, P.G. Merritt, T.M. McCue, J.F. O'Connell, J. Tanski, and J. Wang. 2009. State and Local Governments Plan for Development of Most Land Vulnerable to Rising Sea Level along the U.S. Atlantic Coast, Environmental Research Letters 4 044008. (doi: 10.1088/1748-9326/4/4/044008).
Online_Linkage:
<http://risingseas.net/ERL/data.html>
Description:
Abstract:
Climate change is likely to accelerate the historical rise in sea level, leading to a wide range of impacts on development, wetland resources, and recreation in the U.S. coastal zone. Relative sea level (i.e., the net impact of sea and land level changes) is already rising in most parts of the U.S. The UN Intergovernmental Panel on Climate Change concluded in 1996 that increases in global temperatures over the next century could accelerate the historical rate of sea level rise to an average of about 5 mm/yr (or 50 cm/century). Low-lying and higher elevation lands along the coast may also be threatened by other coastal hazards such as erosion and storms.

The impacts of this increase in sea level, will vary from place-to-place and depend on a range of factors, including the human response. To initiate a national assessment of sea level rise impacts, the U.S. Environmental Protection Agency (EPA) is working with state, county, and local officials to identify the lands likely to receive shoreline protection. Those judgments incorporate state policies and regulations, local concerns, land-use data, and general planning judgment. The resulting data distinguishes areas likely to receive shoreline protection (e.g., beach nourishment and armoring with seawalls or dikes) from the areas where shores will probably retreat naturally, either because the cost of holding back the sea is greater than the value of the land, or because there is a current policy of allowing the shore to retreat. This data should be used in conjunction with information contained in the corresponding planning report ("Assessment of Sea Level Rise Response Scenarios in New York").

Purpose:
This data and the accompanying report are part of a national effort by EPA to encourage the long-term thinking required to deal with the impacts of sea level rise. The nature of rising sea level prevents the issue from being a top priority; but it does give us time to reflect upon how to address the impacts. Maps that illustrate the areas that might ultimately be submerged convey a sense of what is at stake, but they also leave people with the impression that submergence is beyond their control. Maps that illustrate alternative visions of the future may promote a more constructive dialogue.

Through the development of data on the likelihood of shoreline protection, this research seeks to (1) improve future assessments of the impacts of climate change through incorporation of a richer understanding of local land use policies and trends; (2) improve the understanding among federal, state, and local levels of government on the effect of current coastal policies on coastal development and conservation; and (3) identify opportunities for policy refinement to facilitate a more efficient response to rising seas that limits the impact on coastal property, wetlands, and recreational resources.

For more information on the goals of the study and this data set, please refer to the Introduction section of the report.

Supplemental_Information:
When displaying the data, the study authors recommend using the corresponding layer file to ensure that the classifications display in the same way as all print maps created for this study. For instance, brown is used to designate lands where shore protection is almost certain (red designates shore protection likely, blue designates shore protection unlikely, and light green designates no shore protection). Users should store the layer file and associated GIS data in the same folder and then can add the layer file to an ArcGIS project.

Users should display wetlands and the outside-of-study-area layers on top of this data set. This study generally focused on dry land that is either below the 3.5 meter contour or within 1000 feet of the shore. In the case of Nassau County, however, the study area was limited to dry land within the 500 year floodplain (as a result of the limited data provided by the County). The response data for lands located outside of the study area or beneath non-tidal wetlands is typically misleading and has not been reviewed. Wetlands data and the outside-of-study-area data layers are available separately.

For additional information on sea level rise planning, see EPA publications available at: <http://risingsea.net/ERL> or <http://risingsea.net/ERL/NY.html> or <http://plan.risingsea.net>

Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: January 2006
Currentness_Reference: Completion of Draft Report for CCSP Review
Status:
Progress: In work
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -74.261770
East_Bounding_Coordinate: -71.787790
North_Bounding_Coordinate: 41.654743
South_Bounding_Coordinate: 40.116288
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme:
Theme_Keyword: Sea Level Rise
Theme_Keyword: Climate Change
Theme_Keyword: Land Use Planning
Theme_Keyword: Shoreline Armoring
Theme_Keyword: Beach Nourishment
Theme_Keyword: Wetland
Place:
Place_Keyword_Thesaurus: Geographic Names Information System
Place_Keyword: New York NY
Access_Constraints:
Use_Constraints:
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: James G. Titus
Contact_Organization: Environmental Protection Agency, Climate Change Division
Contact_Position: Project Manager
Contact_Address:
Address_Type: mailing address
Address: 1310 L St., N. W.
Address: Mail Code: 6207J
City: Washington
State_or_Province: DC
Postal_Code: 20460
Contact_Voice_Telephone: 202-343-9307
Contact_Facsimile_Telephone: 202-343-2338
Contact_Electronic_Mail_Address: Titus.Jim@epa.gov
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
The underlying data used in the creation of this layer may contain errors or omissions. In addition, site-specific changes made during the course of this study to correct those errors may have added other errors. (For example, we examined recent information to correct for development that took place after the source data was created.)
Logical_Consistency_Report:
Refer to the accompanying planning report for information on the publication date for data and procedures used in the development of this layer.
Completeness_Report:
This layer is based upon land use data available during the study development and may not accurately portray recent events. To the extent possible, the data developers and project manager compared the resulting layer with aerial photos, road, and other supplementary information to identify and correct areas that the raw data misidentified.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Because our maps are based on decision rules and previously published data, the horizontal resolution at which one should reasonably display our maps is limited by the precision of the input data. Because the quality of that data varies for different localities, so does the scale at which these maps ought to be depicted.

For Suffolk and Nassau County, the counties' parcel data served as the core data source (Suffolk's data has a scale of 1:2,400 and Nassau's data has a scale of 1:800). The state wetland data has a scale of 1:2,400. Stakeholder review changes were implemented using the existing boundaries of the parcel data. A small number of final review changes required site-specific editing of the existing polygons; however, there were a minimal number of these changes and the resulting scale of the data should not have been degraded significantly. We recommend that users treat both the data for these counties as having a scale of better than 1:24,000.

For the five New York City Boroughs (Kings, Queens, Manhattan, Staten Island, and Bronx), we used 1995 Land Use data with a scale of 1:66,360. The state wetland data has a scale of 1:2,400. Stakeholder and final review changes were generally implemented using the existing boundaries of the land use data. A small number of final review changes were made based on hand edits made on 1:100,000 scale maps; with changes generally based on road layers with a scale of 1:24,000 or better. Therefore, we recommend that users treat the data for New York City as having a scale better than 1:100,000 or better.

For Westchester County, we used 1996 Land Use data provided by the county, which has a scale of 1:24,000. The state wetland data has a scale of 1:2,400. Stakeholder and final review changes were generally implemented using the existing boundaries of the land use data. A small number of final review changes were made based on hand edits made on 1:100,000 scale maps; however, these edits were not sufficiently numerous so as to deteriorate the scale to worse than 1:50,000. Therefore, we recommend that users treat both these data sets as having a scale of 1:50,000 or better.

Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report: NA
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: ICF Consulting
Title: Study Area
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
ICF Consulting created layer using USGS maps based on the National Geodetic Vertical Datum (NGVD) of 1929.
Source_Scale_Denominator: 1:24,000
Source_Contribution:
Defines landward-boundary of study area by identifying lands that are higher than 3.5 meters in elevation or within 1,000 feet of mean high water based on tidal wetlands data.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Suffolk County Planning Department
Publication_Date:
1991 for Huntington, Babylon, Islip, Smithtown and Brookhaven; 1999 for all eastern towns
Title: Suffolk County Parcel Data
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:2,400
Source_Contribution: Delineates parcel boundaries for Suffolk County
Source_Information:
Source_Citation:
Citation_Information:
Originator: Nassau County GIS Department
Publication_Date: 2002
Title: Nassau County Bulkheads
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:800
Source_Contribution: Identifies location of bulkheads for Nassau county
Source_Information:
Source_Citation:
Citation_Information:
Publication_Date: 2002
Title: Nassau County Land Use Features
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
In the absence of parcel boundary information and considering the high population density along coastal areas in Nassau County, all unidentified lands within the study area were considered to be developed (and therefore classified as "Certain to be Protected" unless otherwise specified).
Source_Scale_Denominator: 1:800
Source_Contribution:
Delineates features including parks, planimetric features (such as buildings, recreational facilities, parking lots, cemeteries, etc.), major roads, and displays parcel centroids.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Department of City Planning, New York City
Publication_Date: 1995
Title: Land Use for New York City
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Where necessary, information on vacant parcel ownership was obtained through the New York Open Space Accessible Space Information System http://www.oasisnyc.net>.
Source_Scale_Denominator: 1:66,360
Source_Contribution:
Identifies coastal Land Use within New York City (Boroughs of Brooklyn, Queens, Manhattan, Staten Island, and Bronx)
Source_Information:
Source_Citation:
Citation_Information:
Originator: Westchester County Department of Planning
Publication_Date: 1996
Title: Land Use for Weschester County
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:24,000
Source_Contribution: Generalized Land Use for Westchester County
Source_Information:
Source_Citation:
Citation_Information:
Originator: New York State Department of Environmental Conservation
Publication_Date: 1998-2000
Title: Shinnecock Bay Tidal Wetlands 1974
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details: Based on 1974 aerial photography of area
Source_Scale_Denominator: 1:2,400
Source_Contribution: Tidal wetlands data for Shinnecock Bay.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
New York State Department of State (Division of Coastal Resources)
Publication_Date: early 1990's
Title: NYSDOS Wetlands data
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Based on 1974 aerial photography of area (same as NYSDEC wetlands information).
Source_Scale_Denominator: 1:2,400
Source_Contribution: NYSDOS wetlands data
Source_Information:
Source_Citation:
Citation_Information:
Originator: New York State Department of Environmental Conservation
Publication_Date: 2000
Title: Draft Tidal Wetlands Jamaica Bay 1974
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:2,400
Source_Contribution: Draft Tidal Wetlands data for Jamaica Bay.
Source_Information:
Source_Citation:
Citation_Information:
Originator: New York State Department Of Environmental Conservation
Publication_Date: 2000
Title: Draft Tidal Wetlands New York City 1974
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:2,400
Source_Contribution:
Draft Tidal Wetlands of New York City (Burroughs of Brooklyn, Queens, Manhattan, Staten Island, and Bronx).
Source_Information:
Source_Citation:
Citation_Information:
Originator: New York State Department Of Environmental Conservation
Publication_Date: 2000
Title: Tidal Wetlands Index Map 5 1974
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 1:2,400
Source_Contribution: Tidal Wetlands Index Map
Process_Step:
Process_Description:
Step 1: Define Study Area

The first step in creating the draft maps was to define the study area. The intention was to include all dry lands either below the 20-foot elevation contour from the USGS 1:24,000 scale maps, or within 1000 feet of the shore (to account for possible erosion). Although the study area might seem over inclusive, the authors do not want the study to be limited to a specific estimate of projected rise in sea levels; instead, the results of the sea level planning studies should apply to the general impact of sea level rise regardless of the extent. Nevertheless, the authors lacked a readily available data set based on the USGS 20-foot contour when they began the study. Therefore, for New York City and Suffolk County, Daniel Hudgens of Industrial Economics provided a study-area based on the 3.5-meter contour from Titus and Richman (2001) plus all land within 1000 feet of the tidal wetlands. Jue Wang of ICF Incorporated later provided as mask based on the 20-foot USGS contour for Westchester County, which was undertaken last.

The Nassau County study area, was defined by all areas within the 500-year flood plain. The study area for this county was more limited because the parcel data provided by the county was limited to the flood plain.

Process_Step:
Process_Description:
Step 2: Consultations with State and Local Planners

To better understand New York's likely sea level rise responses, Jay Tanski researched relevant laws and regulations and conducted interviews with state and local managers and planners familiar with coastal regulations as well as land use patterns and trends. Managers received an overview and summary of the project purpose and goals prior to the meetings.

Tanski asked the managers to consider lands potentially vulnerable to sea level rise on a relatively generic basis. To focus discussions during the interview, he provided digital maps depicting inundation zones associated with Category 1, 2, and 3 hurricanes based on the SLOSH numerical model developed by the National Weather Service to indicate areas already vulnerable to flooding and erosion hazards.

Consultations revealed which factors determined lands likely be protected versus those likely to be abandoned as sea level rises. Also, they highlighted area-specific concerns and provided direction as to where potential modifications were advisable in relation to what geospatial information suggested.

Process_Step:
Process_Description:
Step 3: Identify "Decision Rules" for Mapping Shoreline Protection

Statewide land use data that provided the resolution and level of detail needed for this analysis was not readily available during the time of the study. The most up to date and comprehensive information was collected and maintained at the county level.

For Nassau County, shoreline protection designations were based on parcel centroids (point files) that identified public versus private lands and land use. Consequently, developed areas were interpolated using the location of the parcel centroids in relation to existing polygon layers (delineating parks, buildings, roads, and other planimetric features).

Shoreline protection designations for New York City (boroughs of Brooklyn, Queens, Manhattan, Staten Island, and Bronx) were based on a 1995 land use map provided by the New York City Department of City Planning. In order to transfer the map (stored as a .tif file) into a workable GIS layer, the map was first digitized using a large format, 2400dpi UMAX Scanner and then rectified using ESRI's Network Analyst software. Where necessary, information on vacant parcel ownership was obtained manually through the New York City Open Accessible Space Information System (http://www.oasisnyc.net).

For Suffolk County and Westchester County, Jay Tanski was able to use the data provided by the counties without further modification. He differentiated the shoreline protection designations based upon the land use categories provided by the data.

Initially, when mapping the sea level rise responses Jay Tanski used three sea level rise scenarios (except for Westchester County). The first scenario identifies lands for which local policies and practices allow protection. The second identifies land that planners feel is likely to be protected. The third scenario uses the second scenario as a starting point, but assumes greater efforts would be undertaken to preserve natural resources (e.g., tidal wetlands) or protect historical structures.

All lands within the study area were assigned a protection designation based on applying the aforementioned "decision rules" to the available GIS layers. These "decision rules" (as outlined in Process Step 2) were the product of the planners' general assumptions regarding land use development and protection efforts (please note that these rules do not represent their official position on the likelihood of protection for specific areas).

Wetlands data for the New York shoreline were provided by two sources, the New York State Department of Conservation (NYSDEC) and New York State Department of State (NYSDOS). The NYSDEC wetland data only includes the areas from Moriches Bay to Montauk on the south shore and Gardiners Bay between the forks. NYSDOS maps highlighted wetlands along the south shore estuary. Although Westchester County provided its own wetlands data on its county data clearinghouse webpage, it originates from the same wetland maps used by NYSDEC. Upon data capture, wetlands information was clipped and reflected onto the study area.

Specific data sets and the procedures used for processing and analyzing the information are described in greater depth for each county in the appropriate section of the planning report.

Process_Step:
Process_Description:
Step 4: Conversion of scenario-based responses to anticipated likelihood of shoreline protection

In 2001, the EPA project manager realized that it would be possible to display all three scenarios on a single map, without losing any information, because the lands protected in scenario 3 were always protected in scenario 2, and the lands protected in scenario 2 were always protected in scenario 1. Therefore, the Project Manager defined lands protected in all three scenarios as "shore protection almost certain"; lands protected under scenarios 1 and 2 as "shore protection likely", and lands protected under scenario 1 as "shore protection unlikely." Lands not protected under any scenario were defined as "no protection". Although the interviews were conducted in [year], New York Seagrant?s contract with Industrial Economics for Suffolk, Nassau, and New York City was based on the pre-2001 formulation of the study. During 2004, based upon guidance from Daniel Hudgens of Industrial Economics, Tanski modified the maps to use a single map with multiple colors that represent the varying likelihoods of shoreline protection. For more details, users should refer to the planning report. The Westchester County portion of the study was conducted in 2004.

Process_Step:
Process_Description:
Step 5: Integrate stakeholder reviews changes

Jay Tanski conducted an additional consultation with relevant planners at the county level to review the final response map and draft report. Prior to the review, all parties received and reviewed copies of the draft report and map. These consultations verified previous modifications and, in some cases, provided further changes to reflect recent development.

To implement the stakeholder review changes, Jay Tanski selected the individual parcel or land use polygons identified by the planners and then revised the attributes as necessary.

Process_Step:
Process_Description:
Step 6: Data transfer

For all localities with the exception of Nassau County, Jay Tanski provided Kevin Wright of ICF Consulting with the source data and ArcView project that identified the approach used to produce the maps.

For Nassau County, data license agreements prevented sharing the raw data. As a result, Tanski converted the resulting response maps for this County into a raster image and then provided this as a single layer to Wright. [Specify cell size of the raster image.]

Process_Step:
Process_Description:
Step 7: Integrate final review changes.

During this step, the EPA project manager performed a final review of the GIS data and planning report. This review sought to identify map changes that were still needed. These changes usually involved cases where the requested stakeholder review changes had not been implemented correctly, or the GIS data failed to recognize recent development or newly planned development and the resulting map showed an area as less likely to be protected than anticipated (for example, a recent development might show as unlikely to be protected because the land use data did not reflect the presence of residences that would likely protect their land if ever threatened).

Brit Poole and Kevin Wright of ICF Consulting made the necessary edits and incorporated the data into the GIS project. To implement these changes, Poole and Wright selected the associated polygon(s) that existed within the area and revised the likelihood of protection identified in the layer attributes. Afterwards, they added the new layers to the county project. When the boundaries of the site-specific change did not overlap with the boundaries of land use polygons, they used ArcGIS's edit functions. All edits were then implemented through heads-up digitizing using ArcGIS software.

The fact that the review took place at a scale of approximately 1:100,000 could potentially reduce the resolution of our maps, if the reviewer changes were not as precise as the 1/50 inch assumed by National Map Accuracy Standards. We do not believe that the deterioration was significant. The types of changes that the officials sought were generally for relatively large areas corresponding to the size of parks and new communities. The primary source of error for these maps is not the precision of well-defined boundaries, but rather the uncertainty of how land use will evolve in undeveloped areas.

Process_Step:
Process_Description:
Step 8: Data finalization.

Kevin Wright and Brit Poole of ICF Consulting developed several geoprocessing models, using ESRI's Model Builder, to "flatten" the data into single state-wide files. The process of flattening the data involves combining or unioning each of the source data layers together to create the single file.

The models take the data layers that collectively create a state's sea level rise protection scenarios and flatten them into a single file. During the flattening process, all files are projected into an appropriate projection for the state. The models assign common attributes of shore protection, an appropriate source, whether or not it is military owned land, county name, state name, and if it is to override wetland data. Counties are flattened individually and then another model is used to combine all counties into a single state layer. Any edits that have been made to the protection scenarios are flattened and all attributes are verified.

Using this "flattened data", ICF created 1:100,000 "comparison maps" for the EPA manager to review. Those maps explicitly highlighted areas that had been erroneously masked (as wetland or high ground) during previous phases of the study, and hence not received the same level of scrutiny as most of the study area. We refer to areas erroneously excluded from the study area as ?unveiled? because they were erroneously masked. The comparison maps included 1:24,000 TIGER road layer data.

Process_Step:
Process_Description:
Step 9: Review of Comparison Maps

The project manager examined the comparison maps and made corrections for three reasons

First, , these maps used the out-of-study-area mask provided with this data set.((see data at <http://maps.risingsea.net/data.html>). The new data unveiled areas that had been covered by the draft elevation. The original mask was the 3.5-m contour from a 1:250,000 data set, while the new mask was based upon a 20ft contour from a 1:24,000 data set. . Unlike the other states, Tanski clipped his data along the outside of study area boundary. Therefore, no additional information was ?unveiled? with the corrected study area mask. [Is that true with NYC?]. Therefore, in most cases, the unveiled areas show as ?not considered?.

Second, projection shifts caused the study area to often be substantially narrower than 1000 feet in areas of high ground. The project manager examined gave these ?unveiled? areas scrutiny as well.

With a focus on the unveiled areas, the project manager looked for lands that would not be protected due to our decision rules?or showed up as not consideredbut would be inherently protected by the protection of nearby lands. For example, if a land area were shown as unlikely to be protected but surrounded by land almost certain to be protected, then the protection level for the surrounded polygon would be set to ?protection certain? to match the nearby area. If an area was on high ground (and thus only at risk of erosion), then land inland of areas likely to be protected are?at the very least?likely to be protected Along relatively high ground shores, where erosion is the primary risk, protecting shorefront developed lands has the direct effect of protecting undeveloped inland farms, whether or not protection is otherwise expected for that land use category. In lower areas, lands can be submerged from the back side even if shorefront homes are protected. For those areas, he edited the protection designation only if a polygon is entirely surrounded by land that are more likely to be protected.

Poole and Wright then implemented the final changes by selecting the corresponding polygons in the final response data and changing the source and scenario response fields accordingly.

Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: c:\TEMP\xml383.tmp

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 23387

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 29.500000
Standard_Parallel: 45.500000
Longitude_of_Central_Meridian: -96.000000
Latitude_of_Projection_Origin: 23.000000
False_Easting: 0.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000256
Ordinate_Resolution: 0.000256
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: NY_Protection_ScenariosAlb
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: OBJECTID
Attribute:
Attribute_Label: Source
Attribute_Definition:
Describes the information source used to identify the resulting protection scenario.
Attribute:
Attribute_Label: Scenario
Attribute_Definition: Delineates the likelihood of shoreline protection.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Shore Protection Certain
Enumerated_Domain_Value_Definition:
Identifies areas that will almost certainly be protected if and when the sea rises enough to threaten it (displayed as brown).
Enumerated_Domain:
Enumerated_Domain_Value: Shore Protection Likely
Enumerated_Domain_Value_Definition:
Identifies areas that will probably be protected, but where it is still reasonably possible that shores might retreat naturally if development patterns change or scientists were to demonstrate an ecological imperative to allow wetlands and beaches to migrate inland (displayed as red).
Enumerated_Domain:
Enumerated_Domain_Value: Shore Protection Unlikely
Enumerated_Domain_Value_Definition:
Identifies areas that probably will not be protected, generally because property values are unlikely to justify protection of private lands, but in some cases because managers of publicly owned lands are likely to choose not to hold back the sea (displayed as dark blue).
Enumerated_Domain:
Enumerated_Domain_Value: No Shore Protection
Enumerated_Domain_Value_Definition:
Identifies areas where existing policies would preclude holding back the sea. These areas include both publicly and privately owned lands held for conservation purposes (displayed as light green).
Enumerated_Domain:
Enumerated_Domain_Value: Outside of Study Area
Enumerated_Domain_Value_Definition:
Identifies land located outside of the area studied. Typically, land that is both over 20 ft NGVD in elevation and over 1000 feet from the shoreline is outside of the study area (displayed as white).
Enumerated_Domain:
Enumerated_Domain_Value: Open Water
Enumerated_Domain_Value_Definition:
Includes ocean water, bays, and lakes (displayed as light blue).
Enumerated_Domain:
Enumerated_Domain_Value: Tidal Wetlands
Enumerated_Domain_Value_Definition:
Typically, wetland areas are delineated using a separate layer; however, for some counties, wetlands delineated from land use data are included in this data (displayed as dark green).
Enumerated_Domain:
Enumerated_Domain_Value: Not Considered
Enumerated_Domain_Value_Definition:
Land area not analyzed during planning study. Generally more than 1000 feet from the shore and above the 3.5-meter 1:250,000 contour (Suffolk) or the 500-year flood plain (Nassau), but below the 20-ft NGVD USGS 1:24,000.
Attribute:
Attribute_Label: Military
Attribute_Definition: Identifies whether land is part of a military installation.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: N
Enumerated_Domain_Value_Definition: Land is not part of a military installation
Attribute:
Attribute_Label: State
Attribute_Definition: Identifies State covered by the data layer.
Attribute:
Attribute_Label: County
Attribute_Definition: Identifies county where the land area is located.
Attribute:
Attribute_Label: over_wet
Attribute_Definition:
Identifies whether planners indicate that the response data should display above wetland layers. Generally, wetlands should display above response data; however, in some cases wetlands may be developed or the wetland data may be deemed incorrect.
Overview_Description:
Entity_and_Attribute_Overview:
EPA recommends that users refer to the state planning report for information on the data categories and basis for using specific sources.
Entity_and_Attribute_Detail_Citation: See Entity_and_Attribute_Information

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
The dataset is being distributed by contractors of the US Environmental Protection Agency for the sole purpose of supporting the CCSP. Collaborators requiring such data should contact the EPA project manager, James G, Titus at 202-343-9307.
Resource_Description: Downloadable Data
Distribution_Liability:
Although this data was created under the direction of the EPA, no warranty expressed or implied is made regarding the accuracy or utility of the data. Neither EPA nor the data developers shall be held liable for improper or incorrect use of the data and information described and/or contained herein.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 45MB (Compressed)
Custom_Order_Process:
Data available to CCSP collaborators from James G. Titus at 202-343-9307.
Technical_Prerequisites: Requires software capable of displaying shapefile data.

Metadata_Reference_Information:
Metadata_Date: 20060202
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Industrial Economics, Incorporated
Contact_Person: John Herter
Contact_Address:
Address_Type: mailing address
Address: 2067 Massachusetts Ave.
City: Cambridge
State_or_Province: MA
Postal_Code: 02140
Contact_Voice_Telephone: 617-354-0074
Contact_Facsimile_Telephone: 617-354-0463
Contact_Electronic_Mail_Address: DHudgens@indecon.com
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.8.6 on Thu Feb 02 17:34:22 2006