Trying to buffer a number of polygons - but only one polygon at a time.
There doesn't seem by eye to be any difference in the complexity of the polygons, but some of them cause v.buffer to stall at "Buffering Areas - 100%" and not complete. It didn't complete left overnight. Other, similar polygons complete in about 20 seconds.
It's not reporting any errors...
Running:
Grass-GIS 6.4.0RC5 on OSX 10.4.1
Richard
I've just run the operation in about three hours on an Acer laptop under Puppy Linux, using an old version of v.buffer (from Grass-GIS 6.2, which I had compiled so as to retain the debug=buffer option).
So there's something about v.buffer in Grass-GIS 6.4 that's making it stall on maps that an older version can process.
But it's not reporting any errors - so what's the best approach to identifying what's wrong, so I can file a bug?
Hello,
at first - try rc7
second - g.gisenv set=DEBUG=5
third (best one) - provide sample data with steps to reproduce Your issue.
WBR,
Maris.
2010/8/28 Richard Chirgwin <rchirgwin@ozemail.com.au>:
Further to my first message:
Hi,
Trying to buffer a number of polygons - but only one polygon at a time.
There doesn't seem by eye to be any difference in the complexity of the
polygons, but some of them cause v.buffer to stall at "Buffering Areas -
100%" and not complete. It didn't complete left overnight. Other, similar
polygons complete in about 20 seconds.
It's not reporting any errors...
Running:
Grass-GIS 6.4.0RC5 on OSX 10.4.1
Richard
I've just run the operation in about three hours on an Acer laptop under
Puppy Linux, using an old version of v.buffer (from Grass-GIS 6.2, which I
had compiled so as to retain the debug=buffer option).
So there's something about v.buffer in Grass-GIS 6.4 that's making it stall
on maps that an older version can process.
But it's not reporting any errors - so what's the best approach to
identifying what's wrong, so I can file a bug?