GRASS-Wiki - User contributions [en]

Large raster data processing

2022-12-07T14:00:51Z

⚠️Madi: Added how to category

__TOC__

'''Introduction'''

While GRASS GIS can handle [[GRASS GIS Performance|pretty large raster maps]], sometimes the user systems are hardware limited.

This page collects a number of workarounds for such cases.

== Workaround: Select a smaller area within a very large dataset before importing in GRASS ==

Suppose that we have all ASTER GDEM world coverage (>22000 files) and we aim to build a mosaic of Europe and import it in GRASS. A nice reference on how to deal with ASTER GDEM is [[ASTER_topography | here]].
The very first step is to select among the >22000 files those covering our area of interest (Europe).
To this aim, we can use use [http://gdal.org/gdaltindex.html gdaltindex] to create an index of all the files:

gdaltindex an_index.shp *.tif

This command will create a polygon shapefile with the footprint of each raster as the polygon shape and the name of the image files represented in the attribute table. After that, we just need to do a spatial select on the shapefile and extract the filenames from the attributes from the selected polygons:

ogr2ogr -f CSV list.csv an_index.shp -spat xmin ymin xmax ymax

will produce a CSV file, from which we can easily copy the list of files in a list.txt.

Here, our area of interest (subset) has the following boundaries:

north: N71: ymax = 72.0001389
south: N34: ymin = 33.9998611
west: W011: xmin = -11.0001389
east: E042: xmax = 43.0001389

At 100m this corresponds to 27.8 billion cells.

== Raster map precision types ==

* '''CELL DATA TYPE''': a raster map from INTEGER type (4 bytes, whole numbers only)
** in GRASS GIS, CELL is a 32 bit integer with a range from -2,147,483,647 to +2,147,483,647. The value -2,147,483,648 is reserved for NODATA.
* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 7-9 digits precision)
* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15-17 digits precision)
* '''NULL''': represents "no data" in raster maps, to be distinguished from 0 (zero) data value

Aliases:
* '''INTEGER MAP''': see CELL DATA TYPE
* '''FLOAT MAP''': see FCELL DATA TYPE
* '''DOUBLE MAP''': see DCELL DATA TYPE

(reference in the [https://github.com/OSGeo/grass/blob/master/include/gis.h#L588 GRASS GIS source code])

See also [[GRASS raster semantics]]

== Create a mosaic ==

Now that we have a list of the files interesting our area, and since our files are all in the same datum (WGS84), we can use [http://www.gdal.org/gdalbuildvrt.html gdalbuildvrt] to create a
[http://www.gdal.org/gdal_vrttut.html virtual] mosaic. This will take only a few seconds to run.

gdalbuildvrt -input_file_list list.csv mosaic.vrt

Also note that gdal can read Tifs within a zip/gz-file as well.

To import the mosaic into GRASS, we first need to create a WGS84 location, then:

r.external input=/path/to/mosaic.vrt output=mosaic

GRASS GIS 7.8+ can internally generate VRT-style mosaics with {{cmd|r.buildvrt}}

== Split large maps into tiles ==

Sometimes it is possible to work with tiles, i.e. splitting a big map into chunks. These tiles can be easily generated with {{cmd|r.tile}}. It optionally allows for tiling with overlap.

== Raster map precision: reducing file size ==

Not always double precision is needed for raster map computations. Strategies:
* consider to run with FCELL rather than DCELL precision (see {{cmd|r.mapcalc}}'s float() function).
* you may also multiply with e.g. 100 and then round() to integer (used e.g. for BIOCLIM and WORLDCLIM).

Functions in {{cmd|r.mapcalc}} related to precision:
<pre>
double(x) convert x to double-precision floating point (DCELL)
float(x) convert x to single-precision floating point (FCELL)
round(x) round x to nearest integer (INT)
round(x,y) round x to nearest multiple of y (INT)
round(x,y,z) round x to nearest y*i+z for some integer i (INT)
</pre>

See also [[GRASS raster semantics]]

== Troubleshooting ==

=== Number of open files limitation ===

When working with time series or multispectral data, you may experience the following error message (r.series, r.patch etc.):

Too many open files

or

WARNING: Unable to open raster map <somemap@mapset>
ERROR: One or more input raster maps not found

Many operating systems have the limitation of opening 1024 files at the same time. The limits are just to prevent a process from (accidentally or deliberately) consuming too much memory. The descriptor table is in kernel memory, and can't be swapped to disk. However, this can be enlarged. Note that, in GRASS GIS 7.0, each raster map requires two open files: one for the ''cell''/''fcell'' file, one for the ''null'' bitmap.

Resource limits are per-process, and inherited. The ''ulimit'' command (which is a shell built-in) changes the limits for the current shell process; the new limit will be inherited by any child processes.

==== Solution for Linux: System-wise change ====

On most Linux systems, resource limits are set on login by the ''pam_limits'' module according to the settings contained in /etc/security/limits.conf /etc/security/limits.d/*.conf. You should be able to edit those files if you have root privilege (also via sudo), but you will need to log in again as a user before any changes take effect. A reboot shouldn't be necessary since changes to limits.conf should take effect for any subsequent logins. A hard limit can't be increased for any existing non-root processes, or those descended from them.

Increasing a hard limit requires root privilege (or at least the CAP_SYS_RESOURCE capability), so the limits have to be set by the
program which manages the login (login, xdm, sshd, etc) after the user has identified themself (so it knows which limits to set) but before the process changes its ownership from root to the logged-in user.

sudo su
vim /etc/security/limits.conf

Add in /etc/security/limits.conf something like this:
# Limit user nofile - max number of open files
* soft nofile 1500
* hard nofile 1800

On Ubuntu machines, it may be necessary to edit your /etc/pam.d/common-session file and add the following line:

session required pam_limits.so

Restart the user session (i.e., logout, login).

==== Solution for Windows: System-wise change ====

From the Microsoft documentation it is not very clear how many files can be opened simulaneously (FIX IF POSSIBLE), here some hints:

* https://support.microsoft.com/en-us/kb/87690
* ...

==== Solution for Linux: Session only change ====
To change the limits for an existing session, you may be able to use something like:

sudo bash
ulimit ...
su -c bash <username>

However, sudo will probably reset certain environment variables, particularly LD_LIBRARY_PATH, so you may need to reset those in the new shell.

=== ERROR: G_malloc: unable to allocate xxxx bytes of memory ===

Be sure to use GRASS GIS 7 which has way better support for large files.

If you happen to use the "memory" option requesting more than 2GB (e.g. <tt>memory=3000</tt>) check if you are using 64bit executables since 32bit applications can use only up to 2GB memory. In this case it does not matter if the operating system is 64bit or if there is more than 2GB of memory available. You need to use 64bit binaries of GRASS GIS 7.

== Large File Support (LFS) ==

Affects 32bit systems which are normally limited to 2GB (2^31) per file. As workaround, LFS can be enabled in GRASS GIS at compile time.

* GRASS GIS 6: much of the raster library and modules can be enabled for LFS during compilation
* GRASS GIS 7: raster and vector libraries are LFS enabled.

See also: [[Large File Support]]

== See also ==

* [[GRASS GIS Performance]]
* [[Large vector data processing]]

[[Category:Tutorial]]
[[Category: massive data analysis]]
[[Category: raster]]
[[Category: How To]]

Compile and Install Ubuntu

2019-06-20T08:51:24Z

⚠️Madi: /* Quick instructions */

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
'''Attention''' '''The following instructions describe the compilation and installation of GRASS 6.x or even 7.x and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''
</div>

== Very Important notes ==

* '''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''
** Daily ready to installl GRASS GIS builds of the 7.x release branch and trunk are available from ''ppa:grass/grass-devel''
**: <source lang=bash>sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable</source>
**: <source lang=bash>sudo add-apt-repository ppa:grass/grass-devel</source>
** Latest version of GRASS 7.x is available from ''ppa:grass/grass-stable''
**: <source lang=bash>sudo add-apt-repository ppa:ubuntugis/ppa</source>
**: <source lang=bash>sudo add-apt-repository ppa:grass/grass-stable</source>
*: <source lang=bash>sudo apt-get update</source>
*: <source lang=bash>sudo apt-get install grass70</source>

== Quick instructions ==

These instructions should work fine on recent Ubuntu distributions:

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools
<source lang="bash">
# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# install PROJ
sudo apt-get install libproj-dev proj-data proj-bin -y

# install GEOS
sudo apt-get install libgeos-dev -y

# install GDAL
sudo apt-get install libgdal-dev python-gdal gdal-bin -y

# install PDAL (optional)
sudo apt-get install libpdal-dev pdal libpdal-plugin-python -y

# install compiler stuff and further dependencies
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.0 \
python-dateutil libgsl-dev python-numpy \
wx3.0-headers wx-common libwxgtk3.0-dev \
libwxbase3.0-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev liblas-c-dev \
subversion libzstd-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget
</source>

This are optional video codec libraries for NVIZ video output:
<source lang="bash">
sudo apt-get install \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev
</source>
Now we have all "ingredients" readily installed on our system.

Time to get the GRASS GIS source code: To minimize download efforts, we start with the weekly snapshot and then update it from SVN, the source code management repository:
<source lang="bash">
# download latest GRASS GIS 7 stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass76/source/snapshot/grass-7.6.svn_src_snapshot_latest.tar.gz

# unpack source code package and remove tarball archive:
tar xvfz grass-7.6.svn_src_snapshot_latest.tar.gz
rm -f grass-7.6.svn_src_snapshot_latest.tar.gz

# rename source code directory
mv grass-7.6.svn_src_snapshot_20??_??_?? grass-7.6.svn

# update snapshot once more to grab latest updates and fixes:
cd grass-7.6.svn/
svn update
</source>

Now we can compile the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -march=native -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-liblas \
--with-pdal \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-motif \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp \
--without-ffmpeg
</source>

Now compile source code (takes some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

Install resulting GRASS GIS 7 binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass76
</source>

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''SVN'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...): 

The following dependencies concern [http://releases.ubuntu.com/xenial/ Ubuntu Xenial Xerus (16.04 LTS)]

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.0 \
python-dateutil libgsl-dev python-numpy \
wx3.0-headers wx-common libwxgtk3.0-dev \
libwxbase3.0-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev liblas-c-dev \
resolvconf \
libjasper-dev \
subversion \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern [http://releases.ubuntu.com/trusty/ Ubuntu Trusty Tahr (14.04 LTS)]

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ \
python python-dev \
python-dateutil libgsl0-dev python-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev liblas-c-dev \
resolvconf \
subversion \
checkinstall \
cmake ccache \
python-opengl \
python-wxversion python-wxtools python-wxgtk2.8 \
wx2.8-headers wx-common libwxgtk2.8-dev libwxgtk2.8-dbg \
libwxbase2.8-dev libwxbase2.8-dbg \
libncurses5-dev \
libcairo2 libcairo2-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libjasper-dev \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [http://grass.osgeo.org/grass70/source/REQUIREMENTS.html required], namely PROJ.4, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ.4, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libatlas-dev libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

=== Earlier Ubuntu versions ===

For [http://old-releases.ubuntu.com/releases/ earlier Ubuntu versions], '''watch out for dependency differences!''' Modify the dependency list given above as instructed below.

* for [http://releases.ubuntu.com/raring/ Ubuntu Raring Ringtail (13.04]), change the following dependencies:
** <source lang="bash" enclose="none">libav-tools libavutil-dev --> ffmpeg</source>
** <source lang="bash" enclose="none"> --> lesstif2-dev</source>

* for [http://releases.ubuntu.com/precise/ Ubuntu Precise Pangolin (12.04)], change the following dependencies:
** <source lang="bash" enclose="none">libpnglite-dev --> libpngwriter-dev</source>
** <source lang="bash" enclose="none">libtiff5-dev --> libtiff4-dev</source>

* for [http://old-releases.ubuntu.com/releases/maverick/ Ubuntu Maverick Meerkat (10.10)] or later, change the following dependencies:
** <source lang="bash" enclose="none">libpngwriter-dev --> libpngwriter0-dev</source>
** <source lang="bash" enclose="none">libcairo-dev --> libcairo2-dev</source>
** <source lang="bash" enclose="none">fftw3 --> libfftw3-3</source>
** <source lang="bash" enclose="none">fftw3-dev --> libfftw3-dev</source>

* for [http://old-releases.ubuntu.com/releases/lucid/ Ubuntu Lucid Lynx (10.04)] or later, also install: <source lang="bash">sudo apt-get install libhdf4-alt-dev libhdf4-0-alt</source>

* for [http://old-releases.ubuntu.com/releases/ earlier Ubuntu versions], also install: <source lang="bash"> sudo apt-get install libhdf4g-dev libhdf4g-run</source>

== Using pre-compiled dev Packages for PROJ.4, GEOS and GDAL ==

=== PROJ.4 ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ.4, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS 7 from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ4 ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its Subversion repository: <source lang="bash">
svn co http://svn.osgeo.org/metacrs/proj/branches/4.8/proj/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.5.zip '''proj-datumgrid-1.5.zip'''] from [http://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.5.zip
mv proj-datumgrid-1.5.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.5.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.4.2.tar.bz2''' from [http://trac.osgeo.org/geos/ http://trac.osgeo.org/geos] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget http://download.osgeo.org/geos/geos-3.4.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.4.2.tar.bz2
tar xvf geos-3.4.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.4.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support

* download the current stable version <source lang="bash">
svn co https://svn.osgeo.org/gdal/branches/1.11/gdal gdal_stable
</source>

* enter in the <source lang="bash" enclose="none">gdal_stable</source> directory <source lang="bash">
cd /usr/local/src/gdal_stable
</source>

* optionally, update the source code <source lang="bash">
svn up
</source>

* if required, clean previous configurations/compilations <source lang="bash">
make distclean
</source>

* a simple configuration without any parameters will detect and support various installed libraries <source lang="bash">
./configure
</source>

* skip to the ''compile and install'' step or check the following customised configuration example
<ul>
<source lang="bash">
CFLAGS="-g -Wall" LDFLAGS="-s" ./configure \
--with-png=internal \
--with-libtiff=internal \
--with-geotiff=internal \
--with-jpeg=internal \
--with-gif=internal \
--with-ecw=no \
--with-expat=yes \
--with-sqlite3=yes \
--with-geos=yes \
--with-python \
--with-libz=internal \
--with-netcdf \
--with-threads=yes \
--without-grass \
--without-ogdi \
--with-pg=/usr/bin/pg_config \
--with-xerces=yes
</source>
</ul>

* compile, install & ldconfig <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>
<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

=== GRASS GIS ===

Note the differences between different GRASS version (SVN branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory. For example, if you have problems related to 32bit versus 64bit, pay attention to section <code>(C)</code>, entitled <code>COMPILATION NOTES for 64bit platforms</code>.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download (using SVN) the source code:

* VERY OLD STABLE VERSION: current state of the 6.4.x release branch version (stable) <source lang="bash">
svn co https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4 grass64_release
</source>

* STABLE VERSION: current state of the 7.2.x release branch version (current stable) <source lang="bash">
svn co https://svn.osgeo.org/grass/grass/branches/releasebranch_7_2 grass72_release
</source>

* DEVELOPMENT VERSION: current state of the trunk (latest version of code where the development happens) <source lang="bash">
svn co https://svn.osgeo.org/grass/grass/trunk grass7_trunk
</source>

* for other versions see [http://trac.osgeo.org/grass/wiki/DownloadSource GRASS Trac wiki].

''' Configure, Compile and Install'''

Enter the directory with the source code (downloaded by svn client), for example:

<source lang="bash">
cd grass72_release
</source>

* '''GRASS GIS 6 example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--enable-largefile=yes \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-readline \
--with-python=yes \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-motif \
--with-tcltk-includes="/usr/include/tcl8.5" \
--with-ffmpeg=yes --with-ffmpeg-includes="/usr/include/libavcodec /usr/include/libavformat /usr/include/libswscale /usr/include/libavutil" \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>Proj4</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. <source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* '''GRASS GIS 7 example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--enable-largefile=yes \
--with-nls \
--with-cxx \
--with-readline \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-liblas=yes --with-liblas-config=/usr/bin/liblas-config
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>Proj4</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
'''Note 2''', if compiling with liblas, you will want liblas compiled with laszip support. liblas will look for laszip includes in /usr/local/include/laszip by default. Creating the laszip directory in /usr/local/include and making a soft link. ln -s /usr/local/include/lasz*.hpp /usr/local/include/laszip and ln -s /usr/local/include/lasunz*.hpp /usr/local/include/laszip should allow liblas to compile with laszip support
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

* get the plugin from [http://download.osgeo.org/gdal OSGeo's Download Server]: [http://download.osgeo.org/gdal/gdal-grass-1.4.3.tar.gz http://download.osgeo.org/gdal/gdal-grass-1.4.3.tar.gz] using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
wget http://download.osgeo.org/gdal/gdal-grass-1.4.3.tar.gz
tar xvzf gdal-grass-1.4.3.tar.gz
cd gdal-grass-1.4.3
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS 6.4 library path
/usr/local/src/grass64_release/lib

# GRASS 6.5 library path
/usr/local/src/grass6_devel/lib

# GRASS 7.0 library path
/usr/local/src/grass64_release/lib

# GRASS 7 (development version) library path
/usr/local/src/grass7_trunk/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass-6.4.4svn/ \
--with-autoload="/usr/local/lib/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
<ul>
* for GRASS 6.5, replace the respective line above, depending on where the source code in question is stored, with something like <source lang="bash" enclose="none"> --with-grass=/usr/local/grass-6.5.svn/</source>
* for GRASS 7.0, replace with <source lang="bash" enclose="none"> --with-grass=/usr/local/grass-7.0.0svn/</source>
* for GRASS 7, replace with <source lang="bash" enclose="none"> --with-grass=/usr/local/grass_trunk/</source>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [http://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [http://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete
* <source lang="bash" enclose="none">/usr/local/grass-6.4.4svn</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass64</source> (file)
* <source lang="bash" enclose="none">/usr/local/bin/gem64</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc6</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass64_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass64 # package name defined at installation is important</source>

= Packaging of GRASS =

* See the {{src|debian/README.debian}} file in the GRASS source code for directions on rolling your own packages.

For details about the auto-nightly-builds and after-market supplied packages from UbuntuGIS, please refer to the [[Ubuntu Packaging]] wiki page.

== See also ==

* GRASS GIS in Ubuntu installation: http://www.spatial-ecology.net/dokuwiki/doku.php?id=wiki:install_linux
* Docker: https://registry.hub.docker.com/u/javimarlop/ubuntugis-docker/dockerfile/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

== Ubuntu 7.10 64-bit ==

* Compiling latest GRASS source code on a 64-bit machine (with an ATI graphic card) under Ubuntu 7.10 64-bit with support for: 64-bit, SQLite, OpenGL, PYTHON, FFMPEG
(Based on "Ubuntu 6.06 LTS - GRASS 6.1 Compilation Script" by David Finlayson)
''Assuming it is the first time attempting to compile GRASS' source code & installing SVN, PROJ, GDAL/OGR''

'''Preparation'''
sudo apt-get update && sudo apt-get upgrade

* install dependencies for compiling (in general) and dependencies for GRASS: PROJ, GDAL/OGR
sudo apt-get install grass build-essential flex bison libncurses5-dev zlib1g-dev \
libgdal1-dev libtiff4-dev libgcc1 libpng12-dev tcl8.4-dev tk8.4-dev fftw3-dev \
libfreetype6-dev libavcodec-dev libxmu-dev gdal-bin libreadline5 libreadline5-dev \
make python-dev python-wxversion

* install SQLite
sudo apt-get install sqlite3 libsqlite3-dev

* install SVN
sudo apt-get install subversion

* create a directory as a simple user where source code(s) are going to be stored (in our example we use a directory called '''src''' under '''/usr/local''')

sudo mkdir /usr/local/src

* grant rwx (read-write-execute) permissions for our userid/ groupid on the directory (replace words userid and groupid with real userid):
sudo chown ''userid'':''groupid'' /usr/local/src

sudo chmod ug+rwx /usr/local/src

* download latest source code from GRASS SVN repository in a directory on the system (e.g. /usr/local/src)
svn checkout https://svn.osgeo.org/grass/grass/trunk grass_trunk

* Above command places GRASS' source code in '''/usr/local/src/grass_trunk'''. In case of a subsequent update use the command: '''svn up''' from within the grass_trunk directory

----
'''Before''' attempting to compile GRASS, READ section (C) in the '''INSTALL''' file located in the main directory of GRASS source code entitled:
'''(C) COMPILATION NOTES for 64bit platforms'''
----

* installing FFTW3 if not already on system
sudo apt-get install fftw3 fftw3-dev

'''FFMPEG'''

Note: Back in Ubuntu 7.10, installing ffmpeg through the repositories wouldn't work with grass. The following steps were successfully used.

* install FFMPEG (information taken from: http://stream0.org/2008/01/install-ffmpeg-on-ubuntu-gutsy.html)
* download source code with svn
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg

* install dependencies
sudo apt-get install liblame-dev libfaad2-dev libfaac-dev libxvidcore4-dev \
liba52-0.7.4 liba52-0.7.4-dev libx264-dev libdts-dev checkinstall \
build-essential subversion

* guide to ffmpeg directory
cd ffmpeg

if necessary: '''make distclean''' before configuration (look at notes below)

* configuration ('''note:''' the configuration parameter "'''--enable-pp'''" does not work anymore)
# configure FFMPEG
./configure --enable-gpl --enable-libvorbis --enable-libtheora \
--enable-liba52 --enable-libdc1394 --enable-libgsm \
--enable-libmp3lame --enable-libfaad --enable-libfaac \
--enable-libxvid --enable-libx264 \
--enable-shared

* compilation
make

* installation on /usr/local/bin -- important to remember when configuring GRASS' source code for compilation
sudo checkinstall

'''Go for GRASS!'''
* in our example we used the /usr/local/src directory to store GRASS' source code, so:
cd /usr/local/src/grass_trunk

* configuration
CFLAGS="-g -Wall" ./configure --enable-64bit \
--with-libs=/usr/lib64 --with-cxx --with-freetype=yes \
--with-postgres=no --with-sqlite=yes --enable-largefile=yes \
--with-tcltk-includes=/usr/include/tcl8.4 \
--with-freetype-includes=/usr/include/freetype2 \
--with-opengl-libs=/usr/include/GL --with-readline \
--with-python=yes --with-ffmpeg=yes \
--with-ffmpeg-includes=/usr/local/include/ffmpeg

*if OpenGL fails then maybe it is necessary to link '''glxATI.h''' with '''glx.h''' and re-run the configuration

cd /usr/include/GL

sudo ln glxATI.h glx.h

* compilation
make

* compilation is expected to end with a statement similar to the following:

Started compilation: Wed Feb 27 00:24:36 CET 2008
--
Errors in:
No errors detected.

* installation
sudo checkinstall

* launch 64-bit GRASS.6.4.svn
grass64

'''Notes'''
* in case of errors in future compilation attempts, remember to remove program binaries with
make clean
* and the files created with the "configuration" from previous compilations with
make distclean

== Ubuntu 6.06, 7.10 ==

* [http://david.p.finlayson.googlepages.com/makegrass.sh makegrass.sh] is script designed to automate most of the download, configuration and compilation of GRASS 6.x-CVS
** it is advised use [https://help.ubuntu.com/community/CheckInstall checkinstall] (''sudo apt-get install checkinstall'') instead of ''make install'' to keep track of installed software
** Think twice before using this script. Some users experienced problems such as disabled XGL etc.
* [[User:Steko/Automated_CVS_compiling|Here]] is another of these scripts, it's homemade so probably you'll find the above more useful for production sites.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

GRASS Metadata Management

2018-01-11T14:03:47Z

⚠️Madi: /* INSPIRE Metadata structure */

== Metadata support ==

See [[ISO/INSPIRE Metadata Support]] and related [http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS GSoC project] (g.gui.metadata)

=== Raster ===
* {{cmd|r.support}} (r.support history="long text" now functional, it does line wrapping)
* [[Replacement raster format#Meta-data support|Metadata support in GRASS raster library notes]]

=== Vector ===
* [http://download.osgeo.org/grass/grass6_progman/Vector_Library.html#head_file_format 'head' file format]
* TODO: tool to edit this head file needed using {{cmd|v.support}}. (Reference: http://lists.osgeo.org/pipermail/grass-user/2007-February/038378.html)

Comments on a vector map can be added manually by editing <code>$MAPSET/vector/$MAPNAME/hist</code>.

== Metadata management ideas for future versions of GRASS ==

=== Unified XML-based approach for raster/vector/imagery ===

* store relevant metadata in an XML-based format, along with creation/modification history
* a new directory '$maspset/metadata/' could house this information
* would probably require major re-write of the raster/vector history mechanism
* generic reading/writing of XML data (don't we already have this functionality somewhere...)

=== Creating an INSPIRE compliant version of {v,r}.support ===

One idea would be to develop an INSPIRE compliant version of {v,r}.support. The module would ensure that all fields required for INSPIRE would be completed. It should be possible to write the Metadata out as XML (see above section). The European Union Open Source Metadata Editor (EUOSME) is a Web-based INSPIRE module that is published under the European Union Public Licence [1,2].

[1] [http://inspire-forum.jrc.ec.europa.eu/pg/pages/view/34267/ EUOSME]

[2] [http://www.eurogeoss.eu/Documents/EuroGEOSS_D_2_2_3.pdf Required Fields]

=== Validation ===

The GRASS module could call the [http://inspire-geoportal.ec.europa.eu/validator2/ validator]'s API and return the check result.

== INSPIRE Metadata structure ==

In order to be INSPIRE compliant, a metadata for spatial data sets or spatial data set series should include at least the information provided in the table reported in the [http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32008R1205&from=EN INSPIRE metadata regulation] (those are intended as required fields; the user should be able to add more fields).

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|''' Reference '''
!width=100px|''' Metadata elements '''
!width=50px|''' Multiplicity '''
!''' Condition '''
!''' Notes '''
|-
|1.1
|Resource title
|1
|
| title
|
|-
|1.2
|Resource abstract
|1
|
| (+ optional: abstract_URL)
|-
|1.3
|Resource type
|1
|
| Spatial data set series (series) | Spatial data set (dataset) | Spatial data services (services)
|-
|1.4
|Resource locator
|0..*
|Mandatory if a URL is available to obtain more information on the resource, and/or access related services
|
|-
|1.5
|Unique resource identifier
|1..*
|
|
|-
|1.7
|Resource language
|0..*
|Mandatory if the resource include textual information
|
|-
|2.1
|Topic category
|1..*
|
| Topic categories in accordance with ISO 19115
|-
|3
|Keyword
|1..*
|
|
|-
|4.1
|Geographic bounding box
|1..*
|
|
|-
|5
|Temporal reference
|1..*
|
|
|-
|6.1
|Lineage
|1
|
|
|-
|6.2
|Spatial resolution
|0..*
|Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified
|
|-
|7
|Conformity
|1..*
|
|
|-
|8.1
|Conditions for access and use
|1..*
|
|
|-
|8.2
|Limitations on public access
|1..*
|
|
|-
|9
|Responsible organisation
|1..*
|
|
|-
|10.1
|Metadata point of contact
|1..*
|
|
|-
|10.2
|Metadata date
|1
|
|
|-
|10.3
|Metadata language
|1
|
|
|-
|}

== Links ==
* [http://www.eurogeographics.org/eng/documents/draftINSPIREMetadataIRv2_20070202.pdf DT Metadata – Draft Implementing Rules for Metadata]
* http://wiki.osgeo.org/wiki/Metadata and http://wiki.osgeo.org/wiki/Metadata_software (software list)
* http://www.gsdi.org/gsdicookbookindex.php
* http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/metadata/MD_IR_and_ISO_20090218.pdf
* https://www.ngdc.noaa.gov/wiki/index.php?title=ISO_Metadata_Standard
* [http://inspire-geoportal.ec.europa.eu/validator2/ INSPIRE Geoportal's metadata validator]

[[Category:Development]]
[[Category:Metadata]]
[[Category:INSPIRE]]

GRASS GIS Jupyter notebooks

2017-10-24T10:14:43Z

⚠️Madi: /* How to run GRASS GIS from Jupyter notebook */

A Jupyter Notebook is a web application that allows you to create and share documents that contain scripts and code, equations, visualizations and explanatory text, combined.

You can even change the code and explore your modified script(s).

== How to run GRASS GIS from Jupyter notebook ==

Running GRASS from Jupyter notebook requires that Jupyter notebook is installed on your system, and that you set up the [https://grass.osgeo.org/grass72/manuals/variables.html environment variables] for using GRASS. For example you can create a script called grass_jupyter.sh that contains the following lines:

<source lang="bash">

# directory where GRASS lives
export GISBASE=/usr/local/grass-7.3.svn # Change this path to reflect your own

# generate GISRC
# Defines the system wide value while in a GRASS session
MYGISDBASE=$HOME/grassdata # Change this path to reflect your own
MYLOC=MyLoc # Change this location name to reflect your own
MYMAPSET=PERMANENT

# Set the global grassrc file to individual file name
MYGISRC="$HOME/.grassrc.$$"

echo "GISDBASE: $MYGISDBASE" > "$MYGISRC"
echo "LOCATION_NAME: $MYLOC" >> "$MYGISRC"
echo "MAPSET: $MYMAPSET" >> "$MYGISRC"
echo "GRASS_GUI: text" >> "$MYGISRC"

# path to GRASS settings file
export GISRC=$MYGISRC

export LD_LIBRARY_PATH=$GISBASE/lib:$LD_LIBRARY_PATH
export PYTHONPATH=$GISBASE/etc/python:$PYTHONPATH
export PATH=$GISBASE/bin:$GISBASE/scripts:$PATH

# start the notebook in the notebook folder
cd $HOME/notebooks # change this path to reflect your own path to notebooks folder

nohup jupyter notebook --ip=0.0.0.0 --port=8888 --debug &

</source>

Add this line to your $HOME/.bashrc file:

<source lang="bash">
alias grass_notebook='sh grass_jupyter.sh'
</source>

From terminal, in your home directory:
<source lang="bash">
source .bashrc
</source>

Now you can start your notebook typing in the terminal:
<source lang="bash">
grass_notebook
</source>

=== List of selected GRASS GIS Jupyter notebooks ===

(please expand!)

* OSGeoLive-Notebooks: [https://github.com/OSGeo/OSGeoLive-Notebooks/tree/master/GSoC-2015/Introduction%20to%20GRASS%20GIS Introduction to GRASS GIS]
* [https://github.com/zarch/workshop-pygrass Workshop on pygrass using IPython notebook]
* [https://github.com/tgrippa/Opensource_OBIA_processing_chain An open-source semi-automated processing chain for urban OBIA classification]
* [https://github.com/wenzeslaus/python-grass-addon How to write a Python GRASS GIS 7 addon]
* [https://github.com/lucadelu/docker-stacks/tree/geospatial/geospatial-notebook docker-stacks/geospatial-notebook]
* [https://github.com/wenzeslaus/geospatial-modeling-course-jupyter/tree/master/notebooks 14 Jupyter Notebooks for learning geospatial analysis and modeling with GRASS GIS]

==== See also ====

* [https://github.com/wenzeslaus/gdoc2py GRASS GIS focused converter from HTML with pre code tags to Jupyter Notebook]

[[Category: Documentation]]
[[Category: Python]]
[[Category: Tutorial]]

GRASS GIS Jupyter notebooks

2017-10-24T09:33:48Z

⚠️Madi: added instructions how to run grass from jupyter

A Jupyter Notebook is a web application that allows you to create and share documents that contain scripts and code, equations, visualizations and explanatory text, combined.

You can even change the code and explore your modified script(s).

== How to run GRASS GIS from Jupyter notebook ==

Running GRASS from Jupyter notebook requires that Jupyter notebook is installed on your system, and that you set up the [https://grass.osgeo.org/grass72/manuals/variables.html environment variables] for using GRASS. For example you can create a script called grass_jupyter.sh that contains the following lines:

<source lang="bash">

# directory where GRASS lives
export GISBASE=/usr/local/grass-7.3.svn # Change this path to reflect your own

# generate GISRC
# Defines the system wide value while in a GRASS session
MYGISDBASE=$HOME/grassdata # Change this path to reflect your own
MYLOC=MyLoc # Change this location name to reflect your own
MYMAPSET=PERMANENT

# Set the global grassrc file to individual file name
MYGISRC="$HOME/.grassrc.$$"

echo "GISDBASE: $MYGISDBASE" > "$MYGISRC"
echo "LOCATION_NAME: $MYLOC" >> "$MYGISRC"
echo "MAPSET: $MYMAPSET" >> "$MYGISRC"
echo "GRASS_GUI: text" >> "$MYGISRC"

# path to GRASS settings file
export GISRC=$MYGISRC

export LD_LIBRARY_PATH=$GISBASE/lib:$LD_LIBRARY_PATH
export PYTHONPATH=$GISBASE/etc/python:$PYTHONPATH
export PATH=$GISBASE/bin:$GISBASE/scripts:$PATH

# start the notebook in the notebook folder
cd $HOME/notebooks # change this path to reflect your own path to notebooks folder

nohup jupyter notebook --ip=0.0.0.0 --port=8888 --debug &

</source>

Add this line in your .bashrc file

<source lang="bash">
alias grass_notebook='sh grass_jupyter.sh'
</source>

From terminal, in your home directory:
<source lang="bash">
source .bashrc
</source>

Now you can start your notebook typing in the terminal:
<source lang="bash">
grass_notebook
</source>

=== List of selected GRASS GIS Jupyter notebooks ===

(please expand!)

* OSGeoLive-Notebooks: [https://github.com/OSGeo/OSGeoLive-Notebooks/tree/master/GSoC-2015/Introduction%20to%20GRASS%20GIS Introduction to GRASS GIS]
* [https://github.com/zarch/workshop-pygrass Workshop on pygrass using IPython notebook]
* [https://github.com/tgrippa/Opensource_OBIA_processing_chain An open-source semi-automated processing chain for urban OBIA classification]
* [https://github.com/wenzeslaus/python-grass-addon How to write a Python GRASS GIS 7 addon]
* [https://github.com/lucadelu/docker-stacks/tree/geospatial/geospatial-notebook docker-stacks/geospatial-notebook]
* [https://github.com/wenzeslaus/geospatial-modeling-course-jupyter/tree/master/notebooks 14 Jupyter Notebooks for learning geospatial analysis and modeling with GRASS GIS]

==== See also ====

* [https://github.com/wenzeslaus/gdoc2py GRASS GIS focused converter from HTML with pre code tags to Jupyter Notebook]

[[Category: Documentation]]
[[Category: Python]]
[[Category: Tutorial]]

R.basin

2017-08-10T10:02:57Z

⚠️Madi: /* Maps */

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

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

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632880 , 222890
Rectangle containing basin S-E : 637010 , 218720
Area of basin [km^2] : 7.8592625
Perimeter of basin [km] : 17.7583322395
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.7042
Mean Slope : 3.50
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.61379074702
Circularity Ratio : 0.313175157621
Topological Diameter : 105.0
Elongation Ratio : 0.469323448397
Shape Factor : 1.16602561484
Concentration Time (Giandotti, 1934) [hr] : 3.53310944404
Length of Mainchannel [km] : 6.74021428
Mean slope of mainchannel [percent] : 1.202028
Mean hillslope length [m] : 5932.153
Magnitudo : 415.0
Max order (Strahler) : 5
Number of streams : 612
Total Stream Length [km] : 80.8272
First order stream frequency : 52.8039367562
Drainage Density [km/km^2] : 10.2843237518
Bifurcation Ratio (Horton) : 5.0940
Length Ratio (Horton) : 2.1837
Area ratio (Horton) : 5.6571
Slope ratio (Horton): 1.4418
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78593.0
===========================
Hypsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78593.0
Tot. area 7859300.0
Max distance 6769.341392
===========================
Width Function | quantiles
===========================
801 | 0.05
1507 | 0.15
2166 | 0.3
2572 | 0.4
2958 | 0.5
3629 | 0.6
4184 | 0.7
5132 | 0.85
6089 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 612 | 80.8272 | 7.8593 | 10.2843 | 77.8695

Stream ratios based on regression coefficient:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.0940 | 2.1837 | 5.6571 | 1.4418 | 1.5420

Averaged stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.5417 | 2.6271 | 5.1916 | 1.4625 | 1.6693
3.5678 | 1.9342 | 4.3638 | 0.1448 | 0.6477

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0880 | 0.0100 | 0.0428 | 0.0331 | 3.1995
2 | 0.2025 | 0.0501 | 0.0303 | 0.0250 | 5.3206
3 | 0.5337 | 0.2538 | 0.0212 | 0.0177 | 8.5684
4 | 2.7421 | 2.7104 | 0.0159 | 0.0136 | 25.1265
5 | 1.1871 | 7.8593 | 0.0095 | 0.0051 | 6.1054

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0771 | 0.0082 | 0.0362 | 0.0275 | 3.5790
2 | 0.1841 | 0.0398 | 0.0185 | 0.0145 | 5.6062
3 | 0.6182 | 0.2493 | 0.0131 | 0.0120 | 8.5329
4 | 2.8546 | 3.1286 | 0.0062 | 0.0085 | 15.5228
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 490 | 43.1013 | 4.8895
2 | 98 | 19.8470 | 4.9085
3 | 21 | 11.2077 | 5.3290
4 | 2 | 5.4841 | 5.4207
5 | 1 | 1.1871 | 7.8593

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.0000 | 2.3024 | 0.0000 | 1.4154 | 1.3236 | 8.8151 | 100.2147
2 | 4.6667 | 2.6353 | 5.0194 | 1.4279 | 1.4086 | 4.0434 | 19.9654
3 | 10.5000 | 5.1378 | 5.0664 | 1.3358 | 1.3065 | 2.1031 | 3.9407
4 | 2.0000 | 0.4329 | 10.6807 | 1.6710 | 2.6385 | 1.0117 | 0.3690
5 | 0.0000 | 0.0000 | 2.8997 | 0.0000 | 0.0000 | 0.1510 | 0.1272

</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
out_elevation_outlet_snap
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</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 are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 6.4 ==

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>
r.basin [-ac] map=name prefix=prefix easting=east northing=north [threshold=threshold]
</pre>

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

R.basin

2017-08-10T09:56:23Z

⚠️Madi:

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

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

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632880 , 222890
Rectangle containing basin S-E : 637010 , 218720
Area of basin [km^2] : 7.8592625
Perimeter of basin [km] : 17.7583322395
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.7042
Mean Slope : 3.50
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.61379074702
Circularity Ratio : 0.313175157621
Topological Diameter : 105.0
Elongation Ratio : 0.469323448397
Shape Factor : 1.16602561484
Concentration Time (Giandotti, 1934) [hr] : 3.53310944404
Length of Mainchannel [km] : 6.74021428
Mean slope of mainchannel [percent] : 1.202028
Mean hillslope length [m] : 5932.153
Magnitudo : 415.0
Max order (Strahler) : 5
Number of streams : 612
Total Stream Length [km] : 80.8272
First order stream frequency : 52.8039367562
Drainage Density [km/km^2] : 10.2843237518
Bifurcation Ratio (Horton) : 5.0940
Length Ratio (Horton) : 2.1837
Area ratio (Horton) : 5.6571
Slope ratio (Horton): 1.4418
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78593.0
===========================
Hypsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78593.0
Tot. area 7859300.0
Max distance 6769.341392
===========================
Width Function | quantiles
===========================
801 | 0.05
1507 | 0.15
2166 | 0.3
2572 | 0.4
2958 | 0.5
3629 | 0.6
4184 | 0.7
5132 | 0.85
6089 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 612 | 80.8272 | 7.8593 | 10.2843 | 77.8695

Stream ratios based on regression coefficient:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.0940 | 2.1837 | 5.6571 | 1.4418 | 1.5420

Averaged stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.5417 | 2.6271 | 5.1916 | 1.4625 | 1.6693
3.5678 | 1.9342 | 4.3638 | 0.1448 | 0.6477

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0880 | 0.0100 | 0.0428 | 0.0331 | 3.1995
2 | 0.2025 | 0.0501 | 0.0303 | 0.0250 | 5.3206
3 | 0.5337 | 0.2538 | 0.0212 | 0.0177 | 8.5684
4 | 2.7421 | 2.7104 | 0.0159 | 0.0136 | 25.1265
5 | 1.1871 | 7.8593 | 0.0095 | 0.0051 | 6.1054

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0771 | 0.0082 | 0.0362 | 0.0275 | 3.5790
2 | 0.1841 | 0.0398 | 0.0185 | 0.0145 | 5.6062
3 | 0.6182 | 0.2493 | 0.0131 | 0.0120 | 8.5329
4 | 2.8546 | 3.1286 | 0.0062 | 0.0085 | 15.5228
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 490 | 43.1013 | 4.8895
2 | 98 | 19.8470 | 4.9085
3 | 21 | 11.2077 | 5.3290
4 | 2 | 5.4841 | 5.4207
5 | 1 | 1.1871 | 7.8593

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.0000 | 2.3024 | 0.0000 | 1.4154 | 1.3236 | 8.8151 | 100.2147
2 | 4.6667 | 2.6353 | 5.0194 | 1.4279 | 1.4086 | 4.0434 | 19.9654
3 | 10.5000 | 5.1378 | 5.0664 | 1.3358 | 1.3065 | 2.1031 | 3.9407
4 | 2.0000 | 0.4329 | 10.6807 | 1.6710 | 2.6385 | 1.0117 | 0.3690
5 | 0.0000 | 0.0000 | 2.8997 | 0.0000 | 0.0000 | 0.1510 | 0.1272

</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 6.4 ==

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>
r.basin [-ac] map=name prefix=prefix easting=east northing=north [threshold=threshold]
</pre>

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

R.basin

2017-08-10T09:51:31Z

⚠️Madi: /* Morphometric parameters */

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

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

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632880 , 222890
Rectangle containing basin S-E : 637010 , 218720
Area of basin [km^2] : 7.8592625
Perimeter of basin [km] : 17.7583322395
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.7042
Mean Slope : 3.50
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.61379074702
Circularity Ratio : 0.313175157621
Topological Diameter : 105.0
Elongation Ratio : 0.469323448397
Shape Factor : 1.16602561484
Concentration Time (Giandotti, 1934) [hr] : 3.53310944404
Length of Mainchannel [km] : 6.74021428
Mean slope of mainchannel [percent] : 1.202028
Mean hillslope length [m] : 5932.153
Magnitudo : 415.0
Max order (Strahler) : 5
Number of streams : 612
Total Stream Length [km] : 80.8272
First order stream frequency : 52.8039367562
Drainage Density [km/km^2] : 10.2843237518
Bifurcation Ratio (Horton) : 5.0940
Length Ratio (Horton) : 2.1837
Area ratio (Horton) : 5.6571
Slope ratio (Horton): 1.4418
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78593.0
===========================
Hypsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78593.0
Tot. area 7859300.0
Max distance 6769.341392
===========================
Width Function | quantiles
===========================
801 | 0.05
1507 | 0.15
2166 | 0.3
2572 | 0.4
2958 | 0.5
3629 | 0.6
4184 | 0.7
5132 | 0.85
6089 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 612 | 80.8272 | 7.8593 | 10.2843 | 77.8695

Stream ratios based on regression coefficient:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.0940 | 2.1837 | 5.6571 | 1.4418 | 1.5420

Averaged stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.5417 | 2.6271 | 5.1916 | 1.4625 | 1.6693
3.5678 | 1.9342 | 4.3638 | 0.1448 | 0.6477

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0880 | 0.0100 | 0.0428 | 0.0331 | 3.1995
2 | 0.2025 | 0.0501 | 0.0303 | 0.0250 | 5.3206
3 | 0.5337 | 0.2538 | 0.0212 | 0.0177 | 8.5684
4 | 2.7421 | 2.7104 | 0.0159 | 0.0136 | 25.1265
5 | 1.1871 | 7.8593 | 0.0095 | 0.0051 | 6.1054

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0771 | 0.0082 | 0.0362 | 0.0275 | 3.5790
2 | 0.1841 | 0.0398 | 0.0185 | 0.0145 | 5.6062
3 | 0.6182 | 0.2493 | 0.0131 | 0.0120 | 8.5329
4 | 2.8546 | 3.1286 | 0.0062 | 0.0085 | 15.5228
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 490 | 43.1013 | 4.8895
2 | 98 | 19.8470 | 4.9085
3 | 21 | 11.2077 | 5.3290
4 | 2 | 5.4841 | 5.4207
5 | 1 | 1.1871 | 7.8593

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.0000 | 2.3024 | 0.0000 | 1.4154 | 1.3236 | 8.8151 | 100.2147
2 | 4.6667 | 2.6353 | 5.0194 | 1.4279 | 1.4086 | 4.0434 | 19.9654
3 | 10.5000 | 5.1378 | 5.0664 | 1.3358 | 1.3065 | 2.1031 | 3.9407
4 | 2.0000 | 0.4329 | 10.6807 | 1.6710 | 2.6385 | 1.0117 | 0.3690
5 | 0.0000 | 0.0000 | 2.8997 | 0.0000 | 0.0000 | 0.1510 | 0.1272

</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 has a slightly different usage in GRASS 7.

<pre>
r.basin [-ac] map=name prefix=prefix coordinates=east,north dir=name [threshold=threshold]
</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 outlet_snap has a table associated, in which all the parameters are stored.

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

R.basin

2017-08-10T09:45:37Z

⚠️Madi: /* Usage */

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

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

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632870 , 222890
Rectangle containing basin S-E : 637000 , 218720
Area of basin [km^2] : 7.8559625
Perimeter of basin [km] : 16.8287990515
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.6772
Mean Slope : 2.93
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.32106255399
Circularity Ratio : 0.348580442132
Topological Diameter : 127.0
Elongation Ratio : 0.470961456397
Shape Factor : 1.16984953656
Concentration Time (Giandotti, 1934) [hr] : 3.52654267443
Length of Mainchannel [km] : 6.715361467
Mean slope of mainchannel [percent] : 0.957339
Mean hillslope length [m] : 8145.381
Magnitudo : 621.0
Max order (Strahler) : 5
Number of streams : 884
Total Stream Length [km] : 96.3436
First order stream frequency : 79.0482388377
Drainage Density [km/km^2] : 12.2637550778
Bifurcation Ratio (Horton) : 5.7374
Length Ratio (Horton) : 2.6902
Area ratio (Horton) : 5.6815
Slope ratio (Horton): 1.5533
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78560.0
===========================
Ipsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
121 | 0.7
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78560.0
Tot. area 7856000.0
Max distance 6809.546521
===========================
Whidth Function | quantiles
===========================
784 | 0.05
1477 | 0.15
2137 | 0.3
2543 | 0.4
2933 | 0.5
3606 | 0.6
4169 | 0.7
5144 | 0.85
6105 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 884 | 96.3436 | 7.8339 | 12.2983 | 112.8429

Stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.7374 | 2.6902 | 5.6815 | 1.5533 | 1.7962
3.1961 | 1.9514 | 5.2294 | 0.1250 | 0.7482

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0750 | 0.0069 | 0.0523 | 0.0384 | 3.1062
2 | 0.1428 | 0.0311 | 0.0342 | 0.0277 | 4.1701
3 | 0.4834 | 0.1732 | 0.0243 | 0.0205 | 9.0641
4 | 2.4205 | 2.1885 | 0.0155 | 0.0134 | 24.1708
5 | 1.1247 | 7.8339 | 0.0091 | 0.0046 | 5.1594

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0600 | 0.0052 | 0.0398 | 0.0287 | 3.2301
2 | 0.1244 | 0.0230 | 0.0250 | 0.0196 | 4.4835
3 | 0.4554 | 0.1353 | 0.0132 | 0.0122 | 7.1065
4 | 2.2874 | 2.3843 | 0.0046 | 0.0061 | 12.9175
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 712 | 53.4067 | 4.8998
2 | 137 | 19.5657 | 4.2562
3 | 31 | 14.9849 | 5.3684
4 | 3 | 7.2616 | 6.5655
5 | 1 | 1.1247 | 7.8339

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.1971 | 1.9040 | 0.0000 | 1.5311 | 1.3892 | 10.8998 | 145.3120
2 | 4.4194 | 3.3847 | 4.5144 | 1.4046 | 1.3472 | 4.5970 | 32.1883
3 | 10.3333 | 5.0075 | 5.5742 | 1.5691 | 1.5365 | 2.7913 | 5.7745
4 | 3.0000 | 0.4646 | 12.6376 | 1.7083 | 2.9120 | 1.1060 | 0.4569
5 | 0.0000 | 0.0000 | 3.5796 | 0.0000 | 0.0000 | 0.1436 | 0.1277
</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 has a slightly different usage in GRASS 7.

<pre>
r.basin [-ac] map=name prefix=prefix coordinates=east,north dir=name [threshold=threshold]
</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 outlet_snap has a table associated, in which all the parameters are stored.

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

R.basin

2017-08-10T09:03:20Z

⚠️Madi:

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

<pre>
r.basin map=elevation@PERMANENT prefix=out easting=636654.791181 northing=218824.126649 threshold=20
</pre>

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632870 , 222890
Rectangle containing basin S-E : 637000 , 218720
Area of basin [km^2] : 7.8559625
Perimeter of basin [km] : 16.8287990515
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.6772
Mean Slope : 2.93
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.32106255399
Circularity Ratio : 0.348580442132
Topological Diameter : 127.0
Elongation Ratio : 0.470961456397
Shape Factor : 1.16984953656
Concentration Time (Giandotti, 1934) [hr] : 3.52654267443
Length of Mainchannel [km] : 6.715361467
Mean slope of mainchannel [percent] : 0.957339
Mean hillslope length [m] : 8145.381
Magnitudo : 621.0
Max order (Strahler) : 5
Number of streams : 884
Total Stream Length [km] : 96.3436
First order stream frequency : 79.0482388377
Drainage Density [km/km^2] : 12.2637550778
Bifurcation Ratio (Horton) : 5.7374
Length Ratio (Horton) : 2.6902
Area ratio (Horton) : 5.6815
Slope ratio (Horton): 1.5533
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78560.0
===========================
Ipsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
121 | 0.7
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78560.0
Tot. area 7856000.0
Max distance 6809.546521
===========================
Whidth Function | quantiles
===========================
784 | 0.05
1477 | 0.15
2137 | 0.3
2543 | 0.4
2933 | 0.5
3606 | 0.6
4169 | 0.7
5144 | 0.85
6105 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 884 | 96.3436 | 7.8339 | 12.2983 | 112.8429

Stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.7374 | 2.6902 | 5.6815 | 1.5533 | 1.7962
3.1961 | 1.9514 | 5.2294 | 0.1250 | 0.7482

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0750 | 0.0069 | 0.0523 | 0.0384 | 3.1062
2 | 0.1428 | 0.0311 | 0.0342 | 0.0277 | 4.1701
3 | 0.4834 | 0.1732 | 0.0243 | 0.0205 | 9.0641
4 | 2.4205 | 2.1885 | 0.0155 | 0.0134 | 24.1708
5 | 1.1247 | 7.8339 | 0.0091 | 0.0046 | 5.1594

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0600 | 0.0052 | 0.0398 | 0.0287 | 3.2301
2 | 0.1244 | 0.0230 | 0.0250 | 0.0196 | 4.4835
3 | 0.4554 | 0.1353 | 0.0132 | 0.0122 | 7.1065
4 | 2.2874 | 2.3843 | 0.0046 | 0.0061 | 12.9175
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 712 | 53.4067 | 4.8998
2 | 137 | 19.5657 | 4.2562
3 | 31 | 14.9849 | 5.3684
4 | 3 | 7.2616 | 6.5655
5 | 1 | 1.1247 | 7.8339

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.1971 | 1.9040 | 0.0000 | 1.5311 | 1.3892 | 10.8998 | 145.3120
2 | 4.4194 | 3.3847 | 4.5144 | 1.4046 | 1.3472 | 4.5970 | 32.1883
3 | 10.3333 | 5.0075 | 5.5742 | 1.5691 | 1.5365 | 2.7913 | 5.7745
4 | 3.0000 | 0.4646 | 12.6376 | 1.7083 | 2.9120 | 1.1060 | 0.4569
5 | 0.0000 | 0.0000 | 3.5796 | 0.0000 | 0.0000 | 0.1436 | 0.1277
</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 has a slightly different usage in GRASS 7.

<pre>
r.basin [-ac] map=name prefix=prefix coordinates=east,north dir=name [threshold=threshold]
</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 outlet_snap has a table associated, in which all the parameters are stored.

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

R.basin

2017-08-10T08:20:50Z

⚠️Madi:

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

<pre>
r.basin map=elevation@PERMANENT prefix=out easting=636654.791181 northing=218824.126649 threshold=20
</pre>

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632870 , 222890
Rectangle containing basin S-E : 637000 , 218720
Area of basin [km^2] : 7.8559625
Perimeter of basin [km] : 16.8287990515
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.6772
Mean Slope : 2.93
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.32106255399
Circularity Ratio : 0.348580442132
Topological Diameter : 127.0
Elongation Ratio : 0.470961456397
Shape Factor : 1.16984953656
Concentration Time (Giandotti, 1934) [hr] : 3.52654267443
Length of Mainchannel [km] : 6.715361467
Mean slope of mainchannel [percent] : 0.957339
Mean hillslope length [m] : 8145.381
Magnitudo : 621.0
Max order (Strahler) : 5
Number of streams : 884
Total Stream Length [km] : 96.3436
First order stream frequency : 79.0482388377
Drainage Density [km/km^2] : 12.2637550778
Bifurcation Ratio (Horton) : 5.7374
Length Ratio (Horton) : 2.6902
Area ratio (Horton) : 5.6815
Slope ratio (Horton): 1.5533
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78560.0
===========================
Ipsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
121 | 0.7
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78560.0
Tot. area 7856000.0
Max distance 6809.546521
===========================
Whidth Function | quantiles
===========================
784 | 0.05
1477 | 0.15
2137 | 0.3
2543 | 0.4
2933 | 0.5
3606 | 0.6
4169 | 0.7
5144 | 0.85
6105 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 884 | 96.3436 | 7.8339 | 12.2983 | 112.8429

Stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.7374 | 2.6902 | 5.6815 | 1.5533 | 1.7962
3.1961 | 1.9514 | 5.2294 | 0.1250 | 0.7482

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0750 | 0.0069 | 0.0523 | 0.0384 | 3.1062
2 | 0.1428 | 0.0311 | 0.0342 | 0.0277 | 4.1701
3 | 0.4834 | 0.1732 | 0.0243 | 0.0205 | 9.0641
4 | 2.4205 | 2.1885 | 0.0155 | 0.0134 | 24.1708
5 | 1.1247 | 7.8339 | 0.0091 | 0.0046 | 5.1594

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0600 | 0.0052 | 0.0398 | 0.0287 | 3.2301
2 | 0.1244 | 0.0230 | 0.0250 | 0.0196 | 4.4835
3 | 0.4554 | 0.1353 | 0.0132 | 0.0122 | 7.1065
4 | 2.2874 | 2.3843 | 0.0046 | 0.0061 | 12.9175
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 712 | 53.4067 | 4.8998
2 | 137 | 19.5657 | 4.2562
3 | 31 | 14.9849 | 5.3684
4 | 3 | 7.2616 | 6.5655
5 | 1 | 1.1247 | 7.8339

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.1971 | 1.9040 | 0.0000 | 1.5311 | 1.3892 | 10.8998 | 145.3120
2 | 4.4194 | 3.3847 | 4.5144 | 1.4046 | 1.3472 | 4.5970 | 32.1883
3 | 10.3333 | 5.0075 | 5.5742 | 1.5691 | 1.5365 | 2.7913 | 5.7745
4 | 3.0000 | 0.4646 | 12.6376 | 1.7083 | 2.9120 | 1.1060 | 0.4569
5 | 0.0000 | 0.0000 | 3.5796 | 0.0000 | 0.0000 | 0.1436 | 0.1277
</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 has a slightly different usage in GRASS 7.

<pre>
r.basin [-ac] map=name prefix=prefix coordinates=east,north dir=name [threshold=threshold]
</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.



== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

Large raster data processing

2017-05-08T14:54:52Z

⚠️Madi: /* See also */

__TOC__

== Large File Support (LFS) ==

Affects 32bit systems which are normally limited to 2GB (2^31) per file. As workaround, LFS can be enabled in GRASS GIS at compile time.

* GRASS GIS 6: much of the raster library and modules can be enabled for LFS during compilation
* GRASS GIS 7: raster and vector libraries are LFS enabled.

See also: [[Large File Support]]

== Workaround: Select a smaller area within a very large dataset before importing in GRASS ==

Suppose that we have all ASTER GDEM world coverage (>22000 files) and we aim to build a mosaic of Europe and import it in GRASS. A nice reference on how to deal with ASTER GDEM is [[ASTER_topography | here]].
The very first step is to select among the >22000 files those covering our area of interest (Europe).
To this aim, we can use use [http://gdal.org/gdaltindex.html gdaltindex] to create an index of all the files:

gdaltindex an_index.shp *.tif

This command will create a polygon shapefile with the footprint of each raster as the polygon shape and the name of the image files represented in the attribute table. After that, we just need to do a spatial select on the shapefile and extract the filenames from the attributes from the selected polygons:

ogr2ogr -f CSV list.csv an_index.shp -spat xmin ymin xmax ymax

will produce a CSV file, from which we can easily copy the list of files in a list.txt.

Here, our area of interest (subset) has the following boundaries:

north: N71: ymax = 72.0001389
south: N34: ymin = 33.9998611
west: W011: xmin = -11.0001389
east: E042: xmax = 43.0001389

At 100m this corresponds to 27.8 billion cells.

== Raster map precision types ==

* '''CELL DATA TYPE''': a raster map from INTEGER type (whole numbers only)
* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 7-9 digits precision)
* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15-17 digits precision)
* '''NULL''': represents "no data" in raster maps, to be distinguished from 0 (zero) data value

Aliases:
* '''INTEGER MAP''': see CELL DATA TYPE
* '''FLOAT MAP''': see FCELL DATA TYPE
* '''DOUBLE MAP''': see DCELL DATA TYPE

See also [[GRASS raster semantics]]

== Create a mosaic ==
Now that we have a list of the files interesting our area, and since our files are all in the same datum (WGS84), we can use [http://www.gdal.org/gdalbuildvrt.html gdalbuildvrt] to create a
[http://www.gdal.org/gdal_vrttut.html virtual] mosaic. This will take only a few seconds to run.

gdalbuildvrt -input_file_list list.csv mosaic.vrt

Also note that gdal can read Tifs within a zip/gz-file as well.

To import the mosaic into GRASS, we first need to create a WGS84 location, then:

r.external input=/path/to/mosaic.vrt output=mosaic

== Split into tiles ==

Sometimes it is possible to work with tiles, i.e. splitting a big map into chunks. These tiles can be easily generated with {{cmd|r.tile}}. It optionally allows for tiling with overlap.

== Raster map precision: reducing file size ==

Not always double precision is needed for raster map computations. Strategies:
* consider to run with FCELL rather than DCELL precision (see {{cmd|r.mapcalc}}'s float() function).
* you may also multiply with e.g. 100 and then round() to integer (used e.g. for BIOCLIM and WORLDCLIM).

Functions in {{cmd|r.mapcalc}} related to precision:
<pre>
double(x) convert x to double-precision floating point (DCELL)
float(x) convert x to single-precision floating point (FCELL)
round(x) round x to nearest integer (INT)
round(x,y) round x to nearest multiple of y (INT)
round(x,y,z) round x to nearest y*i+z for some integer i (INT)
</pre>

See also [[GRASS raster semantics]]

== Troubleshooting ==

=== Number of open files limitation ===

When working with time series or multispectral data, you may experience the following error message (r.series, r.patch etc.):

Too many open files

or

WARNING: Unable to open raster map <somemap@mapset>
ERROR: One or more input raster maps not found

Many operating systems have the limitation of opening 1024 files at the same time. The limits are just to prevent a process from (accidentally or deliberately) consuming too much memory. The descriptor table is in kernel memory, and can't be swapped to disk. However, this can be enlarged. Note that, in GRASS GIS 7.0, each raster map requires two open files: one for the ''cell''/''fcell'' file, one for the ''null'' bitmap.

Resource limits are per-process, and inherited. The ''ulimit'' command (which is a shell built-in) changes the limits for the current shell process; the new limit will be inherited by any child processes.

==== Solution for Linux: System-wise change ====

On most Linux systems, resource limits are set on login by the ''pam_limits'' module according to the settings contained in /etc/security/limits.conf /etc/security/limits.d/*.conf. You should be able to edit those files if you have root privilege (also via sudo), but you will need to log in again as a user before any changes take effect. A reboot shouldn't be necessary since changes to limits.conf should take effect for any subsequent logins. A hard limit can't be increased for any existing non-root processes, or those descended from them.

Increasing a hard limit requires root privilege (or at least the CAP_SYS_RESOURCE capability), so the limits have to be set by the
program which manages the login (login, xdm, sshd, etc) after the user has identified themself (so it knows which limits to set) but before the process changes its ownership from root to the logged-in user.

sudo su
vim /etc/security/limits.conf

Add in /etc/security/limits.conf something like this:
# Limit user nofile - max number of open files
* soft nofile 1500
* hard nofile 1800

Restart the user session (i.e., logout, login).

==== Solution for Windows: System-wise change ====

From the Microsoft documentation it is not very clear how many files can be opened simulaneously (FIX IF POSSIBLE), here some hints:

* https://support.microsoft.com/en-us/kb/87690
* ...

==== Solution for Linux: Session only change ====
To change the limits for an existing session, you may be able to use something like:

sudo bash
ulimit ...
su -c bash <username>

However, sudo will probably reset certain environment variables, particularly LD_LIBRARY_PATH, so you may need to reset those in the new shell.

=== ERROR: G_malloc: unable to allocate xxxx bytes of memory ===

Be sure to use GRASS GIS 7 which has way better support for large files.

If you happen to use the "memory" option requesting more than 2GB (e.g. <tt>memory=3000</tt>) check if you are using 64bit executables since 32bit applications can use only up to 2GB memory. In this case it does not matter if the operating system is 64bit or if there is more than 2GB of memory available. You need to use 64bit binaries of GRASS GIS 7.

== See also ==

* [[GRASS GIS Performance]]
* [[Large vector data processing]]

[[Category:Tutorial]]
[[Category: massive data analysis]]
[[Category: raster]]

Large vector data processing

2017-05-08T14:54:21Z

⚠️Madi: /* See also */

== Option to reduce memory consumption for vector topology ==
''From M.Metz's [http://lists.osgeo.org/pipermail/grass-user/2011-January/059175.html email].''

The topological vector format of GRASS can require quite a bit of memory for larger vectors, which can cause problems such as out-of-memory errors or freezing the machine if a vector module uses up all system memory and goes into swap space.

The largest component in GRASS vector topology is the spatial index which can exceed available system memory with larger vectors, e.g. LiDAR point clouds with hundreds of millions of points, or very large and detailed land cover/land use polygons. In GRASS 7, I have added a new option to use a file-based version of the spatial index which can be activated by setting the new shell environment variable GRASS_VECTOR_LOWMEM, e.g. in bash

export GRASS_VECTOR_LOWMEM=1

and deactivated with

unset GRASS_VECTOR_LOWMEM

As long as the spatial index fits into system memory, e.g. v.build is as expected a bit slower with the file-based version than with the memory-based version and takes about 1.5 times as long for larger vectors (> 100,000 areas). For smaller vectors (e.g. < 50,000 areas),
there is not much difference. If the spatial index does not fit into system memory, the memory-based version would at some stage abort with
an out-of-memory error or go into swap space, whereas the file-based version will very likely complete successfully and not freeze the machine.

Of the vector cleaning tools, breaking polygons (used when importing polygons, the same function as called by v.clean tool=bpol) has the highest memory consumption because all unique vertices of all boundaries are loaded to a search index. I have added a file-based version for breaking polygons in GRASS 7 which is activated as described above. When importing a test vector with 258,000 polygons, memory consumption dropped from 3.9 GB to 90 MB, that is by 98%, while breaking polygons. LFS is recommended for the new file-based version.

== Relevant tickets ==
* https://trac.osgeo.org/grass/ticket/2045

== See also ==

* [[GRASS GIS Performance]]
* [[Large raster data processing]]

[[Category: massive data analysis]]
[[Category: vector]]

GRASS GIS Ispra meetups 2016

2016-10-19T08:53:34Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:Meetup2016-10-18.jpeg|thumb|right|Some fun after the GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 18 10 2016]]

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* Analysis of R code finding the corresponding functions in GRASS.
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]
* Looping GRASS commands in bash
* [[Large_raster_data_processing|Dealing with large datasets]]: [https://grass.osgeo.org/grass73/manuals/r.external.html r.external]; [http://www.gdal.org/gdal_vrttut.html virtual files]
* [[Computational_region|Computational region]]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

File:Meetup2016-10-18.jpeg

2016-10-19T08:47:33Z

⚠️Madi: Some fun after the meetup

Some fun after the meetup

GRASS GIS Ispra meetups 2016

2016-10-18T17:47:30Z

⚠️Madi: /* Work done and topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* Analysis of R code finding the corresponding functions in GRASS.
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]
* Looping GRASS commands in bash
* [[Large_raster_data_processing|Dealing with large datasets]]: [https://grass.osgeo.org/grass73/manuals/r.external.html r.external]; [http://www.gdal.org/gdal_vrttut.html virtual files]
* [[Computational_region|Computational region]]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T17:20:36Z

⚠️Madi: /* Work done and topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* Analysis of R code finding the corresponding functions in GRASS.
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]
* Looping GRASS commands in bash
* [[Large_raster_data_processing|Dealing with large datasets]]: [https://grass.osgeo.org/grass73/manuals/r.external.html r.external]; [http://www.gdal.org/gdal_vrttut.html virtual files]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T17:20:13Z

⚠️Madi: /* Work done and topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* Analysis of a code written in R and finding the corresponding functions in GRASS.
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]
* Looping GRASS commands in bash
* [[Large_raster_data_processing|Dealing with large datasets]]: [https://grass.osgeo.org/grass73/manuals/r.external.html r.external]; [http://www.gdal.org/gdal_vrttut.html virtual files]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T17:17:42Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]: comparison between R and GRASS.
* Looping GRASS commands in bash
* [[Large_raster_data_processing|Dealing with large datasets]]: [https://grass.osgeo.org/grass73/manuals/r.external.html r.external]; [http://www.gdal.org/gdal_vrttut.html virtual files]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T17:06:42Z

⚠️Madi: /* Work done and topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]: comparison between R and GRASS.
* Looping GRASS commands in bash

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:57:07Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Improved documentation {{rev|69701}}
* Using GRASS through QGIS
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]: comparison between R and GRASS.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:53:36Z

⚠️Madi: /* Work done and topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Using GRASS through QGIS
* [https://grasswiki.osgeo.org/wiki/Zonal_statistics Zonal statistics]: comparison between R and GRASS.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:34:06Z

⚠️Madi: /* Done */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Work done and topics touched===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]
* Using GRASS through QGIS

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

R.basin

2016-10-18T16:31:41Z

⚠️Madi: /* Known issues */

== Introduction ==

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.
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 ==

As a first step, we set the computational region to match the elevation raster map:

<pre>
g.region rast=elevation@PERMANENT -ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 228500
south: 215000
west: 630000
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
</pre>

For the basin's delineation, a pair of coordinates is required. Usually coordinates belonging to the natural river network don't exactly match with the calculated stream network. What we should do is to calculate the stream network first, and then to find the coordinates on the calculated stream network closest to the coordinates belonging to the natural stream network.

<pre>
# Calculate flow accumulation map (MFD)
r.watershed -af elevation=elevation@PERMANENT accumulation=accum

# Extract the stream network
r.stream.extract elevation=elevation@PERMANENT accumulation=accum threshold=20 stream_rast=stream_network stream_vect=streams
</pre>

We no longer need the accumulation map:

<pre>
g.remove rast=accum
</pre>

Now that we have the calculated stream network, we should choose a pair of coordinates for the outlet belonging to it. Let's choose for example:

<pre>
easting=636654.791181 northing=218824.126649
</pre>

We no longer need the stream network map:

<pre>
g.remove rast=stream_network
</pre>

== Preparation for multiple basins' analysis ==

If there are a lot of basins to be analysed, the coordinate pairs of the intersections between the calculated stream network and basins (outlet points) can be found by:

<pre>
# Convert basins polygon vector boundaries to lines
v.type input=basinspoly output=basinsline type=boundary,line

# Patch basins lines with stream network
v.patch input=basinsline,streams output=basins_streams

# Find cross points at intersections
v.clean input=basins_streams output=basins_streams_clean error=crosspoints_err tool=break

# Add categories to cross points vector
v.category input=crosspoints_err output=crosspoints

# Add table to cross points vector with columns for category, x and y coordinates
v.db.addtable map=crosspoints columns="cat integer,xcoor double precision, ycoor double precision"

# Upload category to cross points attribute table
v.to.db map=crosspoints option=cat columns=cat

# Upload x and y coordinates to cross points attribute table
v.to.db map=crosspoints option=coor columns=xcoor,ycoor
</pre>

At this point we can create a text file called ''crosspoints'' with the coordinates in this form:

<pre>
xcoor1 ycoor1
xcoor2 ycoor2
xcoor3 ycoor3
...
</pre>

Now we can parse this coordinates file in order to create a new file called ''commands'' in which we'll have the r.basin commands for each sub-watershed, ready to be run in a GRASS session. Let's create a script in python for parsing:

<pre>
#!/usr/bin/env python

# Open the ''crosspoints'' text file to read the coordinates
fin = open("crosspoints","r")

# Create the ''commands'' text file
fout = open("commands","w")

# Read the ''crosspoints'' lines
linesout = (line.rstrip().split() for line in fin)

# Build the r.basin command
# Put your threshold parameter instead of threshold=10000 and the name of your DEM instead of map=elevation
cmd = 'r.basin map=elevation prefix=bas%s easting=%s northing=%s threshold=10000\n'

# Write the file ''commands''
fout.writelines(cmd % (n, easting, northing) for n,(easting,northing) in enumerate(linesout))
</pre>

This is a Python script, it is supposed to run externally from GRASS GIS. Save this script as ''parsing.py'' in a separate folder on your Desktop, and put the file ''crosspoints'' in such folder. To run it, open a terminal and type:

<pre>
cd yourfolder
python parsing.py
</pre>

Now in the same folder you will find the file ''commands'', in which we have the r.basin commands to run in GRASS.

== Usage ==

We can run r.basin:

<pre>
r.basin map=elevation@PERMANENT prefix=out easting=636654.791181 northing=218824.126649 threshold=20
</pre>

Prefix parameter is a string given by the user in order to distinguish all the maps produced by every run of the program, i.e. every set of outlet's coordinates. Prefix must start with a letter.

Threshold is the same parameter given in r.watershed and r.stream.extract. Physically, it means the number of cells that determine "where the river begins". (This is an open issue for the hydrological science and a wide literature has been produced on the topic). Threshold value is usually determined by trials and errors. r.basin has a flag -a, which uses an authomatic value of threshold, corresponding to 1km^2. Such value comes from literature and is usually suitable for Italian territory, but could be definitely wrong for other territories.
In order to determine the threshold, see also {{AddonCmd|r.threshold}} and {{AddonCmd|r.stream.preview}}.

The output of r.basin consists of:

* Several morphometric parameters, which are printed in terminal and also stored in a csv file called out_elevation_parameters.csv, in the working directory;
* Maps;
* Plots.

== Morphometric parameters ==

The main parameters are:

* The coordinates of the vertices of the '''rectangle containing the basin'''.
* The '''center of gravity''' of the basin: the coordinates of the pixel nearest to the center of gravity of the geometric figure resulting from the projection of the basin on the horizontal plane.
* The '''area''' of the basin: is the area of a single cell multiplied by the number of cells belonging to the basin.
* The '''perimeter''': is the length of the contour of the figure resulting by the projection of the basin on the horizontal plane.
[As a side note, a paper namely [http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension "How Long Is the Coast of Britain? Statistical Self-Similarity and Fractional Dimension"] points out that perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset].
* '''Characteristic values of elevation''': the highest and the lowest altitude, the difference between them and the mean elevation calculated as the sum of the values of the cells divided by the number of the cells.
* The '''mean slope''', calculated averaging the slope map.
* The '''length of the directing vector''': the length of the vector linking the outlet to basin's barycenter.
* The '''prevalent orientation''': is the orientation of the directing vector.
* The '''length of main channel''': is the length of the longest succession of segments that connect a source to the outlet of the basin.
* The '''mean slope of main channel''': it is calculated as follows:

<center>
[[File:R.basin1.gif]]
</center>

where N is the topological diameter, i.e. the number of links in which the main channel can be divided on the basis of the junctions.
* The '''circularity ratio''': is the ratio between the area of the basin and the area of the circle having the same perimeter of the basin.
* The '''elongation ratio''': is the ratio between the diameter of the circle having the same area of the basin and the length of the main channel.
* The '''compactness coefficient''': is the ratio between the perimeter of the basin and the diameter of the circle having the same area of the basin.
* The '''shape factor''': is the ratio between the area of the basin and the square of the length of the main channel.
* The '''concentration time''' (Giandotti, 1934):

<center>
[[File:R.basin2.gif]]
</center>

Where A is the area, L the length of the main channel and H the difference between the highest and the lowest elevation of the basin.
* The '''mean hillslope length''': is the mean of the distances calculated along the flow direction of each point non belonging to the river network from the point in which flows into the network.
* The '''magnitudo''': is the number of the branches of order 1 following the Strahler hierarchy.
* The '''max order''': is the order of the basin, following the Strahler hierarchy.
* The '''number of streams''': is the number of the branches of the river network.
* The '''total stream length''': is the sum of the length of every branches.
* The '''first order stream frequency''': is the ratio between the magnitudo and the area of the basin.
* The '''drainage density''': is the ratio between the total length of the river network and the area.
* The '''Horton ratios''' (Horton, 1945; Strahler, 1957).

<pre>
##################################
Morphometric parameters of basin :
##################################
Easting Centroid of basin : 635195.00
Northing Centroid of Basin : 220715.00
Rectangle containing basin N-W : 632870 , 222890
Rectangle containing basin S-E : 637000 , 218720
Area of basin [km^2] : 7.8559625
Perimeter of basin [km] : 16.8287990515
Max Elevation [m s.l.m.] : 151.7396
Min Elevation [m s.l.m.]: 94.82206
Elevation Difference [m]: 56.91754
Mean Elevation [m s.l.m.]: 127.6772
Mean Slope : 2.93
Length of Directing Vector [km] : 2.38880562659
Prevalent Orientation [degree from north, counterclockwise] :
0.913351005341
Compactness Coefficient : 5.32106255399
Circularity Ratio : 0.348580442132
Topological Diameter : 127.0
Elongation Ratio : 0.470961456397
Shape Factor : 1.16984953656
Concentration Time (Giandotti, 1934) [hr] : 3.52654267443
Length of Mainchannel [km] : 6.715361467
Mean slope of mainchannel [percent] : 0.957339
Mean hillslope length [m] : 8145.381
Magnitudo : 621.0
Max order (Strahler) : 5
Number of streams : 884
Total Stream Length [km] : 96.3436
First order stream frequency : 79.0482388377
Drainage Density [km/km^2] : 12.2637550778
Bifurcation Ratio (Horton) : 5.7374
Length Ratio (Horton) : 2.6902
Area ratio (Horton) : 5.6815
Slope ratio (Horton): 1.5533
</pre>

The '''hypsographic curve''' provides the distribution of the areas at different altitudes. Each point on the hypsographic curve has on the y-axis the altitude and on the x-axis the percentage of basin surface placed above that altitude. The '''hypsometric curve''' has the same shape but is dimensionless.
Quantiles of the hypsometric curve are displayed:

<pre>
Tot. cells 78560.0
===========================
Ipsometric | quantiles
===========================
145 | 0.025
143 | 0.05
141 | 0.1
137 | 0.25
129 | 0.5
119 | 0.75
121 | 0.7
110 | 0.9
100 | 0.975
</pre>

The '''width function W(x)''' gives the area of the cells in the basin at a certain flow distance x from the outlet (distance-area function). Note that the distance is not intended in the euclidean sense, but it's calculated considering the hydrological path of the water.

<pre>
Tot. cells 78560.0
Tot. area 7856000.0
Max distance 6809.546521
===========================
Whidth Function | quantiles
===========================
784 | 0.05
1477 | 0.15
2137 | 0.3
2543 | 0.4
2933 | 0.5
3606 | 0.6
4169 | 0.7
5144 | 0.85
6105 | 0.95
</pre>

The output of r.stream.stats is also displayed:

<pre>
Summary:
Max order | Tot.N.str. | Tot.str.len. | Tot.area. | Dr.dens. | Str.freq.
(num) | (num) | (km) | (km2) | (km/km2) | (num/km2)
5 | 884 | 96.3436 | 7.8339 | 12.2983 | 112.8429

Stream ratios with standard deviations:
Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt.
5.7374 | 2.6902 | 5.6815 | 1.5533 | 1.7962
3.1961 | 1.9514 | 5.2294 | 0.1250 | 0.7482

Order | Avg.len | Avg.ar | Avg.sl | Avg.grad. | Avg.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0750 | 0.0069 | 0.0523 | 0.0384 | 3.1062
2 | 0.1428 | 0.0311 | 0.0342 | 0.0277 | 4.1701
3 | 0.4834 | 0.1732 | 0.0243 | 0.0205 | 9.0641
4 | 2.4205 | 2.1885 | 0.0155 | 0.0134 | 24.1708
5 | 1.1247 | 7.8339 | 0.0091 | 0.0046 | 5.1594

Order | Std.len | Std.ar | Std.sl | Std.grad. | Std.el.dif
num | (km) | (km2) | (m/m) | (m/m) | (m)
1 | 0.0600 | 0.0052 | 0.0398 | 0.0287 | 3.2301
2 | 0.1244 | 0.0230 | 0.0250 | 0.0196 | 4.4835
3 | 0.4554 | 0.1353 | 0.0132 | 0.0122 | 7.1065
4 | 2.2874 | 2.3843 | 0.0046 | 0.0061 | 12.9175
5 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000

Order | N.streams | Tot.len (km) | Tot.area (km2)
1 | 712 | 53.4067 | 4.8998
2 | 137 | 19.5657 | 4.2562
3 | 31 | 14.9849 | 5.3684
4 | 3 | 7.2616 | 6.5655
5 | 1 | 1.1247 | 7.8339

Order | Bif.rt. | Len.rt. | Area.rt. | Slo.rt. | Grd.rt. | d.dens. | str.freq.
1 | 5.1971 | 1.9040 | 0.0000 | 1.5311 | 1.3892 | 10.8998 | 145.3120
2 | 4.4194 | 3.3847 | 4.5144 | 1.4046 | 1.3472 | 4.5970 | 32.1883
3 | 10.3333 | 5.0075 | 5.5742 | 1.5691 | 1.5365 | 2.7913 | 5.7745
4 | 3.0000 | 0.4646 | 12.6376 | 1.7083 | 2.9120 | 1.1060 | 0.4569
5 | 0.0000 | 0.0000 | 3.5796 | 0.0000 | 0.0000 | 0.1436 | 0.1277
</pre>

== Maps ==

Since r.basin performs the delimitation of the river basin, all the maps produced are cropped over the basin. They are:

* Raster maps

<pre>
g.list rast

out_elevation_accumulation out_elevation_hillslope_distance
out_elevation_aspect out_elevation_horton
out_elevation_dist2out out_elevation_shreve
out_elevation_drainage out_elevation_slope
out_elevation_hack out_elevation_strahler

</pre>

<center>
<gallery perrow=5 widths=200>

File:Out_elevation_slope.png|Slope
File:Out_elevation_aspect.png|Aspect
File:Out_elevation_drainage.png|Flow direction
File:Out_elevation_accumulation.png|Flow accumulation
File:Out_elevation_dist2out.png|Distance to outlet (width function)
File:Out_elevation_hillslope_distance.png|Length of hillslopes
File:Out_elevation_strahler.png|Stream network ordered according to Strahler
File:Out_elevation_horton.png|Stream network ordered according to Horton
File:Out_elevation_shreve.png|Stream network ordered according to Shreve
File:Out_elevation_hack.png|Stream network ordered according to Hack

</gallery>
</center>

* Vector maps

<pre>
g.list vect

out_elevation_basin out_elevation_network
out_elevation_mainchannel out_elevation_outlet
</pre>

<center>
<gallery perrow=4 widths=200>

File:Out_elevation_basin.png|Basin
File:Out_elevation_mainchannel.png|Main channel
File:Out_elevation_network.png|Stream network
File:Out_elevation_outlet.png|Outlet

</gallery>
</center>

== Graphics ==

Graphics are stored in the working directory:

* out_elevation_ipsographic.png
* out_elevation_ipsometric.png
* out_elevation_width_function.png

<center>
<gallery perrow=3 widths=200>

File:Out_elevation_Ipsographic.png|Ipsographic curve
File:Out_elevation_Ipsometric.png|Ipsometric curve (Nondimensional ipsographic curve)
File:Out_elevation_width_function.png|Width function

</gallery>
</center>

== 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. 
# r.basin is designed to work in meters unit. The values that you get using feet are nonsense. 
# 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 has a slightly different usage in GRASS 7.

<pre>
r.basin [-ac] map=name prefix=prefix coordinates=east,north dir=name [threshold=threshold]
</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 outlet_snap vector map has a table associated, called summary, in which all the calculated parameters are stored.

== See also ==

[[R.stream.*]]

== References ==

* Di Leo Margherita, Di Stefano Massimo, An Open-Source Approach for Catchment's Physiographic Characterization, In: Proceedings of AGU Fall Meeting 2013, S.Francisco, CA, USA.
* Di Leo Margherita, Working report: Extraction of morphometric parameters from a digital elevation model - Panama. North Carolina State University, 2010 ([http://dl.dropbox.com/u/1599323/Report_Panama.pdf PDF])
* Di Leo M., Di Stefano M., Claps P., Sole A., Caratterizzazione morfometrica del bacino idrografico in GRASS GIS (Morphometric characterization of the catchment in GRASS GIS environment), Geomatics Workbooks n.9, 2010. ([http://geomatica.como.polimi.it/workbooks/n9/GW9-FOSS4Git_2010.pdf PDF]).
* Rodriguez-Iturbe I., Rinaldo A., Fractal River Basins, Chance and Self-Organization. Cambridge Press, 2001.

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Hydrology]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:28:02Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Done===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:11:23Z

⚠️Madi: /* 18 Oct 2016 */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

===Done===
* Testing and closing ticket [https://trac.osgeo.org/grass/ticket/2504 #2504 ]

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T16:05:26Z

⚠️Madi: /* Participants */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Philipp Schaegner

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-18T12:37:45Z

⚠️Madi: /* 18 Oct 2016 */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Philipp Schaegner
* ..you..

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-17T12:52:43Z

⚠️Madi: /* Proposed agenda */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* R scripting vs GRASS + Python: some benchmarks.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Philipp Schaegner
* Fabio Fussi
* ..you..

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-17T12:51:07Z

⚠️Madi: /* 18 Oct 2016 */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* ..
* Social dinner w/ beer at clubhouse.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Philipp Schaegner
* Fabio Fussi
* ..you..

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro] [http://dx.doi.org/10.5446/12963 Hi-res version]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-12T08:08:22Z

⚠️Madi: /* 18 Oct 2016 */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* ..
* Social dinner w/ beer at clubhouse.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-12T07:59:32Z

⚠️Madi: /* Proposed agenda */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Short presentations of participants' work and their interest to use GRASS GIS, open discussion.
* How to contribute to the GRASS GIS project.
* ..
* Social dinner / beer at clubhouse.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-12T07:58:49Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* short presentations of participants' work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project.
* ..
* Social dinner / beer at clubhouse.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-10-12T07:57:38Z

⚠️Madi:

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==18 Oct 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room CH-Rose.

'''Time''': h 5:30 PM onward - Feel free to join / leave at any time

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* short presentations of participants' work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project.
* ..
* Social dinner / beer at clubhouse.

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Proposed agenda===
* Introduction of participants with short presentations of their work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project: adding examples to the manual pages.
* Planning meetings and activities of common interest.
* We can take advantage of beer sold at clubhouse and we can have some meters of pizza to be delivered on call.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-09-28T07:16:01Z

⚠️Madi: /* Topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Proposed agenda===
* Introduction of participants with short presentations of their work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project: adding examples to the manual pages.
* Planning meetings and activities of common interest.
* We can take advantage of beer sold at clubhouse and we can have some meters of pizza to be delivered on call.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-09-28T07:12:19Z

⚠️Madi: picture added

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

[[File:IMG 1198.JPG|thumbnail|right|GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016]]

===Proposed agenda===
* Introduction of participants with short presentations of their work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project: adding examples to the manual pages.
* Planning meetings and activities of common interest.
* We can take advantage of beer sold at clubhouse and we can have some meters of pizza to be delivered on call.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Intro to automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

File:IMG 1198.JPG

2016-09-28T07:09:55Z

⚠️Madi: GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016

GRASS GIS Meetup at Clubhouse, Ispra(VA), Italy, on 27 Sep 2016

GRASS GIS Ispra meetups 2016

2016-09-28T07:05:50Z

⚠️Madi: /* Topics touched */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Introduction of participants with short presentations of their work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project: adding examples to the manual pages.
* Planning meetings and activities of common interest.
* We can take advantage of beer sold at clubhouse and we can have some meters of pizza to be delivered on call.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the [https://grass.osgeo.org/grass73/manuals/wxGUI.html Graphical User Interface (GUI)]
* [https://grasswiki.osgeo.org/wiki/Importing_data Importing data]
* Intro to the Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Intro to automating your workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-09-28T07:00:36Z

⚠️Madi: /* 27 Sep 2016 */

A group of people contributing or interested in contributing to GRASS GIS is planning to meet in the coming days in Ispra (VA), Italy, in the Clubhouse of the Joint Research Centre in working days outside working hours and / or during weekend in a place to be decided. If you aren't a contributor but still are interested, please have a look at [https://grass.osgeo.org/documentation/first-time-users/ the documentation for first time users] and come to discover, we will introduce you to GRASS GIS. If you are interested, please contact us.

Moreover, there is a [https://groups.google.com/forum/#!forum/gfoss-jrc mailing list] based in JRC but not only, dedicated to open source geospatial software and local initiatives, you are invited to subscribe to keep yourself up-to-date about local activities related to FOSS. Check also our [https://github.com/gfoss-jrc/mainrepo/wiki wiki].

Contact person: [[User:Madi|Margherita Di Leo]] (diregola gmail com)

==27 Sep 2016==

'''Location''': [http://www.openstreetmap.org/relation/46149?mlat=45.80398008227348&mlon=8.623108863830566#map=18/45.80398008227348/8.623108863830566 '''Clubhouse'''] of the Joint Research Centre, room <strike>CH-Rose</strike> '''Auditorium'''.

'''Time''': h 5:00 PM onward

'''Arrangements''': Bring your laptop, some power strips (ciabatta) if you have, prepare a 5 minutes presentation of your work and what you use / would like to use GRASS for, your experience, your research questions etc..

===Proposed agenda===
* Introduction of participants with short presentations of their work and their interest to use GRASS GIS, questions and answers.
* How to contribute to the GRASS GIS project: adding examples to the manual pages.
* Planning meetings and activities of common interest.
* We can take advantage of beer sold at clubhouse and we can have some meters of pizza to be delivered on call.

===Participants===
* Margherita Di Leo
* Yann Chemin
* Thomas Huld
* Chiara Dorati
* Daniele Borio
* Ciro Gioia
* Ana Gracia
* Ruben Urraca
* Daniele de Rigo
* Philipp Schaegner
* Roxanne Leberger
* Jorge Lopez-Perez
* Fabio Fussi

===Topics touched===
* [https://www.youtube.com/watch?v=U3Hf0qI4JLc&list=PL8_D99w0QB5m4SoYGXbIxyNkspsYFJANW&feature GRASS intro]
* Case studies of GRASS used in research
** Forest tree species distribution
** Solar radiation
** ..
* GRASS installation on MS Windows and Ubuntu
* [https://grass.osgeo.org/download/sample-data Sample data download]
* [https://grasswiki.osgeo.org/wiki/GRASS_Location_Wizard Creating a new location]
* [http://spatialreference.org/ref/epsg/ EPSG codes]
* Getting familiar with the Graphical User Interface (GUI)
* Importing data
* The Command Line Interface (CLI)
* [https://grasswiki.osgeo.org/wiki/GRASS_and_Python GRASS and Python]
* Automating the workflow using bash scripting
* Getting the most updated GRASS version:
** [https://trac.osgeo.org/grass/wiki/DownloadSource Downloading the source code via svn] (on Ubuntu)
** [https://grasswiki.osgeo.org/wiki/Compile_and_Install#Ubuntu Compiling GRASS on Ubuntu]
** [https://wingrass.fsv.cvut.cz/grass73/x86_64/ Nightly builds for MS Windows]

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS GIS Ispra meetups 2016

2016-09-27T18:45:57Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T18:17:31Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:58:20Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:53:43Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:53:02Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:50:22Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:43:36Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:19:33Z

⚠️Madi: /* 27 Sep 2016 */

GRASS GIS Ispra meetups 2016

2016-09-27T17:12:43Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:08:55Z

⚠️Madi: /* Topics touched */

GRASS GIS Ispra meetups 2016

2016-09-27T17:08:29Z

⚠️Madi: /* Topics touched */