Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shoreline Assessment Methodology #1

Open
kvos opened this issue Sep 9, 2022 · 5 comments
Open

Shoreline Assessment Methodology #1

kvos opened this issue Sep 9, 2022 · 5 comments

Comments

@kvos
Copy link
Member

kvos commented Sep 9, 2022

Discussion of Shoreline Assessment Methodology

This thread is to discuss the methodology to assess the accuracy of the satellite-derived shorelines against the in situ data.

@kvos
Copy link
Member Author

kvos commented Sep 9, 2022

I can propose one option, which works for sites where we have topographic surveys along individual transects (eg, Narrabeen, Duck and Torrey Pines):

1. Transects based approach:

  • compute intersections between 2D shorelines and cross-shore transects to obtain time-series of shoreline change.
  • apply a water level correction along the transects to obtain tidally-corrected time-series of shoreline change
  • compare the tidally-corrected time-series of shoreline change against the in situ time-series of shoreline change for the same contour:
    • compute point-by-point RMSE, bias and STD.
    • compare linear trends

For sites where DEMs or camera-derived shorelines are available, there is the possibility to also compare the shorelines alongshore, as previously done by the UPV team. If anyone could expand on this 'alongshore approach' that would be great.

@kvos kvos added the question Further information is requested label Sep 9, 2022
@kvos kvos removed the question Further information is requested label Oct 21, 2022
@kvos
Copy link
Member Author

kvos commented Nov 9, 2022

I have added a new notebook to evaluate the satellite-derived shoreline of time-series of shoreline change against the in situ data:
https://github.com/SatelliteShorelines/SDS_Benchmark/blob/main/2_compare_sat_to_groundtruth.ipynb

You can use this notebook to test your outputs against the in-situ data. Feel free to add to the assessment methodology, for the moment the following metrics are calculated on a transects base as well as grouped into sites:

  • RMSE
  • STD
  • Mean bias
  • 90th error percentile
  • R2
  • Goodness of fit (Chi-squared)

@dbuscombe-usgs
Copy link
Member

Could you please expand a little on the 'alongshore approach' - why is this only possible when DEMS or cameras are available? We can extract the shoreline as a continuous vector defined as latitude, longitude ... tides could be applied in 2d, and shorelines could be tracked in 2d, as well. It's just easier to map everything onto transects

@kvos
Copy link
Member Author

kvos commented Mar 3, 2023

at narrabeen for example we only survey 5 cross-shore transects along the 3.5km beach. Duck and Torrey Pines are also transect based. So the comparison between SDS and in situ timeseries can only be done along those transects.

Tidally-correcting the shorelines directly is possible but not that easy, how do you know what is the cross-shore direction? especially on embayed beaches that rotate this is not straight forward and requires some specific transformations (Mitch's log-spiral for example)

@dbuscombe-usgs
Copy link
Member

We'll stick with transects, although we are being asked by USGS colleagues to provide continuous shorelines. As you say, that would require knowing the orientation of the coast. I was looking for more specific details about how a DEM could be used here - after all, DEMs are available at some resolution everywhere ...

The challenge with transects is that if the orientation of the coast changes, you need to redraw the transect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants