nterval over which the quantity is
integrated. I'll leave the addition of these quantities to communities
that actually use them, IASI on MetOp comes to mind.
Kind regards,
Maarten Sneep
--
KNMI
E: maarten.sn...@knmi.nl
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
questioning the
wisdom of including 'solar' in the name. I'm flexible, and a less
specific name is fine with me.
Do I need to take different actions to start the process?
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
_
nt zenith
angle, azimuth angles) to a variable that needs this.
My earlier comments on units and coordinate variables apply to this
name also. If necessary, we can start a new thread on the mailing
list to discuss the coordinate issue more thoroughly.
Some dis
her
1024x1024, etc ?
Probably not in UDUnits, but there is a different name for those
"slightly more than 1000, but let's treat it as 'kilo' anyway" units.
more info on http://en.wikipedia.org/wiki/Kibibyte
Best,
Maarten
s. Molecules and photons
are an exception in my view because there are large datasets out there
that use explicit molecules and photons for these 'things'.
Best,
Maarten Sneep
[1] https://what-if.xkcd.com/4/
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
only
serve to hinder the transition.
Kind regards,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
significantly. It would be good to help the transition from photons to
mol (photons) as well, which was a request that started this whole
discussion in the first place.
Does this make the argument clearer?
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
__
pecified on the interfaces rather than on the layers
themselves, ans where a coordinate variable doesn't provide the detail
we need?
Kind regards,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metada
ce. I can see why he hesitates
to use this method, but I think this is indeed the way forward.
Kind regards,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
On 19-02-15 18:56, Jim Biard wrote:
Maarten,
It would, instead be something like this:
dimensions:
lon = 360;
lat = 180;
layer = 18;
vertices = 2;
variables:
float lat(lat);
lat:long_name = "latitude";
lat:units = "degrees_north";
lat:bounds = "lat_bnds";
floa
ad is there, but at least it is a lot
smaller. For irregular grids, this overhead is large, and adds variables
no user will ever need. I'll think if I can think of a neat solution
that can be used in CF2.
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
_
where a 3D dummy variable is needed.
And perhaps CF 2.0 is an opportunity to address this.
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
r commas (if a convention name
contains blanks).
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
k out when the observation was
taken with the detail they require.
Oh, funny reference for the discussion: http://xkcd.com/1514/
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
noticed that the status of this proposal is still "Active (not on list or
rejected)". Shouldn't ehy have been marked "Under discussion" by now?
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
atmosphere. For the content between specified levels in the atmosphere, standard
names including "content_of_atmosphere_layer" are used. The construction
"atmosphere_mole_content_of_X" means the vertically integrated number of moles of X
above a unit area. The chemical formula
ory of these quantities in the standard name list.
Can someone advise how to proceed?
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
On 10/07/15 15:31, Maarten Sneep wrote:
Hi,
Below are a few quantities that I'd like to define standard_name values for.
Both the
structure of the names, and the elements in the descriptions are taken from
existing
standard_name values. Point of contention may be the definition of water
On 07/08/15 21:15, Nan Galbraith wrote:
Hi All, and happy Friday.
It's been almost a month since Maarten Sneep posted 'A few definitions seem off'
and there have been just a couple of replies.
Can we please add definitions for albedo and air_pressure to the standard names
t
27;ll let others assemble a full description for
the standard_name list.
Best,
Maarten
On 8/20/15 1:22 PM, Maarten Sneep wrote:
On 10/08/15 19:37, Maarten Sneep wrote:
On 07/08/15 21:15, Nan Galbraith wrote:
Hi All, and happy Friday.
It's been almost a month since Maarten Sneep pos
Hi,
I have the following 5 new standard_name values for you to consider. I'm sure that
the unfinished business of 'albedo' will come back to bite me here.
Best,
Maarten
Name: uv_aerosol_index
Description: UV means ultraviolet radiation. The UV-Aerosol Index is a UV colour
index that repre
the
opposite. What do you suggest? cloud_albedo_assuming_full_cloud_cover
Name: cloud_optical_centroid_pressure_assuming_cloud_area_fraction_of_1
Earlier comments apply.
Which combined leads me to:
air_pressure_at_cloud_optical_centroid_assuming_full_cloud_cover
Best,
Maarten Sneep
will be useful in future to
have a phrase for this, which we currently lack, as you say.
I'm not a native speaker, so I don't think I'm the one to pass judgement on matters
of the English language. "assuming_complete_cloud_cover" has my slight preference.
Best,
Maart
On 01/10/15 13:44, Andreas Hilboll wrote:
On 01.10.2015 13:14, Maarten Sneep wrote:
On 30/09/15 23:33, Jonathan Gregory wrote:
There is one issue left: the two wavelengths used in the derivation of
the 'residue' (older, even more vague name than
ultraviolet_aerosol_index) must
nds fine to me), but because of the correspondence with
assuming_clear_sky. But others may disagree.
If there are no replies in a week or so, we'll go with
assuming_completely_cloudy_sky
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
de scalar coordinate
variables with standard names of "relative_humidity" and "air_temperature". The
specification of a physical process by the phrase due_to_process means that the
quantity named is a single term in a sum of terms which together compose the general
quantity n
es look fine to me.
OK.
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
ficient, but neither are memory leaks deep in netCDF.
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
cuments/level-2-products
http://www.tropomi.eu/science/level-2-products
(the first link contains documentation, the second has (pre-launch) sample
products).
Best,
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
ween specified levels in the atmosphere, standard
names including "content_of_atmosphere_layer" are used. The construction
"atmosphere_mole_content_of_X" means the vertically integrated number of moles
of X
above a unit area. The chemical formula for nitro
benefit most
from the L1B structure. See http://www.tropomi.eu/data-products/level-1
specifically
the IODS. There will be an update of this document, related specifically to the
references.
Kind regards,
Maarten Sneep
>> -Original Message-
>> From: CF-metadata [mailto:cf-met
uld I duplicate the signal metadata such as unit here?
>>
>> The group structure is helpful, because its structure improves
>> self-descriptiveness, I feel. I guess the structure is also a form of
>> metadata. But
>> perhaps it is considered out-of-scope for the CF conventions?
>>
>>
>> Best,
>>
>> Erik
>>
>>
>
Maarten Sneep
--
KNMI
T: 030 2206747
E: maarten.sn...@knmi.nl
R: A2.14
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Hi,
I haven't heard anything after sending this in. Can these names be considered
for
inclusion in the standard_name list?
Kind regards,
Maarten Sneep
On 23/02/18 15:04, Maarten Sneep wrote:
> Hi,
>
> I'd like to propose the following standard names:
>
> * atmospher
"containing_18O" is for H_2(18-O).
That modification is fine with me if the CMIP6 proposal gets through. If that
proposal gets through with modifications, then I prefer to be consistent with
those
modifications as well.
Kind regards,
Maarten
>
> From
34 matches
Mail list logo
