Hi @oceandatalab, Thank you describing your use case that would be benefited by a domain variable.
> Does it mean that when a domain construct is part of a field construct it has > to be stored exclusively via attributes (as it is done with the current > conventions) or is it possible to also have a reference to a domain variable? I am proposing that domain variable references should not be allowed from a data variable. This is to preserve backwards compatibility and to avoid redundancy ([in the senses of design principles 10 and 6](https://github.com/cf-convention/cf-conventions/issues/273#issuecomment-656724527)). We must be careful not to confuse CF data model constructs with netCDF variables - the data model has been designed to be independent of the netCDF encoding. In the modified data mode proposed here, a field construct may contain a domain construct, but that in no way forces the netCDF representation of the field construct to contain an explicit reference to a domain variable. Thanks, David -- 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/301#issuecomment-708304209 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].
