[GRASS-user] Problems with r.terraflow and r.thin

Hamish hamish_nospam at yahoo.com
Wed Aug 15 02:02:15 EDT 2007

christian.braun wrote:
> I am currently working on the generation of watersheds for a small
> european country;-)
> Due to the amount of data (4089x2860, res=20) I have to use
> r.terraflow instead of r.watershed.
> In my opinion the outcoming watersheds of r.terraflow are not really
> compact, rather fuzzy at the borders. See attached file.
> Whats going here?

maybe Helena and Laura's comments help:

searching the mailing lists turns up some more, such as:

> Could that be the problem for my results in r.thin, which are
> completly unuseable? See attached file.

garbage in, garbage out of course. Make sure all your inputs are healthy
before undertaking the next step... I'm not familiar with your dataset
so no idea how good/bad r.thin did, or even what you are thinning.
(stream network?)

> Any ideas to solve this problem?

Let GRASS 6.2.2's r.watershed run for a week or three until you get a
result. Try without the -m flag first, only use that if you get out-of-
memory errors. Eventaully it gets done, it just takes a while.

tip - set shell priority low before starting a long-running process:
GRASS> renice +19 -p $$
GRASS> r.watershed ...

You can make grass shell always start up at a lower priority by adding
the renice to ~/.grass.bashrc


More information about the grass-user mailing list