Opened 11 years ago
Closed 11 years ago
#786 closed defect (fixed)
WCS Scaling extension does not take slicings into account
Reported by: | Piero Campalani | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | major | Milestone: | 9.0.x |
Component: | petascope | Version: | development |
Keywords: | scaling slice | Cc: | |
Complexity: | Medium |
Description (last modified by )
When slicing a dimension with a WCS subset, the sliced dimension turns to a trim subset on the slicing-point, hence breaking the functioning of a query.
As a workaround, WCS slicing needs to be converted to a trim, although this is not a satisfactory workaround:
service=WCS& version=2.0.1& request=GetCoverage& coverageId=mr& + subset=i(100,100)& <== OK, but no slice - subset=i(100)& <== ERROR subset=j(100,104)& scalesize=j(4)
Change History (3)
comment:1 by , 11 years ago
Status: | new → accepted |
---|
comment:2 by , 11 years ago
Description: | modified (diff) |
---|
comment:3 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in changeset:81d7fca (new WCS systemtests n.5[5678] added).