Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
I found and fixed the bug. I did not implement the libdap algorithm quite correctly. The fix should be available in the netcdf snapshot tomorrow. Thanks for pointing this out. =Dennis Heimbigner Jeff Whitaker wrote:
Dennis: If I openhttp://esgcet.llnl.gov/dap/ipcc4/20c3m/gfdl_cm2_1/pcmdi.ipcc4.gfdl_cm2_1.20c3m.run1.atm.mo.xmlwith netcdf-4.1-beta2, then get the time variable, it appears there are no attributes associated with it. Browsing the xml filehttp://esgcet.llnl.gov/aggregates/ipcc4/20c3m/gfdl_cm2_1/pcmdi.ipcc4.gfdl_cm2_1.20c3m.run1.atm.mo.xmlit does appear these attributes are defined, but somehow the client is not getting them.Is it a bug in the way there are serving the data, or a bug in the opendap client in netcdf-4.1?-Jeff
netcdfgroup
archives: