Opened 12 years ago
Closed 12 years ago
#1845 closed defect (fixed)
v.buffer: strange result for lines
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 (last modified by )
Sample data attached: attachment:silnice.txt
Buffer 1000m - OK (attachment:v_buffer_1000.png)
v.buffer input=silnice output=silnice1000 distance=1000
Buffer 100m (using GEOS) - surprisingly wrong (attachment:v_buffer_100_geos.png)
v.buffer input=silnice output=silnice100 distance=100
Buffer 100m (using GRASS) - wrong - not surprisingly (attachment:v_buffer_100_grass.png)
export GRASS_VECTOR_BUFFER=1 v.buffer input=silnice output=silnice100 distance=100
Attachments (5)
Change History (12)
by , 12 years ago
Attachment: | silnice.txt added |
---|
comment:1 by , 12 years ago
Description: | modified (diff) |
---|---|
Priority: | normal → critical |
follow-up: 3 comment:2 by , 12 years ago
Replying to martinl:
Sample data attached: attachment:silnice.txt
Buffer 100m (using GEOS) - surprisingly wrong (attachment:v_buffer_100_geos.png)
Works for me. Do you have any changes in your local copy?
v.buffer input=silnice output=silnice100 distance=100
Buffer 100m (using GRASS) - wrong - not surprisingly (attachment:v_buffer_100_grass.png)
export GRASS_VECTOR_BUFFER=1 v.buffer input=silnice output=silnice100 distance=100
Looks better for me, but still with errors.
I'm using GEOS-3.3.6.
Markus M
follow-up: 4 comment:3 by , 12 years ago
Replying to mmetz:
Works for me. Do you have any changes in your local copy?
hm, it fails only with original binary map (attachment:silnice.pack), not with imported ascii map.
follow-up: 5 comment:4 by , 12 years ago
Replying to martinl:
Replying to mmetz:
Works for me. Do you have any changes in your local copy?
hm, it fails only with original binary map (attachment:silnice.pack), not with imported ascii map.
The original binary map is 3D, the imported ascii map is 2D. I guess one of the cleaning tools does not work with 3D output, even though v.buffer creates 2D output. Strange.
Markus M
comment:5 by , 12 years ago
Keywords: | 3D input added |
---|
Replying to mmetz:
The original binary map is 3D, the imported ascii map is 2D. I guess one of the cleaning tools does not work with 3D output, even though v.buffer creates 2D output. Strange.
I overlooked it, good point.
comment:7 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
sample data