Dear Patrick, Thank you for bringing up "location index set" variables. I agree that in the absence of the `cf_role` attribute it is not always possible to distinguish one from data variable, so I would be happy with retaining it on these variables.
By extension, I think that we should drop the suggestion (it is just that at this stage) of removing `cf_role` from the mesh topology variable. This is because a location index set variable is logically identical to a mash variable, so having a common mechanism of identification would be nice. > ( This problem is entirely analogous to an existing problem with > auxiliary-coordinates in standard CF : If the data-variable which references > them is removed, then they are not distinguishable from data-variables -- so > they "become" data-variables ) I wouldn't call this a problem, rather a feature! When we read a dataset, we tend to not cast variables that have been identified as auxiliary coordinates (or other roles) as data variables _as well_, but that is only a default behaviour that is what most of want most of the time. All the best, David -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/153*issuecomment-872289997__;Iw!!G2kpM7uM-TzIFchu!m3MvmAJbcTaPU6Ztlb1aEbCnoUt3-uDR3R1pG6HQ9fufA_aTTj_7DV37GTYArWT6nxp6IECmCAg$ 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].
