[GRASS-user] r.proj error
lists at lazygranch.com
Wed Jun 21 13:08:50 EDT 2006
Hamish spotted that my projected raster map (via r.proj) has "nan" data
in it, which is probably the source of errors. The data on the input map
is fine, but unfortunately in lat/long format, unsuitable for r.los.
I adjusted the resolution, and r.los still bombs, but again, it is due
to the data.
Thanks for the tip on --enable-largefile. I noticed that the r.los
analysis required 1.8Gbytes, even at the reduced resolution (30 meters).
The PC has about 3.4Gbytes of ram. [Technically, it has 4G, but for
some reason, the mobo can't use it all.]
Glynn Clements wrote:
> gary wrote:
>>I've compiled Grass 6.1. The r.proj at the lower resolution worked fine
>>(Hamish's tip to prevent a 80GByte file!). The r.los bombed. Here are
>>some of the warning messages:
>>WARNING: segment_seek: Invalid argument
>>WARNING: Failed seek in segment file for index = 240605900 n = 12 at
>> col:row 0:201054
> 200,000 rows?
> If the number of columns is anywhere near that figure, the segment
> file will be >2Gb, which probably won't work unless you configured
> GRASS with the --enable-largefile option (it may not even work then;
> it depends whether anyone has actually tested r.los with large file
> support enabled).
More information about the grass-user