WCPS_Check the bbox of output coverage with pixel size is different from original file

[Bang Pham Huu]

In a test sample with original tiff file with metadata:

Origin = (580000.000000000000000,4340000.000000000000000)
Pixel Size = (10.000000000000000,-10.000000000000000)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (  580000.000, 4340000.000) (  2d 4'24.40"W, 39d12'20.11"N)
Lower Left  (  580000.000, 4330000.000) (  2d 4'28.66"W, 39d 6'55.75"N)
Upper Right (  590000.000, 4340000.000) (  1d57'27.51"W, 39d12'16.59"N)
Lower Right (  590000.000, 4330000.000) (  1d57'32.30"W, 39d 6'52.24"N)
Center      (  585000.000, 4335000.000) (  2d 0'58.22"W, 39d 9'36.22"N)

a subset request in WCS (WCPS)

SUBSET=E(580000,580020)&SUBSET=N(4339980,4340000)

returns correct grid points

SELECT encode(c[0:1,0:1,0]

but because of the bbox is not correct for xmax, ymax, so the pixel size of output is 5 instead of 10.

"bbox\":{\"xmin\":580000,\"ymin\":4339990,\"xmax\":580010,\"ymax\":4340000}

[Dimitar Misev]

Is the bbox correct? xmax = 580010, but the query subset has 580020

[Vlad Merticariu]

No, the bbox is the problem, xmax should be 580020 and ymin 4339980. This is causing the pixel size to be different.

[Bang Pham Huu]

If I set to correct xmax, and ymin output will have 10 pixel size

{\"xmin\":580000,\"ymin\":4339980,\"xmax\":580020,\"ymax\":4340000}

Pixel Size = (10.000000000000000,-10.000000000000000)