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.
> I uploaded a file (u850.2015120800.nc) to the idvuploads area on the > Unidata RAMADDA server. If I run ncdump -v time -t on the file, it > prints out the correct times. > > time = "2015-12-08", "2015-12-08 12", "2015-12-09", "2015-12-09 12", > "2015-12-10", "2015-12-10 12", "2015-12-11", "2015-12-11 12", > "2015-12-12", "2015-12-12 12", "2015-12-13", "2015-12-13 12", > "2015-12-14", "2015-12-14 12", "2015-12-15", "2015-12-15 12", > "2015-12-16", "2015-12-16 12", "2015-12-17", "2015-12-17 12", > "2015-12-18", "2015-12-18 12", "2015-12-19", "2015-12-19 12", > "2015-12-20", "2015-12-20 12", "2015-12-21", "2015-12-21 12", > "2015-12-22", "2015-12-22 12", "2015-12-23", "2015-12-23 12", > "2015-12-24" ; > Don, You need to specify the calendar attribute to be "gregorian" to get the correct time, it is supposed to be standard or default, but your init time is way before 1845. Still, I think it is a bug in the CDM. Yuan > > If I load that file into the IDV, the times are 2 days off (first time > is 2015-12-10 00 instead of 2015-12-08 00). > > There is no calendar attribute, but it seems like ncdump knows how to > handle that correctly. > > Don > -- > Don Murray > NOAA/ESRL/PSD and CU-CIRES > 303-497-3596 > http://www.esrl.noaa.gov/psd/people/don.murray/ > > Ticket Details =================== Ticket ID: ZOM-669058 Department: Support IDV Priority: Normal Status: Closed