On Wed, Feb 10, 2010 at 12:00:31PM +0100, Roger Bivand wrote:
I've tried to go through GEOSPolygonize() to put the MULTILINESTRING
together again, and am analysing what has happened, but think that the
output has lost hole attributions, so needs running through GEOSContains
or similar.
On Sat, Feb 06, 2010 at 09:13:46PM +, Mateusz Loskot wrote:
Mateusz Loskot wrote:
mlos...@dog:~/dev/geos/_svn/trunk$ svn-clean
By the way, if you are suspicious about some remaining garbage in the
source tree, just run svn-clean and confirm you have trunk up-to-date
with nothing
On Wed, 10 Feb 2010, strk wrote:
On Wed, Feb 10, 2010 at 02:44:44PM +0100, Roger Bivand wrote:
On Wed, 10 Feb 2010, strk wrote:
On Wed, Feb 10, 2010 at 12:35:46PM +0100, Roger Bivand wrote:
Are GEOSSymDifference() and GEOSIntersection() intended to take at least
POLYGON inputs, and then
I'd like to deprecate non-thread-safe version
of CAPI interface in next release, and stop providing
them for new methods.
If anyone sees a reason not to do that please scream
before it's too late (you've plenty of time).
--strk;
() Free GIS Flash consultant/developer
/\
On Feb 10, 2010, at 5:26 PM, strk wrote:
I'd like to deprecate non-thread-safe version
of CAPI interface in next release, and stop providing
them for new methods.
If anyone sees a reason not to do that please scream
before it's too late (you've plenty of time).
The proposal would be to
On Wed, 10 Feb 2010, Howard Butler wrote:
On Feb 10, 2010, at 5:26 PM, strk wrote:
I'd like to deprecate non-thread-safe version
of CAPI interface in next release, and stop providing
them for new methods.
If anyone sees a reason not to do that please scream
before it's too late (you've
