points, transects, beach width: Barrier island geomorphology and shorebird habitat metrics at 50-m alongshore transects and 5-m cross-shore points: Monomoy Island, MA, 2013-2014

Frequently anticipated questions:

• What does this data set describe?
  1. How might this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How might this data set be cited?
   Sturdivant, Emily J., Zeigler, Sara L., and Gutierrez, Benjamin T., 20191220, points, transects, beach width: Barrier island geomorphology and shorebird habitat metrics at 50-m alongshore transects and 5-m cross-shore points: Monomoy Island, MA, 2013-2014: data release DOI:10.5066/P9V7F6UX, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

   Online Links:

   • https://doi.org/10.5066/P9V7F6UX
   • https://www.sciencebase.gov/catalog/item/5daa3730e4b09fd3b0c9ce30

   This is part of the following larger work.
   Sturdivant, Emily J., Zeigler, Sara L., Gutierrez, Benjamin T., and Weber, Kathryn M., 2019, Barrier island geomorphology and shorebird habitat metrics: Sixteen sites on the U.S. Atlantic Coast, 2013–2014: data release DOI:10.5066/P9V7F6UX, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.5066/P9V7F6UX
   • https://www.sciencebase.gov/catalog/item/5d5ece47e4b01d82ce961e36

   Other_Citation_Details:

   Suggested citation: Sturdivant, E.J., Zeigler, S.L., Gutierrez, B.T., and Weber, K.M., 2019, Barrier island geomorphology and shorebird habitat metrics—Sixteen sites on the U.S. Atlantic Coast, 2013–2014: U.S. Geological Survey data release, https://doi.org/10.5066/P9V7F6UX.

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -70.03399773
   East_Bounding_Coordinate: -69.93582227
   North_Bounding_Coordinate: 41.67818782
   South_Bounding_Coordinate: 41.53738022
   

3. What does it look like?

   https://www.sciencebase.gov/catalog/file/get/5daa3730e4b09fd3b0c9ce30/?name=pts_trans_browse.png (PNG)

   Example view (A) of the 5-m points (black), which follow the cross-shore transects (yellow) and diagram (B) of the metrics computed at each transect point.

4. Does the data set describe conditions during a particular time period?

   Calendar_Date: 2014

   Currentness_Reference:

   Ground condition measured by source data for given attribute as specified in process steps.

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: tabular and raster
   

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?
      
   2. What coordinate system is used to represent geographic features?
      

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:

      UTM_Zone_Number: 19
      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -69
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.6096
      Ordinates (y-coordinates) are specified to the nearest 0.6096
      Planar coordinates are specified in Meter
      The horizontal datum used is D_North_American_1983.
      The ellipsoid used is GRS_1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      

      Vertical_Coordinate_System_Definition:

      Altitude_System_Definition:

      Altitude_Datum_Name: North American Vertical Datum of 1988 (NAVD88)
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
      

