[netCDF #OYW-455599]: Broken 366_day calendar in ncdump

Dave- I am finally in a position to return to this issue about
366 day calendars. I need some help before I can solve.
=Dennis Heimbigner

Specifically, I need to know the following:

I created a minimal example of the 366 day calandar example
to simplify debugging.
Here is the CDL (without the data: section). It is the same
as your original example except the time dimension is smaller.
--------------------------------------------------
netcdf test {
dimensions:
        time = 7 ;
variables: 
        int time(time) ;
                time:units = "days since 1900-1-1" ;
                time:calendar = "366_day" ;
}
--------------------------------------------------
The data part (without using ncdump -t flag)
is this set of 7 values: data: time = 360,361,362,363,364,365,366;
This is a subset of the original failing data you sent.
The output using ncdump -t is this:
data: time = "1900-12-31", "íaÈÄ(", "íaÈÄ(", "íaÈÄ(", "íaÈÄ(", "íaÈÄ(", 
"1901-01-01" ;

So my questions are:
1. is the first value "1900-12-31" correct as the time equivalent of 360?
2. what should those middle 5 failing time outputs look like?
   e.g "1900-12-32"... or what

 

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: OYW-455599
Department: Support netCDF
Priority: Normal
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.