Dear Jonathan, thanks for that useful review. I have to agree with the observation that this discussion has broadened beyond what is considered acceptable for a `defect` .. so I'm happy for it to be relabelled as an `enhancement`.
I agree with your view that `string X(X)` should not be allowed, and, I also believe that `char X(X)` should not be allowed for the same reason. Was your reference to a "string variable" above intended to cover both `string` and `char`? I like the idea of using the phrase **"dimension coordinate variable"**. I would, however, like to be able to use the phrase "coordinate variable" to refer to any kind of coordinate variable (i.e. either "dimension" or "auxiliary"). The concept of a "generic coordinate variable" may make sense as an abstract base class in the data model, but it I don't think it makes much sense here; a coordinate variable in a CF NetCDF file must be either a dimension coordinate variable or an auxiliary coordinate variable. -- 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/174#issuecomment-595101927 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].
