Satellite-derived shoreline vector files and settings from CoastSeg in multiple U.S. locations (1984-2023)

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?
   Buscombe, Daniel D., Burgess, Joseph, Doran, Kara S., Batiste, Sharon N., Gibbs, Ann E., Henderson, Rachel E., Heslin, Julia L., Janda, Catherine N., Lundine, Mark A., O'Neill, Andrea C., Terrano, Joseph F., Warrick, Jonathan A., and Weber, Kathryn M., 20250425, Satellite-derived shoreline vector files and settings from CoastSeg in multiple U.S. locations (1984-2023): data release DOI:10.5066/P1NUEFDP, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

   Online Links:

   • https://doi.org/10.5066/P1NUEFDP

   This is part of the following larger work.
   Buscombe, Daniel D., Burgess, Joseph, Doran, Kara S., Batiste, Sharon N., Gibbs, Ann E., Henderson, Rachel E., Heslin, Julia L., Janda, Catherine N., Lundine, Mark A., O'Neill, Andrea C., Terrano, Joseph F., Warrick, Jonathan A., and Weber, Kathryn M., 2025, Satellite-derived shorelines from CoastSeg in multiple U.S. locations (1984-2023): data release DOI:10.5066/P1NUEFDP, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

   Online Links:

   • https://doi.org/10.5066/P1NUEFDP

   Other_Citation_Details:

   Suggested Citation: Buscombe, D., Burgess, J., Doran, K., Fitzpatrick, S., Gibbs, A., Henderson, R., Heslin, J., Janda, C., Lundine, M., O'Neill, A.C., Terrano, J., Warrick, J., and Weber, K., 2025, Satellite-derived shorelines from CoastSeg in multiple U.S. locations (1984-2023): U.S. Geological Survey data release, https://doi.org/10.5066/P1NUEFDP.

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -143.83834890
   East_Bounding_Coordinate: -67.23436190
   North_Bounding_Coordinate: 70.15710875
   South_Bounding_Coordinate: 18.31396108
   

3. What does it look like?

   SDS_vectorfiles_and_settings_multiplelocations_1984-2023.png (png)

   Image map showing study areas for satellite-derived shoreline vector files and settings in multiple locations.

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

   Beginning_Date: 1984

   Ending_Date: 2023

   Currentness_Reference:

   collection years of satellite imagery used to determine shoreline positions

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

   Geospatial_Data_Presentation_Form: Shoreline vectors and settings in GeoJSON formats
   

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?
      This is a Vector data set.
   2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.00000001. Longitudes are given to the nearest 0.00000001. Latitude and longitude values are specified in Decimal Degrees. The horizontal datum used is World Geodetic System 1984 (WGS84).
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
      

      Vertical_Coordinate_System_Definition:

      Depth_System_Definition:

      Depth_Datum_Name: Mean Sea Level
      Depth_Resolution: 0.01
      Depth_Distance_Units: meters
      Depth_Encoding_Method: Implicit coordinate
      

