@martinjuckes wrote: > Do you acknowledge that the current convention, and version 1.0, contain the > statement that a coordinate variable " is defined as a numeric data type", > and that this would appear to rule out string coordinate variables?
Yes, absolutely. The language in versions of CF developed before the string datatype was available did not envision string dimension coordinate variables and did exclude char dimension coordinate variables. > Can I interpret the fact that you have not addressed the question about > applications as an admission that your definition cannot be converted into a > logical algorithm which can be run in applications? Not at all. In fact, I claim the exact opposite. I claim that the text as I wrote it is easily used by people to write software to create coordinate variables in netCDF files and software to read netCDF files and find 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-598410301 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].
