-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bug Investigation: Tide Correction XY Points used to Predict Tides #222
Comments
Here is the user report along with an image of what they saw when they loaded the XY points from the csv into ARC. The points on the figure are the seaward points used to predict the tides for each of the transects. As you can see the points in the figure don't match the seaward points of the transects in the figure
|
After diving into the tide correction workflow. I'm not sure exactly what caused this exact bug but I think that it has to do with the XY columns used in the seaward points that are used to predict the tides. Instead of creating these 2 columns the XY points should just be read from the geometry which :
I will keep the behavior where an XY point is saved to the tide corrected file for now. |
Closed in version 1.1.30 |
I received a report from a user that when the tide correction is applied to a session that didn't use the default transects the XY points don't reflect the seaward points of the transects in the session but instead appear to be the default transects. I don't know if this is true, but it needs to be investigated.
The text was updated successfully, but these errors were encountered: