Hi Cecelia:
Thanks for this information. A few questions:
* So you are not supporting standard Gregorian calendar even though
thats the CF default?
* Do modelers need to match historical dates? If so, what calendar do
they use?
* Is the time library suitable to be released seperate from
Hi John and all,
Thanks for this information. A few questions:
* So you are not supporting standard Gregorian calendar even though
thats the CF default?
Correct, the climate modelers that we work with don't use it. AFAIK the
decision of
CESM was to reject the CF default as unreasonable for
John
There is some meteorological data that is available pre-Gregorian
calendar (paleo data, some temperature datasets) and of course there are
other scientific fields where data is pre-1500 (e.g. astronomy,
archeology) . Given that netCDF files with data dates spanning ~1550 probably
already
Hi Cathy:
There no question that CF currently defaults to mixed gregorian
calendar. The discussion is whether thats the best choice (probably
not), and to advise users not to cross the discontinuity (eg store
modern dates starting from 1-1-1).
Im curious as to how you generate the dates
On 12/6/2012 4:09 PM, John Caron wrote:
Hi Cathy:
There no question that CF currently defaults to mixed gregorian
calendar. The discussion is whether thats the best choice (probably
not), and to advise users not to cross the discontinuity (eg store
modern dates starting from 1-1-1).
Im
In the last 2 years alone, I've encountered a number of datasets ranging
from reanalysis to climatologies to current ocean models that do utilize
date from 1-1-1. While I agree that ISO8601 is probably a better system,
it's not the one a lot of applications used when they were written. I think
