When overlaying two layers that contain large areas of ‘no data’, r.cross seems to run forever. Running an equally large areas without ‘no data’ is no problem on the other hand.
I tried to run r.cross for a much smaller area and the problem seems to be that r.cross assigns some random value to areas with no-data, even when using the -z flag. See the output of r.what for a point where both input layers have no data:
r.what --v -f -n input=wdpaPNV@ConsStat coordinates=1549281.412639,-1312241.263941 easting|northing|site_name|wdpaPNV@ConsStat|wdpaPNV@ConsStat_label 1549281.412639|-1312241.263941||30114|no data; no data
Attached see also a screen shot, with the no-data area with seemingly random pattern of colors.
I am submitting this as a bug report, as I probably should have done to start with
On 06/13/2012 10:59 AM, Paulo van Breugel wrote:
Hi
When overlaying two layers that contain large areas of ‘no data’, r.cross seems to run forever. Running an equally large areas without ‘no data’ is no problem on the other hand.
I tried to run r.cross for a much smaller area and the problem seems to be that r.cross assigns some random value to areas with no-data, even when using the -z flag. See the output of r.what for a point where both input layers have no data:
r.what --v -f -n input=wdpaPNV@ConsStat coordinates=1549281.412639,-1312241.263941 easting|northing|site_name|wdpaPNV@ConsStat|wdpaPNV@ConsStat_label 1549281.412639|-1312241.263941||30114|no data; no data
Attached see also a screen shot, with the no-data area with seemingly random pattern of colors.
