Hi Massimo,
That will be great!
we do need grass able to talk with R also in osgeo4w.
unlike as rpy2 are R-python-bindings, the R-batchfiles simply enables
invoking R from anywhere you are, e.g. within a WinGRASS-session or within a
OSGeo4W-shell/commandline:
echo The script is self contained
hi,
That will be great!
we do need grass able to talk with R also in osgeo4w.
ok, I've testet a stripped down R-batch-file
http://osgeo-org.1560.x6.nabble.com/file/n5128182/setR.bat and put it
into
C:\OSGeo4W\etc\ini
results:
- R (R and RGui) starts in 'OSGeo4W Shell' and 'OSGeo4W'
Hi devs,
some time ago [1] I've integrated R-batch-files [2] into the GRASS GIS
source [3] for a nice WinGRASS-R-integration [4].
At the moment this functionality of a dynamic R-integration is only
available for standalone WinGRASS7svn, in standalone WinGRASS6.x a static
approach of a
(C) try to include the R-batch-files into OSGeo4W-environment as its own
package - a R-GRASS-
integration would be then possible for standalone WinGRASS6/7 AND
OSGeo4W-WinGRASS6/7
just forgotten to mention, with alternative (C) OSGeo4W and other projects
may benefit from a smooth
That will be great!
we do need grass able to talk with R also in osgeo4w.
do you have any experience in running rpy2 on windows and within the system
python or with osgeo4w python ?
.. hope your solution will make this happening!
Massimo.
On Mar 9, 2014, at 5:57 PM, Helmut Kudrnovsky
