#1119: Buffer memory issue
------------------------+---------------------------
Reporter: kalenik | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.9.2
Component: Default | Version: 3.9.0
Severity: Unassigned | Resolution:
Keywords: |
------------------------+---------------------------
Comment (by mdavis):
There are indeed issues with the memory usage of the current buffer
algorithm - see [https://trac.osgeo.org/geos/ticket/344 GEOS-344] and
[https://trac.osgeo.org/geos/ticket/693 GEOS-693] for examples.
As Paul says, there is no easy fix for this. So trying to condition the
inputs or the process is the only short-term solution.
I note that you are buffering with a distance of 99,999,999 and that the
provided sample geometry has an extent of only about 400,000. Also, the
geometry is fairly complex (420K points with 1203 holes). Computing a
buffer that big on that kind of geometry is pushing the buffer algorithm
way out of it's normal operating regime, and it basically is just going to
produce a roundish blob anyway.
One thing you can do is to buffer at a sequence of 2 or more increasing
values. In this case you could use a distance of 1,000,000, and then
buffer at the 99,999,999 value.
I also wonder what exactly you are trying to do? That buffer distance of
99,999,999 looks highly artificial.
--
Ticket URL: <https://trac.osgeo.org/geos/ticket/1119#comment:7>
GEOS <http://trac.osgeo.org/geos>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite
(JTS).
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
