[GRASS-dev] [GRASS GIS] #3438: v.buffer silently ignores options depending on buffering alhorithm in use

[GRASS GIS]

#3438: v.buffer silently ignores options depending on buffering alhorithm in use
--------------------------+----------------------------
  Reporter:  marisn       |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  major        |  Milestone:  7.4.0
 Component:  Vector       |    Version:  svn-trunk
Resolution:               |   Keywords:  v.buffer, GEOS
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+----------------------------

Comment (by mmetz):

 Replying to [ticket:3438 marisn]:
 > At the moment user gets no warning if some of his input parameters (i.e.
 minordistance, angle) are ignored due to use of GEOS instead of native
 buffering algorithm. v.buffer should fail with a fatal error if user has
 provided unsupported input parameters.

 v.buffer prints now (trunk r71724) warnings if options are used that apply
 only to the native, deprecated algorithm. The manual is updated
 accordingly.
 >
 > Current approach of setting environmental variable to switch between
 GEOS and native algorithms is also suboptimal, as setting env on GNU/Linux
 is easy and common, while setting on Windows is uncommon thus hard. A flag
 would be better approach.

 This is by purpose to make it difficult to use the buggy native algorithm.
 The mechanism with an environmental variable exists only in case someone
 wants to fix and test the native algorithm.

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