Markus,
Could you explain this ? Does this mean that the memory parameter in
r.in.gdal is now automagic ? Or why doesn't it make sens to let the user
define in r.import the memory size ?
Moritz
On 17/09/18 15:30, svn_gr...@osgeo.org wrote:
Author: neteler
Date: 2018-09-17 06:30:25 -0700 (Mon, 17 Sep 2018)
New Revision: 73360
Modified:
grass/branches/releasebranch_7_6/scripts/r.import/r.import.py
Log:
r.import: remove hardcoded memory limit (r.in.gdal will take care)
Modified: grass/branches/releasebranch_7_6/scripts/r.import/r.import.py
===================================================================
--- grass/branches/releasebranch_7_6/scripts/r.import/r.import.py
2018-09-17 13:29:35 UTC (rev 73359)
+++ grass/branches/releasebranch_7_6/scripts/r.import/r.import.py
2018-09-17 13:30:25 UTC (rev 73360)
@@ -39,7 +39,6 @@
#% type: integer
#% required: no
#% multiple: no
-#% options: 0-2047
#% label: Maximum memory to be used (in MB)
#% description: Cache size for raster rows
#% answer: 300
_______________________________________________
grass-commit mailing list
grass-com...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-commit
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
