Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open line splitting and tagging vs clipping #913

Open
bradphelan opened this issue Nov 7, 2024 · 0 comments
Open

Open line splitting and tagging vs clipping #913

bradphelan opened this issue Nov 7, 2024 · 0 comments

Comments

@bradphelan
Copy link

bradphelan commented Nov 7, 2024

Simply clipping is that act of splitting a set into two and then discarding one or other of the sets. But sometimes it is useful to have both sets. ie: a Split operations rather than a Clip operation. Unfortunately with the current API only Clip in that only one of the two sets during a split is returned.

We have one specific use case for this which is. Often when clipping we want to specify that any gaps of length less than some epsilon should not be clipped and should be filled with the original sub curve that would have been removed. This would be easy to do if clipper returned both sets with the same topology but the split points marked and sub curves tagged.

Currently we have a complex algorithm that tries to match up connected section by running the algorithm twice, once for INTERSECT and the other for DIFFERENCE and trying to align the results which seems like we are trying to recover information that clipper internally has somehow thrown away.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant