Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

Powered by ReviewNB

Glad to see this, definitely nice to have this updated. Quick clarification, does this update the bounding box and cross-section to be strictly between those bounds? So if I do a bounding box with a face center as the element, and a face center is inside the bounds but the whole face is not, will it include that face or not?

Not using KDTree queries will definitely speed things up though, so that is really good.

Glad to see this, definitely nice to have this updated. Quick clarification, does this update the bounding box and cross-section to be strictly between those bounds? So if I do a bounding box with a face center as the element, and a face center is inside the bounds but the whole face is not, will it include that face or not?

The subset.bounding_box() methods now use the Grid.bounds to accurately determine the bounding box, instead of using an approximate query.

So if I do a bounding box with a face center as the element, and a face center is inside the bounds but the whole face is not, will it include that face or not?

There is no longer an element needed, since we are not using the coordinates for the query, instead we use the actual geometry.