@JimBiardCics : for completeness I'd like to note that in addition to Jonathan and myself, Karl has expressed opposition to accepting string valued dimension coordinate variables (repeatedly), and David has expressed reservations.
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? You are right in observing that we are talking past each other .. thank you for acknowledging that. I'm puzzled by your confidence that "anyone given that text" could work out which variables in a file were coordinate variables. My objection, I'd like to remind you, was that both applications and users need to be able to identify 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? A tutorial is not good, we need a coherent set of logical rules. -- 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-598363518 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
