On Sat, Sep 6, 2014 at 12:32 PM, Daniel Victoria <[email protected]> wrote: > Maybe, instead of throwing a memory error, grass could check the region size > and if the number of cells is too high, ask for user confirmation or suggest > how the user can change the region.
I have for now added a message: # test case: GRASS 7.1.svn (nc_spm_08_grass7):~ > g.region vect=zipcodes_wake res=5 -pa projection: 99 (Lambert Conformal Conic) zone: 0 datum: nad83 ellipsoid: a=6378137 es=0.006694380022900787 north: 258110 south: 196320 west: 610040 east: 677070 nsres: 5 ewres: 5 rows: 12358 cols: 13406 cells: 165671348 # new message about RAM added: GRASS 7.1.svn (nc_spm_08_grass7):~ > v.to.rast zipcodes_wake out=zipcodes_wake_area use=attr attrcol=SHAPE_Area --o Using at least 0.4 GB of RAM (adjust with 'rows' parameter) Pass 1 of 4: Reading areas... [...] # other test case: GRASS 7.1.svn (nc_spm_08_grass7):~ > g.region vect=zipcodes_wake res=1 -pa projection: 99 (Lambert Conformal Conic) ... rows: 61780 cols: 67020 cells: 4140495600 GRASS 7.1.svn (nc_spm_08_grass7):~ > v.to.rast zipcodes_wake out=zipcodes_wake_area use=attr attrcol=SHAPE_Area --o rows=10000 Using at least 4.6 GB of RAM (adjust with 'rows' parameter) ... Is that new message understandable? Markus _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
