<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1421174271058_5607" dir="ltr"><span id="yui_3_16_0_1_1421174271058_5639" class="" style=""> One more idea is to make sure the DEM is projected. </span>Flow algorithms, in GRASS and ArcGIS, get messed up by unprojected surfaces. Be careful choosing a projection for such a large area. </div><div id="yui_3_16_0_1_1421174271058_5607" dir="ltr" class="" style=""><span id="yui_3_16_0_1_1421174271058_5859"> Also projecting should be done after you put the mosaic together, as you may get streaks around the boundaries of the individual DEMs that will affect the flow. Or just run the individual DEMs and assemble the flow maps after.</span></div><div id="yui_3_16_0_1_1421174271058_5607" dir="ltr"><br></div><div id="yui_3_16_0_1_1421174271058_5607" dir="ltr">-Thayer</div><br> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1421174271058_5671"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1421174271058_5670"> <div dir="ltr" id="yui_3_16_0_1_1421174271058_5669"> <hr size="1" id="yui_3_16_0_1_1421174271058_5725"> <font size="2" face="Arial" id="yui_3_16_0_1_1421174271058_5672"> <b><span style="font-weight:bold;">From:</span></b> Daniel Victoria <daniel.victoria@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Charlie Shobe <chsh5846@colorado.edu> <br><b><span style="font-weight: bold;">Cc:</span></b> Thayer Young <thayeray@yahoo.com>; "grass-user@lists.osgeo.org" <grass-user@lists.osgeo.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, January 13, 2015 10:46 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [GRASS-user] r.terraflow on massive DEM<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1421174271058_5962"><br><div id="yiv1690828645"><div id="yui_3_16_0_1_1421174271058_5965"><div dir="ltr" id="yui_3_16_0_1_1421174271058_5964"><div id="yui_3_16_0_1_1421174271058_5963"><div>Charlie,<br clear="none"><br clear="none"></div>I just downloaded some SRTM 1arc sec. from EarthExplorer. The data is supplied in 3 different file types, GeoTIFF, DTED or BIL and they are all in Integer values (Int16). No floating point elevation values.<br clear="none"><br clear="none"></div>Cheers<br clear="none">Daniel<br clear="none"></div><div class="qtdSeparateBR"><br><br></div><div class="yiv1690828645yqt5127148673" id="yiv1690828645yqt77896"><div class="yiv1690828645gmail_extra" id="yui_3_16_0_1_1421174271058_5970"><br clear="none"><div class="yiv1690828645gmail_quote" id="yui_3_16_0_1_1421174271058_5969">On Tue, Jan 13, 2015 at 12:12 PM, Charlie Shobe <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:chsh5846@colorado.edu" target="_blank" href="mailto:chsh5846@colorado.edu">chsh5846@colorado.edu</a>></span> wrote:<br clear="none"><blockquote class="yiv1690828645gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" id="yui_3_16_0_1_1421174271058_5968"><div id="yui_3_16_0_1_1421174271058_5967"><div id="yui_3_16_0_1_1421174271058_5966">Hi Daniel,</div><div><br clear="none"></div><div>I believe that SRTM data does in fact provide floating point elevation values, so you may want to try working with the DEM as type FCELL from the very beginning. I don't know if this will help solve your problem, but the last time I brought in SRTM (1 arc second) data it was type FCELL and contained several decimal places of precision.</div><div><br clear="none"></div><div>Good luck,</div><div><br clear="none"></div><div>Charlie<br clear="none"><br clear="none"></div><div><div class="yiv1690828645h5"><div><br clear="none">On Jan 13, 2015, at 4:00 AM, Daniel Victoria <<a rel="nofollow" shape="rect" ymailto="mailto:daniel.victoria@gmail.com" target="_blank" href="mailto:daniel.victoria@gmail.com">daniel.victoria@gmail.com</a>> wrote:<br clear="none"><br clear="none"></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div><div>Stephan, I'll give r.watershed a try and let it run for a couple of days. Thanks<br clear="none"><br clear="none"></div>Thayer, I used r.recode because the person that sent me the data messed up the null values. So in order to fix that I did:<br clear="none"></div>1) use r.external to bring the data to Grass<br clear="none"></div>2) fix null values with r.recode, which was faster than r.null<br clear="none"><br clear="none"></div>But I gave up on that path and since imported the data (r.in.gdal) and fixed the null values with r.null.<br clear="none"></div>I'm also using integer values (CELL type) because from what I heard, SRTM does not provide floating point data.<br clear="none"><br clear="none"></div>Now I tried to run r.terraflow but I got a type error which asked me to use r.terraflow.short. Since I don't have that command in my grass instalatin, I converted the SRTM data to float. But that was to no avail since it's now giving me a dimensions type overflow error and asking me to change the dimension_type and recompile.<br clear="none"><br clear="none"></div>I'll give r.watershed a try. If that does not work, I'll see if I can recompile.<br clear="none"><br clear="none"></div>Thanks<br clear="none">Daniel<br clear="none"></div><div class="yiv1690828645gmail_extra"><br clear="none"><div class="yiv1690828645gmail_quote">On Mon, Jan 12, 2015 at 9:22 PM, Thayer Young <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:thayeray@yahoo.com" target="_blank" href="mailto:thayeray@yahoo.com">thayeray@yahoo.com</a>></span> wrote:<br clear="none"><blockquote class="yiv1690828645gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div>W<span>ith regards to the size of DEM, if you can get the command to run it may take several days to finish, this is more than twice the size of the Washington State DEM that took the authors 33 hours in 2003 (Arge, Chase, Halpin, Toma, Urban, Vitter, Wickremesinghe Efficient Flow Computation on Massive Grid Terrain Datasets </span>Geoinformatica
Volume 7 Issue 4, December 2003
<span>Pages 283 - 313
). My mid-2014 computer runs at about twice the speed quoted in the paper.</span></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Did you r.recode it to make it smaller? In flat areas you need the data contained after the decimal point to allow the flow a chance to make it down hill, otherwise you can get streams going no where near where they do in real life. I have never tried running r.terraflow on an integer raster, I know that it works on decimal rasters.<br clear="none"></div><div dir="ltr"><br clear="none"><span></span></div><div>-Thayer</div><div><br clear="none"></div><div><br clear="none"></div><div> <br clear="none"></div><div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div> <hr size="1"><font face="Arial"><b><span style="font-weight:bold;"></span></b></font><br clear="none">Date: Mon, 12 Jan 2015 09:59:40 -0200<br clear="none">From: Daniel Victoria <<a rel="nofollow" shape="rect" ymailto="mailto:daniel.victoria@gmail.com" target="_blank" href="mailto:daniel.victoria@gmail.com">daniel.victoria@gmail.com</a>><br clear="none">To: grass <<a rel="nofollow" shape="rect" ymailto="mailto:grass-user@lists.osgeo.org" target="_blank" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>><br clear="none">Subject: [GRASS-user] r.terraflow on massive DEM<br clear="none">Message-ID:<br clear="none"> <CA+irsJjf7xhWgU968D+4+xc2YGJ=<a rel="nofollow" shape="rect" ymailto="mailto:_n4xJtP0_WeU1ZpoRTt9ng@mail.gmail.com" target="_blank" href="mailto:_n4xJtP0_WeU1ZpoRTt9ng@mail.gmail.com">_n4xJtP0_WeU1ZpoRTt9ng@mail.gmail.com</a>><br clear="none">Content-Type: text/plain; charset="utf-8"<div><div><br clear="none"><br clear="none">Hi list,<br clear="none"><br clear="none">I'm trying to run r.terraflow on a very large DEM but I wander if it's<br clear="none">__too large__.<br clear="none"><br clear="none">The region dimensions are:<br clear="none">ncol=141114<br clear="none">nrow=140487<br clear="none">Data type = CELL<br clear="none"><br clear="none">The map is actually a reclass map of a raster that I imported using<br clear="none">r.external.<br clear="none"><br clear="none">When I run r.terraflow I get:<br clear="none"><br clear="none">r.terraflow elevation=<a rel="nofollow" shape="rect" ymailto="mailto:srtm_brasil@PERMANENT" target="_blank" href="mailto:srtm_brasil@PERMANENT">srtm_brasil@PERMANENT</a> filled=srtm_fill<br clear="none">direction=flowdir swatershed=sink accumulation=flowacc tci=srtm_tci<br clear="none">directory=E:\terraflow_temp<br clear="none"><br clear="none">WARNING: raster srtm_brasil is of type CELL_TYPE --you should use<br clear="none">r.terraflow.short<br clear="none">ERROR: [nrows=140487, ncols=141114] dimension_type overflow -- change<br clear="none">dimension_type and recompile<br clear="none">(Mon Jan 12 09:57:18 2015) Command finished (0<br clear="none">sec)<br clear="none"><br clear="none">However, I don't have an r.terraflow.short command<br clear="none">I'm running Grass 7.0.0beta4 from OsGeo4W<br clear="none"><br clear="none">Cheers<br clear="none">Daniel<br clear="none"></div></div>-------------- next part --------------<br clear="none">An HTML attachment was scrubbed...<br clear="none">URL: <<a rel="nofollow" shape="rect" target="_blank" href="http://lists.osgeo.org/pipermail/grass-user/attachments/20150112/a27c139f/attachment-0001.html">http://lists.osgeo.org/pipermail/grass-user/attachments/20150112/a27c139f/attachment-0001.html</a>><br clear="none"><br clear="none">------------------------------<span><br clear="none"><br clear="none">_______________________________________________<br clear="none">grass-user mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:grass-user@lists.osgeo.org" target="_blank" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br clear="none"><br clear="none"></span>End of grass-user Digest, Vol 105, Issue 16<br clear="none">*******************************************<br clear="none"><br clear="none"><br clear="none"></div> </div> </div> </div></div><br clear="none">_______________________________________________<br clear="none">
grass-user mailing list<br clear="none">
<a rel="nofollow" shape="rect" ymailto="mailto:grass-user@lists.osgeo.org" target="_blank" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br clear="none"></blockquote></div><br clear="none"></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br clear="none"><span>grass-user mailing list</span><br clear="none"><span><a rel="nofollow" shape="rect" ymailto="mailto:grass-user@lists.osgeo.org" target="_blank" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a></span><br clear="none"><span><a rel="nofollow" shape="rect" target="_blank" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a></span></div></blockquote></div></div></div></blockquote></div><br clear="none"></div></div></div></div><br><br></div> </div> </div> </div></body></html>