On 08/06/2012 12:13, Margherita Di Leo wrote:

Hi,

On Fri, Jun 8, 2012 at 1:44 AM, Rich Shepard <[email protected]> wrote:


 In Micha's blog article the cross_points.txt file is used as input to
r.water.outlet which generates the appropriate catchments. I assume this is
also true for r.basin; i.e., it will generate its own basins and sub-basins
based on the outlet points in the cross_points.txt file. Is this assumption
correct?
 
Correct. I've updated the wiki page http://grass.osgeo.org/wiki/R.basin#Preparation_for_multiple_basins.27_analysis
Rich, if you'll test this method, I would appreciate your feedback. Feel free to improve the wiki page (and to put it into real english :P )


Hi Madi:

Regarding the threshold value in your auxilliary parsing.py script, do you think it might be better to calcuclate a suggested value from the size of the original DEM, rather than just put in some random 10,000 or so.

Obviously the user has to understand, and change the threshold to suit his needs, but if the script is going to contain some value, maybe it should be something "reasonable". I thought, for example to choose a suggested thresh size of num_cells/100. i.e.:

N=`r.univar -g | grep "^n=" | cut -d "=" -f 2`

THRESH=$(( $N / 100))

Does that sound reasonable? Since the python auxilliary script runs independently of GRASS, I'm not sure how how this would all merge together. But it's worth thinking about.

Regards,

Micha

ciao madi

--
Dr. Margherita Di Leo

This mail was received via Mail-SeCure System.


_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user

This mail was received via Mail-SeCure System.




_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user

Reply via email to