Custom Query (2765 matches)

Subsetting does not behave very consistently, depending on the actual tiles I'd say (discovered in ticket #1036).

Subsetting needs to conform with SQL/MDA, i.e. the subset must be within the array sdom.

Anything else, e.g. a subset that intersects or is completely outside of the array sdom is an exception: "subset S not within array domain D".

Currently we have dedicated systemtest in source:systemtest/testcases_mandatory/test_subsetting the queries should be verified that they produce the correct outputs or errors.

Rasdaman oids are longs, but in the code(eg raslib/oid.hh) they are stored as double. This is a potential source of bugs and should be changed.

A query using test_grey3d (assumes domain [0:99,0:99,0:4]):

select condense + over i in [0:4]
   using a[0:99,0:99,i]
   where avg_cells(a[0:99,0:99,i]) > 30
from test_grey3d as a

fails with:

rasdaman error 300: Parsing error 300 in line 3, column 4: Unexpected name where.

It should correctly parse the where in the condenser, and then evaluate it: only the array slices for which avg_cells(a[0:99,0:99,i]) > 30 is true should be added up in the condenser.