[GRASS-dev] Re: [bug #2765] (grass) v.buffer produces strange results

[Hamish]

Maciek Sieczka via RT wrote:
> 
> Note there is no single difference between the 2 *besides* the order
> in which boundaries are listed. Somehow, the ditch_1205 having
> boundary #4 listed as first is wrong for v.buffer (on my machine),
> while the ditch_1205_edt, having the same boundary listed as the last
> one, is OK.
> 
> Does this finding help?

Yes. It is excellent information. (but no solution yet)

another test:
  v.build.polylines in=ditch_1205 out=ditch_1205_single
  v.buffer ditch_1205_single out=ditch_1205_single_b4 type=area buffer=4



Could others try buffering this area? Maybe it fails for someone else?

GRASS> v.in.ascii out=ditch_1205 form=standard -n << EOF
B  4
 600727.68682251 5677973.32091602
 600739.16582305 5678137.49568095
 600736.32863997 5678140.4618269
 600730.63832718 5678056.67823368
B  2
 600730.63832718 5678056.67823368
 600725.02385533 5677974.01131491
C  1 1
 600730.04890192 5678035.56666655
 1     1205
B  2
 600727.68682251 5677973.32091602
 600725.02385533 5677974.01131491
EOF

# and then:
GRASS> v.buffer ditch_1205 out=ditch_1205_b1 type=area buffer=1
GRASS> v.buffer ditch_1205 out=ditch_1205_b4 type=area buffer=4


?
Hamish