Opened 7 years ago
Last modified 6 years ago
#12125 assigned Bugs
Another problems performing boolean operations on polygons with shared edges
| Reported by: | Owned by: | Barend Gehrels | |
|---|---|---|---|
| Milestone: | Boost 1.63.0 | Component: | geometry |
| Version: | Boost 1.61.0 | Severity: | Problem |
| Keywords: | union multipolygon sharededge | Cc: |
Description
Trying to solve problems with union_ operation on mpolygons with shared edges (https://svn.boost.org/trac/boost/ticket/12118) with help of boost 1.61.0 beta. But instead of getting problems with zero areas, I'm getting really wrong result.
For example
currentPath
MULTIPOLYGON(((-5.96064376831054687500 -17.19871711730957031250,7.83307075500488281250 -32.98977279663085937500,8.81292819976806640625 -34.11151504516601562500,19.66869926452636718750 -14.42036247253417968750,-5.96064376831054687500 -17.19871711730957031250)),((-14.87041568756103515625 -6.99879980087280273438,-16.12161636352539062500 -18.30021858215332031250,-5.96064376831054687500 -17.19871711730957031250,-14.87041568756103515625 -6.99879980087280273438)))
appended Polygon
MULTIPOLYGON(((7.83307075500488281250 -32.98977279663085937500,8.81292819976806640625 -34.11151504516601562500,13.00057315826416015625 -33.85240554809570312500,7.83307075500488281250 -32.98977279663085937500)),((-22.50806808471679687500 -27.92480468750000000000,7.83307075500488281250 -32.98977279663085937500,-14.87041568756103515625 -6.99879980087280273438,-22.50806808471679687500 -27.92480468750000000000)))
Union result (same as currentPath, appended Polygon was totally ignored)
MULTIPOLYGON(((-5.96064376831054687500 -17.19871711730957031250,7.83307075500488281250 -32.98977279663085937500,8.81292819976806640625 -34.11151504516601562500,19.66869926452636718750 -14.42036247253417968750,-5.96064376831054687500 -17.19871711730957031250)),((-14.87041568756103515625 -6.99879980087280273438,-16.12161636352539062500 -18.30021858215332031250,-5.96064376831054687500 -17.19871711730957031250,-14.87041568756103515625 -6.99879980087280273438)))
Change History (4)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Milestone: | To Be Determined → Boost 1.63.0 |
|---|---|
| Status: | new → assigned |
comment:3 by , 7 years ago
By the way, this one (but not 12118) runs fine using the define BOOST_GEOMETRY_NO_ROBUSTNESS This turns of the rescaling (which was designed to solve cases, and it does, but in the end it also breaks cases such as this one)
comment:4 by , 6 years ago
Hi, Barend!
Sorry for bothering. Is there a chance that those issues will be fixed in 1.63? Thanks!
Thanks for the report. Indeed output is empty. Same as for ticket 12118 reported by you, it will hopefully be solved in 1.63 Sorry for the inconvenience.