7. How does the data set describe geographic features?

   mon_trans.shp

   Geometry of 328 shore-normal transects used as the base for sampling barrier island geomorphology. Various ID fields are included to permit later joining. NoData value for all: -99999. (Source: Producer defined)

   FID

   Internal feature number (Source: Esri) Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: Esri) Coordinates defining the features.

   sort_ID

   Unique identifier that orders transects sequentially along the shoreline. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	328

   Shape_Leng

   Length of the feature automatically calculated by ArcGIS. (Source: Producer defined)

   Range of values
   Minimum:	3849.557604247288
   Maximum:	5103.189620436094
   Units:	meters

   TRANSECTID

   NASC transect ID: "Permanent and unique identification number for each [NASC] transect in the output rates table calculated by DSAS."" (Source: Himmelstoss and others (2010))

   Range of values
   Minimum:	2.0
   Maximum:	1934.0

   DD_ID

   Identifier that orders transects sequentially along the shoreline and is unique across all sites analyzed for Zeigler and others, 2019. (Source: Producer defined)

   Range of values
   Minimum:	60001
   Maximum:	60328

   MHW

   Mean high water offset in meters. (Source: Weber and others (2005))

   Range of values
   Minimum:	0.39
   Maximum:	0.39
   Units:	meters

   mon14_pts.csv

   Geomorphology metrics at 43150 discrete points along shore-normal transects. Transect-averaged values are also included. For enumerated domains (e.g. GeoSet, SubType, Construction, etc.), these metadata list all possible values although all values described may not be present in this dataset. (Source: Producer defined)

   SplitSort

   Unique identifier that sorts the points by transect and distance from MHW. NoData value of -99999. (Source: Producer defined)

   Range of values
   Minimum:	0
   Maximum:	43149

   seg_x

   Point easting referenced to UTM Zone 19N, NAD 83. NoData value of -99999 occurs where the source transect did not intersect land, which results in a record without location. (Source: Producer defined)

   Range of values
   Minimum:	415537.31
   Maximum:	421415.31
   Units:	meters

   seg_y

   Point northing referenced to UTM Zone 19N, NAD 83. NoData value of -99999 occurs where the source transect did not intersect land, which results in a record without location. (Source: Producer defined)

   Range of values
   Minimum:	4599162.57
   Maximum:	4612761.66
   Units:	meters

   seg_lon

   Longitude in NAD 83. Negative values indicate western hemisphere. (Source: Producer defined)

   Range of values
   Minimum:	-70.012719
   Maximum:	-69.943912
   Units:	decimal degrees

   seg_lat

   Latitude in NAD 83 (Source: Producer defined)

   Range of values
   Minimum:	41.539724
   Maximum:	41.66273
   Units:	decimal degrees

   Dist_Seg

   Along-transect distance to the mean high water (MHW) shoreline position. NoData value of -99999 most often indicates that the shoreline was not properly located for the given transect. (Source: Producer defined)

   Range of values
   Minimum:	0.0
   Maximum:	2494.7
   Units:	meters

   Dist_MHWbay

   Distance of the point from the segment adjacent to the Atlantic Ocean. bayside shoreline. A negative value indicates that the point is inland (relative to the mainland) of the applicable bayside shoreline. NoData (-99999) occurs where the transect ends before intersecting a back-barrier shoreline. (Source: Producer defined)

   Range of values
   Minimum:	-1984.4
   Maximum:	1729.3
   Units:	meters

   DistSegDH

   Distance to the dune crest position along the same transect. A negative value indicates that the point is seaward of the dune crest. NoData value of -99999 indicates a dune crest could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	-440.2
   Maximum:	2165.8
   Units:	meters

   DistSegDL

   Distance to the dune toe position along the same transect. A negative value indicates that the point is seaward of the dune toe. NoData value of -99999 indicates a dune toe could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	-411.1
   Maximum:	2185.8
   Units:	meters

   DistSegArm

   Distance to the armoring position along the same transect. A negative value indicates that the point is seaward of the armoring structure. NoData (-99999) indicates armoring was not identified to replace a dune toe along the transect. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   ptZ

   Elevation referenced to NAVD88. Derived from the corresponding pixel in the 5-m DEM. NoData value of -99999 occurs where elevation data was not available. (Source: Producer defined)

   Range of values
   Minimum:	-0.02
   Maximum:	8.92
   Units:	meters

   ptSlp

   Mean slope of the corresponding 5-m pixel in the slope surface, which is derived from the 5-m DEM. NoData value of -99999 occurs where a slope surface could not be generated, most likely because of a data gap in the DEM. (Source: Producer defined)

   Range of values
   Minimum:	0.0096
   Maximum:	53.9785
   Units:	percent

   ptZmhw

   Elevation referenced to MHW. Derived from attribute ptZ (ptZmhw = ptZ - MHW offset). NoData value of -99999. (Source: Producer defined)

   Range of values
   Minimum:	-0.41
   Maximum:	8.53
   Units:	meters

   GeoSet

   The geomorphic setting indicates the classification of the major topographic features within approximately 5 m. All possible values are defined here althoug some may not be present in this dataset. NoData value of -99999 indicates that geomorphic setting data not available (see larger work). (Source: Producer defined)

   Value	Definition
   1	Beach. The relatively thick and temporary accumulation of loose, water-borne material (usually well-sorted sand and pebbles, accompanied by mud, cobbles, boulders, and smoothed rock and shell fragments) that is in active transit along, or deposited on, the shore zone between the limits of low water and high water (Neuendorf and others, 2011). In this study, the beach geomorphic setting occurred between the ocean- or sound-side study area boundary and the mean high-water line (approximated for by the upper-most wrack line in the field).
   2	Backshore. The upper, usually dry, zone of the shore or beach, lying between the high-water line of mean spring tides and the upper limit of shore-zone processes; it is acted upon by waves or covered by water only during exceptionally severe storms or unusually high tides (Neuendorf and others, 2011). In this study, the Backshore geomorphic setting occurred between the mean high-water line and either (i) the dune toe, (ii) the edge of developed areas, or (iii) the edge of dense vegetation (or forest).
   3	Dunes. A low mound, ridge, bank, or hill of loose, windblown granular material (generally sand), either bare or covered by vegetation, capable of movement from place to place but retaining its characteristic shape (Neuendorf and others, 2011). In this study, “dune” also describes low-lying areas between dunes (or “interdune” regions) that are part of the larger dune complex.
   4	Washover. A fan of material deposited from the ocean landward on a mainland beach or barrier island, produced by storm waves breaking over low parts of the mainland beach or barrier and depositing sediment either landward (mainland beaches) or across a barrier island into the bay/sound (barrier islands). A washover typically displays a characteristic fan-like shape (Neuendorf and others, 2011).
   5	Barrier Interior. In this study, the Barrier Interior geomorphic setting described all areas spanning the interior boundary of the dunes (or backshore in the absence of dunes) on the ocean-side to the interior boundary of the marsh, dunes, or backshore on the back-barrier side. This setting was typically used to describe areas that did not fall into any other geomorphic setting (e.g., washovers, ridge/swale complexes).
   6	Marsh. A relatively flat, low-lying, intermittently water-covered area with generally halophytic grasses existing landward of a barrier island (Neuendorf and others, 2011).
   7	Ridge/Swale complex: Long subparallel ridges and swales aligned obliquely across the regional trend of the contours (Neuendorf and others, 2011).
   -99999	Missing value.

   SubType

   Substrate type: dominant classification of substrate within approximately 5 m. Some values listed here may not be present these data; the list defines all values possible. NoData value of -99999 indicates that substrate type data not available (see larger work). Curly brackets ('{}') around two values are used in the modeling process. (Source: Zeigler and others, 2019)

   Value	Definition
   1000	Sand or Mud/Peat: In this study, wet, sandy substrates could not be differentiated from mud/peat in marshy areas. Therefore, we identified substrate as being either of these two types in the Substrate raster layer. Mud/Peat is a sticky, fine-grained, predominantly clay- or silt-sized marine detrital sediment (Neuendorf and others, 2011). Sand included rock or mineral grains with diameters between 0.074 and 4.76 mm (Neuendorf and others, 2011).
   1111	Sand: predominantly sandy substrates that contain rock or mineral grains with diameters between 0.074 and 4.76 mm (Neuendorf and others, 2011) with no discernible shell fragments or large rock fragments.
   2222	Shell/Gravel/Cobble: substrates containing a mixture of sand, shell or rock fragments, or large rocks.
   3333	MudPeat: A sticky, fine-grained, predominantly clay- or silt-sized marine detrital sediment (Neuendorf and others, 2011).
   4444	Water: Any location that (i) is always submerged (e.g., locations several meters into the ocean, bay, or inland water body), (ii) was submerged at the time aerial imagery was captured (i.e., intertidal regions of beaches), or (iii) was not submerged at the time aerial imagery was captured but was outside of the shoreline polygon.
   6666	Development: Any location that fell within areas obviously influenced by anthropogenic activities (e.g., housing developments, paved roads or parking lots, recreational sports fields, etc.).
   {1111, 2222}	Sand or ShellGravelCobble: Substrate is either predominantly sand or a mix of sand with shell or rock fragments. Sand included rock or mineral grains with diameters between 0.074 and 4.76 mm (Neuendorf and others, 2011) with no discernible shell fragments or large rock fragments. ShellGravelCobble described substrates containing a mixture of sand, shell or rock fragments, or large rocks.
   {1111, 3333}	Sand or Mud/Peat: In this study, wet, sandy substrates could not be differentiated from mud/peat in marshy areas. Therefore, we identified substrate as being either of these two types in the Substrate raster layer. Mud/Peat is a sticky, fine-grained, predominantly clay- or silt-sized marine detrital sediment (Neuendorf and others, 2011). Sand included rock or mineral grains with diameters between 0.074 and 4.76 mm (Neuendorf and others, 2011).
   -99999	Unknown: Substrate type could not be determined based on aerial imagery

   VegDens

   The dominant type of vegetation within approximately 5 m. Some values listed here may not be present these data; the list defines all values possible. NoData value of -99999 indicates that vegetation density data not available (see larger work). Curly brackets ('{}') around two values are used in the modeling process. (Source: Zeigler and others, 2019)

   Value	Definition
   111	None: Areas lacking terrestrial vegetation of any type. Such areas were most frequently associated with the beach geomorphic setting (found seaward of the study area shoreline) assumed to be covered by water.
   222	Sparse: areas where vegetation was apparent and covered less than 20% of the 5x5-m raster cell.
   333	Moderate: areas where vegetation appeared to cover 20–90% of the 5x5-m raster cell.
   444	Dense: areas where vegetation appeared to cover greater than 90% of the 5x5-m raster cell.
   555	Development: In this study, we selected development as the vegetation density for any location that fell within areas obviously influenced by anthropogenic activities (e.g., housing developments, paved roads or parking lots, recreational sports fields, etc.).
   {111, 222}	None or Sparse: The given location either appeared to lack vegetation completely in the aerial imagery or, if vegetation was apparent, covered less than 20% of the approximately 5 x 5 m area designated by the transect point.
   {222, 333}	Sparse or Moderate: In this study, areas with sparse vegetation could not consistently be differentiated from areas containing moderate vegetation in the orthoimagery alone. Therefore, we identified vegetation as being either of these two types in the Vegetation Density raster layer. Areas described as having 'Sparse' vegetation appeared to have vegetation that covered less than 20% of the 5x5-m raster cell. In areas described as 'Moderate', vegetation appeared to cover 20-90% of the 5x5-m raster cell.
   {333, 444}	Moderate or Dense: The given location either appeared to have vegetation covering 20-90% or >90% of the approximately 5 x 5 m area designated by the transect point.
   -99999	Unknown: Vegetation density could not be determined based on the aerial imagery

   VegType

   The dominant type of vegetation within approximately 5 m. Some values listed here may not be present these data; the list defines all values possible. NoData value of -99999 indicates that vegetation type data were not available (see larger work). Curly brackets ('{}') around two values are used in the modeling process. (Source: Zeigler and others, 2019)

   Value	Definition
   11	None: Areas lacking terrestrial vegetation of any type. Such areas were associated with the beach geomorphic setting (found seaward of the study area shoreline) assumed to be covered by water.
   22	Herbaceous: areas containing primarily herbaceous vegetation of the forb/herb growth habit (USDA, 2015) and lacking shrubs, trees, or any other vegetation with woody stems (Neuendorf and others, 2011). In this study, the Herbaceous vegetation type typically described the vegetation cover found in Godfrey’s (1976) (i) ‘grassland’ ecological zone along the backshore and dunes, dominated by beach grasses (e.g., Ammophila breviligulata) or (ii) ‘intertidal marsh’ ecological zone dominated by cordgrass (e.g., Spartina patens).
   33	Shrub: Areas containing low (less than 5 m height), multi-stemmed woody plants of the subshrub or shrub growth habits (USDA, 2015). In this study, the Shrub vegetation type typically described vegetation cover found in Godfrey’s (1976) heath-like ‘shrublands’ ecological zone in stable dune systems.
   44	Forest: Areas containing trees and tall (> 5 m) shrubs of the tree growth habit (USDA, 2015). In this study, the Forest vegetation type typically described vegetation cover found in Godfrey’s (1976) ‘woodlands–forests’ ecological zone found in barrier island interiors and dominated by deciduous (e.g., Quercus velutina), pine (e.g., Pinus rigida), and juniper (e.g., Juniperus virginiana) species.
   55	Development: Located within areas obviously influenced by anthropogenic activities (e.g., housing developments, paved roads or parking lots, recreational sports fields, etc.).
   {11, 22}	None or Herbaceous: The given location either lacked vegetation or contained primarily herbaceous vegetation of the forb/herb growth habit (USDA, 2015). In this study, the herbaceous vegetation type typically described the vegetation cover found in Godfrey’s (1976) (i) ‘grassland’ ecological zone along the backshore and dunes, dominated by beach grasses (e.g., Ammophila breviligulata) or (ii) ‘intertidal marsh’ ecological zone dominated by cordgrass (e.g., Spartina patens).
   {22, 33}	Herbaceous or Shrub: The given location either contained primarily herbaceous vegetation of the forb/herb growth habit or low (less than 5 m height), multi-stemmed woody plants of the subshrub or shrub growth habits (USDA, 2015). In this study, the herbaceous vegetation type typically described the vegetation cover found in Godfrey’s (1976) (i) ‘grassland’ ecological zone along the backshore and dunes, dominated by beach grasses (e.g., Ammophila breviligulata) or (ii) ‘intertidal marsh’ ecological zone dominated by cordgrass (e.g., Spartina patens). The shrub vegetation type typically described vegetation cover found in Godfrey’s (1976) heath-like ‘shrublands’ ecological zone in stable dune systems.
   {33, 44}	Shrub or Forest: The given location contained either tall (greater than 5 m height) multi-stemmed woody plants of the shrub growth habit or plants of the tree growth habit (USDA, 2015). In this study, the shrub vegetation type typically described vegetation cover found in Godfrey’s (1976) heath-like ‘shrublands’ ecological zone in stable dune systems. The forest vegetation type typically described vegetation cover found in Godfrey’s (1976) ‘woodlands–forests’ ecological zone found in barrier island interiors and dominated by deciduous (e.g., Quercus velutina), pine (e.g., Pinus rigida), and juniper (e.g., Juniperus virginiana) species.
   -99999	Unknown: Vegetation type could not be determined based on aerial imagery

   sort_ID

   Unique identifier that orders transects sequentially along the shoreline. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	328

   TRANSECTID

   NASC transect ID: "Permanent and unique identification number for each [NASC] transect in the output rates table calculated by DSAS."" (Source: Himmelstoss and others (2010))

   Range of values
   Minimum:	2
   Maximum:	1934

   DD_ID

   Identifier that orders transects sequentially along the shoreline and is unique across all sites analyzed for Zeigler and others, 2019. (Source: Producer defined)

   Range of values
   Minimum:	60001
   Maximum:	60328

   Azimuth

   Bearing of the transect measured in degrees clockwise from North. NoData value of -99999 occurs where the bearing could not be calculated. (Source: Producer defined)

   Range of values
   Minimum:	0.1
   Maximum:	358.0
   Units:	degrees

   LRR

   "A linear regression rate-of-change statistic was calculated by fitting a least-squares regression line to all shoreline points for a particular transect. The best-fit regression line is placed so that the sum of the squared residuals (determined by squaring the offset distance of each data point from the regression line and adding the squared residuals together) is minimized. The linear regression rate is the slope of the line. The rate is reported in meters per year with positive values indicating accretion and negative values indicating erosion." NoData value of -99999 indicates an NASC transect is not present or does not have an LRR value. (Source: Himmelstoss and others (2010))

   Range of values
   Minimum:	-7.98
   Maximum:	8.1
   Units:	meters/year

   SL_x

   Easting of position of MHW shoreline along transect. NoData value of -99999 occurs where the shoreline could not be located along the transect. (Source: Producer defined)

   Range of values
   Minimum:	415732.58
   Maximum:	421415.21
   Units:	meters

   SL_y

   Northing of position of MHW shoreline along transect. NoData value of -99999 occurs where the shoreline could not be located along the transect. (Source: Producer defined)

   Range of values
   Minimum:	4599163.46
   Maximum:	4612733.95
   Units:	meters

   Bslope

   Beach slope calculated between dune toe and shoreline (NAVD88) at the shoreline point nearest to the transect. A negative value indicates decreasing elevation from dune toe to shoreline. NoData value of -99999 occurs where a shoreline point could not be located within 25 m of the transect or the nearest point did not have a beach slope calculated. (Source: Producer defined)

   Range of values
   Minimum:	-0.1241
   Maximum:	-0.0117
   Units:	percent

   DL_x

   Easting of the nearest dune toe point within 25 meters of the transect. NoData value of -99999 indicates a dune toe could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	416249.2
   Maximum:	421366.04
   Units:	meters

   DL_y

   Northing of the nearest dune toe point within 25 meters of the transect. NoData value of -99999 indicates a dune toe could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	4599214.65
   Maximum:	4612981.35
   Units:	meters

   DL_z

   Elevation of the nearest dune toe point within 25 meters of the transect, referenced to NAVD88. NoData (-99999) indicates a dune toe could not be identified within 25 m of the transect or the nearest point did not have an elevation value. (Source: Producer defined)

   Range of values
   Minimum:	1.08
   Maximum:	4.43
   Units:	meters

   DL_zmhw

   Elevation of the nearest dune toe point within 25 meters of the transect, referenced to MHW. NoData (-99999) indicates a dune toe could not be identified within 25 m of the transect or the nearest point did not have an elevation value. (Source: Producer defined)

   Range of values
   Minimum:	0.69
   Maximum:	4.04
   Units:	meters

   DL_snapX

   Easting of the nearest dune toe point within 25 meters of the transect, snapped to the transect. NoData (-99999) indicates a dune toe could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	416250.23
   Maximum:	421371.23
   Units:	meters

   DL_snapY

   Northing of the nearest dune toe point within 25 meters of the transect, snapped to the transect. NoData (-99999) indicates a dune toe could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	4599214.91
   Maximum:	4612962.78
   Units:	meters

   DH_x

   Easting of the nearest dune crest point within 25 meters of the transect. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	416068.26
   Maximum:	421328.56
   Units:	meters

   DH_y

   Northing of the nearest dune crest point within 25 meters of the transect. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	4599227.55
   Maximum:	4612970.1
   Units:	meters

   DH_z

   Elevation of the nearest dune crest point within 25 meters of the transect, referenced to NAVD88. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect or the nearest point did not have an elevation value. (Source: Producer defined)

   Range of values
   Minimum:	1.59
   Maximum:	7.96
   Units:	meters

   DH_zmhw

   Elevation of the nearest dune crest point within 25 meters of the transect, referenced to MHW. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect or the nearest point did not have an elevation value. (Source: Producer defined)

   Range of values
   Minimum:	1.2
   Maximum:	7.57
   Units:	meters

   DH_snapX

   Easting of the nearest dune crest point within 25 meters of the transect, snapped to the transect. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	416070.97
   Maximum:	421330.27
   Units:	meters

   DH_snapY

   Northing of the nearest dune crest point within 25 meters of the transect, snapped to the transect. NoData (-99999) indicates a dune crest could not be identified within 25 m of the transect. (Source: Producer defined)

   Range of values
   Minimum:	4599225.2
   Maximum:	4612967.44
   Units:	meters

   Arm_x

   Easting of the nearest armoring structure within 25 meters of the transect. NoData (-99999) indicates armoring was not found to replace a dune toe position along the transect. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   Arm_y

   Northing of the nearest armoring structure within 25 meters of the transect. NoData (-99999) indicates armoring was not found to replace a dune toe position along the transect. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   Arm_z

   Elevation of the nearest armoring structure within 25 meters of the transect, referenced to NAVD88. NoData (-99999) indicates armoring was not found to replace a dune toe position along the transect or the elevation was not available at the point. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   Arm_zmhw

   Elevation of the nearest armoring structure within 25 meters of the transect, referenced to MHW. NoData (-99999) indicates armoring was not found to replace a dune toe position along the transect or the elevation was not available at the point. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   DistDH

   Horizontal distance along transect from the MHW shoreline to the dune crest (DH_snapX, DH_snapY). NoData (-99999) occurs where a dune crest or shoreline position are not located along the transect. (Source: Producer defined)

   Range of values
   Minimum:	18.5
   Maximum:	440.2
   Units:	meters

   DistDL

   Horizontal distance along transect from the MHW shoreline to the dune toe (DL_snapX, DL_snapY). NoData (-99999) occurs where a dune toe or shoreline position are not located along the transect. (Source: Producer defined)

   Range of values
   Minimum:	9.9
   Maximum:	411.1
   Units:	meters

   DistArm

   Horizontal distance along transect from the MHW shoreline to the first armoring structure (Arm_snapX, Arm_snapY). NoData (-99999) occurs where an armoring position or shoreline position are not located along the transect. (Source: Producer defined)

   Range of values
   Minimum:	-99999
   Maximum:	-99999
   Units:	meters

   Dist2Inlet

   Alongshore distance to nearest inlet. NoData (-99999) occurs where the transect is outside the bounds of the shoreline, as constrained by the tidal inlet delineation. (Source: Producer defined)

   Range of values
   Minimum:	4.4
   Maximum:	6691.3
   Units:	meters

   WidthPart

   Horizontal distance between seaward shoreline and the first break in the land, such as intervening water bodies like back-barrier creeks. NoData (-99999) occurs where the transect does not intersect land or the transect does not intersect another back-barrier water body. (Source: Producer defined)

   Range of values
   Minimum:	70.5
   Maximum:	1729.4
   Units:	meters

   WidthLand

   Barrier Island Width (m). Width of the barrier island cross-section. Measurement only considers width of land and not intervening water bodies such as back barrier creeks. NoData (-99999) occurs where the transect does not intersect land or the transect ends before intersecting a back-barrier shoreline. (Source: Producer defined)

   Range of values
   Minimum:	70.5
   Maximum:	1739.9
   Units:	meters

   WidthFull

   Barrier Island Full Width (m). Horizontal distance along transect from seaward shoreline to farthest bayside shoreline. NoData (-99999) occurs where the transect does not intersect land or the transect ends before intersecting a back-barrier shoreline. (Source: Producer defined)

   Range of values
   Minimum:	70.5
   Maximum:	2500.5
   Units:	meters

   uBW

   Upper beach width. The horizontal distance from MHW shoreline to the dune toe or equivalent. NoData (-99999) occurs where beach width cannot be calculated because input values are missing or the calculation criteria are not met. A negative value indicates that the elevation of the identified top of beach feature is below the MHW elevation. (Source: Producer defined)

   Range of values
   Minimum:	9.9
   Maximum:	411.1
   Units:	meters

   uBH

   Upper beach height. The vertical distance from MHW to the dune toe or equivalent. NoData (-99999) occurs where beach height cannot be calculated because input values are missing or the calculation criteria are not met. A negative value indicates that the identified top of beach feature is seaward of the MHW shoreline. (Source: Producer defined)

   Range of values
   Minimum:	0.69
   Maximum:	4.04
   Units:	meters

   ub_feat

   Feature (dune toe, dune crest, or armoring) that indicates the top of beach, used to calculate beach width and beach height. (Source: Producer defined)

   Value	Definition
   -99999	No feature available to calculate beach width.
   DL	Dune toe.
   DH	Dune crest.
   Arm	Shorefront armoring used in place of dune toe to calculate beach width.

   mean_Zmhw

   Mean elevation along transect, referenced to MHW tidal datum. NoData (-99999) indicates that elevation values are missing for 20 percent or more of the points along the transect. (Source: Producer defined)

   Range of values
   Minimum:	0.38
   Maximum:	2.99
   Units:	meters

   max_Zmhw

   Maximum elevation along transect, referenced to MHW tidal datum. NoData (-99999) indicates that no elevation values were present for the transect. (Source: Producer defined)

   Range of values
   Minimum:	0.91
   Maximum:	8.53
   Units:	meters

   Construction

   Construction: denotes presence of construction-based human erosion management activities. Some values listed here may not be present these data; the list defines all values possible. Unknown is indicated with a NoData value of -99999. (Source: Producer defined)

   Value	Definition
   111	Denotes no constructed features.
   222	Denotes presence of soft approaches (sand fencing, geotubes).
   333	Denotes presence of hard approaches (rip rap, seawall, jetty, groyne).
   444	Denotes presence of hard and soft approaches.

   Development

   Development intensity: denotes intensity of human development. Some values listed here may not be present these data; the list defines all values possible. Unknown is indicated with a NoData value of -99999. (Source: Producer defined)

   Value	Definition
   111	Denotes no human development.
   222	Denotes light development: the presence of a road, paved or unpaved, and the occasional structure.
   333	Denotes moderate development: the presence of more extensive roads and/or buildings along a transect.
   444	Denotes heavy development: a high density of paved surfaces, houses, or buildings along a transect.

   Nourishment

   Nourishment activity: denotes presence of nourishment-based human erosion management activities. Some values listed here may not be present these data; the list defines all values possible. Unknown is indicated with a NoData value of -99999. (Source: Producer defined)

   Value	Definition
   111	Denotes no nourishment.
   222	Denotes occasional nourishment.
   333	Denotes frequent nourishment.

   mon14_ubw.tif values attribute table

   Values attribute table (mon14_ubw.tif.vat.dbf), which indicates the beach width of every cell in the raster (mon14_ubw.tif). The raster is composed of 1642 x 3109 grid cells. Raster cells outside the bounds of the data have a NoData value of 16. (Source: Producer defined)

   Value

   Matches the sort_ID identifier values used to uniquely identify transects in the supplemented NASC transects and the 5-m points (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	328
   Units:	integer

   Count

   Number of pixels pertaining to the transect identified by the Value field. (Source: Producer defined)

   Range of values
   Minimum:	1246
   Maximum:	15502
   Units:	count

   uBW

   Upper beach width. The horizontal distance from the MHW shoreline to the dune toe or equivalent. The fill value for unavailable data is -99999. (Source: Producer defined)

   Range of values
   Minimum:	9.9
   Maximum:	411.1
   Units:	meters

   Entity_and_Attribute_Overview:

   This section provides a separate detailed entity and attribute information section for each dataset described in these metadata. The complete dataset is included in the 5-m points. The other files are included for convenience. Each point represents a 5 x 5 m sample area with the geomorphological characteristics specified. All calculations for length are in meter units and were based on the UTM zone 19N NAD83 projection. These metadata list all possible values for enumerated domains (e.g. GeoSet, SubType, Construction, etc.); however, some of the values described may not be present in this dataset. NoData is indicated with the value -99999. Please review the individual attribute descriptions for detailed information.

   Entity_and_Attribute_Detail_Citation: Methods Open-File Report by Zeigler and others, 2019
   

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Emily J. Sturdivant
   • Sara L. Zeigler
   • Benjamin T. Gutierrez
2. Who also contributed to the data set?
3. To whom should users address questions about the data?
   Sara L. Zeigler

   U.S. Geological Survey

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2290 (voice)

   (508) 457-2310 (FAX)

   szeigler@usgs.gov

Why was the data set created?

How was the data set created?

1. From what previous works were the data drawn?

   NASC transects (source 1 of 3)

   Himmelstoss, Emily A., Kratzmann, Meredith G., Hapke, Cheryl J., Thieler, E. Robert, and List, Jeffrey, 2010, National Assessment of Shoreline Change: A GIS Compilation of Vector Shorelines and Associated Shoreline Change Data for the New England and Mid-Atlantic Coasts: Open-File Report 2010-1119, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://pubs.usgs.gov/of/2010/1119/
   • https://pubs.usgs.gov/of/2010/1119/data_catalog.html

   Type_of_Source_Media: digital data
   Source_Contribution:

   Shore-normal transects with long term shoreline change rates from the National Assessment of Shoreline Change (NASC) (CapeCod_LT.shp). The data are distributed as an Esri polyline shapefile referenced to World Geodetic System 1984 (WGS84). They were downloaded in 2017.

   Orthoimage (source 2 of 3)

   U.S. Geological Survey, and MassGIS (Bureau of Geographic Information), 20181204, MassGIS Data: USGS Color Ortho Imagery (2013/2014): MassGIS (Bureau of Geographic Information), Boston, MA.

   Online Links:

   • https://docs.digital.mass.gov/dataset/massgis-data-usgs-color-ortho-imagery-20132014
   • http://maps.massgis.state.ma.us/map_ol/oliver.php

   Type_of_Source_Media: digital data
   Source_Contribution:

   Visual imagery used for digitizing shorefront development, tidal inlets, and for QA/QC. Source data were distributed at 0.3 m pixel resolution, in horizontal datum NAD83 (2011). Downloaded on 2/6/2017. Data were projected to UTM Zone 19N (EPSG:26919) using the ‘Project Raster’ tool in ArcToolbox (version 10.4.1).

   DEM (source 3 of 3)

   Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office for Coastal Management (OCM), 20150615, 2013-2014 U.S. Geological Survey CMGP LiDAR: Post Sandy (MA, NH, RI): NOAA's Ocean Service, Office for Coastal Management (OCM), Charleston, SC.

   Online Links:

   • https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4914
   • https://coast.noaa.gov/htdata/lidar1_z/geoid12b/data/4914
   • https://coast.noaa.gov/dataviewer
   • https://coast.noaa.gov

   Type_of_Source_Media: digital data
   Source_Contribution:

   Elevation. Source data were downloaded from https://coast.noaa.gov/dataviewer in horizontal datum NAD 1983 (2011), UTM Zone 19N, vertical datum NAVD88. Downloaded on 3/30/2016.

2. How were the data generated, processed, and modified?

   Date: 2018 (process 1 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019). The Jupyter notebook used for processing is distributed with this dataset (extractor_mon14.ipynb).
   mon_trans.shp
   NASC transects from Himmelstoss and others (2010) were modified for the purposes of this study. Transects were extended inland to cover the width of the barrier, and additional transects were added to fill alongshore gaps greater than 50 m.
   Transects are extended by using the last two vertices of each transect to programmatically place the end of the line 3,000 m beyond the end of the original line segment. Python (version 3) with the modules ArcPy and Collections in an ArcGIS Pro 2.0 environment are used for programming (see function core/functions_warcpy.ExtendLine in bi-transect-extractor (Sturdivant, 2019)). The process transforms the data from WGS84 to NAD83 UTM Zone 19N using WGS_1984_(ITRF00)_To_NAD_1983_2011 (WKID: 108354, accuracy: 0.1 m). It uses the coordinates of the last two vertices of each feature and calculates a new second coordinate at a specified distance (3,000 m) along the prolongation of the line from the first coordinate.
   Next, transects are manually added to fill alongshore gaps greater than 50 m. To do so we copy the extended NASC transects, replace their attribute values with fill values (-99999), move groups of them to fill gaps, delete any that are unchanged, and then merge the altered file back to the NASC transects. ID values ('sort_ID') are assigned that order the transects consecutively along the oceanside shoreline using the ArcGIS Spatial Sort tool in spatial increments.
   We eliminate transect overlap in certain locations by manually clipping the transects to the first intersection point with an overlapping transect. While doing so, we prioritize the original NASC transect geometries. Overlapping transects retain the azimuths of the original lines but in some cases are shortened.

   Date: 2019 (process 2 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019) and technical steps can be found in the source code (Sturdivant, 2019). The Jupyter notebook used to create the point dataset (extractor_mon14.ipynb) is distributed in this data release. All steps described below were performed in the Jupyter notebook extractor_mon14.ipynb, which used Python 3 and ArcPy distributed with ArcGIS Pro 2.0. Manual steps indicated in the notebook were executed in a session of ArcGIS Pro 2.0.
   The term "shoreline" is used to describe multiple components. "Shoreline polygon(s)" (mon14_shoreline.shp in larger work) outline the boundary between land and water for the entire study area. They are composed of the oceanside shoreline and the back-barrier shoreline. "Oceanside shoreline" refers to the MHW contour line adjacent to the open ocean and bounded by either tidal inlet or the study area extent. In some cases, we may use MHW shoreline interchangeably with oceanside shoreline. "Back-barrier shoreline" refers to the boundary between land and water on the western side of the island; it usually follows the mean tidal level (MTL) contour line. We also refer to "shoreline points," which are precise MHW positions defined in the mon14_SLpts dataset in the larger work.
   mon14_pts.csv, part 1
   First, we calculate values that apply to entire cross-shore transects. Supplemented NASC transects are populated with the shoreline change rate values from the original NASC transects. Lines that are not present in the NASC transects are populated with fill values (-99999) for LRR, TRANSECTID, and TRANSORDER fields.
   MHW position and foreshore slope along transect:
   Each transect is assigned the foreshore slope (Bslope) from the nearest oceanside shoreline point within 25 m (see larger work). The MHW shoreline easting and northing locate the intersection of the transect with the oceanside shoreline. These values are populated for each transect as follows (using Python 3 distributed with ArcGIS Pro 2.0, especially the modules ArcPy, NumPy, and Pandas): (1) Create a line representing the oceanside shoreline by converting the shoreline polygons to lines, clipping them at the inlet lines, and selecting only those segments that intersect shoreline points (from the morphology feature positions, mon14_SLpts in larger work); (2) get 'SL_x' and 'SL_y' at the intersection point between the transect and the oceanside shoreline (created from mon14_shoreline.shp in larger work); (3) find the closest shoreline point to that intersection point; and (4) assign the slope value from the shoreline point to the transect ('Bslope'). In rare situations, this results in a transect with a slope value but without a shoreline position.
   Dune positions along transects:
   'DL_x', 'DL_y', and 'DL_zMHW' are the easting, northing, and height above MHW, respectively, of the nearest dune toe point (mon14_DLpts.shp in larger work) within 25 meters of the transect. Likewise, 'DH_x', 'DH_y', and 'DH_zMHW' are the easting, northing, and height above MHW, respectively, of the nearest dune crest point within 25 meters (mon14_DCpts.shp in larger work). We find the XYZ positions of the nearest dune crest and dune toe within 25 meters for each transect using bi-transect-extractor (Sturdivant, 2019) to execute the following, repeated for both dune crest and dune toe: (1) evaluate the distance from the transect to every dune crest/toe point and find the shortest of these distances (distanceTo geometry method in ArcPy); (2) if the distance is less than 25 m, return the elevation from the point and the XY position of the point ‘snapped’ to the transect (snapToLine geometry method); (3) if there are no points within 25 m of the transect, populate the transect with null/fill values (Pandas); and (4) convert the elevations to the MHW datum by subtracting the MHW offset value (0.39 m based on Weber and others, 2005).
   'Arm_x', 'Arm_y', and 'Arm_zMHW' are the easting, northing, and height above MHW, respectively, where an artificial structure crosses the transect in the vicinity of the beach. These features are meant to supplement the dune toe dataset by providing an upper limit to the beach in areas where dune toe extraction was confounded by the presence of an artificial structure. Values are populated for each transect as follows: (1) prioritizing areas where dune toe features were not successfully extracted, use orthoimagery, supplemented with the DEM, to manually digitize line segments on the oceanside face of artificial impediments to sediment ("armoring"), such as sand-fencing, sandbags, seawalls, etc.; (2) get the positions of intersection between the digitized armoring lines and the transects (Intersect tool from the Overlay toolset); (3) extract the elevation value at each intersection point from the DEM (Extract Multi Values to Points tool from Spatial Analyst; see Source Information for DEM); and (4) convert the elevations to the MHW datum by subtracting the MHW offset value (0.39 m based on Weber and others, 2005).
   Beach width and height:
   Upper beach width ('uBW') and upper beach height ('uBH') are calculated based on the difference in position between two points: the position of MHW along the transect ('SL_x', 'SL_y') and the dune toe position or equivalent (usually 'DL_x', 'DL_y'). All calculations are performed by the function calc_BeachWidth_fill in bi-transect-extractor (Sturdivant, 2019). In some cases, the dune toe is not appropriate to designate the "top of beach" so beach width and height are calculated from either the position of the dune toe, the dune crest, or the base of an armoring structure. The dune crest is only considered a possibility if the dune crest elevation (DH_zMHW) is less than or equal to 2.5 m, which was selected for this site through expert judgement. They are calculated as follows, relying primarily on NumPy and the snapToLine geometry method in ArcPy, and using Pandas for data storage/organization:
   (1) Find the position along the transect of an orthogonal line drawn to the dune point ('DL_x', 'DL_y' and 'DH_x', 'DH_y'). (2) Calculate distances from MHW to the position along the transect of the dune toe ('DistDL'), dune crest ('DistDH'), and armoring ('DistArm'). (3) Conditionally select the appropriate feature to represent "top of beach." Dune toe is prioritized. If it is not available and 'DH_zMHW' is less than or equal to maxDH, use dune crest. If neither of the dune feature positions satisfy the conditions and an armoring feature intersects with the transect, use the armoring position. If none of the three are possible, 'uBW' and 'uBH' are given a NoData value of -99999. (4) Copy the distance to oceanside shoreline and height above MHW ('Dist--', '---zMHW') to 'uBW' and 'uBH', respectively.
   Distance to inlet:
   Distance to nearest tidal inlet ('Dist2Inlet') is computed as alongshore distance of each sampling transect from the nearest tidal inlet. Inlets are manually delineated during the creation of the shoreline polygon file. This distance includes changes in the path of the oceanside shoreline rather than just a straight-line distance between each transect and the inlet and reflects sediment transport pathways. It is measured using the shoreline polygon(s) and the delineated tidal inlets (mon14_inletLines.shp in larger work) as follows: (1) split the shoreline polygon(s) at the tidal inlets by converting the polygon(s) to polylines including the inlet lines (Feature to Line in Data Management); (2) retain only the oceanside segments of the shoreline by deleting all segments that do not intersect any shoreline points (disjoint geometry method in ArcPy data access module); (3) if the shoreline is bounded on both sides by an inlet, measure the distance to both and assign the minimum distance of the two or if the shoreline meets only one inlet (meaning the study area ends before the island ends), use the distance to the only inlet (cut, disjoint, and length geometry methods and properties in ArcPy)
   Island widths:
   Barrier Island Width ('WidthLand') is calculated as the aggregate above-water width between the easternmost and westernmost shorelines along the transect. 'WidthLand' only included regions of the barrier within the shoreline polygon(s) (mon14_shoreline.shp in larger work). We also measure the shore-to-shore extent of the island, which includes space occupied by waterways ('WidthFull') and the width of only the island portion adjacent to the Atlantic Ocean of land within the shoreline ('WidthPart'). These are calculated as follows:
   (1) Clip the transect to the shoreline polygon(s) (Clip in the Analysis toolbox); (2) for 'WidthLand', get the length of the multipart line segment from "SHAPE@LENGTH" feature class attribute, which will include only the remaining portions of the transect; (3) for 'WidthPart', convert the clipped transect from multipart to singlepart and get the length of the first line segment, which should be the segment adjacent to the Atlantic Ocean.; (4) for 'WidthFull', calculate the distance between the first vertex and the last vertex of the clipped transect (Feature Class to NumPy Array with explode to points, Pandas groupby, NumPy hypot).
   The shoreline polygon may be artificially clipped where the site boundary or the available data do not include a back-barrier shoreline, which prevents the accurate calculation of island width values (e.g. Coast Guard Beach in Massachusetts). In these cases, transects that intersect a false back-barrier shoreline were manually identified and assigned fill values (-99999) for WidthLand, WidthFull, WidthPart, Dist_MHWbay as applicable. Person who carried out this activity:
   

   Emily J. Sturdivant

   U.S. Geological Survey

   Geographer

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2230 (voice)

   508-457-2310 (FAX)

   esturdivant@usgs.gov

   Date: 2019 (process 3 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019) and technical steps can be found in the source code (Sturdivant, 2019). The Jupyter notebook used to create the point dataset (extractor_mon14.ipynb) is distributed in this data release. All steps described below were performed in the Jupyter notebook extractor_mon14.ipynb, which used Python 3 and ArcPy distributed with ArcGIS Pro 2.0. Manual steps indicated in the notebook were executed in a session of ArcGIS Pro 2.0.
   mon14_pts.csv, part 2
   Nourishment, Construction, Development:
   We manually assigned coded values for the attributes Nourishment, Construction, and Development by comparing the transect positions to ancillary datasets in ArcGIS 10.5. These datasets included the inventory of habitat modification (Rice, 2015), available aerial imagery, and the development layer included in this data release. See the associated Methods OFR (Zeigler and others, 2019) for details and example figures. Person who carried out this activity:
   

   Benjamin T. Gutierrez

   U.S. Geological Survey

   Geologist

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2289 (voice)

   508-457-2310 (FAX)

   bgutierrez@usgs.gov

   Date: 2019 (process 4 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019). All steps described below were performed in the Jupyter notebook extractor_mon14.ipynb, which used Python 3 and ArcPy distributed with ArcGIS Pro 2.0. Manual steps indicated in the notebook were executed in a session of ArcGIS Pro 2.0.
   mon14_pts.csv, part 3
   The point dataset represents 5 m sampling of the land along each shore-normal transect (mon_trans.shp; see Zeigler and others, 2019). The 5-m point file is created from the supplemented NASC transects as follows: (1) Manually shorten overlapping transects to the first point of intersection. Prioritize preserving original NASC transects and those that are oriented most orthogonally to the shore. (2) Clip the transects to the shoreline polygon(s) of the barrier island, retaining only those portions of the transects that represent land. (3) Create a point along each transect every 5 m starting from the oceanside shoreline. Person who carried out this activity:
   

   Emily J. Sturdivant

   U.S. Geological Survey

   Geographer

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2230 (voice)

   508-457-2310 (FAX)

   esturdivant@usgs.gov

   Date: 2019 (process 5 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019). All steps described below were performed in the Jupyter notebook extractor_mon14.ipynb, which used Python 3 and ArcPy distributed with ArcGIS Pro 2.0 (Sturdivant, 2019). Manual steps indicated in the notebook were executed in a session of ArcGIS Pro 2.0.
   mon14_pts.csv, part 4
   Point identifier:
   We populate the 5-m points with a numerical identifier ('SplitSort') of the 5-m data sampling points at a particular study site, sorted by order along oceanside shoreline and by distance from the oceanside shoreline. 'SplitSort' values are populated by sorting the points by 'sort_ID' and 'Dist_Seg' (see below).
   Distances:
   'Dist_Seg' and 'Dist_MHWbay' measure the distance of the point from the shoreline adjacent to the open ocean and the shoreline adjacent to the back-barrier waterbody respectively. 'Dist_Seg' is calculated as the Euclidean distance between the point and the shoreline ('SL_x', 'SL_y'). 'Dist_MHWbay' is calculated by subtracting the 'Dist_Seg' value from the transect 'WidthPart'. A NoData value for WidthPart prevents the calculation of Dist_MHWbay. This is performed by the function prep_points in bi-transect-extractor (Sturdivant, 2019).
   'DistSegDH', 'DistSegDL', and 'DistSegArm' measure the distance of each 5-m point from the dune crest, dune toe, and dune armoring position respectively along a particular transect. They are calculated as the Euclidean distance between the 5-m point and the given feature.
   Elevation and slope:
   'ptZ' and 'ptSlp' are the elevation (NAVD88) and slope at the 5-m cell corresponding to the point. We use the 5-m DEM (see Source Information) to generate a slope surface (Slope tool in 3D Analyst). The elevation and slope values are assigned to the points using the Extract Multi Values to Points tool in Spatial Analyst, which is called by bi-transect-extractor (Sturdivant, 2019). 'ptZmhw' is calculated from 'ptZ' by subtracting the MHW offset value (0.39 m based on Weber and others, 2005).
   Transect-averaged elevation:
   We calculate the per-transect mean and maximum barrier elevation (mean_Zmhw, max_Zmhw) from the 5-m elevations (ptZmhw). Mean barrier elevations are calculated for only those transects having less than 20 percent missing values within the 5-m points. Locations not satisfying this criterion are assigned a fill value. This is performed by the function aggregate_z in bi-transect-extractor (Sturdivant, 2019).
   Habitat variables:
   Variables for vegetation type (VegType), vegetation density (VegDens), substrate type (SubType), distance to foraging habitat (DisMOSH), and geomorphic setting (GeoSet) are populated from the corresponding raster layers provided with the larger work (files Mon14_VegType.tif, Mon14_VegDen.tif, Mon14_SubType.tif, Mon14_DisMOSH.tif, Mon14_GeoSet.tif). They are assigned to the points using the Extract Multi Values to Points tool in Spatial Analyst, which is called by bi-transect-extractor (Sturdivant, 2019).
   The values are recoded as follows using bi-transect-extractor, which is documented in the file extractor_mon14.ipynb.
   SubType: 7777:'{1111, 2222}', 1000:'{1111, 3333}’ VegType: 77:'{11, 22}', 88:'{22, 33}', 99:'{33, 44}' VegDens: 666: '{111, 222}', 777: '{222, 333}', 888: '{333, 444}', 999: '{222, 333, 444}'
   To calculate the values, the data are passed between Pandas dataframe format and ArcGIS geodatabase feature class. Once all values have been calculated, the Pandas dataframe is saved in comma-separated values (CSV) format. Curly brackets ('{}') around two values are used in the modeling process. Person who carried out this activity:
   

   Emily J. Sturdivant

   U.S. Geological Survey

   Geographer

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2230 (voice)

   508-457-2310 (FAX)

   esturdivant@usgs.gov

   Date: 2019 (process 6 of 7)

   Full methods are provided in the associated Methods OFR (Zeigler and others, 2019). For the detailed documentation of the processing, see the files extractor_mon14.ipynb and the source code bi-transect-extractor (Sturdivant, 2019).
   mon14_ubw.tif
   The width of the upper beach (from oceanside mean high water (MHW) shoreline to either dune crest, dune toe, or coastal armoring/development) is calculated along the supplemented NASC transects.
   Calculate beach width along transect:
   To calculate the beach width for the transects, upper beach width ('uBW') is calculated based on the difference in position between two points: the position of MHW along the transect ('SL_x', 'SL_y') and the dune toe position or equivalent (usually 'DL_x', 'DL_y'). It is calculated using bi-transect-extractor (Sturdivant, 2019) and documented in extractor_mon14.ipynb as follows:
   (1) Find the position along the transect of an orthogonal line drawn to the dune point ('DL_x', 'DL_y' and 'DH_x', 'DH_y'). (2) Calculate distances from MHW to the position along the transect of the dune toe ('DistDL'), dune crest ('DistDH'), and armoring ('DistArm'). (3) Conditionally select the appropriate feature to represent "top of beach." Dune toe is prioritized. If it is not available and 'DH_zMHW' is less than or equal to maxDH, use dune crest. If neither of the dune feature positions satisfy the conditions and an armoring feature intersects with the transect, use the armoring position. If none of the three are possible, 'uBW' is given a NoData value of -99999. (4) Copy the selected distance to oceanside shoreline and height above MHW ('Dist--') to 'uBW'.
   Assign values to raster
   A transect ID raster is created from the transect file. Transects are modified from the supplemented transect file (mon_trans.shp) by manually shortening overlapping transects to the first point of intersection. Overlapping transects were ignored if the area of overlap did not intersect land. When a transect overlaps with a supplementary transect, the supplementary transect is shortened to the intersection point. The beach width values from each transect are assigned to the cells that represent that transect using the JoinField tool in the data management toolbox, which is also an automated process performed by bi-transect-extractor.
   The raster file is exported to GeoTiff using the Export Raster tool. Raster cells outside the bounds of the data are assigned a NoData value of 16. Person who carried out this activity:
   

   Emily J. Sturdivant

   U.S. Geological Survey

   Geographer

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2230 (voice)

   508-457-2310 (FAX)

   esturdivant@usgs.gov

   Date: 10-Aug-2020 (process 7 of 7)

   Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
   

   U.S. Geological Survey

   Attn: VeeAnn A. Cross

   Marine Geologist

   384 Woods Hole Road

   Woods Hole, MA
   

   508-548-8700 x2251 (voice)

   508-457-2310 (FAX)

   vatnipp@usgs.gov

3. What similar or related data should the user be aware of?
   Zeigler, Sara L., Sturdivant, Emily J., and Gutierrez, Benjamin T., 2019, Evaluating barrier island characteristics and piping plover (Charadrius melodus) habitat availability along the U.S. Atlantic coast—Geospatial approaches and methodology: Open-File Report 2019–1071, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.3133/ofr20191071

   Other_Citation_Details:

   Details the methods used to process these data for use in barrier island and piping plover habitat modeling.

   Weber, Kathryn M., List, Jeffrey H., and Karen L. M. Morgan, 2005, An Operational Mean High Water Datum for Determination of Shoreline Position from Topographic Lidar Data: Open-File Report 2005-1027, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.3133/ofr20051027
   • https://pubs.usgs.gov/of/2005/1027/

   Rice, Tracy M., Hecht, Anne, and Terwilliger, Karen, 2015, Beach and Tidal Habitat Inventories: North Atlantic Landscape Conservation Cooperative, Hadley, MA.

   Online Links:

   • https://northatlanticlcc.org/teams/coastal-resiliency/projects/beach-and-tidal-inlet-habitat-inventories/habitat-inventories-prior-to-hurricane-sandy
   • https://databasin.org/galleries/164daee0855c4228bb6fe8552e704558
   • https://northatlanticlcc.org/teams/coastal-resiliency/projects/beach-and-tidal-inlet-habitat-inventories/beach-and-tidal-inlet-habitat-inventories
   • https://northatlanticlcc.org/products/synthesis-of-tidal-inlet-and-beach-habitat-inventories

   Other_Citation_Details:

   Includes "Inventory of Habitat Modifications to Tidal Inlet and Sandy Beach Habitat Prior to Hurricane Sandy (2012)""

   Sturdivant, Emily J., 2019, bi-transect-extractor: software release DOI:10.5066/P915UYMY, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.5066/P915UYMY
   • https://code.usgs.gov/cmgp/bi-transect-extractor

   Other_Citation_Details:

   Custom-built package used for data processing. The Jupyter notebook file distributed with these data were part of the processing to create these data. The notebook relies on this software package.

   Neuendorf, Klaus K.E., James P. Mehl, Jr., and Jackson, Julia A., 2011, Glossary of geology. Fifth edition: The American Geosciences Institute, Alexandria, VA.

   Godfrey, Paul J., 1976, Comparative ecology of East Coast barrier islands—Hydrology, soil, vegetation, in Barrier islands and beaches: Technical proceedings of the 1976 Barrier Islands Workshop, Annapolis, Maryland, May 17–18, 1976 p. 5–31, The Conservation Foundation, Washington, D.C..

   U.S. Department of Agriculture (USDA), and USDA Natural Resources Conservation Service (NRCS), 2015, The PLANTS Database: National Plant Data Team, Greensboro, NC.

   Online Links:

   • http://plants.usda.gov

   Other_Citation_Details: accessed 13 January 2014
   

How reliable are the data; what problems remain in the data set?

1. How well have the observations been checked?
   Attribute values at each point (mon14_pts.csv) represent a 5 x 5 m square centered at the point. The values are compiled from multiple sources. Transect-averaged values, such as beach width, may represent 25 m on either side of the indicated transect. The following methods were used to validate attribute accuracy: symbolized display of transect and point attribute values overlaid on input datasets including elevation, barrier extent, geomorphic feature (ArcGIS Pro version 2.0); spot-checking of values at individual points and comparison with input datasets and topology (ArcGIS Pro version 2.0); and for random transects, plotting the cross-shore profile using elevation values from each point along the transect, distance values and the cross-shore position of the features they were calculated from (Matlab R2015b). These checks were performed by at least two operators.
   Metrics related to the geomorphic feature points (i.e. dune toe, dune crest, shoreline) do not necessarily provide accurate measurements for bay-side areas. For example, in rare situations a transect might intersect multiple oceanside shorelines, possibly due to the orientation of an inlet (e.g. transect 459 at Rhode Island, ri_trans.shp in larger work), but the single dune crest point associated with the transect is simply the closest point, whether it be on the ocean-side portion of land or not. Thus, the distance to dune crest values may not be realistic for a portion of the points along the transect.
   mon14_ubw.tif: Accuracy of the beach width value is dependent on the accuracy of the lineage data. Beach widths are calculated to the tenths of meters in precision. However, the values are only calculated every 50 m alongshore. Thus, a given cell value may represent the width of the beach at a transect as far as 25 m removed from the cell. Refer to the process steps for details. Beach width values were spot-checked while verifying the reliability of the transect values. Spot checks were performed by plotting the beach width on a cross-shore elevation profile with the available dune positions positioned on the plot as well. These values were always found to be in agreement unless reported elsewhere.
   More detail is provided elsewhere below (Process Steps and Entity and Attribute Information), in the associated Open-File Report (Zeigler and others, 2019), and in the source code (Sturdivant, 2019).
2. How accurate are the geographic locations?
   Depending on the attribute, the accuracy is assumed to be between 5 and 25 m. The horizontal positional accuracy is dependent on the accuracy of the source data and error incorporated during processing. Refer to the process steps for details.
3. How accurate are the heights or depths?
   The vertical accuracy of those attributes that incorporate vertical position is dependent on the digital elevation model and its source data (see Source Information in Process Steps) as well as the MHW datum produced by Weber and others (2005).
4. Where are the gaps in the data? What is missing?
   Dataset completeness is dependent on the completeness of the source data. Transects (mon_trans.shp) are spaced alongshore approximately every 50 m within the study area, with substantial variation on the western side. Not all transects intersect land and transects may overlap. Points (mon14_pts.csv) are spaced every 5 m along the transects within the full island shoreline polygons (mon14_shoreline.shp in the larger work; see Process Steps). Points may not extend to the end of a transect to prevent oversampling (see the fourth Process Step). The beach width raster (mon14_ubw.tif) covers the same extent as the transects.
5. How consistent are the relationships among the observations, including topology?
   These datasets consist of data compiled from multiple sources and aggregated spatially. The data were reviewed using standard USGS review procedures. No checks for topological consistency in addition to those described in the Attribute Accuracy Report were performed on these data. The primary vertical datum used is NAVD88, consistent with the source datasets lidar and geomorph points. Some fields (those with a 'mhw' suffix and explained in the Entity and Attribute section) include the elevation adjusted to the mean high water (MHW) datum calculated by Weber and others (2005) for the area. The field 'MHW' in the transects (mon_trans.shp) indicates the MHW offset along the given transect.
   mon14_pts.csv: With increasing distance of a point from the ocean-facing side of the barrier, there is less likely to be a direct orthogonal relationship between the value and the oceanside shoreline. Prior to segmenting transects into 5-m points, some transects were shortened to eliminate overlap (see first Process Step). Thus transect-based values at back-barrier points could pertain to a more distant shoreline. Where a given attribute value could not be calculated due to lack of input data in the lineage dataset, a NoData value of -99999 was recorded for the attribute. Where a transect does not intersect land, it corresponds to a single point with NoData values for all attributes. More detail is provided in the associated Open-File Report (Zeigler and others, 2019) and in the Entity and Attribute Information.
   mon_trans.shp: This shapefile consists of line data compiled from NASC transects and manual additions. Original NASC transects include ID values ('TRANSECTID') that match them to the original transect and supplemental transects have a NoData value for NASC attributes ('TRANSECTID', 'LRR'). Transects are identified by the field 'sort_ID,' which orders transects sequentially (from south to north) along the shoreline. Transects are spaced alongshore approximately every 50 m within the study area, which is a rough delineation that extends beyond the island outline at most sites. Transect extent and distribution is based on the study area rather than the shoreline, to allow transect positions to encompass the land in years with different shoreline positions. As a result, some transects may not intersect land in certain years. Curves in the generalized shoreline may cause transect spacing to vary from the standard 50 m alongshore, especially along the western side of the study area. Transects are not always orthogonal to the section of shore they intersect. Transects may overlap. In such cases, the complete transect was preserved allowing overlap so that each transect could measure the full width of the barrier. Transects are the base features for mon14_pts.csv and mon14_ubw.tif.
   mon14_ubw.tif: With increasing distance of a cell from the ocean-facing side of the barrier, there is less likely to be a direct orthogonal relationship between the cell value and the beach because transects were shortened to eliminate overlap prior to assigning the line values to the raster grid. Cells may not have the same value as neighboring cells directly oceanward because of the same overlap-elimination process applied to the transects. Where values could not be calculated due to lack of input data in the lineage dataset, a NoData value was recorded for the attribute.

How can someone get a copy of the data set?

1. Who distributes the data set? (Distributor 1 of 1)
   
   U.S. Geological Survey - ScienceBase

   Denver Federal Center, Building 810, Mail Stop 302

   Denver, CO
   

   USA

   1-888-275-8747 (voice)

   sciencebase@usgs.gov
2. What's the catalog number I need to order this data set? This dataset contains three individual datasets: point data as a generic comma-separated ASCII formatted data file (mon14_pts.csv); an Esri shapefile with transect geometries and index values (mon_trans.shp and other shapefile components); and a 16-bit GeoTIFF file containing the upper beach width values (mon14_ubw.tif and associated value attribute table). The CSDGM FGDC metadata describing the datasets in XML format (mon14_pts_trans_ubw_meta.xml) and the browse graphic (pts_browse.png) are also included as well as the Jupyter notebook (extractor_mon14.ipynb) used for processing. These datasets can be downloaded individually or packaged on-demand in a zip file (see the Digital Transfer Option section).
3. What legal disclaimers am I supposed to read?
   Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), and have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
