Re: [CF-metadata] [cf-convention/cf-conventions] What is meant by "original data" in the definition of the "source" attribute? (#341)
Another example for observations might be something like ``source = "the MSU (Microwave Sounding Unit) instrument flown on the XXX satellite produced radiances that were converted into lower tropospheric temperature estimates using the YYY algorithm"``. Not sure that's a great example, but it makes the point that "source" doesn't have to be a terse model acronym, and in this case the algorithm that is in fact the the immediate "source" of the data requires MSU measurements as input. -- 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/341*issuecomment-940132878__;Iw!!G2kpM7uM-TzIFchu!mVjIlasqBtnR56OW89WIAVHfRoqlA877FMsNkqYfCV-7p_omKFR0kQ-DnLaSqSJvFdxJROvUVrY$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Is it possible to use cell methods for percentiles statistics estimated for more than 2 axes (25 axes) ? (#342)
@DikraK, I think you are not calculating statistics over 25 axes, but rather really over only one: the axis of the ensemble. The problem is that this information is not apparent in your current encoding. IMHO, the best way to add this information would be to combine your current 25 variables into a single variable with an additional coordinate, i.e. ``` dimensions: time=UNLIMITED; ensemble=25; variables: float time(time) ; time:long_name = "time" ; time:units = "2021-10-07 12:00:00" ; time:calendar = "gregorian" ; time:standard_name = "time" ; time:axis = "T" ; float pr(ensemble, time, rlon, rlat) ; pr:grid_mapping_name = "latitude_longitude" ; pr:coordinates = "lon lat" ; pr:shortname = "Quantity of precipitation" ; ... pr:standard_name = "precipitation_amount" ; ``` Then it is easy to see that you can add the percentile information using something like `cell_methods="ensemble: sum"`. Note that `sum` in `cell_methods` does not necessary mean "sum", but rather some form of "sum or accumulation", see [CF Conventions 1.9, Appendix E](https://urldefense.us/v3/__http://cfconventions.org/Data/cf-conventions/cf-conventions-1.9/cf-conventions.html*appendix-cell-methods__;Iw!!G2kpM7uM-TzIFchu!g2g_f0_WB2tm-MhehHtFacKJ7z2NUrOtKjfPX1sp507JtId2hsCZvlNeVNlmyK-tTeEzOpGSXkc$ ). Allow me also to comment that your use of `rlon` and `rlat` suggests the use of a rotated grid as is common for example in CORDEX. If this is indeed the case, you probably don't want to use the `latitude_longitude` grid mapping and might want to review [CF Conventions 1.9, Section 5.6](https://urldefense.us/v3/__http://cfconventions.org/Data/cf-conventions/cf-conventions-1.9/cf-conventions.html*grid-mappings-and-projections__;Iw!!G2kpM7uM-TzIFchu!g2g_f0_WB2tm-MhehHtFacKJ7z2NUrOtKjfPX1sp507JtId2hsCZvlNeVNlmyK-tTeEzN_fvvXA$ ) and Appendix F [here](https://urldefense.us/v3/__http://cfconventions.org/Data/cf-conventions/cf-conventions-1.9/cf-conventions.html*_latitude_longitude__;Iw!!G2kpM7uM-TzIFchu!g2g_f0_WB2tm-MhehHtFacKJ7z2NUrOtKjfPX1sp507JtId2hsCZvlNeVNlmyK-tTeEzCVc4oNc$ ) and [here](https://urldefense.us/v3/__http://cfconventions.org/Data/cf-conventions/cf-conventions-1.9/cf-conventions.html*_rotated_pole__;Iw!!G2kpM7uM-TzIFchu!g2g_f0_WB2tm-MhehHtFacKJ7z2NUrOtKjfPX1sp507JtId2hsCZvlNeVNlmyK-tTeEzAiFtJ4M$ ). -- 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/342*issuecomment-940075309__;Iw!!G2kpM7uM-TzIFchu!g2g_f0_WB2tm-MhehHtFacKJ7z2NUrOtKjfPX1sp507JtId2hsCZvlNeVNlmyK-tTeEzZQfv8hY$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] What is meant by "original data" in the definition of the "source" attribute? (#341)
@graybeal , @taylor13 : thank you for those comments. The idea of the "immediately prior source" certainly makes sense, but it may be undesirable if taken literally. For instance, global climate simulations which are distributed for global data exchange will, before being distributed, we rewritten using the CMOR package. CMOR provides a library of routines, which will are designed to be integrated into the workflows of the various modeling centres, so that the software producing the data files is generally some internal software package with a name that means nothing to people outside the institution. We take the "immediate prior source" suggested by Jim to refer to the generation of information content in the data by the global climate model, but this approach runs into ambiguity when the whole range of post-processing options is considered. Hence, I can also see some benefits from the more flexible approach suggested by Karl. Could we encourage flexibility by allowing multiple source elements, e.g. `MOHC-HadGEM2-ES WRF MyCropModel` ? -- 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/341*issuecomment-940031779__;Iw!!G2kpM7uM-TzIFchu!m2xqI5SBee9B-vPxqEsBmkhn5Eq98x-_SPmiT172l3qqxuOTrtBa2BpS6CTtKTovbkhUSLglmUE$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Clarification of requirements on calendar attribute of a bounds variable (#265)
Hi all, I'm still re-assimilating what went on here, but it occurs to me that allowing data type equivalence (rather than equality) is problematic: * The `missing_value` and `_FillValue` (and the `valid_*` attributes) must be of the same data type as the data to which they apply, so if they these attributes are inherited, then the bounds must be of the same data type. * If the bounds are strings and the coordinates chars, then the bounds will _not_ have the extra dimension, as is currently required: "_A boundary variable will have one more dimension than its associated coordinate or auxiliary coordinate variable._". (This is easily dealt with via a caveat, of course.) * Although most software does support type casting, it is not always done in the same way (for example, in Python the default type casting rules of numpy have recently changed), and even if it is done as expected, the recast numbers may produce undesired results in ways that may be hard to detect. Thanks, David -- 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/265*issuecomment-939966466__;Iw!!G2kpM7uM-TzIFchu!hnUIyIO55kD9aTWBt8vQMiLX4Cc2aQHed6RzK22VzsJrxhE9viK8P6udDYy8tmspEpQy0b7NHUE$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Updating definition of coordinate variable to account for NUG changes (#174)
Hi @martinjuckes, Yes, of course! I notice that my offer came just before everything changed last year, so I guess it got lost in the noise. I shall remind myself of the discussion thus far and post a summary. Thanks, David -- 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/174*issuecomment-939944090__;Iw!!G2kpM7uM-TzIFchu!lA0uC_ahYyP_4gf0w9sr7fBclzvsGo-aKAqE372FF1-xW5Wbx8buVEYw1n_B_0DnMJdPulQJsy4$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
