Opened 13 years ago
Last modified 6 years ago
#1674 new defect
r.cross problems when overlaying layers with no-data
| Reported by: | pvanbosgeo | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.0.7 |
| Component: | Raster | Version: | svn-trunk |
| Keywords: | r.cross, no data | Cc: | |
| CPU: | x86-64 | Platform: | Linux |
Description
When overlaying two layers that contain large areas of 'no data', r.cross seems to assign random values to raster cells with no-data, even when using the -z flag. See for example the output of r.what for a point where both input layers have no data but the raster cell get's assigned a value (30114 in the example below):
r.what --v -f -n input=wdpaPNV@ConsStat coordinates=1549281.412639,-1312241.263941 easting|northing|site_name|wdpaPNV@ConsStat|wdpaPNV@ConsStat_label
| 30114|no data; no data |
Probably because of this problem, r.cross cannot be run on large layers with large areas of no-data, it just get's stuck
Paulo
Running GRASS 7.0.svn (2012) on Ubuntu 12.04
Attachments (1)
Change History (6)
by , 13 years ago
| Attachment: | example.png added |
|---|
comment:1 by , 12 years ago
| Component: | Default → Raster |
|---|---|
| Milestone: | → 7.0.0 |
comment:2 by , 9 years ago
| Milestone: | 7.0.0 → 7.0.5 |
|---|
comment:3 by , 8 years ago
| Milestone: | 7.0.5 → 7.0.6 |
|---|
comment:4 by , 7 years ago
| Milestone: | 7.0.6 → 7.0.7 |
|---|
Note:
See TracTickets
for help on using tickets.
shows a result of r.cross, with random colors (and underlying values) for the area where the two input layers have no-data