Opened 11 years ago
Closed 10 years ago
#787 closed defect (duplicate)
WCS scaling extension wrongly maps scale-factor to WCPS
Reported by: | Piero Campalani | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | critical | Milestone: | 9.0.x |
Component: | petascope | Version: | development |
Keywords: | scale factor wcs | Cc: | xinghua |
Complexity: | Medium |
Description
WCS scaling extensions makes a wrong mapping to WCPS query in case of scale factors, turning lo
and hi
bounds to lo/factor
and hi/factor
bounds, but this breaks when lo
or hi
are 0 since the
service=WCS& version=2.0.1& request=GetCoverage& coverageId=mr& subset=i(0,7)& subset=j(0,7)& scalefactor=0.1
becomes:
select csv(scale( c[0:7,203:210], [0:70,2030:2100] )) from mr AS c
but the index extent then is scaled from 8 to 71 cells, while it should go to 80 cells.
Note:
See TracTickets
for help on using tickets.
See #788.