use the attribute "modulus" where Ferret uses "modulo". For example, the above
.das shows this for the time axis
T {
String long_name "Time";
Float32 modulus 12.;
Float32 pointwidth 1.;
String calendar "360";
Int32 gridtype 1;
String units "months since 1960-01-01";
}
Add modulus as an alternative to modulo in cd_get_1_axis.F. We already have the
ability to take an modulo length which is saved in a variable line_modulo_len.
Check to see if there's some sanity-checking on the value, or if some is needed
for these time axes.
Also, the CF standard defines an attribute called "climatology". In its
definition, this points to a "climatology variable" which defines the cell
bounds of the variable. The bounds seems like overdoing it, and is not
generally consistent with Ferret's use of t0=1-jan=0001 to indicate
climatologies. Does it make sense to recognize "climatology" as an equivalent
to "modulo" for a time axis, and ignore any climatology_bounds variable that the
attribute points to?
Reported by @AnsleyManke on 6 Jan 2006 21:04 UTC Files such as http://ingrid.ldeo.columbia.edu/SOURCES/.SOC/.GASC97/dods/.das
use the attribute "modulus" where Ferret uses "modulo". For example, the above .das shows this for the time axis
Add modulus as an alternative to modulo in cd_get_1_axis.F. We already have the ability to take an modulo length which is saved in a variable line_modulo_len. Check to see if there's some sanity-checking on the value, or if some is needed for these time axes.
Also, the CF standard defines an attribute called "climatology". In its definition, this points to a "climatology variable" which defines the cell bounds of the variable. The bounds seems like overdoing it, and is not generally consistent with Ferret's use of t0=1-jan=0001 to indicate climatologies. Does it make sense to recognize "climatology" as an equivalent to "modulo" for a time axis, and ignore any climatology_bounds variable that the attribute points to?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1375