R.basin - Revision history

⚠️Madi: /* Maps */

2017-08-10T10:02:57Z

Maps

← Older revision		Revision as of 10:02, 10 August 2017
Line 351:		Line 351:
	out_elevation_basin out_elevation_network		out_elevation_basin out_elevation_network
	out_elevation_mainchannel out_elevation_outlet		out_elevation_mainchannel out_elevation_outlet
			out_elevation_outlet_snap
	</pre>		</pre>

Line 363:		Line 364:
	</gallery>		</gallery>
	</center>		</center>

			The vector map out_elevation_outlet_snap has a table associated, that stores all the parameters calculated. The outlet_snap is the outlet moved to the nearest river network, and can slightly differ from the outlet given by the coordinates pair, in case this latter doesn't fall on the (calculated) river network.

	== Graphics ==		== Graphics ==

⚠️Madi at 09:56, 10 August 2017

2017-08-10T09:56:23Z

← Older revision		Revision as of 09:56, 10 August 2017
Line 388:		Line 388:
	# r.basin does not handle overwrite. You need to delete the output products already created (maps, text file, figures) by hand before running it again.		# r.basin does not handle overwrite. You need to delete the output products already created (maps, text file, figures) by hand before running it again.

	== r.basin for GRASS 7 ==		== r.basin for GRASS 6.4 ==

	r.basin has ~~a slightly different~~ usage in ~~GRASS 7.~~		r.basin was initially designed to run in grass 6.4, but in G7, r.basin has been improved and bugs were fixed, so it is strongly advised to upgrade to G7. The usage in G6 is:

	<pre>		<pre>
	r.basin [-ac] map=name prefix=prefix ~~coordinates~~=east,north ~~dir=name~~ [threshold=threshold]		r.basin [-ac] map=name prefix=prefix easting=east northing=north [threshold=threshold]
	</pre>		</pre>

	~~It takes in input the coordinates as a pair, separated by a comma. Furthermore, a directory should be indicated, in which~~
	~~the output will be found (the graphics as png and the csv file).~~

	In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.

	~~The vector map whose name ends with <em>outlet_snap</em> has a table associated, in which all the parameters are stored.~~

	== See also ==		== See also ==

⚠️Madi: /* Morphometric parameters */

2017-08-10T09:51:31Z

Morphometric parameters

Show changes

⚠️Madi: /* Usage */

2017-08-10T09:45:37Z

Usage

← Older revision		Revision as of 09:45, 10 August 2017
Line 126:		Line 126:

	<pre>		<pre>
	r.basin map=elevation@PERMANENT prefix=out ~~easting~~=636654.791181 ~~northing=~~218824.126649 threshold=20		r.basin map=elevation@PERMANENT prefix=out coordinates=636654.791181,218824.126649 threshold=20 dir=tmp/my_basin
	</pre>		</pre>

⚠️Madi at 09:03, 10 August 2017

2017-08-10T09:03:20Z

← Older revision		Revision as of 09:03, 10 August 2017
Line 397:		Line 397:
	In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.		In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.

	~~<!--~~ The <em>outlet_snap</em> ~~vector map~~ has a table associated~~, called <em>summary</em>~~, in which all the ~~calculated~~ parameters are stored. ~~-->~~		The vector map whose name ends with <em>outlet_snap</em> has a table associated, in which all the parameters are stored.

	== See also ==		== See also ==

⚠️Madi at 08:20, 10 August 2017

2017-08-10T08:20:50Z

← Older revision		Revision as of 08:20, 10 August 2017
Line 397:		Line 397:
	In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.		In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.

	The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored.		<!-- The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored. -->

	== See also ==		== See also ==

⚠️Madi: /* Known issues */

2016-10-18T16:31:41Z

Known issues

← Older revision		Revision as of 16:31, 18 October 2016
Line 380:		Line 380:
	== Known issues ==		== Known issues ==

	r.basin hasn't been designed for working in lat/long coordinates. This means that if you are working in lat/long coordinates, you need to reproject your map first in order to apply the tool. <br />		# r.basin hasn't been designed for working in lat/long coordinates. This means that if you are working in lat/long coordinates, you need to reproject your map first in order to apply the tool. <br />
	~~Furthermore,~~ r.basin is designed to work in meters unit. The values that you get using feet are nonsense.		# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. <br />
			# r.basin does not handle overwrite. You need to delete the output products already created (maps, text file, figures) by hand before running it again.

	== r.basin for GRASS 7 ==		== r.basin for GRASS 7 ==

⚠️Madi at 14:39, 3 June 2014

2014-06-03T14:39:12Z

← Older revision		Revision as of 14:39, 3 June 2014
Line 3:		Line 3:
	The module {{AddonCmd\|r.basin}} has been designed to perform the delineation and the morphometric characterization of a given basin, on the basis of an elevation raster map and the coordinates of the outlet.		The module {{AddonCmd\|r.basin}} has been designed to perform the delineation and the morphometric characterization of a given basin, on the basis of an elevation raster map and the coordinates of the outlet.
	Please note that it is designed to work only in projected coordinates.		Please note that it is designed to work only in projected coordinates.
	Here a tutorial based on NC sample dataset is presented. ~~Please note that the~~ tutorial refers to GRASS 6. In GRASS 7, a few improvements have been introduced to r.basin. See the section below for details.		Here a tutorial based on NC sample dataset is presented. The tutorial refers to GRASS 6. In GRASS 7, a few improvements have been introduced to r.basin. See the section below for details.

	== Preparation ==		== Preparation ==

⚠️Madi: /* r.basin for GRASS 7 */

2014-04-21T19:57:55Z

r.basin for GRASS 7

← Older revision		Revision as of 19:57, 21 April 2014
Line 394:		Line 394:
	the output will be found (the graphics as png and the csv file).		the output will be found (the graphics as png and the csv file).

	In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, ~~are produced~~ two outlet vector maps: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.		In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, two outlet vector maps are produced: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.

	The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored.		The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored.

⚠️Madi: /* r.basin for GRASS 7 */

2014-04-21T19:48:36Z

r.basin for GRASS 7

← Older revision		Revision as of 19:48, 21 April 2014
Line 393:		Line 393:
	It takes in input the coordinates as a pair, separated by a comma. Furthermore, a directory should be indicated, in which		It takes in input the coordinates as a pair, separated by a comma. Furthermore, a directory should be indicated, in which
	the output will be found (the graphics as png and the csv file).		the output will be found (the graphics as png and the csv file).
	~~<p>~~
	In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, are produced two outlet vector maps: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.		In G7, r.basin has been improved to take in input coordinates not exactly belonging to the river network (but not too far from it). It basically snaps to the closest point belonging to the network. This feature is experimental and might not produce the expected result. To check if the snapped outlet is acceptable, at the end of the computation, are produced two outlet vector maps: the one with the coordinates inserted by the user and the snapped one. If the user is not happy with this latter, should tweak the coordinates to match with the river network.
	~~<p>~~
	The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored.		The <em>outlet_snap</em> vector map has a table associated, called <em>summary</em>, in which all the calculated parameters are stored.