r.texture NULL or negative value ERROR (possible r.null problem)

[khufkens]

Concerning r.texture in GRASS 6.3:

Running r.texture on a map after r.null (should have) replaced all NULL values still produces an error indicating a persistent NULL or negative value in the map.

r.category shows no NULL values or negative values but yet they are there for r.texture...

Adding a fixed value to the map with the map calculator or running a running window analysis removes these hidden values and also removes the error.

This traces back to either an error in r.texture or r.null, not sure...

[neteler]

for the record:

On Tue, Nov 25, 2008 at 2:29 AM, Hamish:

maybe something like this: ​http://trac.osgeo.org/grass/changeset?new=grass%2Ftrunk%2Fraster%2Fr.los%2Fpts_elim.c%4025104&old=grass%2Ftrunk%2Fraster%2Fr.los%2Fpts_elim.c%4018934

[hamish]

what does r.univar say, before and after r.null?

(run 'g.region rast=yourmap' first)

Hamish

[khufkens]

Ok,

seems that setting g.region makes the error disappear. Sorry, for the inconvencience...

Koen