Custom Query (2765 matches)
Results (46 - 48 of 2765)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2767 | fixed | FIX - petascope throws exception on regular time axis if time slice is out of extent | ||
Description |
For example: This WMS GetMap request has a time slice which is out of the time's extent, and it should throw proper exception instead of trying to generate a rasql query: http://localhost:8080/rasdaman/ows?service=WMS&version=1.3.0&request=GetMap&layers=TOPSAR&bbox=-42.54421429899902,-65.61416625976562,-29.171667098999023,-55.18390145976562&time=2022-11-07T11:00:00.000Z&width=800&height=600&crs=EPSG:4326&format=image/png&transparent=true&styles= |
|||
#2764 | duplicate | Make petascope error messages more user friendly | ||
Description |
During a WCPS query. I was attempting to download a 3D coverage, like so: for $c in ( coverage_name ) return encode( $c, "image/tiff" ) And got the following XML error: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ows:ExceptionReport version="2.0.1" xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink"> <ows:Exception exceptionCode="RasdamanRequestFailed"> <ows:ExceptionText>Execution error 381 in line 1, column 8, near token encode: Error in convertor of the selected data exchange format.</ows:ExceptionText> </ows:Exception> <ows:Exception exceptionCode="RasdamanRequestFailed"> <ows:ExceptionText>Failed internal rasql query: SELECT encode(c, "image/tiff" , "{\"geoReference\":{\"crs\":\"EPSG:4326\",\"bbox\":{\"xmin\":-63.151668548583984,\"ymin\":-35.91914992988281,\"xmax\":-62.415750948583984,\"ymax\":-35.02583312988281}},\"metadata\":{\"Title\":\"This is the test coverage\"},\"nodata\":[-0.999]}") FROM single AS c </ows:ExceptionText> </ows:Exception> </ows:ExceptionReport> which was not so helpful. But looking at the logs I saw: /opt/rasdaman/log/rasserver.c9826559-15a8-46a2-8383-a72e38413f55.015212.log <== [INFO] - 2023-08-14 16:18:55,047: Request: 'SELECT encode(c, "image/tiff" , "{\"geoReference\":{\"crs\":\"EPSG:4326\",\"bbox\":{\"xmin\":-63.151668548583984,\"ymin\":-35.91914992988281,\"xmax\":-62.415750948583984,\"ymax\":-35.02583312988281}},\"metadata\":{\"Title\":\"This is the test coverage\"},\"nodata\":[-0.999]}") FROM single AS c'... parsing... checking semantics... evaluating... [ERROR] - 2023-08-14 16:18:55,108, qlparser/qtconversion.cc:290: Format conversion failed: Format conversion failed: cannot encode 3D array with the GDAL library, only 2D is supported rasdaman error 381: Execution error 381 in line 1, column 8, near token encode: Error in convertor of the selected data exchange format. Where this message: Format conversion failed: Format conversion failed: cannot encode 3D array with the GDAL library, only 2D is supported, would have been much more helpful from the client side. |
|||
#2763 | fixed | implement support for function atan2 | ||
Description |
rasdaman should support the atan2 function (and allow alias arctan2 for it). Properties:
One can follow (approximately) the implementation of the Start from the lexer lex.ll and parser oql.yy, then add the implementation in qtbinaryinduce.hh/cc after QtMod. Also add tests in systemtest/00-select, and document here. |