Boost C++ Libraries: Ticket #9162: intersects returns incorrect result in spherical equatorial https://svn.boost.org/trac10/ticket/9162 <p> Hi, </p> <p> The intersects does not return the correct result for point in polygon with spherical equatorial. These are two cases: </p> <ol><li>a polygon with pole (north/south) in it </li></ol><blockquote> <p> assume polygon PL: POLYGON((0 80,-90 80, -180 80, 90 80, 0 80)) a point P: POINT(0 90) </p> </blockquote> <p> </p> <pre class="wiki">boost::geometry::intersects(P, PL) </pre><blockquote> <p> should return TRUE, but return false in boost 1.54. </p> </blockquote> <ol start="2"><li>point in the opposite side of the polygon </li></ol><blockquote> <p> assume polygon PL: POLYGON((30 0,30 30,90 30, 90 0, 30 0)) a point P: POINT(-120 21) </p> </blockquote> <p> </p> <pre class="wiki">boost::geometry::intersects(P, PL) </pre><blockquote> <p> should return FALSE, but return true in boost 1.54. </p> </blockquote> <p> The issue may be caused by the spherical_side_formula can not handle this two cases. </p> <p> Attachment is the test case for these two issues. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9162 Trac 1.4.3 anonymous Wed, 25 Sep 2013 04:49:45 GMT attachment set https://svn.boost.org/trac10/ticket/9162 https://svn.boost.org/trac10/ticket/9162 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">intersectstest.cpp</span> </li> </ul> <p> Sample test </p> Ticket awulkiew Mon, 06 Jun 2016 15:13:52 GMT status, milestone changed; keywords, resolution set https://svn.boost.org/trac10/ticket/9162#comment:1 https://svn.boost.org/trac10/ticket/9162#comment:1 <ul> <li><strong>keywords</strong> within intersects spherical added </li> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> <li><strong>milestone</strong> <span class="trac-field-old">To Be Determined</span> → <span class="trac-field-new">Boost 1.61.0</span> </li> </ul> <p> Thanks! The bug was located in <code>winding</code> strategy which was "scanning" segments using the second coordinate (latitude). In cartesian CS this is ok but in spherical and geographic it isn't. Fixed in Boost 1.61. </p> Ticket