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
Yet getdap4 (and thus by association libdap) fails to read Attribute values encoded this way. The TDS uses thee aforementioned encodings and the getdap4 is used to retrieve the DMR:
The DAP4 specification section 1.5.14 indicates that Attribute values may be encoded in the DMR as:
Yet
getdap4
(and thus by association libdap) fails to read Attribute values encoded this way. The TDS uses thee aforementioned encodings and the getdap4 is used to retrieve the DMR:getdap4 -d "http://35.87.12.216:8080/thredds/dap4/data/NSIDC/SMAP_L3_SM_P_20150406_R14010_001.h5"
All of the Attribute values are empty:
We can see with curl:
curl -L "http://35.87.12.216:8080/thredds/dap4/data/NSIDC/SMAP_L3_SM_P_20150406_R14010_001.h5.dmr"
That the TDS returns values:
The text was updated successfully, but these errors were encountered: