Custom Query (2765 matches)
Results (31 - 33 of 2765)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1211 | fixed | WCPS1.5_Semantic Exception when slicing at geo-referenced axis | ||
Description |
for c in (eobstest) return encode( (c[ t("1950-01-02"), Long(35.5:35.5), Lat(10:15)]), "tiff", "nodata=0") which is translated to Rasql by WCPS 2.0 SELECT encode( ( c[1,21,121:130] ) , "GTiff" , "nodata=0;xmin=25.0;xmax=75.5;ymin=-40.5;ymax=75.5;crs=EPSG:4326") FROM eobstest AS c It will throw an exception <ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" version="2.0.0" xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd"> <ows:Exception exceptionCode="SemanticError"> <ows:ExceptionText> Error evaluating rasdaman query: 'SELECT encode( ( c[1,20,121:130] ) , "GTiff" , "nodata=0;xmin=25.0;xmax=75.5;ymin=-40.5;ymax=75.5;crs=EPSG:4326") FROM eobstest AS c </ows:ExceptionText> </ows:Exception> <ows:Exception exceptionCode="RasdamanRequestFailed"> <ows:ExceptionText> Error evaluating rasdaman query: 'SELECT encode( ( c[1,20,121:130] ) , "GTiff" , "nodata=0;xmin=25.0;xmax=75.5;ymin=-40.5;ymax=75.5;crs=EPSG:4326") FROM eobstest AS c </ows:ExceptionText> </ows:Exception> <ows:Exception exceptionCode="RuntimeError"> <ows:ExceptionText> org.odmg.QueryException : Unexpected internal server error. </ows:ExceptionText> </ows:Exception> </ows:ExceptionReport> while this is translated Rasql by WCPS 1.0 and returns a coverage select encode(c[1,21:21,121:131], "GTiff", "nodata=0;xmin=35.5;xmax=35.5;ymin=10.0;ymax=15.0;crs=EPSG:4326") from eobstest AS c where oid(c)=46081 I think this is problem with convert 1 D to tiff but not sure why WCPS 1.0 can run normally and WPCS 2.0 returns exception? |
|||
#1212 | fixed | WCPS_Inconsistence when trimming at upper geo-referenced axis | ||
Description |
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 |
|||
#1216 | invalid | Rasql returns -inf when divide by 0 | ||
Description |
WCPS query for c in (eobstest) return encode(c[t(0:20), Lat(0:0), Long(25:65)] /0, "csv") which returns {{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf},{-inf}, I think an exception in Rasql to know error divide by 0 is better? |