Volker
Volker
My "tc::geo::polygon" type is actually a multi-polygon, using a polygon type that is based on **int**, oriented **counter-clockwise** and **open** (not closed). I am using **boost 1.70.0**. Please consider the...
Any chance this gets implemented any time soon? See our conversation here: https://lists.boost.org/geometry/2012/02/1838.php
This problem has been with us for a while. It did not occur in 1.55.0/1.59.0, then it did occur in 1.63.0/1.64.0/1.66.0, and **was fixed in 1.67.0**, see: https://svn.boost.org/trac10/ticket/12752 It then...
This problem has been with us for a while. I've seen it in 1.59.0/1.66.0, and it **was fixed in 1.67.0**, see: https://svn.boost.org/trac10/ticket/11676 It then did not occur in 1.75.0, and...
My "tc::geo::polygon" type is actually a multi-polygon, using a polygon type that is based on **int**, oriented **counter-clockwise** and **open** (not closed). I am using **boost 1.70.0**. Please consider the...
My `tc::geo::polygon` type is actually a **multi-polygon**, using a polygon type that is based on **int**, oriented **counter-clockwise** and **open** (not closed). I am using **boost 1.87.0**. Please consider the...
My `tc::geo::polygon` type is actually a **multi-polygon**, using a polygon type that is based on **int**, oriented **counter-clockwise** and **open** (not closed). I am using **boost 1.87.0**. Please consider the...
My `tc::geo::polygon` type is actually a **multi-polygon**, using a polygon type that is based on **double**, oriented **counter-clockwise** and **open** (not closed). I am using **boost 1.87.0**. We compile with...