Private Shoreline Stabilization Structures in Massachusetts, 2013

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: Massachusetts Office of Coastal Zone Management
Publication_Date: 20130614
Title:
Private Shoreline Stabilization Structures in Massachusetts, 2013
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: <http://www.mass.gov/czm/mapping/index.htm>
Description:
Abstract:
This feature class represents privately owned coastal protection structures for the Massachusetts shoreline. Only the ocean-facing shoreline was included in this project area, covering approximately 1,100 miles. The coastal protection structures included in the inventory were bulkhead/seawalls, revetments, groins, and sandbags. Structures were digitized using a heads-up approach based on a combination of aerial imagery and oblique aerial imagery covering the project area. Structure length and material was also determined this way. Elevations were assigned using LiDAR data. The feature class structure was designed to match the database of previous phases of the Massachusetts Coastal Infrastructure Inventory and Assessment project.
Purpose:
The structures feature class inventories the locations of privately owned coastal protection structures for the Massachusetts shoreline. These data are designed to supplement the 2009 Massachusetts Coastal Infrastructure Inventory and Assessment project database covering publically-owned coastal structures.
Time_Period_of_Content:
Time_Period_Information:
Multiple_Dates/Times:
Single_Date/Time:
Calendar_Date: 20130614
Single_Date/Time:
Calendar_Date: 20130614
Currentness_Reference: Ocean-facing coastline of Massachusetts.
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None planned
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -71.118466
East_Bounding_Coordinate: -69.914716
North_Bounding_Coordinate: 42.861911
South_Bounding_Coordinate: 41.253127
Keywords:
Theme:
Theme_Keyword_Thesaurus: Massachusetts Office of Coastal Zone Management
Theme_Keyword:
coastal protection, infrastructure, bulkhead, seawall, groin, jetty, revetment, rip-rap, sandbags, Chapter 91, elevation, height
Theme:
Theme_Keyword_Thesaurus:
NASA/Global Change Master Directory (GCMD) Earth Science Keywords. Version 8.0.0.0.0
Theme_Keyword:
EARTH SCIENCE SERVICES > DATA ANALYSIS AND VISUALIZATION > GEOGRAPHIC INFORMATION SYSTEMS
Theme_Keyword: EARTH SCIENCE > HUMAN DIMENSIONS > INFRASTRUCTURE
Theme_Keyword:
EARTH SCIENCE > LAND SURFACE > GEOMORPHOLOGY > COASTAL LANDFORMS/PROCESSES
Theme_Keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Categories
Theme_Keyword: oceans
Theme_Keyword: structure
Place:
Place_Keyword_Thesaurus: U.S. Board on Geographic Names
Place_Keyword: United States
Place_Keyword: Atlantic Ocean
Place_Keyword: Massachusetts
Place_Keyword: Cape Cod
Place_Keyword: Boston
Place_Keyword: Boston Harbor
Place_Keyword: Buzzards Bay
Place_Keyword: Nantucket Sound
Place_Keyword: Nantucket
Place_Keyword: Vineyard Sound
Place_Keyword: Elizabeth Islands
Place_Keyword: Martha's Vineyard
Place_Keyword: Cape Cod Bay
Place_Keyword: Massachusetts Bay
Place:
Place_Keyword_Thesaurus:
NASA/Global Change Master Directory (GCMD) Location Keywords. Version 8.0.0.0.0
Place_Keyword:
Continent > North America > United States of America > Massachusetts
Place_Keyword: Ocean > Atlantic Ocean > North Atlantic Ocean
Place_Keyword: Ocean > Atlantic Ocean > North Atlantic Ocean > Gulf Of Maine
Access_Constraints:
None. These data are in the public domain. GIS files are freely available for download.
Use_Constraints:
Public domain data from the Massachusetts Office of Coastal Zone Management (CZM), an agency of the Commonwealth of Massachusetts Executive Office of Energy and Environmental Affairs (EEA), are freely redistributable with proper metadata and source attribution. Please recognize the Massachusetts Office of Coastal Zone Management as the source of these data. You are not permitted to use CZM's name or to suggest that CZM endorses your project or product, without its express written consent. While efforts have been made to ensure that these data are accurate and reliable within the state of the art, CZM cannot assume liability for any damages or misrepresentation caused by any inaccuracies in the data or as a result of changes to the data caused by system transfers. The user must be aware of data conditions and bear responsibility for the appropriate use of these data with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to these data.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Massachusetts Office of Coastal Zone Management
Contact_Position: CZM Data Manager
Contact_Address:
Address_Type: mailing and physical
Address: 251 Causeway Street, Suite 800
City: Boston
State_or_Province: MA
Postal_Code: 02114-2138
Country: US
Contact_Voice_Telephone: 617-626-1200
Contact_Facsimile_Telephone: 617-626-1240
Contact_Electronic_Mail_Address: czm@state.ma.us
Hours_of_Service: 0900 hrs to 1600 hrs EST
Contact_Instructions: email preferred
Data_Set_Credit:
These spatial data were created by the Massachusetts Office of Coastal Zone Management (CZM) for the Massachusetts Executive Office of Energy and Environmental Affairs (EEA).
Native_Data_Set_Environment:
Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.1.3143
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
A formal quantitative attribute accuracy report was not conducted for these data.
Logical_Consistency_Report:
A logical consistency report was not conducted for these data, however, the data were entered into an ArcGIS File Geodatabase as a polyline feature class. To ensure data integrity, the database and feature class were created using a subtype and domain architecture.
Completeness_Report:
All digitizing was completed by a single GIS analyst. After initial digitization, the entire dataset was reviewed by a separate analyst, ensuring logical consistency throughout the QAQC process. Any feature still in question after QAQC was and examined by CZM geologists prior to completion of the structure database. Each question was resolved by CZM staff and all validated features were incorporated into the final structures layer.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Positional accuracy was not enumerated. Absolute positional accuracy may be estimated by adding heads-up digitizing error to that inherited from the source imagery including 2008/2009 USGS color ortho imagery, LIDAR datasets collected between 2002 and 2011, Massachusetts oblique imagery (Pictometry), Bing 'Bird's Eye' imagery, and Chapter 91 licenses and points.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: MassGIS, MassGIS
Publication_Date: 20090321
Title: USGS Color Ortho Imagery (2008/2009)
Online_Linkage:
<http://www.mass.gov/anf/research-and-tech/it-serv-and-support/application-serv/office-of-geographic-information-massgis/datalayers/colororthos2008.html>
Type_of_Source_Media: hardDisk
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20080321
Ending_Date: 20090321
Source_Currentness_Reference: Tiles covering the entire coastline of Massachusetts were used.
Source_Citation_Abbreviation: USGS Color Ortho Imagery (2008/2009)
Source_Contribution:
MassGIS Data - USGS Color Ortho Imagery (2008/2009) Aerial photography for the entire state of Massachusetts acquired from 2008 and 2009 by the U.S. Geological Survey (USGS). The imagery had a resolution of either 15 or 30 cm. This imagery was used as the reference for digitizing structures, as well as a source for locating structures and their attributes.
Source_Information:
Source_Citation:
Citation_Information:
Originator: MassGIS, MassGIS
Publication_Date: 20130516
Title: LiDAR Terrain Data
Type_of_Source_Media: hardDisk
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20020401
Ending_Date: 20110507
Source_Currentness_Reference: Tiles covering the entire coastline of Massachusetts were used.
Source_Citation_Abbreviation: LiDAR Terrain Data
Source_Contribution:
MassGIS Data - LiDAR Terrain Data LiDAR Digital Elevation Models (DEMs) from the entire state of Massachusetts based on data that was collected from 2002 to 2011 by various state agencies or partnerships. The following eight datasets were used: 2002 Boston Area, 2006 Bristol, 2006 Plymouth South, 2009 City of Boston, 2010 FEMA Quincy, 2010 FEMA Dukes, 2010 FEMA Nantucket, and 2011 LiDAR for the Northeast. The LiDAR DEMs were used to assign elevations to structures.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Massachusetts Department of Transportation, Massachusetts Department of Transportation
Publication_Date: 20081231
Title: Oblique Aerial Imagery
Online_Linkage:
<http://www.massdot.state.ma.us/planning/Main/MapsDataandReports/Maps/InteractiveMaps/Pictometry.aspx>
Type_of_Source_Media: onLine
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20081231
Source_Currentness_Reference: Tiles covering the entire coastline of Massachusetts were used.
Source_Citation_Abbreviation: Oblique Aerial Imagery
Source_Contribution:
MassDOT - Oblique Aerial Imagery The Massachusetts Department of Transportation (MassDOT) has compiled a library of digital color oblique images for the whole state. The images were captured in 2008, have an 8 inch resolution and are taken at approximately a 45° angle. This imagery was the main source used for identifying coastal structures and for determining their material.
Source_Information:
Source_Citation:
Citation_Information:
Originator: BING, BING
Publication_Date: 20130614
Title: BING Maps
Online_Linkage: <http://www.bing.com/maps/>
Type_of_Source_Media: onLine
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20130614
Source_Currentness_Reference: Tiles covering the entire coastline of Massachusetts were used.
Source_Citation_Abbreviation: BING Maps
Source_Contribution:
BING Maps Birds Eye imagery from Microsoft Bing Maps. This imagery was used as a secondary source for identifying coastal structures and determining their material.
Source_Information:
Source_Citation:
Citation_Information:
Originator: MassGIS, MassGIS
Publication_Date: 20130606
Title: Parcel Data
Type_of_Source_Media: onLine
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20130606
Source_Currentness_Reference: Tiles covering the entire coastline of Massachusetts were used.
Source_Citation_Abbreviation: Parcel Data
Source_Contribution:
MassGIS Data - Parcel Data GIS tax parcels hosted by MassGIS were used to generate IDs for each structure. Each town is responsible for building and maintaining their own dataset, but all datasets are made available by MassGIS for download.
Process_Step:
Process_Description:
DIGITIZATION OF STRUCTURES Man-made features designed to stabilize the shoreline or reduce coastal storm impacts were considered for this inventory. Coastal structures were digitized as polyline features from imagery using a “heads-up” approach. All geographic features were identified and manually traced in ArcGIS using the 2008/2009 USGS Color Ortho Imagery as a reference dataset. Digitizing was done at a minimum scale of 1:2,500, but typically at larger scale. A description of the general work flow follows. All coastal structures were digitized in the Massachusetts State Plane Coordinate System, Mainland Zone, NAD83, meters.
Typically, structures were identified using a combination of the oblique imagery sources (MassDOT and Bing). Given their high resolution and oblique perspective, these sources were also often used to determine structure type and material. The feature was then digitized using the ortho imagery for reference. For bulkheads and seawalls, the polyline was typically digitized along the top of the structure. For revetments, the line was digitized at the landward edge of the structure (presumed to be the highest point). For groins and jetties, a line along the center of each structure was digitized. Multiple imagery datasets were used to ensure that structures were digitized at their maximum elevation, however the final location of the structure was always digitized using the 2008/2009 USGS imagery.
As structures were located and digitized, the primary structure type and its materials were identified and recorded. For features that consist of multiple structure types and materials (for example, a bulkhead or seawall with a revetment in front), a secondary structure type and material was also recorded. For these structures, the landward feature was assigned as the primary structure and the seaward (typically lower) feature was assigned as the secondary structure.
Structures were digitized into an ArcGIS File Geodatabase (FGDB) polyline feature class. To ensure data integrity, the database and feature class were created using a subtype and domain architecture. Subtypes are used to categorize data using an attribute field. For the coastal structures feature class, a subtype was created for the PrimaryType field. This subtype allowed only the following values to be assigned as primary type: 1. Bulkhead/Seawall 2. Revetment 3. SandBags 4. Groin/Jetty For each of the four subtypes defined for the PrimaryType field, default values or domains were created for the PrimaryMaterial field. For the ‘Bulkhead/Seawall’, ‘Revetment’, and ‘Groin/Jetty’ subtypes, domains with allowable materials for each of those features were created. The ‘SandBag’ subtype has a default material of ‘Sandbags’.
The SeconaryType field also contains domains for each PrimaryType subtype; these domains constrained the type of secondary structure that could be associated with each primary structure. The SecondaryMaterial field contained a single domain listing all allowable materials.
Use of the field domain and subtype approach served two purposes. First, it ensured that only valid entries were assigned to each field, for example: • only pre-defined structure types could be entered in the StructureType field; • the structure materials were limited based on structure type; • the secondary structure type was limited based on the primary structure type. In addition, this approach greatly simplified the digitizing process. An editing template was created, which allowed the GIS analyst to quickly select the primary type/material combination from a list of features. Based on the selection, the primary type and material attributes were set automatically as the feature was digitized. Secondary types and materials were selected from the same predefined lists when encountered.
Structures were digitized into an ArcGIS File Geodatabase (FGDB) polyline feature class. To ensure data integrity, the database and feature class were created using a subtype and domain architecture. Subtypes are used to categorize data using an attribute field. For the coastal structures feature class, a subtype was created for the PrimaryType field. This subtype allowed only the following values to be assigned as primary type: 5. Bulkhead/Seawall 6. Revetment 7. SandBags 8. Groin/Jetty
For each of the four subtypes defined for the PrimaryType field, default values or domains were created for the PrimaryMaterial field. For the ‘Bulkhead/Seawall’, ‘Revetment’, and ‘Groin/Jetty’ subtypes, domains with allowable materials for each of those features were created. The ‘SandBag’ subtype has a default material of ‘Sandbags’.
The SeconaryType field also contains domains for each PrimaryType subtype; these domains constrained the type of secondary structure that could be associated with each primary structure. The SecondaryMaterial field contained a single domain listing all allowable materials. Primary (landward) and secondary (seaward) types were mainly identified using the oblique aerial imagery. The primary structure type was stored in the PrimaryType field and the secondary structure type in the SecondaryType field. The structure material was also primarily determined using the oblique aerial imagery. The construction material was recorded for the primary structure type and if present the secondary structure type. The primary structure material was stored in the field named PrimaryMaterial and the secondary structure material in the SecondaryMaterial field.
STRUCTURE LENGTH ATTRIBUTION In FGDBs, ArcGIS automatically stores the length of each polyline feature (in the horizontal units of the layer’s coordinate system) in a field called Shape_Length. Given the requirement to use the Massachusetts State Plane Coordinate System, the units of the Shape¬_Length field are in meters. Using the values in the Shape_Length field, each structure’s length in meters was converted to feet and rounded the nearest foot. This value was stored in the Structure_Length field.
STRUCTURE ID Every coastal protection structure received a unique identifier (ID) based on tax parcel data. The first 12 digits of the ID string correspond to a combination of the town, map, block, and lot number for the nearest parcel. An additional sequential number was appended to ensure the ID was unique for cases where multiple structures occur on the same tax parcel. The ID format matches those from previous phases of the inventory. Each part of the structure ID is separated by a hyphen (“-“).
STRUCTURE ELEVATION ATTRIBUTION Attribution of structures with a single (maximum) elevation value requires careful consideration of each data source, its accuracy, and precision. For example: 1. Because structures are digitized using ortho imagery as a base layer, the alignment of these features with LiDAR is limited by the precision between the imagery and elevation datasets. 2. Most coastal structures do not maintain a consistent elevation for their full length, thus simply extracting an elevation at a point along the linear feature would not necessarily be the most representative elevation for the top of the structure.
Two automated processes were designed to extract the elevations for each structure. One process was developed to assign elevations to shore-parallel structures, and another was used for shore-perpendicular structures (groin and jetties). Each process is described below. All structures were not assigned an elevation. In some areas, the LiDAR data extended only a short distance from the coast and did not intersect with structures situated at or seaward of the shoreline.
SHORE-PARALLEL STRUCTURE ATTRIBUTION For shore-parallel structures, the majority of elevations were generated by creating profile lines and extracting elevations. A series of profile lines was cast perpendicular to each structure. Elevations from the corresponding LiDAR dataset were extracted along each of the profile lines. The maximum elevation of each profile was chosen to represent the structure elevation at that transect. The profile maximums were then averaged to give the structure elevation. Using this approach ensured that 1) a representative elevation was chosen for each structure regardless of any potential misalignment with the DEM, and 2) that the structure elevation value accounted for variability in elevations along each structure.
For each structure, profile lines were created with variable spacing. The spacing interval was designed to not exceed 5 meters. Each profile line was automatically extended from 50 meters in the seaward direction to 2 meters in the landward direction, perpendicular to the structure. Elevations were extracted along these lines at 1 meter intervals (the minimum resolution of the LiDAR data), for a total of 53 elevation points per profile line. In cases where some or all of the elevation points were not covered by the LiDAR DEMs, these points were excluded from analysis. Two limits were put in place to exclude potentially invalid data from the analysis: 1. If the maximum elevation along a given profile was not within 3 meters of the location of the structure, the profile was excluded. 2. Each structure was required to have at least 3 valid profiles for averaging.
Using this approach, 4,248 of the 4,700 shore-parallel structures were successfully assigned an elevation. The rules above were modified for the remaining 452 structures that had too few or no valid profile lines. The steps below were performed in order to assign elevations to as many structures as possible. 1. For each profile, the maximum elevation within 3 meters of the structure was calculated. This excluded the influence of any natural coastal features and/or infrastructure outside of the immediate vicinity of the structure. 2. The minimum requirement for number of profiles was removed. Any structure with at least one profile was assigned an elevation. Collectively, these two changes produced valid elevations for an additional 382 structures. For the remaining 70 structures, cross-shore profiles were manually digitized (3 per structure). Elevations were extracted at 1 meter intervals and the maximum elevation of each profile was averaged to represent the structure. Each profile was manually reviewed to ensure that the maximum elevation was representative of the coastal structure. An additional 69 structures were assigned an elevation using this approach.
SHORE-PERPENDICULAR STRUCTURE ATTRIBUTION For all shore-perpendicular structures (groins and jetties), elevations were extracted directly from the digitized line at 1 meter intervals between the seaward and landward edge of each structure. The maximum value was chosen to represent the structure elevation. In a majority of cases, this was the most landward point along the structure.
Of the 1,991 cross-shore structures, 34 were not assigned an elevation. These structures were located completely outside of the LiDAR data coverage. Another 223 structures were only partially overlapped by the LiDAR dataset. In the case of partial coverage, an elevation was still generated based on the maximum elevation encountered.
Groins and jetties that are physically tied into a shore-parallel structure (seawall or revetment) at their landward edge were snapped to the shore-parallel structure during the digitization process to connect the two features. This may result in some anomalously high elevations for groins and jetties in the final database, particularly for locations where there are substantial height differences between the groin/jetty and the seawall or revetment to which it is connected.
STRUCTURE HEIGHT ATTRIBUTION In addition to structure elevation, the above-ground height was estimated for coastal structures. Because height is measured relative to the true ground surface (as opposed to an orthometric datum), structure heights were determined from engineering plans and other descriptions that were included as part of the Chapter 91 license documents, as opposed to LiDAR data. The height of structures was determined by comparing the structure elevation with the ground surface elevation on the seaward side of the structure. Because of the relative scarcity of this information, only 5% of digitized structures were attributed with height information. The existing database schema contained two fields for recording structure heights, PrimaryHeight and SecondaryHeight. Following the organization of previous studies, structure heights were typically entered in ranges of 5 feet, however, some structure plans listed multiple heights that spanned more than one 5-foot height range. For these cases, the complete range of heights was entered, where the minimum and maximum values were maintained in multiples of 5 feet (e.g., a structure with a height range of 3-7 feet would be assigned a height value 0-10 ft).
OWNERSHIP ATTRIBUTION For all structures the PropertyOwnerDesc and StructureOwnerDesc fields were set to “Private”. The individual owners of structures were not determined. The PropertyOwner and StructureOwner fields, which store a code for ownership, were all set to “1” (corresponding to private ownership).
STRUCTURE COORDINATE ATTRIBUTION The structure location was saved as an attribute using latitude and longitude fields. The PositionX field stores the longitude and the PositionY field stores the latitude. Both coordinates are stored as decimal degrees. The coordinates were calculated using the ArcGIS mid-point function to calculate the mid-point of each structure, this ensures that the coordinates always fall on the line, regardless of its shape.
ASSOCIATING CHAPTER 91 LICENSES WITH STRUCTURES The license shapefile provided by the Massachusetts Department of Environmental Protection (MassDEP) contains records for more than 5,600 Chapter 91 licenses that extend throughout the Commonwealth of Massachusetts. The location of each license is based on a geocoded address, which may not represent the exact location of the licensed structure. To identify licenses within the project area, the following steps were used to filter the data. 1. The shapefile was filtered based on the structure location. Licenses greater than 2 km from the project shoreline were removed, bringing the number of records to 3,118; 2. The shapefile was filtered based on the type of structures covered. Only licenses for relevant structure types were retained. Due to the large number of unclassified licenses, fields that were unfilled or unknown were also saved. This filtering reduced the total number of valid records to 1,497. Paper copies of each license were obtained from the MassDEP archive and scanned to .PDF files. A total of 1,399 licenses were retrieved from the archive; the remaining 98 files were not located in the archive.
Each license was then manually linked to the corresponding digitized structure. By comparing license plans with tax parcel data, a parcel was identified for each license. Typically the license point and tax parcel were close to each other, although some were significantly apart. Several of the licenses covered structures that were outside of the project scope (structures inside bays and estuaries, and up rivers). These licenses were removed from further consideration. Licenses that were found to correspond to private coastal protection structures within the project area were reviewed and the following information was recorded for each license: • Structure IDs – a single license frequently included multiple digitized structures. Each structure present in the plans was recorded. Even if a license only applied to a specific feature, such as a dock, other relevant structures clearly shown and labeled in the plans were included. • Elevation(s) – the elevation of each structure (in feet) was recorded when present. If multiple elevations were listed for a single structure, the full range was recorded. In some instances the elevation was estimated using a vertical scale bar or other scaled features. In these cases the elevation was flagged as ‘estimated’. • Datum – the vertical datum was recorded (when listed in the plans). • Height(s) – the height of each structure (above the ground surface) was recorded when listed or when it could be interpreted from the plans. The exact height was typically not listed. In most cases, heights were estimated by comparing the elevation at the top and the base of each structure. In cases where the structure base elevation was not provided, the base elevation was estimated and the height range was recorded as estimated. In other cases the height was estimated using the scale bar included with the plans. • Notes – Any interesting features in the plans were also recorded. Frequently these notes include any observed discrepancies between the structure type or material listed in the plans, and what was interpreted during the structure digitization.
Process_Date: 20130614
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 6564
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: NAD 1983 StatePlane Massachusetts Mainland FIPS 2001
Lambert_Conformal_Conic:
Standard_Parallel: 41.71666666666667
Standard_Parallel: 42.68333333333333
Longitude_of_Central_Meridian: -71.5
Latitude_of_Projection_Origin: 41.0
False_Easting: 200000.0
False_Northing: 750000.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.0001
Ordinate_Resolution: 0.0001
Planar_Distance_Units: meter
Geodetic_Model:
Horizontal_Datum_Name: D North American 1983
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: CSI_private
Entity_Type_Definition: Linear coastal structures locations and attribute information
Entity_Type_Definition_Source: multiple sources
Attribute:
Attribute_Label: OBJECTID
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: Geometry type of the features
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: STR_ID
Attribute_Definition: Structure ID field
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: ID
Attribute_Definition: Unique sequential ID for each structure.
Attribute_Definition_Source: Calculated
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Town
Attribute_Definition:
Name of the Massachusetts city or town in which the structure is located
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: StructureID
Attribute_Definition: Structure ID field
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Text - defined during data processing
Attribute:
Attribute_Label: CommunityNo
Attribute_Definition: Town identifier
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 001
Range_Domain_Maximum: 351
Attribute:
Attribute_Label: MapNo
Attribute_Definition:
Map Number. The assessor's tax parcel map number for the nearest tax parcel. If the structure was too far from a tax parcel, this was set to "000".
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: BlockNo
Attribute_Definition:
Block Number. The assessor's tax parcel block number for the nearest tax parcel. If the structure was too far from a tax parcel, or the tax parcel had no block number, this was set to "000".
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: ParcelNo
Attribute_Definition:
Parcel (lot) Number. The assessor's tax parcel lot number for the nearest tax parcel. If the structure was too far from a tax parcel, or the tax parcel had no lot number, this was set to "000".
Attribute_Definition_Source: MassGIS Data - Parcel Data
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: StructureNo
Attribute_Definition:
Structure Number. Numeric count of structures for each unique assessor's tax parcel. This number was used to make the Structure ID unique when multiple structures were located on the same tax parcel.
Attribute_Definition_Source: Calculated
Attribute_Domain_Values:
Unrepresentable_Domain: Sequential unique whole numbers.
Attribute:
Attribute_Label: PropertyOwner
Attribute_Definition:
Property owner code. Ownership was not evaluated for private structures, all values are set to 1 = private.
Attribute_Definition_Source: None
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: private
Enumerated_Domain_Value_Definition_Source: CZM
Attribute:
Attribute_Label: PropertyOwnerDesc
Attribute_Definition:
Property owner description. Ownership was not evaluated for private structures, all values are set to "private".
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: StructureOwner
Attribute_Definition:
Structure owner code. Ownership was not evaluated for private structures, all values are set to 1 = private.
Attribute_Definition_Source: None
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition: private
Enumerated_Domain_Value_Definition_Source: CZM
Attribute:
Attribute_Label: StructureOwnerDesc
Attribute_Definition:
Structure owner description. Ownership was not evaluated for private structures, all values are set to "private".
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: OwnerName
Attribute_Definition:
Owner's name. Ownership was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Location
Attribute_Definition:
Structure location description. Location was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: YearBuilt
Attribute_Definition:
Year structure was built. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: BasedOn
Attribute_Definition:
Source structure was based on. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: BasedOnDesc
Attribute_Definition:
Source description of what structure was based on. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: BasedOnComment
Attribute_Definition:
Comments of what structure was based on. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: PrimaryType
Attribute_Definition: Primary Structure Type.
Attribute_Definition_Source: Imagery
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Bulkhead/seawall
Enumerated_Domain_Value_Definition:
Shore-parallel vertical coastal engineering structure (often concrete or stone) separating land and water areas, primarily designed to prevent erosion and other damage by wave action (seawalls are typically more massive and capable of resisting greater wave forces than bulkheads)
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Revetment
Enumerated_Domain_Value_Definition:
A facing of stone, concrete, or other material used to protect an embankment or another coastal structure against erosion by wave action or currents.
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Groin/jetty
Enumerated_Domain_Value_Definition:
Coastal engineering structure typically oriented perpendicular to shore, used to prevent movement of sediments along the shore and/or to reduce longshore currents.
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Sandbags
Enumerated_Domain_Value_Definition:
Bags filled with sand or soil designed to stabilize the shoreline.
Enumerated_Domain_Value_Definition_Source:
Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Attribute:
Attribute_Label: SecondaryType
Attribute_Definition: Secondary Structure Type.
Attribute_Definition_Source: Imagery
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Bulkhead/seawall
Enumerated_Domain_Value_Definition:
Shore-parallel vertical coastal engineering structure (often concrete or stone) separating land and water areas, primarily designed to prevent erosion and other damage by wave action (seawalls are typically more massive and capable of resisting greater wave forces than bulkheads)
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Revetment
Enumerated_Domain_Value_Definition:
A facing of stone, concrete, or other material used to protect an embankment or another coastal structure against erosion by wave action or currents.
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Groin/jetty
Enumerated_Domain_Value_Definition:
Coastal engineering structure typically oriented perpendicular to shore, used to prevent movement of sediments along the shore and/or to reduce longshore currents.
Enumerated_Domain_Value_Definition_Source:
US Army Corps Coastal Engineering Manual (EM 1110-2-1100)/Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Enumerated_Domain:
Enumerated_Domain_Value: Sandbags
Enumerated_Domain_Value_Definition:
Bags filled with sand or soil designed to stabilize the shoreline.
Enumerated_Domain_Value_Definition_Source:
Massachusetts Executive Office of Energy and Environmental Affairs Office of Coastal Zone Management (MACZM)
Attribute:
Attribute_Label: PrimaryMaterial
Attribute_Definition:
Primary structure material. Construction material for primary structure. The material choices were based on the structure type. For bulkhead/seawalls the material options were concrete, steel, stone, and wood. For groins: stone, wood, and concrete. For revetments: stone, gabion, and structural debris. For sandbags, the only option was sandbags.
Attribute_Definition_Source: Imagery
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: concrete
Enumerated_Domain_Value_Definition: concrete
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: steel
Enumerated_Domain_Value_Definition: steel
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: wood
Enumerated_Domain_Value_Definition: wood
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: gabion
Enumerated_Domain_Value_Definition:
Stone or crushed rock contained in a steel wire mesh block form.
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: structural debris
Enumerated_Domain_Value_Definition: Pieces of irregularly shaped concrete and stone piled together.
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: sandbags
Enumerated_Domain_Value_Definition: sandbags
Enumerated_Domain_Value_Definition_Source: unknown
Attribute:
Attribute_Label: SecondaryMaterial
Attribute_Definition:
Secondary structure material. Construction material for secondary structure. The material choices were based on the structure type. For bulkhead/seawalls the material options were concrete, steel, stone, and wood. For groins: stone, wood, and concrete. For revetments: stone, gabion, and structural debris. For sandbags, the only option was sandbags.
Attribute_Definition_Source: Imagery
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: concrete
Enumerated_Domain_Value_Definition: concrete
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: steel
Enumerated_Domain_Value_Definition: steel
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: stone
Enumerated_Domain_Value_Definition: stone
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: wood
Enumerated_Domain_Value_Definition: wood
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: gabion
Enumerated_Domain_Value_Definition:
Stone or crushed rock contained in a steel wire mesh block form.
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: structural debris
Enumerated_Domain_Value_Definition: Pieces of irregularly shaped concrete and stone piled together.
Enumerated_Domain_Value_Definition_Source: unknown
Enumerated_Domain:
Enumerated_Domain_Value: sandbags
Enumerated_Domain_Value_Definition: sandbags
Enumerated_Domain_Value_Definition_Source: unknown
Attribute:
Attribute_Label: PrimaryCondition
Attribute_Definition:
Primary structure Condition. Condition was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: SecondaryCondition
Attribute_Definition:
Secondary structure Condition. Condition was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: PrimaryPriority
Attribute_Definition:
Primary structure Priority. Priority was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: SecondaryPriority
Attribute_Definition:
Secondary structure Priority. Priority was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Repair
Attribute_Definition:
Repair cost. Repair cost estimates were not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Structures_Length
Attribute_Definition:
Structure length in feet, rounded to the nearest foot. Length was calculated based on the structure line feature length.
Attribute_Definition_Source: Calculated
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 4
Range_Domain_Maximum: 19317
Attribute_Units_of_Measure: Feet
Attribute_Measurement_Resolution: 1 foot
Attribute:
Attribute_Label: PrimaryHeight
Attribute_Definition:
Primary structure height. Height range in feet of the primary structure. Ranges are typically 5 feet, except when the structure height varied by more than 5 feet along the length of the structure. Heights were determined from structure plan documents where available.
Attribute_Definition_Source: Chapter 91 licenses
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: SecondaryHeight
Attribute_Definition:
Secondary structure height. Height range in feet of the secondary structure. Ranges are typically 5 feet, except when the structure height varied by more than 5 feet along the length of the structure. Heights were determined from structure plan documents where available.
Attribute_Definition_Source: Chapter 91 licenses
Attribute_Domain_Values:
Unrepresentable_Domain: Defined during data processing
Attribute:
Attribute_Label: PositionX
Attribute_Definition:
The longitude coordinate in decimal degrees for the structure's midpoint.
Attribute_Definition_Source: Calculated
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: -71.1
Range_Domain_Maximum: -69.9
Attribute_Units_of_Measure: degrees
Attribute_Measurement_Resolution: 0.0000000001 degrees
Attribute:
Attribute_Label: PositionY
Attribute_Definition:
The latitude coordinate in decimal degrees for the structure's midpoint.
Attribute_Definition_Source: Calculated
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 41.2
Range_Domain_Maximum: 42.8
Attribute_Units_of_Measure: degrees
Attribute_Measurement_Resolution: 0.0000000001 degrees
Attribute:
Attribute_Label: PositionZ
Attribute_Definition: The structure elevation in meters relative to NAVD88.
Attribute_Definition_Source: LiDAR
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: -1.1
Range_Domain_Maximum: 31.2
Attribute_Units_of_Measure: Meters
Attribute_Measurement_Resolution: 0.0001 meters
Attribute:
Attribute_Label: FEMAZone
Attribute_Definition:
FEMA flood zone ID. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: FEMAElev
Attribute_Definition:
FEMA flood zone elevation. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: EnterBy
Attribute_Definition:
Entered By. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: EnterDate
Attribute_Definition:
Date entered. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: CrewBy
Attribute_Definition:
Crew collected by. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: CrewDate
Attribute_Definition:
Collection date. This was not evaluated for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Comments
Attribute_Definition:
Structure comments. Comments were not added for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Details
Attribute_Definition:
Structure details. Details were not added for private structures, all values were left blank (null).
Attribute_Definition_Source: None
Attribute_Domain_Values:
Unrepresentable_Domain: NULL
Attribute:
Attribute_Label: Shape_Length
Attribute_Definition: Length of feature in internal units.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Massachusetts Office of Coastal Zone Management
Contact_Address:
Address_Type: mailing and physical
Address: 251 Causeway Street, Suite 800
City: Boston
State_or_Province: MA
Postal_Code: 02114-2138
Country: US
Contact_Voice_Telephone: 617-626-1200
Contact_Facsimile_Telephone: 617-626-1240
Contact_Electronic_Mail_Address: czm@state.ma.us
Hours_of_Service: 0900 hrs to 1600 hrs EST
Contact_Instructions: email preferred
Distribution_Liability:
Although every effort has been made to ensure the accuracy of these data, errors and conditions originating from physical sources used to develop these data may be reflected in the data supplied. The client must be aware of data conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. In no event shall CZM be liable for any damages, whether general, special, incidental or consequential damages, arising out of your use of these data. Your sole remedy for damages is to stop using the data. You agree to defend, indemnify, and hold harmless CZM and its employees against any claim, loss, liability or expense, including attorneys' fees, resulting from loss of or damage to property or the injury to or death of any person arising out of the use of the data.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile (.shp)
Format_Version_Number: ArcGIS 8.x, 9.x, and 10.x
Transfer_Size: .01
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.mass.gov/czm/mapping/index.htm>
Fees:
GIS and coordinate files may be downloaded at no charge by following links on the Massachusetts Office of Coastal Zone Management website (<http://www.mass.gov/czm/mapping/index.htm>).
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20130614
Metadata_Reference_Information:
Metadata_Date: 20130627
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Massachusetts Office of Coastal Zone Management
Contact_Position: CZM Data Manager
Contact_Address:
Address_Type: mailing and physical
Address: 251 Causeway Street, Suite 800
City: Boston
State_or_Province: MA
Postal_Code: 02114-2138
Country: US
Contact_Voice_Telephone: 617-626-1200
Contact_Facsimile_Telephone: 617-626-1240
Contact_Electronic_Mail_Address: czm@state.ma.us
Hours_of_Service: 0900 hrs to 1600 hrs EST
Contact_Instructions: email preferred
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Generated by mp version 2.9.12 on Thu Jun 27 09:22:49 2013