Opened 4 months ago

Closed 4 months ago

#1559 closed defect (fixed)

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

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.4
Component: petascope Version: development
Keywords: Cc: dmisev, vmerticariu
Complexity: Medium


In a test sample with original tiff file with metadata:

Origin = (580000.000000000000000,4340000.000000000000000)
Pixel Size = (10.000000000000000,-10.000000000000000)
Image Structure Metadata:
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)


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.


Change History (4)

comment:1 Changed 4 months ago by dmisev

Is the bbox correct? xmax = 580010, but the query subset has 580020; ymin = 4339990, but subset uses 4339980

Last edited 4 months ago by dmisev (previous) (diff)

comment:2 Changed 4 months ago by vmerticariu

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

comment:3 Changed 4 months ago by bphamhuu

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


Pixel Size = (10.000000000000000,-10.000000000000000)

comment:4 Changed 4 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.