v.buffer silently ignores options depending on buffering alhorithm in use
|Reported by:||marisn||Owned by:|
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.
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.