"Killed" ... Memory usage? about tin-terrain HOT 3 CLOSED

You are correct, it's a memory issue. If you need a ballpark estimate of memory requirements then just assume that your raster must fit in memory. If you need to process rasters larger than memory, I can suggest splitting it into smaller tiles before meshing (i.e. with https://www.gdal.org/gdal2tiles.html). But of course it's not a convenient solution.

from tin-terrain.

I'm curious how others use this tool in the real world. If I cut my image into smaller parts, won't there be "seam lines" - areas where the terrain has odd lines due to it being the edge of the source DEMs? This 500gb run was going to be my "small" test, as I has hoped to do the same thing at ~1m instead of ~30m.

from tin-terrain.

And you are correct, splitting raster into chunks will produce artifacts at tile borders. However, visibility of these artifacts also depend on a lighting model you use to render the landscape. One more option is to rent one of these instances and do the work there.

Anyways, at this point processing larger-than-memory datasets is not supported. Unfortunately I can't even tell for sure that it is in a part of a development backlog (although it might be included there suddenly). I will close this issue for now.

from tin-terrain.