@davidhassell commented on this pull request.
> +data variable for describing a domain, with exactly the same meanings +and syntaxes, as described in <<attribute-appendix>>. If an attribute +is needed by a particular data variable to describe its domain, then +that attribute would also be needed by the equivalent domain variable. + +The dimensions of the domain must be stored with the **`dimensions`** +attribute. It is necessary to list these dimensions, rather than +inferring them from the contents of the other attributes, as it can +not be guaranteed that the referenced variables span all of the +required dimensions (as could be the case for a discrete axis, for +instance). The value of the **`dimensions`** attribute is a blank +separated list of the dimensions names. There is no restriction on the +order in which the dimensions appear in the **`dimensions`** attribute +string. The presence of a **`dimensions`** attribute will identify the +variable as a domain variable. If a domain has no dimensions then the +value of the **`dimensions`** attribute must be an empty string. Yes, it can - just provide the `dimensions` with a an empty string (`domain:dimensions = "" ;`). It still needs the `dimensions` attribute so that it is recognisable as a domain variable. Such a domain can still have scalar coordinate variables, grid mappings, etc. I mentioned that it is allowed in the conformance requirements, but I agree that it should be mentioned explicitly in the new 5.8 text. I'll propose some new words in this thread, shortly ... -- 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/pull/302#discussion_r493622754 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].
