Opened 13 years ago
Closed 13 years ago
#1479 closed defect (invalid)
error running v.generalize under Windows/Osgeo4w
Reported by: | lutra | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Vector | Version: | svn-trunk |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | MSWindows 7 |
Description
I see the same "pattern" as in #1477
Using the Wxpython interface it works.
Using the QGIS/GRASS interface it doesn't, but using the QGIS/GRASS interface under Linux works fine.
The command produced by the QGIS/GRASS interface is
v.generalize input=freguesias@mapset_agueda type=area layer=1 -c type=boundary method=douglas threshold=200 look_ahead=7 reduction=50 slide=0.5 angle_thresh=3 degree_thresh=0 closeness_thresh=0 betweeness_thresh=0 alpha=1.0 beta=1.0 ite rations=1 layer=1 output=gene_qgisgrass
but the same command under Linux works fine
v.generalize input=provincias@mapset_agueda type=area layer=1 -c type=boundary method=douglas threshold=200 look_ahead=7 reduction=50 slide=0.5 angle_thresh=3 degree_thresh=0 closeness_thresh=0 betweeness_thresh=0 alpha=1.0 beta=1.0 iterations=1 layer=1 output=gene_qgisgrasslinux
while removing the "layer=1" parameters works also under Window/QGIS/GRASS CLI
v.generalize input=freguesias@mapset_agueda type=area -c type=boundary method=douglas threshold=200 look_ahead=7 reduction=50 slide=0.5 angle_thresh=3 degree_thresh=0 closeness_thresh=0 betweeness_thresh=0 alpha=1.0 beta=1.0 ite rations=1 output=gene_qgisgrass
Note:
See TracTickets
for help on using tickets.
The question is if GRASS should accommodate the QGIS/GRASS plugin or if the QGIS/GRASS plugin should accommodate GRASS. From a GRASS perspective, the answer is obviously that the QGIS/GRASS plugin should adhere to GRASS standards. That means no duplicate options like layer=1 layer=1, no options like =area. Therefore this bug is a QGIS/GRASS plugin bug and not a GRASS bug. Closing as invalid.
Markus M