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
link2GI seems to "break" the link made by rgrass7 between R and GRASS #41
Comments
Dear Loïc Now your issue :
Edit: Sorry, just saw it |
Dear Chris,
Yes, I fully agree with you: it makes no sense to reset GRASS several times with the same settings. It was just to show that the reset was going well and that as soon as link2GI::linkOTB() was called the GRASS initialization crashed right after.
Yes, I agree with you and I already tried to link R and GRASS with link2GI::linkGRASS() but never succeeded (probably still linked to Windows 8.1).
To conclude, I understand that all these problems (i.e. conflict between link2GI and rgrass7, problem in using the linkGI functions dedicated to link R and GRASS) are most probably related to Windows 8.1. For my part I managed to fix the problem with a workaround. So, I'm not asking you to find a solution at all costs (I understand the difficulty of making all packages work perfectly in absolutely all working environments) and, therefore, you can close this thread if you wish. Thanks again for your answer. |
Dear Loïc, |
Actually I am not able to reproduce the error and warning messages. However most of the stuff that happens is done with ASCII text manipulation which is strongly related to the code tables You use. Could you pls install a standalone |
@gisma I'm sorry I couldn't do the test : I tried to install a second standalone version of GRASS but this is not possible because at the time of installation the first version is detected automatically and prevents the installation of the second version... and, to tell the truth, I don't really want to uninstall the first version that works : I'm afraid of doing something wrong ! (my standalone version of GRASS 7.8.3 is installed here : C:\Program Files\GRASS GIS 7.8) Anyway, your hypothesis is probably good because when I made the link with OTB with link2GI::linkOTB(), I already had this space problem in the path. To make it work, I had to install OTB at the root (C:/OTB/) (because windows 8.1 automatically puts a space between Program and Files for its 'Program Files' directory). For OTB, this works fine, but it is not really recommended to install software directly at the root. It still remains preferable (and logical!) to install the softwares in the "Program Files" folder. So , if you can fix this space problem (and if it's not too time-consuming !!), it would be very nice to do it, because I think it should work. Anyway, if you fix it, I will do the test immediately. Kind regards |
@gisma
@rsbivand
Dear Chris,
On Roger's advice, I'm contacting you to report a problem I just highlighted: there seems to be a conflict between link2GI and rgrass7.
More precisely, when I have established a link between R and GRASS with the command rgrass7::initGRASS() and then run the command link2GI::linkOTB(), the link between R and GRASS seems to be broken: if I run the command rgrass7::initGRASS() again, R returns the following error message :
This error message is accompanied by a message that opens in a popup window :
> The procedure entry point GEOSMakeValid_r could not be located in the dynamic link library C:\Program Files\GRASS GIS 7.8\extrabin\gdal300.dll
Some information about the environment :
-OS: Windows 8.1
-R version 3.6.3
-All the packages are up to date
-the GRASS version: stand-alone Windows GRASS 7.8.3
To be a little more concrete and to help you identify the problem, below are two tests.
I am at your disposal if you would like more information or if you would like me to carry out further tests.
Best regards,
Loïc
The second test starting with link2GI::linkOTB() :
The text was updated successfully, but these errors were encountered: