On Aug 19, 2009, at 11:46 AM, Michael Elsdörfer wrote: > Actually, after looking at the PostGIS code again, I realized how > straightforward it really is, and I quickly whipped something up: > > http://bitbucket.org/miracle2k/pyutils/changeset/156c60ec88f8/ > > Feel free to add this to Shapely if you want. > > I further realized that in my somewhat simplified use case, a simple > point.distance(linestring) query would be enough ;) > > One thing that is now still worrying me is this note on the Shapely > site: > > "There are several upstream issues with GEOS versions 2.2.3 and 3.0.0. > The GEOS WKT and WKB writers leak, and so therefore does access of a > geometry's *wkt* and *wkb* properties. There are smaller leaks > associated with creation of some geometry types." > > I'm writing a long-running server app, and memory leaks is not > something > I can just ignore. Is there any information as to which types are > affected? > > Michael
I think the WKT/WKB issue has been fixed in GEOS 3.1, but I haven't gotten around to testing it and so am hesitant to change the warning. The leaks that I'd noted in the GEOS tracker have been fixed, and so has been the LineString leak that Mateusz found: http://trac.osgeo.org/geos/search?q=leak&noquickjump=1&ticket=on Once I'm sure of which GEOS versions have the fixes, I'll update the wiki page. I wonder if your code on bitbucket couldn't be a rallying point for other programmers. I keep hearing about Shapely being used for geo- processing. I'll ask again on the list. Cheers, -- Sean _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
