[GRASS-user] Error in r.in.gdal: CPLCalloc(): Out of memory allocating for "EHdr/ESRI .hdr Labelled" driver

Eric_Patton · April 11, 2007, 6:24pm

I'm trying to import a pile of Arc floating point binary rasters (.flt and .hdr extensions) with r.in.gdal:

$ r.in.gdal input=45_18_N_66_06_W_BACKSCATTER.flt output=45_18_N_66_06_W -oe
WARNING: Over-riding projection check.
ERROR 2: CPLCalloc(): Out of memory allocating -329 bytes.

Aborted (core dumped)

AFAIK, these rasters are in New Brunswick Double Stereographic projection (EPSG 2953), and I've already set up the current location with these projection parameters. gdalinfo doesn't seem to have a problem identifying the files:

$ gdalinfo 45_18_N_66_06_W_BACKSCATTER.flt

Driver: EHdr/ESRI .hdr Labelled
Size is 2641, 3721
Coordinate System is `'
Origin = (2531369.500000000000000,7366720.500000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
Corner Coordinates:
Upper Left ( 2531369.500, 7366720.500)
Lower Left ( 2531369.500, 7362999.500)
Upper Right ( 2534010.500, 7366720.500)
Lower Right ( 2534010.500, 7362999.500)
Center ( 2532690.000, 7364860.000)
Band 1 Block=2641x1 Type=Byte, ColorInterp=Undefined
  NoData Value=255
  Metadata:
    NBITS=-

I'm using a fresh install of GDAL 1.4.1, along with a fresh 6.3 cvs update from today. I see that at 1m resolution, the output raster would be 9,827,161 cells in size - pretty big. Is this the source of the CPLCalloc error?

Can anything be done as a workaround, i.e., using gdal tools to reduce the resolution of the output raster on the fly? I have 350 of these rasters to import.

Thanks,

~ Eric.

Frank_Warmerdam · April 11, 2007, 6:54pm

Patton, Eric wrote:

I'm trying to import a pile of Arc floating point binary rasters (.flt and .hdr extensions) with r.in.gdal:

$ r.in.gdal input=45_18_N_66_06_W_BACKSCATTER.flt output=45_18_N_66_06_W -oe
WARNING: Over-riding projection check.
ERROR 2: CPLCalloc(): Out of memory allocating -329 bytes.

Aborted (core dumped)

...

I'm using a fresh install of GDAL 1.4.1, along with a fresh 6.3 cvs update from today. I see that at 1m resolution, the output raster would be 9,827,161 cells in size - pretty big. Is this the source of the CPLCalloc error?

Can anything be done as a workaround, i.e., using gdal tools to reduce the resolution of the output raster on the fly? I have 350 of these rasters to import.

Eric,

This isn't a big raster, so that's not the problem. Can you try
"gdalinfo -mm" on the same file? Negative allocation errors normally
mean a bug somewhere in the driver code. If gdalinfo -mm also has
a similar error, then file a bug against GDAL and ensure you include
the .flt header (the data itself should not be needed).

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org

Eric_Patton · April 11, 2007, 6:42pm

Frank,

Thanks for the feedback. The error persists with gdalinfo -mm:

$ gdalinfo -mm 45_18_N_66_06_W_BACKSCATTER.flt

Driver: EHdr/ESRI .hdr Labelled
Size is 2641, 3721
Coordinate System is `'
Origin = (2531369.500000000000000,7366720.500000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
Corner Coordinates:
Upper Left ( 2531369.500, 7366720.500)
Lower Left ( 2531369.500, 7362999.500)
Upper Right ( 2534010.500, 7366720.500)
Lower Right ( 2534010.500, 7362999.500)
Center ( 2532690.000, 7364860.000)
Band 1 Block=2641x1 Type=Byte, ColorInterp=Undefined
ERROR 2: CPLCalloc(): Out of memory allocating -329 bytes.