GDAL OPeNDAP Driver Failing

[condit]

This code worked at one point in the past. With the new 3.8 libdap it fails...

condit@indus:~/develop/gdal/apps$ ./gdalinfo -mm ​http://apdrc.soest.hawaii.edu/dods/public_data/SODA/soda_pop2.0.4?u.u[0][0][-y][x] Driver: DODS/DAP 3.x servers Files: none associated Size is 720, 330 Coordinate System is `' Corner Coordinates: Upper Left ( 0.0, 0.0) Lower Left ( 0.0, 330.0) Upper Right ( 720.0, 0.0) Lower Right ( 720.0, 330.0) Center ( 360.0, 165.0) Band 1 Block=720x128 Type=Float32, ColorInterp=Undefined ERROR 1: An internal error was encountered: Expected an Array or Grid variable! Please report this to support@…

ERROR 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: An internal error was encountered: Expected an Array or Grid variable! Please report this to support@…

ERROR 1: IReadBlock failed at X offset 0, Y offset 1 ERROR 1: An internal error was encountered: Expected an Array or Grid variable! Please report this to support@…

ERROR 1: IReadBlock failed at X offset 0, Y offset 2

Computed Min/Max=0.000,0.000

NoData Value=-9.9899999999999995e+33 Overviews: 360x165, 180x82

[condit]

I'm going to go ahead and close this ticket per Stephans email on the GDAL-dev list:

I think the source of the problem in ticket #2492 is not a GDAL defect, but that the variable in the connection string is "u.u". The .operator is used to refer to members of a structure (see ​http://opendap.org/user/guide-html/guide_61.html), but the variables in this dataset are grouped by grids (see ​http://apdrc.soest.hawaii.edu/dods/public_data/SODA/soda_pop2.0.4.dds). It may be that using the .operator to access members of grids was allowed in older versions of libdap. As it is, replacing "u.u" with "u" eliminates the problem for me on machines with libdap-3.8.2/gdal-svn15148 and libdap-3.7.10/gdal-gdal-1.4.2, respectively.

I should note that this same call was working with and older version of the libdap library (3.6.2). This is a change with the 3.7/3.7 library...