Dear Jim Thanks for this text. I prefer the first version, since (as previously stated) I don't think `string x(x)` should be allowed as a dimension coordinate variable. Perhaps you could consider the following text from Hassell et al. (2017, https://doi.org/10.5194/gmd-10-4619-2017):
> NetCDF coordinate variables (in the NUG sense) supply the independent > variables on which the data depend. Coordinate variables must be numeric and > strictly monotonic, so that each element has a unique value. > CF also defines "auxiliary coordinate variables" to provide mandatory or > optional coordinate information which is additional or alternative to that > contained in the coordinate variables in the NUG sense. Auxiliary coordinate > variables can be string valued, may contain missing values, and are not > necessarily monotonic. You have "A one-dimensional auxiliary coordinate variable shall not have the same name as its dimension." That's a new requirement, but it's backwards compatible because it's already the case. I assume we also retain the existing recommendation, "that the name of a multidimensional [auxiliary] coordinate variable should not match the name of *any* of its dimensions." Where do you think this text would go in the document? Cheers Jonathan -- 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-597636202 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].
