[GRASS-user] ERROR: Bytes do not match file size with r.in.bin (but file size is correct!!)

[Ludovico Nicotina]

Thank you for your answers. A few info on my system:

I'm running on a computational node under linux with 64GB or RAM the machine architecture is a x86_64 and the kernel is also 64bit (running getconf LONG_BIT output is 64)

The version of GRASS I am running is 6.4.1

Also I don't have any problem allocating in fortran an 4bytes array of size 19450x29404x15 on the same machine, so I would exclude system limitations and it's likely to be a GRASS issue.

Thanks,

Ludovico

-----Original Message-----
From: Hamish [mailto:hamish_b at yahoo.com]
Sent: 07 May 2013 22:13
To: grass-user at lists.osgeo.org; Ludovico Nicotina
Subject: Re: [GRASS-user] ERROR: Bytes do not match file size with r.in.bin (but file size is correct!!)

Ludovico wrote:
> I get this error while running the following command:
...
> r.in.bin -f input=inputfile.bin output=outputmap bytes=4 n=51:05:20.4N
> s=41:21:50.4N w=5:08:31.2W e=9:33:36E r=19450
> c=29404 anull=-9999.0 --overwrite
...
> WARNING: File Size -2007336096 ... Total Bytes 2287631200
> ERROR: Bytes do not match file size 256
>
> Note the minus sign in front of the first value given for the files
> size in the warning message. Important to notice also that when I do
> an ls –l on the binary input file I get the correct size
> (19450x29404x4):
>
> -rw-rw-r-- 1 user group 2287631200 May  7 15:05 inputfile.bin
>
> Any suggestion on the origin of this error?

what version of GRASS are you using? That overflow should have been fixed just after 6.4.1 was released.


> Is there any limit on the file size for importing binaries into GRASS?

there shouldn't be, other than what the operating system is limited by.


Hamish


This message and any attachments contain information that may be RMS Inc. confidential and/or privileged.  If you are not the intended recipient (or authorized to receive for the intended recipient), and have received this message in error, any use, disclosure or distribution is strictly prohibited.   If you have received this message in error, please notify the sender immediately by replying to the e-mail and permanently deleting the message from your computer and/or storage system.