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

[Fwd: Re: [Fwd: FW: handling the leap year attribute]]

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: [Fwd: Re: [Fwd: FW: handling the leap year attribute]]
  • Date: Wed, 11 Jan 2006 09:18:07 -0700
Hi Noman, heres the answer from our udunits expert:

-------- Original Message --------
Subject: Re: [Fwd: FW: handling the leap year attribute]
Date: Wed, 11 Jan 2006 08:16:05 -0700
From: Steve Emmerson <address@hidden>
Organization: UCAR/Unidata
To: John Caron <address@hidden>

John,


Date: Tue, 10 Jan 2006 17:59:06 -0700
From: John Caron <address@hidden>
Organization: UCAR/Unidata
To: Steve Emmerson <address@hidden>
Subject: [Fwd: FW: handling the leap year attribute]


The above message contained the following:


In the nc file, the attribute is seen as

time = 31025 ;
time:units = "days since 0400-01-01 00:00:00" ;
time:calendar = "noleap" ;

So, how does the udunits library use this attribute?


The UDUNITS library can't handle the "noleap" netCDF attribute.  There's
no mechanism in the API to tell the library that a non-standard calendar
is being used.

If that attribute is being handled by some program, then that program
must take matters into its own hands and not rely, exclusively, on the
UDUNITS library.

Regards,
Steve Emmerson