As far as I can tell there is an implicit restriction on the use of spaces, as the `ancillary_variables` attribute (and other attributes as well) uses a space separated list of variable names. That said, I think that restricting the names of variables to names that can be used as a variable name in (most) programming languages makes sense. In a regex expression: '[A-Za-z][A-Za-z0-9_]*', in words: start with a letter (upper- or lowercase), then zero or more letters, numbers or underscores. Note that the underscore is excluded at the start of a name here.
To indicate a unit, as in your example, the appropriate attribute should be used, CF provides the mechanisms for that. It is also a usability issue, as some characters may be hard to type, or be easy to confuse with characters in this range (o or ο, spot the difference). -- 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/307#issuecomment-727929206 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].
