Timeline for 1m DEM mosaicking results in a very large file; how can I reduce the size of the output file without compromising output quality?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2021 at 11:29 | history | became hot network question | |||
| May 9, 2021 at 6:50 | comment | added | bugmenot123 | Being a bit pedantic: The error is about an intermediate raster in memory, not the final output file. Like other said, a VRT is probably the best way to work around this. | |
| May 9, 2021 at 5:11 | history | edited | Vince | CC BY-SA 4.0 |
English usage
|
| May 9, 2021 at 4:21 | answer | added | ar-siddiqui | timeline score: 4 | |
| May 9, 2021 at 4:00 | comment | added | wingnut |
Without compromising quality? The image size is 27.9 GB at 32 bit. That's just how big it is. You can reduce resolution to Byte, which will reduce it to 7 GB. But that compromises quality. You could create a virtual dataset from the 72 images with gdalbuildvrt. That may be the easiest way to preserve resolution. Not sure how your software will cope later, however.
|
|
| May 9, 2021 at 3:26 | history | asked | user182365 | CC BY-SA 4.0 |