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.
This bug is known and is fixed in 4.3.1.1. There are actually two related issues. First, that server is old and does not properly implement the dap2 protocol. Specifically, this means that a reference such as this: http://data.nodc.noaa.gov/thredds/dodsC/testdata/pathfinderAgg/pathFinderV5.2_night.ncml.dds?sst_dtime.sst_dtime returns Dataset { Int32 sst_dtime[time = 10870][lat = 4320][lon = 8640]; } testdata%2fpathfinderAgg%2fpathFinderV5%2e2_night%2encml; when it should be returning this: Dataset { Structure { Int32 sst_dtime[time = 10870][lat = 4320][lon = 8640]; } sst_dtime; } testdata%2fpathfinderAgg%2fpathFinderV5%2e2_night%2encml; More recent thredds servers have this fixed. The second issue is that I had to add several hacks to the netcdf-c dap2 support to handle such servers. I have been refining and adding hacks over time, and the most recent netcdf-c release, 4.3.1.1, appears to solve your specific example. =Dennis Heimbigner Unidata Ticket Details =================== Ticket ID: QMW-534881 Department: Support netCDF Priority: Normal Status: Closed