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.
>From: Sangeet <address@hidden> >Organization: IIT >Keywords: 200208140551.g7E5p0K21485 netCDF ferret Sangeet, >thank you very much for your prompt response, with all appreciations. The >Ferret as u mentioned was simply used to visualise the said files, which >was found to be ok. In fact, the extraction of the data fields through >ncdump could be accomplished successfully but with erratic values >everywhere in the variable field. Its where the problem lies with the >application of ncdump. The reason I suggested that the problem may be in Ferret is that you commented that the values extracted using ncdump were the same as those extracted from a Fortran program you wrote. This would seem to indicate, if the values are consistent, that the values are exactly what ncdump is returning. If you know this to not be the case, we need to investigate further. >The ncdump works very well with the *.cdf files. >The help is very much saught to extract the fields from nc files with >ncdump or the like.I once again stress to the point that we are facing >problems using ncdump and NOT ferret. > >Thanking you once again,looking for your big hand for the >troubleshooting. Please provide us with the following: 1) the version of the netCDF package that you are using 2) the operating system you are using it on (please include revision level) 3) example output from the ncdump invocation you are running 4) if possible, give us access to one of the netCDF files that you are trying to list values from. >with regards, Tom