Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#776 closed defect (fixed)

WCS scaling operation dosen't work with georeferenced coverage

Reported by: gxinghua Owned by: pcampalani
Priority: critical Milestone: 9.0.x
Component: petascope Version: development
Keywords: scale geo wcs Cc: pbaumann, pcampalani, j.yu
Complexity: Medium


All the scaling operations: scalefactor, scalesize, scaleextend and scaleaxis can not correctly response with georeferenced coverage.

For example, to the system_test coverage irr_cube_2, the WCS request: "service=WCS&version=2.0.1&request=GetCoverage?&coverageId=irr_cube_2&scalefactor=2.0", petascope give this response:

<ows:Exception exceptionCode="InvalidSubsetting">
Error converting WCPS query to rasql query: E axis: subset (0.0:31.0) is out of bounds.

and in catalina.out:

TRACE [18:54:08] CrsUtil@800: Checking order, format and bounds of axis E ...
 ERROR [18:54:08] CrsUtil@848: Subset [0.0, 31.0] is out of coverage bounds [75042.72735943, 705042.72735943]
 ERROR [18:54:08] DimensionIntervalElement@249: Error while transforming geo-coordinates to pixel coordinates. The metadata is probably not valid.
 ERROR [18:54:08] Wcs2Servlet@261: Error stack trace:
InvalidSubsetting: Error converting WCPS query to rasql query: E axis: subset (0.0:31.0) is out of bounds.

Similar result repeat when using other scaling options, no matter the given parameters of scalesize or scaleextent are in grid coordinate or in georeferenced coordinate.

Change History (6)

comment:1 Changed 3 years ago by pcampalani

  • Status changed from new to accepted

Thanks for creating the ticket Xinghua: yes as discussed this is a critical bug in our WCS Scaling Extension. The systemtest which were added for securing it unluckily I see they target only IndexCRS coverages.

I can look at this not before some 10 days: if somebody will want to take it beforehand, just reassign it to him/herself.

comment:2 Changed 3 years ago by pcampalani

  • Keywords scale geo wcs added

comment:3 Changed 3 years ago by pbaumann

  • Cc j.yu added

comment:4 Changed 3 years ago by pcampalani

Fixed in changeset:81d7fca (new WCS systemtests n.5[5678] added).

Xinghua, please verify this then either close the ticket or let me know if some of issue persists.

comment:5 Changed 3 years ago by gxinghua

  • Resolution set to fixed
  • Status changed from accepted to closed

Still has some problems about factor scaling. Since a new ticket #788 has been created, this one should be close.

comment:6 Changed 3 years ago by pcampalani

Fix complete actually with changeset:5d16411 to fix a bad BigDecimal handling.

Note: See TracTickets for help on using tickets.