Coastseg

**Full Changelog**: https://github.com/SatelliteShorelines/CoastSeg/compare/v1.2.3...v1.2.4

**Full Changelog**: https://github.com/SatelliteShorelines/CoastSeg/compare/v1.2.2...v1.2.3

Fixes

- Fixes cloud threshold filtering. Images downloaded will actually not download if the amount of bad pixels or cloud data exceeds the threshold
- No longer saves the index to any of the csv files
- Requires `coastsat-package > 0.1.65` allows for the downloaded images to be filtered by clouds and no data percentage

New Features

1. Cloud Filter Update
1. The cloud threshold filter now controls the amount of clouds that will be downloaded. Downloads will automatically calculate the percentage of cloud in the ROI and if it exceeds the limit the image is not saved.
2. This fixes a bug with CoastSeg 1.2.2 where the cloud threshold was filtering out clouds based on the amount of clouds in the entire scene not the ROI.
2. Bad Filter Update
1. The bad threshold filter now controls the percentage of bad pixels allowed in the imagery. Downloads will automatically calculate the percentage of bad pixels (cloud and no data) in the ROI and if it exceeds the limit the image is not saved.

**Full Changelog**: https://github.com/SatelliteShorelines/CoastSeg/compare/v1.2.1...v1.2.2
Fixes
- Removes deprecated `import pyTMD.constants`
- Updates `scripts/aviso_fes_tides.py` to be up to date with `2.1.1`
- Requires `coastsat-package > 0.1.63` to allow datetime objects to work with extract shorelines

New Features

1. **Resumable Downloads**
You can now resume interrupted downloads. Simply load the session, select the region of interest (ROI), and click "Download Imagery." CoastSeg will download any files that weren't previously downloaded.
2. **Extract Shorelines for Specific Satellites and Dates**
You can extract shorelines for specific satellites and dates by adjusting the settings.
3. **Month Filter**
A new month filter allows you to download imagery only for specific months.

**Resumable Downloads**

- Downloads can now be resumed if interrupted
- Simply reload the session, re-select the region of interest (ROI), and click "Download Imagery"
- CoastSeg will intelligently resume downloading any files that weren't fully transferred previously


This screenshot shows that 6 images from LandSat 8 and 13 images from Sentinel 2 will be downloaded into the existing session for ROI `sun_19`.
**Extract Shorelines for Specific Satellites and Dates**

- New settings allow specifying which satellites and date ranges to use
- Extract shorelines from only the most relevant imagery for your analysis
- Gain more control over the input data for shoreline extraction

**New Month Filter**

- Filter downloads to include only specific months of the year
- Avoid downloading extraneous data when only analyzing certain seasons/months
- Keep download size manageable by retrieving only the needed imagery


Closed Issues
240 : Added controls to only download specific months.
234 : Users can now use the satellite list and date range to control which images the shorelines are extracted from thus there is no longer a need to separate the download settings and extract shoreline settings
226 : Users can now continue downloads that were interrupted.

**Full Changelog**: https://github.com/SatelliteShorelines/CoastSeg/compare/v1.2.0...v1.2.1

New Features

1. **Resumable Downloads**
You can now resume interrupted downloads. Simply load the session, select the region of interest (ROI), and click "Download Imagery." CoastSeg will download any files that weren't previously downloaded.
2. **Extract Shorelines for Specific Satellites and Dates**
You can extract shorelines for specific satellites and dates by adjusting the settings.
3. **Month Filter**
A new month filter allows you to download imagery only for specific months.

**Resumable Downloads**

- Downloads can now be resumed if interrupted
- Simply reload the session, re-select the region of interest (ROI), and click "Download Imagery"
- CoastSeg will intelligently resume downloading any files that weren't fully transferred previously


This screenshot shows that 6 images from LandSat 8 and 13 images from Sentinel 2 will be downloaded into the existing session for ROI `sun_19`.
**Extract Shorelines for Specific Satellites and Dates**

- New settings allow specifying which satellites and date ranges to use
- Extract shorelines from only the most relevant imagery for your analysis
- Gain more control over the input data for shoreline extraction

**New Month Filter**

- Filter downloads to include only specific months of the year
- Avoid downloading extraneous data when only analyzing certain seasons/months
- Keep download size manageable by retrieving only the needed imagery


Closed Issues
240 : Added controls to only download specific months.
234 : Users can now use the satellite list and date range to control which images the shorelines are extracted from thus there is no longer a need to separate the download settings and extract shoreline settings
226 : Users can now continue downloads that were interrupted.

