[gdal-dev] Memory error for gdal_grid if using nearest

Armin Schmidt Armin.R.Schmidt at Gmail.com
Thu Jul 16 12:03:52 PDT 2015


I have a very simple point-shapefile which throws various memory 
allocation errors when I try to grid it with gdal_grid using "nearest", 
but works absolutely fine and fast when using the "invdist" algorithm. I 
never had this problem before. Does anyone have any idea what is wrong? 
If it would help I can provide the shapefile.

The stripped down command-line is:

gdal_grid.exe 02VHiDep_raw.shp test.tif -ot Float32 -of GTiff -zfield 
Cond1_mSm -l 02VHiDep_raw -a nearest

After taking some time (probably searching for the nearest neighbours), 
this throws:

ERROR 1: CPLMalloc(): Out of memory allocating 64 bytes.
FATAL: CPLMalloc(): Out of memory allocating 64 bytes.
ERROR 1: TIFFWriteDirectorySec:Out of memory
ERROR 2: Cannot allocate 8192 bytes
ERROR 1: TIFFWriteDirectorySec:Out of memory
ERROR 1: TIFFWriteDirectorySec:Out of memory

Grid data type is "Float32"
Grid size = (256 256).
Corner coordinates = (449675.737076 6895223.317256)-(449705.249717 
6895209.690215).
Grid cell size = (0.114835 0.053024).
Source point count = 3280.
Algorithm name: "nearest".
Options are 
"radius1=0.000000:radius2=0.000000:angle=0.000000:nodata=0.000000"

Armin

-- 
__________________________________________________________________
Dr. Armin Schmidt
Chief Developer, GeodataWIZ Ltd:  Geo Data + Visualisation
  www.GeodataWIZ.com
  www.GeodataWIZ.com/armin-schmidt
Chairman, Internat. Society for Archaeological Prospection
  www.archprospection.org
Honorary Visiting Research Fellow, University of Bradford
  Department of Archaeological Sciences
Honorary Fellow, Durham University, Department of Archaeology
http://orcid.org/0000-0002-4241-5381

Email: Armin.R.Schmidt at Gmail.com

Now available:
Earth Resistance for Archaeologists (2013). Lanham: AltaMira Press
Geophysical Data in Archaeology (2013). Oxford: Oxbow Books.
http://www.amazon.co.uk/-/e/B0034QC4OW
__________________________________________________________________


More information about the gdal-dev mailing list