Dear all,
We are considering how best to store data produced by some computation where
there has to be a distinction between missing input data (i.e. no input data
available) and "not occurring" (i.e. input data exists but the computation did
not result in a valid numeric value).
In practice,
Dear Robert, Alison,
Having not much previous experience of a KWIC index I had a quick look at the
web page. And my impression is that it would be very useful when looking for
already existing standard names, and even more useful when constructing new
ones based on existing patterns.
I think
l [david.hass...@ncas.ac.uk]
Skickat: den 27 mars 2019 15:22
Till: Bärring Lars
Kopia: cf-metadata@cgd.ucar.edu
Ämne: Re: [CF-metadata] same attribute name in variable and in global
Hi Lars,
Thanks for bringing this up. Here is the background, as I understand it, to the
data model description of
Dear all,
I have come across many CMIP5 files that have the same attribute [name]
attached to the data variable as found in the globals.
In particular it seems that CMOR was writing variable processing history
attached to the variable, and more general file processing in the global
history.
Hello Martin,
Thanks for the response, the Zenodo guide document is really helpful!
/Lars
Från: Martin Juckes - UKRI STFC [martin.juc...@stfc.ac.uk]
Skickat: den 28 januari 2019 12:57
Till: Bärring Lars; cf-metadata@cgd.ucar.edu
Ämne: Re: Two [simple
Nan ---
Just to better understand your setup: the data you are referring to comes from
a totalizer rain gauge, where the data may look like
day i, 321 mm
day j, 321 mm
day k, 333 mm
day l, 333 mm
day k, 399 mm
and this is what you record , and store?
/Lars
Dear all,
Two simple questions of understanding:
1. If I have (observed) daily precipitation with unit mm/day and want to store
this in a CF compliant file, should I use standard name
--- "lwe_thickness_of_precipitation_amount" with canonical unit metre and the
"per day" part is inferred from
n Oct 19, 2018, at 5:13 AM, Bärring Lars
<mailto:lars.barr...@smhi.se> wrote:
Dear all,
I agree with Jonathan's wish for a more well-behaved Earth in the planetary
system :-)
However, awaiting this I think that we have two issues before us:
1. The fact that different datasets fundamental
is specified, time data values are
>> displayed as human-readable date-time strings rather than numerical values,
>> interpreted in terms of a `calendar' variable attribute, if specified. ...
>> Calendar attribute values interpreted with this option include the CF
>> Conventio
hich
gives 84600 seconds.
regards,
Martin
From: CF-metadata
mailto:cf-metadata-boun...@cgd.ucar.edu>> on
behalf of Bärring Lars mailto:lars.barr...@smhi.se>>
Sent: 18 October 2018 09:29:50
To: Ryan Abernathey;
whitaker.jeff...@gmail.com<mailto:whi
Hi,
I have have come to think about this from a somewhat different perspective. For
some analyses, as well as when calculating certain derived climatological
statistics (aka climate indices), using datasets based on different calendars
the problem becomes obvious.
In the model world of a
Dear Jonathan, David, Jon,
I would be in favour to changing the sum cell method to something else, as it
took me a while to grasp that "sum" is the opposite of "point". But having a
cell_method specifying "cell" as the method could very well be as confusing.
But how about "cell_total" (to
Hello Martin, David, all,
Martin raises an relevant point, even though it took me minute or two to see
the difference.
Now :"The only CF standard attribute which is allowed to refer to external
variables is cell_measures."
meaning that that only the CF standard attribute cell_measures is
distinction is needed; but if No then it may not have to be made in
the standard name. It could be recorded in a non-standardised way instead.
Best wishes
Jonathan
- Forwarded message from Bärring Lars <lars.barr...@smhi.se> -
> Date: Tue, 28 Mar 2017 15:02:02 +
> Fro
ÖPING
http://www.smhi.se
E-post / Email: lars.barr...@smhi.se
Tel / Phone: +46 (0)11 495 8604
Fax: +46 (0)11 495 8001
Besöksadress / Visiting address: Folkborgsvägen 17
-Original Message-
From: Hollis, Dan [mailto:dan.hol...@metoffice.gov.uk]
Sent: den 27 mars 2017 13
Dear all,
Several standard names oriented towards climate indices for various impacts are
based on thresholds, and the standard name includes the construct
"..._above_threshold" or "..._below_threshold". However, several
well-established climate indices use non-strict inequalities in their
Dear Jim, all,
This list is very interesting and helpful. I think that most of them if not all
are similar, in structure at least, to the ones we are working on. To what
extent you already managed to find a CF description to describe the them?
I am asking because the ones that we are working
Dear all,
Some further comments (top posting because my email reader does not easily
handle inline comments)
1. I think that it is essential to also capture the temperature threshold used
to calculate the GDD. The Wikipedia article suggests that 10 degC is most
common (or even standard), but
Dear Jon, dear all,
Many thanks for raising this issue, and for moving the discussion towards the
summary below. Indeed, it is timely to raise this issue. As it happens, within
the European IS-ENES2 project we had a small technical workshop last week
dealing with closely related issues. Among
Dear all,
Before the summer I asked in separate emails a few questions related to
standard names. Based on the responses I have worked on this a bit more and
made some good progress, but there still are some open issues that I am trying
to wrap my head around. Most of the issues are related
egory
Sent: den 23 maj 2016 15:03
To: cf-metadata@cgd.ucar.edu
Subject: [CF-metadata] clarification of standard name integral_of_Y_wrt_X
Dear Lars
Best wishes
Jonathan
- Forwarded message from Bärring Lars <lars.barr...@smhi.se> -
> Date: Mon, 23 May 2016 09:19:47 +
>
Dear all,
I am trying to find CF compliant representations of various degree-day indices
and find the standard name integral_of_air_temperature_excess_wrt_time
with the following description:
"integral_of_Y_wrt_X" means int Y dX. The data variable should have an axis for
X specifying
processing of axes in cf-trac.llnl.gov/trac/ticket/82.
Something like
time: mean within years (period: 1 month) time: mean over years time: range
might work.
Best wishes
Jonathan
- Forwarded message from Bärring Lars <lars.barr...@smhi.se> -
> Date: Fri, 13 May 2016 14:09:25 +00
Dear Jonathan,
> > But how about common continentality indices based on the annual range of
> > monthly mean temperatures?
> > Is there a "within months" such that the cell method for the basic element
> > of the continentality index would be "time: mean within months time: range
> > within
Dear Jonathan,
Thanks for these clarifications.
> > 1. Is there a standard name for "diurnal temperature range", or a combined
> > standard name/cell method representation? Cf. the 2010 mail archive thread
> > http://mailman.cgd.ucar.edu/pipermail/cf-metadata/2010/054016.html that
> > added
Dear All,
In a project we are trying to come up with CF compliant description of a range
of climate indices (aka indices of climate extremes, ...), of which most I
would believe fall under the heading "7.4 Climatological statistics". This is
not a new topic for this email list; there was an
26 matches
Mail list logo
