Opened 6 years ago
Closed 6 years ago
#12348 closed Bugs (wontfix)
polygons intersection wrong answer
Reported by: | Owned by: | Barend Gehrels | |
---|---|---|---|
Milestone: | To Be Determined | Component: | geometry |
Version: | Boost 1.60.0 | Severity: | Problem |
Keywords: | Cc: |
Description
POLYGON((0 65536, 0 131072, 65536 131072, 131072 131072, 131072 65536, 65536 65536, 0 65536)) && POLYGON((65536 0, 65536 65536, 65536 131072, 65536 196608, 196608 196608, 196608 0, 65536 0)) intersection result is empty.
Attachments (1)
Change History (3)
by , 6 years ago
comment:1 by , 6 years ago
I confirm. If you try to version 1.59, the result - it is the intersection. At 1.61 - no intersection.
comment:2 by , 6 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
It overflows internally. Sorry, you have to use int64 if you have coordinates like this. We currently don't check this internally. Leaving it as wont fix for now.
Note:
See TracTickets
for help on using tickets.
test file reproducing this bug