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. However, a units attribute specifying a dimensionless
unit may optionally be included."
Indeed, if you run your file through the CF-checker, there are no
warnings or errors, only informational messages:
Checking variable: site_code
------------------
------------------
Checking variable: site_lon
------------------
------------------
Checking variable: procParams
------------------
INFO (3.1): No units attribute set. Please consider adding a units
attribute for completeness.
Thanks,
Rich
On Wed, May 18, 2011 at 3:10 PM, Christopher Mueller
<cmueller at asascience.com> wrote:
> 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"
> unit. ?For example:
> For the dataset here:
> ?http://hfrnet.ucsd.edu:8080/thredds/dodsC/HFRNet/USEGC/6km/hourly/RTV
> The "site_code" is missing a "units" attribute ? but I'm stumped as to what
> it should be. ?Another example in the same dataset is the "procParams"
> variable.
> The nearest "solution" I could decipher is to assign the "units = 1", but
> that seems less than proper as that unit is (I believe) supposed to be
> reserved for fractions and the like.
>
> Any thoughts/solutions someone might have would be much appreciated.
> Best,
> Chris
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
>
--
Dr. Richard P. Signell?? (508) 457-2229
USGS, 384 Woods Hole Rd.
Woods Hole, MA 02543-1598
Received on Wed May 18 2011 - 13:22:37 BST
