Hi , Nancy and I looked at this and it turns out that the file uses an
INT64 data type to store the time coordinates. That's very
slightly non-standard, as INT64 is a type not listed in the CF
standard. We will be able to add it to the types that PyFerret
(and Ferret) recognizes. That will be in a future PyFerret
release. Meanwhile, we can redefine the time axis within the PyFerret
session, so PyFerret will write it out ok, and without changing
any of the time information. DEFINE AXIS/LIKE= gets the time
origin and units from the original axis and t[gt=time] will use
the same coordinates. It just makes it a Ferret-defined axis
rather than an axis from the file. yes? define axis/t/like=time time = t[gt=time] There may be more lines of ***NOTE as the definition of the axis
"time" from the file is being changed for all of the grids in the
file. Again this is happening just in the session, making new
definition of what PyFerret is going to use for the time axis of
the variable. -Ansley
On 11/28/2018 9:47 AM, Nancy Williams -
NOAA Affiliate wrote:
Hello All, |