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

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

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: [netCDF #OZZ-222928]: Re: use of "nctime.c" code in NCL
  • Date: Fri, 26 Aug 2011 08:30:14 -0600
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