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 Lee, First, sorry it has taken so long to get to this, both Ed and I were on spring break last week. Have you tried calling the function nf90_put_var_text to put character data? That function is supposed to be called automatically by nf90_put_var, which is overloaded to call lots of different internal functions such as nf90_put_var_text depending on the types of values given to it, but maybe there's something wrong with the overloading. The function is in f90/netcdf_text_variables.f90: function nf90_put_var_text(ncid, varid, values, start, count, stride, map) integer, intent( in) :: ncid, varid character (len = *), intent( in) :: values integer, dimension(:), optional, intent( in) :: start, count, stride, map integer :: nf90_put_var_text integer, dimension(nf90_max_var_dims) :: localStart, localCount, localStride along with some other functions like nf90_put_var_1D_text, nf90_put_var_2D_text, ... If it turns out it works to call one of these internal functions but not to call nf90_put_var with a character variable, that's a bug we'll have to fix. I'll try to put together a test for this soon, but it's definitely not a "feature"! The netCDF-4 release would currently have the same bug and the same fix should work, if this turns out to be a bug. You're right, that's not a good diagnostic to return for this problem, but I need to duplicate the error first before I know what's going on ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: YEC-124697 Department: Support netCDF Priority: Normal Status: Closed