Correctness of `intersect` operation in Sand3D, specifically preventing it from returning geometry outside the clipping tool's bounds.
Raw Developer Origin & Technical Request
GitHub Issue
Nov 9, 2026
In the reproduction below, `intersect` returns geometry outside the clipping box. The box spans **Z = 611 to 780**, but the result reaches **Z = 64**.
The input rail comes from a difficult, potentially degenerate Boolean construction. This report does not assume that the intersection must succeed on that input. The question is whether Sand3D should detect and report a result that cannot belong to both operands.
### Reproduction
```python
import bpy
import sand3d as s
s.empty_scene()
plan = [(-2404,65),(-2070,577),(-1653,1159),(-1237,1491),(39,1773),(2374,1738)]
bottom = [(-2404,632),(-2153,220),(-1915,64),(-1706,85),(2374,85)]
a = s.body('outer', plan=plan, top=1928, bottom=bottom, n=2.6)
b = s.body('inner', plan=[(y,max(w-260,65)) for y,w in plan], top=1927.9,
bottom=[(y,z+0.1) for y,z in bottom], n=2.6)
rail = s.cut(a,b)
result = s.intersect(rail, s.at(s.box('band',w=3546,d=9620,h=169),z=611))
zs = [v.co.z for v in result.data.vertices]
print(bpy.app.version_string, len(result.data.polygons), min(zs), max(zs))
# Every point of an intersection must belong to both operands' bounding boxes.
assert min(zs) >= 611 - 1e-3 and max(zs)
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from Sandflow-ai/sand3d.
Frequently Asked Questions
Market intelligence mapped to Correctness of `intersect` operation in Sand3D, specifically preventing it from returning geometry outside the clipping tool's bounds..
How is Correctness of `intersect` operation in Sand3D, specifically preventing it from returning geometry outside the clipping tool's bounds. positioned in the market?
Which technical concepts are associated with Correctness of `intersect` operation in Sand3D, specifically preventing it from returning geometry outside the clipping tool's bounds.?
Engagement Signals
Cross-Market Term Frequency
Counts stored text matches for foundational terms like plan and intersect in analysed public discussions. These counts do not measure adoption.
Stored text matches, not adoption or market-share measurements.
- plan: 60 records
- intersect: 6 records
- bottom: 5 records
- bpy: 3 records
- clipping box: 1 records
- geometry outside the clipping box: 1 records
- Z = 611 to 780: 1 records
- Z = 64: 1 records
- degenerate Boolean construction: 1 records
- sand3d as s: 1 records
- s.empty_scene(): 1 records
- s.body('outer', plan=plan, top=1928, bottom=bottom, n=2.6): 1 records
- s.body('inner', plan=[(y,max(w-260,65)) for y,w in plan], top=1927.9, bottom=[(y,z+0.1) for y,z in bottom], n=2.6): 1 records
- rail = s.cut(a,b): 1 records
- result = s.intersect(rail, s.at(s.box('band',w=3546,d=9620,h=169),z=611)): 1 records
- zs = [v.co.z for v in result.data.vertices]: 1 records
- min(zs): 1 records
- max(zs): 1 records
- bpy.app.version_string: 1 records
- len(result.data.polygons): 1 records
- assert min(zs) >= 611 - 1e-3 and max(zs): 1 records
SaaS Metrics