[GRASS-user] r.texture NULL value error

[Hufkens Koen]

It seems that r.null missed some NULL values or some negative values are still there (one or both issues may be the cause).

Anyway I worked around it by adding a fixed amount with the map calculator and rescaling it to the wanted scale.

This workaround seems to be foolproof and confirms that there must be a NULL value or a negative value that is missed by the summary statistics and r.null causing r.texture to go into spasm.

So, it's fixed and not fixed at the same time. Maybe I'll look into the code later.

Cheers,
Koen


-----Oorspronkelijk bericht-----
Van: neteler.osgeo at gmail.com namens Markus Neteler
Verzonden: ma 24-11-2008 15:46
Aan: Hufkens Koen
CC: GRASS user list
Onderwerp: Re: [GRASS-user] r.texture NULL value error
 
On Mon, Nov 24, 2008 at 2:39 PM, Hufkens Koen <koen.hufkens at ua.ac.be> wrote:
> Hi list,
>
> I've been trying to run a r.texture filter on a map but I constantly get the
> error:
>
> ERROR: Negative or no data pixel found. This module is not yet able to
>        process no data holes in a map, please fill with r.fillnulls or
>        other algorithms
>

I ran into this myself a few minutes ago :)
The trick is that *all* pixels in the current region are need to be
set to non-NULL.
If NULL pixels are present, r.texture fails.

run
r.univar mapname
to see how many NULL cells are in the current region.

Solution:
- either zoom into area without NULL pixels (won't always make sense)
- or fill the NULL areas with some value (various options)
- (or fix r.texture if possible).

Markus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20081125/1574c337/attachment.html