Region of Interests (ROI), Transects, and Reference Shorelines for Three Sites of Western Long Island, New York

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

Frequently anticipated questions:

What does this data set describe?
Who produced the data set?
Why was the data set created?
How was the data set created?
How reliable are the data; what problems remain in the data set?
How can someone get a copy of the data set?
Who wrote the metadata?

What does this data set describe?

Title:

Region of Interests (ROI), Transects, and Reference Shorelines for Three Sites of Western Long Island, New York

Abstract:

This data release provides tidally corrected shoreline positions for three sites of western Long Island, NY (Rockaway Peninsula, Long Beach, and Jones Beach Island). GeoJSON files are derived from CoastSeg version 1.1.35 (Fitzpatrick and others, 2024) with settings derived from config files. These files contain the region of interests (ROIs), transects, and reference shorelines for each section. 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 (Farris and Webber, 2024). Data can be viewed in a GIS software such as QGIS or ArcGIS.

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.

How might this data set be cited?
Janda, Catherine N., Warrick, Jonathan A., Buscombe, Daniel, and Batiste, Sharon, 20250115, Region of Interests (ROI), Transects, and Reference Shorelines for Three Sites of Western Long Island, New York: data release DOI:10.5066/P14VFVGZ, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.
Online Links:
- https://doi.org/10.5066/P14VFVGZ
- https://www.sciencebase.gov/catalog/item/67609e46d34e03058f2209b8
This is part of the following larger work.
Janda, Catherine N., Warrick, Jonathan A., Buscombe, Daniel, and Batiste, Sharon, 2025, Shoreline Change of Western Long Island, New York from Satellite Derived Shorelines: data release DOI:10.5066/P14VFVGZ, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.
Online Links:
- https://doi.org/10.5066/P14VFVGZ
Other_Citation_Details:
Suggested Citation: Janda, C.N., Warrick, J.A., Buscombe, D., and Batiste, S. 2025, Shoreline Change of Western Long Island, New York from Satellite Derived Shorelines: U.S. Geological Survey data release, https://doi.org/10.5066/P14VFVGZ.
What geographic area does the data set cover?
West_Bounding_Coordinate: -73.9458
East_Bounding_Coordinate: -73.3087
North_Bounding_Coordinate: 40.6472
South_Bounding_Coordinate: 40.5284
What does it look like?
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.
What is the general form of this data set?
Geospatial_Data_Presentation_Form: GeoJSON
How does the data set represent geographic features?
1. How are geographic features stored in the data set?
  This is a Vector data set. It contains the following vector data types (SDTS terminology):
  - G-Polygon (13)
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_84.
  The ellipsoid used is WGS_84.
  The semi-major axis of the ellipsoid used is 6378137.0.
  The flattening of the ellipsoid used is 1/298.25722.

How does the data set describe geographic features?

GeoJSON files from CoastSeg version 1.1.35 containing the region of interest(ROI), reference shoreline, and transects for each respective ROI.

GeoJSON files containing the region of interest(ROI), shoreline, and transects for each respective ROI. The settings used for each ROI session are tied to the ROI from the config file. (Source: Producer Defined)

id

identification given to each ROI, transect, and shoreline by CoastSeg (Source: Producer Defined) 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(ROI), shoreline, and transect and the number that follows represents the region of interest(ROI) number, shoreline number, or transect number within that region.

type

feature types within the GeoJSON file (Source: Producer Defined)

Value	Definition
roi	Polygon feature specifying the area within the imagery analyzed by CoastSeg
shoreline	Linestring feature specifying the reference shoreline used by CoastSeg
transect	Linestring feature specifying the transect used by CoastSeg

settings

settings from the .config file created within CoastSeg which have been tied to the region of interest(ROI) in each file (Source: Producer Defined) Settings from CoastSeg sessions .config file used to create extracted shorelines. Settings are tied to the region of interest(ROI) which include “dates”, “sat_list”, “cloud_thresh”, ”dist_clouds”, “output_epsg”, “check_detection”, “adjust_detection”, “save_figure”, “min_beach_area”, “min_length_sl”, “cloud_mask_issue”, “sand_color”, “pan_off”, “max_dist_ref”, “along_dist”, “min_points”, “max_std”, “max_range”, “min_chainage”, “multiple_inter”, “prc_multiple”, “apply_cloud_mask”, “image_size_filter”, “percent_no_data”. This column for shorelines and transects is equal to null.

geometry

description of feature geometry (Source: Producer Defined) The geometry is defined as either a polygon for the region of interest(ROI) or a line string for the shorelines and transects. This is then followed by the coordinated of the boundaries of these defined geometry features (example for a transect: "geometry": { "type": "LineString", "coordinates": [ [ -73.415947897400002, 40.614699282698695 ], [ -73.415947897400002, 40.614699282698695 ], [ -73.413274979993446, 40.607787729193952 ] ] } }

