Vissarion Fisikopoulos
Vissarion Fisikopoulos
OK it seems that there are several rutime errors (most probably due to accuracy issues) in formulas, buffer and overlay. Similar errors are encountered when compiling with the `-std=c++2a` flag...
@rconde01 could you tell us if https://github.com/boostorg/geometry/pull/1120 fixed your issue here?
A side note: the correct result is not empty, it is a triangle MULTIPOLYGON(((0 p1,1e-14 0,0 p2,0 p1))) where p1, p2 are intersection points of the segments (-10 50, 1e-14...
I can reproduce the issue. Probably a numerical issue. With `double` instead of `float` the results are as expected.
@jdmarsh could you please open a new issue with your example and data?
Indeed, there are places in the bibliography where Hausdorff distance is defined oriented or assymetric $h(A,B) = max_{a\in A}(min_{b\in B}(d(a,b))$ where $d(a,b)$ is the distance between $a$ and $b$. But...
Shouldn't the `cnc_container` expose its value type by something like `using value_type = Item;`
What version of boost are you using? Could you please share a minimal example so that we can reproduce it? In the current one there are undefined variables and syntactic...
Thanks for the report. After some quick workarounds I am getting `error: no matching function for call to ‘swap(const boost::polygon::point_data&, const boost::polygon::point_data&)’` triggered from https://github.com/boostorg/geometry/blob/develop/include/boost/geometry/algorithms/simplify.hpp#L537 Maybe the begin and end...
I have made a try, actually editing Jamfiles. I couldn't find a simpler way; it seems that b2 does not have an only build command. An alternative could be to...