@davidhassell I am trying to keep this proposal as simple as possible. I've 
gone through a few iterations on options and I think the current proposal is 
the least drastic change to the convention. I see no issue with ancillary 
variables containing ancillary variables as that attribute is just a linkage.

A previous discussion was to use standard name modifiers but that became 
cumbersome and would require a change to the CF document each time we add new 
uncertainty. I also thought about creating a new attribute but that would 
require either changing the CF document appendix where they are listed each 
time a new one is added or a new external look up. Since we have the standard 
name table already I am suggesting we use that.

If we wanted to use cf_role set to "uncertainty" to indicate the variable 
contains uncertainty values that is fine. But we don't require that for other 
variables (like state variables, quality control, data, platform information) 
so it would be a strange one off. If we wanted to create a new attribute to 
signify the values are uncertainty that is fine. But I'd prefer to keep the 
description of the variable contents using standard name table so we don't need 
to create a new table.

Honestly I'm not a huge fan of cell methods. If that is causing strife I'm OK 
with dropping it and just using a comment attribute, standard name table, or 
reference attribute to point to a document with the description of how it was 
computed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/320*issuecomment-879237975__;Iw!!G2kpM7uM-TzIFchu!mblC-70vZim-42d9gznkTR1nJ89NX6altKpS3yiar_KJS6Y76O3xyBmVq4qofew9cDajxjyQuH0$
 
This list forwards relevant notifications from Github.  It is distinct from 
[email protected], although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
[email protected].

Reply via email to