On Tue, Mar 01, 2016 at 03:41:37PM +0100, Mateusz Loskot wrote:
> On 1 March 2016 at 15:09, Sandro Santilli wrote:
> > On Tue, Mar 01, 2016 at 02:52:32PM +0100, Mateusz Loskot wrote:
> >
> >> What about constructing a single LineString from connected
> >> segments, instead of a
On 1 March 2016 at 16:06, Sandro Santilli wrote:
> On Tue, Mar 01, 2016 at 03:41:37PM +0100, Mateusz Loskot wrote:
>> On 1 March 2016 at 15:09, Sandro Santilli wrote:
>> > On Tue, Mar 01, 2016 at 02:52:32PM +0100, Mateusz Loskot wrote:
>> >
>> >> What about
On 1 March 2016 at 15:09, Sandro Santilli wrote:
> On Tue, Mar 01, 2016 at 02:52:32PM +0100, Mateusz Loskot wrote:
>
>> What about constructing a single LineString from connected
>> segments, instead of a MultiLineString?
>
> LineMerge operation, aka GEOSLineMerge_r in C-API.
On Tue, Mar 01, 2016 at 02:52:32PM +0100, Mateusz Loskot wrote:
> What about constructing a single LineString from connected
> segments, instead of a MultiLineString?
LineMerge operation, aka GEOSLineMerge_r in C-API.
--strk;
___
geos-devel mailing
On 29 February 2016 at 20:10, Sandro Santilli wrote:
> On Mon, Feb 29, 2016 at 07:18:08PM +0100, Mateusz Loskot wrote:
>> Hi,
>>
>> I've started adding tests for OverlayOp [1] and I noticed
>> curious results for basic test case.
>>
>> OverlayOp(UNION) on Four segments of a sqare
On Mon, Feb 29, 2016 at 07:18:08PM +0100, Mateusz Loskot wrote:
> Hi,
>
> I've started adding tests for OverlayOp [1] and I noticed
> curious results for basic test case.
>
> OverlayOp(UNION) on Four segments of a sqare
> always construct a MultiLineString.
> I'd have expected a polygon,
Hi,
I've started adding tests for OverlayOp [1] and I noticed
curious results for basic test case.
OverlayOp(UNION) on Four segments of a sqare
always construct a MultiLineString.
I'd have expected a polygon, shouldn't I?
In this case, I noticed OverlayOp always labels edges
as UNDEF or