WCPS - Encode geo-reference not correctly when slicing between time and 1 geo-reference axis in GeoTiff

[Bang Pham Huu]

from eobstest demo has 3 axes (Lat, Long and t - time), when I slice along Lat axis

for c in (eobstest) return encode(c[Lat(20)], "tiff")

in WCPS1.0 it will return this kind of Rasql:

 select encode((c) [*:*,*:*,111], "GTiff", 
"xmin=0.0;xmax=6.0;ymin=25.0;ymax=75.5;crs=EPSG:4326") 
from eobstest AS c where oid(c)=1537

and WCPS1.5 with ticket #1205 still wait then will return:

SELECT encode(c[*:*,*:*,111], "GTiff" , 
"xmin=25.0;xmax=75.5;ymin=-40.5;ymax=75.5;crs=EPSG:4326") FROM eobstest AS c

so both are not correct, I will emphasize to WCPS1.0 as it is problem from here, when in this case, slicing along a Lat axis will return an image which combine 2 axes (Long and time), then it can not set geo-reference axis to this image (CRS:4326).

So no need to add bounding box and CRS if there is mixing between 1 geo-reference axis and other axis (like time, evelavation, pressure, temperature,…).

[Bang Pham Huu]

This ticket was fixed in patch ticket 1188, when combine 2 different kind of axis (e.g: geo-reference, time) it will not set the bounding box, close ticket.

WCPS query

for c in (eobstest) return encode(c[Lat(20)], "tiff")

Rasql query

SELECT encode(c[0:5,0:100,111], "GTiff" , "") FROM eobstest AS c