First of all, let me say that I don't think this is an issue. The variable data seems to be the same! However, the differing time axis attributes—and/or maybe something else causing YEAR to not be parsed by ncdump—did confuse me for a while, so it might be worth considering making these consistent.
In the CLM flanduse_timeseries file, the YEAR variable is the actual year.
f=/glade/campaign/cesm/cesmdata/cseg/inputdata/lnd/clm2/surfdata_esmf/ctsm5.2.0/landuse.timeseries_0.9x1.25_SSP2-4.5_1850-2100_78pfts_c240216.nc
ncdump -h $f | grep time | grep -v time,; ncdump -v YEAR $f | tail
First of all, let me say that I don't think this is an issue. The variable data seems to be the same! However, the differing time axis attributes—and/or maybe something else causing
YEAR
to not be parsed byncdump
—did confuse me for a while, so it might be worth considering making these consistent.In the CLM
flanduse_timeseries
file, theYEAR
variable is the actual year.However, in the FATES
fluh_timeseries
file it's more complicated. This can't be inspected usingncdump
for some reason:However,
xarray
can see it if you tell it not to decode times: