Opened 5 years ago

Closed 5 years ago

#2028 closed defect (invalid)

rasql_null data values should be applied for all bands properly

Reported by: Bang Pham Huu Owned by: Dimitar Misev
Priority: major Milestone: 9.8
Component: rasql Version: 9.7
Keywords: Cc: Vlad Merticariu
Complexity: Medium

Description

Original input file (test_rgb) with 3 bands contains null values: 119 208 248

This rasql query select first 2 bands with specific nodata 119.0 and 208.0.

SELECT encode({c[10:10,333:333].0,c[10:10,333:333].1}, "json" , "{\"metadata\":{\"resolution\":\"1\"},\"nodata\":[119.0,208.0]}") FROM test_rgb AS c

However, the result returns 119 119 while it should be 119 208.

Change History (1)

comment:1 by Dimitar Misev, 5 years ago

Resolution: invalid
Status: newclosed

There is no bug, it works as expected according to documentation: http://doc.rasdaman.org/04_ql-guide.html#limitations

rasql can choose any null value of the null values set, which is {119, 208, 248}. Here it chose 119 for both values and that's correct.

Note: See TracTickets for help on using tickets.