Answers for "raster - outofmemory exception" The latest answers for the question "raster - outofmemory exception" Answer by david_r <p>Hi</p><p>This is a known issue with the ReframeReprojector. Internally it does an affine transformation on all the pixels, skewing and interpolating along the way, which is very memory intensive.</p><p>You might want to ask yourself if subpixel accuracy makes sense in your context. If it is important to you, consider using the Tiler to split the raster into smaller units before sending them off to the ReframeReprojector. But the tiles might not line up perfectly after and the edges might not be completely straight (empty pixels will be set to NODATA).</p><p>For most rasters, it will suffice to use the CsMapReprojector, which is slightly less precise but a lot faster, as it uses a simpler grid transformation.</p><p>Another option is to find the center point of each raster using the CenterPointReplacer, reproject the point using the ReframeReprojector, calculate the offset and then apply the offset on the whole raster using the Offsetter. This has the bonus of being fairly accurate, very fast and will preserve perfectly straight edges in the resulting raster. My colleague has written a fews words on this <a target="_blank" href="">here (in french), look under "Transformation par bloc"</a>.</p><p>David</p> Tue, 26 Jan 2016 15:50:02 GMT david_r