4. How can I download or order the data?
   • Availability in digital form:

     Data format:

     This dataset contains 5-m point data as a comma-separated values (CSV) table (18 MB), a polyline shapefile (0.06 MB), and a 16-bit GeoTIFF of beach width (10.7 MB). The GeoTIFF and its values attribute table must be stored together. Also included are the Jupyter notebook used for processing, the CSDGM metadata, and the browse graphic. in format CSV (version ArcGIS Pro 2.0) comma-separated values table Size: 28

     Network links:

     https://www.sciencebase.gov/catalog/item/5daa3730e4b09fd3b0c9ce30 https://www.sciencebase.gov/catalog/file/get/5daa3730e4b09fd3b0c9ce30 https://doi.org/10.5066/P9V7F6UX

     Data format:	This dataset contains 5-m point data as a comma-separated values (CSV) table (18 MB), a polyline shapefile (0.06 MB), and a 16-bit GeoTIFF of beach width (10.7 MB). The GeoTIFF and its values attribute table must be stored together. Also included are the Jupyter notebook used for processing, the CSDGM metadata, and the browse graphic. in format GeoTIFF (version ArcGIS Pro 2.0) GeoTIFF Size: 58.1
     Network links:	*** *** ***

     Data format:

     This dataset contains 5-m point data as a comma-separated values (CSV) table (18 MB), a polyline shapefile (0.06 MB), and a 16-bit GeoTIFF of beach width (10.7 MB). The GeoTIFF and its values attribute table must be stored together. Also included are the Jupyter notebook used for processing, the CSDGM metadata, and the browse graphic. in format Shapefile (version ArcGIS Pro 2.0) Esri polyline shapefile Size: 28

     Network links:

     *** *** ***

   • Cost to order the data: None

5. What hardware or software do I need in order to use the data set?
   To utilize these data, the user must have software capable of reading a comma-delimited data file, shapefile format, and 16-bit GeoTIFF with associated values attribute table.

Who wrote the metadata?

Dates:

Last modified: 19-Mar-2024

Metadata author:

Sara L. Zeigler

U.S. Geological Survey

384 Woods Hole Road

Woods Hole, MA

USA

508-548-8700 x2290 (voice)

(508) 457-2310 (FAX)

whsc_data_contact@usgs.gov

Contact_Instructions:

The metadata contact email address is a generic address in the event the person is no longer with USGS. (updated on 20240319)

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)