**Full Changelog**: https://github.com/SatelliteShorelines/CoastSeg/compare/v1.2.0...v1.2.1dev1

**Full Changelog**: https://github.com/Doodleverse/CoastSeg/compare/v1.1.45...v1.2.0
New Features
1. Latitude and Longitude of where shoreline points intersected the transects are now saved to the timeseries csv files
2. Two new geojson files that contain the shoreline points that intersected the transects (derived from the timeseries csv) are generated
3. A new setting has been added called 'drop intersection points', which drops any shoreline points that were not located directly on the transect from the timeseries.csv files
4. A new polygon can be drawn on the map called the Shoreline Extraction Area and CoastSeg will only keep the extracted shorelines in this region

Summary

This release adds a brand new control to the settings called 'drop intersection points', which drops any shoreline points that were not located directly on the transect from the timeseries.csv files. Additionally the latitude and longitude of where the shoreline point intersected the transect is now saved to the timeseries csv files under the column names 'shore_x' and 'shore_y'. Two new files are now generated called 'raw_transect_time_series_points.geojson' and 'raw_transect_time_series_vectors.geojson'. Additionally the timeseries csv files containing where the 2D shorelines intersected the transects have been renamed to be much more consistent. We have included a diagram below with the changes.

New GeoJSON Files
- `raw_transect_time_series_points.geojson` : contains the shoreline transect intersections points from `raw_transect_time_series_merged.csv`.
- `raw_transect_time_series_vectors.geojson` : contains the shoreline transect intersections from `raw_transect_time_series_merged.csv`. as vectors by connecting points that occured on the same date together.

If tidal correction is applied then the following files are generated
- `tidally_corrected_transect_time_series_points.geojson` : contains the tidally_corrected shoreline transect intersections points from `raw_transect_time_series_merged.csv`.
- `tidally_corrected_raw_transect_time_series_vectors.geojson` : contains the tidally_corrected shoreline transect intersections from `raw_transect_time_series_merged.csv`. as vectors by connecting points that occurred on the same date together.

How the Shoreline Extraction Process Maps 2D Shorelines onto Transects

New File Names




New Setting to Control Dropping Shoreline Intersection Points Not on Transects
- This new settings controls the whether the shoreline points derived from the transect shoreline intersections from the timeseries csv files are dropped if they are not on transect
- By default this is OFF, meaning all the transect shoreline intersections are kept
- To drop shoreline points not on the transect set this to ON



Effect of dropping Shoreline Transect Intersection Points Not on Transects
- GeoJSON : raw_transect_time_series_points.geojson
- This file contains the shoreline and transect intersection points
Points Before Dropping Shoreline Points Not on Transect

Points After Dropping Shoreline Points Not on Transect


All Points


Understand 'raw_transect_time_series_vectors.geojson' is Created
- This file contains the shoreline and transect intersection points connected together to form a vector
- It creates one continuous shoreline by interpolating the closet points together
- The shoreline vectors generated by interpolating the points together may result in strange shorelines due to the fact the closet points are always connected

Example 1: good shoreline vector
- This vector connects many shoreline and transect intersection points
- Not many transects were missing intersecting shoreline points so the interpolation to create the vector worked great


Example 2: bad shoreline vector
- There is a large straight portion of the shoreline (surrounded by the red box) that is the result of interpolating 2 shorelines points that occurred on transects very far away from each other
- Shoreline points on these transects are missing because they were filtered out because they did not land on the transect.
- The most likely cause of this was a cloud being mis-classified as a shoreline




Shoreline Extraction Area Feature
A new feature called the shoreline extraction area has been added. This is an optional feature that users can draw on the map that removes any extracted shorelines outside of this region. On the figure below the shoreline extraction area is show in purple and the shorelines were only extracted within it.

Zoo Workflow Updates
- Users can now save settings more reliably with the save settings button
- combined the run model and extraction shorelines buttons into a single button
- shoreline extraction area can be uploaded from a geojson file



Closed Issues
206 : Transect time series now saves the lat and lon of the shorelines
223: Zoo workflow notebook has combined the run model and extraction shorelines buttons into a single button
232 : A shoreline extraction area can be drawn on the map and shorelines will be extracted only within this region
229 : An output directory can be passed to the `extract_shorelines` function that specifies the directory where the shoreline extraction detection figures should be saved