Hi @davidhassell : thanks. There is a use case for providing attributes on bounds variables in the Trac ticket which you cited ([140](https://cf-trac.llnl.gov/trac/ticket/140)) : @taylor13 describes a usage where the user needs to know the `units` of the bounds variable and does not make use of the parent coordinate variable. However, the more important point, I think, is that the status quo is clearly that use of these attributes on the bounds variables is clearly deprecated and not forbidden. Changing that would, as you say, be a discussion for another issue.
@JonathanGregory , @taylor13 : can you help with the interpretation of the intention of the discussion in [Trac 140](https://cf-trac.llnl.gov/trac/ticket/140) on the precise rule for `calendar` attributes on bounds variables? In particular, if a variable has `calendar = noleap`, would `calendar = 365_day` on the bounds be: - (A) deprecated as being the same but redundant or - (B) forbidden as being a different string (not exactly the same, even though it has exactly the same meaning)? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/265#issuecomment-627193357 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].
