Timeline for How to avoid very large output rasters using grass algorithms
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2016 at 12:26 | comment | added | joaoal | @dmci. I found out playing around with the gdal options. Your comment provided me the way to go. thx. | |
| Nov 25, 2016 at 12:25 | answer | added | joaoal | timeline score: 5 | |
| Nov 24, 2016 at 21:03 | comment | added | dmci |
regarding the region - you can easily check if it is correct by examining the output of gdalinfo on your input and output files. e.g. gdalinfo input.tif and specifically check the Extent
|
|
| Nov 24, 2016 at 19:58 | comment | added | joaoal |
@dmci i edited the question according to your remarks. I use the GUI in QGIS but from what I can tell createopt="COMPRESS=LZW" was set automatically. Not sure about the region though...could you have a look if this helps...
|
|
| Nov 24, 2016 at 19:56 | history | edited | joaoal | CC BY-SA 3.0 |
added 1594 characters in body
|
| Nov 24, 2016 at 17:38 | history | tweeted | twitter.com/StackGIS/status/801842517058711552 | ||
| Nov 24, 2016 at 14:30 | comment | added | dmci |
have you checked that your GRASS region is correct (g.region) and assuming you have used r.out.gdal have you included the createopt i.e. createopt="COMPRESS=LZW"
|
|
| Nov 24, 2016 at 13:43 | history | edited | whyzar | CC BY-SA 3.0 |
corrected spelling, improved formatting
|
| Nov 24, 2016 at 12:36 | history | asked | joaoal | CC BY-SA 3.0 |