WCPS2.0_Difference between origins of coverages with WCPS1.0

[Bang Pham Huu]

Now, I'm testing WCPS 2.0 and this ticket still open then I will report to here, test wcps "35-coordinates_in_wgs84_crs.test.out" with WCPS query

for c in (eobstest) return encode(
  (c[
    t(1),
    Long:"http://www.opengis.net/def/crs/EPSG/0/4326" (20:35),
    Lat:"http://www.opengis.net/def/crs/EPSG/0/4326" (10:15)]),
"tiff", "nodata=0")

+ Version 1.0 returns the rasql like (returns TOP-DOWN trimming)

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

+ Version 2.0 returns the Rasql like (returns BOTTOM_UP trimming)

Version 2.0 returns the rasql like 

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

view output in here ​https://drive.google.com/a/fimo.edu.vn/folderview?id=0B_VL2-SVlKPHNHpacVRHUDdQalk&usp=drive_web (file .oracle is WCPS 1.0 and file .out is WCPS 2.0).

[Dimitar Misev]

Is the link correct? In the ticket you refer to query 52, in the drive I see 35?

As far as I can see WCPS 2.0 sets the coverage boundaries instead of the subset boundaries as it is supposed to.