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 Ed, > > > > It is unclear what default fill value, if any, to use for NC_STRING > > since NC_FILL_STRING does not yet exist. > > > > Also, I could not find anywhere the CDL notation that will be used > > to specify the new netCDF4 atomic types (e.g., NC_UBYTE, etc.). > > > > As you may have guessed, I'm trying to support the new atomic types > > in NCO. ncks currently works with them. The arithmetic operators will > > take longer. > > > > Thanks, > > Charlie > > -- > > Charlie Zender, address@hidden, Department of Earth System Science > > 3228 Croul Hall, UC Irvine, Irvine CA 92697-3100. (949) 824-2987 :) > > > > > > Thanks for pointing this out, it's a bug either in the header file or the documentation. I'll get back to you as soon as I've checked it out. > > Thanks, > > Ed OK Charlie, I've added those functions, and a test for them in libsrc4/tst_strings.c. This is with HDF5 1.8.0-beta2. Unfortunately string fill values are still a bit of a problem in that release of HDF5. I am working with the HDF5 team to get that resolved. Thanks, Ed Ticket Details =================== Ticket ID: ZKG-804086 Department: Support netCDF Priority: Normal Status: Closed