On Mon, Apr 27, 2009 at 11:47 AM, Aron Bierbaum aronbierb...@gmail.com wrote:
I have attached a patch for both GEOS and Shapely that we have been
testing with for a few weeks without any problems. Does anyone have a
better way to address this issue?
Pretty simple patch... more C-API changes.
Hi Aron,
From what we can tell our application was crashing
because memory that was being allocated in the GEOS dll was being
released inside of our application. When converting a GEOS geometry
object to a string, Shapely calls GEOSGeomToWKT_r which creates a char
buffer using std::malloc.
Paul Ramsey wrote:
On Mon, Apr 27, 2009 at 11:47 AM, Aron Bierbaum aronbierb...@gmail.com wrote:
I have attached a patch for both GEOS and Shapely that we have been
testing with for a few weeks without any problems. Does anyone have a
better way to address this issue?
Pretty simple
I have added a ticket for the issue. I was not sure exactly you wanted
for the version or milestone fields, but I gave it a shot.
http://trac.osgeo.org/geos/ticket/249
Thanks,
Aron
On Mon, Apr 27, 2009 at 3:17 PM, Paul Ramsey pram...@opengeo.org wrote:
In that case, Aron, can you put your
