Opened 12 years ago
Last modified 12 years ago
#1845 closed defect
v.buffer: strange result for lines — at Initial Version
Reported by: | martinl | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | 7.0.0 |
Component: | Vector | Version: | svn-trunk |
Keywords: | v.buffer, lines, 3D input | Cc: | |
CPU: | x86-64 | Platform: | Linux |
Description
Sample data attached: attachment:silnice.txt
Buffer 1000m - OK (attachment:vector_1000.png)
v.buffer input=silnice output=silnice1000 distance=1000
Buffer 100m (using GEOS) - surprisingly wrong (attachment:vector_100_geos.png)
v.buffer input=silnice output=silnice100 distance=100
Buffer 100m (using GRASS) - wrong - not surprisingly (attachment:vector_100_grass.png)
export GRASS_VECTOR_BUFFER=1 v.buffer input=silnice output=silnice100 distance=100
Note:
See TracTickets
for help on using tickets.
sample data