Skip to content

Releases: SatelliteShorelines/coastsat_package

v0.1.43

17 Jan 21:08
Compare
Choose a tag to compare

Full Changelog: v0.1.42...v0.1.43

v0.1.42

17 Jan 18:48
Compare
Choose a tag to compare

Full Changelog: v0.1.41...v0.1.42

v0.1.41

10 Jan 16:39
Compare
Choose a tag to compare

Full Changelog: v0.1.40...v0.1.41

v0.1.40

09 Jan 02:39
Compare
Choose a tag to compare

Full Changelog: v0.1.39...v0.1.40

Release Date: January 8th, 2023

We are excited to announce the release of coastsat_package v0.1.40. We would like to express our gratitude to all the contributors who made this release possible. This version contains upgrades that keeps coastsat_package update to date.

Changelog

  • Now uses the S2_HARMONIZED collection
    • Google Earth Engine announced that the harmonized collection should be used for the S2 imagery

Notice: the Sentinel Level-1C and Level-2A data products shown here have a harmonized time series. The "harmonized" designation means that the band-dependent offset added to reflectance bands in the 04.00 processing baseline has been removed. The offset affects data after January 24th 2022; removing the offset puts these data in spectral alignment with pre-04.00 baseline data. If you are using COPERNICUS/S2 or COPERNICUS/S2_SR, it is recommended that you switch to COPERNICUS/S2_HARMONIZED and COPERNICUS/S2_SR_HARMONIZED." - earth-engine-S2

Bug Fixes

  • Fixed the bug where there was a border of no data pixels around S2 imagery
    2023-12-05-19-04-17_S2

  • Fixed the autodetected range of [nan, nan] is not finite bug in compute_intersection_QC

  • Fixed index is None bug in compute_intersection_QC

v0.1.39

14 Dec 22:37
Compare
Choose a tag to compare

Full Changelog: v0.1.38...v0.1.39

v0.1.38

09 Dec 00:24
Compare
Choose a tag to compare

Full Changelog: v0.1.37...v0.1.38

v0.1.37

30 Nov 17:04
Compare
Choose a tag to compare

Full Changelog: v0.1.36...v0.1.37

v0.1.36

30 Nov 02:09
Compare
Choose a tag to compare

Full Changelog: v0.1.35...v0.1.36

v0.1.35

29 Nov 19:47
Compare
Choose a tag to compare

Full Changelog: v0.1.34...v0.1.35

v0.1.34

15 Nov 20:08
Compare
Choose a tag to compare

Full Changelog: v0.1.33...v0.1.34

Release v0.1.34

Release Date: November 15, 2023

We are excited to announce the release of coastsat_package v0.1.34. We would like to express our gratitude to all the contributors who made this release possible. This version improves download stability and plots the reference shoreline buffer on the extract shorelines detection images, and we highly recommend all users to upgrade.

Changelog

  • Reference Shoreline Buffer is now plotted in extracted shoreline imagery
  • Improved logic to retry failed downloads to bad internet connection
  • Successful downloads are now saved to the download report.txt located in the ROI's directory in /data
  • #7
  • #6

Bug Fixes

  • Fixed in issue #7 where get_images_available would loop forever if there was no internet connection
  • Fixed in issue #7 retrieve_images will attempt to reconnect 3 times before raising an error when querying the GEE API to delete bands from the image when there is no internet connection

New Features

  • Added in issue #6 The reference shoreline buffer is now plotted in the detection images generated by coastsat
    2018-12-11-19-04-12_S2

Known Bugs

  • If the internet connection fails at the same time this code is called in download_tif then no error message will be raised and the download will be stuck. This appears to be an issue with GEE. If this happens the download will need to be restarted.
download_id = ee.data.getDownloadId(
                {
                    "image": image,
                    "region": polygon,
                    "bands": bands,
                    "filePerBand": True,
                    "name": "image",
                }
            )

How to Upgrade

To upgrade to the latest version, you can follow these steps:

  1. Pull the latest version from the main branch. git pull origin main
  2. pip install coastsat_package==v0.1.34

Feedback

We are eager to hear about your experiences with this new release. Please provide your feedback, file issues, or contribute a pull request on our GitHub page.