On Tue, Apr 5, 2011 at 9:40 AM, Maris Nartiss <[email protected]> wrote: > Hello, > I'm totally lost in v.buffer/2 issues. I recompiled v.buffer and > v.buffer2 on 6.5 and was trying out different use cases from trac. All > of them where working fine with v.buffer2. Old v.buffer was still > failing with landcover dataset.
Hmph. Updated v.buffer indeed fails with spearfish landcover map. > I had not tested attribute based > buffering, as it should not be hard to fix buffering by attribute if > in general it works fine. > Buffering by attributes is now working in both versions. Both versions still have different problems with generating and cleaning buffers. > Can anyone give me sample data that triggers failure of v.buffer2? > E.g. in nc_spm with roadsmajor: v.buffer2 input=roadsmajor@PERMANENT output=roadsmajor_buf2_2000 distance=2000 fails, but works fine with updated v.buffer v.buffer input=roadsmajor@PERMANENT output=roadsmajor_buf1_2000 distance=2000 v.parallel2 has more issues than v.buffer2 (see tickets #1231 and #1244). According to the relevant thread in the grass-dev ml [1], I got the impression that Rosen Matev was aware of the problem with parallel lines, but did not get around to fix it [2] (last mail of [1]). Markus M [1] http://thread.gmane.org/gmane.comp.gis.grass.devel/27534/ [2] http://article.gmane.org/gmane.comp.gis.grass.devel/28445 _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
