Hi Chris et al.,
indeed it seems like some clarification is necessary about the use of
different calendars in modelling. Your suggestion to "map" the 360 day calendar
onto the Gregorian calendar in output files won't work: there would be no need
for a 360 day calendar if it would. The idea
For those who have never encountered a non-standard calendar in the wild,
here's one place they show up:
360-day and 365-day calendars are used in climate modeling. It requires a lot
of extra work to write code that can handle leap years by making the year
length variable, and the payoff for doin
On 3/31/11 12:42 AM, Lowry, Roy K. wrote:
Dear All,
This debate between Chris and Benno hinges upon how one determines the sampling
interval for a time series. Benno depends upon semantics encoded in the units
of measure field - something I have done in the past although I am now
convinced t
Hi John,
We label Units of Measure with a URI (e.g. SDN:P061::ULAA represents metres),
which represents a term in the P061 vocabulary
(http://vocab.ndg.nerc.ac.uk/P061/list/current). The vocab (born in the late
70s) is a work of pragmatism that contains a mixture of 'dimensional units'
plus 'p
udunits is a "dimensional units" library, for manipulating powers of the
fundamental dimensions (length, mass, time, charge, temperature). this
is necessary but not complete for capturing the meaning of the "physical
units" of our data.
We also need units like kg/kg, for which the udunit canon
Dear All,
This debate between Chris and Benno hinges upon how one determines the sampling
interval for a time series. Benno depends upon semantics encoded in the units
of measure field - something I have done in the past although I am now
convinced that it is not best practice. Chris advocate
