Opened 14 years ago
Last modified 13 years ago
#2063 new enhancement
wrapper for R and GRASS
Reported by: | pcav | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 2.0.0 |
Component: | GRASS | Version: | Trunk |
Keywords: | Cc: | neteler | |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
It would be good to add a wrapper for one-shot analyses to be done in GRASS and R. In GRASS, this means:
- load a raster with r.external
- generate a location based on it
- run the analysis
- output a tiff
- load the tiff on the canvas
Similar for vectors. Of course serious GRASS work must be done via the GRASS plugin, but this will make rather complex analyses available also to non-GRASS aware people, providing a gentle introduction to it, and increasing the power of QGIS analyses.
Change History (7)
comment:1 by , 14 years ago
Component: | GRASS → Rasters |
---|---|
Owner: | changed from | to
Summary: | wrapper for GRASS and R → wrapper for R |
comment:2 by , 14 years ago
Sorry I was unclear. Many users find the location-mapset GRASS concept difficult to understand, and cumbersome for one-shot analyses. The idea here is to hide this complexity by creating a location on the fly, running the analysis, exporting the result, and load it on the canvas. In this way, one could use GRASS without knowing much about it.
comment:3 by , 13 years ago
Component: | Rasters → GRASS |
---|---|
Summary: | wrapper for R → wrapper for R and GRASS |
See more details in #3135
comment:4 by , 13 years ago
Priority: | minor: annoyance → major: does not work as expected |
---|
comment:5 by , 13 years ago
Cc: | added; removed |
---|
comment:6 by , 13 years ago
Concerning on the fly GRASS locations, see this example of a simple implementation: http://grass.osgeo.org/wiki/GRASS_and_Sextante
comment:7 by , 13 years ago
Sextance uses GRASS in a very efficient way, no need to understand GRASS' location-mapset concept. It creates a mapset on the fly and just runs the analysis in a temporary session as indicated above. Works nicely in the gvSIG-OADE-Sextante-GRASS package which I indicated in the GRASS Wiki page. It would be a BIG (and likely rather easy to implement) improvement of the QGIS-GRASS integration to use the same method. All pieces are likely there.
How GRASS is involved here? There is rgdal. Especially if you start with r.external, I don't see any reason it should be somehow linked to GRASS plugin. It can be general tool either reading data directly from providers (better I think) or via gdal (rgdal).