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.
My last explanation was incorrect. I did some experimenting and found that the reason that foo failed is because the libdap library prefetches small variables as a whole. Ncdump has nothing to do with it. So for foo, it is so small that the whole thing is prefetched (without any constraints). The gfs dataset prefetches only the four variables time,lev,lat,lon, but it does so with a single request, hence it has the constraint ?time,lev,lat,lon. All of the bigger variables in gfs are retrieved piecemeal by ncdump, so they have a constraint also. There is a workaround. If you append #noprefetch to your url, i.e. http://www.monsoondata.org:9191/dods/foo#noprefetch then ncdump will work correctly. =Dennis Heimbigner Unidata Ticket Details =================== Ticket ID: TMR-458993 Department: Support netCDF Priority: Urgent Status: Closed