Im just spit balling here off the top of my head, so could be totaly wrong.
table would need all values from 0 to 200 in X Y an Z (presuming 200x200x200 build area)
even limiting to 2dp (100 points between intergers) thats 20,000 rows, * 3 dimentions = 8,000,000,000,000 rows of data!
thats 8 terabytes just for the index. * what ever your datasize your storing..
sure you could optimise this to only list the points that are used.... but would still be very large and I suspect would take a long time to compute all the pints in advance.
Sure it could be done... but it would be insane!
table would need all values from 0 to 200 in X Y an Z (presuming 200x200x200 build area)
even limiting to 2dp (100 points between intergers) thats 20,000 rows, * 3 dimentions = 8,000,000,000,000 rows of data!
thats 8 terabytes just for the index. * what ever your datasize your storing..
sure you could optimise this to only list the points that are used.... but would still be very large and I suspect would take a long time to compute all the pints in advance.
Sure it could be done... but it would be insane!