Opened 10 years ago
Last modified 7 years ago
#2636 new enhancement
v.buffer, allow selection of columns for opts "distance", "minordistance", and "angle"
| Reported by: | isaacullah | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 8.0.0 |
| Component: | Vector | Version: | svn-releasebranch70 |
| Keywords: | v.buffer, columns | Cc: | |
| CPU: | x86-64 | Platform: | Linux |
Description
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.
Change History (13)
comment:1 by , 9 years ago
| Milestone: | 7.0.1 → 7.0.2 |
|---|
follow-up: 6 comment:5 by , 9 years ago
Replying to 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.
follow-up: 10 comment:6 by , 9 years ago
Replying to mmetz:
Replying to 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
comment:7 by , 9 years ago
| Milestone: | 7.0.4 → 7.0.5 |
|---|
comment:9 by , 8 years ago
| Milestone: | 7.0.5 → 7.3.0 |
|---|
comment:10 by , 8 years ago
Replying to martinl:
Replying to mmetz:
Replying to 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.
comment:13 by , 7 years ago
| Milestone: | 7.4.1 → 8.0.0 |
|---|
Ticket retargeted after 7.0.1 milestone closed