[gradsusr] Time: confused between grid vs. world coordinates
gilles.delaygue at univ-grenoble-alpes.fr
Tue Jul 16 08:06:19 EDT 2019
Thanks again for your explanations.
This is a bit off topic, but which ‘other tools which deal with time axis metadata’ do you know?
All the best, gilles
> On 16 Jul 2019, at 13:06, Jennifer M Adams <jadams21 at gmu.edu> wrote:
> The requirement of a linear time axis is a strong contributor to the fast performace of GrADS. If this constraint is incompatible with your needs, there are other tools that will take the time to read all the time axis metadata and deal with it accordingly.
> The documentation for TDEF (http://cola.gmu.edu/grads/gadoc/descriptorfile.html#TDEF) says, "The method by which times are assigned to T grid points is always LINEAR.”
>> On Jul 16, 2019, at 1:45 AM, gilles delaygue <gilles.delaygue at univ-grenoble-alpes.fr> wrote:
>> Thanks for your answer, and solution. Do you know whether this (strong) limitation of GrADS on the time axis is documented anywhere?
>> With my best regards, gilles
>>> On 11 Jul 2019, at 14:01, Adams, Jennifer M. (GSFC-610.2)[ADNET SYSTEMS INC] <jennifer.m.adams at nasa.gov> wrote:
>>> Yes, GrADS requires a linear time axis with a constant interval between time steps. The only workaround I can think of is to break up your file into pieces, one time step per file, with a naming convention that contains sufficient information about the date associated with your file so that you can use templating. Then create a descriptor file with the daily time axis increment and enough time steps to cover the entire period to span your data, and then GrADS will populate the time steps where your data files exist and treat the rest as missing data.
More information about the gradsusr