v1.1.31

Full Changelog: v1.1.30...v1.1.31

Release Date: Feb 8, 2024

This version of coastseg renders transects as arrows on the map and extracted shorelines on the widget on the right side. It also contains the bug fixed from 1.1.30 which are highlighted below.

It fixes the bug where downloaded ROIs in the /data folder has their config.json and config_gdf.geojson files overwritten when shoreline were extracted. This new version also allows users to load ROI from sessions where not all the ROIs were downloaded. Now a warning appears to tell the user that some of the ROIs are missing but that they can still extract shorelines for the ROIs that were downloaded. (#218) Tide correction now correctly converts the CRS of the transects so tide predictions are correctly performed at the end of each transect (#222) . Lastly tide correction has been fixed so it works in both the coastsat and zoo workflows (#227)

Upgrade

pip install coastseg==1.1.31

Change Log

Closed Issues from 1.1.31

1. Fixes #213 : Transects are now rendered as arrows on the map where each transect points to its end point, which is supposed to be seaward.
2. Extracted shorelines' metadata is once again render on the widget on the right side of the map.

Closed Issues from 1.1.30

1.Fixes issue #222: The transects end point are now correctly converted to the CRS 4326 and used to predict the tides.
3. Fixes issue #227 : Tide correction works in both the Zoo and CoastSat workflows

• All input transects are converted to CRS 4326 before checked which region of the tide model they belong to

4. Fixes issue #218 : ROI Settings Not Found Bug

• If a user shared one ROI out of a session containing more ROIs. Users can now extract shorelines from the one ROI shared. A warning message (see below) will appear to tell them which ROIs are missing and that they can extract shorelines for the downloaded ROIs.
• It fixes the bug where downloaded ROIs in the /data folder has their config.json and config_gdf.geojson files overwritten when shorelines were extracted. If a user extracted shorelines for a single ROI out of a session of 3 ROIs that ROI's config.json and config_gdf.geojson files in the /data folder were overwritten to ONLY have that ROI's data instead of all the ROIs from the session it belonged to.
• ROI settings can be read from multiple subdirectories meaning that users can load a session containing multiple independent ROIs with extracted shorelines and have all the ROI settings load correctly. WARNING only one set of settings will load to populate the widget.

New Warning Messages for Missing ROIs

#218 A new warning message informing the user that not all the ROIs were downloaded but that they can still extract shorelines for the downloaded ROIs.