Wrong ODC query when CRS is specified

[pierocampa]

When crafting the ODC query for the case of a non-default CRS:

            if self.crs is not None:
                query['crs']  = 'epsg:' + str(self.crs)
                query['x']  = (self.south,self.north)
                query['y'] = (self.east,self.west)
                query['output_crs'] = 'epsg:' + str(self.crs)
                query['resolution'] = [10,10]

(odc_wrapper.py)

There are imho 2 issues:

• x / y are wrongly assigned, they should be flipped!
• the resolution should be removed in order to keep the datacube's original one (in case of projected CRS, usually the uom of axis is meters, so the query seems to aggressively upsample the output data to a 10x10 m resolution, whereas in case of geographic CRS the output is downsampled to 10x10 degrees, whole continents in one pixel)

Note that the arbitrary 10x10 resolution is set also in the handling of the exception: Product has no default CRS. Must specify 'output_crs' and 'resolution'.

[clausmichele]

Sorry for not addressing this issue for long time. Going in order:

• The inversion is fixed now 63155cc
• The issue comes from a single collection that we host at Eurac, the Sentinel-2 over the Alps. This collection is a composition of all UTM S2 tiles covering the Alps with different projections. OpenDataCube does not allow to fix a resolution for a collection/product if we do not specify the output CRS as well. So currently it automatically detects the CRS for the required area, but not the resolution. I don't see many solutions here at the moment, maybe we could consider retrieving the resolution info from the STAC metadata.
• I have to investigate about the WGS84 cases