Hi all,
I am trying to find a standard name for a satellite product referred to as
'normalised flurorescence line height'. A description of this from the data
provider[1] is as follows:
"Fluorescence Line Height (FLH) is a relative measure of the amount of radiance
leaving the sea surface in th
Cristina,
My understanding of the conventions is that your standard names would become:
CHL: "mass_concentration_of_chlorophyll_in_sea_water"
CHL_error: "mass_concentration_of_chlorophyll_in_sea_water standard_error"
CHL_count: "mass_concentration_of_chlorophyll_in_sea_water
number_of_observation
water.
Will the latest versions of udunits recognize it?
thanks for any guidance,
Karl
On 26-Mar-10 8:52 AM, Andrew Clegg wrote:
Hi Julien,
I'm glad you brought this up. We had a discussion about this recently
(look for any threads with 'udunits 1 or 2 for CF' in the title):
http://*
mes rather than
shortened, so instead of using 'u' (which has been replaced by 'µ' in
udunits2) you would use 'micro' (which is compatible with both). However
it would be nice to get a consensus on this or another solution, and
some text added to the conventions.
Che
This seems like a good solution to me. Maybe a recommendation (rather
than a requirement) should be added that full units names & prefixes are
used, with a note mentioning that in some cases there may be
incompatibilities when using symbols.
Cheers,
Andrew Clegg
Steve Emmerson wrote:
still use udunits-1 to process the units strings, in nearly all
cases, though obviously a ununits-2 Fortran interface would be preferable.
Cheers,
Andrew Clegg
Steven Emmerson wrote:
Andrew,
The "u" prefix can be added to the UDUNITS-2 database by inserting the
line
Bruno PIGUET wrote:
Le mercredi 03 mars 2010 à 15:10 +, Andrew Clegg a écrit :
[...] In udunits1, I used 'ukg m^-3', which
udunits2 rejects as invalid. udunits2 accepts 'mg m^-3' (which is much
better!), but udunits1 interprets this as to do with gravity. Becau
Steve,
The UDUNITS-1 library had a bug in it. The bug was that "g" was
interpreted as meaning "gravity" (i.e., "standard_free_fall") rather
than "gram". This was corrected in version 1.12.10 of the UDUNITS-1
package, which was released on 2009-09-17.
The UDUNITS-2 package did not have this bug
lly compatible with
udunits...
I would guess that udunits2 is the preferred option, given that udunits1
is deprecated. Should the CF conventions be updated to specify udunits 2?
Cheers,
Andrew Clegg
Plymouth Marine Laboratory
-
