-
Notifications
You must be signed in to change notification settings - Fork 1
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
Quality codes and QARTOD flags #6
Comments
QARTOD variablesHere are my thoughts on what the
It's also recommended to have a
location_classThe location class is currently defined as: However,
It could also be
Ancillary variables:From CF:
I'm not sure what the I'm also wondering about the following variables and if they should be listed as
|
From @iamchrisser:
Standard name additionsAncillary Variables:Questions
|
Yes? So we want |
I thought I commented on this already, but maybe I didn't hit the comment button. Sorry if these notes are somewhere else. I think that's the last of the Within the qartod variables, we should have a |
I think the most recent update addresses all of these. |
Nice! Thanks for putting the ioos-atn-data/data/atn_trajectory_template_ncdump_20211006.txt Lines 186 to 213 in 2dcafb8
|
There was a robust discussion and consensus on how to codify these. I need to digest and see what should be changed.
https://github.com/MathewBiddle/ATN-archive/blob/b738cbcf3836f50a3b518790662e376b7e3ad0d1/data/deployment_km_greyseal_v1.ncdump#L58-L67
https://github.com/MathewBiddle/ATN-archive/blob/b738cbcf3836f50a3b518790662e376b7e3ad0d1/data/deployment_km_greyseal_v1.ncdump#L185-L212
I think we need to bring in the the variable attribute
ancillary_variables
into some of these. See CF-conventions on Ancillary Data.The text was updated successfully, but these errors were encountered: