Hi @davidhassell and @JonathanGregory, > As @JonathanGregory says, this is no problem. I don't think that this needs > special mention, as this is has always been true of all types of variables.
>From a user point of view and for the ease of discovering the domains, it >would appear attractive if: - there is only one domain variable per domain - if domain variables are used in the file, all domains must have a domain variable It would also support better the use case stated by @oceandatalab for accessing coordinate variables without accessing data variables under [Standard way to define subsampled coordinates #37](https://github.com/cf-convention/discuss/issues/37). For other data variables, we do need to permit multiple instances for things to work, and cannot excluded that some of these are copies of each other. If there is no similar need for permitting copies of domain variables, I guess it would be cleaner and more beneficial not to permit copies. -- 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-700029519 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].
