[GRASS-dev] [GRASS GIS] #1845: v.buffer: strange result for lines

GDAL · January 4, 2013, 1:43pm

#1845: v.buffer: strange result for lines
-----------------------------+----------------------------------------------
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: v.buffer, lines | Platform: Linux
Cpu: x86-64 |
-----------------------------+----------------------------------------------
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
}}}

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 4, 2013, 1:46pm

#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>

GDAL · January 4, 2013, 2:12pm

#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 |
-----------------------------+----------------------------------------------

Comment(by mmetz):

Replying to [ticket:1845 martinl]:
> Sample data attached: attachment:silnice.txt
>
> Buffer 100m (using GEOS) - surprisingly wrong
(attachment:v_buffer_100_geos.png)

Works for me. Do you have any changes in your local copy?
>
{{{
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
}}}
>

Looks better for me, but still with errors.

I'm using GEOS-3.3.6.

Markus M

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:2>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 4, 2013, 2:37pm

#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 |
-----------------------------+----------------------------------------------

Comment(by martinl):

Replying to [comment:2 mmetz]:
> Works for me. Do you have any changes in your local copy?

hm, it fails only with original binary map (attachment:silnice.pack), not
with imported ascii map.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:3>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 4, 2013, 2:49pm

#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 |
-----------------------------+----------------------------------------------

Comment(by mmetz):

Replying to [comment:3 martinl]:
> Replying to [comment:2 mmetz]:
> > Works for me. Do you have any changes in your local copy?
>
> hm, it fails only with original binary map (attachment:silnice.pack),
not with imported ascii map.

The original binary map is 3D, the imported ascii map is 2D. I guess one
of the cleaning tools does not work with 3D output, even though v.buffer
creates 2D output. Strange.

Markus M

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:4>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 4, 2013, 2:57pm

#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, 3D input | Platform: Linux
Cpu: x86-64 |
---------------------------------------+------------------------------------
Changes (by martinl):

* keywords: v.buffer, lines => v.buffer, lines, 3D input

Comment:

Replying to [comment:4 mmetz]:
> The original binary map is 3D, the imported ascii map is 2D. I guess one
of the cleaning tools does not work with 3D output, even though v.buffer
creates 2D output. Strange.

I overlooked it, good point.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:5>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 4, 2013, 4:16pm

#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, 3D input | Platform: Linux
Cpu: x86-64 |
---------------------------------------+------------------------------------

Comment(by mmetz):

Should be fixed in r54529.

Markus M

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:6>
GRASS GIS <http://grass.osgeo.org>

GDAL · January 5, 2013, 1:16pm

#1845: v.buffer: strange result for lines
-----------------------+----------------------------------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: critical | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Resolution: fixed | Keywords: v.buffer, lines, 3D input
  Platform: Linux | Cpu: x86-64
-----------------------+----------------------------------------------------
Changes (by martinl):

* status: new => closed
* resolution: => fixed

Comment:

Replying to [comment:6 mmetz]:
> Should be fixed in r54529.

Confirmed, thanks for super-quick fix.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1845#comment:7>
GRASS GIS <http://grass.osgeo.org>