For proper partition elimination we should load min and max for all attributes.
Often happens that the selection, range or point, happens not only in X and Y, but also in one of the attributes such as classification_number.
This becomes more relevant for AHN3 where we load 9 attributes in addition to x, y, z.
I'll try to work on this during this week. I'll let you know when something is ready. If I remember correctly that part of the code needs a bit of attention anyway...
For proper partition elimination we should load min and max for all attributes. Often happens that the selection, range or point, happens not only in X and Y, but also in one of the attributes such as classification_number.
This becomes more relevant for AHN3 where we load 9 attributes in addition to x, y, z.