Hi Antonio,
I've been using WinGRASS for a while but now I would like to run a few
functions from R using spgrass (interface between GRASS and R).
I know that this is possible and stable in Linux but I'm not sure for
Windows. Has anyone tried?
Thanks
Antonio
at the moment there is following
Hi Antonio
-Ursprüngliche Nachricht-
Von: António Rocha
Gesendet: 27.09.2010 11:27:43
An: Helmut Kudrnovsky
Betreff: Re: GRASS-R connection in Windows
Hello Helmut
First of all, let me thank you for your reply.
de nada
Helmut Kudrnovsky wrote:
(2) you can start Grass-command-line
.
Abdoul O. Dia
2010/9/27 António Rocha [antonio.ro...@deimos.com.pt]
Hello Helmut
First of all, let me thank you for your reply.
Helmut Kudrnovsky wrote:
(2) you can start Grass-command-line - it's a windows-command-line, not a
msys-rxvt-terminal (you can find this
starting option under
hi,
in WinGRASS 7 (standalone installer:
http://grass.osgeo.org/download/software.php#g70x) the Windows batchfiles
for use with R (http://code.google.com/p/batchfiles/) are now integrated for
a smooth GRASS-R-coupling in windows.
see also trac.osgeo.org/grass/ticket/1149
and for the usage see
>Wrong target, please use:
>http://win-builder.r-project.org/s90s00N7rhyt/rgrass7_0.1-4.zip
> utils:::menuInstallLocal()
Paket ‘rgrass7’ erfolgreich ausgepackt und MD5 Summen abgeglichen
GRASS version: 7.1.svn
GRASS SVN revision: 67543
>OK. Please check that r.roughness.vector.bat is present in:
>
>C:\Users\xy\AppData\Roaming\GRASS7\addons\bin, or
>C:\Program Files\GRASS GIS 7.1.svn\bin
it is in the addon path: C:\Users\xxx\AppData\Roaming\GRASS7\addons\bin
it works in winGRASS itself.
r.roughness.vector
>
>Is %APPDATA% a predictable location on Windows?
yes, %APPDATA% is predictable on Windows.
we set it e.g. in the winGRASS standalone installer here:
https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L743
and on other places in the
>Thanks. I've committed changes to R-forge, which seem to work for me for
>Linux and Windows. The updated draft Windows binary is at:
>
>http://win-builder.r-project.org/KJJJkeazt7Sw/rgrass7_0.1-5.zip
> utils:::menuInstallLocal()
Paket ‘rgrass7’ erfolgreich ausgepackt und MD5 Summen abgeglichen
>
>> library(rgrass7)
>> initGRASS("/usr/local/grass7", home=tempdir())
>sh: 1: g.gisenv: not found
>sh: 1: g.gisenv: not found
>sh: 1: g.gisenv: not found
>sh: 1: g.gisenv: not found
>sh: 1: g.gisenv: not found
>sh: 1: g.version: not found
>Error in system(paste("g.version", get("addEXE", envir =
>I am using Rstudio within GRASS without problems (on Ubuntu 14.04). No
specific configuration required as >far as I remember. Also on Windows I
generally have no problem running Rstudio under GRASS (the latter >installed
using OSGeo4W), but there I had to define the path to Rstudio
Anna Petrášová wrote
> On Thu, Jul 14, 2016 at 9:20 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>>>When I enter the command echo %PATH% I get:
>>>[...]
>>>Dnvm\;C:\Program Files
>> (x86)\Skype\Phone\;c:\users\buer3379\appdata\local\enthought\canopy\us
>and start a normal windows console, just the one which is delivered by
windows itself and type RScript
>
>here on my side:
>
>Microsoft Windows [Version 10.0.10586]
>(c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.
>
>C:\Users\>cd C:\Program Files\R\R-3.3.1\bin
of course, first
>In order for GRASS to be able to find R executables, R must be on the
>PATH variable.
in the standalone winGRASS installer R is already in the %PATH% variable, so
no extra work is needed.
I hope I'll find some time to implement this also in OSGeo4W-winGRASS.
see in original report above, R is
Anna Petrášová wrote
> Hi,
>
> In order for GRASS to be able to find R executables, R must be on the
> PATH variable. Follow for example this solution:
>
> https://pvanb.wordpress.com/2014/12/17/access-r-from-grass-gis-on-windows/
>
> to make R accessible from GRASS permanently. A simple but
C. Buerger IV wrote
> I'm attempting to use the FUTURES
> https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Softwaremodel
> for GRASSGIS, which requires an interface with R to use the drudge
> function. I'm running Windows 7 and the automatic linkup between R and
>
[please keep it on the ML]
>A Standalone install. At the time it seemed like what I wanted.
tested here:
System Info
GRASS Version: 7.3.svn
GRASS SVN revision: r68855
>Using Windows 7 Enterprise and R 3.3.0 and R 3.3.1, GRASS 7.0.4, and rgrass7
0.1-7 and 0.1-8, I see no >issues and cannot reproduce it. Could other users
of Windows (I am not a Windows user) please report >whether this loading
error is specific to the OP (and another person who contacted me
[you have to be subscribed to post in this ML]
benhemingway wrote
> I am having the same problem.
>
> Windows 10 Home 64 bit. Native GRASS 7.0.4 R 3.3.1
>
> When I try to load the rgrass7 library from within GRASS i get:
>
> Error : .onAttach failed in attachNamespace() for 'rgrass7',
>I've put a Windows binary and source of rgrass7_0.1-9 on:
>
>http://spatial.nhh.no/R/rgrass7/
>
>which I believe resolves the issue. Please test and report back (on list,
>subscribe first, then reply or post). Please also check with addons
>present to be sure that the fix works both with and
>The OP replied off-list 20/9 that:
>
>"I'm working on win7 home professional.
>
>It's the latest r version (3.3.0) and native grass 7.0.4.
>
>The rgrass7 package is the latest, downloaded yesterday. In the single r
session it works and reports that grass is not running.
>
>But if i start it in
Helmut Kudrnovsky wrote
> what can be the reason of such an attachNamespace() issue?
>
> two installed rgrass7 packages (with and without admin rights)?
> locale issue?
> path issue?
>
> anything else to test?
maybe .Rprofile file that is loading it already at Startup?
> >With the fix, R for Windows picks up the default personal library
location.
>> This is both with Rgui started in the GRASS Layer Manager console, and in
>> the Windows GRASS terminal.
> >
>> Thanks very much!
>Excellent, thanks for the rapid test! Hence I'll backport the fix.
thanks for
Helmut Kudrnovsky wrote
> if we let %HOME% untouched, the easiest way may be
> (similar as we already do it with Rstudio:
> IF EXIST "%ProgramFiles%\RStudio\bin\rstudio.exe" set
> PATH=%PATH%;%ProgramFiles%\RStudio\bin)
>
> - check if there is C:\Users\yourusername
Helmut Kudrnovsky wrote
>
> Helmut Kudrnovsky wrote
>> both changes should be discussed on the dev ML.
>>
>> before such changes are implemented, the workaround to manage this issue
>> manually via the control panel should go to the wiki.
>>
>> Anna, a
Helmut Kudrnovsky wrote
>
> Roger Bivand wrote
>> For me on Linux, R_LIBS is set by me and works, but on Windows the
>> default
>> is (possibly) set in the Registry anyway, which would/should be used if
>> R_LIBS is not set. Within R, .libPaths() should be the sam
Helmut Kudrnovsky wrote
> now tested by intalling some libraries into my personal library.
>
> outside a winGRASS7.2.svn session
>
>> .libPaths()
> [1] "C:/Users/test/Documents/R/win-library/3.3"
> [2] "C:/Program Files/R/R-3.3.1/library"
Helmut Kudrnovsky wrote
>
> Helmut Kudrnovsky wrote
>> now tested by intalling some libraries into my personal library.
>>
>> outside a winGRASS7.2.svn session
>>
>>> .libPaths()
>> [1] "C:/Users/test/Documents/R/win-libra
>My Windows 7, GRASS 7.0.4 shows identical .libPaths() values both inside
>and out with RGui. I don't know how the location of the personal library
>folder is recorded - is it in the registry? How might one know? It looks
>like:
>
>Sys.getenv("R_LIBS_USER")
tested within a winGRASS7.0.5 session:
Roger Bivand wrote
> On Tue, 15 Nov 2016, Anna Petrášová wrote:
>
>> Hi,
>>
>> I installed latest R on fresh Windows 10, then I installed several
>> packages into my personal library, then I installed standalone GRASS
>> GIS 7.3, and when I run R from GRASS session, it does not see the
>>
Helmut Kudrnovsky wrote
> both changes should be discussed on the dev ML.
>
> before such changes are implemented, the workaround to manage this issue
> manually via the control panel should go to the wiki.
>
> Anna, any suggestions?
just opened a discussion on
Roger Bivand wrote
> Right. Both R and Python seem to use %USERPROFILE% which is predictably
> present in modern Windows. In winGRASS this is used to set %HOME%, which R
> uses instead of %USERPROFILE%. R believes a set %HOME%, leading to the
> difficulties.
a list of available windows
Roger Bivand wrote
> On Thu, 17 Nov 2016, Roger Bivand wrote:
>
>> On Thu, 17 Nov 2016, Helmut Kudrnovsky wrote:
>>
>>> > My Windows 7, GRASS 7.0.4 shows identical .libPaths() values both
>>> inside
>>> > and out with RGui. I don't know how the
Roger Bivand wrote
>> could you download the files from
>> https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/external/rbatch,
>> copy these to an arbitrary folder e.g. C:\wd\testfolder, open a windows
>> console within this folder and type R in the console, then try your test
>> with
Helmut Kudrnovsky wrote
> I had a look into the sources; I can't find a line of code where winGRASS
> changes %HOME% at the moment; but it obvious uses %USERPROFILE% as %HOME%.
maybe just found it:
for trunk
https://trac.osgeo.org/grass/browser/grass/trunk/lib/init/grass.py#L712
712
Roger Bivand wrote
>>
>> no idea at the moment if this change in env.bat has a side effect to the
>> winGRASS installation; further tests are needed.
>>
>
> See also
>
>> ?"environment variables"
>
> which on a Windows installation shows "R_USER" in the Windows specific
> section at foot, this
>Are SQLite and GML drivers disabled/broken in readVECT? I only get
driver="ESRI Shapefile" to work,
confirmed by:
---
> sessionInfo()
R version 3.4.0 (2017-04-21)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 15063)
Matrix products: default
locale:
[1] C
>Are SQLite and GML drivers disabled/broken in readVECT?
some earlier discussions I remembered:
https://lists.osgeo.org/pipermail/grass-stats/2015-July/001561.html
https://lists.osgeo.org/pipermail/grass-stats/2015-July/001562.html
[...]
>For some vectors, I get the following warnings (loss of data apparently):
>
>> bla2<-readVECT("census_wake2000")
>Exporting 105 areas (may take some time)...
>Warning 1: Value 120426752 of field AREA of feature 23 not successfully
written. Possibly due to too larger >number with respect to field
>> bla2<-readVECT("census_wake2000")
>Exporting 105 areas (may take some time)...
>Warning 1: Value 120426752 of field AREA of feature 23 not successfully
written. Possibly due to too larger >number with respect to field width
testing by:
v.out.ogr input=census_wake2000@PERMANENT
>Von: "Roger Bivand"
>Please report sessionInfo() in R, and check the ogrDrivers() list.
sessionInfo() already posted in the mail before, here again:
> sessionInfo()
R version 3.4.0 (2017-04-21)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build
Gesendet: Dienstag, 10. Oktober 2017 um 22:52 Uhr
Von: "Veronica Andreo" <veroand...@gmail.com>
An: "Roger Bivand" <roger.biv...@nhh.no>
Cc: "grass-stats@lists.osgeo.org" <grass-stats@lists.osgeo.org>, "Helmut
Kudrnovsky" <hel..
>Von: "Roger Bivand"
>And output of v.in.ogr -f?
v.in.ogr -f
JP2ECW (ro): ERDAS JPEG2000 (SDK 5.3)
FileGDB (rw+): ESRI FileGDB
PCIDSK (rw+): PCIDSK Database File
netCDF (rw+): Network Common Data Format
JP2OpenJPEG (rw):
>Gesendet: Dienstag, 10. Oktober 2017 um 23:24 Uhr
>Von: "Ahmadou Dicko" <dicko.ahma...@gmail.com>
>An: "Helmut Kudrnovsky" <hel...@web.de>
>Cc: "Roger Bivand" <roger.biv...@nhh.no>, "grass-stats@lists.osgeo.org"
><grass
Maximilian Bakenhus wrote
> Hello all,
>
> nearly any GRASS command which I write gives me Errors like:
>
> 1: running command 'r.to.vect.exe --quiet --overwrite input=sites_catchm_1
> output=sites_catchm_1_v type=area' had status 1
>
> 2: running command 'v.overlay.exe --overwrite --quiet
>
---
(1)‘3.4.2’of R, Version 1.1.383 of R Studio
(2) GRASS Standalone
(3)
a <- NULL
for(i in 1:length(anames)){
print(anames[i])
a <- c(a,unique(execGRASS("v.db.select",
parameters = list(
map = anames[i],
>Please try:
>
>install.packages("rgrass7", repos="http://R-Forge.R-project.org;)
>
>which incorporates the change in both places, not just one as before (svn
>revision 63 on R-Forge, spgrass project).
tested with above install.packages cmd:
> sessionInfo()
R version 3.4.0 (2017-04-21)
Veronica Andreo wrote
> Hi
>
> I taught a GRASS course last week and all students got the same error when
> trying to init GRASS from R or Rstudio (in all cases grass was installed
> through OSGeo4W installer).
>
> Here´s the command we used (paths must be adapted accordingly):
>
>
>I got the same error a while back and I ended up finding a workaround by
copying all of the .dll files from >C:\OSGeo4W64\bin to
C:\OSGeo4W64\apps\grass\grass-7.4.1\bin. I have grass installed on my C
drive >but follow the path to your installation path bin. It appears that
the .dlls are
Markus Neteler wrote
> On Thu, Nov 1, 2018 at 1:20 PM Veronica Andreo
> veroandreo@
> wrote:
>> In the body of the ticket I mentioned that the "pop-up error is a missing
>> iconv.dll" and
>
> Yes - but the real error message might help.
see
>How to find/test for the location of PROJ shared files?
see
https://r-forge.r-project.org/scm/viewvc.php/pkg/rgrass7/R/initGRASS.R?root=spgrass=55=64
for a diff
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Stats-f4049448.html
>I could reproduce the problem after starting the OSGeo4W console from the
>desktop shortcut icon.
>
>The problem seems to be that OSGeo4W's console starts in a directory for
>which the user does not have write access (for me from a desktop shortcut
>C:\Users\Public\Desktop\OSGeo4W). Because
.
>
> Roger
>
> Roger Bivand
> Norwegian School of Economics
> Bergen, Norway
>
>
>
> Fra: Helmut Kudrnovsky
> Sendt: søndag 16. september, 16.26
> Emne: Re: [GRASS-stats] Error when starting grass from R (grass
> installedthru osgeo4w)
> Til:
> grass-stat
>Should I open R from OSGeo4W command console and then init grass there? Is
that the workflow?
Yes, that's the workflow.
because environment variables for e.g. gdal, proj4 etc have to be set. And
that's nicely done in the OSGeo4W command line
-
best regards
Helmut
--
Sent from:
Veronica Andreo wrote
> Hello,
>
> I am preparing a one week GRASS GIS course and I mostly expect Windows
> users, so I recommend to install from OSGeo4W that allows to easily
> install
> also QGIS, msys (to get nice bash tricks) and other libraries that are
> then
> needed for some grass
>OK, thanks for confirming that OSGeo4W remains feasible for rgrass7; I don't
have access. Does usability >include initGRASS()? This would be most fragile
because environment variables are being set, and >condition on Windows and
OSGeo4W.
R within a GRASS session works quite well so far.
did a
romain Fer. wrote
> Hello,
>
> I am a french student in master's degrees, in advence I'm sorry for my
> english.
>
> I using the package rgrass7 with R during my internship and I have a error
> on one function of this package. I use g.extension to import r.clip. I
> explain this error on this
56 matches
Mail list logo