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.
Hi Ian, Did you explicitly define a "_FillValue" attribute for the time coordinate dimension? If so, was the type something other than NF_DOUBLE? I've managed to duplicate the problem in a small Fortran program from your description, but only by explicitly defining a _FillValue attribute for the unlimited coordinate dimension that did not match the type for the associated coordinate variable. It seems to me that should be an error when the attribute is first defined, not later when you try to write a value for it. I'll look into this more carefully, but a workaround for the bug for now would be to make sure the _FillValue attribute type matches the variable type. Thanks for reporting the problem. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: DXD-376053 Department: Support netCDF Priority: Normal Status: Closed