-
-
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
grass not working in qgisn 2.18.26 ltr. 'r was unexpected at this time8 #28475
Comments
Author Name: Daniel Morton (Daniel Morton) Yes, it is different. It mostly works, but fails trying to copy the results from the temporary Grass working directory to user specified output directory. I had the same problem with r.texture, so I assume it is a generic problem with the grass toolbox functionality. I can still view the results if I use Grass and point it to the temporary dataset. Note this was observed in 2.18.26, which cannot be selected from the drop-down when submitting an issue. |
Author Name: Giovanni Manghi (@gioman) Daniel Morton wrote:
GRASS plugin or Processing/GRASS? |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Nyall Dawson (@nyalldawson) Please test with 3.4 - 2.18 is no longer supported |
Author Name: Jürgen Fischer (@jef-n) Please test with QGIS 3.4 - QGIS 2.18 reached it's end of life. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Daniel Morton (Daniel Morton)
Original Redmine Issue: 20655
Affected QGIS version: 2.18.26
Redmine category:grass
script fail to move results from grass' temporary work are (Appdata).
I expect this is associated with the message: 'r was unexpected at this time'.
C:\OSGeo4W64\bin>g.gisenv.exe set="GISDBASE=C:\Users\user\AppData\Local\Temp\processing0fe29e2ca2af4404b4455312c20274a5\grassdata"
C:\OSGeo4W64\bin>g.gisenv.exe set="GRASS_GUI=text"
r was unexpected at this time.
C:\OSGeo4W64\bin>for r in $(g.list type=rast pattern='tmp15433306485454*'); do
Converting outputs
Loading resulting layers
Algorithm i.pca - Principal components analysis (PCA) for image processing. correctly executed...
The text was updated successfully, but these errors were encountered: