-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If GRASS variables are set, use them for analyses #15092
Comments
Author Name: Giovanni Manghi (@gioman) And if somehow would be ever possible to set (in Sextante) the region extent and resolution (in similar way as it is possible in the qgis/grass plugin) we can drop the qgis/grass plugin all together ;) |
Author Name: Paolo Cavallini (@pcav) Not really: we would still miss the browser and the digitizer. |
Author Name: Victor Olaya (@volaya) from r146 there is a tool that allows you to graphically define the region setting. It is in the algorithms tree, under GRASS/tools Have to figure out now how to use grass settings created from the grass plugin |
Author Name: Markus Neteler (Markus Neteler) GRASS (raster) modules respect the WIND file. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav) Still true in QGIS 3, unsure whether still desirable.
|
Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 5462
Redmine category:processing/grass
Currently, the plugin generates locations on the fly. It would be good if, in case a region etc. is defined by opening a mapset, these variables would be used for subsequent analyses. If so, the GRASS modules should be removed from the GRASS plugin, as they would be redundant when feature parity will be achieved.
The text was updated successfully, but these errors were encountered: