<div dir="ltr"><br><br>On Thu, Aug 23, 2018 at 1:39 PM Stefan Blumentrath <<a href="mailto:Stefan.Blumentrath@nina.no">Stefan.Blumentrath@nina.no</a>> wrote:<br>><br>> Hi Marcus,<br>><br>> I am not too familiar with C and the like so I might confuse some things here...<br>><br><div>> I noticed that using .buffer() in PyGRASS gives a lot of "using native format" output.</div><div><br></div><div>this "using native format" refers to the format of newly created vector maps (could also be OGR via v.external.out)<br></div>><br>> So I looked it up and it seems to be using native buffering (Vect_area_buffer2):<br><div>> <a href="https://trac.osgeo.org/grass/browser/grass/trunk/lib/python/pygrass/vector/geometry.py#L1654">https://trac.osgeo.org/grass/browser/grass/trunk/lib/python/pygrass/vector/geometry.py#L1654</a></div>><br>> And Vect_area_buffer2 is the non-geos buffering, right?<br>> <a href="https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.buffer/main.c#L564">https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.buffer/main.c#L564</a><br>><br><div>> So, should then PyGRASS be changed/fixed to use geos buffering too?</div><div><br></div><div><div>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. <br></div></div><br>> Shall I open a ticket?<br><div><br></div><div>yes please, pygrass should use the module v.buffer, or GEOS functions</div><div><br></div><div>Markus M<br></div><div>></div>> Cheers,<br>> Stefan<br>><br>><br>> -----Original Message-----<br>> From: grass-dev <<a href="mailto:grass-dev-bounces@lists.osgeo.org">grass-dev-bounces@lists.osgeo.org</a>> On Behalf Of GRASS GIS<br>> Sent: onsdag 22. august 2018 22:07<br>> Cc: <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>> Subject: Re: [GRASS-dev] [GRASS GIS] #3448: v.buffer native failures<br>><br>> #3448: v.buffer native failures<br>> --------------------------+---------------------------------<br>> Reporter: marisn | Owner: grass-dev@…<br>> Type: defect | Status: closed<br>> Priority: normal | Milestone: 7.6.0<br>> Component: Vector | Version: unspecified<br>> Resolution: wontfix | Keywords: v.buffer v.parallel<br>> CPU: Unspecified | Platform: Unspecified<br>> --------------------------+---------------------------------<br>> Changes (by mmetz):<br>><br>> * status: new => closed<br>> * resolution: => wontfix<br>><br>><br>> Comment:<br>><br>> 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.<br>><br>> --<br>> Ticket URL: <<a href="https://trac.osgeo.org/grass/ticket/3448#comment:4">https://trac.osgeo.org/grass/ticket/3448#comment:4</a>><br>> GRASS GIS <<a href="https://grass.osgeo.org">https://grass.osgeo.org</a>><br>><br>> _______________________________________________<br>> grass-dev mailing list<br>> <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>> <a href="https://lists.osgeo.org/mailman/listinfo/grass-dev">https://lists.osgeo.org/mailman/listinfo/grass-dev</a></div>