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

Wave Height vs. Significant Wave Height #290

Open
abkfenris opened this issue Feb 3, 2021 · 1 comment
Open

Wave Height vs. Significant Wave Height #290

abkfenris opened this issue Feb 3, 2021 · 1 comment
Assignees

Comments

@abkfenris
Copy link
Member

abkfenris commented Feb 3, 2021

Copied from ClickUp CU-64fght

There are inconsistencies with how we are labeling wave measurements. Some of this is from failing over to the secondary wave sensors that are measuring significant wave height vs. average. The charts are also a little misleading. Placeholder for this issue, I need some clarification from Tom so I can do a better job of explaining exactly what needs updating!

@youngmorse
Copy link

It's confusing. I think we were trying make sure the label on the variable matched the BIO forecast - which is significant wave height. If the secondary sensors are measuring an average value then they should probably be their own chart and not a fail over. Safe to say this isn't well understood (or documented in the ERDDAP metadata) as to which are actual values vs. average over a period of time. Re: the forecast charts, what Tom wants, and I think makes sense, is that the forecast variable matches the observation variable. So if the forecast is for significant wave height, the only observations we should show are significant wave height. Just a placeholder comment in case it's helpful at the moment, but I'll try to get clarification from Tom.

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