After a lot of work, I have finally trimmed these hexagons the way I want them. But you can see when I choose Item 1 (second item) it picks the correct surface 5 times. The 6th time it doesn’t? Any suggestions before I do this by hand? I have to make one more ring of hexagons, so I’d like to learn why its making these choices.
Thanks.
You could also take the center point of each hexagon and evaluate the surface you were originally splitting at the srf cp, and use the surface parameters to sort.
Sorting geometry by various means is common. I included three clusters (open source) in the cyan group that I often use. Sorting by edge length instead of area can be useful and is much faster when there are thousands to sort.
P.P.S. I keep the clusters in the cyan group as “User Objects”, always handy, created like this:
in my -little- experience, if all the geometrical inputs are well sorted also the geometrical outputs will be well sorted
for instance, in your starting situation you provide 6 surfaces and 6 lines and let the SplitSurface component do its job with the data he gets… if you jitter the inputs you will get similar results
if, instead, you provide two data trees:
→ surfaces: 6 branches with one surface per branch
→ curves: 6 branches with left and right curve-cutters for each branch
then the very same component will output a well sorted data tree:
it’s not wrong at all to sort the output surfaces, but if doesn’t take a huge effort to create well-organized input data trees, then I’d suggest that as best practice