v.buffer, allow selection of columns for opts "distance", "minordistance", and "angle"

[landam]

Reported by isaacullah on 24 Mar 2015 00:05 UTC Currently, v.buffer only allows a column selection for single radius (opt "column"), but allows the creation of "oblong" buffers using the manual entry opts "distance", "minordistance", and "angle". v.buffer would be a lot more useful if these could all simply be column selectable too. For example, if I have a large vector points file of archaeological site locations, and I have BOTH a length and width column (and, potentially, a "site axis direction" column too), then I could make a "buffer" map of the actual site size and orientation. Currently, in v.buffer, I can only use a calculated "average" site radius column, and make circular buffers for these sites.

Operating system

Linux

GRASS GIS version and provenance

svn-releasebranch70

Migrated-From: https://trac.osgeo.org/grass/ticket/2636

[landam]

Comment by neteler on 30 Jul 2015 21:19 UTC Ticket retargeted after 7.0.1 milestone closed

[landam]

Comment by neteler on 20 Nov 2015 17:08 UTC Ticket retargeted after milestone closed

[landam]

Comment by neteler on 28 Jan 2016 08:02 UTC Ticket retargeted after milestone closed

[landam]

Comment by neteler on 28 Jan 2016 08:06 UTC Ticket retargeted after 7.0.3 milestone closed

[landam]

Comment by mmetz on 22 Feb 2016 10:09 UTC Replying to [ticket:2636 isaacullah]:

Currently, v.buffer only allows a column selection for single radius (opt "column"), but allows the creation of "oblong" buffers using the manual entry opts "distance", "minordistance", and "angle". v.buffer would be a lot more useful if these could all simply be column selectable too. For example, if I have a large vector points file of archaeological site locations, and I have BOTH a length and width column (and, potentially, a "site axis direction" column too), then I could make a "buffer" map of the actual site size and orientation. Currently, in v.buffer, I can only use a calculated "average" site radius column, and make circular buffers for these sites.

The options "minordistance" and "angle" apply only to the GRASS-internal buffering method which never worked. It is recommended to use only the GEOS buffering method, but it does not support these options to create oblong buffers. To avoid confusion, the options "minordistance" and "angle" should be removed.

[landam]

Comment by @landam on 25 Mar 2016 22:40 UTC Replying to [comment:5 mmetz]:

Replying to [ticket:2636 isaacullah]:

The options "minordistance" and "angle" apply only to the GRASS-internal buffering method which never worked. It is recommended to use only the GEOS buffering method, but it does not support these options to create oblong buffers. To avoid confusion, the options "minordistance" and "angle" should be removed.

Agreed, are you planning to remove these options? Martin

[landam]

Modified by @landam on 12 May 2016 06:36 UTC

[landam]

Comment by @landam on 23 Aug 2016 10:22 UTC Ping

[landam]

Modified by @landam on 25 Aug 2016 15:51 UTC

[landam]

Comment by mmetz on 25 Aug 2016 17:12 UTC Replying to [comment:6 martinl]:

Replying to [comment:5 mmetz]:

Replying to [ticket:2636 isaacullah]:

The options "minordistance" and "angle" apply only to the GRASS-internal buffering method which never worked. It is recommended to use only the GEOS buffering method, but it does not support these options to create oblong buffers. To avoid confusion, the options "minordistance" and "angle" should be removed.

Agreed, are you planning to remove these options? Martin

Not before G8, it would break compatibility. In G7, if these options are set, a warning could be issued that these options are ignored with the recommended GEOS buffering method. Currently, these options are silently ignored.

[landam]

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

[landam]

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

[landam]

Modified by @landam on 28 Jan 2018 11:05 UTC