<div dir="ltr"><div><div><div><div><div>Micha,<br><br></div>You raise very good questions. I think you may have misunderstood; perhaps I explained poorly. r.watershed is NOT running slowly; I have had no problems with r.watershed performance. The performance slowness I have had is with r.carve -- it is running very slowly.<br><br></div>I am also using GRASS 7.0RC1; but for the final step in one of my analysis (not what I have described here), I need to use r.arc.out, which is now handled by r.out.gdal; I have not had the chance to explore this, but the ascii output files generated by the two are different. I use a subsequent binary application (written by someone else) that reformats the GRASS r.out.arc output to a new binary grid file that is only used within the U.S. National Weather Service. So, wanting a more simplified workflow, I'm stuck with using GRASS 6.4.5 for some of this.<br><br></div>The reason I need to use the D8 (SFD) algorithm is that I am generating a file that identifies how pixels are connected hydraulically; the distributed hydrologic model I am using requires that this connectivity be unique; so a pixel must be uniquely connected to a single downstream pixel. Consequently, with the GRASS scripting I have done to produce the needed ascii output file I need, I think I have to use the D8 SFD algorithm.<br><br></div>Cheers!<br></div>Tom<br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 14, 2015 at 5:02 AM, Micha Silver <span dir="ltr"><<a href="mailto:micha@arava.co.il" target="_blank">micha@arava.co.il</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="direction:ltr" bgcolor="#FFFFFF" text="#000000">
Hi Thomas:<span class=""><br>
<br>
<div>On 02/13/2015 10:28 PM, Thomas Adams
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Micha,
<div><br>
</div>
<div>No, after looking at what's going-on in more detail, I
think the DEM is too coarse (even at 90m), so the flow
direction and accumulation is mis-directed in one critical
area of the watershed. I tried using r.carve, but it is taking
forever — after 15 minutes, no advancement of the progress
bar…</div>
<div><br>
</div>
</div>
</blockquote>
<br></span>
I don't see why carving into a DEM should cause r.watershed to run
more slowly, unless you have carved out only a section of some of
the streams. If your carving does not continue right to the outlet
of the stream (i.e. to an ocean, or to the edge of the region) then
r.watershed would actually have to fill in that carved out stream to
find a flow path. That could cause the performance hit. <br>
<br>
Additionally, are you using GRASS 7.0? As you probably know some
substantial improvements to the algorithms were introduced in 7 for
several modules, r.watershed among them.<br>
<br>
And third, why use the D8 flow direction when MFD is available
(again in GRASS 7.0)? That could also be causing what you refer to
as breaks in the channels. MFD is especailly good, I believe, in
flat areas.<br>
<br>
In any case, Keep up posted on your progress.<br>
Thanks,<br>
Micha<div><div class="h5"><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>I did not want to have to do this for my testing, but I'll
probably try at 3 or 10 meter — lots of pixels for my basin!
The problem, in general, for me is that I want to apply my
techniques at international locations where I probably won't
have the benefit of higher resolution DEMs, so I need to
develop something a bit more robust…</div>
<div><br>
</div>
<div>Cheers!</div>
<div>Tom</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Feb 13, 2015 at 1:15 PM,
Micha Silver <span dir="ltr"><<a href="mailto:micha@arava.co.il" target="_blank">micha@arava.co.il</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="direction:ltr" bgcolor="#FFFFFF" text="#000000"><span> <br>
<div>On 02/13/2015 08:48 PM, Thomas Adams wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Stefan,
<div><br>
</div>
<div>A fair question; since I know the stream
topology from personal experience it is clear
that there should be no break in the stream
network and the flow accumulation grid should
reflect that. I am seeing the flow accumulation
values break at a point where they should
continue to accumulate downstream.</div>
<div><br>
</div>
</div>
</blockquote>
<br>
</span> Are these breaks possibly caused by null pixels
in the DEM? <br>
<br>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>Tom</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Feb 13, 2015
at 11:43 AM, Stefan Lüdtke <span dir="ltr"><<a href="mailto:sluedtke@gfz-potsdam.de" target="_blank">sluedtke@gfz-potsdam.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN
PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi Tom,<br>
<br>
just out of curiosity, what do you mean by
"break in the flow<br>
accumulation"?<br>
<br>
Cheers,<br>
<br>
Stefan<br>
<div>
<div><br>
On 02/13/2015 07:12 PM, Thomas Adams
wrote:<br>
> Hello all!<br>
><br>
> I'm making use of the flow
accumulation grid in GRASS 6.4.5<br>
> generated from r.watershed using
the SFD (D8) flow algorithm. The<br>
> DEM has a 250m spatial
resolution. What I'm getting is a
break in<br>
> the flow accumulation in a few
locations which is causing me<br>
> serious problems with subsequent
processing (with help from some<br>
> here, I have put together some
scripting to generate a pixel<br>
> connectivity file for a
distributed hydrologic model).<br>
><br>
> Besides going to a higher
resolution DEM, are there any thoughts
as<br>
> to how I can eliminate these flow
accumulation breaks?<br>
><br>
> Thank you, Tom<br>
><br>
> --<br>
><br>
><br>
><br>
</div>
</div>
>
_______________________________________________
grass-user mailing<br>
> list <a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
><br>
<br>
- --<br>
Stefan Lüdtke<br>
<br>
Section 5.4- Hydrology<br>
Tel.: <a href="tel:%2B49%20331%20288%202821" value="+493312882821" target="_blank">+49
331 288 2821</a><br>
Fax: <a href="tel:%2B49%20331%20288%201570" value="+493312881570" target="_blank">+49
331 288 1570</a><br>
Email: <a href="mailto:sluedtke@gfz-potsdam.de" target="_blank">sluedtke@gfz-potsdam.de</a><br>
<br>
Helmholtz-Zentrum Potsdam<br>
Deutsches GeoForschungsZentrum GFZ<br>
(GFZ German Research Centre for
Geoscience)<br>
Stiftung des öff. Rechts Land Brandenburg<br>
Telegrafenberg, 14473 Potsdam<br>
- -------------------<br>
<br>
PGP Public Key: <a href="http://bit.ly/13d9Sca" target="_blank">http://bit.ly/13d9Sca</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
<br>
iQEcBAEBAgAGBQJU3kXYAAoJEB5GAbKcg+D8YqMH/jgJZ70cz69IJal6ICi66wqW<br>
lQYnnko592KAOlFDu1lReZhWWVgeA59rDsYA2Gg/rBzoL9Nst3hzIJDWqnhIWl3W<br>
YgF/vOJgTRnrNJtOibGpOc8hxrHwElxU7afYlXU8Zk+4tXdZRK4/vrQ4tKEcbY0z<br>
MrhAYjR66RRpoNf9/3WJ3s14CpPA+KEkOaysOOoTV6Ni7qZTK8rVxt+svQQoPtW+<br>
5QwRJLkLeM6bUrqfQifHis91j4k3JSoSp7ZjIInKwi1tvCSfcFQhzvANs4x8e1Lo<br>
Q5wDbzHshhJieGKyraUZyT8cn9vszv9cm2Sf49O/0FWVz3Eyc9vsKFxVcvfEb1E=<br>
=Sy/3<br>
-----END PGP SIGNATURE-----<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div><br>
<div><br>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
This mail was received via Mail-SeCure System.<br>
<br>
<fieldset></fieldset>
<br>
<pre><span>_______________________________________________
grass-user mailing list
<a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a></span>
This mail was received via Mail-SeCure System.
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
<br>
<div>
<div><br>
</div>
</div>
</div>
</div>
<br>
This mail was received via Mail-SeCure System.<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br><div><br></div>
</div></div>