Tidally corrected shoreline positions for five groin fields sites around the United States

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Tidally corrected shoreline positions for five groin fields sites around the United States
Abstract:
This data release provides tidally corrected shoreline positions for five groin field sites of around the United States (Ventura, CA, Newport Beach, CA , Santa Monica, CA, Long Branch, NJ, Sandwich, MA). The CSVs are derived from the software CoastSeg (Fitzpatrick and others, 2024). CoastSeg collects satellite images from Google Earth Engine to create shoreline data along with user supplied inputs based on the CoastSat methodology (Vos and others, 2019). Data have been tidally corrected based on beach foreshore slopes. The data can be viewed in either a text or spreadsheet program.
Supplemental_Information:
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Janda, Catherine N., Warrick, Jonathan A., Buscombe, Daniel, Batiste, Sharon F., and Lundine, Mark A., 20250814, Tidally corrected shoreline positions for five groin fields sites around the United States: data release DOI:10.5066/P14BIJDN, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Janda, Catherine N., Warrick, Jonathan A., Buscombe, Daniel, Batiste, Sharon F., and Lundine, Mark A., 2025, Satellite-derived shorelines for five groin field sites across the United States.: data release DOI:10.5066/P14BIJDN, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Other_Citation_Details:
    Suggested Citation: Janda, C.N., Warrick, J.A., Buscombe, D.D., Batiste, S.F., and Lundine, M.A., 2025, Satellite-derived shorelines for five groin field sites across the United States : U.S. Geological Survey data release, https://doi.org/10.5066/P14BIJDN.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -119.302302
    East_Bounding_Coordinate: -70.390003
    North_Bounding_Coordinate: 41.778327
    South_Bounding_Coordinate: 33.603224
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Jan-1984
    Ending_Date: 31-Dec-2022
    Currentness_Reference:
    Years of available satellite imagery used to determine shoreline positions. Date range of January 1, 1984, to December 31, 2022, was used within CoastSeg (Fitzpatrick and others, 2024) to download satellite images from Google Earth Engine.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: comma-delimited text
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Point (978745)
    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.00000000000001. Latitude and longitude values are specified in Decimal Degrees. The horizontal datum used is WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.25722.
      Vertical_Coordinate_System_Definition:
      Depth_System_Definition:
      Depth_Datum_Name: NAVD88
      Depth_Resolution: 1.0
      Depth_Distance_Units: meters
      Depth_Encoding_Method: Implicit coordinate
  7. How does the data set describe geographic features?
    [field site]_tidally_corrected_transect_time_series.csv
    CSV file consisting of shoreline positions from 1984-2022 for five groin field sites across the United States (Ventura, CA, Newport Beach, CA, Santa Monica, CA, Long Branch, NJ, Sandwich, MA) that are tidally corrected based on satellite imagery from CoastSeg. (Source: Producer Defined)
    dates
    date and time of extracted shoreline (Source: Producer Defined)
    Range of values
    Minimum:1984-03-23 17:50:13+00:00
    Maximum:2022-12-30 15:21:20+00:00
    Units:time in yyyy-mm-dd HH:MM:SS+MS format
    id
    Unique identifier of transects along each region of intrest (Source: Producer Defined) Transect IDs are defined based on the region of interest and geographical area within CoastSeg. CoastSeg assigns a three letter ID to the region of interest and then the number represents the transect number within that region.
    x_start
    Starting latitude position of transects (Source: Producer Defined)
    Range of values
    Minimum:-119.3013366
    Maximum:-70.41873515
    Units:decimal degrees
    Resolution:0.00000001
    y_start
    Starting longitude position of transects (Source: Producer Defined)
    Range of values
    Minimum:33.6048768400829
    Maximum:41.7745954964064
    Units:decimal degrees
    Resolution:0.00000001
    x_end
    Ending latitude position of transects (Source: Producer Defined)
    Range of values
    Minimum:-119.3008974
    Maximum:-70.41756874
    Units:decimal degrees
    Resolution:0.00000001
    y_end
    Ending longitude position of transects (Source: Producer Defined)
    Range of values
    Minimum:33.6021974100000
    Maximum:41.7762958039487
    Units:decimal degrees
    Resolution:0.0000000000001
    tide
    observed tide at each recorded shoreline in meters with respect to mean sea level (MSL) (Source: Producer Defined)
    Range of values
    Minimum:-1.57664120800000
    Maximum:1.98502355268893
    Units:meters
    Resolution:0.00000000000001
    cross_distance
    distance along transect of extracted shoreline from transect origin point (Source: Producer Defined)
    Range of values
    Minimum:-13.8938642
    Maximum:378.5238597
    Units:meters
    Resolution:0.0000001
    shore_x
    Latitude position of derived shoreline point (Source: Producer Defined)
    Range of values
    Minimum:-119.30127380
    Maximum:-70.41783678
    Units:decimal degrees
    Resolution:0.00000001
    shore_y
    Longitude position of derived shoreline point (Source: Producer Defined)
    Range of values
    Minimum:33.60341938
    Maximum:41.77588717
    Units:decimal degrees
    Resolution:0.00000001
    slope
    slope used for tide correction (Source: Producer Defined)
    Range of values
    Minimum:0.067
    Maximum:0.140
    Units:meters/meters
    Resolution:0.001
    ref_elevation
    Reference elevation (Source: Producer Defined) Reference elevation is used within CoastSeg to aid in the tide correction process. Reference elevation for all sites in this study was mean sea level (MSL), and all sites had a reference elevation of zero.
    Entity_and_Attribute_Overview:
    CSV files for Ventura, CA, Newport Beach, CA, Santa Monica, CA, Long Branch, NJ, and Sandwich, MA from 1984-2022. The first line of the CSV is a header line containing the names of each column. CSVs contain the date, transect ID, transect staring latitude point, transect starting longitude point, transect ending latitude point, transect ending longitude point, tide, cross distance, shoreline point latitude, shoreline point longitude, slope, and reference elevation of each point derived from the satellite imagery. Files are named by region and ROI number if the region has more than one ROI. ROIs are numbered from west to east or south to north following the numbering given by CoastSeg.
    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)
    • Catherine N. Janda
    • Jonathan A. Warrick
    • Daniel Buscombe
    • Sharon F. Batiste
    • Mark A. Lundine
  2. Who also contributed to the data set?
  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 Native_Data_Set_Environment: The datasets were created on a Windows 11 operating system, using CoastSeg v1.2.16. Results are outputted as R files that are read into Matlab R2019b and Python 3.8.