7. How does the data set describe geographic features?

   Satellite-derived shorelines and associated CoastSeg settings for historical period (1984-2023) for multiple locations

   GeoJSON files consist of shoreline positions (extracted shorelines) derived from imagery for multiple locations across the United States, and include reference shorelines, Regions of Interest (ROIs), transects, and other settings used in CoastSeg. (Source: Producer defined)

   id

   Identification label of transects (numeric) and ROIs (alphanumeric) used in satellite derivation. IDs are only presented for transects and ROIs. (Source: Producer defined) IDs of ROIs are alphanumeric and are unique to each site. IDs of transects are numeric and increase in number across each site; starting values are unique to each site.

   type

   Type of vector output presented: extracted shoreline, reference shoreline, transect, or ROI (Source: Producer defined)

   Value	Definition
   extracted shoreline	Shoreline vector is an extracted shoreline from CoastSeg for listed date. Vector vertices are from shoreline positions derived along transects. Shoreline vector is connected along consecutive transects and split if consecutive data is not present.Shoreline vector is an extracted shoreline from CoastSeg for listed date. Vector vertices are from shoreline positions derived along transects. Shoreline vector is connected along consecutive transects and split if consecutive data is not present.
   reference shoreline	Reference shoreline vector is the reference shoreline used in CoastSeg to identify satellite-derived shoreline positions along transects.
   transect	Transect vectors are transects used in CoastSeg to identify satellite-derived shoreline positions.
   ROI	ROI vectors are Regions of Interest (ROI) used in CoastSeg to identify areas to download imagery and identify shoreline positions.

   settings

   Information about CoastSeg settings used in the specified ROI to derive the extracted shorelines. (Source: Producer defined) Settings contains information on Landsat satellites used, date ranges, and specific settings used within CoastSeg. See Fitzgerald and others (2024a, 2024b) for details of all settings.

   settings: landsat collection

   Subfield within settings that specifies the Landsat collection sourced for satellite imagery. (Source: Producer defined)

   Value	Definition
   CO2	Landsat Collection 2

   settings: dates

   Subfield within settings that details the start and end dates of imagery searched within each ROI, where date (UTC) is in yyyy-mm-dd (where yyyy is 4 digit year, mm is 2-digit month, and dd is 2-digit day). (Source: Producer defined)

   Range of values
   Minimum:	1984-01-01
   Maximum:	2023-12-31
   Units:	day
   Resolution:	1

   settings: months_list

   Subfield within settings that details the months that were searched within each ROI for imagery, where the month is identified by its numeral. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	12
   Units:	month
   Resolution:	1

   settings: sat_list

   Subfield within settings that details which satellites (Landsat 5-9, Sentinel 2) were used in a search for available imagery within each ROI. (Source: Producer defined)

   Formal codeset
   Codeset Name:	L5, L7, L8, L9, S2
   Codeset Source:	Producer defined

   settings: cloud_thresh

   Subfield within settings that specifies the cloud threshold (maximum percentage of clouds in image) allowed to exist within the ROI in CoastSeg. (Source: Producer defined)

   Range of values
   Minimum:	0.0
   Maximum:	1.0
   Units:	fractional percentage
   Resolution:	0.1

   settings: percent_no_data

   Subfield within settings that specifies the bad-pixel threshold for imagery (as a fractional percentage) used in the ROI in CoastSeg. (Source: Producer defined)

   Range of values
   Minimum:	0.0
   Maximum:	1.0
   Units:	fractional percentage
   Resolution:	0.1

   settings: dist_clouds

   Subfield within settings that specifies a buffer distance from clouds to identify shorelines used in the ROI. (Source: Producer defined)

   Range of values
   Minimum:	0
   Maximum:	300
   Units:	meters
   Resolution:	10

   settings: output_epsg

   Subfield within settings that specifies the coordinate system reference for CoastSeg outputs. (Source: Producer Defined)

   Range of values
   Minimum:	32607
   Maximum:	32619
   Units:	EPSG projection identifer
   Resolution:	1

   settings: check_detection

   Subfield within settings that specifies whether the shoreline detection figures should be created in CoastSeg. (Source: Producer Defined)

   Value	Definition
   false	all identification figures are not created

   settings: adjust_detection

   Subfield within settings that specifies whether the user should be allowed to manually modify the Modified Normalized Difference Water Index (MNDWI) threshold for detecting the shoreline for each image. False by default in CoastSeg. (Source: Producer Defined)

   Value	Definition
   false	default MNDWI threshold was not modified

   settings: save_figure

   Subfield within settings that specifies whether figures of the shoreline detection for each image are saved. (Source: Producer Defined)

   Value	Definition
   true	detection images for each downloaded satellite image are saved

   settings: min_beach_area

   Subfield within settings that specifies a minimum beach area/width to identify shorelines within in the ROI. (Source: Producer defined)

   Range of values
   Minimum:	50
   Maximum:	6750
   Units:	meters
   Resolution:	10

   settings: min_length_sl

   Subfield within settings that specifies a minimum shoreline length (alongshore) to identify shorelines within in the ROI. (Source: Producer defined)

   Range of values
   Minimum:	50
   Maximum:	500
   Units:	meters
   Resolution:	10

   settings: cloud_mask_issue

   Subfield within settings that specifies whether the default cloud masking algorithm is erroneously masking the shoreline. (Source: Producer Defined)

   Value	Definition
   false	default satellite-source cloud mask was used

   settings: sand_color

   Subfield within settings that specifies sand color used for shoreline detection in the ROI. (Source: Producer Defined)

   Value	Definition
   default	default sand color is used in land classification

   settings: pan_off

   Subfield within settings that controls whether pan-sharpening is applied to the images before shoreline detection in CoastSeg. (Source: Producer Defined)

   Value	Definition
   False	pan-sharpening was not applied

   settings: max_dist_ref

   Subfield within settings that specifies a maximum distance to the reference shoreline to identify shorelines within in the ROI. (Source: Producer defined)

   Range of values
   Minimum:	100
   Maximum:	1000
   Units:	meters
   Resolution:	10

   settings: along_dist

   Subfield within settings that defines the maximum alongshore distance from the transect at which shoreline points are considered for calculating intersections. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	100
   Units:	meters
   Resolution:	5

   settings: min_points

   Subfield within settings that defines the minimum number of shoreline points required to identify a valid shoreline intersection with the transect. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	5
   Units:	points
   Resolution:	1

   settings: max_std

   Subfield within settings that defines the maximum standard deviation for the shoreline points when calculating the median intersection with the transects. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	15
   Units:	points
   Resolution:	0.1

   settings: max_range

   Subfield within settings that defines the maximum range allowed for the shoreline points when calculating the median intersection with the transects. (Source: Producer defined)

   Range of values
   Minimum:	1
   Maximum:	30.0
   Units:	points
   Resolution:	0.1

   settings: min_chainage

   Subfield within settings that specifies the furthest distance landward from the transect origin that a shoreline intersection is accepted. (Source: Producer defined)

   Range of values
   Minimum:	-100.00
   Maximum:	0
   Units:	points
   Resolution:	0.1

   settings: multiple_inter

   Subfield within settings that specifies how a scenario with multiple shoreline points intersecting a transect should be processed. (Source: Producer defined)

   Value	Definition
   auto	will set multiple intersection points to the furthest shoreline point (maximum distance) if the standard deviation of all the shoreline intersections is above the max_std value, otherwise it will assign these shoreline points as null.

   settings: prc_multiple

   Subfield within settings that specifies a percentage of shoreline points that can exceed the 'max_std' setting value in 'auto' mode. If this value is exceeded, then any case where multiple shoreline points intersected the transect these intersections will be set to the max shoreline intersection point, otherwise these points will be set to null. (Source: Producer defined)

   Range of values
   Minimum:	0
   Maximum:	1
   Units:	points
   Resolution:	0.1

   settings: apply_cloud_mask

   Subfield within settings that specifies whether the cloud mask in imagery is used. (Source: Producer defined)

   Value	Definition
   true	a cloud mask in level 2 imagery is used and shorelines are identified outside this mask and any buffer distances.
   false	a cloud mask in level 2 imagery is not used and shorelines are identified throughout the image

   settings: image_size_filter

   Subfield within settings that specifies whether the images were classified as bad if the image area did not meet the minimum area allowed. (Source: Producer defined)

   Value	Definition
   true	images that cover less than 40% of the ROI area are classified as bad, and only images that cover more than 40% of the ROI are used for shoreline detection

   settings: drop_intersection_pts

   Subfield within settings that controls whether shoreline intersection points that did not land on the transect should be removed or not. False by default. (Source: Producer defined)

   Value	Definition
   true	intersection points that do not land on a transect are removed
   false	intersection points that do not land on a transect are kept

   date

   Date and time of projected data (UTC) in yyyy-mm-dd HH:MM:ss format (where yyyy is 4 digit year, mm is 2-digit month, dd is 2-digit day, HH is hour in 24-hour notation, MM is minute, and ss is seconds). (Source: Producer defined)

   Range of values
   Minimum:	1984-01-01 00:00:00
   Maximum:	2023-12-31 00:00:00
   Units:	yyyy-mm-dd HH:MM:ss
   Resolution:	1

   Entity_and_Attribute_Overview:

   Each GeoJSON file depicts shorelines (as vectors, where vertices are positions determined along transects) derived from satellite imagery and associated configuration settings and setup data used in CoastSeg to derive the shoreline positions. Files are generated for several tidal correction values, including: average slope, low slope, high slope, and no correction (no tidal correction). Files are packaged into zip files by site location (for example satellite-derived-shoreline_coastseg-vectors_BarterIsland.zip), and individual files are named for the correction (for example, coastseg_config_shorelines_averageslopecorrection_Barter.geojson is the file for Barter Island and the average slope tidal correction).

   Entity_and_Attribute_Detail_Citation: U.S. Geological Survey
   

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Daniel D. Buscombe
   • Joseph Burgess
   • Kara S. Doran
   • Sharon N. Batiste
   • Ann E. Gibbs
   • Rachel E. Henderson
   • Julia L. Heslin
   • Catherine N. Janda
   • Mark A. Lundine
   • Andrea C. O'Neill
   • Joseph F. Terrano
   • Jonathan A. Warrick
   • Kathryn M. Weber
