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.
Dennis Heimbigner wrote:
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
Dennis: Although the attributes are now appearing correctly, I'm still having trouble accessing the IPCC data. For example,
ncdump -v prw http://esgcet.llnl.gov/dap/ipcc4/20c3m/gfdl_cm2_0/pcmdi.ipcc4.gfdl_cm2_0.20c3m.run1.atm.mo.xml
gives data: prw = ; // UNDEFINED } with the Sept 16 snapshot. The coordinate variables seem to work fine data:lat = -89, -87, -85, -83, -81, -79, -77, -75, -73, -71, -69, -67, -65, -63,
-61, -59, -57, -55, -53, -51, -49, -47, -45, -43, -41, -39, -37, -35, -33, -31, -29, -27, -25, -23, -21, -19, -17, -15, -13, -11, -9, -7, -5, -3, -1, 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45, 47, 49, 51, 53, 55, 57, 59, 61, 63, 65, 67, 69, 71, 73, 75, 77, 79, 81, 83, 85, 87, 89 ; }but all the data grids come back undefined. The same thing happens when trying to access data from the IRI data library
ncdump -v hgt http://iridl.ldeo.columbia.edu/expert/SOURCES/.NOAA/.NCEP/.EMC/.CFS/.MONTHLY_REALTIME/.PRESS/.hgt/dods
hgt = ; // UNDEFINED } Other dap URLs work fine though, for examplencdump -v vvelprs http://nomad1.ncep.noaa.gov:9090/dods/reanalyses/reanalysis-2/6hr/pgb/pgb
-Jeff
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: