Lewis John McGibbney

Hi @Omkar20895 yes one resides [here](https://podaac-opendap.jpl.nasa.gov/opendap/allData/ghrsst/data/GDS2/L2P/AMSR2/REMSS/v8a/2019/044/20190213001101-REMSS-L2P_GHRSST-SSTsubskin-AMSR2-L2B_rt_r35859-v02.0-fv01.0.nc.ddx). It's very simple XML.

@Omkar20895 thanks for stepping up here. > We can use XML Xpaths using lxml.xtree/xpath module in the variable utility function to get the variable names. The only issue just now...

In short no that is not a scenario I think is possible. The contents of the granule data products is consistent. It’s only the actual sensor observation values which change....

@Omkar20895 > Each XML tag(related to a variable) in the .ddx response either has Array or Grid as the tag name, are these in any way associated with different levels...

So really, it is the `Grid`'s which we are interested in extracting.

Hi @ShubhamShaswat did you see the proposed solution at the following PR https://github.com/nasa/podaacpy/pull/129#issuecomment-471198841

Hi @Omkar20895 yes you are right it does. The correct way to address this is for us to implement the support over on the PO.DAAC side. I'll keep this issue...

@Omkar20895 looks like we may need to implement a [NetCDFReponse](http://pydap.readthedocs.io/en/latest/responses.html#netcdf)

Thanks @ffang10 @Omkar20895, even if the NetCDF response returned by Pydap may work better on gridded data as oppose to swatch and other granularities, I still think that having functionality...

Thanks for looking into it @Omkar20895 I've replied over on the Pydap issue.