Custom Query (124 matches)

Following a suggestion of Aaron Sweeney, I propose that this sentence in the first paragraph of Sect 3.3 should be amended:

"For some applications it would be desirable to have a more definitive description of the quantity, which would allow users of data from different sources to determine whether quantities were in fact comparable."

to read

"For some applications it would be desirable to have a more definitive description of the quantity, which would allow users of data from different sources (some of which might be models and others observational) to determine whether quantities were in fact comparable."

Since this is a defect ticket, which aims to clarify the convention but not to alter it in meaning, it will be accepted by default unless there is an objection or alternative suggestion.

Jonathan

In order to specify the character set of char and string variables, I propose that we append these two paragraphs to the end of CF section 2.2:

Each char array variable that is to be interpreted as an array of individual characters (not string(s)) must have a "charset" attribute which clarifies that the variable is to be interpreted as individual characters (not string(s)) and specifies the 8-bit character set used by the chars. Values for "charset" are case-insensitive. See ​http://www.iana.org/assignments/character-sets/character-sets.xhtml . Currently, the only values allowed for "charset" are "ISO-8859-1" and "ISO-8859-15". A scalar char variable may also use the "charset" attribute, which defaults to "ISO-8859-15" if it is not specified.

A string or string array variable (including a char array variable that is to be interpreted as a string or array of strings) may have an "_Encoding" attribute. Alternatively, a file may have a global "_Encoding" attribute which applies to all strings (scalar and array) in the file. Values for "_Encoding" are case-insensitive. See ​http://www.iana.org/assignments/character-sets/character-sets.xhtml . Currently, the only values allowed for "_Encoding" are "ISO-8859-1", "ISO-8859-15" and "UTF-8". A missing "_Encoding" attribute defaults to "UTF-8".

(This 2017-03-02b version is the consensus revised proposal from Chris Barker, Heiko Klein, and Bob Simons, with further changes requested by Jonathon Gregory.)

1. Title

New cell_method 'count over days'

2. Moderator

Jonathan Gregory

3. Proposing

New entry for table E.1. Cell Methods:

name='count over days' Units=1 description='the number of occurences of a condition specified in the standard name'

The Units are Integer.

4.Use Cases

For statistic indices we like to add the following new standard_names:

number_of_days_with_air_temperature_below_threshold

examples:

frost_days min<0 degC = fd (IPCC AR4 and AR5)

ice days max<0 degC

frost days where no snow

number_of_days_with_air_temperature_above_threshold examples:

summer days max>25 degC

tropical nights min>20 degC

number_of_days_with_lwe_thickness_of_precipitation_amount_above_threshold

examples:

heavy precipitation >10 mm = r10 (IPCC AR4 and AR5)

very heavy precipitation >20 mm

wet days > 1mm

number_of_days_with_wind_speed_above_threshold

examples:

strong breeze days max > 10,5 m/s

strong gale days max > 20,5 m/s

hurricane days max > 32,5 m/s

To specify the standard_name the CDLs should have the following form:

/* number of days with daily minimum below 0 degC = frost_days = fd (IPCC AR4 and AR5) */ float n1(lat,lon);

n1:standard_name="number_of_days_with_temperature_below_threshold"; n1:coordinates="threshold time"; n1:cell_methods="time: count over days";

float threshold;

threshold:standard_name="air_temperature"; threshold:units="degC"; threshold:cell_methods="time: minimun within days"

data:

threshold=0.;

Best regards Heinke