[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20041118: Decoders gribtocdl, gribtonc

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20041118: Decoders gribtocdl, gribtonc
  • Date: Tue, 21 Dec 2004 09:24:51 -0700 (MST)
On Thu, 18 Nov 2004, Unidata Support wrote:

>

Arthur,

sorry it took so long to get back to you. the conventions are now the same
for the ETA211 and the WSETA.  i think this should solve your problems.

robb...

>
> ------- Forwarded Message
>
> >To: address@hidden
> >From: "Arthur Clifford" <address@hidden>
> >Subject: Case Studies - valtime_offset?
> >Organization: UCAR/Unidata
> >Keywords: 200411172132.iAHLW0Zh012846
>
> Institution: The New Media Studio
> Package Version: n/a
> Operating System: n/a
> Hardware Information: n/a
> Inquiry: Hello, I am working on a project for Ben Domenico where I've 
> retrieved information from DODS for ETA_211 and WSETA data that are case 
> studies, but also for getting the "Latest" data.
>
> I want to be able to display accurate time information. At the moment, I am 
> using the valtimes returned (since they are unique) to calculate the date and 
> hour a given grid is related to.
>
> In the WSETA data valtime_ofset is 0, and there is only the one value. 
> valtime_offset for ETA_211 has values of 0,6,12,18,24,30,36,42,48,54,and 60. 
> (every 6 hours, there is an entry for every val_time/ref_time).
>
> There is a datetime field but all its values are the same and appear to be 
> the date the model was run rather than the date being forecast. ETA_211 has a 
> forecast time but WSETA does not.
>
> Is there anything anywhere that explains how ref_time, val_time, and val_time 
> offset are determined and what they are for?
>
> And, can I reliably use val_time to get the date for grids? Of coure, this is 
> less an issue for case-studies as it is for handling Latest datasets.
>
> Thanks for your time,
>
> Art C.
>
>
>
> --
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.
>
> ------- End of Forwarded Message
>

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================