This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#104: Clarify the interpretation of scalar coordinate variables -----------------------------+---------------------------------------------- Reporter: jonathan | Owner: [email protected] Type: defect | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by davidhassell): Replying to [comment:4 edward.campbell]: Dear Ed, Thank you for posting on our proposal. This view is, of course, not unexpected. However, to move things on from the current area of discussion on this point (on this ticket and elsewhere), I suggest that it would be useful if you, or anyone, could post some examples of software libraries which by design interpret, read or write CF-netCDF datasets in the manner in which suggest. This would give us some evidence for or against your assertions about the reinterpretation of existing datasets, and how widespread this practice may be. I don't know of any, but I'm the first to admit that I'm familiar with only a small fraction of what is out there. > If the dimensions are not specified one cannot currently infer independence. Put another way, > without a dimension (a direction if you like) these are true scalars as opposed to unit > vectors. Your proposed change will impose a single interpretation of existing data where a > single interpretation does not currently exist. That in my view constitutes a material change. I don't agree with your 'direction' analogy. Scalar coordinates are often endowed with a direction, via some combination of their `positive` property, their `units` property and their bounds' values. So I would say that they are indeed logically equivalent to unit vectors. All the best, David -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/104#comment:5> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
