[GRASS-user] "WARNING: Line ignored as requested" in processing ASTER GDEM2 tiles

Hi list!

In processing ASTER GDEM2 tiles over Portugal, using r.denoise, I get (too)
many WARNINGS like:

--%<---
WARNING: Line ignored as requested
WARNING: Not enough data columns. Incorrect delimiter or column number?
        Found the following character(s) in row 4296516:
        [-8.855 37.6686111111111]
--->%--

and so on.

For example, using a for loop to execute the following

r.denoise --o in="${ASTGTM2}" out="${ASTGTM2}"_smoothed iterations=10
threshold=0.8 epsg=3763

failed for some tiles. What do the WARNING messages mean? Could it be that
the tiles are corrupted?

Also, no matter what color rules I try to apply to all (original) tiles, be it
with "-e" or without, the overall drawn tiles look weird, i.e. there is no
seamless integration of the tiles. This is something not expected normally.

Anyone experienced the same problem(s)?
Thank you, Nikos

On Fri, Jan 25, 2013 at 3:39 PM, Nikos Alexandris
<nik@nikosalexandris.net> wrote:

Hi list!

In processing ASTER GDEM2 tiles over Portugal, using r.denoise, I get (too)
many WARNINGS like:

--%<---
WARNING: Line ignored as requested
WARNING: Not enough data columns. Incorrect delimiter or column number?
                                Found the following character(s) in row 4296516:
                                [-8.855 37.6686111111111]
--->%--

and so on.

Please try

http://grasswiki.osgeo.org/wiki/GRASS_Debugging#Shell_script_debugging

to figure out where it happens. A candidate is as usual "mdenoise"...

Markus

Nikos Alexandris wrote:

> In processing ASTER GDEM2 tiles over Portugal, using r.denoise, I get
> (too) many WARNINGS like:
> --%<---
> WARNING: Line ignored as requested
> WARNING: Not enough data columns. Incorrect delimiter or column number?
>
> Found the following character(s) in row
> 4296516:
> [-8.855 37.6686111111111]
>
> --->%--
> and so on.

Markus Neteler wrote:

Please try
http://grasswiki.osgeo.org/wiki/GRASS_Debugging#Shell_script_debugging
to figure out where it happens. A candidate is as usual "mdenoise"...

Not sure whether it was "mdenoise" or "available system RAM". Looping over
the same process on a smaller set of maps, did complete successfully :-).

Nikos