WCPS1.5_Wrong geo-referencing from WCPS query to RASQL query

[Bang Pham Huu]

test wcps query "82-timestamp_in_subset.test"

for c in (eobstest) return encode(
  (c[
    t("1950-01-02"),
    Long(20:35),
    Lat(10:15)]),
"tiff", "nodata=0")

which is translated wrong geo-referencing in WCPS 2.0 (in here it get all the bounding box instead of trimming).

SELECT encode( ( c[1,-10:19,121:130] ),
"GTiff" ,
"nodata=0;xmin=25.0;xmax=75.5;ymin=-40.5;ymax=75.5;crs=EPSG:4326") FROM eobstest AS c

instead of correct translation as WCPS 1.0

select encode(c[1,-10:20,121:131],
"GTiff",
"nodata=0;xmin=20.0;xmax=35.0;ymin=10.0;ymax=15.0;crs=EPSG:4326") from eobstest AS c where oid(c)=46081

[Bang Pham Huu]

In WCPS 1.0 there is a bug when using "*" in axis, with WCPS query like this

for c in (eobstest) return encode(c[t(0), Lat(0:*), Long(0:35)], "tiff")

will returns Rasql

select encode(c[0,-50:20,0:151], "GTiff") from eobstest AS c where oid(c)=1537

without GeoReferencing parameters (xmin, xmax, ymin, ymax)

While with same WCPS query with same limit upper bound but using number

for c in (eobstest) return encode(c[t(0), Lat(0:75.5), Long(0:35)], "tiff")

it will returns the GeoReferencing parameters as

select encode(c[0,-50:20,0:151], "GTiff",
 "xmin=0.0;xmax=35.0;ymin=0.0;ymax=75.5;crs=EPSG:4326") from eobstest AS c where oid(c)=1537

This problem will be fixed in WCPS1.5 with this ticket.

[Bang Pham Huu]

It is now set correct bounding box according to the domain of coverage's axis, thanks for Vlad's idea, close ticket.