Jonathan,

Thanks for the suggestion. I can see how using cell_method = "uncertainty" 
would work, but the main issue is that we don't know the method. The method is 
not standard_error. So the information provided in cell_methods in your example 
is incorrect. We do not know the method. I would be on board with moving the 
statistical or subjective into the method location as that is not listing a 
specific mathematical process.

float random(time);
   random:long_name = "Random uncertainty in calibration_e_LH";
   random:units = "1";
   random:cell_methods = "uncertainty: statistical (random)";

float systematic(time);
   systematic:long_name = "Systematic uncertainty in calibration_e_LH";
   systematic:units = "1";
   systematic:cell_methods = "uncertainty: subjective (systematic)";

I think there is confusion between the need to describe the process 
(statistical vs. subjective) and need to describe the type (total, random, 
systematic, specific random, specific systematic). According to GUM both 
classifiers are needed for describing uncertainty. Following the idea of 
absence of a qualifier defaulting to something, the default would be "(total)".

With this method I would suggest the data user searching cell_methods for a 
string starting with "uncertainty: " as the indicator a variable is an 
uncertainty variable. This would be equivalent to searching the standard_name 
ending in "uncertainty". Then the keywords random or systematic in parentheses 
would indicate the type. Absence of these words would mean total. This would 
require the addition of subjective and statistical to the cell_methods method 
list.

I feel we are getting close to a solution.

Thanks,

Ken

-- 
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-920134125__;Iw!!G2kpM7uM-TzIFchu!lP05Dd0nakhTVpV_E4KcY17Y4P8eZhZnbzR2MHgnqEXP1kK40TGv7Evs7QYfXftmKRQTxr6CyDw$
 
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