@dblodgett-usgs commented on this pull request.
> + +A data variable defines its domain via its own attributes, but a +domain variable provides the description of a domain in the absence of +any data values. It is of arbitrary type since it contains no data. It +acts as a container for the attributes that define the domain. The +purpose of a domain variable is to provide domain information to +applications that have no need of data values at the domain's +locations, thus removing any ambiguity when retrieving a domain from a +dataset. Ancillary variables and cell methods are not part of the +domain, because they are only defined in relation to data values. + +The domain variable supports the same attributes as are allowed on a +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. Having domain variables adopt from field variables in this way may become problematic. I think this is probably the right -- pragmatic -- approach for now, but we need to be careful with sweeping statements like is made here. -- 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#pullrequestreview-494651324 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].
