Is it better to use the built-in bounding box intersection or a roll-your-own series of calculations if the bounding boxes are 2D rather than 3D? I’m assuming it’s pretty darn close but, let’s say you’re comparing several hundred thousand, which way would be faster?
I would think that anything within the limits of your RAM for the dataset would have similar results on those two, and bounding boxes are fairly simple to define - two points. Might be best to stick with the built in.
1 Like