About roi() - yes I was referring to the server-side function for level-2 data subsetting. Consider this data:
I can subset "FInalAlgorithmFlags" without trouble. It is a 2-D array, like "Latitude" and "Longitude" in that dataset.
If I pick a 3-D array "FinalAerosolAbsOpticalDepth", say, I couldn't be successful.
I suppose something in the function is rigid that the shape of the subset array has to be the same as the "Latitude" and "longitude". It's all a problem of knowing the dimensions - if the function can recognize that the 3rd (or beyond) dimension, "nWavel" in this case, is not shared with those of the "Latitude" and "Longitude", but rather with a different variable which may or may not need subset (nWavel in this case, specified in the URL for subset), the function may execute correctly.
About .rdf - you may just try
None of our data responded nicely, but we have 1.13.4. Perhaps some stylesheet is missing. I can test your new release.
We decided to add a new function that will enable combining bounding boxes with different dimensions. Lets call this bbox_comb(…). It will take 2 bounding boxes (i.e., items returned by bbox() or bbox_union()) and return a new bounding box that is their cross product. To _comb_ine more than two bounding boxes, nest calls to bbox_comb().