https://svn.boost.org/trac10/ticket/9934 <p> This might be a duplicate of <a class="new ticket" href="https://svn.boost.org/trac10/ticket/8419" title="#8419: Bugs: boost::geometry::intersection still broken with integer coordinates (new)">#8419</a>, <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/9081" title="#9081: Bugs: boost geometry booleans create self-intersecting polygons from ... (reopened)">#9081</a>, or <a class="new ticket" href="https://svn.boost.org/trac10/ticket/9909" title="#9909: Bugs: boost::geometry::intersection on two polygons returns incorrect result ... (new)">#9909</a>. </p> <p> Please see here: <a class="ext-link" href="http://stackoverflow.com/questions/23157391/taking-intersections-of-convex-hulls-in-boostgeometry"><span class="icon">​</span>http://stackoverflow.com/questions/23157391/taking-intersections-of-convex-hulls-in-boostgeometry</a> </p> <p> I ran into the same problems with using double coordinates instead of integer ones and thought switching to integer ones would be a sufficient workaround. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9934 Trac 1.4.3 anonymous Tue, 22 Apr 2014 10:59:33 GMT