Fix covered_by incorrect results #1283
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| calc_t s1 = get<0>(seg1); | ||
| calc_t s2 = get<0>(seg2); | ||
|
|
||
| // In case of a segment that contains a pole endpoint we need an arbitrary but consistant |
vissarion
force-pushed
the
fix/covered_by_multiple_poles
branch
2 times, most recently
from
1f03912
to
f90952c
Compare
vissarion
force-pushed
the
fix/covered_by_multiple_poles
branch
from
f90952c
to
aa840ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix covered_by incorrect results for polygons with multiple defined points as a pole.
Resolves #1279 (the special case arise as part of issue #1161)