You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Mitch,
I've been testing the tool you've implemented for the trend plot and animation these days. On the beaches facing west, it performs the beach width calculations in reverse of what is expected, meaning when it should be a minimum value, it comes out as a maximum and vice versa. I thought it might be due to the orientation of the transects, and I've tried not flipping the transects, but it still does it the same, which has surprised me. However, on the beaches facing east, the results are logical. Any idea why this might be? If you need, I can send you images.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi Rita, this could be a bug in the rotatePoints code when the orientation is from a certain quadrant (such as your beaches). I wont have time to look into it myself but would suggest looking into that
Hi Mitch,
I've been testing the tool you've implemented for the trend plot and animation these days. On the beaches facing west, it performs the beach width calculations in reverse of what is expected, meaning when it should be a minimum value, it comes out as a maximum and vice versa. I thought it might be due to the orientation of the transects, and I've tried not flipping the transects, but it still does it the same, which has surprised me. However, on the beaches facing east, the results are logical. Any idea why this might be? If you need, I can send you images.
Thanks!
The text was updated successfully, but these errors were encountered: