Opened 9 years ago
Closed 9 years ago
#1212 closed defect (fixed)
WCPS_Inconsistence when trimming at upper geo-referenced axis
Reported by: | Bang Pham Huu | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 10.0 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu, Alex Dumitru | |
Complexity: | Medium |
Description
a new test wcps query (eobstest with Long domain is (25, 75.5) or (0, 100) in grid axis)
query=for c in (eobstest) return encode( (c[ t("1950-01-02"), Long(75.5:85), Lat(10:15)]), "csv")
The problem is it is not limit the upper (≥75.5 )when converted to Rasql Query as it will converted to
select csv(c[1,101:120,121:131]) from eobstest AS c where oid(c)=46081 and returns {0,0,0,0,0,0,0,0,0,0,0},{0,0,0,0,0,0,0,0,0,0,0},....
instead of a WCPS query in below lower bound ( ⇐ 25) like
for c in (eobstest) return encode( (c[ t("1950-01-02"), Long(0.5:25), Lat(10:15)]), "csv")
which is translated to Rasql
select csv(c[1,-49:0,121:131]) from eobstest AS c where oid(c)=46081
and only returns
{-9999,-9999,-9999,-9999,-9999,-9999,-9999,-9999,-9999,-9999,-9999}
I think:
+ It should set the lower bound when query < lower bound, e.g (c[Long(25:25)] and higher bound when query > highger bound, e. (c[Long(75.5:75.5)].
+ It is also inconsistent from Rasql which is pointed out http://www.rasdaman.org/ticket/1049
Change History (2)
comment:1 by , 9 years ago
Priority: | major → minor |
---|
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Patch was accepted, close ticket.
wait for http://www.rasdaman.org/ticket/1049 (when query outside of bounding interval will throw an exception), e.g Long(75.5 80) or Long(0, 25) with bounding is (25, 75.5).