#1845: v.buffer: strange result for lines
-----------------------------+----------------------------------------------
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: v.buffer, lines | Platform: Linux
Cpu: x86-64 |
-----------------------------+----------------------------------------------
Changes (by martinl):
* priority: normal => critical
Old description:
> Sample data attached: attachment:silnice.txt
>
> Buffer 1000m - OK (attachment:vector_1000.png)
>
> {{{
> v.buffer input=silnice output=silnice1000 distance=1000
> }}}
>
> Buffer 100m (using GEOS) - surprisingly wrong
> (attachment:vector_100_geos.png)
>
> {{{
> v.buffer input=silnice output=silnice100 distance=100
> }}}
>
> Buffer 100m (using GRASS) - wrong - not surprisingly
> (attachment:vector_100_grass.png)
>
> {{{
> export GRASS_VECTOR_BUFFER=1
> v.buffer input=silnice output=silnice100 distance=100
> }}}
New description:
Sample data attached: attachment:silnice.txt
Buffer 1000m - OK (attachment:v_buffer_1000.png)
{{{
v.buffer input=silnice output=silnice1000 distance=1000
}}}
Buffer 100m (using GEOS) - surprisingly wrong
(attachment:v_buffer_100_geos.png)
{{{
v.buffer input=silnice output=silnice100 distance=100
}}}
Buffer 100m (using GRASS) - wrong - not surprisingly
(attachment:v_buffer_100_grass.png)
{{{
export GRASS_VECTOR_BUFFER=1
v.buffer input=silnice output=silnice100 distance=100
}}}
--
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:1>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