Why was the data set created?

These shoreline positions were used to observe the change in shoreline position over the entire observed record for groin field sites across the country. The data are intended to be used to find erosion and accretion patterns, as well as observing if groin fields behave similarly at varying locations. This data set can be used both in geographic information systems (GIS) as well as other software such as MATLAB or Python.

How was the data set created?

  1. From what previous works were the data drawn?
    Landsat 5 imagery (source 1 of 7)
    U.S. Geological Survey, 2020, Landsat 4-5 Thematic Mapper Level-1, Collection 2: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study
    Landsat 7 imagery (source 2 of 7)
    U.S. Geological Survey, 2022, Landsat 7 Enhanced Thematic Mapper Plus Level-1, Collection 2: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study
    Landsat 8-9 imagery (source 3 of 7)
    U.S. Geological Survey, 2022, Landsat 8-9 Operational Land Imager / Thermal Infrared Sensor Level-1, Collection 2: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study
    Sentinel 2 imagery (source 4 of 7)
    Release, Copernicus Data EU, 2017, Sentinel imagery (from Sentinel 2): Copernicus Data Release, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The archive of satellite images from Google Earth Engine was used to derive the shoreline positions for the study
    FES 2014 (source 5 of 7)
    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:

    Type_of_Source_Media: online database
    Source_Contribution:
    Tidal corrections in CoastSeg were made with tide height predictions from the FES 2014 model
    Slopes_East (source 6 of 7)
    Farris, Amy, and Weber, Kathryn M, 2024, Beach foreshore slope for the East Coast of the United States: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The foreshore slopes were used to help tide correct the time-series data in CoastSeg
    Slopes_West (source 7 of 7)
    Farris, Amy, and Weber, Kathryn M, 2024, Beach foreshore slope for the West Coast of the United States: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution:
    The foreshore slopes were used to help tide correct the time-series data in CoastSeg
  2. How were the data generated, processed, and modified?
    Date: 20-Sep-2024 (process 1 of 3)
    Set up CoastSeg toolbox (Fitzpatrick and others, 2024) to derive the imagery and extract shorelines to be used in the region of interest (ROI). Version 1.2.16 was used to download the imagery from January 1, 1984, to December 31, 2022.
    Date: 01-Oct-2024 (process 2 of 3)
    Ran CoastSeg toolbox on imagery downloaded from Google Earth Engine for the time period and geographical region of interest. CoastSeg version v1.2.16. was used to extract the shoreline positions. Only images free of clouds or pixel errors were included. Data sources used in this process:
    • Landsat 5 imagery
    • Landsat 7
    • Landsat 8-9 imagery
    • Sentinel 2 imagery
    Date: 01-Nov-2024 (process 3 of 3)
    Data were tidally corrected in CoastSeg based off the slope data. Data sources used in this process:
    • Slopes_East
    • Slopes_West
    • FES 2014
  3. What similar or related data should the user be aware of?
    Fitzpatrick, Sharon, Buscombe, Daniel, Warrick, Jonathan A., Lundine, Mark A., and Vos, Killian, 2024, CoastSeg: an accessible and extendable hub for satellite-derived shoreline (SDS) detection and mapping.

    Online Links:

    Other_Citation_Details:
    Fitzpatrick, S., Buscombe, D., Warrick, J.A., Lundine, M.A., Vos, K., 2024, CoastSeg: an accessible and extendable hub for satellite-derived shoreline (SDS) detection and mapping: Journal of Open Source Software, https://doi.org/10.21105/joss.06683.
    Vos, Killian, Splinter, Kristen D., Harley, Mitchell D., Simmons, Joshua A., and Turner, Ian L., 2019, CoastSat: A Google Earth Engine-enabled Python toolkit to extract shorelines from publicly available satellite imagery.

    Online Links:

    Other_Citation_Details:
    Vos K., Splinter, K.D., Harley M.D., Simmons, J.A., Turner, I.L., 2019, CoastSat: A Google Earth Engine-enabled Python toolkit to extract shorelines from publicly available satellite imagery: Environmental Modelling & Software, https://doi.org/10.1016/j.envsoft.2019.104528

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

  1. How well have the observations been checked?
    Attribute values are estimated such as shoreline position based on satellite imagery. Vos and others (2019) assessed this method which compared to ground-based surveys at Duck, North Carolina. The authors are using a cross-shore horizontal error of 10 meters root mean squared error (RMSE) in most locations. In more dynamic areas such as river mouths, capes, and the ends of spits, the uncertainty is greater, and all positions should be inspected further.
  2. How accurate are the geographic locations?
    Data are respective with its 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 are considered complete for the information presented.
  5. How consistent are the relationships among the observations, including topology?
    Data have undergone quality assurance and quality control (QA/QC) and fall within expected ranges.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originator(s) of the dataset and in products derived from these data.
  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

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in CSV format contained in a single zip file (GroinField_csv.zip) accompanied by CSDGM FGDC-compliant metadata.
  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?
  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 ArcGIS or QGIS, numerical processing software such as Matlab or python, or any text editing software.

Who wrote the metadata?

Dates:
Last modified: 14-Aug-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)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/ScienceBase/DR_P14BIJDN/GroinField_csvs_metadata.faq.html>
Generated by mp version 2.9.51 on Fri Aug 15 11:01:27 2025