Dear all,
once again I haven't followed the entire discussion carefully, but I sense
there is more to the problem than what has been discussed so far:
1) if we define the meaning of "time" as a specific datetime instance on a
given calendar, then all time values along a trajectory should in
Sorry, I was not clear, I think. I was proposing
time(reftime,leadtime)
time:standard_name="time";
time:units = "days since 1970-01-01 00:00:00";
a 2D variable which gives the actual time corresponding to each reftime,
leadtime pair -- it can be computed as the unit-corrected sum of reftime and
Hi all,
I'm wondering if someone can help me sort out the most proper way to handle
something. I'm processing some datasets and validating them for CF compliance
using the CF Checker and I'm running into a problem with variables that are NOT
dimensionless, but still really don't have a "valid"
Dear Chris,
Do you have the latest version of the checker? Is the behavior you're
seeing consistent with what is stated in the email copied below?
regards,
Karl
email from 3/1/11
Dear All,
I've made a couple of fixes to the CF checker:
1) If the variable is deemed unitless, then the checke
Chris,
I took a look at
http://hfrnet.ucsd.edu:8080/thredds/dodsC/HFRNet/USEGC/6km/hourly/RTV.html
I agree that "site_code" should not have units.
The CF document states: "Units are not required for dimensionless
quantities. A variable with no units attribute is assumed to be
dimensionless. Howeve
Karl (also verified by Rich) - thanks for the replies. I was using the
previous release of the cf-checker which throws errors rather than ignoring
and/or reporting as "info".
Thanks!!
Chris
From: Karl Taylor mailto:taylo...@llnl.gov>>
Date: Wed, 18 May 2011 15:21:18 -0400
To: "cf-metadata@cgd
