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): 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? Shall I open a ticket? Cheers, Stefan -----Original Message----- From: grass-dev <[email protected]> On Behalf Of GRASS GIS Sent: onsdag 22. august 2018 22:07 Cc: [email protected] 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 [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
