You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to use the OpenDAP capabilities of adaguc in order to serve some netCDF files over the network. At most, I can see the header and dimension values, such as time or geographical coordinates, but variables only return errors or garbage.
Both locally compiled versions and docker ones seem to be affected. Last test was to setup the environment yesterday with latest docker images, download a well-known netCDF file (https://www.unidata.ucar.edu/software/netcdf/examples/tos_O1_2001-2002.nc) and place it in autowms directory. It can be visualised in the viewer, but with ncdump + openDAP the trouble begins.
The command ncdump -v tos , after the header, returns:
data:
tos =
syntax error, unexpected WORD_WORD, expecting SCAN_ATTR or SCAN_DATASET or SCAN_ERROR
context: Content-type^: text/plainException with code 2 found
NetCDF: Malformed or inaccessible DAP2 DATADDS or DAP4 DAP response
Location: file ; line 478
And this is the adaguc-server log
pplicationlog 2024-03-14 09:01:50,152 - routers.opendap - INFO - tos_O1_2001-2002.nc.dods
applicationlog 2024-03-14 09:01:50,152 - routers.setup_adaguc - INFO - Using config file /adaguc/adaguc-server-master///python/lib/adaguc/adaguc-server-config-python-postgres.xml
applicationlog 2024-03-14 09:01:50,152 - routers.opendap - INFO - Setting request_uri to https://adaguc-server:8080
applicationlog 2024-03-14 09:01:50,299 - routers.opendap - INFO - [D:000:pid44: adagucserverEC/COpenDAPHandler.cpp:427 COpenDAPHandler] 2024-03-14T09:01:50Z CONTENT_TYPE
[D:001:pid44: adagucserverEC/COpenDAPHandler.cpp:436 COpenDAPHandler] 2024-03-14T09:01:50Z OpenDAP Received [adagucopendap/tos_O1_2001-2002.nc.dods] [&tos[0][0][0:179]=]
[D:002:pid44: adagucserverEC/COpenDAPHandler.cpp:536 COpenDAPHandler] 2024-03-14T09:01:50Z Checking /data/adaguc-datasets
[D:003:pid44: adagucserverEC/CAutoResource.cpp:69 CAutoResource] 2024-03-14T09:01:50Z Dataset not found in [/data/adaguc-datasets/tos_O1_2001-2002.nc.xml]
[D:004:pid44: adagucserverEC/CAutoResource.cpp:69 CAutoResource] 2024-03-14T09:01:50Z Dataset not found in [/data/adaguc-datasets-internal//tos_O1_2001-2002.nc.xml]
[E:005:pid44: adagucserverEC/CAutoResource.cpp:78 CAutoResource] 2024-03-14T09:01:50Z No such dataset
[D:006:pid44: adagucserverEC/COpenDAPHandler.cpp:536 COpenDAPHandler] 2024-03-14T09:01:50Z Checking /data/adaguc-datasets-internal/
[D:007:pid44: adagucserverEC/CAutoResource.cpp:69 CAutoResource] 2024-03-14T09:01:50Z Dataset not found in [/data/adaguc-datasets/tos_O1_2001-2002.nc.xml]
[D:008:pid44: adagucserverEC/CAutoResource.cpp:69 CAutoResource] 2024-03-14T09:01:50Z Dataset not found in [/data/adaguc-datasets-internal//tos_O1_2001-2002.nc.xml]
[E:009:pid44: adagucserverEC/CAutoResource.cpp:78 CAutoResource] 2024-03-14T09:01:50Z No such dataset
[D:010:pid44: adagucserverEC/CServerParams.cpp:392 CServerParams] 2024-03-14T09:01:50Z szResolvedPath: /data/adaguc-autowms/tos_O1_2001-2002.nc
[D:011:pid44: adagucserverEC/CServerParams.cpp:393 CServerParams] 2024-03-14T09:01:50Z baseDir : /data/adaguc-autowms
[D:012:pid44: adagucserverEC/CAutoResource.cpp:226 CAutoResource] 2024-03-14T09:01:50Z OGC REQUEST Remote resource /data/adaguc-autowms/tos_O1_2001-2002.nc
[E:013:pid44: adagucserverEC/COpenDAPHandler.cpp:1172 COpenDAPHandler] 2024-03-14T09:01:50Z Exception with code 2 found
accesslog 172.18.0.2:49222 ; [14/Mar/2024:09:01:50 +0000] ; HTTP/1.0 ; GET ; /adagucopendap/tos_O1_2001-2002.nc.dods ; tos%5b0%5d%5b0%5d%5b0:179%5d ; 200 ; 158 ; "oc4.9.0"
As a workaround, WMS/WCS are adequate in certain scenarios. However, it would be great to have openDAP as well, given the ability of creating virtual netCDFs.
Thanks a lot and don't hesitate asking me more info / tests.
The text was updated successfully, but these errors were encountered:
I have been trying to use the OpenDAP capabilities of adaguc in order to serve some netCDF files over the network. At most, I can see the header and dimension values, such as time or geographical coordinates, but variables only return errors or garbage.
Both locally compiled versions and docker ones seem to be affected. Last test was to setup the environment yesterday with latest docker images, download a well-known netCDF file (https://www.unidata.ucar.edu/software/netcdf/examples/tos_O1_2001-2002.nc) and place it in autowms directory. It can be visualised in the viewer, but with ncdump + openDAP the trouble begins.
The command ncdump -v tos , after the header, returns:
And this is the adaguc-server log
As a workaround, WMS/WCS are adequate in certain scenarios. However, it would be great to have openDAP as well, given the ability of creating virtual netCDFs.
Thanks a lot and don't hesitate asking me more info / tests.
The text was updated successfully, but these errors were encountered: