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/.
#79: Handling and formatting of vector quantities in CF
-----------------------------+----------------------------------------------
Reporter: lavergne | Owner: cf-conventi...@lists.llnl.gov
Type: enhancement | Status: reopened
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords: vector
-----------------------------+----------------------------------------------
Comment (by lavergne):
Mark,
Replying to [comment:65 markh]:
> Replying to [comment:64 lavergne]:
>
>
> > I do not really see where (or how) to put a "break" and conclude. Do
we have to reach 100% agreement? or have some voices more weight than
others? How to we take the final decision in such a ticket?
>
> My view is that we need to reach a consensus on what represents a good
enough solution, without any strong objections to the approach left
outstanding.
>
> I feel that there is a good case for adding extra structure to this
proposal, in order to meet a set of use cases which we have for specifying
and working with vector quantities.
Let's discuss it a bit further, then:
Does the problem with the "simple" solution boil down to the standard
names being cumbersome to parse by a machine (like sea_ice_x_velocity,
u_wind, etc...) ?
If yes, I argue the "component" attribute as you propose are a way around
an issue with the standard name table. I do not say it rules your approach
out, but are we introducing the components attributes because we cannot
practically change the standard names?
Now imagine the standard names were "easy" to parse, and it was thus easy
to decide if a variable was a "x", or a "direction" would there be
anything missing from the "simple" implementation?
Cheers,
Thomas
--
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/79#comment:66>
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
"majord...@lists.llnl.gov" with "unsubscribe cf-metadata" in the body of your
message.