2. Who also contributed to the data set?
   This data release was funded by the USGS Coastal and Marine Hazards and Resources Program.
3. To whom should users address questions about the data?
   U.S. Geological Survey, Pacific Coastal and Marine Science Center

   Attn: PCMSC Science Data Coordinator

   2885 Mission Street

   Santa Cruz, CA
   

   831-427-4747 (voice)

   pcmsc_data@usgs.gov

Why was the data set created?

How was the data set created?

1. From what previous works were the data drawn?

   Landsat imagery (source 1 of 10)

   U.S. Geological Survey, 2025, Landsat imagery (from Landsat 5): U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/P9IAXOVV

   Type_of_Source_Media: online database
   Source_Contribution:

   The archive of Landsat 5 satellite imagery was accessed through Google Earth Engine and was used to derive shoreline positions for the study area.

   Landsat imagery (source 2 of 10)

   U.S. Geological Survey, 2025, Landsat imagery (from Landsat 7): U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/P9C7I13B

   Type_of_Source_Media: online database
   Source_Contribution:

   The archive of Landsat 7 satellite imagery was accessed through Google Earth Engine and was used to derive shoreline positions for the study area.

   Landsat 8-9 imagery (source 3 of 10)

   U.S. Geological Survey, 2023, Landsat 8-9 imagery for multiple locations: U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/P975CC9B

   Type_of_Source_Media: online database
   Source_Contribution:

   The archive of Landsat 8-9 satellite imagery was used to derive shoreline positions for the study area.

   Sentinel 2 imagery (source 4 of 10)

   Agency, European Space, 2023, Sentinel 2 imagery for multiple locations: Copernicus, online.

   Online Links:

   • https://dataspace.copernicus.eu/explore-data/data-collections/sentinel-data/sentinel-2

   Type_of_Source_Media: online database
   Source_Contribution:

   The archive of Sentinel 2 satellite imagery was used to derive shoreline positions for the study area.

   FES 2014 (source 5 of 10)

   Carrere, L., Lyard, F., Cancet, M., Guillot, A., and Picot, N., 20160501, FES (Finite Element Solution) 2014, a new tidal model—Validation results and perspectives for improvements: AVISO, online.

   Online Links:

   • https://www.aviso.altimetry.fr/en/data/products/auxiliary-products/global-tide-fes/description-fes2014.html

   Type_of_Source_Media: online model
   Source_Contribution:

   Tidal corrections in the shoreline position were made with tide height predicted from the FES 2014 model.

   Barter slopes (source 6 of 10)

   Gibbs, A.E., Nolan, M., and Snyder, A.G., 20190226, Orthophotomosaics, elevation point clouds, digital surface elevation models and supporting data from the north coast of Barter Island, Alaska: U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/P9964TKX

   Type_of_Source_Media: online dataset
   Source_Contribution:

   beach slope data used to correct shoreline positions for tidal water levels

   Cape Cod slopes (source 7 of 10)

   Farris, A.S., Weber, K.M., and List, J.H., 20200922, Mean high water shorelines for the Outer Cape of Massachusetts from Nauset Inlet to Race Point (1998-2005): U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/P9GWL52F

   Type_of_Source_Media: online dataset
   Source_Contribution:

   beach slope data used to correct shoreline positions for tidal water levels

   Elwha slopes (source 8 of 10)

   Stevens, A.W., Gelfenbaum, G., Warrick, J.A., Miller, I.M., and Weiner, H.M., 20171208, Bathymetry, topography, and sediment grain-size data from the Elwha River delta, Washington (ver. 5.0, November 2024): U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/F72N51GC

   Type_of_Source_Media: online dataset
   Source_Contribution:

   beach slope data used to correct shoreline positions for tidal water levels

   Madeira slopes (source 9 of 10)

   Brown, J.A., J.J., Birchler, Thompson, D.M., Long, J.W., and Seymour, A.C., 20180314, Beach Profile Data Collected From Madeira Beach, Florida: U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/F7T43S94

   Type_of_Source_Media: online dataset
   Source_Contribution:

   beach slope data used to correct shoreline positions for tidal water levels

   Rincon slopes (source 10 of 10)

   Doran, K.S., Long, J.W., Birchler, J.J., Brenner, O.W., Hardy, M.W., Morgan, K.L.M., Stockdon, H.F., and Torres, M.L., 20170805, Lidar-derived Beach Morphology (Dune Crest, Dune Toe, and Shoreline) for U.S. Sandy Coastlines: U.S. Geological Survey, online.

   Online Links:

   • https://doi.org/10.5066/F7GF0S0Z

   Type_of_Source_Media: online dataset
   Source_Contribution:

   beach slope data used to correct shoreline positions for tidal water levels

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

   Date: 01-Sep-2023 (process 1 of 6)

   Set up CoastSeg program (Fitzpatrick and others, 2024a; Fitzpatrick and others, 2024b; Buscombe and Fitzpatrick, 2023) for each location. CoastSeg is set up using python 3.7 installed via pip into a conda environment. Regions of Interest (ROIs), transects, and reference shorelines were generated, as included in this data release. For Barter Island, ROIs were generated outside CoastSeg, using the standard CoastSeg sizes, to preserve recommended land-ocean area ratios (Vos and others, 2019) around complex coastlines. In Cape Cod, Elwha, Madeira, and Rincon, ROIs were generated within CoastSeg. Transects were generated outside CoastSeg for all locations and setup to have 30m – 140m alongshore spacing. DSAS (Himmelstoss and others, 2018) was used for Barter Island, Cape Cod, Madeira, and Rincon, to adjust transect orientation (with landward origin point) and consecutive transect labels. CoastSeg’s default reference shoreline was used in Cape Cod, Madeira Beach, and Rincon. In Barter Island and Elwha, a reference shoreline was created outside CoastSeg to reflect older shoreline positions and significant shoreline change over the observation period. These and other settings used at each site are explicitly listed in the shoreline vectors files, included in this data release. See Fitzpatrick and others (2024a, 2024b) and Vos and others (2019) for details on settings, ROIs, transects, reference shorelines, and using CoastSeg.

   Date: 01-Feb-2024 (process 2 of 6)

   After initial setup of ROIs, transects, reference shorelines and settings, the CoastSeg program was run to download all available imagery for satellites (Landsat 5, 7, 8, and 9 for all locations, and also Sentinel 2 for Barter Island) between 1 January 1984 and 31 December 2023. For Barter Island, imagery collected during months when sea-ice is typically present (October – May) were removed. Data sources used in this process:

   • Landsat imagery
   • Landsat 8-9 imagery
   • Sentinel imagery

   Date: 30-Apr-2024 (process 3 of 6)

   After all imagery was downloaded, shorelines were detected within each ROI. Initial shoreline detection images were reviewed and images with bad detections, due to clouds and weather, were manually removed from analysis and the shoreline detection process-step was repeated in CoastSeg. Output from this step included CSV and GeoJSON data for raw (not tidally corrected) shoreline positions. Data sources used in this process:

   • Landsat imagery
   • Landsat 8-9 imagery
   • Sentinel imagery

   Data sources produced in this process:

   • uncorrected shorelines

   Date: Sep-2024 (process 4 of 6)

   Once raw, uncorrected shoreline positions were generated, tidal corrections were conducted using three different slope values (average, high and low) to show the variance of beach slope conditions at each site. Slope values were determined from in situ beach survey and elevation data. Average slope values were defined as the mean from respective datasets for Cape Cod, Elwha and Madeira Beach (Farris and others, 2020; Stevens and others, 2017; Brown and others, 2018), and high/low slope values were defined as +/- 2 standard deviations away from the mean. Because detailed slope data was not available at Barter Island for the study period, slopes at Barter Island were determined empirically from various locations across the site based on elevation data from 2014-2015 (Gibbs and others, 2019). Average, low, and high slope values were derived from the aggregate data (as mean, minimum, and maximum, respectively). Slope values were similarly determined at Rincon based on the elevation dataset from Doran and others (2018). Average/high/low slope values used for Barter Island are 0.07/0.15/0.01; values for Cape Cod are 0.13/0.201/0.061; values for Elwha are 0.125/0.15/.01; values for Madeira are 0.08/0.1596/0.033; and values for Rincon are 0.1287/0.3968/0.0211. Output from this step included tidally corrected CSV and GeoJSON shoreline positions. Tidal corrections were applied using tide heights estimated from the FES 2014 Tidal model. Data sources used in this process:

   • FES 2014
   • uncorrected shorelines
   • Barter slopes
   • Cape Cod slopes
   • Elwha slopes
   • Madeira slopes
   • Rincon slopes

   Date: 15-Dec-2024 (process 5 of 6)

   Output was checked to ensure quality results. In dynamic locations, including areas such as river mouths, capes, and ends of spits, uncertainty can increase, and shorelines in these locations should be inspected and used with care.

   Date: 17-Jan-2025 (process 6 of 6)

   Data were packaged and prepared for data release. Data are zipped together by location and labeled according to whether the SDS are uncorrected or are tidally corrected (using average, high, or low beach slope values). GeoJSON files contain both the CoastSeg setup settings (including ROI, transects, and reference shoreline), and the output shorelines as vectors where vertices are the positions along each transect. CSV files contain the shoreline positions along each transect.

