scale with imageCrsDomain returns wrong rasdaman axis order

[Dimitar Misev]

E.g. a query like this:

for c in (Sentinel_2A_B12_20m), d in (Sentinel_2A_B11_20m), e in (Sentinel_2A_B04_10m) return encode(
{ red: c[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)];
  green: d[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)];
  blue: scale(e[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)], { imageCrsDomain(c[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)]) })
}, 
 "tiff")

The imageCrsDomain according to WCPS standard is

Extent of the coverage in (integer) grid
coordinates, relative to the coverage’s
Image CRS2; essentially, the set of all
point coordinates inside the coverage 

But it has been done for a very long time before WCPS 1.5 with the result in geo CRS order (e.g: Lat, Long)

c[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)];

return [Lat: 885:1898, Long: 745:2417]

but not rasdaman order

c[Lat(53.6734: 53.9267), Long(7.6550:8.0729), unix:"CRS:1"(0)];

return [Long: 745:2417, Lat: 885:1898]