Il 19/10/2015 11:30, Markus Neteler ha scritto: > The problem is to "guess" how much memory resources are available > which change continuously (i.e. RAM is naturally static but its > allocation not).
sure - perhaps taking the total memory as an upper bound could mitigate at least the most serious cases. > Just check the "history" file of the mapset. Some previously issued > command will have set the computational region. > A candidate might be a g.region vector=vmap with an additional > (unneeded) res=value call (maybe from "Processing"?). right - interestingly enough, the history does not seem to be visible in the current version of the grass qgis plugin - going to explore this. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