3. What similar or related data should the user be aware of?
   Fitzpatrick, S., Buscombe, D., Warrick, J.A., Lundine, M.A., and Vos, K., 2024, CoastSeg: an accessible and extendable hub for satellite-derived-shoreline (SDS) detection and mapping.

   Online Links:

   • https://doi.org/10.21105/joss.06683

   Other_Citation_Details:

   Fitzpatrick, S., Buscombe, D., Warrick, J.A., Lundine, M.A., and Vos, K., 2024a, CoastSeg: an accessible and extendable hub for satellite-derived-shoreline (SDS) detection and mapping: Journal of Open Source Software, v. 99(99), 6683.

   Fitzpatrick, S., Buscombe, D., Warrick, J.A., Lundine, M.A., and Vos, K., 2024, CoastSeg: an accessible and extendable hub for satellite-derived-shoreline (SDS) detection and mapping.

   Online Links:

   • https://doi.org/10.5281/zenodo.12555413

   Other_Citation_Details:

   Fitzpatrick, S., Buscombe, D., Warrick, J.A., Lundine, M.A., and Vos, K., 2024b, CoastSeg: an accessible and extendable hub for satellite-derived-shoreline (SDS) detection and mapping: (v1.2.9). Zenodo. https://doi.org/10.5281/zenodo.12555413

   Buscombe, D., and Fitzpatrick, S., 2023, CoastSeg: Beach transects and beachface slope database v1.0 (Version v1.0).

   Online Links:

   • https://doi.org/10.5281/zenodo.8187949

   Other_Citation_Details:

   Buscombe, D., & Fitzpatrick, S., 2023, CoastSeg: Beach transects and beachface slope database v1.0 (v1.0). Zenodo. https://doi.org/10.5281/zenodo.8187949

   Vos, K., Splinter, K.D., Harley, M.D., Simmons, J.A., and Turner, I.L., 2019, CoastSat: A Google Earth Engine-enabled Python toolkit to extract shorelines from publicly available satellite imagery.

   Online Links:

   • https://doi.org/10.1016/j.envsoft.2019.104528

   Other_Citation_Details:

   Vos, K., Splinter, K.D., Harley, M.D., Simmons, J.A., and Turner, I.L., 2019, CoastSat: A Google Earth Engine-enabled Python toolkit to extract shorelines from publicly available satellite imagery: Environmental Modelling and Software, v. 122, 104528.

   Himmelstoss, E.A., Farris, A.S., Henderson, R.E., Kratzmann, M.G., Ergul, A., Zhang, O., Zichichi, J.L., and Thieler, E.R., 2021, Digital Shoreline Analysis System (version 5.1).

   Online Links:

   • https://code.usgs.gov/cch/dsas

   Other_Citation_Details:

   Himmelstoss, E.A., Farris, A.S., Henderson, R.E., Kratzmann, M.G., Ergul, A., Zhang, O., Zichichi, J.L., Thieler, E.R., 2021, Digital Shoreline Analysis System (version 5.1): U.S. Geological Survey software release, https://code.usgs.gov/cch/dsas.

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

1. How well have the observations been checked?
   Attribute values are estimates of shoreline position based on satellite imagery. The accuracy of this method was assessed by Vos and others (2019), who compared data with ground-based surveys at Duck, North Carolina. In line with these estimates, a cross-shore horizontal error of 10 m (root mean square error) can be used in most locations. In dynamic locations, including areas such as river mouths, capes, ends of spits, and adjacent to wetlands in Barter Island, uncertainty is greater, and positions should be inspected and used with care.
2. How accurate are the geographic locations?
   Data are concurrent with specified transect locations.
3. How accurate are the heights or depths?
   There has not been a formal accuracy assessment of vertical position in this dataset and/or is not applicable.
4. Where are the gaps in the data? What is missing?
   Data set is considered complete for the information presented.
5. How consistent are the relationships among the observations, including topology?
   Data have undergone QA/QC and fall within expected/reasonable ranges.

How can someone get a copy of the data set?

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

   2885 Mission Street

   Santa Cruz, CA
   

   831-427-4747 (voice)

   pcmsc_data@usgs.gov
2. What's the catalog number I need to order this data set? These data are available in GeoJSON format by location. Shoreline vector vertices are derived from points along transects within each ROI, included in the file. Other configuration settings necessary to derive the shoreline positions within each ROI are included in the files.
3. What legal disclaimers am I supposed to read?
   Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
