I must disagree; I can plug that url into a web browser and get the same results (i.e. no data). This clearly indicates that the client-side netcdf code is not the problem; it must be a server problem. You should verify my claim by using those urls in a web browser to see what result you get. It may be that the server problem is located in the libnc-dap or libdap code that it uses, but we do not manage that code; you will have to submit a bug report to opendap.org. Sorry I cannot be more help. =Dennis Heimbigner Unidata Ticket Details =================== Ticket ID: DOE-704686 Department: Support netCDF Priority: Normal Status: Open
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.