Coordinate values have to be unique and monotonic, because they define the 
order of the elements along an axis. Strings don't have a unique way of being 
ordered monotonically. Of course we could define which order CF was to use, but 
that's an extra complexity, and it would probably go wrong sometimes, so there 
has to be a good reason for introducing and depending on it.
The usual rule in CF is that we don't add something unless there is a clear 
use-case for it. `string x(x)` and `char x(x)` are currently not allowed as a 
coordinate variables or auxiliary coordinate variables. Is there a circumstance 
where they are needed? No-one has asked for them up to now. I continue to think 
that we should disallow them as coordinate variables, because of the problem 
with monotonicity, and as auxiliary coordinate variables because they look like 
coordinate variables.

-- 
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-595879363

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].

Reply via email to