4. How can I download or order the data?
   • Availability in digital form:

     Data format:	Zip file contains Geographic JavaScript Object Notation (GeoJSON) file with spatial point locations and associated attributes for Barter Island in format GeoJSON Size: 4.2
     Network links:	https://doi.org/10.5066/P1NUEFDP

     Data format:	Zip file contains Geographic JavaScript Object Notation (GeoJSON) file with spatial point locations and associated attributes for Cape Cod in format GeoJSON Size: 5.4
     Network links:	https://doi.org/10.5066/P1NUEFDP

     Data format:	Zip file contains Geographic JavaScript Object Notation (GeoJSON) file with spatial point locations and associated attributes for Elwha in format GeoJSON Size: 0.96
     Network links:	https://doi.org/10.5066/P1NUEFDP

     Data format:	Zip file contains Geographic JavaScript Object Notation (GeoJSON) file with spatial point locations and associated attributes for Madeira Beach in format GeoJSON Size: 0.1
     Network links:	https://doi.org/10.5066/P1NUEFDP

     Data format:	Zip file contains Geographic JavaScript Object Notation (GeoJSON) file with spatial point locations and associated attributes for Rincon in format GeoJSON Size: 0.8
     Network links:	https://doi.org/10.5066/P1NUEFDP

   • Cost to order the data: None.

5. What hardware or software do I need in order to use the data set?
   These data can be viewed with GIS software such as Arc, Global Mapper or QGIS, or numerical processing software such as python or Matlab.

Who wrote the metadata?

Dates:

Last modified: 25-Apr-2025

Metadata author:

U.S. Geological Survey, Pacific Coastal and Marine Science Center

Attn: PCMSC Science Data Coordinator

2885 Mission Street

Santa Cruz, CA

831-427-4747 (voice)

pcmsc_data@usgs.gov

Metadata standard:

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