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

Stefan Blumentrath Stefan.Blumentrath at nina.no
Thu Aug 23 04:39:19 PDT 2018

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.

So I looked it up and it seems to be using native buffering (Vect_area_buffer2):

And Vect_area_buffer2 is the non-geos buffering, right?

So, should then PyGRASS be changed/fixed to use geos buffering too?
Shall I open a ticket?


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


 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>

More information about the grass-dev mailing list