Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

self-intersection of connected segment list not checked #2

Open
GoogleCodeExporter opened this issue Aug 25, 2015 · 1 comment
Open

self-intersection of connected segment list not checked #2

GoogleCodeExporter opened this issue Aug 25, 2015 · 1 comment
Labels
auto-migrated Priority-Low Type-Defect

Comments

@GoogleCodeExporter
Copy link 

In class domain constructor,
currently the topology-checking is only that connected segment pieces don't
fall outside the primary domain. We should eventually check for
self-intersections of each analytic segment, and intersections with other
segments in the same list.

Original issue reported on code.google.com by [email protected] on 3 Jul 2008 at 11:51
@GoogleCodeExporter
Copy link
Author 

this type of geometry checking is hard. we have to trust the user checks their 
own
geometry somewhat.

Original comment by [email protected] on 16 Jul 2009 at 6:18

  • Added labels: Priority-Low
  • Removed labels: Priority-Medium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Low Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter