Opened 9 years ago

Closed 8 years ago

#1203 closed defect (invalid)

WCPS1.5_Difference values between same interval from coverage[scalar] and coverage[expression]

Reported by: Bang Pham Huu Owned by:
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: scalar, interval, Cc: Dimitar Misev, Vlad Merticariu, Alex Dumitru
Complexity: Medium

Description

Below is another example which returns 2 different values but same scalar interval (c[j(0)] and c[j(0+0)])

+ This returns 36

http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=ProcessCoverages
&query=for c in (mr) return max(c[j(0)])&wcpsVersion=2.0

+ This returns 15

http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=ProcessCoverages
&query=for c in (mr) return max(c[j(0+0)])&wcpsVersion=2.0

Change History (4)

comment:1 by Bang Pham Huu, 9 years ago

Cc: Dimitar Misev Vlad Merticariu Alex Dumitru added

comment:2 by Bang Pham Huu, 9 years ago

Summary: WCPS2.0_Difference values between same interval from coverage[scalar] and coverage[expression]WCPS1.5_Difference values between same interval from coverage[scalar] and coverage[expression]

comment:3 by Bang Pham Huu, 9 years ago

The problem with this ticket (also with WCPS 1.0) due to it does not calculate the expression in petascope and convert to grid coordinate (e.g: c[j(0)] = c[210] in grid coordinate), then c[j(0 + 0)] = c[0] in grid coordinate.

Ticket http://rasdaman.org/ticket/1239 will fix this and in this ticket will need to test it by a test case.

comment:4 by Bang Pham Huu, 8 years ago

Milestone: 10.09.3
Resolution: invalid
Status: newclosed

In current WCPS 1.5, we don't support a numeric expression inside interval (e.g: c[i(1+1)]) but if it has the axis iterator variable then no problem (e.g: c[i($px + 1)]).

Note: See TracTickets for help on using tickets.