[GRASS-user] limitations of r.stream.order
carlos.grohmann at gmail.com
Tue Apr 23 09:50:27 PDT 2013
Well, working with subsets of the area worked, It was indeed a RAM
On Sun, Apr 21, 2013 at 6:09 PM, Rich Shepard <rshepard at appl-ecosys.com>wrote:
> On Sun, 21 Apr 2013, Carlos Grohmann wrote:
> I need a detail a bit more compatible with topo maps at 1:1.000.000 scale,
>> which I can get if I use a threshold of 25-50 cells. But then, of course,
>> I have a more dense drainage network, and it seems that r.stream.order is
>> having problems dealing with such dense networks.
> Well, if your workstation has sufficient memory for all the calculations
> then I've no idea what to suggest. The largest area with which I've worked
> is 125 square miles (however many square kilometers that is) and I can
> delineate too many drainage basins with 4G RAM.
> Perhaps working in smaller chunks of area and recombining results will
> do the
> job. Otherwise, others with more expertise will need to offer suggestions.
> Richard B. Shepard, Ph.D. | Integrity - Credibility - Innovation
> Applied Ecosystem Services, Inc. |
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax:
Prof. Carlos Henrique Grohmann
Institute of Geosciences - Univ. of São Paulo, Brazil
- Digital Terrain Analysis | GIS | Remote Sensing -
Can’t stop the signal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-user