Server side function roi() is failing on datasets with more than 2 dimensions

Hi Nathan,

About roi() - yes I was referring to the server-side function for level-2 data subsetting. Consider this data:

https://aura.gesdisc.eosdis.nasa.gov/opendap/Aura_OMI_Level2/OMAERUV.003/2005/001/OMI-Aura_L2-OMAERUV_2005m0101t0020-o02472_v003-2017m0720t185621.he5.html

I can subset "FInalAlgorithmFlags" without trouble. It is a 2-D array, like "Latitude" and "Longitude" in that dataset.

https://aura.gesdisc.eosdis.nasa.gov:443/opendap/Aura_OMI_Level2/OMAERUV.003/2005/001/OMI-Aura_L2-OMAERUV_2005m0101t0020-o02472_v003-2017m0720t185621.he5.nc4?roi(FinalAlgorithmFlags,Latitude,Longitude,bbox_union(bbox(Latitude,-62,-58),bbox(Longitude,-26,26),inter))

If I pick a 3-D array "FinalAerosolAbsOpticalDepth", say, I couldn't be successful.

https://aura.gesdisc.eosdis.nasa.gov:443/opendap/Aura_OMI_Level2/OMAERUV.003/2005/001/OMI-Aura_L2-OMAERUV_2005m0101t0020-o02472_v003-2017m0720t185621.he5.nc?roi(FinalAerosolAbsOpticalDepth,Latitude,Longitude,nWavel,bbox_union(bbox(Latitude,-62,-58),bbox(Longitude,-26,26),bbox(nWavel,0,1),inter))

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

https://aura.gesdisc.eosdis.nasa.gov/opendap/Aura_OMI_Level2/OMAERUV.003/2005/001/OMI-Aura_L2-OMAERUV_2005m0101t0020-o02472_v003-2017m0720t185621.he5.rdf

None of our data responded nicely, but we have 1.13.4. Perhaps some stylesheet is missing. I can test your new release.

-Fan