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
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.