| _version_ | 1866902278850478080 |
|---|---|
| author | Muir, Freya |
| author_facet | Muir, Freya |
| contents | <div> <h2>Second Release</h2> <ul> <li>This is the second release of the COASTGUARD repo. The repo has been extended to a new toolset <a href="https://github.com/fmemuir/COASTGUARD/blob/master/CoasTrack_DriverTemplate.py">CoasTrack</a> for generating and analysing timeseries of coastal vegetation edges, waterlines, topographic swaths and wave conditions along cross-shore transects.</li> <li>The goal with the CoasTrack release/toolset is to build a digital twin of the coast, using only satellite- or aerially-derived data.</li> <li>Note: the tag date for this release is 2024-06-12, even though the release is 2025-01-22</li> <li>More tools for predicting changes to vegetation edges and waterlines will be coming soon</li> </ul> <h2>New Functionality</h2> <ul> <li>Transects now intersect with and store: <ul> <li>Timeseries of VE positions, dates of capture, NDVI thresholds used to contour;</li> <li>Timeseries of WL positions, dates of capture, NDWI thresholds used to contour;</li> <li>Timeseries of beach widths between them;</li> <li>Timeseries of tidal elevations at the time of each satellite image (from FES2014 and <strong>now FES2022</strong> <a href="https://github.com/fmemuir/COASTGUARD/issues/26">#26</a>);</li> <li>Rate of change from oldest to newest VE and WL in m/yr;</li> <li>Rate of change from second newest to newest VE and WL in m/yr;</li> <li>Timeseries of corrected WL positions based on tidal elevation and beach slope;</li> <li><a href="https://github.com/kvos/CoastSat.slope/">Dynamic beach slope</a> value based on WL timeseries;</li> <li>Timeseries of maximum slope values at each VE position, extracted from single DEM;</li> <li>Timeseries of mean slope values at each VE position, extracted from single DEM;</li> <li>Timeseries of widths of the vegetation transition zone;</li> <li>Mean width of the vegetation transition zone;</li> <li>Timeseries of significant wave height from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of mean wave direction from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of peak wave period from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of wave alpha AKA difference between mean wave direction and shore angle (full timeseries, not just satellite dates);</li> <li>Net wave diffusivity index;</li> <li>Net wave stability index;</li> <li>Wave runups calculated using chosen runup formulation (<a href="https://doi.org/10.1029/2010JC006819" rel="nofollow">Senechal et al., 2011</a> or <a href="https://doi.org/10.1016/j.coastaleng.2005.12.005" rel="nofollow">Stockdon et al., 2006</a>);</li> <li>Iribarren number based on extracted wave conditions</li> </ul> </li> <li>Updates to geemap implemented (<a href="https://github.com/fmemuir/COASTGUARD/issues/10">#10</a>)</li> <li>New Google Earth Engine Landsat collections updated (<a href="https://github.com/fmemuir/COASTGUARD/issues/13">#13</a>)</li> <li>Streamlining of GEE ImageCollection creation in a loop (<a href="https://github.com/fmemuir/COASTGUARD/issues/19">#19</a> and <a href="https://github.com/fmemuir/COASTGUARD/issues/24">#24</a>)</li> <li>Tidal correction functions extended, enhanced, and now use <a href="https://github.com/kvos/CoastSat.slope/">CoastSat.slope</a> to calculate the dynamic beach slope (<a href="https://github.com/fmemuir/COASTGUARD/issues/20">#20</a>)</li> <li>Plotting functions for analysis (<a href="https://github.com/fmemuir/COASTGUARD/blob/master/Toolshed/Plotting.py">Plotting.py</a> and <a href="https://github.com/fmemuir/COASTGUARD/blob/master/Toolshed/PlottingSeaborn.py">PlottingSeaborn.py</a>): <ul> <li>VE timeseries, WL timeseries Transition Zone timeseries;</li> <li>Seasonality assessment where seasonal (annual) signals are extracted from the timeseries and a Seasonal Strength Index is calculated;</li> <li>Wave direction rose plots with wave height histograms on radius axis;</li> <li>Multivariate matrix of all the single-value-per-transect metrics listed above, plotted as scatter plots with linear and LOESS lines of best fit;</li> <li>Ability to cluster per-transect values in multivariate matrix by VE trend (eroding or accreting);</li> <li>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;</li> <li>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)</li> </ul> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fmemuir/COASTGUARD/compare/VedgeSat-v1.0...CoasTrack-v1.0">VedgeSat-v1.0...CoasTrack-v1.0</a></p> <h2>Acknowledgments</h2> <ul> <li><a href="https://github.com/IdhamN">@IdhamN</a>: bug-finding, testing, TZ adjustments, plotting suggestions</li> <li><a href="https://github.com/nguardo24">@nguardo24</a>: bug-finding, testing, and PlanetScope API suggestions</li> <li><a href="https://github.com/cmac95">@cmac95</a>: bug-finding, testing, datetime suggestions</li> <li><a href="https://github.com/ccromwellu">@ccromwellu</a>: bug-finding, testing</li> <li><a href="https://github.com/DakDune">@DakDune</a>: bug-finding, testing</li> </ul> </div> |
| format | Recurso digital |
| id | zenodo_https___doi_org_10_5281_zenodo_14719870 |
| institution | Zenodo |
| language | |
| publishDate | 2025 |
| publisher | Zenodo |
| record_format | zenodo |
| spellingShingle | CoasTrack release in COASTGUARD repo Muir, Freya <div> <h2>Second Release</h2> <ul> <li>This is the second release of the COASTGUARD repo. The repo has been extended to a new toolset <a href="https://github.com/fmemuir/COASTGUARD/blob/master/CoasTrack_DriverTemplate.py">CoasTrack</a> for generating and analysing timeseries of coastal vegetation edges, waterlines, topographic swaths and wave conditions along cross-shore transects.</li> <li>The goal with the CoasTrack release/toolset is to build a digital twin of the coast, using only satellite- or aerially-derived data.</li> <li>Note: the tag date for this release is 2024-06-12, even though the release is 2025-01-22</li> <li>More tools for predicting changes to vegetation edges and waterlines will be coming soon</li> </ul> <h2>New Functionality</h2> <ul> <li>Transects now intersect with and store: <ul> <li>Timeseries of VE positions, dates of capture, NDVI thresholds used to contour;</li> <li>Timeseries of WL positions, dates of capture, NDWI thresholds used to contour;</li> <li>Timeseries of beach widths between them;</li> <li>Timeseries of tidal elevations at the time of each satellite image (from FES2014 and <strong>now FES2022</strong> <a href="https://github.com/fmemuir/COASTGUARD/issues/26">#26</a>);</li> <li>Rate of change from oldest to newest VE and WL in m/yr;</li> <li>Rate of change from second newest to newest VE and WL in m/yr;</li> <li>Timeseries of corrected WL positions based on tidal elevation and beach slope;</li> <li><a href="https://github.com/kvos/CoastSat.slope/">Dynamic beach slope</a> value based on WL timeseries;</li> <li>Timeseries of maximum slope values at each VE position, extracted from single DEM;</li> <li>Timeseries of mean slope values at each VE position, extracted from single DEM;</li> <li>Timeseries of widths of the vegetation transition zone;</li> <li>Mean width of the vegetation transition zone;</li> <li>Timeseries of significant wave height from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of mean wave direction from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of peak wave period from requested Copernicus Marine Service product (full timeseries, not just satellite dates);</li> <li>Timeseries of wave alpha AKA difference between mean wave direction and shore angle (full timeseries, not just satellite dates);</li> <li>Net wave diffusivity index;</li> <li>Net wave stability index;</li> <li>Wave runups calculated using chosen runup formulation (<a href="https://doi.org/10.1029/2010JC006819" rel="nofollow">Senechal et al., 2011</a> or <a href="https://doi.org/10.1016/j.coastaleng.2005.12.005" rel="nofollow">Stockdon et al., 2006</a>);</li> <li>Iribarren number based on extracted wave conditions</li> </ul> </li> <li>Updates to geemap implemented (<a href="https://github.com/fmemuir/COASTGUARD/issues/10">#10</a>)</li> <li>New Google Earth Engine Landsat collections updated (<a href="https://github.com/fmemuir/COASTGUARD/issues/13">#13</a>)</li> <li>Streamlining of GEE ImageCollection creation in a loop (<a href="https://github.com/fmemuir/COASTGUARD/issues/19">#19</a> and <a href="https://github.com/fmemuir/COASTGUARD/issues/24">#24</a>)</li> <li>Tidal correction functions extended, enhanced, and now use <a href="https://github.com/kvos/CoastSat.slope/">CoastSat.slope</a> to calculate the dynamic beach slope (<a href="https://github.com/fmemuir/COASTGUARD/issues/20">#20</a>)</li> <li>Plotting functions for analysis (<a href="https://github.com/fmemuir/COASTGUARD/blob/master/Toolshed/Plotting.py">Plotting.py</a> and <a href="https://github.com/fmemuir/COASTGUARD/blob/master/Toolshed/PlottingSeaborn.py">PlottingSeaborn.py</a>): <ul> <li>VE timeseries, WL timeseries Transition Zone timeseries;</li> <li>Seasonality assessment where seasonal (annual) signals are extracted from the timeseries and a Seasonal Strength Index is calculated;</li> <li>Wave direction rose plots with wave height histograms on radius axis;</li> <li>Multivariate matrix of all the single-value-per-transect metrics listed above, plotted as scatter plots with linear and LOESS lines of best fit;</li> <li>Ability to cluster per-transect values in multivariate matrix by VE trend (eroding or accreting);</li> <li>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;</li> <li>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)</li> </ul> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fmemuir/COASTGUARD/compare/VedgeSat-v1.0...CoasTrack-v1.0">VedgeSat-v1.0...CoasTrack-v1.0</a></p> <h2>Acknowledgments</h2> <ul> <li><a href="https://github.com/IdhamN">@IdhamN</a>: bug-finding, testing, TZ adjustments, plotting suggestions</li> <li><a href="https://github.com/nguardo24">@nguardo24</a>: bug-finding, testing, and PlanetScope API suggestions</li> <li><a href="https://github.com/cmac95">@cmac95</a>: bug-finding, testing, datetime suggestions</li> <li><a href="https://github.com/ccromwellu">@ccromwellu</a>: bug-finding, testing</li> <li><a href="https://github.com/DakDune">@DakDune</a>: bug-finding, testing</li> </ul> </div> |
| title | CoasTrack release in COASTGUARD repo |
| url | https://doi.org/10.5281/zenodo.14719870 |