[GRASS-user] r.basin not running completely

Margherita Di Leo diregola at gmail.com
Sat Apr 25 00:12:04 PDT 2020


cc list

On Sat, Apr 25, 2020 at 9:11 AM Margherita Di Leo <diregola at gmail.com>
wrote:

> Hi,
>
> On Sat, Apr 25, 2020 at 8:49 AM jomaljochan <jochanjomal1998 at gmail.com>
> wrote:
>
>> Hi, I am a new GRASS GIS User (using GRASS GIS 7.6.1) trying to get the
>> morphometric parameters of a watershed(Bhadra river basin, India).
>> Steps followed:
>> 1) Cropped and set the DEM file in UTM projection.
>> 2) Created a new location and used the georeferenced DEM file to set the
>> projection of GRASS Session.
>> 3) Ran the following lines of code:
>>
>>   g.region rast=elevation at PERMANENT -ap
>>
>>   r.watershed -a elevation=elevation at PERMANENT accumulation=accum
>>
>>   r.stream.extract elevation=elevation at PERMANENT accumulation=accum
>> threshold=1000
>>   stream_rast=stream_network stream_vect=streams --overwrite
>>   #(overwrite with different threshold until clear network)
>>
>>   #Find the coordinates of the outlet from network and input in r.basin fn
>>
>>   r.basin map=elevation at PERMANENT prefix=out
>> coordinates=572957.585125,1547823.44718
>>   threshold=20 dir=tmp/my_basin
>>
>>
>>
>> The function stops running with the following error:
>>
>>   ERROR: option <output>: <tmp/my_basin\out_elevation_outlet_coors.txt>
>> exists. To overwrite, use the
>>   --overwrite flag
>>
>>   ------------------------------
>>
>>   An ERROR occurred running r.basin
>>   Please check for error messages above or try with another pairs of
>> outlet
>> coordinates
>>   Removing region definition <original>
>>
>> The command is telling you that an output with the same name is already
> there. You need to delete it* and run the command again.
>
> *Sorry r.basin doesn't handle overwrite, as written in the manual.
>
> Hope this helps.
>
> Kind regards,
>
>
> --
> Margherita Di Leo
>


-- 
Margherita Di Leo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20200425/049c4e27/attachment.html>


More information about the grass-user mailing list