<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Catherine N. Janda</origin>
        <origin>Jonathan A. Warrick</origin>
        <origin>Daniel Buscombe</origin>
        <origin>Sharon F. Batiste</origin>
        <origin>Mark A. Lundine</origin>
        <pubdate>20250814</pubdate>
        <title>Tidally corrected shoreline positions for five groin fields sites around the United States</title>
        <geoform>comma-delimited text</geoform>
        <serinfo>
          <sername>data release</sername>
          <issue>DOI:10.5066/P14BIJDN</issue>
        </serinfo>
        <pubinfo>
          <pubplace>Pacific Coastal and Marine Science Center, Santa Cruz, California</pubplace>
          <publish>U.S. Geological Survey</publish>
        </pubinfo>
        <onlink>https://doi.org/10.5066/P14BIJDN</onlink>
        <onlink>https://www.sciencebase.gov/catalog/item/68751d74d4be025f81987c27</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Catherine N. Janda</origin>
            <origin>Jonathan A. Warrick</origin>
            <origin>Daniel Buscombe</origin>
            <origin>Sharon F. Batiste</origin>
            <origin>Mark A. Lundine</origin>
            <pubdate>2025</pubdate>
            <title>Satellite-derived shorelines for five groin field sites across the United States.</title>
            <serinfo>
              <sername>data release</sername>
              <issue>DOI:10.5066/P14BIJDN</issue>
            </serinfo>
            <pubinfo>
              <pubplace>Pacific Coastal and Marine Science Center, Santa Cruz, CA</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <othercit>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.</othercit>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <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.</abstract>
      <purpose>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.</purpose>
      <supplinf>Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>19840101</begdate>
          <enddate>20221231</enddate>
        </rngdates>
      </timeinfo>
      <current>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.</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-119.302302</westbc>
        <eastbc>-70.390003</eastbc>
        <northbc>41.778327</northbc>
        <southbc>33.603224</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>geoscientificInformation</themekey>
        <themekey>environment</themekey>
        <themekey>oceans</themekey>
      </theme>
      <theme>
        <themekt>Data Categories for Marine Planning</themekt>
        <themekey>Structures</themekey>
        <themekey>Distributions</themekey>
        <themekey>Physical Habitats and Geomorphology</themekey>
      </theme>
      <theme>
        <themekt>USGS Thesaurus</themekt>
        <themekey>Ocean Sciences</themekey>
        <themekey>Remote Sensing</themekey>
        <themekey>Visible Light Imaging</themekey>
        <themekey>Sea-level Change</themekey>
      </theme>
      <theme>
        <themekt>Marine Realms Information Bank (MRIB) keywords</themekt>
        <themekey>Shoreline Accretion</themekey>
        <themekey>Shoreline Erosion</themekey>
      </theme>
      <theme>
        <themekt>None</themekt>
        <themekey>U.S. Geological Survey</themekey>
        <themekey>USGS</themekey>
        <themekey>Coastal and Marine Hazards and Resources Program</themekey>
        <themekey>CMHRP</themekey>
        <themekey>Pacific Coastal and Marine Science Center</themekey>
        <themekey>PCMSC</themekey>
      </theme>
      <theme>
        <themekt>USGS Metadata Identifier</themekt>
        <themekey>USGS:68751d74d4be025f81987c27</themekey>
      </theme>
      <place>
        <placekt>Geographic Names Information System (GNIS)</placekt>
        <placekey>State of California</placekey>
        <placekey>State of New Jersey</placekey>
        <placekey>Commonwealth of Massachusetts</placekey>
        <placekey>Sandwich</placekey>
        <placekey>Sandwich Harbor</placekey>
        <placekey>Long Branch</placekey>
        <placekey>Ventura</placekey>
        <placekey>Ventura City Beach</placekey>
        <placekey>Santa Monica</placekey>
        <placekey>Santa Monica Bay</placekey>
        <placekey>Newport Beach</placekey>
      </place>
    </keywords>
    <accconst>No access constraints</accconst>
    <useconst>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.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Geological Survey, Pacific Coastal and Marine Science Center</cntorg>
          <cntper>PCMSC Science Data Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2885 Mission Street</address>
          <city>Santa Cruz</city>
          <state>CA</state>
          <postal>95060</postal>
        </cntaddr>
        <cntvoice>831-427-4747</cntvoice>
        <cntemail>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.</cntemail>
      </cntinfo>
    </ptcontac>
    <crossref>
      <citeinfo>
        <origin>Sharon Fitzpatrick</origin>
        <origin>Daniel Buscombe</origin>
        <origin>Jonathan A. Warrick</origin>
        <origin>Mark A. Lundine</origin>
        <origin>Killian Vos</origin>
        <pubdate>2024</pubdate>
        <title>CoastSeg: an accessible and extendable hub for satellite-derived shoreline (SDS) detection and mapping</title>
        <othercit>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.</othercit>
        <onlink>https://doi.org/10.21105/joss.06683</onlink>
      </citeinfo>
    </crossref>
    <crossref>
      <citeinfo>
        <origin>Killian Vos</origin>
        <origin>Kristen D. Splinter</origin>
        <origin>Mitchell D. Harley</origin>
        <origin>Joshua A. Simmons</origin>
        <origin>Ian L. Turner</origin>
        <pubdate>2019</pubdate>
        <title>CoastSat: A Google Earth Engine-enabled Python toolkit to extract shorelines from publicly available satellite imagery</title>
        <othercit>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 &amp; Software, https://doi.org/10.1016/j.envsoft.2019.104528</othercit>
        <onlink>https://doi.org/10.1016/j.envsoft.2019.104528</onlink>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>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.</attraccr>
    </attracc>
    <logic>Data have undergone quality assurance and quality control (QA/QC) and fall within expected ranges.</logic>
    <complete>Data are considered complete for the information presented.</complete>
    <posacc>
      <horizpa>
        <horizpar>Data are respective with its specified transect locations.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>There has not been a formal accuracy assessment of vertical position in this dataset and/or is not applicable.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Geological Survey</origin>
            <pubdate>2020</pubdate>
            <title>Landsat 4-5 Thematic Mapper Level-1, Collection 2</title>
            <geoform>Remote-Sensing Image</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://doi.org/10.5066/P918ROHC</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19840101</begdate>
              <enddate>20120531</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Date range of available satellite imagery used to determine shoreline positions</srccurr>
        </srctime>
        <srccitea>Landsat 5 imagery</srccitea>
        <srccontr>The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Geological Survey</origin>
            <pubdate>2022</pubdate>
            <title>Landsat 7 Enhanced Thematic Mapper Plus Level-1, Collection 2</title>
            <geoform>Remote-Sensing Image</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://doi.org/10.5066/P9TU80IG</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19990401</begdate>
              <enddate>20221231</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Date range of available satellite imagery used to determine shoreline positions</srccurr>
        </srctime>
        <srccitea>Landsat 7 imagery</srccitea>
        <srccontr>The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Geological Survey</origin>
            <pubdate>2022</pubdate>
            <title>Landsat 8-9 Operational Land Imager / Thermal Infrared Sensor Level-1, Collection 2</title>
            <geoform>Remote-Sensing Image</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://doi.org/10.5066/P975CC9B</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20130201</begdate>
              <enddate>20221231</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Date range of available satellite imagery used to determine shoreline positions</srccurr>
        </srctime>
        <srccitea>Landsat 8-9 imagery</srccitea>
        <srccontr>The archive of satellite images from Earth Explorer was used to derive the shoreline positions for the study</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Copernicus Data Release EU</origin>
            <pubdate>2017</pubdate>
            <title>Sentinel imagery (from Sentinel 2)</title>
            <geoform>image</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>Copernicus Data Release</publish>
            </pubinfo>
            <onlink>https://dataspace.copernicus.eu/explore-data/data-collections/sentinel-data/sentinel-2</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20170301</begdate>
              <enddate>20221231</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Date range of available satellite imagery used to determine shoreline positions</srccurr>
        </srctime>
        <srccitea>Sentinel 2 imagery</srccitea>
        <srccontr>The archive of satellite images from Google Earth Engine was used to derive the shoreline positions for the study</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Carrere, L.</origin>
            <origin>Lyard, F.</origin>
            <origin>Cancet, M.</origin>
            <origin>Guillot, A.</origin>
            <origin>Picot, N.</origin>
            <pubdate>20160501</pubdate>
            <title>FES (Finite Element Solution) 2014, a new tidal model—Validation results and perspectives for improvements</title>
            <geoform>NetCDF</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>AVISO</publish>
            </pubinfo>
            <onlink>https://www.aviso.altimetry.fr/en/data/products/auxiliary-products/global-tide-fes/description-fes2014.html</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>20160501</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>publication date</srccurr>
        </srctime>
        <srccitea>FES 2014</srccitea>
        <srccontr>Tidal corrections in CoastSeg were made with tide height predictions from the FES 2014 model</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Amy Farris</origin>
            <origin>Kathryn M Weber</origin>
            <pubdate>2024</pubdate>
            <title>Beach foreshore slope for the East Coast of the United States</title>
            <geoform>CSV</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://www.sciencebase.gov/catalog/item/663d18a6d34e77890839e46f</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19970915</begdate>
              <enddate>20180807</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Ground condition at time data were collected</srccurr>
        </srctime>
        <srccitea>Slopes_East</srccitea>
        <srccontr>The foreshore slopes were used to help tide correct the time-series data in CoastSeg</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Amy Farris</origin>
            <origin>Kathryn M Weber</origin>
            <pubdate>2024</pubdate>
            <title>Beach foreshore slope for the West Coast of the United States</title>
            <geoform>CSV</geoform>
            <pubinfo>
              <pubplace>online</pubplace>
              <publish>U.S. Geological Survey</publish>
            </pubinfo>
            <onlink>https://www.sciencebase.gov/catalog/item/65a0296bd34e5af967a3841d</onlink>
          </citeinfo>
        </srccite>
        <typesrc>online database</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20220901</begdate>
              <enddate>20110730</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Ground condition at time data were collected</srccurr>
        </srctime>
        <srccitea>Slopes_West</srccitea>
        <srccontr>The foreshore slopes were used to help tide correct the time-series data in CoastSeg</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>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.</procdesc>
        <procdate>20240920</procdate>
      </procstep>
      <procstep>
        <procdesc>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.</procdesc>
        <srcused>Landsat 5 imagery</srcused>
        <srcused>Landsat 7</srcused>
        <srcused>Landsat 8-9 imagery</srcused>
        <srcused>Sentinel 2 imagery</srcused>
        <procdate>20241001</procdate>
      </procstep>
      <procstep>
        <procdesc>Data were tidally corrected in CoastSeg based off the slope data.</procdesc>
        <srcused>Slopes_East</srcused>
        <srcused>Slopes_West</srcused>
        <srcused>FES 2014</srcused>
        <procdate>20241101</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Point</sdtstype>
        <ptvctcnt>978745</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <geograph>
        <latres>0.00000001</latres>
        <longres>0.00000000000001</longres>
        <geogunit>Decimal Degrees</geogunit>
      </geograph>
      <geodetic>
        <horizdn>WGS_1984</horizdn>
        <ellips>WGS_1984</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.25722</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <depthsys>
        <depthdn>NAVD88</depthdn>
        <depthres>1.0</depthres>
        <depthdu>meters</depthdu>
        <depthem>Implicit coordinate</depthem>
      </depthsys>
    </vertdef>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>[field site]_tidally_corrected_transect_time_series.csv</enttypl>
        <enttypd>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.</enttypd>
        <enttypds>Producer Defined</enttypds>
      </enttyp>
      <attr>
        <attrlabl>dates</attrlabl>
        <attrdef>date and time of extracted shoreline</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>1984-03-23 17:50:13+00:00</rdommin>
            <rdommax>2022-12-30 15:21:20+00:00</rdommax>
            <attrunit>time in yyyy-mm-dd HH:MM:SS+MS format</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>id</attrlabl>
        <attrdef>Unique identifier of transects along each region of intrest</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <udom>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.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>x_start</attrlabl>
        <attrdef>Starting latitude position of transects</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-119.3013366</rdommin>
            <rdommax>-70.41873515</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.00000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>y_start</attrlabl>
        <attrdef>Starting longitude position of transects</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>33.6048768400829</rdommin>
            <rdommax>41.7745954964064</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.00000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>x_end</attrlabl>
        <attrdef>Ending latitude position of transects</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-119.3008974</rdommin>
            <rdommax>-70.41756874</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.00000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>y_end</attrlabl>
        <attrdef>Ending longitude position of transects</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>33.6021974100000</rdommin>
            <rdommax>41.7762958039487</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.0000000000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>tide</attrlabl>
        <attrdef>observed tide at each recorded shoreline in meters with respect to mean sea level (MSL)</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-1.57664120800000</rdommin>
            <rdommax>1.98502355268893</rdommax>
            <attrunit>meters</attrunit>
            <attrmres>0.00000000000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>cross_distance</attrlabl>
        <attrdef>distance along transect of extracted shoreline from transect origin point</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-13.8938642</rdommin>
            <rdommax>378.5238597</rdommax>
            <attrunit>meters</attrunit>
            <attrmres>0.0000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>shore_x</attrlabl>
        <attrdef>Latitude position of derived shoreline point</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-119.30127380</rdommin>
            <rdommax>-70.41783678</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.00000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>shore_y</attrlabl>
        <attrdef>Longitude position of derived shoreline point</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>33.60341938</rdommin>
            <rdommax>41.77588717</rdommax>
            <attrunit>decimal degrees</attrunit>
            <attrmres>0.00000001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>slope</attrlabl>
        <attrdef>slope used for tide correction</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>0.067</rdommin>
            <rdommax>0.140</rdommax>
            <attrunit>meters/meters</attrunit>
            <attrmres>0.001</attrmres>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ref_elevation</attrlabl>
        <attrdef>Reference elevation</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <udom>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.</udom>
        </attrdomv>
      </attr>
    </detailed>
    <overview>
      <eaover>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.</eaover>
      <eadetcit>U.S. Geological Survey</eadetcit>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Geological Survey - ScienceBase</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>Denver Federal Center, Building 810, Mail Stop 302</address>
          <city>Denver</city>
          <state>CO</state>
          <postal>80225</postal>
        </cntaddr>
        <cntvoice>1-888-275-8747</cntvoice>
        <cntemail>sciencebase@usgs.gov</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>These data are available in CSV format contained in a single zip file (GroinField_csv.zip) accompanied by CSDGM FGDC-compliant metadata.</resdesc>
    <distliab>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.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>comma-deliminated text</formname>
          <formcont>These data are available in CSV format (for example,  Ventura_transect_time_series_tidally_corrected.csv) contained in a single zip file (GroinField_csv.zip). Shorelines are identified by points along the transects where the start and end point of each transect is included in the CSV.</formcont>
          <filedec>WinZip or archive utility</filedec>
          <transize>33</transize>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>https://www.sciencebase.gov/catalog/file/get/68751d74d4be025f81987c27</networkr>
                <networkr>https://www.sciencebase.gov/catalog/item/68751d74d4be025f81987c27</networkr>
                <networkr>https://doi.org/10.5066/P14BIJDN</networkr>
              </networka>
            </computer>
            <accinstr>Data can be downloaded using the Network_Resource_Name links. The first link is a direct link to download the zipped file of data and metadata. The second link points to a landing page with metadata and data. The third link points to the landing page for the entire data release.</accinstr>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>None.</fees>
    </stdorder>
    <techpreq>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.</techpreq>
  </distinfo>
  <metainfo>
    <metd>20250814</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Geological Survey, Pacific Coastal and Marine Science Center</cntorg>
          <cntper>PCMSC Science Data Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2885 Mission Street</address>
          <city>Santa Cruz</city>
          <state>CA</state>
          <postal>95060</postal>
        </cntaddr>
        <cntvoice>831-427-4747</cntvoice>
        <cntemail>pcmsc_data@usgs.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>
