[GRASS-dev] [GRASS GIS] #3448: v.buffer native failures

[Markus Metz]

On Thu, Aug 23, 2018 at 1:39 PM Stefan Blumentrath <
Stefan.Blumentrath at nina.no> wrote:
>
> Hi Marcus,
>
> I am not too familiar with C and the like so I might confuse some things
here...
>
> I noticed that using .buffer() in PyGRASS gives a lot of "using native
format" output.

this "using native format" refers to the format of newly created vector
maps (could also be OGR via v.external.out)
>
> So I looked it up and it seems to be using native buffering
(Vect_area_buffer2):
>
https://trac.osgeo.org/grass/browser/grass/trunk/lib/python/pygrass/vector/geometry.py#L1654
>
> And Vect_area_buffer2 is the non-geos buffering, right?
>
https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.buffer/main.c#L564
>
> So, should then PyGRASS be changed/fixed to use geos buffering too?

all vector buffering functions in the vector libs are GRASS native
functions, only the module v.buffer uses GEOS buffering. That means you
should use v.buffer instead of vector library functions.

> Shall I open a ticket?

yes please, pygrass should use the module v.buffer, or GEOS functions

Markus M
>
> Cheers,
> Stefan
>
>
> -----Original Message-----
> From: grass-dev <grass-dev-bounces at lists.osgeo.org> On Behalf Of GRASS GIS
> Sent: onsdag 22. august 2018 22:07
> Cc: grass-dev at lists.osgeo.org
> Subject: Re: [GRASS-dev] [GRASS GIS] #3448: v.buffer native failures
>
> #3448: v.buffer native failures
> --------------------------+---------------------------------
>   Reporter:  marisn       |      Owner:  grass-dev@…
>       Type:  defect       |     Status:  closed
>   Priority:  normal       |  Milestone:  7.6.0
>  Component:  Vector       |    Version:  unspecified
> Resolution:  wontfix      |   Keywords:  v.buffer v.parallel
>        CPU:  Unspecified  |   Platform:  Unspecified
> --------------------------+---------------------------------
> Changes (by mmetz):
>
>  * status:  new => closed
>  * resolution:   => wontfix
>
>
> Comment:
>
>  This is a long known issue and the reason why v.buffer uses GEOS
 buffering. GRASS native buffering will probably not be fixed because GEOS
 buffering is working, thus closing as won't fix.
>
> --
> Ticket URL: <https://trac.osgeo.org/grass/ticket/3448#comment:4>
> GRASS GIS <https://grass.osgeo.org>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180823/647f63b7/attachment-0001.html>