Just FYI, the UDUNITS-2 package accepts ISO 8601-compliant timestamps like
the following:
2016-01-01T05:04:03-0600
2016-01-01T05:04:03Z
Regards,
Steve Emmerson
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
Chris,
That's a completely valid suggestion. We have to consider implications
for backwards compatibility. Among other things, UDUNITS would need to
change their convention, since CF follows UDUNITS in this matter, as
with all other units. There's nothing that says we can't make changes. I
Jim and Chris B,
I would like to weigh in here, please?
Adhering to UDUnits has merits, but once one adopts ISO8601-like notations, as
there is no way of specifying otherwise, people assume it *is* ISO8601 and
therefore a string without a time zone marker indicates local time (whatever
that
