Skip to content

CoasTrack release

Latest
Compare
Choose a tag to compare
@fmemuir fmemuir released this 22 Jan 15:16
· 318 commits to master since this release

Second Release

  • This is the second release of the COASTGUARD repo. The repo has been extended to a new toolset CoasTrack for generating and analysing timeseries of coastal vegetation edges, waterlines, topographic swaths and wave conditions along cross-shore transects.
  • The goal with the CoasTrack release/toolset is to build a digital twin of the coast, using only satellite- or aerially-derived data.
  • Note: the tag date for this release is 2024-06-12, even though the release is 2025-01-22
  • More tools for predicting changes to vegetation edges and waterlines will be coming soon

New Functionality

  • Transects now intersect with and store:
    • Timeseries of VE positions, dates of capture, NDVI thresholds used to contour;
    • Timeseries of WL positions, dates of capture, NDWI thresholds used to contour;
    • Timeseries of beach widths between them;
    • Timeseries of tidal elevations at the time of each satellite image (from FES2014 and now FES2022 #26);
    • Rate of change from oldest to newest VE and WL in m/yr;
    • Rate of change from second newest to newest VE and WL in m/yr;
    • Timeseries of corrected WL positions based on tidal elevation and beach slope;
    • Dynamic beach slope value based on WL timeseries;
    • Timeseries of maximum slope values at each VE position, extracted from single DEM;
    • Timeseries of mean slope values at each VE position, extracted from single DEM;
    • Timeseries of widths of the vegetation transition zone;
    • Mean width of the vegetation transition zone;
    • Timeseries of significant wave height from requested Copernicus Marine Service product (full timeseries, not just satellite dates);
    • Timeseries of mean wave direction from requested Copernicus Marine Service product (full timeseries, not just satellite dates);
    • Timeseries of peak wave period from requested Copernicus Marine Service product (full timeseries, not just satellite dates);
    • Timeseries of wave alpha AKA difference between mean wave direction and shore angle (full timeseries, not just satellite dates);
    • Net wave diffusivity index;
    • Net wave stability index;
    • Wave runups calculated using chosen runup formulation (Senechal et al., 2011 or Stockdon et al., 2006);
    • Iribarren number based on extracted wave conditions
  • Updates to geemap implemented (#10)
  • New Google Earth Engine Landsat collections updated (#13)
  • Streamlining of GEE ImageCollection creation in a loop (#19 and #24)
  • Tidal correction functions extended, enhanced, and now use CoastSat.slope to calculate the dynamic beach slope (#20)
  • Plotting functions for analysis (Plotting.py and PlottingSeaborn.py):
    • VE timeseries, WL timeseries Transition Zone timeseries;
    • Seasonality assessment where seasonal (annual) signals are extracted from the timeseries and a Seasonal Strength Index is calculated;
    • Wave direction rose plots with wave height histograms on radius axis;
    • Multivariate matrix of all the single-value-per-transect metrics listed above, plotted as scatter plots with linear and LOESS lines of best fit;
    • Ability to cluster per-transect values in multivariate matrix by VE trend (eroding or accreting);
    • Perform Principal Component Analysis on all the single-value-per-transect metrics listed above, and generate a biplot of the first and second PCs with eigenvectors of each metric;
    • Timeseries of storms, tidal elevations, and successful vs. unsuccessful satellite images (new functionality also added to record success rates and reasons for images being ignored)

Full Changelog: VedgeSat-v1.0...CoasTrack-v1.0

Acknowledgments

  • @IdhamN: bug-finding, testing, TZ adjustments, plotting suggestions
  • @nguardo24: bug-finding, testing, and PlanetScope API suggestions
  • @cmac95: bug-finding, testing, datetime suggestions
  • @ccromwellu: bug-finding, testing
  • @DakDune: bug-finding, testing