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

Water levels differ from the public tide predictors #149

Open
landyrev opened this issue Aug 19, 2022 · 2 comments
Open

Water levels differ from the public tide predictors #149

landyrev opened this issue Aug 19, 2022 · 2 comments

Comments

@landyrev
Copy link

landyrev commented Aug 19, 2022

Hey, @kevee! Thanks for a great lib.

I'm playing with tide predictions and noticed that water levels generated by neaps/tide-predictor are quite different from the ones I can find in other tide predictors.

As an example I'm comparing the Monterey, CA tidal station, 2022-08-19

Neaps results:
High level at 2022-08-19T21:08:11.000Z is 0.711727... meters
Low level at 2022-08-19T17:28:11.000Z is -0.0094... meters

US Harbors results:
High level at 2022-08-19T00:13:00.000Z is 1.55... meters
Low level at 2022-08-19T17:31:00.000Z is 0.85... meters

So, while the time is pretty correct, the water levels looks offsetted compared to public predictions.

@kevee
Copy link
Member

kevee commented Jan 13, 2023

Thank you, @landyrev! I've been heads down in other projects for the past few months but I'll take a look at this PR next week.

Quick question - did you include an offset when you passed the harmonic constituents?

@noGAFAM
Copy link

noGAFAM commented Jul 8, 2024

@kevee, indeed, with offset, namely data_sets.datum from a harmbase2 database it works. Any reason for not including this data by default?

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

4 participants
@kevee @landyrev @noGAFAM and others