Subject: Re: [geometry] ring, multi_polygon concepts too limited or not
From: Barend Gehrels (barend_at_[hidden])
Date: 2013-09-03 16:10:32
On 3-9-2013 1:40, Barend Gehrels wrote:
> Sorry for these calls of, indeed, non-concept method. They should be
> fixed. .back() is easy to avoid.
> Range is enough for const Rings. But here (and also in wkt) polygons
> must be written. As was also recently on the list. There are no
> standard concepts we can use (such as in Boost.Range), so we made a
> minimum traits class ourselves. But apparently it is not yet called
> everywhere, indeed we have no unit-tests yet for classes as yours. The
> traits also have to be extended by something to erase a point from a
> It will be fixed.
The issues you reported are fixed in the SVN Trunk. Are you using Trunk?
Could you verify if your intersection is working for your Ring/MultiPolygon?
Geometry list run by mateusz at loskot.net