[snip]
> Practical limitations may come from the variety of time axis definitions
> (usage of different calendars etc). Right now I believe, udunits
> supports only one kind of calendar. Applications such as GrADS assume
> that the time information is always written using a standard calendar.
> This could give rise to problems when for example using a NetCDF file
> that writes time in terms of a 360 day calendar for example.
[snip]
If anyone is aware of robust, portable calendar software
[C/Fortran/.../NCL] that supports any or all CF netCDF calendars:
gregorian, standard, proleptic_gregorian, noleap, 365_day,
all_leap, 366_day, 360_day, julian calendars, we would like
to look at it. :-)
Incidently, when creating time with units "hours/days since ..."
regardless of calendar, I suggest that *auxiliary time variables*
be created.
time .... "days since ..."
auxilary time variable [like CCSM]
date .... for whatever calendar is being used
eg: yyyymmdd
datesec .... secends of the day
D
_______________________________________________
ncl-talk mailing list
ncl-talk_at_ucar.edu
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Fri Oct 13 2006 - 08:09:14 MDT
This archive was generated by hypermail 2.2.0 : Fri Oct 13 2006 - 10:37:11 MDT