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

[netCDF #OZZ-222928]: Re: use of "nctime.c" code in NCL



Hi Mary,

I've finally handling this bug you reported.

> Thanks Russ.  My original tests didn't catch this easier. I only caught it 
> because I noticed the
> minute/second code was unique in the nctime.c, and thought I better check my 
> own interface
> to it.
> 
> I'm not sure the original cdtime code is correct either, but I can't test it 
> directly since I don't
> have CDAT installed.

The problem is use of the ISO 8601 standard and its use of the "T" in the time 
string 
separating the date and time:

  time:units = "seconds since 2008-06-04T00:15:03Z" ;

It works as expected if instead you use the same notation as "ncdump -t" emits, 
which 
doesn't include the "T" separator:

  time:units = "seconds since 2008-06-04 00:15:03Z" ;

The problem with parsing the "T" separator was actually in the CDAT library.  
I've
modified it to accept the "T" separator, so your example now works in the 
snapshot.

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: OZZ-222928
Department: Support netCDF
Priority: Critical
Status: Closed


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.