https://svn.boost.org/trac10/ticket/8380 <p> Here is an example where using a relatively small number yields the correct result whereas using <em>boost::numeric::bounds&lt;int&gt;::highest()/2</em> yields a bad result when calling boost::geometry::sym_difference. </p> <p> My polygon type is <strong>oriented counter-clockwise</strong> and <strong>not closed</strong>, my point type is based on <strong>int</strong>. Based on using int, can you offer any guidance about the largest possible numbers ("domain of definition") that yield correct results in the boost geometry algorithms? </p> <p> Here is our conversation on the geometry mailing list regarding this issue in 1.48.0:<br /> <a class="ext-link" href="http://lists.boost.org/geometry/2012/02/1849.php"><span class="icon">​</span>http://lists.boost.org/geometry/2012/02/1849.php</a> </p> <p> For readability, I use the <code>^</code> operator to denote the call to sym_difference below. </p> <pre class="wiki">MULTIPOLYGON(((564 2394,1548 2850,2526 2916,2526 32767,564 32767))) ^ MULTIPOLYGON(((564 3252,2526 3252,2526 32767,564 32767))) correct result: MULTIPOLYGON(((564 3252,564 2394,1548 2850,2526 2916,2526 3252))) MULTIPOLYGON(((564 2394,1548 2850,2526 2916,2526 1073741823,564 1073741823))) ^ MULTIPOLYGON(((564 3252,2526 3252,2526 1073741823,564 1073741823))) bad result: MULTIPOLYGON(((564 3252,564 2394,1548 2850,2526 2916,2526 333411))) </pre> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/8380 Trac 1.4.3 Volker Schöch <vschoech@…> Thu, 14 Nov 2013 12:03:28 GMT