Entity_and_Attribute_Overview:

GeoJSON files for Rockaway Peninsula, Long Beach, and Jones Beach Island, New York from 1984-2022.

Entity_and_Attribute_Detail_Citation:

GeoJSON files contain the region of interest(ROI), transects, and reference shorelines derived from satellite imagery. The ROIs are polygons while the transects and shorelines are line-strings. Settings are available within the attributes of each GeoJSON. Files are named by region and ROI number with three different region labels: RW for Rockaway Peninsula, LB for Long Beach, and JB for Jones Beach Island. ROIs are numbered from west to east following the numbering given by CoastSeg.

Who produced the data set?

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 Batiste
Who also contributed to the data set?
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?

These GeoJSON files were used to observe the change in shoreline position over the entire observed record for Rockaway Peninsula, Long Beach, and Jones Beach Island in New York. Each ROI from CoastSeg has its own GeoJSON. The data are intended to be used to find sediment waves and erosion and accretion patterns, as well as evidence of storm damage and beach nourishments. 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?

From what previous works were the data drawn?
Landsat 5-8 imagery (source 1 of 5)
U.S. Geological Survey, 2022, Landsat imagery (from Landsat 5-8): U.S. Geological Survey, online.
Online Links:
- https://earthengine.google.com/
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
Landsat 9 imagery (source 2 of 5)
U.S. Geological Survey, 2022, Earth Explorer: U.S. Geological Survey, online.
Online Links:
- https://doi.org/10.5066/P975CC9B
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 3 of 5)
Release, Copernicus Data EU, 2017, Sentinel imagery (from Sentinel 2): Copernicus Data Release, 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 satellite images from Google Earth Engine was used to derive the shoreline positions for the study
FES 2014 (source 4 of 5)
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 database
Source_Contribution:
Tidal corrections in CoastSeg were made with tide height predictions from the FES 2014 model
Slopes (source 5 of 5)
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:
- https://www.sciencebase.gov/catalog/item/663d18a6d34e77890839e46f
Type_of_Source_Media: online database
Source_Contribution:
The foreshore slopes were used to tide correct the time-series data in CoastSeg
How were the data generated, processed, and modified?
Date: 01-Feb-2024 (process 1 of 4)
Set up CoastSeg toolbox (Fitzpatrick and others, 2024) to derive the imagery and extract shorelines to be used in the region of interest. Version 1.1.28 was used to download the imagery from January 1, 1984 to December 31, 2022.
Date: 14-Feb-2024 (process 2 of 4)
Ran CoastSeg toolbox on imagery downloaded from Google Earth Engine for the time period and geographical region of interest. CoastSeg version v1.1.35 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-8 imagery
- Landsat 9 imagery
- Sentinel 2 imagery
Date: 14-Feb-2024 (process 3 of 4)
Data was tidally corrected in CoastSeg based off the slope data. Data sources used in this process:
- Slopes
- FES 2014
Date: 01-Nov-2024 (process 4 of 4)
GeoJSON files output by CoastSeg were modified to include the settings for each region of interest (ROI) which were contained within the config files.
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:
- https://doi.org/10.21105/joss.06683
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:
- https://doi.org/10.1016/j.envsoft.2019.104528
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?

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.
How accurate are the geographic locations?
Data are respective with their specified transect locations.
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.
Where are the gaps in the data? What is missing?
Data are considered complete for the information presented.
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.

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
What's the catalog number I need to order this data set? These data are available in GeoJSON Linestrings format contained in a single zip file (LongIsland_geojson.zip) accompanied by CSDGM FGDC-compliant metadata.
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.

How can I download or order the data?

Availability in digital form:

Data format:	These data are available in GeoJSON format corresponding to the ROI name given (for example, JB_ROI1_combined_config_gdf.geojson). Each GeoJSON contains a polygon for the region of interest (ROI) box and line strings for the transects and shorelines. in format GeoJSON (version CoastSeg v1.1.28) GeoJSON Polygon and GeoJSON Linestrings Size: 0.26249
Network links:	https://www.sciencebase.gov/catalog/file/get/67609e46d34e03058f2209b8 https://www.sciencebase.gov/catalog/item/67609e46d34e03058f2209b8 https://doi.org/10.5066/P14VFVGZ

Cost to order the data: None.

What hardware or software do I need in order to use the data set?
These data can be viewed with GIS software such as QGIS or ArcGIS.

Who wrote the metadata?

Dates:: Last modified: 15-Jan-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_P14VFVGZ/LongIsland_geojson_metadata.faq.html>