GRASS-Wiki - User contributions [en]

Team

2018-09-14T19:47:43Z

⚠️Sbl: /* Add Stefan */

The GRASS GIS project is an international team effort with scientists and developers participating from various fields. Below is a list of the current team.

All general queries concerning GRASS should be addressed to the respective [http://grass.osgeo.org/support/mailing-lists/ GRASS mailing lists]. If you miss yourself or somebody else on the lists below, please feel free to edit this Wiki page or send mail to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list].
__TOC__
== Current contributors to the development of the GRASS code ==

In alphabetical order; see for example [http://www.ohloh.net/p/grass_gis/contributors here] for contribution statistics.

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| width=200px | [[Image:Grasslogo vector small.png|100px|center]]
| '''Anna Kratochvílová''': GRASS 7 wxGUI development, Prague, CZ, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:benjamin.png|100px|center|center]]
| '''Benjamin Ducke''': extension manager, spatial statistics, archaeological applications, predictive modelling Location: Berlin, Germany, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Glynn Clements''': core development, UK, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:hamish.jpg|100px|center]]
| '''Hamish Bowman''': Development of display, PostScript, raster, and GPS modules as well as general sanitation of the code, help, and web pages. Location: Department of Marine Science, University of Otago. Dunedin, New Zealand mail: hamish_b AT yahoo com [http://hamish.bowman.googlepages.com/grassfiles http://hamish.bowman.googlepages.com/grassfiles]

|-
| [[Image:helena.jpg|100px|center]]
| '''Helena Mitasova''': surface and volume modeling and analysis (RST modules), topographic analysis, hydrologic and erosion modelling, assistance with visualization, working with students on new module development, testing, and bug fixing Location: Raleigh, North Carolina, USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ][http://www4.ncsu.edu/~hmitaso/ http://www4.ncsu.edu/~hmitaso/]

|-
| [[Image:hellik.png|100px|center]]
| '''Helmut Kudrnovsky''': [http://grass.osgeo.org/grass64/binary/mswindows/native/ winGRASS packaging],german translation, Austria, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Huidae Cho''': Hydrologic modeling (TOPMODEL modules), DXF modules, FreeType support, Korean translation. Location: Atlanta, Georgia, USA mail: grass4u AT gmail com, IRC Nick: grass4u [http://idea.isnew.info http://idea.isnew.info]

|-
| [[Image:lucadelu.png|100px|center]]
| '''Luca Delucchi''': Python GRASS development (GUI and Modules), Documentation, Italian Translation, Location: Trento (Italy), mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Maris_nartiss.jpg|100px|center]]
| '''[[user:MarisN|Maris Nartiss]]''': Tcl/TK GUI development, Latvia, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Markus Metz''': GRASS 7 development, massive data processing, vector library, Italy + Germany, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:markus.jpg|100px|center]]
| '''Markus Neteler''': various contributions, coordination, main Web site and mailing lists maintenance, Location: Bonn, Germany, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], IRC Nick: markusN [http://www.grassbook.org/neteler/ http://www.grassbook.org/neteler/]

|-
| [[Image:mlanda.png|100px|center]]
| '''Martin Landa''': various contributions, vector engine improvements, [[wxGUI]], Location: Prague, Czech Republic Mail: landa.martin AT gmail.com Homepage: [http://geo.fsv.cvut.cz/~landa http://geo.fsv.cvut.cz/~landa]

|-
| [[Image:michael.jpg|100px|center]]
| '''Michael Barton ''': GRASS native GUI development, Mac binaries, Location: Tempe, Arizona, USA mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ][http://www.public.asu.edu/~cmbarton/ http://www.public.asu.edu/~cmbarton/]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Moritz Lennert''': display tools, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Nikos Alexandris''': tester, contributed add-ons, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Pietro Zambelli''': GRASS7 Python API (mainly pygrass), Location: Europe, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link: ''

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Soeren Gebbert''': improvements of [http://www-pool.math.tu-berlin.de/~soeren/grass/ 3D functionality] mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
|
[[Image:Stefan.png|100px|center]]
| '''Stefan Blumentrath''': GRASS Python development, Oslo, NO, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list][https://www.nina.no/english/Contact/Employees/Employee-info?AnsattID=14230 NINA Oslo]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Stepan Turek''': GRASS 7 wxGUI development, Prague, CZ, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Vaclav Petras''': GRASS 7 wxGUI development, Prague, CZ, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''William Kyngesburye''': [http://www.kyngchaos.com/software:grass/ Mac OS X packaging], USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Yann Chemin''': image processing, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''''your name''': what-you-do, Location: xyz, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link: ''

|}

== Former or currently inactive developers ==

(in alphabetical order)

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| width=200px | [[Image:Grasslogo vector small.png|100px|center]]
| '''Bob Covill''' Role: visualization, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Brad Douglas''' Role: bug fixing, code portability, imagery modules Location: Fremont, California, USA, IRC Nick: bdouglas, mail: rez AT touchofmadness com

|-
| [[Image:cedric.jpg|100px|center]]
| '''Cedric Shock''' Role: user interface enhancements, debugging Location: Eugene, Oregon, USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], [http://www.shockfamily.net/cedric/ http://www.shockfamily.net/cedric/]

|-
| [[Image:DaveSampson.png|100px|center]]
| '''Dave Sampson''' Role: tutorials, data sets & public data licensing, GRASS map gallery, Ottawa Chapter of OSGeo, Location: Ottawa, Ontario, Canada, mail: samper.d at gmail dot com [http://davidsampson.ca/ http://davidsampson.ca]

|-
| [[Image:jachym.png|100px|center]]
| '''Jachym Cepicky''' Role: bug fixing, support of 3D vectors, tester and translator, UI developer, Czech Republic, mail: jachym.cepicky AT gmail.com [http://les-ejk.cz/ http://les-ejk.cz/]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Jaroslav Hofierka''' Role: development of modules for solar irradiation, flow routing, surface and volume modelling and analysis (RST modules), hydrologic and erosion modelling, assistance with visualization Location: Presov, Slovakia, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:maciek.png|100px|center]]
| '''Maciej Sieczka''' Role: power user, testing Location: Wroclaw, Poland, mail: msieczka AT sieczka.org [http://www.sieczka.org/ http://www.sieczka.org]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Marco Pasetti''' Role: Microsoft Windows native binary port of GRASS Location: Brescia, Italy, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link: [http://grass.osgeo.org/grass64/binary/mswindows/native/ WinGRASS Project Homepage]

|-
| [[Image:Grasslogo vector small.png|100px|center]]
| '''Paul Kelly''' Role: Proj integration, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:radim.jpg|100px|center]]
| '''Radim Blazek''' Role: DBMI, vector engine core developer, Location: Trento, Italy till 2006, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:scott.jpg|100px|center]]
| '''Scott Mitchell''' Role: tutorial and documentation development, web site maintenance, Ottawa User's Group, OSGeo Journal News and Events Editor Location: Ottawa, Ontario, Canada, mail: [http://lists.osgeo.org/mailman/listinfo/grass-web GRASS web site maintenance mailing list] [http://www.carleton.ca/~smitch http://www.carleton.ca/~smitch]

|}

== The following institutions are currently supporting the GRASS-Project ==

Please see our [http://grass.osgeo.org/donations/ GRASS sponsoring] page.

And a ''thank-you'' to:

* the many people who have contributed in the past
* the various users who have contributed bug reports and tested unstable GRASS versions;
* all the sites (and the people behind them) that provide mirrors for the GRASS web pages.

File:Stefan.png

2018-09-14T19:44:50Z

⚠️Sbl:

Stefan

GRASS Python Scripting Library

2018-04-23T10:18:19Z

⚠️Sbl: update cleanup to new g.remove

{{Python}}
Python API documentation:

* [http://grass.osgeo.org/grass70/manuals/libpython/ Python API for GRASS GIS 7] and [http://grass.osgeo.org/grass70/manuals/libpython/script_intro.html Python Scripting Library]
* [http://grass.osgeo.org/programming6/pythonlib.html for GRASS GIS 6]: core.py, db.py, raster.py, vector.py, setup.py, array.py task.py

The GRASS Python Scripting Library can be imported by statement

<source lang=python>
import grass.script as gscript
</source>

The other packages such as PyGRASS can be imported in a similar way.

The code in {{src|lib/python/|lib/python}} provides <tt>grass.script</tt> and other packages in order to support GRASS scripts written in Python. The {{src|scripts}} directory of GRASS GIS 7 contains a series of examples actually provided to the end users (while the script in GRASS GIS 6 are shell scripts).

For more general info, see also [[GRASS and Python]] and see also [[Converting Bash scripts to Python]] if you have some Bash scripts you want to rewrite to Python.

== Uses for read, feed and pipe, start and exec commands ==

All of the <tt>*_command</tt> functions use {{pyapi|script|script.core|make_command}} to construct a command
line for a program which uses the {{cmd|g.parser|desc=GRASS parser}}. Most of them then pass
that command line to <tt>subprocess.Popen()</tt> via {{pyapi|script|script.core|start_command}}, except
for {{pyapi|script|script.core|exec_command}} which uses <tt>os.execvpe()</tt>.

[To be precise, they use <tt>grass.Popen()</tt>, which just calls
<tt>subprocess.Popen()</tt> with 'shell=True' on Windows and 'shell=False'
otherwise. On Windows, you need to use 'shell=True' to be able to
execute scripts (including batch files); 'shell=False' only works with
binary executables.]

{{pyapi|script|script.core|start_command}} separates the arguments into those which
<tt>subprocess.Popen()</tt> understands and the rest. The rest are passed to
<tt>make_command()</tt> to construct a command line which is passed as the
"args" parameter to <tt>subprocess.Popen()</tt>.

In other words, {{pyapi|script|script.core|start_command}} is a GRASS-oriented interface to
<tt>subprocess.Popen()</tt>. It should be suitable for any situation where you
would use <tt>subprocess.Popen()</tt> to execute a normal GRASS command (one
which uses the GRASS parser, which is almost all of them; the main
exception is {{cmd|r.mapcalc}} in 6.x).

Most of the others are convenience wrappers around <tt>start_command()</tt>, for common use cases.

* {{pyapi|script|script.core|run_command}} calls the wait() method on the process, so it doesn't return until the command has finished, and returns the command's exit code. Similar to <tt>system()</tt>.

* {{pyapi|script|script.core|pipe_command}} calls <tt>start_command()</tt> with 'stdout=PIPE' and returns the process object. You can use the process' .stdout member to read the command's stdout. Similar to popen(..., "r").

* {{pyapi|script|script.core|feed_command}} calls <tt>start_command()</tt> with stdin=PIPE and returns the process object. You can use the process' .stdin member to write to the command's stdout. Similar to popen(..., "w")

* {{pyapi|script|script.core|read_command}} calls <tt>pipe_command()</tt>, reads the data from the command's stdout, and returns it as a string. Similar to `backticks` in the shell.

* {{pyapi|script|script.core|write_command}} calls <tt>feed_command()</tt>, sends the string specified by the "stdin" argument to the command's stdin, waits for the command to finish and returns its exit code. Similar to "echo ... | command".

* {{pyapi|script|script.core|parse_command}} calls <tt>read_command()</tt> and parses its output as key-value pairs. Useful for obtaining information from {{cmd|g.region}}, {{cmd|g.proj}}, {{cmd|r.info}}, etc.

* {{pyapi|script|script.core|exec_command}} doesn't use <tt>start_command()</tt> but <tt>os.execvpe()</tt>. This causes the specified command to replace the current program (i.e. the Python script), so <tt>exec_command()</tt> never returns. Similar to bash's "exec" command. This can be useful if the script is a "wrapper" around a single command, where you construct the command line and execute the command as the final step. Notes: exec_command() is rarely appropriate. You probably want run_command() instead. On Windows, exec_command() will probably require the ".exe" suffix.

If you have any other questions, you might want to look at the code ({{src|lib/python/core.py}}). Most of these functions are only a few lines long.

=== Hints for parse_command() ===

To turn this command
g.rename rast=old_name,new_name
into a g.parse_command() call, you need to consider that it is a function call with three arguments:
# "g.rename"
# rast=old_name
# new_name

The second argument is a keyword argument, the first and third are
positional (non-keyword) arguments. Python doesn't allow positional
arguments to follow keyword arguments; positional arguments come
first, keyword arguments last.

Given the context, it's safe to assume that you want to pass a pair of
map names as the value to the rast= option. This requires explicit
parentheses so that the comma is treated as forming a tuple rather
than as an argument separator:

g.parse_command("g.rename", rast=(old_name,new_name))

The parentheses in a tuple value can only be omitted if it doesn't
result in the comma being ambiguous (as is the case in a function
call).

== Interfacing ==

=== Interfacing with NumPy ===

The {{pyapi|script|script.array|array}} module defines a <code>class array</code> which is a subclass of [http://docs.scipy.org/doc/numpy/reference/generated/numpy.memmap.html numpy.memmap] with <code>.read()</code> and <code>.write()</code> methods to read/write the underlying file via {{cmd|r.out.bin}}/{{cmd|r.in.bin}}. Metadata can be read with {{pyapi|script|script.raster|raster_info}}:

Example:

<source lang="python">
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

# read map
a = garray.array()
a.read(map)

# get raster map info
print grass.raster_info(map)['datatype']
i = grass.raster_info(map)

# get computational region info
c = grass.region()
print "rows: %d" % c['rows']
print "cols: %d" % c['cols']

# new array for result
b = garray.array()
# calculate new map from input map and store as GRASS raster map
b[...] = (a / 50).astype(int) * 50
b.write("elev.50m")
</source>

The size of the array is taken from the current region ([[computational region]]).

The main drawback of using numpy is that you're limited by available
memory. Using a subclass of <code>numpy.memmap</code> lets you use files which may
be much larger, but processing the entire array in one go is likely to
produce in-memory results of a similar size.

'''NULL (no data) management:'''

For integer maps, the NULL value is -2^31 = -2147483648. For floating-point maps, the NULL value is NaN. Note that the null= parameter for read() and write() specifies the value in the numpy array which is mapped to/from null values in the GRASS raster map.

If you're using floating-point numpy arrays, then use (Note: This assumes that atof() and sscanf("%lf") recognise "nan"; this is the case on Linux, but doesn't appear to work on Windows)
null=numpy.nan

For integer arrays, using
null=-2147483648
will ensure that valid values don't collide with NYLLs.

'''MASK support:'''

The function grass.script.array.read() and ...write() use r.out.bin and r.in.bin respectively. r.out.bin respects the MASK.

=== Interfacing with NumPy and SciPy ===

[http://docs.scipy.org/doc/scipy/reference/index.html SciPy] offers simple access to complex calculations. Example:

<source lang="python">
from scipy import stats
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

x = garray.array()
x.read(map)

# Descriptive Statistics:
print "max, min, mean, var:"
print x.max(), x.min(), x.mean(), x.var()
print "Skewness test: z-score and 2-sided p-value:"
print stats.skewtest(stats.skew(x))
</source>

=== Interfacing with NumPy, SciPy and Matlab ===

One may also use the SciPy - Matlab interface:

r.out.mat input=elevation output=elev.mat

<source lang="python">
### PY ###
import scipy.io as sio
# load data
elev = sio.loadmat('elev.mat')
# retrive the actual array. the data set contains also the spatial reference
elev.get('map_data')
data = elev.get('map_data')
# a first simple plot
import pylab
pylab.plot(data)
pylab.show()
# the contour plot
pylab.contour(data)
# obviously data needs to ne reversed
import numpy as np
data_rev = data[::-1]
pylab.contour(data_rev)
# => this is a quick plot. basemap mapping may provide a nicer map!
#######
</source>

== Usage Examples ==

=== Display example ===
Example of Python script, which is processed by {{cmd|g.parser}}:

<source lang="python">
#!/usr/bin/env python
#
############################################################################
#
# MODULE: d.shadedmap
# AUTHOR(S): Unknown; updated to GRASS 5.7 by Michael Barton
# Converted to Python by Glynn Clements
# PURPOSE: Uses d.his to drape a color raster over a shaded relief map
# COPYRIGHT: (C) 2004,2008,2009 by the GRASS Development Team
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################

#%Module
#% description: Drapes a color raster over a shaded relief map using d.his
#% keyword: display
#% keyword: raster
#%End
#%option
#% key: reliefmap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of shaded relief or aspect map
#% required : yes
#%end
#%option
#% key: drapemap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of raster to drape over relief map
#% required : yes
#%end
#%option
#% key: brighten
#% type: integer
#% description: Percent to brighten
#% options: -99-99
#% answer: 0
#%end

import sys
from grass.script import core as grass

def main():
drape_map = options['drapemap']
relief_map = options['reliefmap']
brighten = options['brighten']
ret = grass.run_command("d.his", h_map = drape_map, i_map = relief_map, brighten = brighten)
sys.exit(ret)

if __name__ == "__main__":
options, flags = grass.parser()
main()

</source>

=== Parsing the options and flags ===

{{pyapi|script|script.core|parser}} is an interface to {{cmd|g.parser}}, and allows to parse the ''options'' and ''flags'' passed to your script on the command line. It is to be called at the top-level:

<source lang="python">
if __name__ == "__main__":
options, flags = grass.parser()
main()
</source>

Global variables "options" and "flags" are Python dictionaries containing the options/flags values, keyed by lower-case option/flag names. The values in "options" are strings, those in "flags" are Python booleans. All those variables have to be previously declared in the header of your script.

<source lang="python">
>>> options, flags = grass.parser()
>>> options
{'input': 'my_map', 'output': 'map_out', 'option1': '21.472', 'option2': ''}
>>> flags
{'c': True, 'm': False}
</source>

'''Passing several floats to a single option:'''

Example:
<source lang="bash">
python my.module.py input=input output=output myoption=0.1,0.2,0.5
</source>

The values in the "options" dictionary returned from the parser()
function are always strings. You can parse the string with:

<source lang="python">
myoption = map(float, options['myoption'].split(','))
</source>

The option definition in the script should have:

<source lang="python">
#% type: double
#% multiple: yes
</source>

This allows g.parser to validate the option syntax, so you can rely
upon the string being in the correct format. If the values have a
fixed range, you can use e.g.:

<source lang="python">
#% options: 0.0-1.0
</source>

to have the parser check that the values fall within the range.

For more information on option definitions, see:

http://grass.osgeo.org/programming7/gislib.html#Complete_Structure_Members_Table

=== Example for embedding r.mapcalc (map algebra) ===

{{pyapi|script|script.raster|mapcalc}} accepts a template string followed by keyword
arguments for the substitutions, e.g. (code snippets):

<source lang="python">
grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = options['output'],
rast1 = options['raster1'],
rast2 = options['raster2'])
</source>

''Best practice'': first copy all of the options[] into separate variables at the beginning of main(), i.e.:

<source lang="python">
def main():
output = options['output']
raster1 = options['raster1']
raster2 = options['raster2']

...

grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = output,
rast1 = raster1,
rast2 = raster2)
</source>

Performing multiple computations using <tt>grass.script.raster.mapcalc()</tt>:
<source lang="python">
expr = ";".join([
"$out.r = r#$first * $frac + (1.0 - $frac) * r#$second",
"$out.g = g#$first * $frac + (1.0 - $frac) * g#$second",
"$out.b = b#$first * $frac + (1.0 - $frac) * b#$second"])
grass.mapcalc(expr, out=out, first=first, second=second, frac=percent/100.0)
</source>

Hint: multi-line strings can be separated by using a semicolon instead of a newline.

=== Looping over file names stored in an ASCII file ===

When looping over file names stored in an ASCII file and getting the error

WARNING: Illegal filename <map.f1jan.05216.something
>. Character <
> not allowed.

then the line terminators may be the reason.
When you iterate over a file, the strings include the line terminators (e.g. '\n' or '\r\n'). Use e.g.

<source lang="python">
for line in gl:
renamed = line.rstrip().replace('.','_')
...
</source>

to remove any trailing whitespace (including newlines) from each line.

=== Example for parsing raster category labels ===

How to obtain the text labels
<source lang="python">
# dump cats to file to avoid "too many argument" problem:
p = grass.pipe_command('r.category', map = rastertmp, separator = ';', quiet = True)
cats = []
for line in p.stdout:
cats.append(line.rstrip('\r\n').split(';')[0])
p.wait()

number = len(cats)
if number < 1:
grass.fatal(_("No categories found in raster map"))
</source>

=== Example for parsing category numbers ===

'''Q:''' How to obtain the number of cells of a certain category?

'''A:''' It is recommended to use {{pyapi|script|script.core|pipe_command}} and parse the output, e.g.:

<source lang="python">
p = grass.pipe_command('r.stats',flags='c',input='map')
result = {}
for line in p.stdout:
val,count = line.strip().split()
result[int(val)] = int(count)
p.wait()
</source>

=== Example for parsing the region output of a module ===

Some of the GRASS GIS modules are delivering region information (e.g. {{cmd|r.in.xyz}} which scans a LiDAR file for the extent of the point cloud). The retrieved region settings (using '''-g''' flag for script style output) can be parsed in Python:

<source lang="python">
import os
from grass.script import core as gcore

from grass.pygrass.modules.shortcuts import general as g
from grass.pygrass.modules.shortcuts import raster as r

# scan a LiDAR xyz point file for its extent
compregion = gcore.parse_command("r.in.xyz", input="tmp.xyz", separator="space", flags="sg", output="bbox",
parse=(gcore.parse_key_val, {'sep': '=', 'vsep': ' '}))
print(compregion)
# set computational region from LiDAR extent
# hint: we turn here the dictionary to a region by unpacking the dictionary:
g.region(res="1", flags="p", **compregion)
</source>

Note the two '''*''' above which unpack the dictionary (see also the related [https://docs.python.org/2/tutorial/controlflow.html#keyword-arguments Python manual] page).

=== Example for getting the region's number of rows and columns ===

'''Q:''' How to obtain the number of rows and columns of the current region?

'''A:''' It is recommended to use the {{pyapi|script|script.core|region}} function which will create a dictionary with values for extents and resolution, e.g.:

<source lang="python">
#!/usr/bin/env python
#-*- coding:utf-8 -*-
#
############################################################################
#
# MODULE: g.region.resolution
# AUTHOR(S): based on a post at GRASS-USER mailing list [1]
# PURPOSE: Parses "g.region -g", prints out number of rows, cols
# COPYLEFT: ;-)
# COMMENT: ...a lot of comments to be easy-to-read for/by beginners
#
#############################################################################
#
#%Module
#% description: Print number of rows, cols of current geographic region
#% keyword: region
#%end

# importing required modules
import sys # the sys module [2]
from grass.script import core as grass # the core module [3]

# information about imported modules can be obtained using the dir() function
# e.g.: dir(sys)

# define the "main" function: get number of rows, cols of region
def main():

# #######################################################################
# the following commented code works but is kept only for learning purposes

## assigning the output of the command "g.region -g" in a string called "return_rows_x_cols"
# return_rows_x_cols = grass.read_command('g.region', flags = 'g')

## parsing arguments of interest (rows, cols) in a dictionary named "rows_x_cols"
# rows_x_cols = grass.parse_key_val(return_rows_x_cols)

## selectively print rows, cols from the dictionary "rows_x_cols"
# print 'rows=%d \ncols=%d' % (int(rows_x_cols['rows']), int(rows_x_cols['cols']))

# #######################################################################

# faster/ easier way: use of the "grass.region()" function
gregion = grass.region()
rows = gregion['rows']
cols = gregion['cols']

# print rows, cols properly formated
print 'rows=%d \ncols=%d' % (rows, cols)

# this "if" condition instructs execution of code contained in this script, *only* if the script is being executed directly
if __name__ == "__main__": # this allows the script to be used as a module in other scripts or as a standalone script
options, flags = grass.parser() #
sys.exit(main()) #

# Links
# [1] http://n2.nabble.com/Getting-rows-cols-of-a-region-in-a-script-tp2787474p2787509.html
# [2] http://www.python.org/doc/2.5.2/lib/module-sys.html
# [3] https://grass.osgeo.org/grass75/manuals/libpython
</source>

=== Managing mapsets ===

To check if a certain mapset exists in the active location, use {{pyapi|script|script.core|mapsets}}

<source lang="python">
grass.mapsets(False)
</source>

... returns a list of mapsets in the current location.

=== r.mapcalc example ===

Example of Python script, which is processed by {{cmd|g.parser}}:

The shell script line:

<source lang="bash">
r.mapcalc "MASK = if(($cloudResampName < 0.01000),1,null())"
</source>

would be written like this:

<source lang="python">
import grass.script as grass

...

grass.mapcalc("MASK=if(($cloudResampName < 0.01000),1,null())",
cloudResampName = cloudResampName)
</source>

The first argument to the mapcalc function is a template (see the Python library documentation for [http://docs.python.org/library/string.html string.Template]). Any keyword arguments (other than <tt>quiet</tt>, <tt>verbose</tt> or <tt>overwrite</tt>) specify substitutions.

=== r.mapcalc example: defining a moving window ===

Moving window of 4 cell in every 8 direction and do a boolean comparison. Boolean value (e.g. the result of a comparison) is an integer, with 1 for true, 0 for false.
Then do a r.mapcalc calculation with the moving window.

<source lang="python">

import grass.script as grass

# define a moving window of 4 cell in every 8 direction
#
# map[4,4] map[4,0] map[4,-4]
# map[3,3] map[3,0] map[3,-3]
# map[2,2] map[2,0] map[2,-2]
# map[1,1] map[1,0] map[1,-1]
# map[0,4] map[0,3] map[0,2] map[0,1] x map[0,-1] map[0,-2] map[0,-3] map[0,-4]
# map[-1,1] map[-1,0] map[-1,-1]
# map[-2,2] map[-2,0] map[-2,-2]
# map[-3,3] map[-3,0] map[-3,-3]
# map[-4,4] map[-4,0] map[-4,-4]

# define the offet duplets

offsets = [d
for j in xrange(1,4+1)
for i in [j,-j]
for d in [(i,0),(0,i),(i,i),(i,-i)]]

# >>>offsets
# [(1, 0), (0, 1), (1, 1), (1, -1), (-1, 0), (0, -1), (-1, -1), (-1, 1), (2, 0), (0, 2), (2, 2), (2, -2), (-2, 0), (0, -2), \
# (-2, -2), (-2, 2), (3, 0), (0, 3), (3, 3), (3, -3), (-3, 0), (0, -3), (-3, -3), (-3, 3), (4, 0), (0, 4), (4, 4), (4, -4), \
# (-4, 0), (0, -4), (-4, -4), (-4, 4)]

# define the calculation term

terms = ["(myelevnc[%d,%d] < myelevnc)" % d
for d in offsets]

# >>>terms
# ['(myelevnc[1,0] < myelevnc)', '(myelevnc[0,1] < myelevnc)', '(myelevnc[1,1] < myelevnc)', '(myelevnc[1,-1] < myelevnc)', \
# '(myelevnc[-1,0] < myelevnc)', '(myelevnc[0,-1] < myelevnc)', '(myelevnc[-1,-1] < myelevnc)', '(myelevnc[-1,1] < myelevnc)',\
# '(myelevnc[2,0] < myelevnc)', '(myelevnc[0,2] < myelevnc)', '(myelevnc[2,2] < myelevnc)', '(myelevnc[2,-2] < myelevnc)', \
# '(myelevnc[-2,0] < myelevnc)', '(myelevnc[0,-2] < myelevnc)', '(myelevnc[-2,-2] < myelevnc)', '(myelevnc[-2,2] < myelevnc)', \
# '(myelevnc[3,0] < myelevnc)', '(myelevnc[0,3] < myelevnc)', '(myelevnc[3,3] < myelevnc)', '(myelevnc[3,-3] < myelevnc)', \
# '(myelevnc[-3,0] < myelevnc)', '(myelevnc[0,-3] < myelevnc)', '(myelevnc[-3,-3] < myelevnc)', '(myelevnc[-3,3] < myelevnc)', \
# '(myelevnc[4,0] < myelevnc)', '(myelevnc[0,4] < myelevnc)', '(myelevnc[4,4] < myelevnc)', '(myelevnc[4,-4] < myelevnc)', \
# '(myelevnc[-4,0] < myelevnc)', '(myelevnc[0,-4] < myelevnc)', '(myelevnc[-4,-4] < myelevnc)', '(myelevnc[-4,4] < myelevnc)']

# define the calculation expression

expr = "elevation_percentile4 = (100.0 / 48.0) * (%s)" % " + ".join(terms)

# >>>expr
# elevation_percentile4 = (100.0 / 48.0) * ((myelevnc[1,0] < myelevnc) + (myelevnc[0,1] < myelevnc) + (myelevnc[1,1] < myelevnc) + \
# (myelevnc[1,-1] < myelevnc) + (myelevnc[-1,0] < myelevnc) + (myelevnc[0,-1] < myelevnc) + (myelevnc[-1,-1] < myelevnc) + \
# (myelevnc[-1,1] < myelevnc) + (myelevnc[2,0] < myelevnc) + (myelevnc[0,2] < myelevnc) + (myelevnc[2,2] < myelevnc) + \
# (myelevnc[2,-2] < myelevnc) + (myelevnc[-2,0] < myelevnc) + (myelevnc[0,-2] < myelevnc) + (myelevnc[-2,-2] < myelevnc) + \
# (myelevnc[-2,2] < myelevnc) + (myelevnc[3,0] < myelevnc) + (myelevnc[0,3] < myelevnc) + (myelevnc[3,3] < myelevnc) + \
# (myelevnc[3,-3] < myelevnc) + (myelevnc[-3,0] < myelevnc) + (myelevnc[0,-3] < myelevnc) + (myelevnc[-3,-3] < myelevnc) + \
# (myelevnc[-3,3] < myelevnc) + (myelevnc[4,0] < myelevnc) + (myelevnc[0,4] < myelevnc) + (myelevnc[4,4] < myelevnc) + \
# (myelevnc[4,-4] < myelevnc) + (myelevnc[-4,0] < myelevnc) + (myelevnc[0,-4] < myelevnc) + (myelevnc[-4,-4] < myelevnc)\
# + (myelevnc[-4,4] < myelevnc))

# do the r.mapcalc calculation with the moving window

grass.mapcalc( expr )

</source>

=== Using output from GRASS modules in the script ===

Sometimes you need to use the output of a module for the next step. There are dedicated functions to obtain the result of, for example, a statistical analysis.

Example: get the range of a raster map and use it in {{cmd|r.mapcalc}}. Here you can use {{pyapi|script|script.raster|raster_info}}, e.g.:

<source lang="python">
import grass.script as grass

max = grass.raster_info(inmap)['max']
grass.mapcalc("$outmap = $inmap / $max",
inmap = inmap, outmap = outmap, max = max)
</source>

=== Using output from r.what ===

''Q: How does one return attribute values from a call to the 'r.what' module running in a python script?''

A: If you use <tt>grass.script.raster_what()</tt>, it returns a list of dictionaries.

PyGRASS which requires you to add <tt>stdout_=PIPE</tt>, then you can get the output as a string from <tt>module.outputs.stdout</tt>.

Or using directly the C API through python with (North Carolina dataset example):

<source lang="python">
from grass.pygrass.vector import VectorTopo
from grass.pygrass.raster import RasterRow
from grass.pygrass.gis.region import Region

with RasterRow('elevation', mode='r') as rast:
with VectorTopo('hospitals', mode='r') as hospitals:
region = Region()
for hosp in hospitals:
value = rast.get_value(hosp, region)
if value is not None:
print(hosp.cat, value)
</source>

=== Calling a GRASS module in Python ===

Imagine, you wanted to execute this command in Python:
<source lang="bash">
r.profile -g input=mymap output=newfile profile=12244.256,-295112.597,12128.012,-295293.77
</source>

All arguments except the first (which is a flag) are keyword arguments, i.e. <tt>arg = val</tt>. For the flag, use <tt>flags = 'g'</tt> (note that "-g" would be the negative of a Python variable named "g"!). So:

<source lang="python">
grass.run_command('r.profile',
input = input_map,
output = output_file,
profile = [12244.256,-295112.597,12128.012,-295293.77]
</source>
or:
<source lang="python">
profile = [(12244.256,-295112.597),(12128.012,-295293.77)]
</source>

i.e. you need to provide the keyword, and the argument must be a valid Python expression. Function <code>run_command()</code> etc accept lists and tuples.

'''What is the proper way to include keyword-arguments tuples?'''

For example, "g.list -f type=rast,vect" translates into:
<source lang="python">
grass.run_command("g.list", flags="f", type="rast,vect")
</source>
or:
<source lang="python">
grass.run_command("g.list", flags="f", type=["rast","vect"])
</source>

The various *_command() functions accept arbitrary keyword arguments. Any keywords which don't have a specific meaning to either the *_command() function or the Popen constructor are treated as arguments to the GRASS module.

'''What is the proper way to use multiple flags?'''

How can I call a module with multiple flags set (e.g., -a and -b) in GRASS-Python?

flags = "ab"

Example:
<source lang="python">
grass.run_command("r.info", flags="eg", map=["elevation"])
</source>

'''Differences between ''run_command()'' and ''read_command()'':'''

* {{pyapi|script|script.core|run_command}} executes the command and waits for it to terminate; it doesn't redirect any of the standard streams.
* {{pyapi|script|script.core|read_command}} executes the command with stdout redirected to a pipe, and reads everything written to it. Once the command terminates, it returns the data written to stdout as a string.

'''How to retrieve error messages from ''read_command()'':'''

None of the existing *_command functions redirect stderr. You can do so with e.g.:

<source lang="python">
def read2_command(*args, **kwargs):
kwargs['stdout'] = grass.PIPE
kwargs['stderr'] = grass.PIPE
ps = grass.start_command(*args, **kwargs)
return ps.communicate()
</source>

This behaves like <tt>read_command()</tt> except that it returns a tuple of (stdout, stderr) rather than just stdout.

=== Interface to copying maps (g.copy) ===

Copy a raster map (for vector, replace "rast" with "vect"):

<source lang="python">
grass.run_command('g.copy', rast = (input, output))
</source>

To generalize it, "datatype" is the form of grass data to copy (eg, rast, vect, etc)

<source lang="python">
grass.run_command('g.copy', **{datatype: (input, output)})
</source>

=== Interface to listing maps (g.list) ===

You may use the functions in [http://grass.osgeo.org/programming7/namespacepython_1_1script_1_1core.html python.script.core.mlist_grouped()]:

<source lang="python">
list_grouped('raster')['PERMANENT']
[..., 'lakes', ..., 'slope', ...
</source>

and

<source lang="python">
mlist_grouped('vector', pattern='*roads*')['PERMANENT']
['railroads', 'roadsmajor']
</source>

See also [[Python/pygrass#Sample_PyGRASS_scripts|Sample PyGRASS scripts]] for an alternative solution.

=== i.group with patterns as name for input ===

Imagery groups can be populated like this:

<source lang="python">
from grass.pygrass.gis import Mapset

run_command("i.group", group="mygroup", input=mset.glist("raster", pattern="mypattern_*"))
</source>

=== Percentage output for progress of computation ===

A) Within a Python script, the {{pyapi|script|script.core|percent}} module method wraps the <tt>g.message -p</tt> command.

B) If you call a GRASS command within the Python code, you have to parse the output by setting <tt>GRASS_MESSAGE_FORMAT=gui</tt> in the environment when running the command and read from the command's stderr; e.g.

<source lang="python">
import grass.script as grass
env = os.environ.copy()
env['GRASS_MESSAGE_FORMAT'] = 'gui'
p = grass.start_command(..., stderr = grass.PIPE, env = env)
# read from p.stderr
p.wait()
</source>

If you need to capture both stdout and stderr, you need to use threads, select, or non-blocking I/O to consume data from both streams as it is generated in order to avoid deadlock.

ALTERNATIVE:

Redirect both stdout and stderr to the same pipe (and hope that the normal output doesn't include anything which will be mistaken for progress/error/etc messages):

<source lang="python">
p = grass.start_command(..., stdout = grass.PIPE, stderr = grass.STDOUT, env = env)
</source>

=== NULL data management ===

How to analyse if there are only NULL cells in a map:

If a map contains only null cells, its minimum and maximum will be "NULL":

<source lang="bash">
$ r.mapcalc 'foo = null()'
$ r.info -r foo
min=NULL
max=NULL
</source>

Using the Python API, The 'min' and 'max' values in the result of the {{pyapi|script|script.raster|raster_info}} function will be <tt>None</tt>.

=== Counting cells ===

Counting cells is far more expensive than simply determining whether
there are any non-null cells. Counting cells requires reading the
entire map, while the {{cmd|r.info}} approach only needs to read the metadata
files.

If you do need to count cells, {{cmd|r.stats}} is likely to be more efficient than {{cmd|r.univar}}.

A count loop:

<source lang="python">
while grass.raster_info(inmap)['max'] is not None:
...
</source>

=== Display: overlayed map display with labels ===

Example: display a vector map and overlay its labels on top of the map.

If the environment contains the setting GRASS_PNG_READ=TRUE, d.* commands should overlay their output on an existing image (otherwise the first command creates the file map.png but the second command overwrites the file with only the labels). So the following should work:

<source lang="python">
grass.run_command('d.vect', map='my_shape')
env = os.environ.copy()
env['GRASS_PNG_READ'] = 'TRUE'
grass.run_command('d.labels', labels='my_shape_labels', env = env)
</source>

=== Path to GISDBASE ===
In order to a avoid hardcoded paths to GRASS mapset files like the SQLite DB file, you can get the GISDBASE variable from the environment:
<source lang="python">
import grass.script as grass
import os.path

env = grass.gisenv()

gisdbase = env['GISDBASE']
location = env['LOCATION_NAME']
mapset = env['MAPSET']

path = os.path.join(gisdbase, location, mapset, 'sqlite.db')
</source>

=== Creating a new location ===

Use {{pyapi|script|script.core|create_location}} to create a new location.

=== Use Python reserved keyword ===

'''Q:''' ''r.resamp.bspline'' uses 'lambda' as a command line parameter name, but when you try to use it with {{pyapi|script|script.core|run_command}} or {{pyapi|script|script.core|start_command}} you get an error as lambda is a python reserved keyword. How to work around that?

'''A:''' Append an underscore to the name, i.e.:

<source lang="python">
grass.run_command('r.resamp.bspline', lambda_ = ...)
</source>

Note that this follows Python [http://legacy.python.org/dev/peps/pep-0008/#descriptive-naming-styles PEP8] style guide. In GRASS GIS version 6, you have to prepend the underscore.

=== Controlling the PNG display driver ===

Code fragment to control the {{cmd|pngdriver}} in Python:

<source lang="python">
import os
import sys
from grass.script import core as grass
def main():
os.environ['GRASS_PNGFILE'] = filename
os.environ['GRASS_WIDTH'] = str(width)
os.environ['GRASS_HEIGHT'] = str(height)
grass.run_command('d.his', i='elevation_shade', h='elevation')
</source>

=== Sophisticated cleanup procedure ===

Scripts which create several temporary files need a more sophisticated cleanup procedure which deletes all the tmp maps which have been created. This procedure should also work if the script stops (e.g due to an error).

Solution: Define a list of map names which starts out empty and has names appended to it as the names are generated. Code fragment:

<source lang="python">
import atexit, sys
import grass.script as grass

tmp_rast = []

def cleanup():
for rast in tmp_rast:
grass.run_command("g.remove",
flags = 'f',
type = 'raster',
name = rast,
quiet = True)

def main():
...
while ...:
next_rast = ...
tmp_rast.append(next_rast)
...

if __name__ == "__main__":
options, flags = grass.parser()
atexit.register(cleanup)
sys.exit(main())
</source>

=== Using temporary region for computations ===

There are two possible ways how to define temporary region for raster-based computations within your scripts. First method uses environmental variable WIND_OVERRIDE, the second GRASS_REGION, see {{cmd|variables|desc=GRASS variables}} for more info. The key point is to recover the current region when the script is finished or terminated.

* ''First method'' (WIND_OVERRIDE) is implemented as {{pyapi|script|script.core|use_temp_region}}

<source lang=python>
import grass.script as grass

# store the current region settings and installs an atexit
# handler to recover the current region on script termination
grass.use_temp_region()

grass.run_command('g.region', region='detail')

grass.mapcalc('map = 1', overwrite=True)

# after making operations using the temporary region,
# to unset the temporary WIND_OVERRIDE file and remove any
# region named by it, it is possible to use del_temp_region
grass.del_temp_region()
</source>

* ''Second method'' (GRASS_REGION) doesn't store current region settings to any temporary region, it just defines GRASS_REGION which forces GIS Library to use this settings for raster-based computations instead of the settings stored in WIND file (ie. current region). See {{pyapi|script|script.core|region_env}}.

<source lang=python>
import os
import grass.script as grass

# copy environment and define GRASS_REGION environmental variable
# same as `g.region region=detail`
env = os.environ.copy()
env['GRASS_REGION'] = grass.region_env(region='detail')

grass.mapcalc('map = 1', overwrite=True, env=env)
</source>

== Direct Access from wxGUI ==

[[wxGUI]] Layer Manager in GRASS GIS comes with "Python shell" which enables users to type and execute python commands directly in wxGUI environment.

[[Image:wxgui-pyshell.png|center|400px|Embedded interactive Python Shell in wxGUI Layer Manager]]

== See also ==

* [[GRASS GIS Jupyter notebooks]]
* [[Working with GRASS without starting it explicitly‎]]
* Many more tutorials under [[:Category:Python]]

GRASS Python Scripting Library

2018-04-23T10:16:32Z

⚠️Sbl: update cleanup to new g.remove

{{Python}}
Python API documentation:

* [http://grass.osgeo.org/grass70/manuals/libpython/ Python API for GRASS GIS 7] and [http://grass.osgeo.org/grass70/manuals/libpython/script_intro.html Python Scripting Library]
* [http://grass.osgeo.org/programming6/pythonlib.html for GRASS GIS 6]: core.py, db.py, raster.py, vector.py, setup.py, array.py task.py

The GRASS Python Scripting Library can be imported by statement

<source lang=python>
import grass.script as gscript
</source>

The other packages such as PyGRASS can be imported in a similar way.

The code in {{src|lib/python/|lib/python}} provides <tt>grass.script</tt> and other packages in order to support GRASS scripts written in Python. The {{src|scripts}} directory of GRASS GIS 7 contains a series of examples actually provided to the end users (while the script in GRASS GIS 6 are shell scripts).

For more general info, see also [[GRASS and Python]] and see also [[Converting Bash scripts to Python]] if you have some Bash scripts you want to rewrite to Python.

== Uses for read, feed and pipe, start and exec commands ==

All of the <tt>*_command</tt> functions use {{pyapi|script|script.core|make_command}} to construct a command
line for a program which uses the {{cmd|g.parser|desc=GRASS parser}}. Most of them then pass
that command line to <tt>subprocess.Popen()</tt> via {{pyapi|script|script.core|start_command}}, except
for {{pyapi|script|script.core|exec_command}} which uses <tt>os.execvpe()</tt>.

[To be precise, they use <tt>grass.Popen()</tt>, which just calls
<tt>subprocess.Popen()</tt> with 'shell=True' on Windows and 'shell=False'
otherwise. On Windows, you need to use 'shell=True' to be able to
execute scripts (including batch files); 'shell=False' only works with
binary executables.]

{{pyapi|script|script.core|start_command}} separates the arguments into those which
<tt>subprocess.Popen()</tt> understands and the rest. The rest are passed to
<tt>make_command()</tt> to construct a command line which is passed as the
"args" parameter to <tt>subprocess.Popen()</tt>.

In other words, {{pyapi|script|script.core|start_command}} is a GRASS-oriented interface to
<tt>subprocess.Popen()</tt>. It should be suitable for any situation where you
would use <tt>subprocess.Popen()</tt> to execute a normal GRASS command (one
which uses the GRASS parser, which is almost all of them; the main
exception is {{cmd|r.mapcalc}} in 6.x).

Most of the others are convenience wrappers around <tt>start_command()</tt>, for common use cases.

* {{pyapi|script|script.core|run_command}} calls the wait() method on the process, so it doesn't return until the command has finished, and returns the command's exit code. Similar to <tt>system()</tt>.

* {{pyapi|script|script.core|pipe_command}} calls <tt>start_command()</tt> with 'stdout=PIPE' and returns the process object. You can use the process' .stdout member to read the command's stdout. Similar to popen(..., "r").

* {{pyapi|script|script.core|feed_command}} calls <tt>start_command()</tt> with stdin=PIPE and returns the process object. You can use the process' .stdin member to write to the command's stdout. Similar to popen(..., "w")

* {{pyapi|script|script.core|read_command}} calls <tt>pipe_command()</tt>, reads the data from the command's stdout, and returns it as a string. Similar to `backticks` in the shell.

* {{pyapi|script|script.core|write_command}} calls <tt>feed_command()</tt>, sends the string specified by the "stdin" argument to the command's stdin, waits for the command to finish and returns its exit code. Similar to "echo ... | command".

* {{pyapi|script|script.core|parse_command}} calls <tt>read_command()</tt> and parses its output as key-value pairs. Useful for obtaining information from {{cmd|g.region}}, {{cmd|g.proj}}, {{cmd|r.info}}, etc.

* {{pyapi|script|script.core|exec_command}} doesn't use <tt>start_command()</tt> but <tt>os.execvpe()</tt>. This causes the specified command to replace the current program (i.e. the Python script), so <tt>exec_command()</tt> never returns. Similar to bash's "exec" command. This can be useful if the script is a "wrapper" around a single command, where you construct the command line and execute the command as the final step. Notes: exec_command() is rarely appropriate. You probably want run_command() instead. On Windows, exec_command() will probably require the ".exe" suffix.

If you have any other questions, you might want to look at the code ({{src|lib/python/core.py}}). Most of these functions are only a few lines long.

=== Hints for parse_command() ===

To turn this command
g.rename rast=old_name,new_name
into a g.parse_command() call, you need to consider that it is a function call with three arguments:
# "g.rename"
# rast=old_name
# new_name

The second argument is a keyword argument, the first and third are
positional (non-keyword) arguments. Python doesn't allow positional
arguments to follow keyword arguments; positional arguments come
first, keyword arguments last.

Given the context, it's safe to assume that you want to pass a pair of
map names as the value to the rast= option. This requires explicit
parentheses so that the comma is treated as forming a tuple rather
than as an argument separator:

g.parse_command("g.rename", rast=(old_name,new_name))

The parentheses in a tuple value can only be omitted if it doesn't
result in the comma being ambiguous (as is the case in a function
call).

== Interfacing ==

=== Interfacing with NumPy ===

The {{pyapi|script|script.array|array}} module defines a <code>class array</code> which is a subclass of [http://docs.scipy.org/doc/numpy/reference/generated/numpy.memmap.html numpy.memmap] with <code>.read()</code> and <code>.write()</code> methods to read/write the underlying file via {{cmd|r.out.bin}}/{{cmd|r.in.bin}}. Metadata can be read with {{pyapi|script|script.raster|raster_info}}:

Example:

<source lang="python">
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

# read map
a = garray.array()
a.read(map)

# get raster map info
print grass.raster_info(map)['datatype']
i = grass.raster_info(map)

# get computational region info
c = grass.region()
print "rows: %d" % c['rows']
print "cols: %d" % c['cols']

# new array for result
b = garray.array()
# calculate new map from input map and store as GRASS raster map
b[...] = (a / 50).astype(int) * 50
b.write("elev.50m")
</source>

The size of the array is taken from the current region ([[computational region]]).

The main drawback of using numpy is that you're limited by available
memory. Using a subclass of <code>numpy.memmap</code> lets you use files which may
be much larger, but processing the entire array in one go is likely to
produce in-memory results of a similar size.

'''NULL (no data) management:'''

For integer maps, the NULL value is -2^31 = -2147483648. For floating-point maps, the NULL value is NaN. Note that the null= parameter for read() and write() specifies the value in the numpy array which is mapped to/from null values in the GRASS raster map.

If you're using floating-point numpy arrays, then use (Note: This assumes that atof() and sscanf("%lf") recognise "nan"; this is the case on Linux, but doesn't appear to work on Windows)
null=numpy.nan

For integer arrays, using
null=-2147483648
will ensure that valid values don't collide with NYLLs.

'''MASK support:'''

The function grass.script.array.read() and ...write() use r.out.bin and r.in.bin respectively. r.out.bin respects the MASK.

=== Interfacing with NumPy and SciPy ===

[http://docs.scipy.org/doc/scipy/reference/index.html SciPy] offers simple access to complex calculations. Example:

<source lang="python">
from scipy import stats
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

x = garray.array()
x.read(map)

# Descriptive Statistics:
print "max, min, mean, var:"
print x.max(), x.min(), x.mean(), x.var()
print "Skewness test: z-score and 2-sided p-value:"
print stats.skewtest(stats.skew(x))
</source>

=== Interfacing with NumPy, SciPy and Matlab ===

One may also use the SciPy - Matlab interface:

r.out.mat input=elevation output=elev.mat

<source lang="python">
### PY ###
import scipy.io as sio
# load data
elev = sio.loadmat('elev.mat')
# retrive the actual array. the data set contains also the spatial reference
elev.get('map_data')
data = elev.get('map_data')
# a first simple plot
import pylab
pylab.plot(data)
pylab.show()
# the contour plot
pylab.contour(data)
# obviously data needs to ne reversed
import numpy as np
data_rev = data[::-1]
pylab.contour(data_rev)
# => this is a quick plot. basemap mapping may provide a nicer map!
#######
</source>

== Usage Examples ==

=== Display example ===
Example of Python script, which is processed by {{cmd|g.parser}}:

<source lang="python">
#!/usr/bin/env python
#
############################################################################
#
# MODULE: d.shadedmap
# AUTHOR(S): Unknown; updated to GRASS 5.7 by Michael Barton
# Converted to Python by Glynn Clements
# PURPOSE: Uses d.his to drape a color raster over a shaded relief map
# COPYRIGHT: (C) 2004,2008,2009 by the GRASS Development Team
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################

#%Module
#% description: Drapes a color raster over a shaded relief map using d.his
#% keyword: display
#% keyword: raster
#%End
#%option
#% key: reliefmap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of shaded relief or aspect map
#% required : yes
#%end
#%option
#% key: drapemap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of raster to drape over relief map
#% required : yes
#%end
#%option
#% key: brighten
#% type: integer
#% description: Percent to brighten
#% options: -99-99
#% answer: 0
#%end

import sys
from grass.script import core as grass

def main():
drape_map = options['drapemap']
relief_map = options['reliefmap']
brighten = options['brighten']
ret = grass.run_command("d.his", h_map = drape_map, i_map = relief_map, brighten = brighten)
sys.exit(ret)

if __name__ == "__main__":
options, flags = grass.parser()
main()

</source>

=== Parsing the options and flags ===

{{pyapi|script|script.core|parser}} is an interface to {{cmd|g.parser}}, and allows to parse the ''options'' and ''flags'' passed to your script on the command line. It is to be called at the top-level:

<source lang="python">
if __name__ == "__main__":
options, flags = grass.parser()
main()
</source>

Global variables "options" and "flags" are Python dictionaries containing the options/flags values, keyed by lower-case option/flag names. The values in "options" are strings, those in "flags" are Python booleans. All those variables have to be previously declared in the header of your script.

<source lang="python">
>>> options, flags = grass.parser()
>>> options
{'input': 'my_map', 'output': 'map_out', 'option1': '21.472', 'option2': ''}
>>> flags
{'c': True, 'm': False}
</source>

'''Passing several floats to a single option:'''

Example:
<source lang="bash">
python my.module.py input=input output=output myoption=0.1,0.2,0.5
</source>

The values in the "options" dictionary returned from the parser()
function are always strings. You can parse the string with:

<source lang="python">
myoption = map(float, options['myoption'].split(','))
</source>

The option definition in the script should have:

<source lang="python">
#% type: double
#% multiple: yes
</source>

This allows g.parser to validate the option syntax, so you can rely
upon the string being in the correct format. If the values have a
fixed range, you can use e.g.:

<source lang="python">
#% options: 0.0-1.0
</source>

to have the parser check that the values fall within the range.

For more information on option definitions, see:

http://grass.osgeo.org/programming7/gislib.html#Complete_Structure_Members_Table

=== Example for embedding r.mapcalc (map algebra) ===

{{pyapi|script|script.raster|mapcalc}} accepts a template string followed by keyword
arguments for the substitutions, e.g. (code snippets):

<source lang="python">
grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = options['output'],
rast1 = options['raster1'],
rast2 = options['raster2'])
</source>

''Best practice'': first copy all of the options[] into separate variables at the beginning of main(), i.e.:

<source lang="python">
def main():
output = options['output']
raster1 = options['raster1']
raster2 = options['raster2']

...

grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = output,
rast1 = raster1,
rast2 = raster2)
</source>

Performing multiple computations using <tt>grass.script.raster.mapcalc()</tt>:
<source lang="python">
expr = ";".join([
"$out.r = r#$first * $frac + (1.0 - $frac) * r#$second",
"$out.g = g#$first * $frac + (1.0 - $frac) * g#$second",
"$out.b = b#$first * $frac + (1.0 - $frac) * b#$second"])
grass.mapcalc(expr, out=out, first=first, second=second, frac=percent/100.0)
</source>

Hint: multi-line strings can be separated by using a semicolon instead of a newline.

=== Looping over file names stored in an ASCII file ===

When looping over file names stored in an ASCII file and getting the error

WARNING: Illegal filename <map.f1jan.05216.something
>. Character <
> not allowed.

then the line terminators may be the reason.
When you iterate over a file, the strings include the line terminators (e.g. '\n' or '\r\n'). Use e.g.

<source lang="python">
for line in gl:
renamed = line.rstrip().replace('.','_')
...
</source>

to remove any trailing whitespace (including newlines) from each line.

=== Example for parsing raster category labels ===

How to obtain the text labels
<source lang="python">
# dump cats to file to avoid "too many argument" problem:
p = grass.pipe_command('r.category', map = rastertmp, separator = ';', quiet = True)
cats = []
for line in p.stdout:
cats.append(line.rstrip('\r\n').split(';')[0])
p.wait()

number = len(cats)
if number < 1:
grass.fatal(_("No categories found in raster map"))
</source>

=== Example for parsing category numbers ===

'''Q:''' How to obtain the number of cells of a certain category?

'''A:''' It is recommended to use {{pyapi|script|script.core|pipe_command}} and parse the output, e.g.:

<source lang="python">
p = grass.pipe_command('r.stats',flags='c',input='map')
result = {}
for line in p.stdout:
val,count = line.strip().split()
result[int(val)] = int(count)
p.wait()
</source>

=== Example for parsing the region output of a module ===

Some of the GRASS GIS modules are delivering region information (e.g. {{cmd|r.in.xyz}} which scans a LiDAR file for the extent of the point cloud). The retrieved region settings (using '''-g''' flag for script style output) can be parsed in Python:

<source lang="python">
import os
from grass.script import core as gcore

from grass.pygrass.modules.shortcuts import general as g
from grass.pygrass.modules.shortcuts import raster as r

# scan a LiDAR xyz point file for its extent
compregion = gcore.parse_command("r.in.xyz", input="tmp.xyz", separator="space", flags="sg", output="bbox",
parse=(gcore.parse_key_val, {'sep': '=', 'vsep': ' '}))
print(compregion)
# set computational region from LiDAR extent
# hint: we turn here the dictionary to a region by unpacking the dictionary:
g.region(res="1", flags="p", **compregion)
</source>

Note the two '''*''' above which unpack the dictionary (see also the related [https://docs.python.org/2/tutorial/controlflow.html#keyword-arguments Python manual] page).

=== Example for getting the region's number of rows and columns ===

'''Q:''' How to obtain the number of rows and columns of the current region?

'''A:''' It is recommended to use the {{pyapi|script|script.core|region}} function which will create a dictionary with values for extents and resolution, e.g.:

<source lang="python">
#!/usr/bin/env python
#-*- coding:utf-8 -*-
#
############################################################################
#
# MODULE: g.region.resolution
# AUTHOR(S): based on a post at GRASS-USER mailing list [1]
# PURPOSE: Parses "g.region -g", prints out number of rows, cols
# COPYLEFT: ;-)
# COMMENT: ...a lot of comments to be easy-to-read for/by beginners
#
#############################################################################
#
#%Module
#% description: Print number of rows, cols of current geographic region
#% keyword: region
#%end

# importing required modules
import sys # the sys module [2]
from grass.script import core as grass # the core module [3]

# information about imported modules can be obtained using the dir() function
# e.g.: dir(sys)

# define the "main" function: get number of rows, cols of region
def main():

# #######################################################################
# the following commented code works but is kept only for learning purposes

## assigning the output of the command "g.region -g" in a string called "return_rows_x_cols"
# return_rows_x_cols = grass.read_command('g.region', flags = 'g')

## parsing arguments of interest (rows, cols) in a dictionary named "rows_x_cols"
# rows_x_cols = grass.parse_key_val(return_rows_x_cols)

## selectively print rows, cols from the dictionary "rows_x_cols"
# print 'rows=%d \ncols=%d' % (int(rows_x_cols['rows']), int(rows_x_cols['cols']))

# #######################################################################

# faster/ easier way: use of the "grass.region()" function
gregion = grass.region()
rows = gregion['rows']
cols = gregion['cols']

# print rows, cols properly formated
print 'rows=%d \ncols=%d' % (rows, cols)

# this "if" condition instructs execution of code contained in this script, *only* if the script is being executed directly
if __name__ == "__main__": # this allows the script to be used as a module in other scripts or as a standalone script
options, flags = grass.parser() #
sys.exit(main()) #

# Links
# [1] http://n2.nabble.com/Getting-rows-cols-of-a-region-in-a-script-tp2787474p2787509.html
# [2] http://www.python.org/doc/2.5.2/lib/module-sys.html
# [3] https://grass.osgeo.org/grass75/manuals/libpython
</source>

=== Managing mapsets ===

To check if a certain mapset exists in the active location, use {{pyapi|script|script.core|mapsets}}

<source lang="python">
grass.mapsets(False)
</source>

... returns a list of mapsets in the current location.

=== r.mapcalc example ===

Example of Python script, which is processed by {{cmd|g.parser}}:

The shell script line:

<source lang="bash">
r.mapcalc "MASK = if(($cloudResampName < 0.01000),1,null())"
</source>

would be written like this:

<source lang="python">
import grass.script as grass

...

grass.mapcalc("MASK=if(($cloudResampName < 0.01000),1,null())",
cloudResampName = cloudResampName)
</source>

The first argument to the mapcalc function is a template (see the Python library documentation for [http://docs.python.org/library/string.html string.Template]). Any keyword arguments (other than <tt>quiet</tt>, <tt>verbose</tt> or <tt>overwrite</tt>) specify substitutions.

=== r.mapcalc example: defining a moving window ===

Moving window of 4 cell in every 8 direction and do a boolean comparison. Boolean value (e.g. the result of a comparison) is an integer, with 1 for true, 0 for false.
Then do a r.mapcalc calculation with the moving window.

<source lang="python">

import grass.script as grass

# define a moving window of 4 cell in every 8 direction
#
# map[4,4] map[4,0] map[4,-4]
# map[3,3] map[3,0] map[3,-3]
# map[2,2] map[2,0] map[2,-2]
# map[1,1] map[1,0] map[1,-1]
# map[0,4] map[0,3] map[0,2] map[0,1] x map[0,-1] map[0,-2] map[0,-3] map[0,-4]
# map[-1,1] map[-1,0] map[-1,-1]
# map[-2,2] map[-2,0] map[-2,-2]
# map[-3,3] map[-3,0] map[-3,-3]
# map[-4,4] map[-4,0] map[-4,-4]

# define the offet duplets

offsets = [d
for j in xrange(1,4+1)
for i in [j,-j]
for d in [(i,0),(0,i),(i,i),(i,-i)]]

# >>>offsets
# [(1, 0), (0, 1), (1, 1), (1, -1), (-1, 0), (0, -1), (-1, -1), (-1, 1), (2, 0), (0, 2), (2, 2), (2, -2), (-2, 0), (0, -2), \
# (-2, -2), (-2, 2), (3, 0), (0, 3), (3, 3), (3, -3), (-3, 0), (0, -3), (-3, -3), (-3, 3), (4, 0), (0, 4), (4, 4), (4, -4), \
# (-4, 0), (0, -4), (-4, -4), (-4, 4)]

# define the calculation term

terms = ["(myelevnc[%d,%d] < myelevnc)" % d
for d in offsets]

# >>>terms
# ['(myelevnc[1,0] < myelevnc)', '(myelevnc[0,1] < myelevnc)', '(myelevnc[1,1] < myelevnc)', '(myelevnc[1,-1] < myelevnc)', \
# '(myelevnc[-1,0] < myelevnc)', '(myelevnc[0,-1] < myelevnc)', '(myelevnc[-1,-1] < myelevnc)', '(myelevnc[-1,1] < myelevnc)',\
# '(myelevnc[2,0] < myelevnc)', '(myelevnc[0,2] < myelevnc)', '(myelevnc[2,2] < myelevnc)', '(myelevnc[2,-2] < myelevnc)', \
# '(myelevnc[-2,0] < myelevnc)', '(myelevnc[0,-2] < myelevnc)', '(myelevnc[-2,-2] < myelevnc)', '(myelevnc[-2,2] < myelevnc)', \
# '(myelevnc[3,0] < myelevnc)', '(myelevnc[0,3] < myelevnc)', '(myelevnc[3,3] < myelevnc)', '(myelevnc[3,-3] < myelevnc)', \
# '(myelevnc[-3,0] < myelevnc)', '(myelevnc[0,-3] < myelevnc)', '(myelevnc[-3,-3] < myelevnc)', '(myelevnc[-3,3] < myelevnc)', \
# '(myelevnc[4,0] < myelevnc)', '(myelevnc[0,4] < myelevnc)', '(myelevnc[4,4] < myelevnc)', '(myelevnc[4,-4] < myelevnc)', \
# '(myelevnc[-4,0] < myelevnc)', '(myelevnc[0,-4] < myelevnc)', '(myelevnc[-4,-4] < myelevnc)', '(myelevnc[-4,4] < myelevnc)']

# define the calculation expression

expr = "elevation_percentile4 = (100.0 / 48.0) * (%s)" % " + ".join(terms)

# >>>expr
# elevation_percentile4 = (100.0 / 48.0) * ((myelevnc[1,0] < myelevnc) + (myelevnc[0,1] < myelevnc) + (myelevnc[1,1] < myelevnc) + \
# (myelevnc[1,-1] < myelevnc) + (myelevnc[-1,0] < myelevnc) + (myelevnc[0,-1] < myelevnc) + (myelevnc[-1,-1] < myelevnc) + \
# (myelevnc[-1,1] < myelevnc) + (myelevnc[2,0] < myelevnc) + (myelevnc[0,2] < myelevnc) + (myelevnc[2,2] < myelevnc) + \
# (myelevnc[2,-2] < myelevnc) + (myelevnc[-2,0] < myelevnc) + (myelevnc[0,-2] < myelevnc) + (myelevnc[-2,-2] < myelevnc) + \
# (myelevnc[-2,2] < myelevnc) + (myelevnc[3,0] < myelevnc) + (myelevnc[0,3] < myelevnc) + (myelevnc[3,3] < myelevnc) + \
# (myelevnc[3,-3] < myelevnc) + (myelevnc[-3,0] < myelevnc) + (myelevnc[0,-3] < myelevnc) + (myelevnc[-3,-3] < myelevnc) + \
# (myelevnc[-3,3] < myelevnc) + (myelevnc[4,0] < myelevnc) + (myelevnc[0,4] < myelevnc) + (myelevnc[4,4] < myelevnc) + \
# (myelevnc[4,-4] < myelevnc) + (myelevnc[-4,0] < myelevnc) + (myelevnc[0,-4] < myelevnc) + (myelevnc[-4,-4] < myelevnc)\
# + (myelevnc[-4,4] < myelevnc))

# do the r.mapcalc calculation with the moving window

grass.mapcalc( expr )

</source>

=== Using output from GRASS modules in the script ===

Sometimes you need to use the output of a module for the next step. There are dedicated functions to obtain the result of, for example, a statistical analysis.

Example: get the range of a raster map and use it in {{cmd|r.mapcalc}}. Here you can use {{pyapi|script|script.raster|raster_info}}, e.g.:

<source lang="python">
import grass.script as grass

max = grass.raster_info(inmap)['max']
grass.mapcalc("$outmap = $inmap / $max",
inmap = inmap, outmap = outmap, max = max)
</source>

=== Using output from r.what ===

''Q: How does one return attribute values from a call to the 'r.what' module running in a python script?''

A: If you use <tt>grass.script.raster_what()</tt>, it returns a list of dictionaries.

PyGRASS which requires you to add <tt>stdout_=PIPE</tt>, then you can get the output as a string from <tt>module.outputs.stdout</tt>.

Or using directly the C API through python with (North Carolina dataset example):

<source lang="python">
from grass.pygrass.vector import VectorTopo
from grass.pygrass.raster import RasterRow
from grass.pygrass.gis.region import Region

with RasterRow('elevation', mode='r') as rast:
with VectorTopo('hospitals', mode='r') as hospitals:
region = Region()
for hosp in hospitals:
value = rast.get_value(hosp, region)
if value is not None:
print(hosp.cat, value)
</source>

=== Calling a GRASS module in Python ===

Imagine, you wanted to execute this command in Python:
<source lang="bash">
r.profile -g input=mymap output=newfile profile=12244.256,-295112.597,12128.012,-295293.77
</source>

All arguments except the first (which is a flag) are keyword arguments, i.e. <tt>arg = val</tt>. For the flag, use <tt>flags = 'g'</tt> (note that "-g" would be the negative of a Python variable named "g"!). So:

<source lang="python">
grass.run_command('r.profile',
input = input_map,
output = output_file,
profile = [12244.256,-295112.597,12128.012,-295293.77]
</source>
or:
<source lang="python">
profile = [(12244.256,-295112.597),(12128.012,-295293.77)]
</source>

i.e. you need to provide the keyword, and the argument must be a valid Python expression. Function <code>run_command()</code> etc accept lists and tuples.

'''What is the proper way to include keyword-arguments tuples?'''

For example, "g.list -f type=rast,vect" translates into:
<source lang="python">
grass.run_command("g.list", flags="f", type="rast,vect")
</source>
or:
<source lang="python">
grass.run_command("g.list", flags="f", type=["rast","vect"])
</source>

The various *_command() functions accept arbitrary keyword arguments. Any keywords which don't have a specific meaning to either the *_command() function or the Popen constructor are treated as arguments to the GRASS module.

'''What is the proper way to use multiple flags?'''

How can I call a module with multiple flags set (e.g., -a and -b) in GRASS-Python?

flags = "ab"

Example:
<source lang="python">
grass.run_command("r.info", flags="eg", map=["elevation"])
</source>

'''Differences between ''run_command()'' and ''read_command()'':'''

* {{pyapi|script|script.core|run_command}} executes the command and waits for it to terminate; it doesn't redirect any of the standard streams.
* {{pyapi|script|script.core|read_command}} executes the command with stdout redirected to a pipe, and reads everything written to it. Once the command terminates, it returns the data written to stdout as a string.

'''How to retrieve error messages from ''read_command()'':'''

None of the existing *_command functions redirect stderr. You can do so with e.g.:

<source lang="python">
def read2_command(*args, **kwargs):
kwargs['stdout'] = grass.PIPE
kwargs['stderr'] = grass.PIPE
ps = grass.start_command(*args, **kwargs)
return ps.communicate()
</source>

This behaves like <tt>read_command()</tt> except that it returns a tuple of (stdout, stderr) rather than just stdout.

=== Interface to copying maps (g.copy) ===

Copy a raster map (for vector, replace "rast" with "vect"):

<source lang="python">
grass.run_command('g.copy', rast = (input, output))
</source>

To generalize it, "datatype" is the form of grass data to copy (eg, rast, vect, etc)

<source lang="python">
grass.run_command('g.copy', **{datatype: (input, output)})
</source>

=== Interface to listing maps (g.list) ===

You may use the functions in [http://grass.osgeo.org/programming7/namespacepython_1_1script_1_1core.html python.script.core.mlist_grouped()]:

<source lang="python">
list_grouped('raster')['PERMANENT']
[..., 'lakes', ..., 'slope', ...
</source>

and

<source lang="python">
mlist_grouped('vector', pattern='*roads*')['PERMANENT']
['railroads', 'roadsmajor']
</source>

See also [[Python/pygrass#Sample_PyGRASS_scripts|Sample PyGRASS scripts]] for an alternative solution.

=== i.group with patterns as name for input ===

Imagery groups can be populated like this:

<source lang="python">
from grass.pygrass.gis import Mapset

run_command("i.group", group="mygroup", input=mset.glist("raster", pattern="mypattern_*"))
</source>

=== Percentage output for progress of computation ===

A) Within a Python script, the {{pyapi|script|script.core|percent}} module method wraps the <tt>g.message -p</tt> command.

B) If you call a GRASS command within the Python code, you have to parse the output by setting <tt>GRASS_MESSAGE_FORMAT=gui</tt> in the environment when running the command and read from the command's stderr; e.g.

<source lang="python">
import grass.script as grass
env = os.environ.copy()
env['GRASS_MESSAGE_FORMAT'] = 'gui'
p = grass.start_command(..., stderr = grass.PIPE, env = env)
# read from p.stderr
p.wait()
</source>

If you need to capture both stdout and stderr, you need to use threads, select, or non-blocking I/O to consume data from both streams as it is generated in order to avoid deadlock.

ALTERNATIVE:

Redirect both stdout and stderr to the same pipe (and hope that the normal output doesn't include anything which will be mistaken for progress/error/etc messages):

<source lang="python">
p = grass.start_command(..., stdout = grass.PIPE, stderr = grass.STDOUT, env = env)
</source>

=== NULL data management ===

How to analyse if there are only NULL cells in a map:

If a map contains only null cells, its minimum and maximum will be "NULL":

<source lang="bash">
$ r.mapcalc 'foo = null()'
$ r.info -r foo
min=NULL
max=NULL
</source>

Using the Python API, The 'min' and 'max' values in the result of the {{pyapi|script|script.raster|raster_info}} function will be <tt>None</tt>.

=== Counting cells ===

Counting cells is far more expensive than simply determining whether
there are any non-null cells. Counting cells requires reading the
entire map, while the {{cmd|r.info}} approach only needs to read the metadata
files.

If you do need to count cells, {{cmd|r.stats}} is likely to be more efficient than {{cmd|r.univar}}.

A count loop:

<source lang="python">
while grass.raster_info(inmap)['max'] is not None:
...
</source>

=== Display: overlayed map display with labels ===

Example: display a vector map and overlay its labels on top of the map.

If the environment contains the setting GRASS_PNG_READ=TRUE, d.* commands should overlay their output on an existing image (otherwise the first command creates the file map.png but the second command overwrites the file with only the labels). So the following should work:

<source lang="python">
grass.run_command('d.vect', map='my_shape')
env = os.environ.copy()
env['GRASS_PNG_READ'] = 'TRUE'
grass.run_command('d.labels', labels='my_shape_labels', env = env)
</source>

=== Path to GISDBASE ===
In order to a avoid hardcoded paths to GRASS mapset files like the SQLite DB file, you can get the GISDBASE variable from the environment:
<source lang="python">
import grass.script as grass
import os.path

env = grass.gisenv()

gisdbase = env['GISDBASE']
location = env['LOCATION_NAME']
mapset = env['MAPSET']

path = os.path.join(gisdbase, location, mapset, 'sqlite.db')
</source>

=== Creating a new location ===

Use {{pyapi|script|script.core|create_location}} to create a new location.

=== Use Python reserved keyword ===

'''Q:''' ''r.resamp.bspline'' uses 'lambda' as a command line parameter name, but when you try to use it with {{pyapi|script|script.core|run_command}} or {{pyapi|script|script.core|start_command}} you get an error as lambda is a python reserved keyword. How to work around that?

'''A:''' Append an underscore to the name, i.e.:

<source lang="python">
grass.run_command('r.resamp.bspline', lambda_ = ...)
</source>

Note that this follows Python [http://legacy.python.org/dev/peps/pep-0008/#descriptive-naming-styles PEP8] style guide. In GRASS GIS version 6, you have to prepend the underscore.

=== Controlling the PNG display driver ===

Code fragment to control the {{cmd|pngdriver}} in Python:

<source lang="python">
import os
import sys
from grass.script import core as grass
def main():
os.environ['GRASS_PNGFILE'] = filename
os.environ['GRASS_WIDTH'] = str(width)
os.environ['GRASS_HEIGHT'] = str(height)
grass.run_command('d.his', i='elevation_shade', h='elevation')
</source>

=== Sophisticated cleanup procedure ===

Scripts which create several temporary files need a more sophisticated cleanup procedure which deletes all the tmp maps which have been created. This procedure should also work if the script stops (e.g due to an error).

Solution: Define a list of map names which starts out empty and has names appended to it as the names are generated. Code fragment:

<source lang="python">
import atexit, sys
import grass.script as grass

tmp_rast = []

def cleanup():
for rast in tmp_rast:
grass.run_command("g.remove",
rast = rast,
quiet = True)

def main():
...
while ...:
next_rast = ...
tmp_rast.append(next_rast)
...

if __name__ == "__main__":
options, flags = grass.parser()
atexit.register(cleanup)
sys.exit(main())
</source>

=== Using temporary region for computations ===

There are two possible ways how to define temporary region for raster-based computations within your scripts. First method uses environmental variable WIND_OVERRIDE, the second GRASS_REGION, see {{cmd|variables|desc=GRASS variables}} for more info. The key point is to recover the current region when the script is finished or terminated.

* ''First method'' (WIND_OVERRIDE) is implemented as {{pyapi|script|script.core|use_temp_region}}

<source lang=python>
import grass.script as grass

# store the current region settings and installs an atexit
# handler to recover the current region on script termination
grass.use_temp_region()

grass.run_command('g.region', region='detail')

grass.mapcalc('map = 1', overwrite=True)

# after making operations using the temporary region,
# to unset the temporary WIND_OVERRIDE file and remove any
# region named by it, it is possible to use del_temp_region
grass.del_temp_region()
</source>

* ''Second method'' (GRASS_REGION) doesn't store current region settings to any temporary region, it just defines GRASS_REGION which forces GIS Library to use this settings for raster-based computations instead of the settings stored in WIND file (ie. current region). See {{pyapi|script|script.core|region_env}}.

<source lang=python>
import os
import grass.script as grass

# copy environment and define GRASS_REGION environmental variable
# same as `g.region region=detail`
env = os.environ.copy()
env['GRASS_REGION'] = grass.region_env(region='detail')

grass.mapcalc('map = 1', overwrite=True, env=env)
</source>

== Direct Access from wxGUI ==

[[wxGUI]] Layer Manager in GRASS GIS comes with "Python shell" which enables users to type and execute python commands directly in wxGUI environment.

[[Image:wxgui-pyshell.png|center|400px|Embedded interactive Python Shell in wxGUI Layer Manager]]

== See also ==

* [[GRASS GIS Jupyter notebooks]]
* [[Working with GRASS without starting it explicitly‎]]
* Many more tutorials under [[:Category:Python]]

GRASS Python Scripting Library

2018-04-23T10:15:46Z

⚠️Sbl: update cleanup to new g.remove

{{Python}}
Python API documentation:

* [http://grass.osgeo.org/grass70/manuals/libpython/ Python API for GRASS GIS 7] and [http://grass.osgeo.org/grass70/manuals/libpython/script_intro.html Python Scripting Library]
* [http://grass.osgeo.org/programming6/pythonlib.html for GRASS GIS 6]: core.py, db.py, raster.py, vector.py, setup.py, array.py task.py

The GRASS Python Scripting Library can be imported by statement

<source lang=python>
import grass.script as gscript
</source>

The other packages such as PyGRASS can be imported in a similar way.

The code in {{src|lib/python/|lib/python}} provides <tt>grass.script</tt> and other packages in order to support GRASS scripts written in Python. The {{src|scripts}} directory of GRASS GIS 7 contains a series of examples actually provided to the end users (while the script in GRASS GIS 6 are shell scripts).

For more general info, see also [[GRASS and Python]] and see also [[Converting Bash scripts to Python]] if you have some Bash scripts you want to rewrite to Python.

== Uses for read, feed and pipe, start and exec commands ==

All of the <tt>*_command</tt> functions use {{pyapi|script|script.core|make_command}} to construct a command
line for a program which uses the {{cmd|g.parser|desc=GRASS parser}}. Most of them then pass
that command line to <tt>subprocess.Popen()</tt> via {{pyapi|script|script.core|start_command}}, except
for {{pyapi|script|script.core|exec_command}} which uses <tt>os.execvpe()</tt>.

[To be precise, they use <tt>grass.Popen()</tt>, which just calls
<tt>subprocess.Popen()</tt> with 'shell=True' on Windows and 'shell=False'
otherwise. On Windows, you need to use 'shell=True' to be able to
execute scripts (including batch files); 'shell=False' only works with
binary executables.]

{{pyapi|script|script.core|start_command}} separates the arguments into those which
<tt>subprocess.Popen()</tt> understands and the rest. The rest are passed to
<tt>make_command()</tt> to construct a command line which is passed as the
"args" parameter to <tt>subprocess.Popen()</tt>.

In other words, {{pyapi|script|script.core|start_command}} is a GRASS-oriented interface to
<tt>subprocess.Popen()</tt>. It should be suitable for any situation where you
would use <tt>subprocess.Popen()</tt> to execute a normal GRASS command (one
which uses the GRASS parser, which is almost all of them; the main
exception is {{cmd|r.mapcalc}} in 6.x).

Most of the others are convenience wrappers around <tt>start_command()</tt>, for common use cases.

* {{pyapi|script|script.core|run_command}} calls the wait() method on the process, so it doesn't return until the command has finished, and returns the command's exit code. Similar to <tt>system()</tt>.

* {{pyapi|script|script.core|pipe_command}} calls <tt>start_command()</tt> with 'stdout=PIPE' and returns the process object. You can use the process' .stdout member to read the command's stdout. Similar to popen(..., "r").

* {{pyapi|script|script.core|feed_command}} calls <tt>start_command()</tt> with stdin=PIPE and returns the process object. You can use the process' .stdin member to write to the command's stdout. Similar to popen(..., "w")

* {{pyapi|script|script.core|read_command}} calls <tt>pipe_command()</tt>, reads the data from the command's stdout, and returns it as a string. Similar to `backticks` in the shell.

* {{pyapi|script|script.core|write_command}} calls <tt>feed_command()</tt>, sends the string specified by the "stdin" argument to the command's stdin, waits for the command to finish and returns its exit code. Similar to "echo ... | command".

* {{pyapi|script|script.core|parse_command}} calls <tt>read_command()</tt> and parses its output as key-value pairs. Useful for obtaining information from {{cmd|g.region}}, {{cmd|g.proj}}, {{cmd|r.info}}, etc.

* {{pyapi|script|script.core|exec_command}} doesn't use <tt>start_command()</tt> but <tt>os.execvpe()</tt>. This causes the specified command to replace the current program (i.e. the Python script), so <tt>exec_command()</tt> never returns. Similar to bash's "exec" command. This can be useful if the script is a "wrapper" around a single command, where you construct the command line and execute the command as the final step. Notes: exec_command() is rarely appropriate. You probably want run_command() instead. On Windows, exec_command() will probably require the ".exe" suffix.

If you have any other questions, you might want to look at the code ({{src|lib/python/core.py}}). Most of these functions are only a few lines long.

=== Hints for parse_command() ===

To turn this command
g.rename rast=old_name,new_name
into a g.parse_command() call, you need to consider that it is a function call with three arguments:
# "g.rename"
# rast=old_name
# new_name

The second argument is a keyword argument, the first and third are
positional (non-keyword) arguments. Python doesn't allow positional
arguments to follow keyword arguments; positional arguments come
first, keyword arguments last.

Given the context, it's safe to assume that you want to pass a pair of
map names as the value to the rast= option. This requires explicit
parentheses so that the comma is treated as forming a tuple rather
than as an argument separator:

g.parse_command("g.rename", rast=(old_name,new_name))

The parentheses in a tuple value can only be omitted if it doesn't
result in the comma being ambiguous (as is the case in a function
call).

== Interfacing ==

=== Interfacing with NumPy ===

The {{pyapi|script|script.array|array}} module defines a <code>class array</code> which is a subclass of [http://docs.scipy.org/doc/numpy/reference/generated/numpy.memmap.html numpy.memmap] with <code>.read()</code> and <code>.write()</code> methods to read/write the underlying file via {{cmd|r.out.bin}}/{{cmd|r.in.bin}}. Metadata can be read with {{pyapi|script|script.raster|raster_info}}:

Example:

<source lang="python">
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

# read map
a = garray.array()
a.read(map)

# get raster map info
print grass.raster_info(map)['datatype']
i = grass.raster_info(map)

# get computational region info
c = grass.region()
print "rows: %d" % c['rows']
print "cols: %d" % c['cols']

# new array for result
b = garray.array()
# calculate new map from input map and store as GRASS raster map
b[...] = (a / 50).astype(int) * 50
b.write("elev.50m")
</source>

The size of the array is taken from the current region ([[computational region]]).

The main drawback of using numpy is that you're limited by available
memory. Using a subclass of <code>numpy.memmap</code> lets you use files which may
be much larger, but processing the entire array in one go is likely to
produce in-memory results of a similar size.

'''NULL (no data) management:'''

For integer maps, the NULL value is -2^31 = -2147483648. For floating-point maps, the NULL value is NaN. Note that the null= parameter for read() and write() specifies the value in the numpy array which is mapped to/from null values in the GRASS raster map.

If you're using floating-point numpy arrays, then use (Note: This assumes that atof() and sscanf("%lf") recognise "nan"; this is the case on Linux, but doesn't appear to work on Windows)
null=numpy.nan

For integer arrays, using
null=-2147483648
will ensure that valid values don't collide with NYLLs.

'''MASK support:'''

The function grass.script.array.read() and ...write() use r.out.bin and r.in.bin respectively. r.out.bin respects the MASK.

=== Interfacing with NumPy and SciPy ===

[http://docs.scipy.org/doc/scipy/reference/index.html SciPy] offers simple access to complex calculations. Example:

<source lang="python">
from scipy import stats
import grass.script as grass
import grass.script.array as garray

def main():
map = "elevation.dem"

x = garray.array()
x.read(map)

# Descriptive Statistics:
print "max, min, mean, var:"
print x.max(), x.min(), x.mean(), x.var()
print "Skewness test: z-score and 2-sided p-value:"
print stats.skewtest(stats.skew(x))
</source>

=== Interfacing with NumPy, SciPy and Matlab ===

One may also use the SciPy - Matlab interface:

r.out.mat input=elevation output=elev.mat

<source lang="python">
### PY ###
import scipy.io as sio
# load data
elev = sio.loadmat('elev.mat')
# retrive the actual array. the data set contains also the spatial reference
elev.get('map_data')
data = elev.get('map_data')
# a first simple plot
import pylab
pylab.plot(data)
pylab.show()
# the contour plot
pylab.contour(data)
# obviously data needs to ne reversed
import numpy as np
data_rev = data[::-1]
pylab.contour(data_rev)
# => this is a quick plot. basemap mapping may provide a nicer map!
#######
</source>

== Usage Examples ==

=== Display example ===
Example of Python script, which is processed by {{cmd|g.parser}}:

<source lang="python">
#!/usr/bin/env python
#
############################################################################
#
# MODULE: d.shadedmap
# AUTHOR(S): Unknown; updated to GRASS 5.7 by Michael Barton
# Converted to Python by Glynn Clements
# PURPOSE: Uses d.his to drape a color raster over a shaded relief map
# COPYRIGHT: (C) 2004,2008,2009 by the GRASS Development Team
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################

#%Module
#% description: Drapes a color raster over a shaded relief map using d.his
#% keyword: display
#% keyword: raster
#%End
#%option
#% key: reliefmap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of shaded relief or aspect map
#% required : yes
#%end
#%option
#% key: drapemap
#% type: string
#% gisprompt: old,cell,raster
#% description: Name of raster to drape over relief map
#% required : yes
#%end
#%option
#% key: brighten
#% type: integer
#% description: Percent to brighten
#% options: -99-99
#% answer: 0
#%end

import sys
from grass.script import core as grass

def main():
drape_map = options['drapemap']
relief_map = options['reliefmap']
brighten = options['brighten']
ret = grass.run_command("d.his", h_map = drape_map, i_map = relief_map, brighten = brighten)
sys.exit(ret)

if __name__ == "__main__":
options, flags = grass.parser()
main()

</source>

=== Parsing the options and flags ===

{{pyapi|script|script.core|parser}} is an interface to {{cmd|g.parser}}, and allows to parse the ''options'' and ''flags'' passed to your script on the command line. It is to be called at the top-level:

<source lang="python">
if __name__ == "__main__":
options, flags = grass.parser()
main()
</source>

Global variables "options" and "flags" are Python dictionaries containing the options/flags values, keyed by lower-case option/flag names. The values in "options" are strings, those in "flags" are Python booleans. All those variables have to be previously declared in the header of your script.

<source lang="python">
>>> options, flags = grass.parser()
>>> options
{'input': 'my_map', 'output': 'map_out', 'option1': '21.472', 'option2': ''}
>>> flags
{'c': True, 'm': False}
</source>

'''Passing several floats to a single option:'''

Example:
<source lang="bash">
python my.module.py input=input output=output myoption=0.1,0.2,0.5
</source>

The values in the "options" dictionary returned from the parser()
function are always strings. You can parse the string with:

<source lang="python">
myoption = map(float, options['myoption'].split(','))
</source>

The option definition in the script should have:

<source lang="python">
#% type: double
#% multiple: yes
</source>

This allows g.parser to validate the option syntax, so you can rely
upon the string being in the correct format. If the values have a
fixed range, you can use e.g.:

<source lang="python">
#% options: 0.0-1.0
</source>

to have the parser check that the values fall within the range.

For more information on option definitions, see:

http://grass.osgeo.org/programming7/gislib.html#Complete_Structure_Members_Table

=== Example for embedding r.mapcalc (map algebra) ===

{{pyapi|script|script.raster|mapcalc}} accepts a template string followed by keyword
arguments for the substitutions, e.g. (code snippets):

<source lang="python">
grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = options['output'],
rast1 = options['raster1'],
rast2 = options['raster2'])
</source>

''Best practice'': first copy all of the options[] into separate variables at the beginning of main(), i.e.:

<source lang="python">
def main():
output = options['output']
raster1 = options['raster1']
raster2 = options['raster2']

...

grass.mapcalc("${out} = ${rast1} + ${rast2}",
out = output,
rast1 = raster1,
rast2 = raster2)
</source>

Performing multiple computations using <tt>grass.script.raster.mapcalc()</tt>:
<source lang="python">
expr = ";".join([
"$out.r = r#$first * $frac + (1.0 - $frac) * r#$second",
"$out.g = g#$first * $frac + (1.0 - $frac) * g#$second",
"$out.b = b#$first * $frac + (1.0 - $frac) * b#$second"])
grass.mapcalc(expr, out=out, first=first, second=second, frac=percent/100.0)
</source>

Hint: multi-line strings can be separated by using a semicolon instead of a newline.

=== Looping over file names stored in an ASCII file ===

When looping over file names stored in an ASCII file and getting the error

WARNING: Illegal filename <map.f1jan.05216.something
>. Character <
> not allowed.

then the line terminators may be the reason.
When you iterate over a file, the strings include the line terminators (e.g. '\n' or '\r\n'). Use e.g.

<source lang="python">
for line in gl:
renamed = line.rstrip().replace('.','_')
...
</source>

to remove any trailing whitespace (including newlines) from each line.

=== Example for parsing raster category labels ===

How to obtain the text labels
<source lang="python">
# dump cats to file to avoid "too many argument" problem:
p = grass.pipe_command('r.category', map = rastertmp, separator = ';', quiet = True)
cats = []
for line in p.stdout:
cats.append(line.rstrip('\r\n').split(';')[0])
p.wait()

number = len(cats)
if number < 1:
grass.fatal(_("No categories found in raster map"))
</source>

=== Example for parsing category numbers ===

'''Q:''' How to obtain the number of cells of a certain category?

'''A:''' It is recommended to use {{pyapi|script|script.core|pipe_command}} and parse the output, e.g.:

<source lang="python">
p = grass.pipe_command('r.stats',flags='c',input='map')
result = {}
for line in p.stdout:
val,count = line.strip().split()
result[int(val)] = int(count)
p.wait()
</source>

=== Example for parsing the region output of a module ===

Some of the GRASS GIS modules are delivering region information (e.g. {{cmd|r.in.xyz}} which scans a LiDAR file for the extent of the point cloud). The retrieved region settings (using '''-g''' flag for script style output) can be parsed in Python:

<source lang="python">
import os
from grass.script import core as gcore

from grass.pygrass.modules.shortcuts import general as g
from grass.pygrass.modules.shortcuts import raster as r

# scan a LiDAR xyz point file for its extent
compregion = gcore.parse_command("r.in.xyz", input="tmp.xyz", separator="space", flags="sg", output="bbox",
parse=(gcore.parse_key_val, {'sep': '=', 'vsep': ' '}))
print(compregion)
# set computational region from LiDAR extent
# hint: we turn here the dictionary to a region by unpacking the dictionary:
g.region(res="1", flags="p", **compregion)
</source>

Note the two '''*''' above which unpack the dictionary (see also the related [https://docs.python.org/2/tutorial/controlflow.html#keyword-arguments Python manual] page).

=== Example for getting the region's number of rows and columns ===

'''Q:''' How to obtain the number of rows and columns of the current region?

'''A:''' It is recommended to use the {{pyapi|script|script.core|region}} function which will create a dictionary with values for extents and resolution, e.g.:

<source lang="python">
#!/usr/bin/env python
#-*- coding:utf-8 -*-
#
############################################################################
#
# MODULE: g.region.resolution
# AUTHOR(S): based on a post at GRASS-USER mailing list [1]
# PURPOSE: Parses "g.region -g", prints out number of rows, cols
# COPYLEFT: ;-)
# COMMENT: ...a lot of comments to be easy-to-read for/by beginners
#
#############################################################################
#
#%Module
#% description: Print number of rows, cols of current geographic region
#% keyword: region
#%end

# importing required modules
import sys # the sys module [2]
from grass.script import core as grass # the core module [3]

# information about imported modules can be obtained using the dir() function
# e.g.: dir(sys)

# define the "main" function: get number of rows, cols of region
def main():

# #######################################################################
# the following commented code works but is kept only for learning purposes

## assigning the output of the command "g.region -g" in a string called "return_rows_x_cols"
# return_rows_x_cols = grass.read_command('g.region', flags = 'g')

## parsing arguments of interest (rows, cols) in a dictionary named "rows_x_cols"
# rows_x_cols = grass.parse_key_val(return_rows_x_cols)

## selectively print rows, cols from the dictionary "rows_x_cols"
# print 'rows=%d \ncols=%d' % (int(rows_x_cols['rows']), int(rows_x_cols['cols']))

# #######################################################################

# faster/ easier way: use of the "grass.region()" function
gregion = grass.region()
rows = gregion['rows']
cols = gregion['cols']

# print rows, cols properly formated
print 'rows=%d \ncols=%d' % (rows, cols)

# this "if" condition instructs execution of code contained in this script, *only* if the script is being executed directly
if __name__ == "__main__": # this allows the script to be used as a module in other scripts or as a standalone script
options, flags = grass.parser() #
sys.exit(main()) #

# Links
# [1] http://n2.nabble.com/Getting-rows-cols-of-a-region-in-a-script-tp2787474p2787509.html
# [2] http://www.python.org/doc/2.5.2/lib/module-sys.html
# [3] https://grass.osgeo.org/grass75/manuals/libpython
</source>

=== Managing mapsets ===

To check if a certain mapset exists in the active location, use {{pyapi|script|script.core|mapsets}}

<source lang="python">
grass.mapsets(False)
</source>

... returns a list of mapsets in the current location.

=== r.mapcalc example ===

Example of Python script, which is processed by {{cmd|g.parser}}:

The shell script line:

<source lang="bash">
r.mapcalc "MASK = if(($cloudResampName < 0.01000),1,null())"
</source>

would be written like this:

<source lang="python">
import grass.script as grass

...

grass.mapcalc("MASK=if(($cloudResampName < 0.01000),1,null())",
cloudResampName = cloudResampName)
</source>

The first argument to the mapcalc function is a template (see the Python library documentation for [http://docs.python.org/library/string.html string.Template]). Any keyword arguments (other than <tt>quiet</tt>, <tt>verbose</tt> or <tt>overwrite</tt>) specify substitutions.

=== r.mapcalc example: defining a moving window ===

Moving window of 4 cell in every 8 direction and do a boolean comparison. Boolean value (e.g. the result of a comparison) is an integer, with 1 for true, 0 for false.
Then do a r.mapcalc calculation with the moving window.

<source lang="python">

import grass.script as grass

# define a moving window of 4 cell in every 8 direction
#
# map[4,4] map[4,0] map[4,-4]
# map[3,3] map[3,0] map[3,-3]
# map[2,2] map[2,0] map[2,-2]
# map[1,1] map[1,0] map[1,-1]
# map[0,4] map[0,3] map[0,2] map[0,1] x map[0,-1] map[0,-2] map[0,-3] map[0,-4]
# map[-1,1] map[-1,0] map[-1,-1]
# map[-2,2] map[-2,0] map[-2,-2]
# map[-3,3] map[-3,0] map[-3,-3]
# map[-4,4] map[-4,0] map[-4,-4]

# define the offet duplets

offsets = [d
for j in xrange(1,4+1)
for i in [j,-j]
for d in [(i,0),(0,i),(i,i),(i,-i)]]

# >>>offsets
# [(1, 0), (0, 1), (1, 1), (1, -1), (-1, 0), (0, -1), (-1, -1), (-1, 1), (2, 0), (0, 2), (2, 2), (2, -2), (-2, 0), (0, -2), \
# (-2, -2), (-2, 2), (3, 0), (0, 3), (3, 3), (3, -3), (-3, 0), (0, -3), (-3, -3), (-3, 3), (4, 0), (0, 4), (4, 4), (4, -4), \
# (-4, 0), (0, -4), (-4, -4), (-4, 4)]

# define the calculation term

terms = ["(myelevnc[%d,%d] < myelevnc)" % d
for d in offsets]

# >>>terms
# ['(myelevnc[1,0] < myelevnc)', '(myelevnc[0,1] < myelevnc)', '(myelevnc[1,1] < myelevnc)', '(myelevnc[1,-1] < myelevnc)', \
# '(myelevnc[-1,0] < myelevnc)', '(myelevnc[0,-1] < myelevnc)', '(myelevnc[-1,-1] < myelevnc)', '(myelevnc[-1,1] < myelevnc)',\
# '(myelevnc[2,0] < myelevnc)', '(myelevnc[0,2] < myelevnc)', '(myelevnc[2,2] < myelevnc)', '(myelevnc[2,-2] < myelevnc)', \
# '(myelevnc[-2,0] < myelevnc)', '(myelevnc[0,-2] < myelevnc)', '(myelevnc[-2,-2] < myelevnc)', '(myelevnc[-2,2] < myelevnc)', \
# '(myelevnc[3,0] < myelevnc)', '(myelevnc[0,3] < myelevnc)', '(myelevnc[3,3] < myelevnc)', '(myelevnc[3,-3] < myelevnc)', \
# '(myelevnc[-3,0] < myelevnc)', '(myelevnc[0,-3] < myelevnc)', '(myelevnc[-3,-3] < myelevnc)', '(myelevnc[-3,3] < myelevnc)', \
# '(myelevnc[4,0] < myelevnc)', '(myelevnc[0,4] < myelevnc)', '(myelevnc[4,4] < myelevnc)', '(myelevnc[4,-4] < myelevnc)', \
# '(myelevnc[-4,0] < myelevnc)', '(myelevnc[0,-4] < myelevnc)', '(myelevnc[-4,-4] < myelevnc)', '(myelevnc[-4,4] < myelevnc)']

# define the calculation expression

expr = "elevation_percentile4 = (100.0 / 48.0) * (%s)" % " + ".join(terms)

# >>>expr
# elevation_percentile4 = (100.0 / 48.0) * ((myelevnc[1,0] < myelevnc) + (myelevnc[0,1] < myelevnc) + (myelevnc[1,1] < myelevnc) + \
# (myelevnc[1,-1] < myelevnc) + (myelevnc[-1,0] < myelevnc) + (myelevnc[0,-1] < myelevnc) + (myelevnc[-1,-1] < myelevnc) + \
# (myelevnc[-1,1] < myelevnc) + (myelevnc[2,0] < myelevnc) + (myelevnc[0,2] < myelevnc) + (myelevnc[2,2] < myelevnc) + \
# (myelevnc[2,-2] < myelevnc) + (myelevnc[-2,0] < myelevnc) + (myelevnc[0,-2] < myelevnc) + (myelevnc[-2,-2] < myelevnc) + \
# (myelevnc[-2,2] < myelevnc) + (myelevnc[3,0] < myelevnc) + (myelevnc[0,3] < myelevnc) + (myelevnc[3,3] < myelevnc) + \
# (myelevnc[3,-3] < myelevnc) + (myelevnc[-3,0] < myelevnc) + (myelevnc[0,-3] < myelevnc) + (myelevnc[-3,-3] < myelevnc) + \
# (myelevnc[-3,3] < myelevnc) + (myelevnc[4,0] < myelevnc) + (myelevnc[0,4] < myelevnc) + (myelevnc[4,4] < myelevnc) + \
# (myelevnc[4,-4] < myelevnc) + (myelevnc[-4,0] < myelevnc) + (myelevnc[0,-4] < myelevnc) + (myelevnc[-4,-4] < myelevnc)\
# + (myelevnc[-4,4] < myelevnc))

# do the r.mapcalc calculation with the moving window

grass.mapcalc( expr )

</source>

=== Using output from GRASS modules in the script ===

Sometimes you need to use the output of a module for the next step. There are dedicated functions to obtain the result of, for example, a statistical analysis.

Example: get the range of a raster map and use it in {{cmd|r.mapcalc}}. Here you can use {{pyapi|script|script.raster|raster_info}}, e.g.:

<source lang="python">
import grass.script as grass

max = grass.raster_info(inmap)['max']
grass.mapcalc("$outmap = $inmap / $max",
inmap = inmap, outmap = outmap, max = max)
</source>

=== Using output from r.what ===

''Q: How does one return attribute values from a call to the 'r.what' module running in a python script?''

A: If you use <tt>grass.script.raster_what()</tt>, it returns a list of dictionaries.

PyGRASS which requires you to add <tt>stdout_=PIPE</tt>, then you can get the output as a string from <tt>module.outputs.stdout</tt>.

Or using directly the C API through python with (North Carolina dataset example):

<source lang="python">
from grass.pygrass.vector import VectorTopo
from grass.pygrass.raster import RasterRow
from grass.pygrass.gis.region import Region

with RasterRow('elevation', mode='r') as rast:
with VectorTopo('hospitals', mode='r') as hospitals:
region = Region()
for hosp in hospitals:
value = rast.get_value(hosp, region)
if value is not None:
print(hosp.cat, value)
</source>

=== Calling a GRASS module in Python ===

Imagine, you wanted to execute this command in Python:
<source lang="bash">
r.profile -g input=mymap output=newfile profile=12244.256,-295112.597,12128.012,-295293.77
</source>

All arguments except the first (which is a flag) are keyword arguments, i.e. <tt>arg = val</tt>. For the flag, use <tt>flags = 'g'</tt> (note that "-g" would be the negative of a Python variable named "g"!). So:

<source lang="python">
grass.run_command('r.profile',
input = input_map,
output = output_file,
profile = [12244.256,-295112.597,12128.012,-295293.77]
</source>
or:
<source lang="python">
profile = [(12244.256,-295112.597),(12128.012,-295293.77)]
</source>

i.e. you need to provide the keyword, and the argument must be a valid Python expression. Function <code>run_command()</code> etc accept lists and tuples.

'''What is the proper way to include keyword-arguments tuples?'''

For example, "g.list -f type=rast,vect" translates into:
<source lang="python">
grass.run_command("g.list", flags="f", type="rast,vect")
</source>
or:
<source lang="python">
grass.run_command("g.list", flags="f", type=["rast","vect"])
</source>

The various *_command() functions accept arbitrary keyword arguments. Any keywords which don't have a specific meaning to either the *_command() function or the Popen constructor are treated as arguments to the GRASS module.

'''What is the proper way to use multiple flags?'''

How can I call a module with multiple flags set (e.g., -a and -b) in GRASS-Python?

flags = "ab"

Example:
<source lang="python">
grass.run_command("r.info", flags="eg", map=["elevation"])
</source>

'''Differences between ''run_command()'' and ''read_command()'':'''

* {{pyapi|script|script.core|run_command}} executes the command and waits for it to terminate; it doesn't redirect any of the standard streams.
* {{pyapi|script|script.core|read_command}} executes the command with stdout redirected to a pipe, and reads everything written to it. Once the command terminates, it returns the data written to stdout as a string.

'''How to retrieve error messages from ''read_command()'':'''

None of the existing *_command functions redirect stderr. You can do so with e.g.:

<source lang="python">
def read2_command(*args, **kwargs):
kwargs['stdout'] = grass.PIPE
kwargs['stderr'] = grass.PIPE
ps = grass.start_command(*args, **kwargs)
return ps.communicate()
</source>

This behaves like <tt>read_command()</tt> except that it returns a tuple of (stdout, stderr) rather than just stdout.

=== Interface to copying maps (g.copy) ===

Copy a raster map (for vector, replace "rast" with "vect"):

<source lang="python">
grass.run_command('g.copy', rast = (input, output))
</source>

To generalize it, "datatype" is the form of grass data to copy (eg, rast, vect, etc)

<source lang="python">
grass.run_command('g.copy', **{datatype: (input, output)})
</source>

=== Interface to listing maps (g.list) ===

You may use the functions in [http://grass.osgeo.org/programming7/namespacepython_1_1script_1_1core.html python.script.core.mlist_grouped()]:

<source lang="python">
list_grouped('raster')['PERMANENT']
[..., 'lakes', ..., 'slope', ...
</source>

and

<source lang="python">
mlist_grouped('vector', pattern='*roads*')['PERMANENT']
['railroads', 'roadsmajor']
</source>

See also [[Python/pygrass#Sample_PyGRASS_scripts|Sample PyGRASS scripts]] for an alternative solution.

=== i.group with patterns as name for input ===

Imagery groups can be populated like this:

<source lang="python">
from grass.pygrass.gis import Mapset

run_command("i.group", group="mygroup", input=mset.glist("raster", pattern="mypattern_*"))
</source>

=== Percentage output for progress of computation ===

A) Within a Python script, the {{pyapi|script|script.core|percent}} module method wraps the <tt>g.message -p</tt> command.

B) If you call a GRASS command within the Python code, you have to parse the output by setting <tt>GRASS_MESSAGE_FORMAT=gui</tt> in the environment when running the command and read from the command's stderr; e.g.

<source lang="python">
import grass.script as grass
env = os.environ.copy()
env['GRASS_MESSAGE_FORMAT'] = 'gui'
p = grass.start_command(..., stderr = grass.PIPE, env = env)
# read from p.stderr
p.wait()
</source>

If you need to capture both stdout and stderr, you need to use threads, select, or non-blocking I/O to consume data from both streams as it is generated in order to avoid deadlock.

ALTERNATIVE:

Redirect both stdout and stderr to the same pipe (and hope that the normal output doesn't include anything which will be mistaken for progress/error/etc messages):

<source lang="python">
p = grass.start_command(..., stdout = grass.PIPE, stderr = grass.STDOUT, env = env)
</source>

=== NULL data management ===

How to analyse if there are only NULL cells in a map:

If a map contains only null cells, its minimum and maximum will be "NULL":

<source lang="bash">
$ r.mapcalc 'foo = null()'
$ r.info -r foo
min=NULL
max=NULL
</source>

Using the Python API, The 'min' and 'max' values in the result of the {{pyapi|script|script.raster|raster_info}} function will be <tt>None</tt>.

=== Counting cells ===

Counting cells is far more expensive than simply determining whether
there are any non-null cells. Counting cells requires reading the
entire map, while the {{cmd|r.info}} approach only needs to read the metadata
files.

If you do need to count cells, {{cmd|r.stats}} is likely to be more efficient than {{cmd|r.univar}}.

A count loop:

<source lang="python">
while grass.raster_info(inmap)['max'] is not None:
...
</source>

=== Display: overlayed map display with labels ===

Example: display a vector map and overlay its labels on top of the map.

If the environment contains the setting GRASS_PNG_READ=TRUE, d.* commands should overlay their output on an existing image (otherwise the first command creates the file map.png but the second command overwrites the file with only the labels). So the following should work:

<source lang="python">
grass.run_command('d.vect', map='my_shape')
env = os.environ.copy()
env['GRASS_PNG_READ'] = 'TRUE'
grass.run_command('d.labels', labels='my_shape_labels', env = env)
</source>

=== Path to GISDBASE ===
In order to a avoid hardcoded paths to GRASS mapset files like the SQLite DB file, you can get the GISDBASE variable from the environment:
<source lang="python">
import grass.script as grass
import os.path

env = grass.gisenv()

gisdbase = env['GISDBASE']
location = env['LOCATION_NAME']
mapset = env['MAPSET']

path = os.path.join(gisdbase, location, mapset, 'sqlite.db')
</source>

=== Creating a new location ===

Use {{pyapi|script|script.core|create_location}} to create a new location.

=== Use Python reserved keyword ===

'''Q:''' ''r.resamp.bspline'' uses 'lambda' as a command line parameter name, but when you try to use it with {{pyapi|script|script.core|run_command}} or {{pyapi|script|script.core|start_command}} you get an error as lambda is a python reserved keyword. How to work around that?

'''A:''' Append an underscore to the name, i.e.:

<source lang="python">
grass.run_command('r.resamp.bspline', lambda_ = ...)
</source>

Note that this follows Python [http://legacy.python.org/dev/peps/pep-0008/#descriptive-naming-styles PEP8] style guide. In GRASS GIS version 6, you have to prepend the underscore.

=== Controlling the PNG display driver ===

Code fragment to control the {{cmd|pngdriver}} in Python:

<source lang="python">
import os
import sys
from grass.script import core as grass
def main():
os.environ['GRASS_PNGFILE'] = filename
os.environ['GRASS_WIDTH'] = str(width)
os.environ['GRASS_HEIGHT'] = str(height)
grass.run_command('d.his', i='elevation_shade', h='elevation')
</source>

=== Sophisticated cleanup procedure ===

Scripts which create several temporary files need a more sophisticated cleanup procedure which deletes all the tmp maps which have been created. This procedure should also work if the script stops (e.g due to an error).

Solution: Define a list of map names which starts out empty and has names appended to it as the names are generated. Code fragment:

<source lang="python">
import atexit, sys
import grass.script as grass

tmp_rast = []

def cleanup():
for rast in tmp_rast:
grass.run_command("g.remove",
flags='f',
type= 'raster',
name = rast,
quiet = True)

def main():
...
while ...:
next_rast = ...
tmp_rast.append(next_rast)
...

if __name__ == "__main__":
options, flags = grass.parser()
atexit.register(cleanup)
sys.exit(main())
</source>

=== Using temporary region for computations ===

There are two possible ways how to define temporary region for raster-based computations within your scripts. First method uses environmental variable WIND_OVERRIDE, the second GRASS_REGION, see {{cmd|variables|desc=GRASS variables}} for more info. The key point is to recover the current region when the script is finished or terminated.

* ''First method'' (WIND_OVERRIDE) is implemented as {{pyapi|script|script.core|use_temp_region}}

<source lang=python>
import grass.script as grass

# store the current region settings and installs an atexit
# handler to recover the current region on script termination
grass.use_temp_region()

grass.run_command('g.region', region='detail')

grass.mapcalc('map = 1', overwrite=True)

# after making operations using the temporary region,
# to unset the temporary WIND_OVERRIDE file and remove any
# region named by it, it is possible to use del_temp_region
grass.del_temp_region()
</source>

* ''Second method'' (GRASS_REGION) doesn't store current region settings to any temporary region, it just defines GRASS_REGION which forces GIS Library to use this settings for raster-based computations instead of the settings stored in WIND file (ie. current region). See {{pyapi|script|script.core|region_env}}.

<source lang=python>
import os
import grass.script as grass

# copy environment and define GRASS_REGION environmental variable
# same as `g.region region=detail`
env = os.environ.copy()
env['GRASS_REGION'] = grass.region_env(region='detail')

grass.mapcalc('map = 1', overwrite=True, env=env)
</source>

== Direct Access from wxGUI ==

[[wxGUI]] Layer Manager in GRASS GIS comes with "Python shell" which enables users to type and execute python commands directly in wxGUI environment.

[[Image:wxgui-pyshell.png|center|400px|Embedded interactive Python Shell in wxGUI Layer Manager]]

== See also ==

* [[GRASS GIS Jupyter notebooks]]
* [[Working with GRASS without starting it explicitly‎]]
* Many more tutorials under [[:Category:Python]]

Talk:GRASS Community Sprint Bonn 2018

2018-03-23T13:36:22Z

⚠️Sbl: Added stefan

= Participants and Reports =

== Martin Landa ==

* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=martinl&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* Show computation region extent settings, see {{trac|3519}}
* wxGUI/datacatalog: zoom to first added map (sync with lmgr behaviour)
* wxGUI/preferences: add new option for random colors (vector)
* Read EPSG codes with PROJ v.5 fails, see {{trac|3514}}
* wxGUI/datacatalog: display layer on double click
* disable to_text_string() in grass.py, see {{trac|3508}}
* rename r.sentinel -> i.sentinel (work in progress), see {{trac|3522}}
* v.random restrict wrong categories assigned, see {{trac|3524}}
* Currently G7:v.random with restrict parameter transfers categories {{trac|3528}}
* wxGUI: set up default map display properties when new display is open
* libgis: improve parser UI description error reporting
* v.to.rast: add support for centroids

== Moritz Lennert ==

* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=mlennert&milestone=on&ticket=on&changeset=on&wiki=on&update=Update SVN log] overview
* Committed fix for r.texture to avoid overwrite of existing output maps
* Committed fox for i.segment.uspo to avoid zero division error
* Worked on and discussed new startup mockup, created [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup wiki page] for brainstorming
* Use of '_' in i.zc module parameter in i.cutlines to enable parallelization of i.zc. Thanks to Pietro for making this possible in pygrass.
* Some testing for [https://trac.osgeo.org/grass/ticket/3361 #3361] on slowness of v.select with GEOS. Added explanation to man page to clarify that GRASS' "overlap' = GEOS 'intersects'.
* Testing Ondrej' artificial neural networks modules + discussions on further improvements
* Discussion of new website design
* Discussion on move to github.

== Markus Neteler ==

* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=neteler&milestone=on&ticket=on&changeset=on&wiki=on&update=Update%20SVN%20log SVN log] overview
* set up [https://docs.google.com/spreadsheets/d/1BgFMiYlLosFjsVUlUCWwssoxiQB_G7gpkVFgG29gZBM/edit?usp=sharing Budget] for this community sprint
* testing of {{AddonCmd|i.nightlights.intercalibration}} with DMSP-OLS data, parser fix (contributed by Anika Bettge) and HTML fixes
* Web: activation of roles in http://staging.grass.osgeo.org/
* svn to git migration discussions
** Following https://trac.osgeo.org/gdal/wiki/rfc71_github_migration with interest
* Ticket {{trac|3527}} (i.atcorr: discrepancy in sensor band numbering in the manual)
* added "How to add keywords in code" submitting rules for [https://trac.osgeo.org/grass/wiki/Submitting/Python#Addingdescriptionandkeywords Python] and [https://trac.osgeo.org/grass/wiki/Submitting/C#Addingdescriptionandkeywords C]

== Veronica Andreo ==

* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=veroandreo&milestone=on&ticket=on&changeset=on&wiki=on&update=Update%20SVN%20log SVN log] overview
* tested {{cmd|r.texture}}
* committed {{cmd|i.atcorr}} manual example and figure contributed by Zofie Cimburova to perform atmospheric correction on Sentinel-2 bands
* performed general clean-up on i.atcorr manual page
* completed [https://grasswiki.osgeo.org/wiki/SENTINEL Sentinel wiki] (kinda). Editions, corrections and more examples are welcome.
* discussion about new flag and flag behavior for {{cmd|t.remove}} with Luca {{trac|3362}}
* revised and tested old t.* related tickets; closed some old ones as wontfix or worksforme accordingly.
* created patch for {{trac|3264}} with Luca's help
* tested -h flag in {{cmd|t.info}}, see {{trac|3322}}
* added example to {{cmd|t.register}} (contributed by Ondrej Pesek) + correction of typos and minor text edition
* tweeted and RT from GRASS account and posted in FB GRASS GIS group
* completed revision and clean-up of the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing Temporal data processing] wiki
* opened tickets for {{cmd|g.gui.tplot}} (after discussions with Nikos and Luca)
* tested {{trac|3223}} and {{trac|3302}}
* created draft roadmap of priorities for the migration of the web site: see [https://grasswiki.osgeo.org/wiki/GRASS-Wiki/CMS_migration_plan_2018 wiki]

== Ondřej Pešek ==

* Working on artificial neural network modules (see [https://github.com/ctu-geoforall-lab-projects/dp-pesek-2018/compare/master@%7B18/3/2018%7D...master github commits] overview)
* g.gui.gmodeler: Support parameterization and GUI generation in python script; export to PyWPS script (see [https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps/compare/master@%7B18/03/2018%7D...master github commits] overview)
* Working on SOS modules (see [https://github.com/pesekon2/GRASS-GIS-SOS-tools/compare/master@%7B17/03/2018%7D...master github commits] overview)

== Luca Delucchi ==

* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=lucadelu&milestone=on&ticket=on&changeset=on&wiki=on&update=Update%20SVN%20log SVN log] overview
* {{cmd|g.region}} improved grow option
* renamed r.modis addons to {{AddonCmd|i.modis}}
* working on temporal framework open tickets
* discussion about new flag and flag behavior for {{cmd|t.remove}} with Vero {{trac|3362}}
* created three new modules to work with signature files {{AddonCmd|i.signature.list}}, {{AddonCmd|i.signature.copy}}, {{AddonCmd|i.signature.remove}}
* worked with Markus Metz on {{cmd|i.ortho.transform}} command
* fixed some bug in {{cmd|g.gui.tplot}} {{rev|72485}} {{rev|72489}}, one related to {{trac|3294}}
* review GSoC proposals

== Nikos Alexandris ==

* Discussion about GRASS GIS, HPC and distributed file systems with Markus Neteler, Soeren Gebert, Markus Metz. Respective wiki pages to be updated.
* Tests related to https://trac.osgeo.org/grass/ticket/774 available at https://github.com/NikosAlexandris/test_color_space_conversions

== Stefan Blumentrath ==

* Made his first commit to trunk {{rev|72444}} and fixed {{trac|3322}}
* worked on an AddOn [https://trac.osgeo.org/grass/browser/sandbox/sbl/t.rast.aggregate.update/t.rast.aggregate.update.py t.rast.aggegate.update] for updating aggregated STRDS from t.rast.aggregate (please test)
* wrote a patch for improving performace of v.rast.stats that allows multiple input {{trac|3523}} (testing/feedback very welcome)
* [https://trac.osgeo.org/grass/timeline?from=Mar+25%2C+2018&daysback=7&authors=sbl&milestone=on&ticket=on&changeset=on&wiki=on&update=Update%20SVN%20log SVN log] overview

GRASS GIS Community Sprint Bonn 2018

2018-02-03T19:28:35Z

⚠️Sbl: Stefan arrival

{{toc|right}}

The '''GRASS GIS community''' will join the general '''OSGeo Code Sprint''' at BaseCamp in Bonn, following the annual FOSSGIS conference (German Speaking OSGeo Local Chapter conference in Bonn, Germany)

<center>
[[File:GRASS_GIS_Code_Sprint_2018.png|320px]]
</center>

== Timing, Venue ==

OSGeo Code Sprint: '''March 18 - 25, 2018 at BaseCamp. Bonn, Germany'''.

== Sponsors ==

Please check more info on the Bonn Code Sprint 2018 [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 here].

We also welcome direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.
This Bonn event is especially interesting since '''important OSGeo projects come together'''!

== Agenda - What we plan to do ==

=== Move to Git ===

* Choose among different options: OSGeo Git, Github, GitLab
* Participants are invited to study Git in advance :-)

=== New website ===

* Choose among different options: Wordpress, Sphinx, ... ?

=== Port wxGUI to wxPython 4 ===

* Finish porting wxGUI code to the new wxPython 4
* It also includes porting code to Python 3

=== Finish complete Python 3 support ===

* Includes also wxGUI support for wxPython 4
* ...

== Planned participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants <<--- important!

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Neteler|Markus Neteler]]
|Germany
|18.3.
|25.3.
|Migration to git discussion, GRASS GIS 8
|M
|
|-
|2
|[[User:Ychemin|Yann Chemin]]
|France
|18.3.
|25.3.
|ISIS-GRASS, Planetary projections, i.ortho.photo, bundle blocks, GRASS GIS 8
|XL
|
|-
|3
|[[User:Landa|Martin Landa]]
|Czech Republic
|18.3.
|25.3.
|Migration to git discussion, website discussion, GRASS GIS 8
|L
|
|-
|4
|Stefan Blumentrath
|Germany/Norway
|20.03.
|25.03.
|Flexible
|L
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina/Netherlands
|18.3
|??.??
|TGRASS, Documentation, website discussion
|S
|
|-
|6
|[[User:Lucadelu|Luca Delucchi]]
|Italy
|18.3
|??.??
|Migration to git discussion, TGRASS, testsuite, website discussion
|L
|
|-
|7
|[[User:Mlennert|Moritz Lennert]]
|Italy
|18.3
|21.3
|Migration to git discussion, website discussion, GRASS 8, new GRASS GIS startup, work on OBIA addons, ...
|M
|
|-
|8
|Markus Metz
|Germany
|18.3.
|22.3.
|Migration to git discussion, website discussion, GRASS 8, new GRASS GIS startup
|M
|
|-
|#
|...
|
|
|
|
|
|
|-
|}

=== Via IRC chat ===

(IRC is a nice archaic chat system, see [[IRC]])

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|Add
|your
|self..
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== Reports ==

See [[Talk:GRASS_Community_Sprint_Bonn_2018]]

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2018]]

SENTINEL

2018-01-29T11:26:27Z

⚠️Sbl: /* Import data */ Link Martins new addon

=Sentinel 2=

Sentinel-2 is an Earth observation mission developed by [https://en.wikipedia.org/wiki/European_Space_Agency ESA] as part of the [https://en.wikipedia.org/wiki/Copernicus_Programme Copernicus Programme] to perform terrestrial observations in support of services such as forest monitoring, land cover changes detection, and natural disaster management. It consists of two identical satellites, [https://en.wikipedia.org/wiki/Sentinel-2A Sentinel-2A] and [https://en.wikipedia.org/wiki/Sentinel-2B Sentinel-2B]. Details about the mission, user and technical guides as well as other documentation can be found at the ESA dedicated website [https://sentinel.esa.int/web/sentinel/missions/sentinel-2] and a number of other sites.

==Overview of Sentinel-2 mission capabilities==

Sentinel-2 mission has the following features:
* Multi-spectral data with ''13 bands'' in the visible, near infrared (NIR), and short wave infrared (SWIR).
* Systematic global coverage of land surfaces from 56° S to 84° N, coastal waters, and all of the Mediterranean Sea
* Revisiting every ''5 days'' under the same viewing angles. At high latitudes, Sentinel-2 swath overlaps and some regions are observed twice or more every 5 days, but with different viewing angles.
* Spatial resolutions of 10 m (Bands 2, 3, 4 and 8 - Blue, Green, Red and NIR), 20 m (Bands 5, 6 and 7 - Red Edge bands, Band 8A - Narrow infrared and Bands 11 and 12 - SWIR) and 60 m (Bands 1 - Coastal aerosol, Band 9 - Water vapour and Band 10 - SWIR/Cirrus)
* 290 km field of view
* Free and open data policy

==Sentinel-2 products==

* '''Level-1B''' product provides radiometrically corrected imagery in Top-Of-Atmosphere (TOA) radiance values and in sensor geometry. Level-1B product is composed of an ensemble of granules that are 25 km across track (AC) by 23 km along track (AL). Additionally, this product includes the refined geometry which is used to generate the Level-1C product. Level-1B pixel coordinates refer to the centre of each pixel.

* '''Level-1C''' product is composed of 100 km² single tiles (ortho-images in UTM/WGS84 projection). The Level-1C product results from using a Digital Elevation Model (DEM) to project the image in cartographic coordinates. Per-pixel radiometric measurements are provided in TOA reflectances with all parameters to transform them into radiances. Level-1C products are resampled with a constant Ground Sampling Distance (GSD) of 10, 20 and 60 m depending on the native resolution of the different spectral bands. In Level-1C products, pixel coordinates refer to the upper left corner of the pixel. Before September 2016, Level-1C was delivered as multi-tile product.

* '''Level-2A''' product provides Bottom Of Atmosphere (BOA) reflectance images derived from the associated Level-1C products. Therefore, each Level-2A product is also a 100 km² tile in cartographic geometry (UTM/WGS84 projection). BOA reflectances in Level-2A products are scaled by a factor of 10000.

==Data download==

Sentinel-2 data might be obtained from the [https://scihub.copernicus.eu/ Copernicus Open Access Hub], either by using the online interactive interface and browsing to your area of interest or by means of the API Hub. There are several other sites from which it is possible to download Sentinel-2 imagery as well. Here, some of them:

* [http://apps.sentinel-hub.com/eo-browser/ Sentinel-app]
* [http://sentinel-pds.s3-website.eu-central-1.amazonaws.com/ Amazon S3]
* [https://code-de.org/ Copernicus Data and Exploitation Platform – Deutschland (CODE-DE)]
* [https://maps.mundialis.de/ mundialis]
* [https://remotepixel.ca/projects/satellitesearch.html RemotePixel]
* [https://lv.eosda.com Land Viewer]

For those preferring or needing to download data via the API, there also exist several options:

* [https://github.com/ibamacsr/sentinelsat/ sentinelsat]: Python utilities to access the API of Copernicus Sentinels Scientific Data Hub (useful for all Sentinel satellite imagery)
* [https://github.com/olivierhagolle/Sentinel-download/ Sentinel-download]: Automated download of Sentinel-2 L1C data from ESA (through wget)

The probably most convenient way to download (and import) Sentinel data is to use the dedicated AddOn:
* [https://grass.osgeo.org/grass74/manuals/addons/r.sentinel.download.html r.sentinel.download]
It is build on top of the ''sentinelsat'' library (and also requires ''python-pandas'').

==Data pre-processing==

As from May 2017, ESA started to provide Level 2A products for Europe and they will reprocess the archive during this year (2017). However, it is (still) possible to download Level-1C products and customize the atmospheric correction by using different algorithms (i.e.: 6S, 6SV, [http://rsgislib.org/arcsi/ arcsi]) and/or a different DEM (Sen2Cor uses STRM 90m by default).

==Sentinel-2 in GRASS GIS==

To exemplify the handling of Sentinel-2 data with GRASS GIS, we will use S2 L1C scene from North Carolina (NC) from November 2016. Here are the details:

S2A_OPER_PRD_MSIL1C_PDMC_20161111T123605_R097_V20161110T160502_20161110T160502
830f2a5a-9914-427c-b4e0-69c6c14c71d4
2016-11-10T15:05:02Z


In the zipped folder delivered by ESA, the data itself is hidden under:
S2A_OPER_PRD_MSIL1C_PDMC_20161111T123605_R097_V20161110T160502_20161110T160502.SAFE/GRANULE/S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_N02.04/IMG_DATA/

S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B01.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B02.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B03.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B04.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B05.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B06.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B07.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B08.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B09.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B10.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B11.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B12.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B8A.jp2



===Import data===

The most convenient way to import downloaded Sentinel-data is to use the:
* [https://grass.osgeo.org/grass74/manuals/addons/r.sentinel.import.html r.sentinel.import] addon.

Manual import of Sentinel data is described below:

Sentinel-2 data comes in JPEG2000 format that can be easily imported into GRASS GIS either by means of {{cmd|r.in.gdal}} (in a UTM location) or using {{cmd|r.import}} that provides reprojection on the fly. In this example, we will use {{cmd|r.import}} to reproject and import into the NC sample location delivered with GRASS GIS.

<source lang="bash">
for map in `ls *.jp2` ; do
outmap=`basename $map .jp2`
r.import input=$map output=$outmap
done
</source>

If you prefer shorter map names, then it is possible to use {{cmd|g.rename}} or the add-on {{AddonCmd|g.rename.many}}. The other option is editing the file names before importing with sed, for example. Let us keep the S2A, date and band number parts only:

<source lang="bash">
for map in `ls *.jp2` ; do
outmap1=`basename $map .jp2`
outmap2=`echo $outmap1 | sed s/OPER_MSI_L1C_TL_MTI__//g | sed s/T210803_A007244_T17SPV//g`
r.import input=$map output=$outmap2
done
</source>

The output resolution estimated by {{cmd|r.import}} is slightly different than the nominal resolution of Sentinel-2 bands.

<source lang="bash">
r.info S2A_20161110_B08 -g | grep res
nsres=9.80178836938829
ewres=9.80224757766693
</source>

We need to set the proper resolution at import by means of the resolution and resolution_value options in {{cmd|r.import}}.

<source lang="bash">
for i in 02 03 04 08 ; do
g.message message="importing band ${i} with R 10m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=10 extent=input
done

for i in 05 06 07 8A 11 12 ; do
g.message message="importing band ${i} with R 20m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=20 extent=input
done

for i in 01 09 10 ; do
g.message message="importing band ${i} with R 60m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=60 extent=input
done
</source>

Unfortunately, nodata are not encoded in the Sentinel data and need to be set manually by replacing 0 with NULL.
This should be done in the original projection, before reprojecting the data.

In L2A products, there are artefacts along edges of swath paths, cell values are too low, caused by a bug in sen2cor.
All cells that are bordering a NULL cell must be set to NULL. This step might need to be repeated twice.

Because neighboring Sentinel tiles are overlapping each other, file sizes can be reduced by patching together neighboring tiles with
the same datatake sensing start time.

Before the actual reprojection, the computational region must be set properly. In the original projection,
four 10 meter cells fall exactly into one 20 meter cell, and nine 20 meter cells fall exactly into one 60 meter cell.
This can be achieved by first setting the region to the input extents (obtained with {{cmd|r.proj}} -g), then
aligning the region to a resolution of 60 meter, after that setting the region's resolution to the actual resolution of
the input band, this time without alignment. Alternatively, a reference grid can be created and the region for the current
input can then be aligned to that reference grid.

Now the data can be reprojected, preferably with method=bicubic_f or method=lanczos_f to avoid sawtooth patterns
of linear features which can appear with method=nearest (default).

===Atmospheric correction with {{cmd|i.atcorr}}===

Example here

Alternative: [https://rsgislib.org/arcsi/ Atmospheric and Radiometric Correction of Satellite Imagery (ARCSI)]



===Estimate diverse indices===

Given that Sentinel-2 MSI comes with 3 red edge bands, it allows to estimate several other vegetation indices, aside from the most classic ones. There is a quite exhaustive list at the [http://www.sentinel-hub.com/eotaxonomy/indices?page=1 Sentinel Hub] website.

* EVI = 2.5*(B08 - B04) / (B08 + 6*B04 - 7.5*B02 + 1) 
* ARVI = (B08 - (2*B04 - B02)) / (B08 + (2*B04 - B02)) 
* NDII = (B08 - B11) / (B08 + B11) 
* MSI = B11 / B08 
* PSRI-NIR = (B04 - B02) / B08 
* NDVI-GREEN = B03 * (B08 - B04) / (B08 + B04) 
* MTCI = (B06 - B05) / (B05 - B04) 
* IRECI = (B07 - B04) * B06 / B05 
* GRVI1 = (B04 - B03) / (B04 + B03) 
* GNDVI = (B08 - B03) / (B08 + B03) 
* EVI2 = 2.5 * (B08 - B04) / (B08 + 2.4 * B04 + 1) 
* ChlRE = B05 / B08 

===Classification===

Example here

==Further reading==
IMAGICO.DE blog
* [http://blog.imagico.de/sentinel-2-having-a-first-look-at-the-data-part-1/ First look at Sentinel data]
* [http://blog.imagico.de/who-is-moving-the-cheese-again/ Who is moving the cheese again?]

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Image processing]]
[[Category: Sentinel]]

SENTINEL

2018-01-29T11:21:22Z

⚠️Sbl: /* Data download */ link Martins new addon(s)

=Sentinel 2=

Sentinel-2 is an Earth observation mission developed by [https://en.wikipedia.org/wiki/European_Space_Agency ESA] as part of the [https://en.wikipedia.org/wiki/Copernicus_Programme Copernicus Programme] to perform terrestrial observations in support of services such as forest monitoring, land cover changes detection, and natural disaster management. It consists of two identical satellites, [https://en.wikipedia.org/wiki/Sentinel-2A Sentinel-2A] and [https://en.wikipedia.org/wiki/Sentinel-2B Sentinel-2B]. Details about the mission, user and technical guides as well as other documentation can be found at the ESA dedicated website [https://sentinel.esa.int/web/sentinel/missions/sentinel-2] and a number of other sites.

==Overview of Sentinel-2 mission capabilities==

Sentinel-2 mission has the following features:
* Multi-spectral data with ''13 bands'' in the visible, near infrared (NIR), and short wave infrared (SWIR).
* Systematic global coverage of land surfaces from 56° S to 84° N, coastal waters, and all of the Mediterranean Sea
* Revisiting every ''5 days'' under the same viewing angles. At high latitudes, Sentinel-2 swath overlaps and some regions are observed twice or more every 5 days, but with different viewing angles.
* Spatial resolutions of 10 m (Bands 2, 3, 4 and 8 - Blue, Green, Red and NIR), 20 m (Bands 5, 6 and 7 - Red Edge bands, Band 8A - Narrow infrared and Bands 11 and 12 - SWIR) and 60 m (Bands 1 - Coastal aerosol, Band 9 - Water vapour and Band 10 - SWIR/Cirrus)
* 290 km field of view
* Free and open data policy

==Sentinel-2 products==

* '''Level-1B''' product provides radiometrically corrected imagery in Top-Of-Atmosphere (TOA) radiance values and in sensor geometry. Level-1B product is composed of an ensemble of granules that are 25 km across track (AC) by 23 km along track (AL). Additionally, this product includes the refined geometry which is used to generate the Level-1C product. Level-1B pixel coordinates refer to the centre of each pixel.

* '''Level-1C''' product is composed of 100 km² single tiles (ortho-images in UTM/WGS84 projection). The Level-1C product results from using a Digital Elevation Model (DEM) to project the image in cartographic coordinates. Per-pixel radiometric measurements are provided in TOA reflectances with all parameters to transform them into radiances. Level-1C products are resampled with a constant Ground Sampling Distance (GSD) of 10, 20 and 60 m depending on the native resolution of the different spectral bands. In Level-1C products, pixel coordinates refer to the upper left corner of the pixel. Before September 2016, Level-1C was delivered as multi-tile product.

* '''Level-2A''' product provides Bottom Of Atmosphere (BOA) reflectance images derived from the associated Level-1C products. Therefore, each Level-2A product is also a 100 km² tile in cartographic geometry (UTM/WGS84 projection). BOA reflectances in Level-2A products are scaled by a factor of 10000.

==Data download==

Sentinel-2 data might be obtained from the [https://scihub.copernicus.eu/ Copernicus Open Access Hub], either by using the online interactive interface and browsing to your area of interest or by means of the API Hub. There are several other sites from which it is possible to download Sentinel-2 imagery as well. Here, some of them:

* [http://apps.sentinel-hub.com/eo-browser/ Sentinel-app]
* [http://sentinel-pds.s3-website.eu-central-1.amazonaws.com/ Amazon S3]
* [https://code-de.org/ Copernicus Data and Exploitation Platform – Deutschland (CODE-DE)]
* [https://maps.mundialis.de/ mundialis]
* [https://remotepixel.ca/projects/satellitesearch.html RemotePixel]
* [https://lv.eosda.com Land Viewer]

For those preferring or needing to download data via the API, there also exist several options:

* [https://github.com/ibamacsr/sentinelsat/ sentinelsat]: Python utilities to access the API of Copernicus Sentinels Scientific Data Hub (useful for all Sentinel satellite imagery)
* [https://github.com/olivierhagolle/Sentinel-download/ Sentinel-download]: Automated download of Sentinel-2 L1C data from ESA (through wget)

The probably most convenient way to download (and import) Sentinel data is to use the dedicated AddOn:
* [https://grass.osgeo.org/grass74/manuals/addons/r.sentinel.download.html r.sentinel.download]
It is build on top of the ''sentinelsat'' library (and also requires ''python-pandas'').

==Data pre-processing==

As from May 2017, ESA started to provide Level 2A products for Europe and they will reprocess the archive during this year (2017). However, it is (still) possible to download Level-1C products and customize the atmospheric correction by using different algorithms (i.e.: 6S, 6SV, [http://rsgislib.org/arcsi/ arcsi]) and/or a different DEM (Sen2Cor uses STRM 90m by default).

==Sentinel-2 in GRASS GIS==

To exemplify the handling of Sentinel-2 data with GRASS GIS, we will use S2 L1C scene from North Carolina (NC) from November 2016. Here are the details:

S2A_OPER_PRD_MSIL1C_PDMC_20161111T123605_R097_V20161110T160502_20161110T160502
830f2a5a-9914-427c-b4e0-69c6c14c71d4
2016-11-10T15:05:02Z


In the zipped folder delivered by ESA, the data itself is hidden under:
S2A_OPER_PRD_MSIL1C_PDMC_20161111T123605_R097_V20161110T160502_20161110T160502.SAFE/GRANULE/S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_N02.04/IMG_DATA/

S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B01.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B02.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B03.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B04.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B05.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B06.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B07.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B08.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B09.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B10.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B11.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B12.jp2
S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B8A.jp2



===Import data===

Sentinel-2 data comes in JPEG2000 format that can be easily imported into GRASS GIS either by means of {{cmd|r.in.gdal}} (in a UTM location) or using {{cmd|r.import}} that provides reprojection on the fly. In this example, we will use {{cmd|r.import}} to reproject and import into the NC sample location delivered with GRASS GIS.

<source lang="bash">
for map in `ls *.jp2` ; do
outmap=`basename $map .jp2`
r.import input=$map output=$outmap
done
</source>

If you prefer shorter map names, then it is possible to use {{cmd|g.rename}} or the add-on {{AddonCmd|g.rename.many}}. The other option is editing the file names before importing with sed, for example. Let us keep the S2A, date and band number parts only:

<source lang="bash">
for map in `ls *.jp2` ; do
outmap1=`basename $map .jp2`
outmap2=`echo $outmap1 | sed s/OPER_MSI_L1C_TL_MTI__//g | sed s/T210803_A007244_T17SPV//g`
r.import input=$map output=$outmap2
done
</source>

The output resolution estimated by {{cmd|r.import}} is slightly different than the nominal resolution of Sentinel-2 bands.

<source lang="bash">
r.info S2A_20161110_B08 -g | grep res
nsres=9.80178836938829
ewres=9.80224757766693
</source>

We need to set the proper resolution at import by means of the resolution and resolution_value options in {{cmd|r.import}}.

<source lang="bash">
for i in 02 03 04 08 ; do
g.message message="importing band ${i} with R 10m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=10 extent=input
done

for i in 05 06 07 8A 11 12 ; do
g.message message="importing band ${i} with R 20m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=20 extent=input
done

for i in 01 09 10 ; do
g.message message="importing band ${i} with R 60m"
r.import S2A_OPER_MSI_L1C_TL_MTI__20161110T210803_A007244_T17SPV_B${i}.jp2 out=S2A_20161110_B${i} resolution=value resolution_value=60 extent=input
done
</source>

Unfortunately, nodata are not encoded in the Sentinel data and need to be set manually by replacing 0 with NULL.
This should be done in the original projection, before reprojecting the data.

In L2A products, there are artefacts along edges of swath paths, cell values are too low, caused by a bug in sen2cor.
All cells that are bordering a NULL cell must be set to NULL. This step might need to be repeated twice.

Because neighboring Sentinel tiles are overlapping each other, file sizes can be reduced by patching together neighboring tiles with
the same datatake sensing start time.

Before the actual reprojection, the computational region must be set properly. In the original projection,
four 10 meter cells fall exactly into one 20 meter cell, and nine 20 meter cells fall exactly into one 60 meter cell.
This can be achieved by first setting the region to the input extents (obtained with {{cmd|r.proj}} -g), then
aligning the region to a resolution of 60 meter, after that setting the region's resolution to the actual resolution of
the input band, this time without alignment. Alternatively, a reference grid can be created and the region for the current
input can then be aligned to that reference grid.

Now the data can be reprojected, preferably with method=bicubic_f or method=lanczos_f to avoid sawtooth patterns
of linear features which can appear with method=nearest (default).

===Atmospheric correction with {{cmd|i.atcorr}}===

Example here

Alternative: [https://rsgislib.org/arcsi/ Atmospheric and Radiometric Correction of Satellite Imagery (ARCSI)]



===Estimate diverse indices===

Given that Sentinel-2 MSI comes with 3 red edge bands, it allows to estimate several other vegetation indices, aside from the most classic ones. There is a quite exhaustive list at the [http://www.sentinel-hub.com/eotaxonomy/indices?page=1 Sentinel Hub] website.

* EVI = 2.5*(B08 - B04) / (B08 + 6*B04 - 7.5*B02 + 1) 
* ARVI = (B08 - (2*B04 - B02)) / (B08 + (2*B04 - B02)) 
* NDII = (B08 - B11) / (B08 + B11) 
* MSI = B11 / B08 
* PSRI-NIR = (B04 - B02) / B08 
* NDVI-GREEN = B03 * (B08 - B04) / (B08 + B04) 
* MTCI = (B06 - B05) / (B05 - B04) 
* IRECI = (B07 - B04) * B06 / B05 
* GRVI1 = (B04 - B03) / (B04 + B03) 
* GNDVI = (B08 - B03) / (B08 + B03) 
* EVI2 = 2.5 * (B08 - B04) / (B08 + 2.4 * B04 + 1) 
* ChlRE = B05 / B08 

===Classification===

Example here

==Further reading==
IMAGICO.DE blog
* [http://blog.imagico.de/sentinel-2-having-a-first-look-at-the-data-part-1/ First look at Sentinel data]
* [http://blog.imagico.de/who-is-moving-the-cheese-again/ Who is moving the cheese again?]

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Image processing]]
[[Category: Sentinel]]

GRASS GIS Community Sprint Bonn 2018

2017-12-22T14:08:44Z

⚠️Sbl: Add Stefan

{{toc|right}}

The '''GRASS GIS community''' will join the general '''OSGeo Code Sprint''' at BaseCamp in Bonn, following the annual FOSSGIS conference (German Speaking OSGeo Local Chapter conference in Bonn, Germany)

<center>
[[File:GRASS_GIS_Code_Sprint_2018.png|320px]]
</center>

== Timing, Venue ==

OSGeo Code Sprint: '''March 18 - 25, 2018 at BaseCamp. Bonn, Germany'''.

== Sponsors ==

Please check more info on the Bonn Code Sprint 2018 [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 here].

We also welcome direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.
This Bonn event is especially interesting since '''important OSGeo projects come together'''!

== Agenda - What we plan to do ==

=== Move to GIT ===
* Choose among different options: OSGeo Git, Github, GitLab
* Participants are invited to study GIT in advance :-)

== Planned participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants <<--- important!

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Neteler|Markus Neteler]]
|Germany
|18.3.
|25.3.
|Migration to git discussion, GRASS GIS 8
|M
|
|-
|2
|[[User:Ychemin|Yann Chemin]]
|France
|18.3.
|25.3.
|ISIS-GRASS, Planetary projections, i.ortho.photo, bundle blocks, GRASS GIS 8
|XL
|
|-
|3
|[[User:Landa|Martin Landa]]
|Czech Republic
|18.3.
|25.3.
|Migration to git discussion, website discussion, GRASS GIS 8
|L
|
|-
|4
|Stefan Blumentrath
|Germany/Norway
|??.??.
|25.3.
|Flexible
|L
|
|-
|3
|...
|
|
|
|
|
|
|-
|}

=== Via IRC chat ===

(IRC is a nice archaic chat system, see [[IRC]])

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|Add
|your
|self..
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== Reports ==

See [[Talk:GRASS_Community_Sprint_Bonn_2018]]

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2018]]

Talk:GRASS Community Sprint Bonn 2016

2016-09-05T19:59:05Z

⚠️Sbl: Stefans report

== Thoughts and impressions from the GRASS GIS Community Sprint at FOSS4G 2016 ==

Last week we had the pleasure to attend the International FOSS4G 2016 Conference in Bonn. But not only that... Both, before and after
the conference, "Code Sprints" took place. What is a '''"Code Sprint"'''? Basically, it is a group of free and open source developers who (fueled with beer, coffee and snacks/pizza/sandwiches) gather to develop new stuff, enhance existing tools, perform bug fixing, translate and write documentation, discuss and decide the way to go with the software they contribute to (essentially the software they love we would say, it all comes to that). Anyway, in this context, also GRASS GIS developers gathered in what we usually call the '''"Community Sprints"''', since it's not only a meeting of developers but also of users, and other contributors - everybody is welcome and their help appreciated.

So, what did we do at these two sprints?

Well, first of all, '''we had a great time!''' It is always a great joy to meet again (or in some cases even for the first time) with those people that use to answer your emails in the mailing list(s), fix or enhance modules, help in so many ways... One feels at home :-)

But we also worked a lot! The most important is that '''the last GRASS GIS 6 version''' was released on Sunday at 1:00 am or so [https://grass.osgeo.org/news/58/15/GRASS-GIS-6-4-6-released]. Also several other issues were discussed and addressed, i.e.: the next minor release of 7.0.5 - planned for mid of September, and the new major release of GRASS GIS 7.2.0, which is planned for 1st of October 2016. Furthermore, the styling of a new Web site for the GRASS GIS project was lively discussed. Moreover, the participants fixed a number of bugs, backported numerous features, cleaned outdated tickets, and added some new features. Even a new add-on was developed in these days. Eventually also some tutorials explaining how to work with time series and Sentinel-2 satellite data got written up. Last but not least, a member of the community provided a new [https://trac.osgeo.org/grass/browser/grass-promo/grassflyer/flyer_2016 flyer] for GRASS GIS. Please help us translating, improving and distributing it!

Oh! And by Sunday evening, also the PSC election 2016 time was over, and we got a '''new PSC''' (See results [https://trac.osgeo.org/grass/wiki/PSC/Election2016 here])! Congratulations!!! For the first time, users that have contributed to GRASS GIS project were formally invited to vote... Isn't that great? Therefore, Community Sprints, '''Community Spirit''' ;-)

'''Join and en-joy GRASS GIS!'''

[[File:Grass community sprint 2016.png|thumb|center|1000px]]

== Participants and Reports ==

=== Moritz ===
* OBIA Toolchain
** Cleaned up r.object.geometry and moved it to addons {{rev|69187}} + {{rev|69188}}, {{AddonCmd|r.object.geometry}}
** Modified {{AddonCmd|i.segment.stats}} to user.object.geometry instead of v.to.db
** Improved error handling in i.segment.stats and use temporary files on disk to reduce memory use
** Modified {{AddonCmd|i.segment.uspo}} to also allow testing new mean shift algorithm (currently only available in sandbox) {{rev|69236}}
** Tested mean shift algorithm
* Working on 6.4.6 release
** General bug triaging
** Backported fix of {{trac|1444}} to release_64
** Backported fix of {{trac|2558}} to release_64
* Scratched an old itch and implement a flag in {{Cmd|g.region}} to allow shell style output in flat (one line) style {{rev|69240}}

*[https://trac.osgeo.org/grass/timeline?from=Aug+23%2C+2016&daysback=2&authors=mlennert&milestone=on&ticket=on&changeset=on&wiki=on&sfp_email=&sfph_mail=&update=Update Log overview]

=== Markus Neteler ===
* assist CRO in cleaning PSC election voter email addresses (400 addresses reduced to 240 clean addresses)
* minor pseudo-mercator discussions
* major datum shift file discussions with Even Rouault (GDAL) and fellow GRASS sprinters: libproj cleanup of local copies of NAD and datum shift files which are indeed used from GDAL; extended documentation in README.txt ({{trac|2456}}, {{rev|2456}})
* GRASS GIS 6.4.6 release management
** tagging, packaging source code, upload
** writing announcement together with Milena, Vero and Moritz: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* checking backports together with Martin Landa for GRASS GIS 7.0.5 and for the planned GRASS GIS 7.2.0
* written draft Sentinel-2 processing script for Vero
* backports: {{rev|69265}}, etc

=== Anna Petrasova ===
* {{rev|69199}}: major backport of Adam's GSoC work to 7.2. (please test!)
* fix {{trac|3133}}, {{trac|2252}}

=== Martin Landa ===

* Fix {{trac|2480}}, {{trac|2765}}
* Bug reports for 7.0.5 milestone reviewed, outdated tickets closed
* [https://trac.osgeo.org/grass/timeline?from=Aug+28%2C+2016&daysback=7&authors=martinl&milestone=on&ticket=on&changeset=on&wiki=on&sfp_email=&sfph_mail=&update=Update Log overview]

=== Vero ===

* Tutorials (to be published soon):
# R-GRASS integration for raster time series handling/processing.
# Sentinel-2 processing chain in GRASS with Markus' help.
* Discussed with Stefan about new add-on design and helped testing (See {{rev|69294}}).
* Helped testing new pymodis.
* Wrote draft of announcement for GRASS 6.4.6 release along with Milena, Moritz and Markus.

=== Nikos ===

===== Done =====

* CRO related tasks
* Patched [https://trac.osgeo.org/grass/changeset/69012/grass/trunk/imagery/i.atcorr/create_iwave.py create_iwave.py], see {{trac|3027}} -- mentored by Moritz.
* Rewrote {{Cmd|i.rgb.his}} to allow for 16-bit input data -- need to test more though.
* Corrected erroneous function in {{AddonCmd|i.landsat8.swlst}} -- thanks to Stefan Blumentrath!

===== On-Going =====

* Rewrite: {{Cmd|i.his.rgb}} -- see {{trac|774}}!

===== Ideas =====

* Scratching a new version for `create_iwave.py` -- vision: one Class to rule them all.
* Reviewing options to fuse {{Cmd|i.pansharpen}} with/into {{AddonCmd|i.fusion.hpf}}

=== Luca Delucchi ===

* working mostly in pyModis sorry
* fixed {{trac|2864}}
* started to update r.modis
* discussed about new website
* submit and work on the new flyer created by Vincent Bain (https://svn.osgeo.org/grass/grass-promo/grassflyer/flyer_2016/)
* Translated the flyer in Italian

=== Stefan Blumentrath ===

* wrote v.in.pygbif addon (https://svn.osgeo.org/grass/grass-addons/grass7/vector/v.in.pygbif) for downloading species occurrence data from GBIF using pygbif (with kind support from Lucca, Vero and Helmut)

GRASS Community Sprint Bonn 2016

2016-08-17T21:09:15Z

⚠️Sbl: stefan to do

{{toc|right}}
During the [http://2016.foss4g.org/ FOSS4G 2016] , 21-28 August 2016, [http://en.wikipedia.org/wiki/Bonn Bonn], [https://en.wikipedia.org/wiki/Germany Germany], the GRASS GIS project will join the code sprint

'''Important dates:'''

* CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end) (see also [http://2016.foss4g.org/programme.html#code-sprints here])
* [http://2016.foss4g.org/#page9 FOSS4G 2016 Schedule]
* CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m (see also [http://2016.foss4g.org/programme.html#code-sprints here])

== Purpose ==

Get together of GRASS GIS project members to take decisions and tackle small and larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators, and users!

== Sponsors ==

If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Bonn. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

== Venue ==

* Bonn, Germany: http://www.basecamp-bonn.de - 7.12316E 50.70763N ([http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap])

== Accommodation and Costs ==

* to be defined

== Weather ==

* https://en.wikipedia.org/wiki/Bonn#Climate

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please edit this wiki page!

=== More core developers with SVN write access ===
* Develop a strategy to refresh the group with core SVN write access

=== Web site ===
* Migrate the good old CMSMS to Wordpress

=== Promo ===
* Finalize the new GRASS GIS flyer prepared by Vincent Bain
** needed: catchy time series screenshot

=== New Releases ===
Minor releases:
* Release GRASS GIS 6.4.6:
** Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* Release GRASS GIS 7.0.5:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News

'''Major release''':
* Release GRASS GIS 7.2.0:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News

=== Documentation and translation ===
* Add examples to manual pages
* Translation of messages
* Translation of Wiki pages

=== Source code Quality Assessment ===
* integrate "coverity scan" with Travis, https://scan.coverity.com/travis_ci
* check "coverity scan": copy-paste errors, https://scan.coverity.com/projects/1038

=== Bug squashing ===
* Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
* {{trac|2864}}: Add link to source code in the documentation pages (almost done, let's finish it!)

=== Improvements ===
* improve r.modis addons
* integrate Google Summer of Code projects (where adequate)
* continue working on OBIA toolchain:
** Testing of mean shift in i.segment
** Finalization of r.object.geometry and its integration into i.segment.uspo
* add R-batch files to OSGeo4W-winGRASS7 see [https://trac.osgeo.org/osgeo4w/ticket/413 osgeo4w/ticket 413]
* Implement an optional session "kickstart" in GRASS with LatLong predefined, then open import wizard | switch projection inside (like most other GIS do!)

=== Better integration of git into development ===
* since github/gitlab/bitbucket etc are a valuable and recognized source of new source code, we should be able to receive such contributions easily
** OSGeo currently deploys a self-hosted "gitlab" repo: https://lists.osgeo.org/pipermail/sac/2016-August/007345.html

... YOUR IDEA HERE ...

== Participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| August 21
| August 28
|
| L
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
| August 21
| August 28
|
| L
|
|-
|3
|[[User:Neteler|Markus Neteler]]
|Italy
| August 21
| August 28
| Releases, project coordination, bug hunting, getting more ppl involved
| M
|
|-
|4
|[[User:NikosA|Nikos Alexandris]]
|Switzerland
| August 21
| August 28
|
| S or M
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina
| August 26
| August 28
|
| S
|
|-
|6
|[[User:mlennert|Moritz Lennert]]
|Belgium
| August 21
| August 27
|
| M
|
|-
|7
|[[User:sbl|Stefan Blumentrath]]
|Norway
| August 26
| August 28
| Port some Addons to python? (or whatever you put me up to)
| L
|
|-
|8
|[[User:MilenaN|Milena Nowotarska]]
|Poland
| August 21
| August 28
|
| M
|
|-
|9
|[[User:annazanchetta|Anna Zanchetta]]
|Italy - Israel
| August 22
| August 27
| Implementing and improving some imagery modules, inshallah
| S
|
|-
|}

=== Via IRC chat ===

(IRC is a nice archaic chat system, see [[IRC]])

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[[User:Ychemin|Yann Chemin]]
|France
|-
|2
|[[User:hellik|Helmut Kudrnovsky]]
|Austria
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

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

GRASS Community Sprint Bonn 2016

2016-08-16T13:16:00Z

⚠️Sbl: /* Sponsors */

{{toc|right}}
During the [http://2016.foss4g.org/ FOSS4G 2016] , 21-28 August 2016, [http://en.wikipedia.org/wiki/Bonn Bonn], [https://en.wikipedia.org/wiki/Germany Germany], the GRASS GIS project will join the code sprint

'''Important dates:'''

* CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end)
* [http://2016.foss4g.org/#page9 FOSS4G 2016 Schedule]
* CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m

== Purpose ==

Get together of GRASS GIS project members to take decisions and tackle small and larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators, and users!

== Sponsors ==

If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Bonn. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

== Venue ==

* Bonn, Germany: http://www.basecamp-bonn.de

== Accommodation and Costs ==

* to be defined

== Weather ==

* https://en.wikipedia.org/wiki/Bonn#Climate

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please edit this wiki page!

=== Web site ===
* Migrate the good old CMSMS to Wordpress

=== Promo ===
* Finalize the new GRASS GIS flyer prepared by Vincent Bain
** needed: catchy time series screenshot

=== New Releases ===
Minor releases:
* Release GRASS GIS 6.4.6:
** Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* Release GRASS GIS 7.0.5:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News

'''Major release''':
* Release GRASS GIS 7.2.0:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News

=== Documentation and translation ===
* Add examples to manual pages
* Translation of messages
* Translation of Wiki pages

=== Bug squashing ===
* Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
* {{trac|2864}}: Add link to source code in the documentation pages (almost done, let's finish it!)

=== Improvements ===
* improve r.modis addons
* integrate Google Summer of Code projects (where adequate)
* continue working on OBIA toolchain:
** Testing of mean shift in i.segment
** Finalization of r.object.geometry and its integration into i.segment.uspo

=== Better integration of git into development ===
* since github/gitlab/bitbucket etc are a valuable and recognized source of new source code, we should be able to receive such contributions easily

... YOUR IDEA HERE ...

== Participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| August 21
| August 28
|
| L
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
| August 21
| August 28
|
| L
|
|-
|3
|[[User:Neteler|Markus Neteler]]
|Italy
| August 21
| August 28
| Releases, project coordination, bug hunting, getting more ppl involved
| M
|
|-
|4
|[[User:NikosA|Nikos Alexandris]]
|Switzerland
| August 21
| August 28
|
| S or M
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina
| August 26
| August 28
|
| S
|
|-
|6
|[[User:mlennert|Moritz Lennert]]
|Belgium
| August 21
| August 27
|
| M
|
|-
|7
|[[User:sbl|Stefan Blumentrath]]
|Norway
| August 26
| August 28
|
| L
|
|-
|}

=== Via IRC chat ===

(IRC is a nice archaic chat system, see [[IRC]])

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[[User:Ychemin|Yann Chemin]]
|France
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

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

GRASS Community Sprint Bonn 2016

2016-08-16T08:52:45Z

⚠️Sbl: I am inn

{{toc|right}}
During the [http://2016.foss4g.org/ FOSS4G 2016] , 21-28 August 2016, [http://en.wikipedia.org/wiki/Bonn Bonn], [https://en.wikipedia.org/wiki/Germany Germany], the GRASS GIS project will join the code sprint

'''Important dates:'''

* CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end)
* [http://2016.foss4g.org/#page9 FOSS4G 2016 Schedule]
* CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m

== Purpose ==

Get together of GRASS GIS project members to take decisions and tackle small and larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators, and users!

== Sponsors ==

If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donations/ http://grass.osgeo.org/donations/]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

== Venue ==

* Bonn, Germany: http://www.basecamp-bonn.de

== Accommodation and Costs ==

* to be defined

== Weather ==

* https://en.wikipedia.org/wiki/Bonn#Climate

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please edit this wiki page!

=== Web site ===
* Migrate the good old CMSMS to Wordpress

=== New Releases ===
Minor releases:
* Release GRASS GIS 6.4.6:
** Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
* Release GRASS GIS 7.0.5:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News

'''Major release''':
* Release GRASS GIS 7.2.0:
** Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
** Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News

=== Documentation and translation ===
* Add examples to manual pages
* Translation of messages
* Translation of Wiki pages

=== Bug squashing ===
* Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
* {{trac|2864}}: Add link to source code in the documentation pages (almost done, let's finish it!)

=== Improvement ===
* improve r.modis addons
* integrate Google Summer of Code projects (where adequate)
* continue working on OBIA toolchain:
** Testing of mean shift in i.segment
** Finalization of r.object.geometry and its integration into i.segment.uspo

... YOUR IDEA HERE ...

== Participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| August 21
| August 28
|
| L
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
| August 21
| August 28
|
| L
|
|-
|3
|[[User:Neteler|Markus Neteler]]
|Italy
| August 21
| August 28
|
| M
|
|-
|4
|[[User:NikosA|Nikos Alexandris]]
|Switzerland
| August 21
| August 28
|
| S or M
|
|-
|5
|[[User:Veroandreo|Veronica Andreo]]
|Argentina
| August 26
| August 28
|
| S
|
|-
|6
|[[User:mlennert|Moritz Lennert]]
|Belgium
| August 21
| August 27
|
| M
|
|-
|7
|[[User:sbl|Stefan Blumentrath]]
|Norway
| August 26
| August 28
|
| L
|
|-
|}

=== Via IRC chat ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|-
|1
|[[User:Ychemin|Yann Chemin]]
|France
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

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

LANDSAT

2016-05-22T19:35:14Z

⚠️Sbl: Added new modules

== Data Availability==

Landsat imagery can be obtained from [http://landsat.usgs.gov/ USGS' LANDSAT archive]:

* [http://glovis.usgs.gov USGS GloVis]
* [http://earthexplorer.usgs.gov/ EarthExplorer]
* [http://earthexplorer.usgs.gov/bulk/help Bulk Download Orders] using the [http://earthexplorer.usgs.gov/bulk/ Bulk Download Application]
* [http://landsatlook.usgs.gov/ LandsatLook Viewer]

See also the [[Global datasets]] wiki page

On 06/12/13, USGS [http://landsat.usgs.gov/about_LU_Vol_7_Issue_4.php announced] the availability of [http://landsat.usgs.gov/landsat8.php LANDSAT 8]. See also [http://landsat.usgs.gov/band_designations_landsat_satellites.php this page].

== Modules overview ==

GRASS GIS features a complete set of native modules and various add-ons for pre- and post-processing Landsat satellite imagery. The following lists offer an overview of related modules and add-ons.

=== Generic modules applicable to Landsat ===

* {{cmd|d.rgb}} → display 3-band data
* {{cmd|r.composite}} → flatten 3-bands of data into a single image (lossy, maybe used in combination with {{cmd|i.landsat.rgb|version=64}} (GRASS 6.x) | {{cmd|i.colors.enhance|version=70}} (GRASS 7.x)
* {{cmd|i.atcorr}} → correct top of atmosphere to surface reflectance - see also the [[Atmospheric correction]] wiki page
* {{cmd|i.topo.corr}} → used to topographically correct reflectance from imagery files, e.g. obtained with {{cmd|i.landsat.toar}}, using a sun illumination terrain model
* {{cmd|i.oif}} → calculate the 3 bands showing the greatest difference (for use as R,G,B bands)
* {{AddonCmd|i.histo.match}} (addon) → histogram matching of two or more raster maps (in grass 7) ''Note, the module works with integer values and does not accept the "." character as part of the raster map's name!''

=== Landsat specific modules ===

* {{cmd|i.landsat.rgb|version=64}} (GRASS 6.x) | {{cmd|i.colors.enhance|version=70}} (GRASS 7.x) → auto-enhance colors
* {{cmd|i.landsat.toar}} → convert DN to top of atmosphere radiance
* {{cmd|i.landsat.acca}} → cloud cover assessment
* {{cmd|i.tasscap}} → Performs Tasseled Cap (Kauth Thomas) transformation

=== Landsat specific GRASS AddOns ===

* {{AddonCmd|i.landsat.trim|version=64}} → trims border fringes for each band separately or with the MASK where coverage exists for all bands
* {{AddonCmd|i.landsat.dehaze|version=64}} → haze removal
* {{AddonCmd|i.landsat8.qc|version=70}} → Reclass Landsat8 QA band according to acceptable pixel quality as defined by the user
* {{AddonCmd|i.landsat8.swlst|version=70}} → Practical split-window algorithm estimating Land Surface Temperature from Landsat 8 OLI/TIRS imagery
* {{AddonCmd|i.wi|version=70}} → Calculate different water indices

== Pre-Processing ==

=== Overview ===

Typically, pre-processing Landsat imagery comprises the following steps:

# '''import''' in the database → {{cmd|r.in.gdal}}
# geometrically & orthometrically correct imagery
#* already done for L1T products, read more at [http://landsat.usgs.gov//Landsat_Processing_Details.php USGS' Landsat Information Products] webpage
# optionally, automatically '''cut-off border fringes''' → {{AddonCmd|i.landsat.trim|version=64}}
#* of course one can use the official WRS2 Path/Row vector tiles to manually trim border fringes
# optionally, '''denoise''' for obvious/intensive salt & pepper effects, stripes, etc.
#* for example by applying Principal Components Analysis as a denoising technique → {{cmd|i.pca}} ''<<< Re-order this step?''
# '''convert''' the '''Digital Numbers''' (DNs) to '''Top-of-Atmosphere Radiances/Reflectances''' (ToARs) → {{cmd|i.landsat.toar}}
# optionally, '''correct for atmospheric effects''' → {{cmd|i.atcorr}}
#* that is, accounting for distorting atmospheric effects and estimating actual reflectances as they would have been measured on the ground
#* also described as conversion to Top-of-Canopy Reflectances (ToCRs)
# '''assessing cloud cover''' → {{cmd|i.landsat.acca}}
#* optionally, detect and remove clouds shadows as well
# '''topographically normalise''' imagery → {{cmd|i.topo.corr}}
#* also known as topographic correction, that is, accounting for illumination differences due to the acquisition's geometry
# '''radiometrically normalise''' → one approach via {{AddonCmd|i.histo.match}} (in '''grass 7''', addon), also known as relative radiometric normalisation -- one approach is the ''histogram matching'' technique of two or more raster maps
#* '''ToDo/More techniques?'''

See also
* [http://courses.neteler.org/processing-landsat8-data-in-grass-gis-7/ Processing Landsat 8 data in GRASS GIS 7: Import and visualization]

=== Importing data ===

Importing Landsat spectral bands in GRASS GIS' data base can be done both from the Graphical User Interface or from the command line

# Open GRASS GIS, select ''Location Wizard'' in order to create a new location from georeferenced file
# Use the ''Import file tool'', or the {{cmd|r.in.gdal}} module, to import the GeoTIFF files into GRASS GIS.

See also [http://grasswiki.osgeo.org/wiki/LANDSAT#Automated_data_import Automated data import] below.

==== Notes ====

# Most Landsat scenes are delivered in ''north-is-up'' orientation, hence the import process is straightforward.
# If you get <source lang="bash" enclose="none">ERROR: Input map is rotated - cannot import.</source>, the image must be first rotated externally, applying the rotation info stored in the metadata field of the raster image file. For example, the <code>gdalwarp</code> software can be used to transform the map to North-up (note, there are several <code>gdalwarp</code> parameters to select the resampling algorithm):

<ul>
<source lang="bash">
gdalwarp rotated.tif northup.tif
</source>
</ul>

==== Hint: Minimal disk space copies ====

Here's a little trick using {{cmd|r.reclass}} to rename maps (for example, from ''L71074092_09220040924_B'''10''''' to ''L71074092_09220040924_B'''1''''') without touching the data or wasting disk space:

<source lang="bash">
BASE=L71074092_09220040924

for BAND in 10 20 30 40 50 61 70 80; do
BAND1st=`echo $BAND | sed -e 's/0$//'`
r.reclass in="${BASE}_B$BAND" out=$BASE.$BAND1st << EOF
* = *
EOF
done
</source>

==== Automated data import ====

The following ''Python'' script imports Landsat imagery into GRASS' data base. Specifically, the script

* creates an independent Mapset for each Landsat scene
* imports and renames bands of a scene as <tt>B<id></tt>, e.g. B10, B20, ..., B80.
* additionaly sets up the timestamp based on MTL metadata file

'''Note,''' the (newest) official naming pattern for Landsat scenes -- explained in [https://lta.cr.usgs.gov/landsat_dictionary.html USGS' Landsat Data Dictionary] as the [https://lta.cr.usgs.gov/landsat_dictionary.html#entity_id Landsat Scene Identifier] -- and all individual bands that compose a scene -- bands have a suffix which is like _B10, _B20, _B30, etc. -- differ from what some Landsat specific modules expect. For example, the modules {{cmd|i.landsat.toar}} and {{cmd|i.landsat.acca}} expect the bands to follow a naming pattern such as "scenename.1, .2, .3", etc.

To use the script save it as <source lang="bash" enclose="none">import_landsat.py</source> file and make sure it is granted the execution permission.

<source lang=python>
#!/usr/bin/python

import os
import sys
import glob
import grass.script as grass

def get_timestamp(mapset):
try:
metafile = glob.glob(mapset + '/*MTL.txt')[0]
except IndexError:
return

result = dict()
try:
fd = open(metafile)
for line in fd.readlines():
line = line.rstrip('\n')
if len(line) == 0:
continue
if any(x in line for x in ('DATE_ACQUIRED', 'ACQUISITION_DATE')):
result['date'] = line.strip().split('=')[1].strip()
finally:
fd.close()

return result

def import_tifs(mapset):
meta = get_timestamp(mapset)
for file in os.listdir(mapset):
if os.path.splitext(file)[-1] != '.TIF':
continue
ffile = os.path.join(mapset, file)
if ('VCID') in ffile:
name = "".join((os.path.splitext(file)[0].split('_'))[1::2])
else:
name = os.path.splitext(file)[0].split('_')[-1]
if len(name) == 3 and name[-1] == '0':
band = int(name[1:2])
elif len(name) == 3 and name[-1] != '0':
band = int(name[1:3])
else:
band = int(name[-1:])
grass.message('Importing %s -> %s@%s...' % (file, name, mapset))
grass.run_command('g.mapset',
flags = 'c',
mapset = mapset,
quiet = True,
stderr = open(os.devnull, 'w'))
grass.run_command('r.in.gdal',
input = ffile,
output = name,
quiet = True,
overwrite = True,
title = 'band %d' % band)
if meta:
year, month, day = meta['date'].split('-')
if month == '01':
month = 'jan'
elif month == '02':
month = 'feb'
elif month == '03':
month = 'mar'
elif month == '04':
month = 'apr'
elif month == '05':
month = 'may'
elif month == '06':
month = 'jun'
elif month == '07':
month = 'jul'
elif month == '08':
month = 'aug'
elif month == '09':
month = 'sep'
elif month == '10':
month = 'oct'
elif month == '11':
month = 'nov'
elif month == '12':
month = 'dec'

grass.run_command('r.timestamp',
map = name,
date = ' '.join((day, month, year)))

def main():
if len(sys.argv) == 1:
for directory in filter(os.path.isdir, os.listdir(os.getcwd())):
import_tifs(directory)
else:
import_tifs(sys.argv[1])

if __name__ == "__main__":
main()
</source>

'''Example of usage'''

After having collected the Landsat scenes of interest in one directory, the script can be used as follows:

* <source lang="python" enclose="none">./import_landsat.py</source> → the script will walk through a ''pool'' directory that contains unique Landsat scene directories (e.g. three directories named after the official naming pattern: LT51800342011158MOR00 LT51810352009079MTI00 LT51820352009326MTI00) and import all bands of each individual scene in their own Mapset
* <source lang="python" enclose="none">./import_landsat.py LM41890261983200FFF03</source> → the scrip will import only bands of the specified Landsat scene directory

== Post-Processing ==

=== Natural color composites ===

Creating natural (also known as true-) color composites, can be done by

a) using {{cmd|i.landsat.rgb|version=64}} (GRASS 6.x) | {{cmd|i.colors.enhance|version=70}} (GRASS 7.x) to automatically balance the colors for the Red, Green and Blue bands

or

b) equalizing the colors on each of the Red, Green and Blue bands

<ul>
<source lang="bash">
r.colors -e map=band1 color=grey
</source>
</ul>

'''Composites''' can then be produced with the {{cmd|r.composite}} module.

'''Resetting the color tables''' of all bands back to normal greyscale can be done with a for loop:

<source lang="bash">
BASE=L71074092_09220040924

for map in `g.mlist pat="$BASE.[0-8]*"` ; do
r.colors $map color=grey255
done
</source>

See also:
* [http://courses.neteler.org/processing-landsat-8-data-in-grass-gis-7-rgb-composites-and-pan-sharpening/ Processing Landsat 8 data in GRASS GIS 7: RGB composites and pan sharpening]

=== Create a MASK to only show data where coverage exists for all bands ===

<source lang="bash">
BASE=L71074092_09220040924

g.region rast=$BASE.1
r.series in=`g.mlist pat="$BASE.[0-8]*" sep=,` -n out=$BASE.thresh method=threshold thresh=1
r.mapcalc "$BASE.mask = if(isnull($BASE.thresh))"
g.remove $BASE.thresh
</source>

=== Calculate Top-of-Atmosphere Reflectance and band-6 Temperature ===

Calculate ''Top-of-Atmosphere'' reflectance and band-6 temperature using the {{cmd|i.landsat.toar}} module. For details, refer to USGS' [http://landsat.usgs.gov/Landsat_Metadata_Changes.php Landsat Filename and Metadata Changes] dedicated page. For Landsat 8, see also [http://landsat.usgs.gov/about_LU_Vol_7_Issue_4.php#3a here].
<source lang="bash">
i.landsat.toar input_prefix=$BASE output_prefix=${BASE}_toar metfile=${BASE}_MTL.txt
</source>

Note, the resulting temperature map is in Kelvin:
<source lang="bash">
# convert to degree Celsius
r.mapcalc "$BASE.temp_celsius = ${BASE}_toar.6 - 273.15"
r.info -r $BASE.temp_celsius
</source>

=== Haze removal ===

Simple haze removal can be done with {{AddonCmd|i.landsat.dehaze|version=64}}. This addons applies a bandwise haze correction using tasscap4 (haze) and linear regression.

During the 2000s, prior acquired Landsat data were reprocessed to LPGS (Level 1 Product Generation System). Seems that with this level of processing, haze effect in raw data was removed and now is sufficient to apply {{Cmd|i.colors.enhance}} to obtain a good image with high contrast.

=== Atmospheric correction ===

See [[Atmospheric correction]]

=== Cloud identification ===

Identify clouds in the image with {{cmd|i.landsat.acca}}:
<source lang="bash">i.landsat.acca -f input_prefix=226_62_toar. output=226_62.acca_cloudmask</source>

Mask out the clouds:
<source lang="bash">r.mapcalc "MASK = if(isnull($BASE.acca_cloudmask))"</source>

== Download sample data ==

=== Preprocessed Landsat-7 data for North Carolina ===

The [[Sample_datasets|North Carolina 2008 sample dataset]] comes with 3 different Landsat scenes:
: (''Wake County -- path: 16 row: 35 for various dates'')

The above import efforts are not needed since the data are already in a GRASS location.

=== Landsat-5: Oct 14, 1987 ===

;Glovis download: LT50160351987287XXX08
: http://edcsns17.cr.usgs.gov/cgi-bin/EarthExplorer/run-phtml/results/download.phtml?node=GV&ordered=LT50160351987287XXX08&dataset_name=LANDSAT_TM



Provided metadata:
IMAGE_ID=P016R35_5T871014
PATH=16
ROW=35
DATE=10/14/87
PLATFORM=LANDSAT5

=== Landsat-7: Mar 31, 2000 ===

;Glovis download: LE70160352000091EDC00
: http://edcsns17.cr.usgs.gov/cgi-bin/EarthExplorer/run-phtml/results/download.phtml?node=GV&ordered=LE70160352000091EDC00&dataset_name=LANDSAT_ETM

Values in the metadata below indicate that the version provided with the NC 2008 dataset's production date was after July 1, 2000, and that the channel gains were <tt>HHHLHLHHL</tt>.

Convert DNs to radiance/temperatures:<source lang="bash">
GRASS> i.landsat.toar -v band=lsat7_2000 sensor=7 date=2000-03-31 \
product_date=2000-07-02 solar_elevation=51.5246529 gain=HHHLHLHHL</source>

Provided metadata:
SPACECRAFT_ID=Landsat7
SENSOR_ID=ETM+
'''ACQUISITION_DATE=2000-03-31'''
WRS_PATH=16
CPF_FILE_NAME=L7CPF20000101_20000331_12
SUN_AZIMUTH=139.6033279
'''SUN_ELEVATION=51.5246529'''
LMAX_BAND1=191.600
LMIN_BAND1=-6.200
LMAX_BAND2=196.500
LMIN_BAND2=-6.400
LMAX_BAND3=152.900
LMIN_BAND3=-5.000
LMAX_BAND4=241.100
LMIN_BAND4=-5.100
LMAX_BAND5=31.060
LMIN_BAND5=-1.000
LMAX_BAND61=17.040
LMIN_BAND61=0.000
LMAX_BAND62=12.650
LMIN_BAND62=3.200
LMAX_BAND7=10.800
LMIN_BAND7=-0.350
LMAX_BAND8=243.100
LMIN_BAND8=-4.700
QCALMAX_BAND1=255.0
QCALMIN_BAND1=1.0
QCALMAX_BAND2=255.0
QCALMIN_BAND2=1.0
QCALMAX_BAND3=255.0
QCALMIN_BAND3=1.0
QCALMAX_BAND4=255.0
QCALMIN_BAND4=1.0
QCALMAX_BAND5=255.0
QCALMIN_BAND5=1.0
QCALMAX_BAND61=255.0
QCALMIN_BAND61=1.0
QCALMAX_BAND62=255.0
QCALMIN_BAND62=1.0
QCALMAX_BAND7=255.0
QCALMIN_BAND7=1.0
QCALMAX_BAND8=255.0
QCALMIN_BAND8=1.0

=== Landsat-7: May 24, 2002 ===

;Glovis download: LE70160352002144EDC00
: http://edcsns17.cr.usgs.gov/cgi-bin/EarthExplorer/run-phtml/results/download.phtml?node=GV&ordered=LE70160352002144EDC00&dataset_name=LANDSAT_ETM



Provided metadata: (`p016r035_7x20020524.met`)
SPACECRAFT_ID=Landsat7
SENSOR_ID=ETM+
'''ACQUISITION_DATE=2002-05-24'''
WRS_PATH=016
WRS_ROW=035
SUN_AZIMUTH=120.8810347
'''SUN_ELEVATION=64.7730999'''
QA_PERCENT_MISSING_DATA=0
CLOUD_COVER=0
CPF_FILE_NAME=L7CPF20020401_20020630_03
LMAX_BAND1=191.600
LMIN_BAND1=-6.200
LMAX_BAND2=196.500
LMIN_BAND2=-6.400
LMAX_BAND3=152.900
LMIN_BAND3=-5.000
LMAX_BAND4=241.100
LMIN_BAND4=-5.100
LMAX_BAND5=31.060
LMIN_BAND5=-1.000
LMAX_BAND61=17.040
LMIN_BAND61=0.000
LMAX_BAND62=12.650
LMIN_BAND62=3.200
LMAX_BAND7=10.800
LMIN_BAND7=-0.350
LMAX_BAND8=243.100
LMIN_BAND8=-4.700
QCALMAX_BAND1=255.0
QCALMIN_BAND1=1.0
QCALMAX_BAND2=255.0
QCALMIN_BAND2=1.0
QCALMAX_BAND3=255.0
QCALMIN_BAND3=1.0
QCALMAX_BAND4=255.0
QCALMIN_BAND4=1.0
QCALMAX_BAND5=255.0
QCALMIN_BAND5=1.0
QCALMAX_BAND61=255.0
QCALMIN_BAND61=1.0
QCALMAX_BAND62=255.0
QCALMIN_BAND62=1.0
QCALMAX_BAND7=255.0
QCALMIN_BAND7=1.0
QCALMAX_BAND8=255.0
QCALMIN_BAND8=1.0

== LANDSAT Image classification ==

See [[Image classification]]

== Time series analysis ==

See [[Time series]]

== Sources ==

* [http://landsat.usgs.gov/tools_access_all_faqs.php Frequently Asked Questions about the Landsat Missions]
* [https://landsat8portal.eo.esa.int/portal/ European LANDSAT 8 data in near-realtime]
* [http://courses.neteler.org/processing-landsat8-data-in-grass-gis-7/ Processing Landsat 8 data in GRASS GIS 7: Import and visualization]
* [http://courses.neteler.org/processing-landsat-8-data-in-grass-gis-7-rgb-composites-and-pan-sharpening/ Processing Landsat 8 data in GRASS GIS 7: RGB composites and pan sharpening]

[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Landsat]]
[[Category: Image processing]]
[[Category: Import]]
[[Category: Digital Numbers]]
[[Category: Radiance]]
[[Category: Reflectance]]
[[Category: Geodata]]

ISO/INSPIRE Metadata Support

2015-08-20T12:31:59Z

⚠️Sbl: On ubuntu the installation instructions did not work out of the box. Hope I did not damage things for other OS...

== ISO 19115:2003- Geographic information -- Metadata ==
[http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020 ISO 19115:2003] defines the scheme required for description of geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal scheme, spatial reference, and distribution of digital geographic data.

== Catalogue Service for the Web ==
[http://www.opengeospatial.org/standards/cat]Catalogue services support the ability to publish and search collections of descriptive information (metadata) for data, services, and related information objects. Metadata in catalogues represent resource characteristics that can be queried and presented for evaluation and further processing by both humans and software. Catalogue services are required to support the discovery and binding to registered information resources within an information community.

= About =
Wx.metadata which was developed during Google Summer of Code 2014/2015 is currently available in GRASS add-ons.
* Package for creating and editing metadata according to EN ISO 19115, described here, consists of few modules. Modules r.info.iso, v.info.iso and t.info.iso are command line based and support conversion from current native metadata management (r.info, v.info,t.info) into ISO based metadata. GUI based module - g.gui.metadata offers advanced tools for management of metadata. For
[[Image:Wxmetadata-editing.png|center|600px]]

* Package also includs modue g.gui.cswbrowser for searching and browsing metadata catalog(csw). For advanced users there are few modeles for establishing and handling pycsw server:
* db.csw.admin - module for administration of pycsw server
* db.csw.run - module for starting server on localhost
* db.csw.harvest - modul for harvesting metadata between two csw.

= Requirements and installation =
* [http://grass.osgeo.org/download/software/#g71x GRASS GIS 7.1 ]
wx.metadata package has dependence on external libraries:

* pycsw package - development version(OGC CSW server implementation written in Python):
<source lang="bash">
git clone https://github.com/geopython/pycsw.git && cd pycsw
sudo pip install -e . && sudo pip install -r requirements-standalone.txt
</source>

* owslib package - development version (OGC CSW client implementation written in Python):
<source lang="bash">
git clone git://github.com/geopython/OWSLib.git
cd OWSLib && sudo python setup.py install
</source>

* Jinja2 (one of the most used template engines for Python)
<source lang="bash">
git clone https://github.com/mitsuhiko/jinja2.git
cd jinja2 && sudo python setup.py install
</source>

= Creating and editing metadata =
== Naming of metadata files and storage ==
Default location for exported metadata files is ''metadata'' directory in the map's mapset. For raster maps, the prefix derived from the current nomenclature is ''cell'', for vector maps ''vector''. File ends with .xml suffix.

For example default metadata file name for vector map "roads" is ''vector_roads.xml''.

== Metadata profile ==
The metadata profile defines attributes, which can be edited in this editor. The editor offers the already mentioned two profiles(Basic and Inspire). Editor also supports loading of customized profiles. See Creation of custom ISO based profile.

<big>Currently there are three build-in ISO profiles available: </big>
* '''The basic profile''' is substituted from intersection between items stored in GRASS native metadata format and INSPIRE profile. The intersect (subset) includes all available GRASS metadata. Metadata which cannot be assigned to ISO based attributes are stored in metadata attribute sabstractact.

* '''The Inspire profile''' fulfills the criteria of INSPIRE profile. In case if is not possible to get the values from native GRASS metadata, these are filled with text string '$NULL'. This rule is applied for both profiles.

* '''The temporal profile''' is based on the Grass basic profile and includes additional specific attributes for Temporal framework.

== Modules r.info.iso, v.info.iso t.info.iso ==
Command line based modules implements conversion of native GRASS metadata to ISO based XML metadata files. Identical configuration applies for both modules. Products of these modules differ partly in certain metadata attributes related to differences between raster (r.info) and vector (v.info) maps metadata.

'''Parameters of modules:'''
* map - selection of map for metadata creation
* profile - selection of metadata profile (basic or inspire)
* output - path to output XML metadata file. Default = according to naming&storage rules

== Module g.gui.metadata ==
Metadata editor (editor) includes graphical interface for conversion metadata from r.info and v.info to ISO based metadata, editing metadata files and creating metadata templates. In addition, the graphical module allows validating of INSPIRE and Basic profile.

=== Information about metadata item ===
Tooltip function helps to fill in the form correctly.
[[Image:Wxmetadata-tooltip.png|center|350]]

=== Creation of metadata ===
Editor offers two editing modes. The first one allows to create metadata from selected GRASS maps from an active location. The second one allows editing of external metadata file.

=== Fetching values from database backand ===
Editor automaticaly fetch keywords from SQLite GRASS GIS backend. Three well know dictionaries are added by default. User can manualy add dictionaries by sql commands.
Dictionaries are stored in table ''metadata_themes''

{| border="1" class="wikitable"
|+ teble metadta_themes
! Attribut
| title
| keyword
| date_iso
| date_type
|-
! Date type
| TEXT || TEXT|| TEXT|| TEXT
|-
! Example
|Example || GEMET - Concepts, version || 2010-01-13 || publication

|}

[[Image:Keywords.png|center|350]]

=== Exporting metadata reports to format PDF ===
This funciton allows to export metadata of GRASS maps to report in pdf format. The report template is based on INSPIRE profile. Unknown values of metadta atributes are filled by text $UNKNOWN.
[[Image:Pdfexp.png|center|350]]

{{YouTube|V7tgOOuRyuA}}

=== GRASS metadata map editor ===
[[Image:Wxmetadata-mapEdit.png|center|150px]]

Combo box for selection of ISO profile:
* basic
* inspire
* load custom – allows to load metadata profile from file. For example in case of using predefined template. The intersection of GRASS Basic profile(all available metadata for selected map) and loaded custom profile will proced with this selection.

{{YouTube|7V5NyVdO05o}}

=== External metadata editor ===
[[Image:Wxmetadata-externalEdit.png|center|150]]
This editor mode allows to load own template and xml file for editing. This option does not support any connection with GRASS maps metadata.

{{YouTube|npMAavbwfi0}}

=== Defining templates ===
This function allows to create pattern of metadata profile. In other words it support defining fixed values to template. With using created template, the editor does not initialize texts inputs of defined values. These attributes is able to see only in Tree Browser in editor. Direct link on this function is multiple editing mode (see below).
* If check-box of metadata attribute is checked, the OWSLib object in template will be replaced by value. Unchecked attributes will not change this 'part' of the template.
* The yellow background of text fields indicates metadata attributes, which are not possible get from GRASS map information.
[[Image:Wxmetadata-template.png|center|600px]]

=== Usage ===
* If check-box of metadata attribute is checked, the OWSLib object in template will be replaced by value. Unchecked attributes will not change this 'part' of the template.

example: Template result of attribute which is checked
<pre>
<gmd:dateStamp>
<gco:Date>2013-01-01</gco:Date>
</gmd:dateStamp>
</pre>

example: Template result of attribute which is unchecked
<pre>
<gmd:dateStamp>
<gco:Date>{{ md.datestamp }}{# tag="md.datestamp" , name="Metadata date" ,\
ref= "Part B 10.2" , desc= "Date that the metadata was created.",type = "date" ,
example = "2005-03-27" , multi= 0 , group= "Metadata" , multiline= False #}</gco:Date>
</gmd:dateStamp>
</pre>

Video shows record of simple practice of defining custom template
{{YouTube|Pu2sQoAJXfo}}

=== Editing metadata of multiple map selection ===
Advantages of this editing mode is in work using of defined template. This option can be used by selection of multiple maps in data catalog.

=== Validation of metadata profile ===
On the right side of editor is a validator of metadata. Currently, validator is able to validate two build-in profiles. For selection of profile “Load custom” is set by default the inspire profile.

=== Updating GRASS native metadata ===
The g.gui.metadata module allows updating native GRASS metadata with using modules r.support and v.support. The intersection between ISO based metadata and r|v.support is limited by available parameters for these modules.

=== Notes ===
* EPSG code must by added in url format. Information of projection is added only if EPSG code is known or if GDAL function for identifying from WKT is succesful.
<source lang="xml">
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<gmd:code>
<gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/3035</gco:CharacterString>
</gmd:code>
<gmd:codeSpace>
<gco:CharacterString>INSPIRE RS registry</gco:CharacterString>
</gmd:codeSpace>
</gmd:RS_Identifier>
</gmd:referenceSystemIdentifier>
</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>
</source>

= Tools for working with metadata catalogue (csw) =
== Browsing and searching -g.gui.cswbrowser ==
Module g.gui.cswbrowser(Browser) based graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS.
=== Connection manager ===
Connection manager allows:
* adding
* removing
* loading list of connections from file.
By default the Browser is initialized by list of few well known csw providers of csw. Button "Service info" shows metadata of the service.
User can manage connection in two ways:
* First one is with using hidden storage provided by [http://wxpython.org/Phoenix/docs/html/ConfigBase.html wx.Config]. This case is without accessing default connection file.
* After prompt user also can add/remove connection from default .xml file.
[[File:ConnectionMgr.png|600px|Connection manager in g.gui.cswbrowser]]

=== Searching ===
Before fetching data from selected csw server is proper to set up searching filter. Searching can be restricted by:
* DCMI Type (Collection , Dataset , Event , Image , InteractiveResource , MovingImage , PhysicalObject , Service , Software , Sound , StillImage , Text)
* Area(bounding box)
** current GRASS GIS computation region
** manually
* Keywords
** basic filter allows to use basic or advance keyword filtering. In the simple case user can define single keywords or multiple keywords with button "+". Logic operator between keywords is AND(&).
** second, advanced is based on OGC list of expressions which means that can be set filter with logic relations between keywords or sets of keywords. Dialogue for settings keywords text string is under "Advanced" check-box. Syntax of constraints is based on python list syntax. Each keywords must be in braces
[[File:Find1.png|600px|g.gui.cswbrowser, searching page]]
==== Advanced keywords filtering ====
On the left panel of Browser is placed check-box named "Advance". The keywords advanced dialogue allows to use basic bool operations.

*OR condition
a || b || c
["a","b","c"]
*AND condition
a && b && c
[ ["a","b","c"] ]
*composition
(a && b) || c || d || e
[["a","b"],["c"],["d"],["e"]] or [["a","b"],"c","d","e"]

=== Browsing results===
On the bottom of Browser is a controller for browsing results. The data from server are fetched by number of items per one transaction. Default is a 20 items. After selection of item in the result table, metadata of record should be displayed. Browser automatically enables buttons on the top of Browser if WMS, WCS or WFS services are available.

== CSW server management ==
wx.metadata package includes tools for establishing and handling pycsw server. Pycsw stuff consist:
*db.csw.admin
*db.csw.run
*db.csw.harvest
=== Setting up csw server- db.csw.admin ===

= Creation of custom ISO based profile =
Creation of own custom ISO based profile is with using Jinja template syntax and some addition rules.
The main item of template is composite from two braces.
Both of them are fully according to syntax of Jinja template. First holds information about statements of loop or condition and also simple Python object. Second braces according to Jinja template syntax is represented by comment {# #}. In this braces additional information for generating graphical interface of editor are stored. In addition also information about individual metadata attributes (name, example, description, multiplicity, etc) is included.

== The first braces ==
Contain object of OWSLib which holds the metadata value. This values can be object which is describing single variable or list of variables. Value of some attribute can be defined￹￹ many times(according to ISO). This attributes must be defined in block of template with starting statements and ending mark of block. Only allowed loop statement is FOR(see jinja2 manual). The XML based text of block will by duplicated according to number of items in the list.

== Initialize of OWSLib objects ==
Most object are initialized in configuration of file which is stored in wx.metadat/config/init_md.txt
example: Default configuration file for the build-in Basic and Inspire profile:
<pre>
self.md.identification = MD_DataIdentification()
self.md.dataquality = DQ_DataQuality()
self.md.distribution = MD_Distribution()
self.md.identification.extent = EX_Extent()
self.md.identification.extent.boundingBox = EX_GeographicBoundingBox()
</pre>
# on the left side of equation is obligatory prefix 'self.md'. Postfix(name of variable) is open. On right side is OWSLib object

== Single element ==
In case if the value of metadata element is declared only once:
example: Identifier
<pre>
{{ md.identifier }}
</pre>

example: Lineage
<pre>
{{ md.dataquality.lineage }}
</pre>

== Loop or Condition statements ==
Loops and condition are defined in by starting braces and ending braces '{% -%}' .
Start of block:

example: for statement
<pre>
{% for co in md.contact -%}
</pre>

Editor allows to use Python 'zip' function and 'len' function. Note- in Jinja syntax is Python len(length) function defined specifically.

example: zip
<pre>
{% for (u,d) in zip(md.identification.uom,md.identification.distance) -%}
</pre>

example: len
<pre>
{% if md.identification.denominators|length > 0 -%}
</pre>

End of block is defined by:

example: if statement
<pre>
{% endif -%}
</pre>

example: for statement
<pre>
{% endfor -%}
</pre>
== The second braces ==
The second braces(by Jinja syntax comment) contains these parameters:
* tag - just copy of string from first braces
* object – for reading and holding metadata in python objects is used OWSLib library.

Most of object are initialized by configuration file wx.metadata/config/init_md.txt. Some metadata attributes are necessary initialized directly in this(object) parameter. Best example is the metadata contact object(organization,email) which can be initialized for many times.

example: responsible party
<pre>
{% for co in md.contact -%}{# object="CI_ResponsibleParty()" #}
{{ co.organization }}{# object="CI_ResponsibleParty()" #}
{{ co.email }}{# object="CI_ResponsibleParty()" #}
{{ co.role }}{# object="CI_ResponsibleParty()" #}
{% endfor -%}
</pre>

* name – free text string describing the name of metadata item
* ref – free additional information. By default should be reference of ISO attributes
* type – data type characteristic. Input text field validator for 'email' and 'date' is implemented.
* desc – free text which should describe or define the characteristic of metadata item
* example – free text with example of the value for metadata item
* group- label of the notebook list(tab) in editor.
* inbox- label of the box which includes attributes from the block of Jinja template. All items from one block of Jinja template must be in same box(same name).
* multi- 0 or 1. In case 0, the item cannot be duplicated= text field widget does not contain button for duplicating itself. Note that only OWSLib list based variables can be used with duplication button.
* inboxmulti- 0 or 1. In case 0, the items in box cannot be duplicated = box with items not dispose with button for cloning self.
* multiline – True = initialize text field with multilines editing. Suitable for longer texts input

example of second braces:
<pre>
{# tag="md.dataquality.lineage" , name="Lineage" , ref= "Part B 6.1" ,/
desc= "General explanation of the data producers knowledge about the lineage of a dataset."/
,example = "Product 1 scenes correspond to the path/row of the Landsat orbit.." ,/
type ="string" , group= "Quality and Validity" , multiline= True #}
</pre>

== Syntax of Jinja template system and editor custom parser ==
* both of braces of one metadata element must be on same line
* after '{# ','{%' must be white space. Also before '#}' '-%}'

== Examples of template ==
[http://trac.osgeo.org/grass/browser/grass-addons/grass7/gui/wxpython/wx.metadata/templates?order=date&desc=1 INSPIRE and Basic]

Video tutorial shows practice of creation custom ISO profile.
{{YouTube|ahl41mFD5w0}}

= See also =
* [[GRASS Metadata Management]]
* [http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS Development page]

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

GRASS-QGIS relevant module list

2015-08-19T07:57:58Z

⚠️Sbl: r./v.import added

= GRASS modules available in the QGIS toolbox =
* See [[Development#GRASS_and_QGIS|GRASS and QGIS]] and [[QGIS GRASS Cookbook]]

== List of GRASS modules relevant to QGIS ==

=== Status Templates ===
{| class="wikitable1"
| Present in QGIS:
| {{ModuleAvailable}}
|-
| Present in QGIS but shouldn't be
|
|-
| Not present in QGIS - High Priority:
| {{ModuleNotAvailable}}
|-
| Not present in QGIS - Low Priority:
| {{ModuleNotAvailableLo}}
|-
| Not relevant to QGIS:
| {{ModuleNotRelevant}}
|}

* "Status" is for modules currently present in qgis source code dir src/plugins/grass/modules-*/
* Color coding indicates availability of module in the GRASS Toolbox

=== Database modules ===

{| class="wikitable sortable"
|+ db.* 
! Module
! Status
! Icon
! Comments
|-
| {{cmd|db.columns}}
| {{ModuleNotAvailableLo}}
|
| Is this really useful? Seems better to use standard QGIS commands for this
|-
| {{cmd|db.connect}}
| {{ModuleAvailable}}
| [[File:Db-connect.png]] [[File:Db-connect-schema.png]]
| login; generic, schema, which
|-
| {{cmd|db.copy}}
| {{ModuleAvailable}}
| [[File:Db-copy.png]]
|
|-
| {{cmd|db.describe}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|db.drivers}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|db.dropcol}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|db.droptable}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|db.execute}}
| {{ModuleAvailable}}
| [[File:Db-execute.png]]
|
|-
| {{cmd|db.in.ogr}}
| {{ModuleAvailable}}
| [[File:Db-import.png]]
|
|-
| {{cmd|db.login}}
| {{ModuleAvailable}}
| [[File:Db-login.png]]
|
|-
| {{cmd|db.out.ogr}}
| {{ModuleAvailable}}
| [[File:Db-export.png]]
|
|-
| {{cmd|db.select}}
| {{ModuleAvailable}}
| [[File:Data-select.png]]
|
|-
| {{cmd|db.tables}}
| {{ModuleNotAvailable}}
|
| To be realy useful, it should not be an additional command, but be added as an option to v.db.connect and similar commands (requires additional C++ coding)
|-
| {{cmd|db.test}}
| {{ModuleNotAvailableLo}}
|
|
|}

=== General modules ===

{| class="wikitable sortable"
|+ g.* 
! Module
! Status
! Comments
|-
| {{cmd|g.access}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.ask}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.copy}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.dirseps}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.extension}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.filename}}
|{{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.findetc}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.findfile}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.gisenv}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|g.gui}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.list}}
| {{ModuleNotRelevant}}
| Handled in the Toolbox
|-
| {{cmd|g.manual}}
| {{ModuleAvailable}}
|
|-
| {{cmd|g.mapset}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.mapsets}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.message}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.mkfontcap}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.mlist}}
| {{ModuleNotRelevant}}
| Handled in the Toolbox
|-
| {{cmd|g.mremove}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|g.parser}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.pnmcomp}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.proj}}
| {{ModuleAvailable}}
| generic, ascii, geo, print, proj
|-
| {{cmd|g.region}}
| {{ModuleAvailable}}
| save, zoom, multi-rast multi-vect
|-
| {{cmd|g.remove}}
| {{ModuleNotRelevant}}
| Handled in the Toolbox
|-
| {{cmd|g.rename}}
| {{ModuleNotRelevant}}
| Handled in the Toolbox
|-
| {{cmd|g.setproj}}
| {{ModuleNotAvailable|Lo}}
|Better to add it as an option to the "Create new location" wizard (requires additional C++ coding)
|-
| {{cmd|g.tempfile}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|g.transform}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|g.version}}
| {{ModuleNotRelevant}}
| Not really relevant
|}

=== Imagery modules ===

''Essentially these are raster modules that deal with satellite or aerial photography.''

{| class="wikitable sortable"
|+ i.* 
! Module
! Status
! Comments
|-
| {{cmd|i.atcorr}}
| {{ModuleNotAvailableLo}}
|Seems too complicated to be added - help needed (comment: see [[Atmospheric correction|tutorial]])
|-
| {{cmd|i.cca}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.class}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|i.cluster}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.fft}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.fusion.brovey}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.gensig}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.gensigset}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.group}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.his.rgb}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.ifft}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.image.mosaic}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.in.spotvgt}}
| {{ModuleAvailable}}
|
|-
| {{cmd|i.landsat.rgb}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.maxlik}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.oif}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.ortho.photo}}
| {{ModuleNotRelevant}}
| Not possible
|-
| {{cmd|i.pca}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|i.points}}
| {{ModuleNotRelevant}}
| Not possible
|-
| {{cmd|i.rectify}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|i.rgb.his}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|i.smap}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.spectral}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|i.target}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|i.tasscap}}
| {{ModuleAvailable}}
| common x3
|-
| {{cmd|i.vpoints}}
| {{ModuleNotRelevant}}
| Not possible
|-
| {{cmd|i.zc}}
|{{ModuleAvailable}}
| common
|}

=== Miscellaneous modules ===

{| class="wikitable sortable"
|+ m.* 
! Module
! Status
! Comments
|-
| {{cmd|m.cogo}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|m.proj}}
| {{ModuleAvailable}}
| common
|}

=== Paint modules ===

''These have been abandoned in GRASS 6.''

{| class="wikitable sortable"
|+ p.* 
! Module
! Status
! Comments
|-
| {{cmd|p.out.vrml}}
| {{ModuleNotRelevant}}
| old & renamed; not for QGIS
|}

=== PostScript modules ===

{| class="wikitable sortable"
|+ ps.* 
! Module
! Status
! Comments
|-
| {{cmd|ps.map}}
| {{ModuleNotRelevant}}
| QGIS has its own map composer, so this probably isn't needed.
|}

=== Raster modules ===

{| class="wikitable sortable"
|+ r.* 
! Module
! Status
! Comments
|-
| {{cmd|r.average}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.basins.fill}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.bilinear}}
| {{ModuleAvailable}}
| modules-6.4 ''Please use "r.resamp.interp" instead.''
|-
| {{cmd|r.bitpattern}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.blend}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.buffer}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.carve}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.category}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.cats}}
| {{ModuleNotRelevant}}
| Wrapper script for backwards compatibility.
|-
| {{cmd|r.circle}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.clump}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.coin}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.colors}}
| {{ModuleAvailable}}
| common x4, generic, rast, rules, table
|-
| {{cmd|r.colors.stddev}}
| {{ModuleAvailable}}
| modules-6.4
|-
| {{cmd|r.composite}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.compress}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.contour}}
| {{ModuleAvailable}}
| common x2
|-
| {{cmd|r.cost}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.covar}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.cross}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.describe}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.digit}}
| {{ModuleNotRelevant}}
| Not possible
|-
| {{cmd|r.distance}}
| {{ModuleAvailable}}
|
|-
| {{cmd|r.drain}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.external}}
| {{ModuleAvailable}}
| modules-6.4 x3
|-
| {{cmd|r.fill.dir}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.fillnulls}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.flow}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.grow}}
| {{ModuleAvailable}}
| 6.4/common
|-
| {{cmd|r.grow.distance}}
| {{ModuleAvailable}}
|
|-
| {{cmd|r.gwflow}}
| {{ModuleNotAvailableLo}}
| ground water flow modeling
|-
| {{cmd|r.his}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.horizon}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.import}}
| {{ModuleNotAvailable}}
|New since Community sprint in Como as a modified version of r.in.proj
|-
| {{cmd|r.in.arc}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.ascii}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.aster}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.bin}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.gdal}}
|{{ModuleAvailable}}
| common x4, generic, loc, qgis.loc, qgis
|-
| {{cmd|r.in.gridatb}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.mat}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.poly}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.srtm}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.in.wms}}
| {{ModuleAvailable}}
| common, somewhat brittle
|-
| {{cmd|r.in.xyz}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.info}}
| {{ModuleNotRelevant}}
| Handled in the Toolbox
|-
| {{cmd|r.kappa}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.lake}}
| {{ModuleAvailable}}
| common x3, generic, seed, xy
|-
| {{cmd|r.le.setup}}
| {{ModuleNotAvailable}}
|Creates configuration for r.le.* analysis modules. Requires a dedicated GUI.
|-
| {{cmd|r.le.patch}}
| {{ModuleNotAvailable}}
|
|-
| {{cmd|r.le.pixel}}
| {{ModuleNotAvailable}}
|
|-
| {{cmd|r.le.trace}}
| {{ModuleNotAvailable}}
|
|-
| {{cmd|r.li.setup}}
| {{ModuleNotAvailable}}
|Creates configuration file for r.li.* analysis modules. Requires a dedicated GUI.
|-
| {{cmd|r.li.cwed}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.dominance}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.edgedensity}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.mpa}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.mps}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.padcv}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.padrange}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.padsd}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.patchdensity}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.patchnum}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.richness}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.shannon}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.shape}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.li.simpson}}
| {{ModuleNotAvailable}}
|Done, but needs r.li.setup.
|-
| {{cmd|r.los}}
| {{ModuleAvailable}}
| common
|
|-
| {{cmd|r.mapcalc}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.mapcalculator}}
| {{ModuleAvailable}}
| common, gui wrapper (need both?)
|-
| {{cmd|r.mask}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.median}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.mfilter}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.mfilter.fp}}
| {{ModuleAvailable}}
|
|-
| {{cmd|r.mode}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.neighbors}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.null}}
| {{ModuleAvailable}}
| common x4, null, to, val, r.to.null?
|-
| {{cmd|r.out.arc}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.ascii}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.bin}}
| {{ModuleAvailable}}
|
|-
| {{cmd|r.out.gdal}}
| {{ModuleAvailable}}
| common x2 generic, GeoTiff
|-
| {{cmd|r.out.gdal.sh}}
| {{ModuleNotAvailableLo}}
| old full map extent version
|-
| {{cmd|r.out.gridatb}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.mat}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.mpeg}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.png}}
| {{ModuleAvailable}}
| common, important once transparency and Worldfile gets backported from 6.5svn (for OpenLayers/KML tile source)
|-
| {{cmd|r.out.pov}}
| {{ModuleAvailable}}
| common POVray
|-
| {{cmd|r.out.ppm}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.ppm3}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.tiff}}
| {{ModuleAvailable}}
| common, ''visual'' RGB output, not data values (use r.out.gdal for that)
|-
| {{cmd|r.out.vrml}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.vtk}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.out.xyz}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.param.scale}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.patch}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.plane}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.profile}}
| {{ModuleNotAvailableLo}}
| Python plugin available to find transect profile
|-
| {{cmd|r.proj}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.quant}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.quantile}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.random}}
| {{ModuleAvailable}}
|
|-
| {{cmd|r.random.cells}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.random.surface}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.reclass}}
| {{ModuleAvailable}}
| common x2, generic, file
|-
| {{cmd|r.reclass.area}}
| {{ModuleAvailable}}
| common x3, generic, greater, lesser
|-
| {{cmd|r.recode}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.region}}
| {{ModuleAvailable}}
| Oversold?, common x6, generic, rast, vect, region, edge, alignTo
|-
| {{cmd|r.regression.line}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.report}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.resamp.interp}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.resamp.rst}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.resamp.stats}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.resample}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.rescale}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.rescale.eq}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.ros}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.series}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.shaded.relief}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.sim.sediment}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|r.sim.water}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.slope.aspect}}
| {{ModuleAvailable}}
| common x2, slope, aspect, '''but not others'''
|-
| {{cmd|r.spread}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.spreadpath}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.statistics}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.stats}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.sum}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.sun}}
| {{ModuleNotAvailable|Lo}}
|
|-
| {{cmd|r.sunmask}}
| {{ModuleAvailable}}
| common x2, date_time, position
|-
| {{cmd|r.support}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.support.stats}}
| {{ModuleAvailable}}
| common, maybe not needed
|-
| {{cmd|r.surf.area}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.surf.contour}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.surf.fractal}}
| {{ModuleAvailable}}
| 6.3/6.4
|-
| {{cmd|r.surf.gauss}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.surf.idw}}
| {{ModuleAvailable}}
| common, faster
|-
| {{cmd|r.surf.idw2}}
| {{ModuleAvailable}}
| common, supports floating point
|-
| {{cmd|r.surf.random}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.terraflow}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.terraflow.short}}
| {{ModuleNotRelevant}}
| Not needed
|-
| {{cmd|r.texture}}
| {{ModuleAvailable}}
| common x2, generic, bis
|-
| {{cmd|r.thin}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.tileset}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|r.timestamp}}
| {{ModuleNotRelevant}}
|
|-
| {{cmd|r.to.rast3}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.to.rast3elev}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.to.vect}}
| {{ModuleAvailable}}
| common x3, point, line, area
|-
| {{cmd|r.topidx}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.topmodel}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r.transect}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.univar}}
| {{ModuleAvailable}}
| common
|
|-
| {{cmd|r.univar.sh}}
| {{ModuleNotRelevant}}
| Not needed
|-
| {{cmd|r.volume}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.walk}}
| {{ModuleAvailable}}
|
|
|-
| {{cmd|r.water.outlet}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.watershed}}
| {{ModuleAvailable}}
| common
|-
| {{cmd|r.what}}
| {{ModuleNotRelevant}}
| Handled in the QGIS GUI
|-
| {{cmd|r.what.color}}
| {{ModuleNotRelevant}}
|
|-
|}

=== 3D raster modules ===

{| class="wikitable sortable"
|+ r3.* 
! Module
! Status
! Comments
|-
| {{cmd|r3.cross.rast}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.gwflow}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.in.ascii}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.in.v5d}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.info}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.mapcalc}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.mapcalculator}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.mask}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.mkdspf}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.null}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.out.ascii}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.out.v5d}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.out.vtk}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.stats}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.timestamp}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.to.rast}}
| {{ModuleNotAvailableLo}}
|
|-
| {{cmd|r3.univar}}
| {{ModuleNotAvailableLo}}
|
|}

=== Vector modules ===

{| class="wikitable sortable"
|+ v.* 
! Module
! Status
! Icon
! Comments
|-
| {{cmd|v.buffer}}
| {{ModuleAvailable}}
|
| 6.3/6.4, https://trac.osgeo.org/grass/ticket/994
|-
| {{cmd|v.build}}
| {{ModuleAvailable}}
|
| see specific modules
|-
| {{cmd|v.build.all}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.build.polylines}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.category}}
| {{ModuleAvailable}}
|
| common x4, add, del, sum, change
|-
| {{cmd|v.centroids}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.class}}
| {{ModuleNotAvailableLo}}
|
| Fuctionality supplied in QGIS Vector symbology
|-
| {{cmd|v.clean}}
| {{ModuleAvailable}}
|
| common x13
|-
| {{cmd|v.colors}}
| {{ModuleNotRelevant}}
|
| Fuctionality supplied in QGIS Vector symbology
|-
| {{cmd|v.convert}}
| {{ModuleNotRelevant}}
|
| For loading in old GRASS 4/5 vector data format. Not needed by QGIS.
|-
| {{cmd|v.convert.all}}
| {{ModuleNotRelevant}}
|
| For loading in old GRASS 4/5 vector data format. Not needed by QGIS.
|-
| {{cmd|v.db.addcol}}
| {{ModuleAvailable}}
| [[File:Table-field-create.png]]
| common
|-
| {{cmd|v.db.addtable}}
| {{ModuleAvailable}}
| [[File:Table-create.png]]
| common
|-
| {{cmd|v.db.connect}}
| {{ModuleAvailable}}
| [[File:Db-connect.png‎]]
| common, v.db.sconnect? v.db.what.connect?
|-
| {{cmd|v.db.dropcol}}
| {{ModuleAvailable}}
| [[File:Table-field-delete.png]]
| modules-6.4
|-
| {{cmd|v.db.droptable}}
| {{ModuleAvailable}}
| [[File:Table-delete.png]]
| common
|-
| {{cmd|v.db.join}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.db.reconnect.all}}
| {{ModuleAvailable}}
|
| common
|
|-
| {{cmd|v.db.renamecol}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.db.select}}
| {{ModuleAvailable}}
|
| 6.3/6.4 x2
|-
| {{cmd|v.db.univar}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.db.update}}
| {{ModuleAvailable}}
|
| common x4, const, op, op query, query
|-
| {{cmd|v.delaunay}}
| {{ModuleAvailable}}
|
| common x2, line, area
|-
| {{cmd|v.digit}}
| {{ModuleNotRelevant}}
|
| Not possible
|-
| {{cmd|v.dissolve}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.distance}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.drape}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.edit}}
| {{ModuleNotAvailable}}
|
|Requires an ad hoc GUI (more C++ coding)
|-
| {{cmd|v.external}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.extract}}
| {{ModuleAvailable}}
|
| common, list, where
|-
| {{cmd|v.extrude}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.generalize}}
| {{ModuleAvailable}}
|
| common, complicated
|-
| {{cmd|v.hull}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.import}}
| {{ModuleNotAvailable}}
|
|New since Community sprint in Como as a modified version of v.in.proj
|-
| {{cmd|v.in.ascii}}
| {{ModuleAvailable}}
|
|Added in r14546
|-
| {{cmd|v.in.db}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.in.dxf}}
| {{ModuleAvailable}}
|
| common x2, generic, multi
|-
| {{cmd|v.in.e00}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.in.garmin}}
| {{ModuleAvailable}}
|
| common, only for old serial models
|-
| {{cmd|v.in.geonames}}
| {{ModuleAvailable}}
|
| modules-6.4
|-
| {{cmd|v.in.gns}}
| {{ModuleAvailable}}
|
| modules-6.4
|-
| {{cmd|v.in.gpsbabel}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.in.lines|version=65}}
| {{ModuleAvailable}}
|
| Only in 6.5svn, new wrapper script around v.in.mapgen with more obvious name
|-
| {{cmd|v.in.mapgen}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.in.ogr}}
| {{ModuleAvailable}}
|
| common x7
|-
| {{cmd|v.in.region}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.in.sites}}
| {{ModuleNotRelevant}}
|
| For loading in old GRASS 4/5 vector data format. Not needed by QGIS.
|-
| {{cmd|v.in.sites.all}}
| {{ModuleNotRelevant}}
|
| For loading in old GRASS 4/5 vector data format. Not needed by QGIS.
|-
| {{cmd|v.in.wfs}}
| {{ModuleNotAvailable}}
|
|Requires curl (not always available); errors with some servers
|-
| {{cmd|v.info}}
| {{ModuleNotRelevant}}
|
| Functionality supplied in Toolbox
|-
| {{cmd|v.kcv}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.kernel}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.krige.py}}
| {{ModuleNotAvailable|Lo}}
|
|Available only from GRASS 6.5
|-
| {{cmd|v.label}}
| {{ModuleNotRelevant}}
|
| Functionality supplied in QGIS GUI
|-
| {{cmd|v.label.sa}}
| {{ModuleNotRelevant}}
|
| Functionality supplied in QGIS GUI
|-
| {{cmd|v.lidar.correction}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.lidar.edgedetection}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.lidar.growing}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.lrs.create}}
| {{ModuleNotAvailableLo}}
|
| Python plugin for Linear Referencing available
|-
| {{cmd|v.lrs.label}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.lrs.segment}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.lrs.where}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.mkgrid}}
| {{ModuleAvailable}}
|
| common, by region (by coord is a custom graticule creator)
|-
| {{cmd|v.neighbors}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.nodes}}
| {{ModuleAvailable}}
|
|
|-
| {{cmd|v.net.alloc}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.allpairs}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.bridge}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.centrality}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.components}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.connectivity}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.distance}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.flow}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.iso}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.path}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.salesman}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.spanningtree}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.steiner}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.net.timetable}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.net.visibility}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.normal}}
| {{ModuleNotAvailableLo}}
|
| common
|-
| {{cmd|v.out.ascii}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.out.dxf}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.out.gpsbabel}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.out.ogr}}
| {{ModuleAvailable}}
|
| 6.3/6.4/common x4, shapefile, generic, gml, mapinfo; 6.x: PostgreSQL
|-
| {{cmd|v.out.pov}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.out.svg}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.out.vtk}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.outlier}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.overlay}}
| {{ModuleAvailable}}
|
| common x4, and, or, not, xor
|-
| {{cmd|v.parallel}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.patch}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.perturb}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.proj}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.qcount}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.random}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.rast.stats}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.reclass}}
| {{ModuleAvailable}}
|
| common x2, attr, file
|-
| {{cmd|v.report}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.sample}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.segment}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.select}}
| {{ModuleAvailable}}
|
| common, v.select.overlap
|-
| {{cmd|v.split}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.support}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.surf.bspline}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.surf.idw}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.surf.rst}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.to.3d}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.to.db}}
| {{ModuleAvailable}}
|
| 6.3/6.4
|-
| {{cmd|v.to.points}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.to.rast}}
| {{ModuleAvailable}}
|
| common x2, attr, constant
|-
| {{cmd|v.to.rast3}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.transform}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.type}}
| {{ModuleAvailable}}
|
| common x4, b2l, l2b, c2p, p2c
|-
| {{cmd|v.univar}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.univar.sh}}
| {{ModuleNotRelevant}}
|
| old, not needed
|-
| {{cmd|v.vol.rst}}
| {{ModuleNotAvailableLo}}
|
|
|-
| {{cmd|v.voronoi}}
| {{ModuleAvailable}}
|
| common x2, line, area; https://trac.osgeo.org/grass/ticket/957
|-
| {{cmd|v.what}}
| {{ModuleNotRelevant}}
|
| QGIS GUI supplies query at location function
|-
| {{cmd|v.what.rast}}
| {{ModuleAvailable}}
|
| common
|-
| {{cmd|v.what.vect}}
| {{ModuleAvailable}}
|
| common
|}

=== GUI and command modules ===
{| class="wikitable sortable"
|+ GUI modules 
! Module
! Status
! Comments
|-
| {{cmd|gis.m}}
| {{ModuleNotRelevant}}
| Not relevant
|-
| {{cmd|nviz}}
| {{ModuleAvailable}}
| common
|-
| shell
| {{ModuleAvailable}}
| common
|-
| {{cmd|xganim}}
| {{ModuleNotAvailableLo}}
|
|}

=== Display modules ===

{| class="wikitable "
|+ d.* 
|-
| '' None of the display modules will be relevant. Display functionality is handled in the QGIS GUI. ''

<!--
! Module
! Priority
! Status
! Comments
|-
| {{cmd|d.ask}}
|
|
|
|-
| {{cmd|d.barscale}}
|
|
|
|-
| {{cmd|d.colorlist}}
|
|
|
|-
| {{cmd|d.colors}}
|
|
|
|-
| {{cmd|d.colortable}}
|
|
|
|-
| {{cmd|d.correlate}}
|
|
|
|-
| {{cmd|d.erase}}
|
|
|
|-
| {{cmd|d.extend}}
|
|
|
|-
| {{cmd|d.extract}}
|
|
|
|-
| {{cmd|d.font}}
|
|
|
|-
| {{cmd|d.font.freetype}}
|
|
|
|-
| {{cmd|d.frame}}
|
|
|
|-
| {{cmd|d.geodesic}}
|
|
|
|-
| {{cmd|d.graph}}
|
|
|
|-
| {{cmd|d.grid}}
|
|
|
|-
| {{cmd|d.his}}
|
|
|
|-
| {{cmd|d.histogram}}
|
|
|
|-
| {{cmd|d.info}}
|
|
|
|-
| {{cmd|d.labels}}
|
|
|
|-
| {{cmd|d.legend}}
|
|
|
|-
| {{cmd|d.linegraph}}
|
|
|
|-
| {{cmd|d.m}}
|
|
|
|-
| {{cmd|d.mapgraph}}
|
|
|
|-
| {{cmd|d.measure}}
|
|
|
|-
| {{cmd|d.menu}}
|
|
|
|-
| {{cmd|d.mon}}
|
|
|
|-
| {{cmd|d.monsize}}
|
|
|
|-
| {{cmd|d.mvmon}}
|
|
|
|-
| {{cmd|d.nviz}}
|
|
|
|-
| {{cmd|d.out.file}}
|
|
|
|-
| {{cmd|d.out.gpsdrive}}
|
|
|
|-
| {{cmd|d.out.png}}
|
|
|
|-
| {{cmd|d.paint.labels}}
|
|
|
|-
| {{cmd|d.path}}
|
|
|
|-
| {{cmd|d.polar}}
|
|
|
|-
| {{cmd|d.profile}}
|
|
|
|-
| {{cmd|d.rast}}
|
|
|
|-
| {{cmd|d.rast.arrow}}
|
|
|
|-
| {{cmd|d.rast.edit}}
|
|
|
|-
| {{cmd|d.rast.leg}}
|
|
|
|-
| {{cmd|d.rast.num}}
|
|
|
|-
| {{cmd|d.redraw}}
|
|
|
|-
| {{cmd|d.resize}}
|
|
|
|-
| {{cmd|d.rgb}}
|
|
|
|-
| {{cmd|d.rhumbline}}
|
|
|
|-
| {{cmd|d.save}}
|
|
|
|-
| {{cmd|d.shadedmap}}
|
|
|
|-
| {{cmd|d.slide.show}}
|
|
|
|-
| {{cmd|d.split}}
|
|
|
|-
| {{cmd|d.split.frame}}
|
|
|
|-
| {{cmd|d.text}}
|
|
|
|-
| {{cmd|d.text.freetype}}
|
|
|
|-
| {{cmd|d.thematic.area}}
|
|
|
|-
| {{cmd|d.title}}
|
|
|
|-
| {{cmd|d.vect}}
|
|
|
|-
| {{cmd|d.vect.chart}}
|
|sortable"
|+ 

[[Category: Development]]
[[Category: QGIS]]

AddOns/GRASS7/vector

2014-09-24T11:03:57Z

⚠️Sbl: Added v.lidar.mcc addon

{{AddOns}}
See also
svn co https://svn.osgeo.org/grass/grass-addons/grass7/vector/

==== v.area.weigh ====

{{AddonSrc|vector|v.area.weigh|version=7}} creates a raster surface from vector areas using known cell weights and preserving the value of the area attribute. For example, if the selected area attribute is the population count, the sum of all pixel values in a given area is equal to the area's population count with the area's population concentrated on the known location of urban areas.

: '''Author:''' Markus Metz

==== v.build.pg ====

{{AddonSrc|vector|v.build.pg|version=7}} builds PostGIS topology for feature tables linked via v.external.

==== v.centerpoint ====

{{AddonSrc|vector|v.centerpoint|version=7}} calculates various center points for points, lines and areas: center of gravity, geometric median etc.

: '''Author:''' Markus Metz

==== v.class.mlpy ====

{{AddonSrc|vector|v.class.mlpy|version=7}} classifies vector features. It is an interface to the [http://mlpy.sourceforge.net mlpy library] (Machine Learning Python). Classification is supervised and based on attribute table data. Geometry is not used. A training dataset is always required.

==== v.colors2 ====

{{AddonSrc|vector|v.colors|version=7}} is much like r.colors, but may be used for vector maps.

==== v.concave.hull ====

{{AddonSrc|vector|v.concave.hull|version=7}} creates a concave hull describing the shape of point clouds.

==== v.delaunay3d ====

{{AddonSrc|vector|v.delaunay3d|version=7}} creates a 3D triangulation from an input vector map containing points or centroids.

Requires [http://www.cgal.org CGAL library].

: '''Author:''' Martin Landa

==== v.external.all ====

{{AddonSrc|vector|v.external.all|version=7}} creates (using v.external) in the current mapset new pseudo-vector maps for all OGR layers from given OGR datasource (dsn option).

==== v.habitat.dem ====

{{AddonSrc|vector|v.habitat.dem|version=7}} calculates DEM and solar derived characteristics of habitat polygons.

: '''Author:''' Helmut Kudrnovsky

==== v.in.geopaparazzi ====

{{AddonSrc|vector|v.in.geopaparazzi|version=7}} imports all elements saved into [http://code.google.com/p/geopaparazzi/ Geopaparazzi].

==== v.in.ply ====

{{AddonSrc|vector|v.in.ply|version=7}} is a C program that imports a PLY file and writes it as GRASS vector map.

: '''Author:''' Markus Metz

==== v.in.redwg ====

: [http://lists.gnu.org/archive/html/info-libredwg/2010-08/msg00000.html v.in.redwg imports DWG files into GRASS.], see also [https://svn.osgeo.org/grass/grass-addons/grass7/vector/v.in.redwg here]

:'''Author:''' Rodrigo Rodrigues da Silva

==== v.in.wfs2 ====

{{AddonSrc|vector|v.in.wfs2|version=7}} imports OGC WFS maps (Web Feature Service) from external servers.

==== v.lidar.mcc ====

{{AddonSrc|vector|v.lidar.mcc|version=7}} applies a Multi Curvature Classification procedure on LiDAR point clouds e.g. for filtering vegetation returns. The module is also usable for discrete LiDAR.

: '''Author:''' Stefan Blumentrath

==== v.median ====

{{AddonSrc|vector|v.median|version=7}} create the median point of a cloud of point.

==== v.net.salesman.opt ====

{{AddonSrc|vector|v.net.salesman.opt|version=7}} estimates the optimal route to visit nodes on a vector network and optionally tries to improve the result.

==== v.out.ply ====

{{AddonSrc|vector|v.out.ply|version=7}} is a C program that exports a GRASS vector map as PLY file.

: '''Author:''' Markus Metz

==== v.ply.rectify ====

{{AddonSrc|vector|v.ply.rectify|version=7}} imports a PLY point cloud, georeferences and exports it. The first three vertex properties must be the x, y, z coordinates with property names "x", "y", "z", in this order.

: '''Author:''' Markus Metz

==== v.surf.icw ====

{{AddonSrc|vector|v.surf.icw|version=7}}:
Inverse cost weighting is like inverse distance weighted (IDW) interpolation, but uses cost instead of shortest Euclidean distance. In this way solid barriers and molasses zones may be correctly taken into account.

: '''Author:''' Hamish Bowman

==== v.to.lines ====

{{AddonSrc|vector|v.to.lines|version=7}}:
converts vector polygons (boundaries) to lines as well as vector points to lines via triangulations.

: '''Author:''' Luca Delucchi

==== v.surf.mass ====

{{AddonSrc|vector|v.surf.mass|version=7}} creates a raster surface from vector areas, preserving the value of the area attribute. For example, if the selected area attribute is the population count, the sum of all pixel values in a given area is equal to the area's population count. ([http://svn.osgeo.org/grass/grass-addons/grass7/vector/v.surf.mass/v.surf.mass.html manual page])

: '''Author:''' Markus Metz

GRASS Community Sprint Portland 2014

2014-09-23T20:05:45Z

⚠️Sbl: Update manual page status

The GRASS GIS [[team]] will participate in the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint Portland Code Sprint 2014] at FOSS4G 2014 in US. The sprint will be held the day after the main conference ('''Saturday, September 13th''' 2014).

== Purpose ==
This '''Portland FOSS4G Code Sprint 2014''' is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. This code sprint is targeting members of OSGeo software projects.

For this meeting, we welcome people committed to improving the '''GRASS GIS project''' and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others. We'll try to make a major step forward towards a stable GRASS GIS 7 release.

== Sponsors ==

We welcome inkind as well as direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

The Portland event is especially interesting since important OSGeo projects come together!

=== Thanks to our sponsors ===



We are greatful to the organizers of FOSS4G Portland and to the Eliot Center for hosting us!

== Timing ==

'''When''': '''Saturday, September 13th''' 2014

'''Duration''': One day

WHEN: '''08:00 until 16:00''' (although the building will be open into the evening)

WHERE: The sprint will be in the [http://eliotcenterportland.org Eliot Center] ([http://osm.org/go/WIDlUtpOQ-?m=&relation=186579 OSM]) along side [http://wherecamppdx.org WhereCampPDX].

== Venue ==

The sprint will be in the [http://eliotcenterportland.org Eliot Center] ([http://osm.org/go/WIDlUtpOQ-?m=&relation=186579 OSM]) along side [http://wherecamppdx.org WhereCampPDX].

== Accommodation and Costs ==

Please check on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint page of the sprint] more information about accommodation and cost. The participation is free of charge. However, participants should plan for the following costs:

* Travel to Portland
* Accommodation
* Breakfast and dinner (partly)

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution or modify this wiki.

Further details about the action items you '''find [[Talk:GRASS Community Sprint Portland 2014|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Ideas ===

Please edit this wiki page!

==== GRASS GIS 7 release related ====
* http://trac.osgeo.org/grass/wiki/Grass7Planning
** Fix the few remaining http://trac.osgeo.org/grass/wiki/Grass7Planning#Blockers
** Decide an official sample dataset for TGRASS, see {{trac|2259}} (comment 4)
* ...
* Last call for options keys, values and flags consolidation, use {{trac|2409}} to coordinate

==== Manual improvements ====
* Update the remaining "empty" manual pages (<<--- power users, please contribute!)
In order to coordinate efforts (also with people working from remote places) it would be helpful if volunteers sign up in the table below, for a manual they would feel comfortable to fill. Please feel free to add other modules which need a manual update or with missing manual pages... Regarding examples for the TGRASS modules see also discussion here: http://lists.osgeo.org/pipermail/grass-dev/2014-April/068556.html
And for
{| class="wikitable"
|-
! Module with incomplete manual !! Who !! Status !! Link
|-
| t.rast.out.vtk || || TBD || http://grass.osgeo.org/grass71/manuals/t.rast.out.vtk.html
|-
| t.rast.to.rast3 || || TBD || http://grass.osgeo.org/grass71/manuals/t.rast.to.rast3.html
|-
| t.rast3d.extract || || TBD || http://grass.osgeo.org/grass71/manuals/t.rast3d.extract.html
|-
| t.rast3d.list || ? || {{done}} || http://grass.osgeo.org/grass71/manuals/t.rast3d.list.html
|-
| t.rast3d.mapcalc || || TBD || http://grass.osgeo.org/grass71/manuals/t.rast3d.mapcalc.html
|-
| t.rast3d.univar || ? || Check page || http://grass.osgeo.org/grass71/manuals/t.rast3d.univar.html
|-
| t.remove || Stefan B. || {{done}} || http://grass.osgeo.org/grass71/manuals/t.remove.html
|-
| t.sample || || TBD || http://grass.osgeo.org/grass71/manuals/t.sample.html
|-
| t.support || || TBD || http://grass.osgeo.org/grass71/manuals/t.support.html
|-
| t.topology || || TBD || http://grass.osgeo.org/grass71/manuals/t.topology.html
|-
| t.unregister || ? || {{done}} || http://grass.osgeo.org/grass71/manuals/t.unregister.html
|-
| t.vect.db.select || || TBD || http://grass.osgeo.org/grass71/manuals/t.vect.db.select.html
|-
| t.vect.export || Eric G. || {{done}} || http://grass.osgeo.org/grass71/manuals/t.vect.export.html
|-
| t.vect.extract || Stefan B. || TBD || http://grass.osgeo.org/grass71/manuals/t.vect.extract.html
|-
| t.vect.import || Eric G. || {{done}} || http://grass.osgeo.org/grass71/manuals/t.vect.import.html
|-
| t.vect.list || ? || {{done}} || http://grass.osgeo.org/grass71/manuals/t.vect.list.html
|-
| t.vect.observe.strds || || TBD || http://grass.osgeo.org/grass71/manuals/t.vect.observe.strds.html
|-
| t.vect.univar || || TBD || http://grass.osgeo.org/grass71/manuals/t.vect.univar.html
|-
| t.vect.what.strds || || TBD || http://grass.osgeo.org/grass71/manuals/t.vect.what.strds.html
|-
| More? || || ||
|}
* add more examples to the manual which in turn can be used for the new [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS Testing framework for GRASS GIS]
* <strike>change TOC to collapse style with mouse-over expansion</strike>: [http://grass.osgeo.org/grass71/manuals/ new manual style]
* clone http://grasswiki.osgeo.org/wiki/Quick_wxGUI_tutorial into new one for GRASS 7 (and replace therein "random surface" with WMS etc)
* ...

==== New funding model to facilitate payed GRASS GIS programming ====
* in order to get annoying/boring issues fixed, try a crowd funding approach, eg Kickstarter
** identify GRASS issues to be fixed for cash
** discuss how to select the programmers
** example: http://zim-wiki.org/contribute.html --> Bounties

==== Testing framework ====
* <strike>how to write tests for the new [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS testing framework] and general presentation</strike>
* discuss relation to benchmarking (https://github.com/jachym/grass-performace)
* write closing Future work statement (TODO list) for related GSoC project

==== Module fixes related ====
* <strike>get g.gui.rlisetup working for circular buffers </strike> (see [http://lists.osgeo.org/pipermail/grass-user/2014-August/070799.html step-by-step example]) [need some testing] {{changeset|61866}}
* <strike>fix v.to.lines in Addons and move it to main GRASS GIS 7</strike> {{changeset|61923}}
* <strike>fix r.li.daemon memory leak</strike>: fixed in {{changeset|61812}} <<-- testing needed, use examples
* <strike>TGRASS: fix numbers in aggregate: tempmean_seasonal_9 --> tempmean_seasonal_0009 | see animation tool where it is solved</strike> {{changeset|61888}}
* <strike>port grass64/raster/r.out.vrml/ to GRASS 7 for 3D printing:</strike> it is {{cmd|r.out.vrml|version=70}}
* check wxGUI r.colors tool for integer maps (may show as FP maps): {{trac|2202}}
* check patch for *.colors.out {{trac|2399}}
* complete r.reclass.area improvements (LD + MN)
* ...

==== Web site: related ====
* simplify http://grass.osgeo.org/download/software/ms-windows/
* OSGeoREL: add parsable "GRASS GIS" tag to [http://wiki.osgeo.org/wiki/Edu_current_initiatives#Current_members_of_the_ICA-OSGeo_Network table of OSGeoREL labs] - then we could showcase them easily in the GRASS CMS
* ...

==== GDAL/OGR interface ====

* Patch for GDAL-GRASS plugin for GRASS 7: fix patch in https://trac.osgeo.org/gdal/ticket/2953

== Participation ==

=== In person ===
Please fill the related table on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint#GRASS_GIS wiki page of the sprint].

=== Via IRC chat or hangout===

==== IRC ====
: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

==== Hangout/Videobridge ====

There is the option to use Google+ Hangout, it is technically limited to 10 people and may require everyone to have G+ social media accounts to participate. More [http://www.google.com/+/learnmore/hangouts/ Information on G+ hangout].

Similarly multi-video conference calls can be done with Skype if the conference call initiator is a paid-up commercial Skype customer.

The FOSS [http://www.jitsi.org Jitsi] VoIP, IM, and video conferencing software produces a trivial to set up [https://jitsi.org/Projects/JitsiVideobridge VideoBridge] server software to the same. '''''New:''''' https://meet.jit.si -- zero-conf free no-accounts needed video conferencing; chat, etherpad, and prezi built in. (needs recent Opera or Chrome/Chromium with WebRTC support)

Further discussion on the pros and cons of these can be found on the [[Talk:GRASS_Community_Sprint_Prague_2013|Talk side of this wiki page]].

Please add yourself here below (please add also your gmail account for G+ hangout):
* ...

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (USA {{wikipedia|File:A_plug.jpg|(Type A)}} {{wikipedia|File:B_plug.jpg|(Type B)}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

Perhas during the event :)

== Photos ==

...

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS Community Sprint Vienna 2014]]!
* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Neteler|Markus Neteler]], ... (add)

== Press Release ==

...

[[Category:Workshops]]

Talk:GRASS Community Sprint Portland 2014

2014-09-14T21:28:27Z

⚠️Sbl: Individual report: Stefan Blumentrath

== Reports ==

<center>
[[Image:Portland2014 grassgis7 code sprint.jpg|400px|GRASS GIS 7 sprint team at FOSS4G 2014, Portland (OR), USA]]

GRASS GIS 7 sprint team at FOSS4G 2014, Portland (OR), USA
</center>

=== Overall ===

* heavy backporting to release_branch70 activity
* ...

=== Individual reports ===
==== Stefan Blumentrath (remote) ====
* attended such an event for the first time and had a great deal of fun!
* wrote manual page for t.remove (and started working on t.unregister)
* found out that writing manual pages can be very instructive and helps understanding details of the respective modules as well as it gives a deeper insight into the TGIS concept in general
* can recommend the experience to other users and is looking forward to a next occasion
* will continue working on the other manual pages as time permits

==== Vaclav Petras ====
* Move r.los to GRASS Addons ({{trac|2342}})
* Change {{cmd|i.tasscap|version=70}} interface to more general one ({{trac|2407}})
* New [http://grass.osgeo.org/grass71/manuals/ GRASS GIS HTML 7 manual pages style] ({{changeset|61935}})

==== Anna Petrasova ====
* attempts to fix blocker {{trac|1681}} in {{changeset|61897}}
* mainly backporting (d.what.rast/vect, v/r.in.lidar, ...)
* fix for {{trac|1954}}, in {{changeset|61938}}

==== [[User:lucadelu|Luca Delucchi]] ====
* improved sphinx documentation for GUI and libs [{{changeset|61917}} {{changeset|61898}} {{changeset|61891}} {{changeset|61886}}]
* improvement in bug {{trac|2413}} [{{changeset|61862}}]
* fixed ''g.gui.rlisetup'' working for circular buffers [{{changeset|61866}}]
* fix ''v.to.lines'' in Addons and move it to main GRASS GIS 7 [{{changeset|61923}}]
* ...

==== Jarrett Keifer ====
* PyGRASS vector documentation expanded [{{changeset|61941}}]

==== [[User:Neteler|Markus Neteler]] ====
* r.viewshed test added for testsuite [{{changeset|61930}}]
* backport of i.modis.qc: Added Internal Climatology for MOD09CMG and MYD09CMG [{{changeset|61937}}]

==== Eric Goddard ====
* manual pages for t.vect.import/export

==== [[User:hellik|Helmut Kudrnovsky]] (remote) ====
* winGRASS: MS runtime installation - investigation why it fails [{{changeset|61911}}]

== Overall Code Sprint page ==

See http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint

== Press release ==

...

GRASS Community Sprint Portland 2014

2014-09-11T12:05:03Z

⚠️Sbl: manual pages which could be filled by Stefan B.

The GRASS GIS [[team]] will participate in the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint Portland Code Sprint 2014] at FOSS4G 2014 in US. The sprint will be held the day after the main conference ('''Saturday, September 13th''' 2014).

== Purpose ==
This '''Portland FOSS4G Code Sprint 2014''' is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. This code sprint is targeting members of OSGeo software projects.

For this meeting, we welcome people committed to improving the '''GRASS GIS project''' and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others. We'll try to make a major step forward towards a stable GRASS GIS 7 release.

== Sponsors ==

We welcome inkind as well as direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

The Portland event is especially interesting since important OSGeo projects come together!

=== Thanks to our sponsors ===



== Timing ==

'''When''': '''Saturday, September 13th''' 2014

'''Duration''': One day

== Venue ==

The sprint will be in the [http://eliotcenterportland.org Eliot Center] ([http://osm.org/go/WIDlUtpOQ-?m=&relation=186579 OSM]) along side [http://wherecamppdx.org WhereCampPDX].

== Accommodation and Costs ==

Please check on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint page of the sprint] more information about accommodation and cost. The participation is free of charge. However, participants should plan for the following costs:

* Travel to Portland
* Accommodation
* Breakfast and dinner (partly)

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution or modify this wiki.

Further details about the action items you '''find [[Talk:GRASS Community Sprint Portland 2014|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Ideas ===

Please edit this wiki page!

==== GRASS GIS 7 release related ====
* http://trac.osgeo.org/grass/wiki/Grass7Planning
** Fix the few remaining http://trac.osgeo.org/grass/wiki/Grass7Planning#Blockers
** Decide an official sample dataset for TGRASS, see {{trac|2259}} (comment 4)
* ...
* Last call for options keys, values and flags consolidation, use {{trac|2409}} to coordinate

==== Manual improvements ====
* Update the remaining "empty" manual pages (<<--- power users, please contribute!)
In order to coordinate efforts (also with people working from remote places) it would be helpful if volunteers sign up in the table below, for a manual they would feel comfortable to fill. Please feel free to add other modules which need a manual update or with missing manual pages... Regarding examples for the TGRASS modules see also discussion here: http://lists.osgeo.org/pipermail/grass-dev/2014-April/068556.html
And for
{| class="wikitable"
|-
! Module with incomplete manual !! Who !! Status !! Link
|-
| t.rast.out.vtk || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast.out.vtk.html
|-
| t.rast.to.rast3 || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast.to.rast3.html
|-
| t.rast3d.extract || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast3d.extract.html
|-
| t.rast3d.list || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast3d.list.html
|-
| t.rast3d.mapcalc || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast3d.mapcalc.html
|-
| t.rast3d.univar || || TBD || http://grass.osgeo.org/grass70/manuals/t.rast3d.univar.html
|-
| t.remove || Stefan B. || TBD || http://grass.osgeo.org/grass70/manuals/t.remove.html
|-
| t.sample || || TBD || http://grass.osgeo.org/grass70/manuals/t.sample.html
|-
| t.support || || TBD || http://grass.osgeo.org/grass70/manuals/t.support.html
|-
| t.topology || || TBD || http://grass.osgeo.org/grass70/manuals/t.topology.html
|-
| t.unregister || Stefan B. || TBD || http://grass.osgeo.org/grass70/manuals/t.unregister.html
|-
| t.vect.db.select || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.db.select.html
|-
| t.vect.export || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.export.html
|-
| t.vect.extract || Stefan B. || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.extract.html
|-
| t.vect.import || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.import.html
|-
| t.vect.list || || || http://grass.osgeo.org/grass70/manuals/t.vect.list.html
|-
| t.vect.observe.strds || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.observe.strds.html
|-
| t.vect.univar || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.univar.html
|-
| t.vect.what.strds || || TBD || http://grass.osgeo.org/grass70/manuals/t.vect.what.strds.html
|-
| More? || || ||
|}
* add more examples to the manual which in turn can be used for the new [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS Testing framework for GRASS GIS]
* change TOC to collapse style with mouse-over expansion
* clone http://grasswiki.osgeo.org/wiki/Quick_wxGUI_tutorial into new one for GRASS 7 (and replace therein "random surface" with WMS etc)
* ...

==== New funding model to facilitate payed GRASS GIS programming ====
* in order to get nasty annoying issues fixed, try a crowd funding approach, eg Kickstarter
** identify GRASS issues to be fixed for cash
** discuss how to select the programmers

==== Testing framework ====
* how to write tests and general presentation
* discuss relation to benchmarking (https://github.com/jachym/grass-performace)
* write closing Future work statement (TODO list) for related GSoC project

==== Module fixes related ====
* get g.gui.rlisetup working for circular buffers (see [http://lists.osgeo.org/pipermail/grass-user/2014-August/070799.html step-by-step example])
* fix v.to.lines in Addons and move it to main GRASS GIS 7
* <strike>fix r.li.daemon memory leak</strike> test fixed in {{changeset|61812}} <<-- testing needed, use examples
* fix potential v.generalize memory leak (add such tests to [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS testsuite])
* check wxGUI r.colors tool for integer maps (may show as FP maps?)
* complete r.reclass.area improvements (LD + MN)
* TGRASS: fix numbers in aggregate: tempmean_seasonal_9 --> tempmean_seasonal_0009 | see animation tool where it is solved
* ...

==== Web site: related ====
* simplify http://grass.osgeo.org/download/software/ms-windows/
* OSGeoREL: add parsable "GRASS GIS" tag to [http://wiki.osgeo.org/wiki/Edu_current_initiatives#Current_members_of_the_ICA-OSGeo_Network table of OSGeoREL labs] - then we could showcase them easily in the GRASS CMS
* ...

==== GDAL/OGR interface ===

* Patch for GDAL-GRASS plugin for GRASS 7: fix patch in https://trac.osgeo.org/gdal/ticket/2953

== Participation ==

=== In person ===
Please fill the related table on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint#GRASS_GIS wiki page of the sprint].

=== Via IRC chat or hangout===

==== IRC ====
: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

==== Hangout/Videobridge ====

There is the option to use Google+ Hangout, it is technically limited to 10 people and may require everyone to have G+ social media accounts to participate. More [http://www.google.com/+/learnmore/hangouts/ Information on G+ hangout].

Similarly multi-video conference calls can be done with Skype if the conference call initiator is a paid-up commercial Skype customer.

The FOSS [http://www.jitsi.org Jitsi] VoIP, IM, and video conferencing software produces a trivial to set up [https://jitsi.org/Projects/JitsiVideobridge VideoBridge] server software to the same. '''''New:''''' https://meet.jit.si -- zero-conf free no-accounts needed video conferencing; chat, etherpad, and prezi built in. (needs recent Opera or Chrome/Chromium with WebRTC support)

Further discussion on the pros and cons of these can be found on the [[Talk:GRASS_Community_Sprint_Prague_2013|Talk side of this wiki page]].

Please add yourself here below (please add also your gmail account for G+ hangout):
* ...

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (USA {{wikipedia|File:A_plug.jpg|(Type A)}} {{wikipedia|File:B_plug.jpg|(Type B)}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

Perhas during the event :)

== Photos ==

...

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS Community Sprint Vienna 2014]]!
* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Neteler|Markus Neteler]], ... (add)

== Press Release ==

...

[[Category:Workshops]]

GRASS Community Sprint Portland 2014

2014-09-06T22:02:13Z

⚠️Sbl: Added list over modules with incomplete manuals

The GRASS GIS [[team]] will participate in the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint Portland Code Sprint 2014] at FOSS4G 2014 in US. The sprint will be held the day after the main conference ('''Saturday, September 13th''' 2014).

== Purpose ==
This '''Portland FOSS4G Code Sprint 2014''' is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. This code sprint is targeting members of OSGeo software projects.

For this meeting, we welcome people committed to improving the '''GRASS GIS project''' and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others. We'll try to make a major step forward towards a stable GRASS GIS 7 release.

== Sponsors ==

We welcome inkind as well as direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

The Portland event is especially interesting since important OSGeo projects come together!

=== Thanks to our sponsors ===



== Timing ==

'''When''': '''Saturday, September 13th''' 2014

'''Duration''': One day

== Venue ==

The sprint will be in the [http://eliotcenterportland.org Eliot Center] ([http://osm.org/go/WIDlUtpOQ-?m=&relation=186579 OSM]) along side [http://wherecamppdx.org WhereCampPDX].

== Accommodation and Costs ==

Please check on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint page of the sprint] more information about accommodation and cost. The participation is free of charge. However, participants should plan for the following costs:

* Travel to Portland
* Accommodation
* Breakfast and dinner (partly)

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution or modify this wiki.

Further details about the action items you '''find [[Talk:GRASS Community Sprint Portland 2014|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Ideas ===

Please edit this wiki page!

'''GRASS GIS 7 release related:'''
* http://trac.osgeo.org/grass/wiki/Grass7Planning
** Fix the few remaining http://trac.osgeo.org/grass/wiki/Grass7Planning#Blockers
** Decide an official sample dataset for TGRASS, see {{trac|2259}} (comment 4)
* ...

'''Manual related:'''
* Update the remaining "empty" manual pages (<<--- power users, please contribute!)
In order to coordinate efforts (also with people working from remote places) it would be helpful if volunteers sign up in the table below, for a manual they would feel comfortable to fill. Please feel free to add other modules which need a manual update or with missing manual pages... Regarding examples for the TGRASS modules see also discussion here: http://lists.osgeo.org/pipermail/grass-dev/2014-April/068556.html
And for
{| class="wikitable"
|-
! Module with incomplete manual !! Who !! Status !! Link
|-
| t.rast.out.vtk || || || http://grass.osgeo.org/grass70/manuals/t.rast.out.vtk.html
|-
| t.rast.to.rast3 || || || http://grass.osgeo.org/grass70/manuals/t.rast.to.rast3.html
|-
| t.rast3d.extract || || || http://grass.osgeo.org/grass70/manuals/t.rast3d.extract.html
|-
| t.rast3d.list || || || http://grass.osgeo.org/grass70/manuals/t.rast3d.list.html
|-
| t.rast3d.mapcalc || || || http://grass.osgeo.org/grass70/manuals/t.rast3d.mapcalc.html
|-
| t.rast3d.univar || || || http://grass.osgeo.org/grass70/manuals/t.rast3d.univar.html
|-
| t.remove || || || http://grass.osgeo.org/grass70/manuals/t.remove.html
|-
| t.sample || || || http://grass.osgeo.org/grass70/manuals/t.sample.html
|-
| t.support || || || http://grass.osgeo.org/grass70/manuals/t.support.html
|-
| t.topology || || || http://grass.osgeo.org/grass70/manuals/t.topology.html
|-
| t.unregister || || || http://grass.osgeo.org/grass70/manuals/t.unregister.html
|-
| t.vect.db.select || || || http://grass.osgeo.org/grass70/manuals/t.vect.db.select.html
|-
| t.vect.export || || || http://grass.osgeo.org/grass70/manuals/t.vect.export.html
|-
| t.vect.extract || || || http://grass.osgeo.org/grass70/manuals/t.vect.extract.html
|-
| t.vect.import || || || http://grass.osgeo.org/grass70/manuals/t.vect.import.html
|-
| t.vect.list || || || http://grass.osgeo.org/grass70/manuals/t.vect.list.html
|-
| t.vect.observe.strds || || || http://grass.osgeo.org/grass70/manuals/t.vect.observe.strds.html
|-
| t.vect.univar || || || http://grass.osgeo.org/grass70/manuals/t.vect.univar.html
|-
| t.vect.what.strds || || || http://grass.osgeo.org/grass70/manuals/t.vect.what.strds.html
|-
| More? || || ||
|}
* add more examples to the manual which in turn can be used for the new [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS Testing framework for GRASS GIS]
* change TOC to collapse style with mouse-over expansion
* ...

'''Design portal (?) for payed GRASS GIS programming:'''
* in order to get nasty annoying issues fixed, try a crowd funding approach
** identify GRASS issues to be fixed for cash
** discuss how to select the programmers

'''Modules related:'''
* get g.gui.rlisetup working for circular buffers
* fix v.to.lines in Addons and move it to main GRASS GIS 7
* <strike>fix r.li.daemon memory leak</strike> test fix in {{changeset|61812}}
* fix potential v.generalize memory leak (add such tests to [http://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS testsuite])
* ...

'''Web site: related:'''
* simplify http://grass.osgeo.org/download/software/ms-windows/
* ...

== Participation ==

=== In person ===
Please fill the related table on the [http://wiki.osgeo.org/wiki/FOSS4G_2014_Code_Sprint#GRASS_GIS wiki page of the sprint].

=== Via IRC chat or hangout===

==== IRC ====
: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

==== Hangout/Videobridge ====

There is the option to use Google+ Hangout, it is technically limited to 10 people and may require everyone to have G+ social media accounts to participate. More [http://www.google.com/+/learnmore/hangouts/ Information on G+ hangout].

Similarly multi-video conference calls can be done with Skype if the conference call initiator is a paid-up commercial Skype customer.

The FOSS [http://www.jitsi.org Jitsi] VoIP, IM, and video conferencing software produces a trivial to set up [https://jitsi.org/Projects/JitsiVideobridge VideoBridge] server software to the same. '''''New:''''' https://meet.jit.si -- zero-conf free no-accounts needed video conferencing; chat, etherpad, and prezi built in. (needs recent Opera or Chrome/Chromium with WebRTC support)

Further discussion on the pros and cons of these can be found on the [[Talk:GRASS_Community_Sprint_Prague_2013|Talk side of this wiki page]].

Please add yourself here below (please add also your gmail account for G+ hangout):
* ...

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (USA {{wikipedia|File:A_plug.jpg|(Type A)}} {{wikipedia|File:B_plug.jpg|(Type B)}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

Perhas during the event :)

== Photos ==

...

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS Community Sprint Vienna 2014]]!
* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Neteler|Markus Neteler]], ... (add)

== Press Release ==

...

[[Category:Workshops]]

Working with GRASS without starting it explicitly

2014-08-17T20:12:23Z

⚠️Sbl: /* Bash examples (GNU/Linux) - added variables for the temporal modules*/

GRASS modules and imports of GRASS Python packages works only in a specific environmental settings (GRASS session). This settings is ensured by starting GRASS GIS application which prepares this GRASS session for you. It is possible to set up you system in the way GRASS session will be always active (GRASS is not running, just the environmental settings is ready). People often prefer to set up the GRASS environment in their script or program and this is what this article discuss. However, it must be noted that the the generally preferred (and easy) way is to create scripts and programs as GRASS modules which means that your don't have to bother with setting up the environment since the GRASS module should be always invoked only in GRASS session.

== GRASS sessions ==

It is possible to access GRASS modules without explicitly starting a "GRASS session". GRASS libraries require certain [http://grass.osgeo.org/grass70/manuals/variables.html environment variables] to be set. In fact a "GRASS session" is just a set of processes (e.g. a shell and/or GUI) which have the necessary environment settings, specifically:

* '''GISBASE''' needs to be set to the top-level directory of the GRASS installation.
* '''GISRC''' needs to contain the absolute path to a file containing settings for '''GISDBASE''', '''LOCATION_NAME''' and '''MAPSET'''.
* '''PATH''' needs to include '''$GISBASE/bin''' and '''$GISBASE/scripts'''.

If the GRASS libraries are shared libraries, the loader needs to be able to find them. This normally means that '''LD_LIBRARY_PATH''' (Linux, Solaris), '''DYLD_LIBRARY_PATH''' (MacOSX) or '''PATH''' (Windows) need to contain '''$GISBASE/lib''', although there are other means to the same end (e.g. on Linux, putting $GISBASE/lib (with $GISBASE replaced by its actual value) into /etc/ld.so.conf then running ldconfig).

Some libraries and modules use other variables. More information for most of them is available in the file ''$GISBASE/docs/html/variables.html''. The display libraries used by ''d.*'' commands use additional variables, which are documented along with the individual drivers.

=== Batch jobs ===

You can run GRASS scripts non-interactively from outside of a GRASS session with the GRASS_BATCH_JOB environment variable. When GRASS is started with this environment variable set it will automatically run the contents of the script given in the variable, then close the GRASS session when complete. In this way full lock-checking, GRASS variables setup, and temporary file cleaning tasks are still performed.

See the [[GRASS_and_Shell#GRASS_Batch_jobs|Batch jobs]] section of the GRASS shell-help wiki page for details.

=== Accessing GRASS modules without starting a GRASS session ===

==== Python examples ====

See also [[GRASS Python Scripting Library]]

===== Python: GRASS GIS 7 =====

The script initializes the session and lists available raster and vector maps:

<source lang=python>
#!/usr/bin/env python

import os
import sys
import subprocess

# some predefined variables, name of the GRASS launch script + location/mapset
#grass7bin = 'C:\Program Files (x86)\GRASS GIS 7.0.svn\grass70svn.bat'
grass7bin = 'grass71'
location = "nc_spm_08_grass7"
mapset = "user1"

########### SOFTWARE
# query GRASS 7 itself for its GISBASE
# we assume that GRASS GIS' start script is available and in the PATH
startcmd = grass7bin + ' --config path'
p = subprocess.Popen(startcmd, shell=True,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
out, err = p.communicate()
if p.returncode != 0:
print >>sys.stderr, "ERROR: Cannot find GRASS GIS 7 start script (%s)" % startcmd
sys.exit(-1)
gisbase = out.strip('\n')

# Set GISBASE environment variable
os.environ['GISBASE'] = gisbase
# define GRASS-Python environment
gpydir = os.path.join(gisbase, "etc", "python")
sys.path.append(gpydir)

########### DATA
# define GRASS DATABASE
gisdb = os.path.join(os.path.expanduser("~"), "grassdata")
# Set GISDBASE environment variable
os.environ['GISDBASE'] = gisdb

# import GRASS Python bindings (see also pygrass)
import grass.script as gscript
import grass.script.setup as gsetup

###########
# launch session
gsetup.init(gisbase,
gisdb, location, mapset)

gscript.message('Current GRASS GIS 7 environment:')
print gscript.gisenv()

gscript.message('Available raster maps:')
for rast in gscript.list_strings(type = 'rast'):
print rast

gscript.message('Available vector maps:')
for vect in gscript.list_strings(type = 'vect'):
print vect

sys.exit(0)
</source>

===== Python: GRASS GIS 6 =====

The script initializes the session and lists available raster maps:

<source lang=python>
import os
import sys

gisbase = os.environ['GISBASE'] = "/usr/local/src/grass_trunk/dist.x86_64-unknown-linux-gnu"

gisdbase = os.path.join(os.environ['HOME'], "grassdata")
location = "nc_spm_08"
mapset = "user1"

sys.path.append(os.path.join(os.environ['GISBASE'], "etc", "python"))
import grass.script as grass
import grass.script.setup as gsetup

gsetup.init(gisbase,
gisdbase, location, mapset)

print grass.gisenv()

grass.message('Raster maps:')
for rast in grass.list_strings(type = 'rast'):
print rast
</source>

==== Bash examples (GNU/Linux) ====

Below an example of a '''~/.bash_profile''' script to set the required settings in order to access GRASS commands outside of a GRASS-session. Specifically it is for GRASS 7 (commented parts for GRASS 6.4.2):

<source lang=bash>
# example for GRASS 7
export GISBASE=/usr/local/grass-7.0.svn
# example for GRASS 6.4.2
### export GISBASE=/usr/local/grass-6.4.2svn

# GRASS 7
export GRASS_VERSION="7.0.svn"
# GRASS 6.4.2
### export GRASS_VERSION="6.4.2svn"

#generate GISRCRC
MYGISDBASE=$HOME/grassdata
MYLOC=nc_spm_08
MYMAPSET=user1

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

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 GRASS_PYTHON=python
export GRASS_MESSAGE_FORMAT=plain
export GRASS_TRUECOLOR=TRUE
export GRASS_TRANSPARENT=TRUE
export GRASS_PNG_AUTO_WRITE=TRUE
export GRASS_GNUPLOT='gnuplot -persist'
export GRASS_WIDTH=640
export GRASS_HEIGHT=480
export GRASS_HTML_BROWSER=firefox
export GRASS_PAGER=cat
export GRASS_WISH=wish

export PATH="$GISBASE/bin:$GISBASE/scripts:$PATH"
export LD_LIBRARY_PATH="$GISBASE/lib"
export GRASS_LD_LIBRARY_PATH="$LD_LIBRARY_PATH"
export PYTHONPATH="$GISBASE/etc/python:$PYTHONPATH"
export MANPATH=$MANPATH:$GISBASE/man

#For the temporal modules
export TGISDB_DRIVER=sqlite
export TGISDB_DATABASE=$MYGISDBASE/$MYLOC/PERMANENT/tgis/sqlite.db

# test a command
g.list rast

######### below not needed ########
# GRASS 7
tmp=/tmp/grass7-"`whoami`"-$GIS_LOCK
# GRASS 6.4.2
### tmp=/tmp/grass6-"`whoami`"-$GIS_LOCK

export GISRC="$tmp/rc"
mkdir "$tmp"

# GRASS 7
cp ~/.grass7/rc "$GISRC"
# GRASS 6.4.2
### cp ~/.grassrc6 "$GISRC"
######### END below not needed ########
</source>

The above script will allow GRASS commands to be used anywhere. Furthermore, if the '''~/.Xsession''' sources the bash startup scripts, the settings aren't limited to interactive shells, but also work for e.g. M-! in XEmacs). Each interactive shell gets a separate "session" (i.e. a separate $GISRC file), while GUI programs share a common session.

Note, however, that '''~/.bash_profile''' is a personal initialization startup script and, thus, read during the login process. Any modifications to it will be read after (re-)login or explicitly sourcing it.

At the end of the ~/.bash_profile file, the following lines can be added to ensure no duplication of entries in the PATH variable.

<source lang=bash>
PATH=`awk -F: '{for(i=1;i<=NF;i++){if(!($i in a)){a[$i];printf s$i;s=":"}}}'<<<$PATH`
PYTHONPATH=`awk -F: '{for(i=1;i<=NF;i++){if(!($i in a)){a[$i];printf s$i;s=":"}}}'<<<$PYTHONPATH`
</source>

=== Important notes ===

Launching a grassXY session could still permit access on GRASS modules of the version that is set with the above script. The reason being is that grassXY scripts (e.g.: grass64, grass65, grass70) prepend the GRASS directories to '''PATH''', '''LD_LIBRARY_PATH''', etc. They won't remove any entries which are already there. A solution to this is to ''switch'' between GRASS versions by using a script like the following:

<source lang="bash">
strippath()
{
(
oldpath="$1"
newpath=
IFS=:
for dir in $oldpath ; do
case "${dir}" in
*grass*)
;;
*)
newpath="$newpath:$dir"
;;
esac
done
echo "${newpath#:}"
)
}

PATH=`strippath $PATH`

export GISBASE=$PWD/dist.i686-pc-linux-gnu
export PATH="$GISBASE/bin:$GISBASE/scripts:$PATH"
export LD_LIBRARY_PATH="$GISBASE/lib"
export PYTHONPATH="$GISBASE/etc/python"
</source>

'''Note: the above script needs to be "source"d; executing it won't work. It might also require some adjustments (e.g. the ''GISBASE'' variable).'''

Using normal grass sessions commands are recorded in '''$GISDBASE/$LOCATION_NAME/$MAPSET/.bash_history'''. While working with "pure" bash, shell entries go in '''~/.bash_history'''. Merging existing "grass-bash_history(-ies)" with the bash history log, would probably be not a good idea. Perhaps it is wise(r) to use normal GRASS sessions when working on real projects. Nevertheless, it is upon the users preferences and expertise level to decide what is best.

=== References ===
* Instructions and discussion on ''how to access GRASS mapsets outside of a GRASS session'' in the grass-user mailing list [http://n2.nabble.com/can-I-access-mapset-outside-of-grass-by-using-python-td3405902.html#a3405902].
* removing duplicate entries in $PATH taken from [http://chunchung.blogspot.com/2007/11/remove-duplicate-paths-from-path-in.html]

== GRASS databases ==

(project file structure)

=== Minimal mapsets ===

within a functional LOCATION (see below) the minimal mapset is a subdirectory of the MAPSET's name, containing a WIND file. The WIND file can simply be copied from PERMANENT/DEFAULT_WIND. Optionally you can put a VAR file in there too to define the default database driver to use.

* You can create a new mapset when starting GRASS with the -c flag. e.g.
grass64 -c /path/to/location/new_mapset_name

=== Minimal locations ===

Within the GISDATABASE (which is simply a subdirectory some where), the minimum LOCATION consists of a directory giving the LOCATION its name, which in turn contains a PERMANENT subdirectory for the PERMANENT mapset. The PERMANENT mapset contains a few special files that regular mapsets don't. These are:
; PROJ_INFO: contains the location's projection information
; PROJ_UNITS: contains the location's map units definition
; DEFAULT_WIND: the default region (WINDow file). The format is identical to the WIND files created by g.region
; WIND: (optional?)

* see also {{src|demolocation}} in the GRASS source code

== See also ==
* [[GRASS_and_Shell#GRASS_Batch_jobs|GRASS Batch jobs]]

[[Category: FAQ]]
[[Category: Linking to other languages]]
[[Category: bash]]
[[Category:Scripting]]
[[Category: Python]]

Global datasets

2014-02-26T22:00:16Z

⚠️Sbl: Add a section on CSW and links to European Services

= Raster data =

== Elevation data ==

=== ASTER topography (GDEM V1) ===

Improved ASTER GDEM 1 from 2009:

GDEM global 30m elevation calculated from stereo-pair images collected by the Terra satellite.
''"This is the most complete, consistent global digital elevation data yet made available to the world."''
This is a very new dataset, at version 1 (treat as ''experimental''). Accuracy will be improved in forthcoming versions (validation with SRTM, etc.; [http://blog.neteler.org/aster-gdem-30m-quality-assessment/ see assessment here] and [http://www.viewfinderpanoramas.org/reviews.html#aster here]).

* ''[https://lpdaac.usgs.gov/lpdaac/about/news_archive/monday_june_22_20092 pre-release announcement]''
* [http://www.nasa.gov/home/hqnews/2009/jun/HQ_09-150_ASTER_Topographic_Map.html NASA press release]
* [https://wist.echo.nasa.gov/~wist/api/imswelcome/ Warehouse Inventory Search Tool] or [http://www.gdem.aster.ersdac.or.jp/search.jsp Easy search tool] (Data download)

'''Tutorial:''' [[ASTER topography]]

''See also: [http://blog.neteler.org/aster-gdem-30m-quality-assessment/ ASTER GDEM 30m quality assessment]''

=== ASTER topography (GDEM V2) ===

Improved ASTER GDEM 2 from 2011:
* https://lpdaac.usgs.gov/products/aster_products_table/astgtm

The ASTER GDEM covers land surfaces between 83°N and 83°S and is comprised of 22,702 tiles. Tiles that contain at least 0.01% land area are included. The ASTER GDEM is distributed as Geographic Tagged Image File Format (GeoTIFF) files with geographic coordinates (latitude, longitude). The data are posted on a '''1 arc-second''' (approximately '''30–m at the equator''') grid and referenced to the 1984 World Geodetic System (WGS84)/ 1996 Earth Gravitational Model (EGM96) geoid.

'''Notes:''' this DEM can be rather well filtered and smoothed with the [http://personalpages.manchester.ac.uk/staff/neil.mitchell/mdenoise/ Sun's denoising algorithm] (using GDAL and free / open source program <mdenoise> or simply GRASS add-on {{AddonCmd|r.denoise}}.

Experiments showed that the best smoothing of ASTER GDEM 2 is reached with such parameters of <mdenoise>:
* threshold = 0.8
* iterations = 10-20

Also filtering with {{cmd|r.neighbors}} by "average" method and window size >=5 is quite useful to remove some noise from DEM.

''See also: [http://www.isprs2012.org/abstract/299.asp Validation of the ASTER Global Digital Elevation Model Version 2 over the Conterminous United States]''

=== ACE2 ===

The ACE2 Global Digital Elevation Model is available at 3", 30" and 5' spatial resolutions.

* http://tethys.eaprs.cse.dmu.ac.uk/ACE2/

Import example:
r.in.bin -f input="00N105E_3S.ACE2" output="ACE2_00N105E" bytes=4 \
order="native" north=15 south=0 east=120 west=105 \
rows=18000 cols=18000

=== CleanTOPO2 (DEM) ===

* [http://www.shadedrelief.com/cleantopo2/ CleanTOPO2 download]: Edited SRTM30 Plus World Elevation Data

Import in GRASS:
r.in.gdal CleanTOPO2.tif out=cleanTOPO2.tmp -l -o
g.region rast=cleanTOPO2 -p -g
# rescale from odd integer values to true world values
r.rescale cleanTOPO2.tmp out=cleanTOPO2 to=-10701,8248
r.colors cleanTOPO2_final col=terrain

[[Image:CleanTOPO2_map.png|thumb|center|300px|Rescaled ClearTOPO2 map]]

=== EGM2008 Geoid Data (Earth Gravitational Model) ===

Global 2.5 Minute Geoid Undulations:
* download GIS Format at http://earth-info.nga.mil/GandG/wgs84/gravitymod/egm2008/egm08_gis.html

[[Image:Trentino_egm2008_map_5m_resampled.jpg|thumb|center|300px|Geoid undulations in Trentino, Italy]]

Verifications of points can be done with the http://geographiclib.sourceforge.net/cgi-bin/GeoidEval

=== ETOPO (DEM) ===

The ETOPO datasets provide global topography and bathymetry at 1', 2', and 5' per-cell resolutions.

==== ETOPO1 (DEM) ====

* http://www.ngdc.noaa.gov/mgg/global/

* '''The ''cell registered'' version can be loaded directly into a lat/lon location'''. GRASS raster data is cell registered (see the [[GRASS raster semantics]] page)

* Special care must be taken with the ''grid registered'' version. It can not be loaded directly into a lat/lon location as the parameters found in the .hdr file exceed the limits of polar coordinate space: they have N,S rows which go 1/2 a cell beyond 90 latitude, when considered in the ''cell registered'' convention.
: So the data needs to have those 90deg N,S rows cropped away, and while we're at it we crop away a redundant overlapping column at 180 longitude. To do this we have to first tell the GIS a little fib during import to squeeze the data into lat/lon space, then crop away the spurious rows and column, then finally reset the resulting map's bounds to its true extent.

<source lang="bash">
# Import grid registered binary float, fibbing about its true extent
r.in.bin -f in=etopo1_bed_g.flt out=etopo1_bed_g.raw \
n=90 s=-90 e=180 w=-180 rows=10801 cols=21601 anull=-9999

# reduce the working region by 1 cell
g.region rast=etopo1_bed_g.raw
eval `g.region -g`
g.region n=n-$nsres s=s+$nsres e=e-$ewres -p

# save smaller raster and remove original
r.mapcalc "etopo1_bed_g.crop = etopo1_bed_g.raw"
g.remove etopo1_bed_g.raw

# re-establish the correct bounds, now that they'll fit
r.region etopo1_bed_g.crop n=89:59:30N s=89:59:30S w=179:59:30E e=179:59:30E
g.region rast=etopo1_bed_g.crop

# check that N,S,E,W and Res are all nice and clean:
r.info etopo1_bed_g.crop

# looks good, so accept the results by resetting the map name
g.rename etopo1_bed_g.crop,etopo1_bed_g

# set to use appropriate color rules
r.colors etopo1_bed_g color=etopo2

# set the 'units' metadata field (for elevation data contained within the map)
r.support etopo1_bed_g units=meters
</source>

* For the problematic ''grid registered'' version, the resulting {{cmd|r.info}} report should look like:
| Rows: 10799 |
| Columns: 21600 |
| Total Cells: 233258400 |
| Projection: Latitude-Longitude |
| N: 89:59:30N S: 89:59:30S Res: 0:01 |
| E: 179:59:30E W: 179:59:30E Res: 0:01 |
| Range of data: min = -10898 max = 8271 |
(the east and west bounds of the map touch 1/2 a cell west of 180 longitude)

* For the problematic ''grid registered'' version, since the data's grid is 1/2 a cell shifted from nicely rounded 1 arc-minutes (0:01), you'll need to ensure that the mapset's region preserves that alignment after zooming or panning:
g.region align=etopo1_bed_g -p
: (or oversample and set the region resolution to 1/2 arc-minutes (0:00:30), which will be four times as slow)

==== ETOPO2 (DEM) ====

* See the ETOPO2 (2' global) article by M.H. Bowman in the [http://grass.osgeo.org/newsletter/GRASSNews_vol1.pdf GRASS Newsletter, 1:8-11, August 2004].
: [http://www.ngdc.noaa.gov/mgg/fliers/01mgg04.html ETOPO2v2 data download] (take for example the ETOPO2v2g_f4_LSB.flt file)

=== GTOPO30 (DEM) ===

* Data [http://eros.usgs.gov/#/Find_Data/Products_and_Data_Available/gtopo30_info download] - Import with {{cmd|r.in.gdal}}.

''Note:'' To avoid that the GTOPO30 data are read incorrectly, you can add a new line "PIXELTYPE SIGNEDINT" in the .HDR to force interpretation of the file as signed rather than unsigned integers. Then the .DEM file can be imported. Finally, e.g. the 'terrain' color table can be assigned to the imported map with r.colors.

=== Global Multi-resolution Terrain Elevation Data 2010 (GMTED2010) ===

* Data [https://lta.cr.usgs.gov/GMTED2010 download] - Import with {{cmd|r.in.gdal}}.

Import of GMTED2010 tiles in GRASS GIS:

r.in.gdal 30N000E_20101117_gmted_mea075.tif out=gmted2010_30N000E_20101117
r.colors gmted2010_30N000E_20101117 color=elevation
g.region rast=gmted2010_30N000E_20101117
r.shaded.relief gmted2010_30N000E_20101117 units=meters
d.mon x0
d.rast gmted2010_30N000E_20101117.shade
d.grid 1 color=red textcolor=red

[[Image:Gmted2010_30N000E_20101117_shaded.png|thumb|center|300px|GMTED2010 example: Trento - Garda Lake - Verona area (Northern Italy)]]

=== GEBCO Bathymetric Chart ===

* The General Bathymetric Chart of the Oceans (original 1' release 2003, new 1' and 30" releases 2008)
: http://www.gebco.net/data_and_products/gridded_bathymetry_data/
: http://www.bodc.ac.uk/data/online_delivery/gebco/

{{cmd|r.in.gdal}} can be used to import the GMT netCDF files directly, or if that doesn't work you can use GMT tools to convert to an old-style native GMT format and import that with {{cmd|r.in.bin}}.
: example: (GEBCO 2003 1' data)

# convert to an old style GMT binary .grd using grdreformat
$ grdreformat 3n24s47w14w.grd 3n24s47w14w_Native.grd=bs

# then import into GRASS,
GRASS> r.in.bin -h -s bytes=2 in=3n24s47w14w_Native.grd out=3n24s47w14w

# and set some nice colors
GRASS> r.colors 3n24s47w14w rules=- << EOF
nv magenta
0% black
-7740 0:0:168
0 84:176:248
0 40:124:0
522 68:148:24
1407 148:228:108
1929 232:228:108
2028 232:228:92
2550 228:160:32
2724 216:116:8
2730 grey
2754 grey
2760 252:252:252
2874 252:252:252
2883 192:192:192
2913 192:192:192
100% 252:252:252
EOF

=== Global Multi-Resolution Topography (GMRT DEM) ===
: ''From Columbia University's Lamont-Doherty Earth Observatory''
(it is reported that this is what Google Maps uses for their global bathymetry)

* Global ~1 arc-second (~90 m) topography using multi-beam and satellite data in the oceans combined with SRTM on land.
* Full information at: http://www.marine-geo.org/portals/gmrt/
* Accessible via [http://www.geomapapp.org/ GeoMapApp] or [http://www.virtualocean.org/ Virtual Ocean] software.
* Very convenient to download into GRASS via wget:

export `g.region -g`
wget "http://www.marine-geo.org/cgi-bin/getgridB?west=${w}&east=${e}&south=${s}&north=${n}&resolution=1" -O /tmp/test.grd
r.in.gdal /tmp/test.grd output=GMRT -o
rm /tmp/test.grd

* Note: Downloaded file contains no projection information, but is EPSG:4326 (WGS84 Geographic). The file size is limited, but lower resolution (resolution=2,4,8) data can be downloaded for larger areas.

=== Smith and Sandwell DEM ===

* Merge info here from the [[Marine Science]] wiki page

=== SRTM DEM ===

[http://www2.jpl.nasa.gov/srtm/ Space Shuttle Radar Topography Mission]
* see [[HOWTO import SRTM elevation data]]

=== SRTM30plus data DEM ===

SRTM30plus data consists of 33 files of global topography in the same format as the SRTM30 products distributed by the USGS EROS data center. The grid resolution is 30 second which is roughly one kilometer.

Land data are based on the 1-km averages of topography derived from the USGS SRTM30 grided DEM data product created with data from the NASA Shuttle Radar Topography Mission. GTOPO30 data are used for high latitudes where SRTM data are not available.

Ocean data are based on the Smith and Sandwell global 2-minute grid between latitudes +/- 72 degrees. Higher resolution grids have been added from the LDEO Ridge Multibeam Synthesis Project and the NGDC Coastal Relief Model. Arctic bathymetry is from the International Bathymetric Chart of the Oceans (IBCAO).

All data are derived from public domain sources and these data are also in the public domain.

GRASS 6 script <code>r.in.srtm</code> described in GRASSNews vol. 3 won't work with this dataset (as it was made for the original SRTM HGT files). But you can import SRTM30plus tiles into GRASS this way:

r.in.bin -sb input=e020n40.Bathmetry.srtm output=e020n40_topex bytes=2 north=40 south=-10 east=60 west=20 r=6000 c=4800
r.colors e020n40_topex rules=etopo2

; Source
: GRASS Users Mailing List http://lists.osgeo.org/pipermail/grass-user/2005-August/030063.html
; Getting as SRTM30plus tiles: ftp://topex.ucsd.edu/pub/srtm30_plus/srtm30/data/
; Getting as SRTM30plus huge file: ftp://topex.ucsd.edu/pub/srtm30_plus/topo30/
; SRTMPLUS WCS server: http://svn.osgeo.org/gdal/trunk/autotest/gdrivers/data/srtmplus.wcs (read with {{cmd|r.external}}

== Soil data ==

=== Harmonized World Soil Database (HWSD Database) ===

Download: http://webarchive.iiasa.ac.at/Research/LUC/External-World-soil-database/HTML/

[http://webarchive.iiasa.ac.at/Research/LUC/External-World-soil-database/HTML/DataDesc.html?sb=12 Spatial reference system:] [http://spatialreference.org/ref/epsg/4326/ EPSG:4326] (LatLong WGS84)

Import:
grass70 -c EPSG:4326 ~/grassdata/hwsd
# -e: expand location to dataset; -o: override (missing) projection in input dataset:
r.in.gdal input=hwsd.bil output=hwSoil -e -o
g.region rast=hwSoil -p
r.category hwSoil

The data is distributed with an MSAccess .mdb which contains additional data for each of the categories in the raster file. Opening the file in access, the data is found in the query "HWSD_Q". Save this query in .csv format (with a name like "HWSD_Q.csv") so that it may then be imported into GRASS. Before you can import it, you also need a file "HWSD_Q.csvt", which contains a single line listing the type for each column in the database:
"Integer","String","Integer","Integer","Integer","String","Integer","Integer","Real","Integer","String","Integer","String","Integer","String","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Integer","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real","Integer","Integer","Integer","Integer","Integer","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real","Real"

With both the .csv and the .csvt file in the same directory, you can then import them into GRASS:
db.in.ogr dsn=~/grassdata/hwsd/HWSD_Q.csv output=hwsdData

The data cannot be connected directly to the raster, it must be converted to a vector first:
g.region rast=hwSoil
r.to.vect -v in=hwSoil out=hwSoil feature=area
v.db.droptable hwSoil
db.droptable -f hwSoil # delete the table completely

Now we can connect the map and the table:
v.db.connect -o map=hwSoil table=hwsdData driver=sqlite key=MU_GLOBAL

To create a new raster map taking the values from the table:
g.region rast=hwSoil ## make sure we get the whole map
v.to.rast in=hwSoil out=T_SAND col=T_SAND

== Imagery ==

=== AVHRR ===

* see the [[AVHRR]] wiki page

=== Blue Marble imagery ===

NASA's Blue Marble is a 500m-8 degree per-cell world wide visual image of the Earth from space, with the clouds removed.

* see the [[Blue Marble]] wiki page

=== EO-1 imagery ===

(Earth Observing-1)
* "''Advanced Land Imager (ALI) provides image data from ten spectral bands (band designations). The instrument operates in a pushbroom fashion, with a spatial resolution of 30 meters for the multispectral bands and 10 meters for the panchromatic band.''"
:-- http://eros.usgs.gov/products/satellite/eo1.php
* On-board Atmospheric Corrections

=== Global Land Cover Characteristics ===

USGS ''et al.'' generated dataset at 1km resolution. Provides global landcover characteristics.

* see the [[Global Land Cover Characteristics]] wiki page

=== LANDSAT imagery ===

Since October 1, 2008 all Landsat 7 ETM+ scenes held in the [http://landsat.usgs.gov/ USGS EROS archive] are available for download at no charge.
* Download via the [http://glovis.usgs.gov/ Glovis] online search tool (req. Java)
* Download via the USGS's [http://edcsns17.cr.usgs.gov/EarthExplorer/ EarthExplorer] interface

==== Import Modules ====

* {{cmd|r.in.gdal}} - Main import tool for complete multiband scenes
* {{cmd|r.in.wms}} - Download data covering current map region via WMS server
* [[GRASS_AddOns#r.in.onearth|r.in.onearth]] - WMS frontend for NASA's OnEarth Global Landsat Mosaic
* {{cmd|i.landsat.rgb}} - Color balancing/enhancement tool

==== See also ====

* Processing tips can be found on the [[LANDSAT]] wiki page

=== Miscellaneous ===

==== Data sources ====

* Some datasource links: http://www.ruf.rice.edu/~ben/gmt.html
* [http://www.geotorrent.org/browse.php Geotorrent.org]

==== Import Modules ====
* The {{cmd|r.in.gdal}} modules may be used to import data of [http://www.gdal.org/formats_list.html many formats], including GMT netCDF
* The {{cmd|r.in.bin}} module may be used to import raw binary files

=== MODIS imagery ===

* see the [[MODIS]] wiki page

=== Natural Earth imagery ===

* [http://www.naturalearthdata.com/ Natural Earth II]: World environment map in natural color. GeoTIFF (use the {{cmd|r.in.gdal}} module)
* see also 1:10 million, 1:50 million and 1:110million scale maps from http://www.naturalearthdata.com/

=== Orthoimagery ===

* [http://worldwindcentral.com/wiki/Sources_of_free_orthoimagery Sources of free orthoimagery]

=== Pathfinder AVHRR SST imagery ===

* see the Pathfinder [[AVHRR]] SST wiki page

=== QuickBird imagery ===

* See the [[QuickBird]] wiki page

=== SeaWiFS imagery ===

* see the [[SeaWiFS]] wiki page

=== SPOT Vegetation imagery ===

SPOT Vegetation (1km) global: NDVI data sets

* [http://free.vgt.vito.be/ SPOT Vegetation (1km, global) NDVI data set server]
* for import, see {{cmd|i.in.spotvgt}}

=== True Marble imagery ===

* [http://www.unearthedoutdoors.net/global_data/true_marble/download True Marble]: 250m world wide visual image of the Earth from space, with the clouds removed. GeoTIFF (use the {{cmd|r.in.gdal}} module)

== Climatic data ==

=== OGC WCS - Albedo example ===

TODO: update this example e.g. to http://demo.mapserver.org/cgi-bin/wcs?SERVICE=wcs&VERSION=1.0.0&REQUEST=GetCapabilities

GRASS imports OGC Web Coverage Service data. Example server (please suggest a better one!)
<WCS_GDAL>
<ServiceURL>http://laits.gmu.edu/cgi-bin/NWGISS/NWGISS?</ServiceURL>
<CoverageName>AUTUMN.hdf</CoverageName>
<Timeout>90</Timeout>
<Resample>nearest</Resample>
</WCS_GDAL>

Save this as albedo.xml. Import into a LatLong WGS84 location:
r.in.gdal albedo.xml out=albedo

Unfortunately this server sends out the map shifted by 0.5 pixel. This requires a fix to the map boundary coordinates:
r.region albedo n=90 s=-90 w=-180 e=180

Now apply color table and look at the map:
r.colors albedo color=byr
d.mon x0
d.rast albedo

=== SNODAS maps ===

[http://nsidc.org/data/docs/noaa/g02158_snodas_snow_cover_model/index.html Snow Data Assimilation System] data that support hydrological modeling and analysis. First download the data, and untar them (once for each month, and once for each day), and you should get pairs of “.dat” and “.Hdr” files. The data files are stored in flat 16-bit binary format, so assuming that “snowdas_in.dat” is the name of the input file, at the GRASS prompt:

r.in.bin -bs bytes=2 rows=3351 cols=6935 north=52.874583333332339 \
south=24.949583333333454 east=-66.942083333334011 west=-124.733749999998366 \
anull=-9999 input=snowdas_input.dat output=snowdas

=== WorldClim maps ===

[http://www.worldclim.org/ WorldClim] is a set of global climate layers (climate grids) with a spatial resolution of a square kilometer.
* Load into a Lat/Lon WGS84 location (EPSG:4326)
* Import with {{cmd|r.in.bin}} or {{cmd|r.in.gdal}}
* {{cmd|r.in.gdal}} will read .BIL format, see the {{cmd|r.in.srtm}} shell script for hints
* binary format is 2 byte integer. Multiply by 10 using {{cmd|r.mapcalc}} to convert units. See http://www.worldclim.org/format.htm for more information and the [[MODIS]] help page for example of converting raw to data units.

== Population maps ==

=== Gridded Population of the World ===

* http://sedac.ciesin.columbia.edu/gpw/global.jsp

Import with {{cmd|r.in.gdal}}, assign population color table with {{cmd|r.colors}}

== Topographic maps ==
=== Soviet topographic maps ===

* [http://en.poehali.org/maps Soviet topographic maps] as geocoded GeoTIFFs

= Vector data =

=== CDC Geographic Boundary and Public Health Maps ===

* http://www.cdc.gov/epiinfo/maps.htm

=== Global Administrative Areas ===

* GADM is a database of the location of the world's administrative areas (boundaries) available in shapefiles.
: http://gadm.org (extracted by country [http://gadm.org/country here])

* World Borders Dataset including ISO 3166-1 Country codes available in shapefiles.
: http://thematicmapping.org/downloads/world_borders.php
* Free GIS data from Mapping Hacks
: http://mappinghacks.com/data/

=== GSHHS World Coastline ===

GSHHS is a high resolution shoreline dataset. It is derived from data in the public domain and licensed as GPL. The shorelines are constructed entirely from hierarchically arranged closed polygons. It is closely linked to the [[GMT]] project.

==== Availability ====

* Download the original data set from http://www.soest.hawaii.edu/pwessel/gshhg/index.html. Also available at http://www.ngdc.noaa.gov/mgg/shorelines/data/gshhg/latest/.

* The data set, or parts from it, can be extracted from [http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html NOAA's shoreline extractor].
:For GRASS 6 you can download 1:250,000 shoreline data from NOAA's site in Mapgen format, which can be imported with the {{cmd|v.in.mapgen}} module.

* '''ESRI Shapefiles''' of the latest version are available at http://www.ngdc.noaa.gov/mgg/shorelines/data/gshhg/latest/. The old 1.6 version is available at ftp://ftp.ihg.uni-duisburg.de/GIS/GISData/GSHHS/.

==== Import ====

* Import with the GRASS6 add-on module {{AddonCmd|v.in.gshhs}}

=== OpenStreetMap ===

See the [[OpenStreetMap]] wiki page.

=== SALB ===

Second Administrative Level Boundaries: ''"The SALB dataset is a global digital dataset consisting of digital maps and codes that can be downloaded on a country by country basis."''

* http://www.who.int/whosis/database/gis/salb/salb_home.htm

=== VMap0 ===

1:1 million vector data. Formerly known as ''Digital Chart of the World''

* see the two articles in [http://grass.osgeo.org/newsletter/index.php ''GRASS Newsletter vol. 3 (June 2005)'']

Check the [http://en.wikipedia.org/wiki/Vector_Map Wikipedia page] on VMAP, see the links at the bottom of that article to shapefile versions of VMAP0 and VMAP1. Those look like the versions that were, several years ago, on a NIMA (predecessor to NGA, and successor to the Defense Mapping Agency that managed the Digital Chart of the World and VMAP project) Website. Many GRASS users may prefer the shapefiles to the original Vector Product Format data.

* [http://gis-lab.info/qa/vmap0-eng.html VMap0 data in ESRI shape format]

= See also =

* [http://spatial-analyst.net/wiki/index.php?title=Global_datasets Global datasets] list by T. Hengl (with dataset download)
* http://freegisdata.rtwilson.com/
* The FreeGIS.org database: http://www.freegis.org/database/
* http://finder.geocommons.com/
* http://wiki.openstreetmap.org/wiki/Potential_Datasources
* http://www.geonames.org/data-sources.html
* [http://ckan.net/tag/read/geo Open Knowledge Foundation link collection]
* [http://openweathermap.org/ Open Weather Map] free weather data and forecast API suitable for any cartographic services like web and smartphones applications. Ideology is inspired by OpenStreetMap and Wikipedia that make information free and available for everybody.

=== Metadata Catalogues ===
Catalog Service for the Web (CSW) is an OGC standard for offering access to catalogues of geospatial information over the Internet (HTTP). CSW allow for discovering, browsing, and querying metadata about data, services, and similar resources. A list of Metadata Catalogues / CSW services from member states of the European Union can be found here: 
* [http://inspire-geoportal.ec.europa.eu/INSPIRERegistry/ http://inspire-geoportal.ec.europa.eu/INSPIRERegistry/] 
And here: [http://inspire-geoportal.ec.europa.eu/discovery/ http://inspire-geoportal.ec.europa.eu/discovery/] one can search European Metadata Catalogues online.

=== European datasets ===

* [[European datasets]]
* [http://preview.grid.unep.ch/index3.php?preview=data&lang=eng Global Risk Data Platform]
* [http://open-data.europa.eu/open-data/data/ European Commission Opendata Portal]: 5800+ datasets
* [http://eca.knmi.nl/download/ensembles/download.php E-OBS] This is the download page for the ENSEMBLES daily gridded observational dataset for precipitation, temperature and sea level pressure in Europe
* [http://mars.jrc.ec.europa.eu/mars/About-us/AGRI4CAST/Data-distribution MARS @ JRC] Temperature, vapour pressure, rainfall, relative humidity, cloud cover, solar radiation, wind speed.
* [http://www.efas.eu/ EFAS @ JRC] is a High resolution pan-European dataset for hydrologic modelling.

=== National datasets ===

* [http://asdd.ga.gov.au/asdd/tech/zap/basic.html Australian Spatial Data Directory]
* [http://wiki.gfoss.it/index.php/GIS_Open_Data Italian Geodata collection]
* [http://koordinates.com/ New Zealand] data from Koordinates.com
* United States from NOAA/USGSs data portal (FIXME: link?)
* [http://geodata.gov.gr/geodata/ Greek Public Geodata] (in Greek)

=== Various datasets worldwide ===

* [http://geospatial.edublogs.org/ GEOSPATIAL DATA REPORT]: Finding and Using GIS Data
* [http://www.edenextdata.com/?q=data Edenext data portal]: Land Cover, Transport networks, Elevation, Orthoimagery, Human health and safety, Species Distribution, Atmospheric Conditions and Meteorological Geographical Features, Training Program Presentations and Data, Utility and governmental services, Hydrography, Soil, Bio geographical regions, Population distribution and Demographics
* [http://gdex.cr.usgs.gov/gdex/ Global Data Explorer USGS]: ASTER, SRTM, GTOPO etc
* [http://www.landcover.org/ landcover]
* [http://www.gripweb.org/gripweb/?q=data-information GRIPWEB’s Data & Informational Portal]: hazard & risk
* [http://sedac.ciesin.columbia.edu/data/sets/browse SEDAC]: Agriculture, Climate, Conservation, Framework Data, Governance, Hazards, Health, Infrastructure, Land Use, Marine and Coastal, Population, Poverty, Remote Sensing, Sustainability, Urban, Water
* [http://www.preventionweb.net/english/professional/maps/?pid:6&pih:2 Prevention Web]: hazard & risk
* [http://data.un.org/Default.aspx UNdata]: UN database
* [http://www.undp.org/content/undp/en/home.html UNDP home page]
* [http://www.cgiar-csi.org/data global climatic data]
* [http://csi.cgiar.org/cgiargeospatialtools.asp cosortium for spatial information CGIAR-CSI GeoSpatial Toolkits]
* [http://freegisdata.rtwilson.com/ inks to over 300 sites providing freely available geographic datasets]
* [http://www.diva-gis.org/Data Free Spatial Data]
* [http://edc2.usgs.gov/glcc/globe_int.php Global Land Cover Characteristics Data Base Version 2.0]
* [http://opentopo.sdsc.edu/gridsphere/gridsphere?cid=datasets A Portal to High-Resolution Topography Data and Tools]
* [http://www.metoffice.gov.uk/hadobs/hadghcnd/ HadGHCND] is a gridded daily temperature dataset based upon near-surface maximum (TX) and minimum (TN) temperature observations.

=== WMS servers ===

* See [[WMS]] page

=== River discharge data ===

* [http://www.bafg.de/GRDC/EN/Home/homepage_node.html Global Runoff Data Centre]
* [http://www.sage.wisc.edu/riverdata/ Global River Discharge Database]
* [http://csdms.colorado.edu/wiki/River_discharge_data CSDMS]

[[Category: Geodata]]
[[Category: Import]]

WCS

2014-01-04T22:55:11Z

⚠️Sbl: /* Using WCS in GRASS GIS, limit to BB */

__TOC__

This page is about support of OGC web coverage services (WCS) in GRASS GIS.

== Metasites and collections of WCS servers ==

* ...

== Using WCS in GRASS GIS ==

One option is to register the WCS service via {{cmd|r.external|version=70}}.

First create ASCII file with this content, named e.g. "wcs_geoserver_LL.wcs":

<source lang="xml">
<WCS_GDAL>
<ServiceURL>http://demo.opengeo.org/geoserver/wcs?</ServiceURL>
<CoverageName>Img_Sample</CoverageName>
</WCS_GDAL>
</source>

or simply download this file from [http://svn.osgeo.org/gdal/trunk/autotest/gdrivers/data/geoserver.wcs here].

Start GRASS in a latlong location (EPSG 4326), then register the WCS file:

<source lang="bash">
r.external input=wcs_geoserver_LL.wcs output=wcs_data
</source>

Then you can look at the map in the wxGUI map display:

[[Image:WCS import with r external.png|thumb|center|400px|Import of WCS via r.external, display with RGB viewer]]

In order to limit the WCS to a bounding box (e.g. from current region) a GDAL vrt file can be created from the WCS ASCII file using gdalbuildvrt:
<source lang="bash">
gdalbuildvrt wcs_geoserver_LL_BB.vrt wcs_geoserver_LL.wcs -te xmin ymin xmax ymax
</source>

== See also ==

* [http://www.gdal.org/frmt_wcs.html WCS_GDAL - OGC Web Coverage Service support]

[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Geodata]]
[[Category: OGC]]
[[Category: Raster]]

AddOns

2012-08-31T13:21:01Z

⚠️Sbl: r.connectivity.* addons added

This page contains references to user contributions and add-ons (the original GRASS GIS software can be downloaded [http://grass.osgeo.org/download/ here]).

__TOC__
== AddOns source code repository ==

The AddOns source code is hosted in [http://svn.osgeo.org/grass/grass-addons/ GRASS-AddOns SVN repository].

To checkout:

svn checkout https://svn.osgeo.org/grass/grass-addons

== Building and installing Addons ==

See the [[Compile and Install#Addons|compile and install]] wiki page.

In GRASS 6.4 and newer you can use the {{cmd|g.extension}} module, e.g. to install <tt>r.fuzzy.system</tt> run:

g.extension extension=r.fuzzy.system

To remove installed Addons run

g.extension extension=r.fuzzy.system operation=remove

== Adding something new ==

=== How to obtain write-access ===

Please read [http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository how to get write access to the GRASS-Addons-SVN repository] and contact the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list if you would like to host your module there.

Please announce your add-on to the GRASS users' mailing list so that others may be aware of your work. Also please consider adding your module to one of the [[Applications]] pages.

=== Copyright and licensing information ===

''Please be sure to include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.''

e.g. at the top of a shell script:
<pre>
#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################
#
# REQUIREMENTS:
# - avcimport: http://avce00.maptools.org

[script follows]
</pre>

=== Coding standards ===

Please have a look at our {{src|SUBMITTING}} for C-programs, {{src|SUBMITTING_PYTHON}} for Python scripts or {{src|SUBMITTING_SCRIPTS|branch=branches/develbranch_6}} for Bash scripts coding standards before submitting here.

=== Documenting your code ===

You can have an help page template auto-generated by using the GRASS [[module command line parser | command line parser]] with the <tt>--html-description</tt> command line option. Please, see also the {{cmd|g.parser}} help page.

== Miscellaneous Add-ons ==

* [http://trac.osgeo.org/grass/browser/grass-addons/grass6/misc/utm_which_zone utm_which_zone.sh] is a shell script to determine UTM zone from Lat/Lon input. Requires [http://www.octave.org Octave] or Matlab to be installed. A shell-only version is [http://dcalvelo.free.fr/grass/utm_which_zone_sh.sh available] which only requires awk. '''Authors''': Hamish Bowman (Octave part), Markus Neteler (shell script wrapper), Daniel Calvelo (sh+awk version)

* Perl scripts for converting data forth and back between Excel files and PostgreSQL: [http://dcalvelo.free.fr/grass/pg2xls.pl pg2xls.pl] reads data from PostgreSQL and produces an excel workbook; [http://dcalvelo.free.fr/grass/xls2sql.pl xls2sql.pl] reads excel files and outputs SQL statements to be fed into an RDBMS. Both scripts need modules from [http://www.cpan.org CPAN], especially [http://search.cpan.org/dist/Spreadsheet-ParseExcel/ Spreadsheet::ParseExcel] for xls2sql.pl and [http://search.cpan.org/~tmtm/Spreadsheet-WriteExcel-FromDB Spreadsheet::WriteExcel::FromDB] and its dependencies for pg2sql.pl. Check the source headers for more info. '''Authors:''' Daniel Calvelo (xls2sql.pl), Markus Neteler (pg2xls.pl)

* [http://dream.lrrl.arch.tu-muenchen.de/~wqual/perl/dbf2sql.tgz dbf2sql] is a Perl script for translating dbf-tables into a sql-command. dbf-tables are read using dbfdump-command from dbd-xbase-perl module ([http://search.cpan.org/~janpaz/DBD-XBase-0.241/ dbd::xbase] and [http://search.cpan.org/~jv/Getopt-Long-2.35/lib/Getopt/Long.pm getopt::long] have to be installed from CPAN first). There are problems, if the last column of the table contains characters. Suggestions for improvements welcome! '''Author:'''Wolfgang Qual

* [http://www.igc.usp.br/pessoais/guano/downloads/azimuth2.c azimuth2.c] is a small C program to calculate the azimuth and length of vector lines exported by GRASS-GIS as ASCII files (like this: v.out.ascii input=vector output=ascii format=standard). It is useful for create rose diagrams of lineament maps. Improvements on the original code after suggestions by Örs Téglásy, Hungary. '''Author:''' Carlos Henrique Grohmann

* [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 ann.*] is the set of GRASS modules (in python) which implements artificial neural network using FANN library. The package requires Fast Artificial Neural Network Library ([http://leenissen.dk/fann/wp/ FANN]) v2.x. '''Author:''' Pawel Netzel

* [http://trac.osgeo.org/grass/browser/grass-addons/tools/csv_dequote.pl csv_dequote.pl] is a Perl script to convert comma separated .csv files (including "quoted" text strings containing commas) into a form ready for {{Cmd|v.in.ascii}}. Comma separators are converted to pipes (|), commas in quoted strings are preserved, and "quotes" are removed where it is appropriate to do so. It doesn't need GRASS to run, but it does need the Text::CSV Perl Module (<tt>apt-get install libtext-csv-perl</tt>). '''Author''': Hamish Bowman

== GRASS 6.x (current) ==
* todo: move this content to [[AddOns/GRASS6]]
: (requires an update of the mediawiki AddOnCmd macro to be more like the versioned html doc macro)

See also
svn co https://svn.osgeo.org/grass/grass-addons/grass6/

=== Vector add-ons ===

See also
svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector

==== v.adehabitat.clusthr, v.adehabitat.kernelUD, v.adehabitat.mcp ====

: Tools to calculate home ranges of animals
: '''Author:''' Clement Calenge

Available via SVN or {{cmd|g.extension}}:
svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/adehabitat

==== v.append ====

: [http://web.archive.org/web/20060914172621/http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.append v.append] is a shell script combining two vector files AND their associated attribute tables. The vector files should be of the same type and, for best results, should have identically formatted attribute tables.
: ''Note'': also module ''v.patch'' can be used for this task.

: '''Author:''' Michael Barton

==== v.autokrige ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.autokrige/v.autokrige.py v.autokrige] achieves automatic ordinary kriging from GRASS sites (vector point data), using R with spgrass6 (RGRASS) and automap packages.

: '''Author:''' Mathieu Grelier

==== v.breach ====

: [http://www.sieczka.org/programy_en.html v.breach] creates vector maps of lines and points of continously lowering elevation down the input watercourses, based on the input raster DEM.

: '''Author:''' Maciej Sieczka

==== v.colors ====

: {{cmd|v.colors}} ''moved into main archive''

==== v.count.points.sh ====

: [http://wiki.iosa.it/dokuwiki/spatial_analysis:feature_count v.count.points.sh] counts point features in areas, generates table good as input to d.vect.chart.

: '''Author:''' Stefano Costa

==== v.digatt ====

: [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt v.digatt] (shell script) Interactively assign numeric table attributes to series of vector objects. It is meant to be effective by avoiding to type in the attribute value for all single objects again and again. The user is prompted for typing in an attribute value which is assigned to all objects selected by mouseclick afterwards. Next the display is redrawn after updating the table column. Zooming allows to change the region before the old value can be reused or a new one can be typed in (or copied by mouse from another object) in order to assign it to the next series of objects etc. It is tested not very extensively yet. Therefore better work with a copy of your map and consider using v.digit or d.what.vect -e alternatively. [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt.png screenshot].

: '''Author:''' Andreas Philipp

==== v.dip ====

: [http://marcin.slodkowski.googlepages.com/v.dip.tgz v.dip] creates points of thickness vectors from the vectors of strike and dip angles. The v.dip is the main ANSI C core program. Program so-called v.dip can run without GRASS environment.

: '''Author:''' Marcin Slodkowski

==== v.flip ====

: [http://www.sieczka.org/programy_en.html v.flip] flips the direction of selected vector lines (redundant since GRASS 6.3 - there is "v.edit tool=flip").

: '''Author:''' Maciej Sieczka

==== v.group ====

: [http://www.shockfamily.net/cedric/grass/v.group v.group] generates a new vector map with the same geometry as an existing map. The new map has categories and a table based on grouping by the values in certain columns of the existing map's table. The values in these columns are preserved in the table for the new map. It's like a v.reclass that preserves data.

: '''Author:''' Cedric Shock

==== v.in.gama ====

: Converts [http://www.gnu.org/software/gama/ GNU GaMa] XML output file to a GRASS vector map layer.

:'''Author:''' Martin Landa

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.in.gama

==== v.in.geodesic ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.geodesic v.in.geodesic] is a shell script which will create a new vector map containing a great circle line. The user may either define a beginning and end coordinate, or define a starting coordinate along with initial azimuth and desired line length.

: '''Author:''' Hamish Bowman

==== v.in.geoplot ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.geoplot v.in.geoplot] converts a [http://www.geoscan-research.co.uk/page9.html/ Geoplot] ASCII export file to a GRASS vector map layer.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.in.geoplot

==== v.in.gshhs ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.gshhs v.in.gshhs] imports [http://www.soest.hawaii.edu/pwessel/gshhs/index.html GSHHS] shorelines into a GRASS vector map. GSHHS data are automatically reprojected to the current location.

:'''Authors:''' several, updated to GRASS 6 by Markus Metz

==== v.in.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.marxan v.in.marxan] is a python script that imports Marxan output data for display in a vector grid file prepared using v.out.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.in.mbsys_fnv ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.mbsys_fnv v.in.mbsys_fnv] imports [[MB-System]] navigation files into a GRASS vector map. You can choose from swath area coverage, track lines (including outer port/starboard edges), all bounds as points, etc. An attribute database is created containing the vital statistics of the specified feature such as track length or swath coverage (geodesic), start stop time and location, pitch, roll, heave, etc. See also the [[#v.in.p190]] addon.

:'''Author:''' Hamish Bowman

==== v.in.ncdc ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.ncdc v.in.ncdc] imports an [http://www.ncdc.noaa.gov NCDC] stn file (station data) into a GRASS vector map.

: '''Author:''' Huidae Cho

==== v.in.osm ====

: [http://kripton.kripserver.net/software/v.in.osm/ v.in.osm]: OpenStreetMap import into GRASS. Yet only supports deprecated API 0.4, will be modified to work with API 0.5 some time soon.

: '''Author:''' Jannis Achstetter

: See also [http://hamish.bowman.googlepages.com/gpsdrivefiles#osm osm2grass.sh] by H Bowman

==== v.in.osm2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.osm2 v.in.osm2]: OpenStreetMap import into GRASS. Supports current API 0.6, downloads using the [http://wiki.openstreetmap.org/wiki/Xapi Xapi] interface and imports using GpsBabel 1.3.5 or newer. GpsBabel restricts to either nodes or ways being imported at a time, not both. Use {{cmd|v.patch}} to rejoin them. (''work in progress'')

: '''Author:''' Hamish Bowman

==== v.in.ovl ====

: [http://grasslab.gisix.com/scripts/v.in.ovl/ v.in.ovl] is a shell script that imports an ASCII vector file created with TOP10|25|50 or similar products.

: '''Author:''' Peter Löwe

==== v.in.p190 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.p190 v.in.p190] is a shell script that imports 'Centre of Source' "S" navigation data from seismic P1/90 (UKOOA) data files and writes it either GRASS vector points or vector lines format. Optionally it will export the navigation data into .csv text files as well. ''Currently in the functional prototype stage, some assembly is required. See inside the shell script for details.'' For working with SEG-Y data, see also the [[#v.in.mbsys_fnv]] addon.

: '''Author:''' Hamish Bowman

==== v.in.ply ====

* GRASS 6: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.ply v.in.ply] is a shell script that imports a PLY file and writes it as GRASS vector points. For a much more advanced version, see the GRASS 7 version.

: '''Author:''' Markus Neteler

* GRASS 7: [https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.ply v.in.ply] is a C program that imports a PLY file and writes it as GRASS vector map.

: '''Author:''' Markus Metz

==== v.in.postgis ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.in.postgis/v.in.postgis.py v.in.postgis] Create a GRASS layer from any sql query on PostGIS data.

: '''Author:''' Mathieu Grelier

==== v.in.redwg ====

: [http://lists.gnu.org/archive/html/info-libredwg/2010-08/msg00000.html v.in.redwg imports DWG files into GRASS.]
:'''Author:''' Rodrigo Rodrigues da Silva

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.in.redwg

==== v.krige ====

: [[V.krige_GSoC_2009 | v.krige]] aims to integrate R functions for kriging (packages automap, gstat, geoR) in a trasparent way. '''Moved into trunk/devbr6 code (r40048)'''

: '''Author:''' Anne Ghisla, as Google Summer of Code 2009 project

: See also [[GRASS_AddOns#v.autokrige]] by Mathieu Grelier

==== v.lda.py ====
* '''Spatial Analysis Tools'''

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.lda.py v.lda.py] is a Python script for calculating Ian Johnson's (U. Sidney) Local Density Analysis values. This can be used in two ways. When only one vector points file is entered, it serves to measure clustering of point data at different neighborhood radii. When two different point files are entered, it measures the the co-occurence of the points from the two files. There is an option to export the data into a cvs format file for easy plotting in a spreadsheet or statistical program like R.

==== v.nn.py ====
* '''Spatial Analysis Tools'''

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.nn.py v.nn.py] is a Python script for calculating the nearest neighbor coefficient of a single vector points file--as an index of clustering--or of two points files--to provide an index of the correspondence between the points in one file and points in a different file.

==== v.ldm ====
:[https://raw.github.com/amuriy/GRASS-scripts/master/v.ldm v.ldm] Shell script to compute "Linear Directional Mean" of vector lines, to display LDM graphics on the graphic monitor, and optionally to save it to vector line and update attribute table with LDM parameters.
:See [http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/How_Linear_Directional_Mean_works/005p0000001r000000/ this link] for full LDM description.

: '''Author:''' Alexander Muriy

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.ldm/

==== v.line.center ====

: [http://www.sieczka.org/programy_en.html v.line.center] creates a points vector map with each point located in the middle of the length of the input vector line.

: '''Author:''' Maciej Sieczka

==== v.lmeasure ====

: [http://web.archive.org/web/20060827192321/http://ngeo.de/grassstuff/v.lmeasure v.lmeasure] and [http://web.archive.org/web/20060827060303/http://ngeo.de/grassstuff/v.revlmeasure v.revlmeasure] are two perl scripts that place equidistant vector points along a given arbitrary vector line starting from the beginning or end of the vector line, respectively. Resulting vector points are labeled with the distance from origin.

: '''Author:''' Mats Schuh

==== v.mainchannel ====

: [https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.strahler/v.mainchannel.html v.mainchannel] is a shell script which finds the main channel of a basin starting from the vector file of the stream network.
: '''Author:''' Ivan Marchesini, Annalisa Minelli

Available via SVN or {{cmd|g.extension}}:
svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.strahler/v.mainchannel.sh

==== v.mk_circle ====

: [http://tekmap.ns.ca/blog/grass_mk_circle v.mk_circle] is a program to create a closed vector at a user defined location and size. The program supports output of different shapes, open boundaries and closed centroids, and will accept multiple locations and sizes from an ASCII file or standard input. GRASS 7 version is also available.

: '''Author:''' Bob Covill

==== v.mkhexgrid ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.mkhexgrid v.mkhexgrid] is a python script that creates a hexagonal grid the size of the selected region using user specified side lengths or areas. This has been updated 2011-09-14.

: '''Author:''' Trevor Wiens

==== v.out.ascii.db ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.out.ascii.db v.out.ascii.db] is a shell script for exporting vector point data coordinates and selected attribute columns to either a file or to the console.
: ''Superseded in GRASS 6.4 by the new v.out.ascii columns= option.''

: '''Author:''' Hamish Bowman

==== v.out.ascii.mat ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.out.ascii.mat v.out.ascii.mat] is a shell script for exporting vector polygon and polyline data into an ASCII text file suitable for loading into Matlab (or [http://www.gnu.org/software/octave/ Octave]).

: '''Author:''' Hamish Bowman

==== v.out.geoserver ====

: [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 v.out.geoserver] is a shell script for exporting vector data to [http://geoserver.org GeoServer] directly. It uses: v.out.ogr, curl, zip and GeoServer REST interface.

: '''Author:''' Pawel Netzel

==== v.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.out.gmt v.out.gmt] is a shell script that exports a polygon vector file into GMT xy file. psbasemap code was copied from Hamish's r.out.gmt.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== v.out.kml ====

: [http://grasslab.gisix.com/scripts/v.out.kml/ v.out.kml] is a shell script that exports a vector file into a KML file for Google Earth or Worldwind. see also [[#r.out.kml|r.out.kml]] and [[#r.out.gmap|r.out.gmap]]

: '''Author:''' Peter Löwe

==== v.out.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.out.marxan v.out.marxan] is a python script that prepares vector layers and exports GRASS vector attributes and adjacency information as Marxan input files. Output from Marxan simulations can be imported using v.in.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.out.ply ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.out.ply v.out.ply] is a shell script that exports a GRASS vector points cloud into a PLY file.

: '''Author:''' Markus Neteler

==== v.out.svg ====

: [http://svg.cc/assvg/grass.html v.out.svg] is a module that exports SVG notation along with optional attribute data directly from GRASS 6.x vector layers. Now part of [http://svn.osgeo.org/grass/grass/trunk/vector/v.out.svg/ grass6-svn].

: '''Author:''' Klaus Förster

==== v.points.cog ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.points.cog v.points.cog] is a shell script which will create a new point at the center of gravity of each cluster of input points or centroids, grouped by attribute. Among other things this is useful for labeling swarms of points.

: '''Author:''' Hamish Bowman

==== v.profile ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.profile v.profile] is vector map profiling tool similar to r.profile. This module will print out distance and attributes to points/lines along profiling line. It's also usefull to determine places where raster profile crosses vector features (i.e. where to place river marker on river walley crossection).

: '''Author:''' Maris Nartiss

==== v.random.cover ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.random.cover v.random.cover] is a shell script for creating random points constrained within an irregularly shaped vector area. (v.random places points only in current region rectangle). Optionally the user can upload raster values at the points. See also '<tt>r.random cover= vector_output=</tt>'

: '''Author:''' Hamish Bowman

==== v.rasterbounds ====

: [http://les-ejk.cz/programs v.rasterbounds] is a shell script for creating polygon-vector file of rasterfile boundaries. The best version of GRASS is 6.1+. If you are using GRASS < 6.1, you have to be in the same mapset as your raster maps are from.

: '''Author:''' Jachym Cepicky

==== v.rast.stats2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.rast.stats2 v.rast.stats2] is an adapted version of the GRASS module v.rast.stats. It uses the grass addon [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.univar.zonal r.univar.zonal] to speed up calculation of univariate statistics from a GRASS raster map based on vector polygons.

: '''Authors:''' Markus Neteler, Otto Dassau

==== v.sample.buffer ====
* ''Currently unavailable. Being re-written in python. Target for inclusion in addons svn is January 2011''
''v.sample.buffer'' is a shell script that samples rasters in buffers of a specified size around features in a specified vector file. Sampling results are added as attributes to the vector file. This script was designed for sampling vegetation indices and DEM derived attributes for bird point counts. Sampling results can be one or more basic statistics such as mean, range, max, etc.

: '''Author:''' Trevor Wiens

==== v.select.region ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/v.select.region.tar.bz2 v.select.region] is a shell script that prints out the names of all vectors matching an input search pattern that has geometry (points, line, areas) that fall within a region bounded by an existing vector map, or within the current Grass region.

: '''Author:''' Eric Patton

==== v.selmany ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/vector/v.selmany/v.selmany v.selmany] is a shell script that allows to interactively select a set of vector objects on a given layer, then assign them attribute values in a connected database table. The script runs on the command line prompt and within a graphic monitor ; it does not work with DBF driver.

: '''Author:''' Vincent Bain

==== v.surf.icw ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.surf.icw v.surf.icw] is an IDW interpolation method using true distance cost instead of euclidean shortest distance, i.e. ''as the fish swims around an island'' not ''as the bird flies''. This will cleanly travel around hard barriers and a cost surface map may be used to model expensive-cross barriers. Input data points do not need direct line of sight to be considered, but should be kept to less than one hundred as the module becomes very computationally expensive. A number of radial basis function options are available. ([http://grass.osgeo.org/wiki/Image:Inlets_03_SurfSal_icw_big.png screenshot])

: '''Author:''' Hamish Bowman

==== v.surf.idwpow ====

: [http://www.geospatial.it/allegri/grass/v.surf.idwpow.zip v.surf.idwpow] integrates the common v.surf.idw algorithm with the exponential parameter for the distance weights

: '''Author:''' Giovanni Allegri

==== v.surf.krige [deprecated: use v.autokrige instead] ====

: v.surf.krige is a script that do a surface interpolation from vector point data by Kriging method. The interpolated value of a cell is determined by using an omnidirectional variogram model fitted starting from model parameter given by user shown from the experimental semi variogram produced by v.variogram. The script can perform also the Leave-One-out cross validation to test the variogram model "fitted by eye" and an automatic fitted variogram model. The cross validation helps the user to choose the best variogram model to interpolate own data.

: '''Author:''' Pierluigi De Rosa.

==== v.strahler ====

: [http://www.pois.org/florian/downloads/grass/v.strahler.tgz v.strahler] is a module that calculates the Strahler Order for all lines of a given dendritic network.

: '''Author:''' Florian Kindl. Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.strahler

==== v.swathwidth ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.swathwidth v.swathwidth] creates a vector map representing the sea bottom coverage of a multibeam (swath) sonar survey.
: ([http://david.p.finlayson.googlepages.com/swathwidth Screenshots])

: '''Authors:''' David Finlayson, Hamish Bowman

==== v.thickness ====

: [http://marcin.slodkowski.googlepages.com/v.thickness.tgz v.thickness] creates points of thickness vectors from the vectors of strike and dip angles.The v.thickness is GUI GRASS script for v.dip.

: '''Author:''' Marcin Slodkowski

==== v.transect.kia ====

: [https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.transect.kia v.transect.kia] calculates kilometric abundance indexes (KIA), a common indirect presence index used in wildlife monitoring along line transect surveys.
: Path lenghts can be corrected by draping on a DEM, different type of point objects can be weighted according to their relative importance, and paths can be segmented using a further polygon vector (to calculate, say, abundances per elevation range or per habitat class).
: The module is written in bash and needs a GRASS install compiled with sqlite support.

: '''Author:''' Clara Tattoni and Damiano G. Preatoni

==== v.transects ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.transects v.transects] is a python script that creates a set of equidistant lines (transects) that are perpendicular to an input vector line file. Points and quadrilateral areas are alternative outputs.

: '''Author:''' Eric Hardin

==== v.trees3d ====

: [http://les-ejk.cz/programs/ v.trees3d] is a module for making 3D trees from input vector point file.

: '''Author:''' Jachym Cepicky

==== v.triangle ====
: [https://raw.github.com/amuriy/GRASS-scripts/a7df12d996abfe6461f509fce6feb6c869af2d5e/v.triangle v.triangle] -- front-end for <Triangle> utility (http://www.cs.cmu.edu/~quake/triangle.html) of J.R. Shewchuk.

Makes exact Delaunay triangulations, constrained Delaunay triangulations, conforming Delaunay triangulations and high-quality triangular meshes. In GIS terminology, it produces 2D TIN, optionally with "breaklines".
For more details see GRASS-wiki page [http://grass.osgeo.org/wiki/TIN_with_breaklines TIN with breaklines].

: '''Author:''' Alexander Muriy

==== v.trimesh ====
: [http://www.valledemexico.ambitiouslemon.com/vtrimesh.html v.trimesh] creates a triangular mesh from a vector map using areal constraints for refinement. It uses Jonathan Shewchuk's Triangle library.

: '''Author:''' Jaime Carrera

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.trimesh/

==== v.to.averline ====

: [https://raw.github.com/amuriy/GRASS-scripts/a7df12d996abfe6461f509fce6feb6c869af2d5e/v.to.averline v.to.averline] is a shell script to find "average" line(s) of input vector map. It works with simple algorithm stated [http://forums.arcgis.com/threads/26757-quot-Averaging-quot-lines?p=88781&viewfull=1#post88781 here] (2 methods -- average distance to vectors sampling or average number of vectors segments).

: '''Author:''' Alexander Muriy

==== v.to.equidist ====

: [https://raw.github.com/amuriy/GRASS-scripts/master/v.to.equidist v.to.equidist] is a shell script that generates vector points or line segments along a given vector line(s) with the equal distances (uses v.segment)

: '''Author:''' Alexander Muriy

==== v.what.rast.buffer ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.what.rast.buffer v.what.rast.buffer] is a script that calculates univariate statistics of raster map(s) from buffers around vector points. Results are written to a file. Resolution is taken from each input map.
: ''see also the [http://starspan.casil.ucdavis.edu StarSpan] software

: '''Author:''' Hamish Bowman

==== v.variogram ====
* [deprecated: use v.autokrige instead]

: v.variogram is a script that create an omnidirectional experimental semi-variogram. This scripts require R-statistics software installed on your machine. Now the script is updated to run on spgrass6 >= 0.3 and sp >= 0.9 [http://grass.osgeo.org/pipermail/statsgrass/2006-October/000455.html reply].

: '''Author:''' Ivan Marchesini, Pierluigi De Rosa.

==== v.vect.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/vector/v.vect.stats v.vect.stats] counts the number of points falling into each polygon and optionally calculates statistics from numeric point attributes for each polygon. v.vect.stats is a C module for GRASS 6.4 and 6.5 (see enclosed patch for 6.5, applies also to 6.4.2) and included in GRASS 7.

: '''Author:''' Markus Metz

==== AniMove ====

: [http://www.faunalia.it/animov/ AniMove] is software for analysis of animal movement and ranging behaviour using QGIS+GRASS+R.

:'''Authors:''' Support by Faunalia.it

==== Utilities ====

===== Shapemerge =====

: [http://perrygeo.googlecode.com/svn/trunk/gis-bin/shpmerge.sh shpmerge] merges all the shapefiles in the current directory into a single output shapefile

:'''Authors:''' Perrygeo

=== Raster add-ons ===

See also:

svn co http://svn.osgeo.org/grass/grass-addons/grass6/raster

==== Raplat ====

GRASS-RaPlaT: The Radio Planning Tool for GRASS GIS system developed by support of Slovenian largest mobile operator Mobitel. It is especially designed for radio coverage calculation of GSM/UMTS systems, but can be applied also to other wireless systems in the frequency range 400 MHz – 2.4 GHz (e.g. TETRA, WiFi). Its structure is modular and characterized by high level of flexibility and adaptability.

* Documentation: http://commsys.ijs.si/en/component/content/article/54-software/149-user-manual
* Software: http://commsys.ijs.si/en/software/grass-raplat

: '''Author:''' Department of Communication Systems, Jozef Stefan Institue, Jamova 39, SI-1000 Ljubljana, Slovenia

==== r.area ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.area r.area] Very simple module. Calculate area size (in cells) for every individual category in input raster map and write number of cells as the value of each cell in the area. Optionally write a binary coverage map and set a minimum area threshold. Works well with {{cmd|r.clump}}.

: '''Author:''' Jarek Jasiewicz

==== r.basin ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.basin/ r.basin] Generates the main morphometric parameters of the basin starting from the digital elevation model and the coordinates of the basin's closing section (see [http://grass.osgeo.org/wiki/R.basin wiki] for howto).

: '''Author:''' Margherita Di Leo, Massimo Di Stefano

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.basin/

==== r.bilateral ====

: [http://les-ejk.cz/files/programs/grass/r.bilateral.tgz r.bilateral] Bilateral filter is an edge-preserving filter, which combines domain and range filtering. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.broscoe ====

: r.broscoe.sh calculates waerden test and t test statistics for some values of threshold area on a single basin, according to A.J.Broscoe theory (1959). Dependence: v.strahler package.
: '''Authors:''' Ivan Marchesini, Annalisa Minelli

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/vector/v.strahler/

==== r.boxcount ====

: r.boxcount and r.boxcount.sh calculate the fractal dimension for a given map. These are versions for grass6 of [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake's modules] for grass43.

: '''Authors:''' Mark Lake, grass6 port: Florian Kindl.

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.boxcount/
svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.boxcount.sh/

==== r.burn.frict ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.burn.frict r.burn.frict] converts vector geometries to raster cells, using a simple anti-aliasing method to close "gaps" between diagonal cells. Useful for "burning" vector geometries into a friction surface, making sure that simulated movement does not "slip" through converted cells that have only diagonal neighbours.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.burn.frict

==== r.clump2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.clump2 r.clump2] is a C module similar to r.clump. Differences are: diagonally adjacent cells are also clumped but can be excluded, NULL (nodata) cells are always excluded, and selective clumping with start coordinates is supported.

: '''Author:''' Markus Metz

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.clump2

==== r.colors.out_sld ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.colors.out_sld r.colors.out_sld] is a shell script used to export the color table associated with a raster map layer to an OGC [http://docs.geoserver.org/latest/en/user/styling/sld-cookbook/rasters.html SLD] XML file, for use with [[GeoServer]] and the ilk.

: '''Author:''' Hamish Bowman

==== r.colors.out_vtk ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.colors.out_vtk r.colors.out_vtk] is a shell script used to export the color table associated with a raster map layer to a {{wikipedia|VTK}} XML file. (see also [[Help with 3D]])

: '''Author:''' Hamish Bowman

==== r.colors.quantiles ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.colors.quantiles/r.colors.quantiles r.colors.quantiles] is a shell script used to create raster colors rules based on nquantiles. It uses R and spgrass6 package (RGRASS).

: '''Authors:''' Mathieu Grelier

==== r.colors.stddev ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.colors.stddev] ''moved into main archive''

==== r.connectivity.distance ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.distance r.connectivity.distance] is a shell script, which is - as a part of the r.connectivity.* tool-chain - intended to make connectivity analysis based on graph-theory more easily available to conservation planning. r.connectivity.distance computes the (cost) distance between all habitat patches of an input vector map within a user defined euclidean distance threshold. See also [[#r.connectivity.network]] and [[#r.connectivity.corridors]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.distance/

==== r.connectivity.network ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.network r.connectivity.network] is a shell script, which is - as a part of the r.connectivity.* tool-chain - intended to make connectivity analysis based on graph-theory more easily available to conservation planning. r.connectivity.network performs the (core) network analysis and computes connectivity measures for a set of habitat patches based on graph-theory (usig the igraph-package in R). See also [[#r.connectivity.distance]] and [[#r.connectivity.corridors]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.network/

==== r.connectivity.corridors ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.corridors r.connectivity.corridors] is a shell script, which is - as a part of the r.connectivity.* tool-chain - intended to make connectivity analysis based on graph-theory more easily available to conservation planning. r.connectivity.corridors computes corridors between habitat patches for edges from r.connectivity.network based on (cost) distance raster maps from r.connectivity.distance and assigns user defined weight to the corridors. See also [[#r.connectivity.distance]] and [[#r.connectivity.network]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.corridors/

==== r.convergence ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.convergence r.convergence] calculate topographic convergence index, useful to detect lineamets represented by chanell/ridge system

: '''Author:''' Jarek Jasiewicz

==== r.cpt2grass ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.cpt2grass] is a GRASS script for importing a [http://www.soest.hawaii.edu/gmt/ GMT] .cpt color table into GRASS. It can save to a text file suitable for r.colors or automatically apply the color table to a raster map. For a large collection of GMT .cpt files see http://sview01.wiredworkplace.net/pub/cpt-city/
: Other palette ideas from [http://geography.uoregon.edu/datagraphics/color_scales.htm Univ. Oregon] and [http://oceancolor.gsfc.nasa.gov/PRODUCTS/colorbars.html NASA/Goddard's OceanColor] (latter partially translated for use with GRASS on the [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.colors.tools/palettes grass-addons SVN]).

: '''Author:''' Hamish Bowman

==== r.csr ====

: [https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.csr r.csr] integrates several Grass programs to produce colored, shaded-relief rasters in one step. Accepts single or multiple elevation/bathymetry maps as input; optionally will fill data holidays with 3x3 median filter, multiple times, if required; can apply color maps from a) input raster, b) another raster in MAPSET, or c) from a rules file; otherwise, rainbow colorbar is applied. Output colored, shaded-relief rasters can optionally be exported to tiff format if the appropriate flag is given. Shading parameters can be modified, though useful defaults are given.

: '''Author:''' Eric Patton

==== r.cva ====

: [http://www.ucl.ac.uk/~tcrnmar/GIS/r.cva.html r.cva] is a cumulative viewshed analysis module. It is an advanced version of the {{cmd|r.los}} program.

: '''Author:''' [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.cva/

==== r.denoise ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.denoise r.denoise] denoises (smooths/despeckles) topographic data, particular DEMs derived from radar data (including SRTM), using Xianfang Sun's [http://www.cs.cf.ac.uk/meshfiltering/index_files/Page342.htm denoising algorithm]. It is designed to preserve sharp edges and to denoise with minimal changes to the original data. See the [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.denoise/description.html manual pages] for details. Further information on Sun's denoising algorithm, including an example, is available [http://personalpages.manchester.ac.uk/staff/neil.mitchell/mdenoise/ here].

: '''Author:''' John Stevenson

==== r.dominant_dir.m and r.calc_terraflow_dir.m ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.terraflow.tools dominant_dir.m and calc_terraflow_dir.m] are two Matlab scripts for determining the dominant flow direction from a r.terraflow MFD map and converting into a GRASS aspect map for use with d.rast.arrow, etc.

: '''Author:''' Hamish Bowman

==== r.diversity ====
: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.diversity/ r.diversity] calculates selected diversity indices by calling various r.li commands.This script uses the [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.pielou.html Pielou], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.renyi.html Renyi], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.shannon.html Shannon] and [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.simpson.html Simpson] indices. The output is a map for each index.

: '''Author:''' Luca Delucchi, Duccio Rocchini

==== r.eucdist ====

: [http://david.p.finlayson.googlepages.com/r.eucdist r.eucdist] creates a raster map estimating the euclidean distance from known cells.

: '''Author:''' David Finlayson

==== r.forestfrag ====

: [http://dl.dropbox.com/u/10445979/r.forestfrag.sh r.forestfrag.sh] creates forest fragmentation index from a GRASS raster map (where forest=1, non-forest=0) based on a method developed by Riitters et. al (2000). So far only running/tested on GRASS 6.4 and only with 3x3 moving window (shell-script has to be adjusted for other window-sizes)
: '''Author:''' Maning Sambale, Stefan Sylla

==== r.fragment ====

: [http://www.chrisgarstin.com/stuff/r.fragment r.fragment] fragments a raster into a user-defined set of smaller tiles according to an input number of rows and columns.
: '''Author:''' Eric Patton

==== r.fuzzy ====
: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.fuzzy r.fuzzy] Calculates membership of every cell in raster according membership function defined by user.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.logic ====
: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.fuzzy.logic r.fuzzy.logic] Perform fuzzy operators (AND, OR, NOT, IMP) on membership's map using T-norms and T-conorms for 6 most popular families.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.system ====
: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.fuzzy.system r.fuzzy.system] Perform full fuzzy clasificationwith 6 most popular fuzzy logic families and few methods of deffuzification.
: '''Author:''' Jarek Jasiewicz

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.fuzzy.system

==== r.game_of_life ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.game_of_life r.game_of_life] is a shell script which runs Conway's classic Game of Life using GRASS raster modules. It is meant to demonstrate how easy it is to program cellular automata in GRASS as well as various 3D raster volume and time series visualization techniques.

: '''Author:''' Hamish Bowman

==== r.gauss ====

: [http://www.les-ejk.cz/files/programs/grass/r.gauss.tgz r.gauss] is Gaussian and Laplacian of Gaussian filter for GRASS. It is written in C language.

:'''Author:''' Jachym Cepicky

==== r.gradgrid4 ====

: [http://www.uibk.ac.at/geographie/personal/mergili/gradgrid4.zip gradgrid4] is a tool for interpolating values of discrete data points to a raster map, applying a local regression approach with a predictor raster. The model is based on shell and python scripts as well as an R batchfile. It was tested on Fedora Core 6 with GRASS 6.2.1 and R 2.5.1, but should work under most UNIX systems. After unzipping the gradgrid4 folder, store it at any place in your local file system. In the subfolder docs you can find a manual and a publication draft with a detailed description of the concept and the example of an application. The subfolder testloc constitutes a GRASS location with test data.

: '''Author:''' Martin Mergili

==== r.hazard.flood ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.hazard.flood/ r.hazard.flood] is an implementation of a fast procedure to detect flood prone areas. The exposure to flooding may be delineated by adopting a topographic index (TIm) computed from a DEM. The portion of a basin exposed to flood inundation is generally characterized by a TIm higher than a given threshold, tau. The threshold is automatically determinated from the cellsize. The proposed procedure may help in the delineation of flood prone areas especially in basins with marked topography. The use of the modified topographic index should not be considered as an alternative to standard hydrological-hydraulic simulations for flood mapping, but it may represent a useful and rapid tool for a preliminary delineation of flooding areas in ungauged basins and in areas where expensive and time consuming hydrological-hydraulic simulations are not affordable or economically convenient.

: '''Author:''' Margherita Di Leo

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.hazard.flood/

==== r.hydrdem ====

'''r.hydrodem''' applies hydrological conditioning (sink removal) to a required input elevation map. If the conditioned elevation map is going to be used as input elevation for r.watershed, only small sinks should be removed and the amount of modifications restricted with the mod option. For other modules such as r.terraflow or third-party software, full sink removal is recommended.

: '''Author:''' Markus Metz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass7/raster/r.hydrodem/

==== r.in.ign ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.ign/ r.in.ign] imports raster data from [http://api.ign.fr IGN WMS-C stream service]. Yet an uncompleted version, briefly documented [http://grass.osgeo.org/wiki/IGN_wms-c_stream here].

: '''Author:''' Vincent Bain

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.in.ign/

==== r.in.mb ====

: [http://www.tekmap.ns.ca/blog/multibeam_import r.in.mb] is a "GRASS/[[MB-System]] program designed to import ''mbio'' compatible multibeam sonar data directly into the GRASS GIS. The program is a modified version of {{cmd|r.in.xyz}}. Instead of reading an ASCII XYZ file, ''r.in.mb'' reads an MB-System compatible list file." It can do automatic reprojection and minor hole filling. Options for restricting data according to line length, speed, acrosstrack width, beam number and survey mode (Simrad only). The default is to import bathymetry data, but optionally amplitude or sidescan sonar data can be loaded instead. GRASS 7 version is also available.

: '''Author:''' Bob Covill

==== r.in.onearth ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.onearth r.in.onearth]  for download and import satellite images direct from the NASA OnEarth WMS server into GRASS.

: '''Authors:''' Soeren Gebbert, Markus Neteler, Hamish Bowman

==== r.in.srtm.region ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.in.srtm.region r.in.srtm.region] for download and import of SRTM for the current region. If needed, tiles are patched together and optionally holes interpolated.

: '''Author:''' Markus Metz

==== r.in.swisstopo ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.swisstopo/ r.in.swisstopo] for importing swisstopo digital elevation model data into GRASS raster maps.

: '''Author:''' Jürgen Hansmann

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.in.swisstopo/

==== r.in.wms (.py) ====

: [http://les-ejk.cz/files/programs/grass/r.in.wms.tgz r.in.wms] for download and import maps direct from WMS servers into GRASS. This script is written in Python Programming language. Note GRASS 6.2+ provides a shell script version of r.in.wms, take care of which one is actually being run.

: '''Author:''' Jachym Cepicky

==== r.in.xyz.auto ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.xyz.auto r.in.xyz.auto] runs the {{Cmd|r.in.xyz}} module, automatically setting up the region extent for you. ''For useful output it is strongly recommended to manually set the region resolution and bounds yourself instead of using this script.''

: '''Author:''' Hamish Bowman

==== r3.in.xyz ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster3d/r3.in.xyz r3.in.xyz] creates a 3D raster map from an assemblage of many coordinates using univariate statistics. It is the 3D version of {{Cmd|r.in.xyz}}.

: '''Author:''' Hamish Bowman

==== r.inund.fluv ====

: [https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.inund.fluv/ r.inund.fluv]This command allows to obtain a fluvial potentially inundation map given a high-resolution DTM of the area surrounding the river and a water surface profile calculated through an 1-D hydrodinamic model.

: '''Authors:''' Roberto Marzocchi, Bianca Federici, Domenico Sguerso

==== r.isoregions ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.isoregions/r.isoregions r.isoregions] allows isoregions creation from a GRASS raster map.

: '''Authors:''' Mathieu Grelier

==== r.interp.mask ====

: [http://david.p.finlayson.googlepages.com/r.interp.mask r.interp.mask] Creates a user-specified buffer around interpolation points that can be used as a MASK to prevent or clip excessive extrapolation artifacts. This works much better than a standard convex hull around the points.

: '''Author:''' David Finlayson

==== r.ipso ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.ipso/ r.ipso] Produces the ipsometric and ipsographic curve related to a digital elevation model and prints the percentiles

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.ipso/

==== r.li ====

: [http://www.faunalia.it/download/r_li/ r.li] is a more flexible and faster replacement of the old r.le. '''''Moved into 6.3-SVN'''''.

: '''Authors:''' Claudio Porta, Davide Spano, Serena Pallecchi, [http://www.faunalia.it Faunalia]

==== r.local_max.pl ====

: [http://les-ejk.cz/files/programs/local_max.pl Local maxima] is a Perl script for <code>r.mapcalc</code>. It detects local maxima of the image.

: '''Author:''' Jachym Cepicky

==== r.mandelbrot ====

: [http://grasslab.gisix.com/scripts/r.mandelbrot r.mandelbrot] is a shell script to calculate the Mandelbrot set.- for GRASS versions 6.X.

: '''Author:''' Peter Löwe

==== r.maxent.lambdas ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.maxent.lambdas r.maxent.lambdas] is a shell script to compute raw and/or logistic prediction maps from a lambdas file produced with MaxEnt 3.3.3e. See also [[#r.out.maxent_swd]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.maxent.lambdas/

==== mcda ====

: mcda suite is a toolset for geographics multi-criteria decision aiding and data analysis based on ELECTRE (r.mcda.electre), REGIME (r.mcda.regime) and FUZZY (r.mcda.fuzzy) algorithm. The module r.roughset is also included for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/mcda/

==== r.modis ====

:The '''r.modis''' suite is a toolset to import MODIS satellite data in GRASS GIS. It uses the [http://gis.cri.fmach.it/pymodis/ pyModis library] and the MODIS Reprojection Tool software to convert, mosaik and process MODIS data. It is written in Python language for GRASS 7, developed during the Google Summer of Code 2011.

See also [[R.modis]]:

: '''Author:''' Luca Delucchi (GSoC mentor: Markus Neteler)

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass7/raster/r.modis/

==== r.mlv ====

: [http://les-ejk.cz/files/programs/grass/r.mlv.tgz r.mlv] is Mean of least variance filter for GRASS. It is an edge-preserving (or even edge-enhacing) filter, which should serve for removing additive noise from images. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.obstruction, r.planning.static, r.planning.cinematic ====

: [http://www.ing.unitn.it/~grass/software.html r.obstruction, r.planning.static, r.planning.cinematic]: r.obstruction creates a polar obstruction map from a DTM. r.planning.static performs a static planning for GPS and Glonass surveys using the obstruction map created with r.obstruction. r.planning.cinematic performs a cinematic planning for GPS and Glonass surveys. (University of Trento, Faculty of Engineering)

: '''Author:''' Daniele Carli, Dimitri D'Inca', Gianluca Fruet, Domenico Sguerso, Paolo Zatelli

==== r.out.colorbar ====

: [http://tekmap.ns.ca/blog/colorbar_out r.out.colorbar] is an export program for saving GRASS raster colorbars to an image. The program uses GTK+ and cairographics. Supported export formats are PNG, PDF, and EPS.

: '''Author:''' Bob Covill

==== r.out.jpeg ====

: [http://www.geospatial.it/allegri/grass/r.out.jpeg_ r.out.jpeg] is a simple GRASS script to export georeferenced JPEG images from rasters, keeping the associated color table. It is a two-step export: first a ppm file is created, then it is converted to jpeg usgin the "convert" command from ImageMagick

: '''Author:''' Giovanni Allegri

==== r.out.geoserver ====

: [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 r.out.geoserver] exports GRASS raster layer to [http://geoserver.org GeoServer] and publishes it using WMS. The modul is a shell script. It uses: r.out.gdal, curl, xmlstarlet and GeoServer REST interface.

: '''Author:''' Pawel Netzel

==== r.out.gmap ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.out.gmap r.out.gmap] outputs GRASS raster map into set of image tiles
following the tiling scheme of Google Maps and Microsoft Virtual Earth. Read more in the OSGeo Journal [http://www.osgeo.org/journal Volume 5 (2009, to appear)] see also [[#r.out.kml|r.out.kml]] and [[#v.out.kml|v.out.kml]]

: '''Author:''' Tomas Cebecauer

==== r.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.out.gmt r.out.gmt] is a GRASS script for exporting a GRASS raster map into a [http://www.soest.hawaii.edu/gmt/ GMT] grid file. It also creates a GMT color table from the data and can generate some GMT commands for plotting a postscript file. (code is experimental, but functional) see also http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview

: '''Authors:''' Hamish Bowman, Dylan Beaudette

==== r.out.gmt2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.out.gmt2 r.out.gmt2] is a modified version of Hamish's r.out.gmt. Added options for title, xlabel, ylabel, comment, and map width. Removed any settings that can be changed by gmtset for more flexibility.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== r.out.kap_template ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.out.kap_template r.out.kap_template] is a shell script that exports a raster map into a GeoTiff and a metadata text file suitable for use with KAP (BSB) raster nautical chart converter programs such as <tt>tif2bsb</tt> (after verifying that you are legally entitled to use such a tool).
: '''''This is EXPERIMENTAL software. NOT FOR NAVIGATIONAL USE.'''''
: For an easy to use data viewer, see also the [http://www.opencpn.org OpenCPN] free navigational software.

: '''Author:''' Hamish Bowman

==== r.out.kml ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.out.kml r.out.kml] is a shell script that exports a raster map into a KML file and image for Google Earth or Worldwind. See also [[#v.out.kml|v.out.kml]] and [[#r.out.gmap|r.out.gmap]].

: '''Author:''' Hamish Bowman

==== r.out.maxent_swd ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.out.maxent_swd r.out.maxent_swd] is a shell script to produce a set of SWD files as input to MaxEnt 3.3.3e using r.stats. See also [[#r.maxent.lambdas]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.out.maxent_swd/

==== r.pack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.pack r.pack] and [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.unpack r.unpack] are two GRASS scripts for transferring raster maps to another computer as a single compressed file including color table etc.
: An earlier version has been renamed as [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.pack/experiment r.pack.mat] and [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.unpack/experiment r.unpack.mat].

: '''Author:''' Hamish Bowman

==== r.pi ====

: [https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.pi/ r.pi] (raster patch index) provides various functions to analyse spatial attributes of a landscape. It has a focus on patch-based indices but delivers class-based indices as well. r.le and its successor r.li provide landscape indices.

: '''Authors:''' Programming: Elshad Shirinov, Scientific concept: Dr. Martin Wegmann

==== r.prominence ====

: '''r.prominence''' calculates the average difference between a central cell and its neighbors. It approximated the terrain 'ruggedness' by looking at average differences in elevation within a given neighborhood.

: '''Author:''' Benjamin Ducke

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.prominence/

==== r.refine ====

: [http://www.bowdoin.edu/~ltoma/research.html r.refine]: reduces a DEM to a TIN (takes as input a grid DEM and an error margin and simplifies it to the desired accuracy into a TIN)
Available via the source code repository [https://github.com/jonrtodd/r.refine]
: '''Authors:''' Laura Toma and Jonathan Todd

==== r.rifs ====

: [http://www.ucl.ac.uk/~tcrnmar/ r.rifs]: r.rifs generates a raster map and/or image of a fractal by means of the specified random iterated function system.

: '''Author:''' Mark Lake

==== r.roughness ====

[http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.roughness/r.roughness.sh r.roughness.sh] is a shell script to calculate the surface roughness of a DEM, using r.surf.area and v.surf.rst. (for GRASS versions 6.1 and above)

[http://www.igc.usp.br/pessoais/guano/downloads/r.roughness60 r.roughness60] - for GRASS versions 6.0.X

[http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.roughness/r.roughness.window.area r.roughness.window.area] - calculate surface roughness as the ratio of real (surface) area and planar area, using a moving-window approach.

[http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.roughness/r.roughness.window.vector r.roughness.window.vector] - calculate surface roughness as vector dispersion, using a moving-window approach. Resulting maps are: Vector Strength (R) and Inverted Fisher's k parameter.

[http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.roughness/r.roughness.window.vector.html r.roughness.window.vector.html] - provisional help page for r.roughness.window.vector.

: '''Author:''' Carlos Henrique Grohmann

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.roughness/

==== r.roughset ====

: r.roughset is a module for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/mcda/r.roughset/

==== r.seg ====

: '''r.seg''' performs image segmentation and discontinuity detection (based on the Mumford-Shah variational model).
: The module generates a piece-wise smooth approximation of the input raster map and a raster map of the discontinuities of the output approximation. The discontinuities of the output approximation are preserved from being smoothed.
: See [http://www.ing.unitn.it/~vittia/sw here] for details and examples.

Available [http://www.ing.unitn.it/~vittia/sw here] and with improvements via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.seg/

: '''Author''' Alfonso Vitti

==== r.smoothpatch ====

: [http://david.p.finlayson.googlepages.com/r.smoothpatch r.smoothpatch] creates a composite of two rasters using a distance-weighted average across the transition to smooth the edges.

: '''Author:''' David Finlayson

==== r.soils.texture ====

: r.soils.texture is a module to define soils texture from sand and clay raster file with a schema text file (now FAO,USDA and ISSS are available). It is written in C language. - for GRASS versions 6.x - For bugs and suggest: g_massa@libero.it

:'''Author:''' Gianluca Massei

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.soils.texture/

====r.split.line====

: [https://raw.github.com/amuriy/GRASS-scripts/master/r.split.line r.split.line] is a shell script to split raster into parts with vector line(s).

:'''Author:''' Alexander Muriy

==== r.stack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stack r.stack] is a shell script used to patch all the raster maps in a time series (or burst 3D raster) together into a vertical stack, to aid multi-map analyses in modules where group input is not yet available.

: '''Author:''' Hamish Bowman

==== r.stream.angle ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.angle r.stream.angle] Divide stream network into stright line segments according users input. It extends Module uses as input direction and stream network map produced by r.watershed and stream.extract or custom user input. See description for details.

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.angle

==== r.stream.basins ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.basins r.stream.basins] delineate basins according users input. It extends r.water.outlet funcionality to extracting more than one basin at one step. Module uses as input direction map produced stream network produced by r.stream.extract, r.watershed, r.stream order or custom user input. More in tutorial on grass-wiki pages.

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.basins

==== r.stream.del ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.del r.stream.del] Calculates downslope length of first order streams and delete them if it length (in pixels) is lower than the treeshold. It also join false segments left by deletion into one with category of upper. It uses r.watershed direction map and r.watershed stream map as input. The module is added only for r.watershed module, r.stream.extract has deleting short streams build-in. During development of r.stream.* it will be probably abandoned due to duplicate functionality

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.del

==== r.stream.distance ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.distance r.stream.distance] Calculates downslope distance and downslope elevation difference between current cell and stream or outlet cells. It uses r.watershed direction map, r.watershed or r.stream.extract stream map and optionally DEM as input.

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.distance

==== r.stream.extract ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.extract r.stream.extract] extracts topologically clean stream networks from input elevation and optionally accumulation maps. Output is available as raster and vector and can be used as input for the other r.stream.* modules by Jarek Jasiewicz.

: '''Author:''' Markus Metz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.extract

==== r.stream.order ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.order r.stream.order] orders stream network outputed by r.watershed or r.stream.extract according Sthrahler, Shreve, Horton and Hack ordering systems. It require as input stream and direction map and optionally accumulation map. It handle both SFD nad MFD modes but all data must come from the same procedure.

: '''Author:''' Jarek Jasiewicz, Markus Metz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.order

==== r.stream.pos ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.pos r.stream.pos] Helper module for calculating local stream network properties and linear geostatistics. Mostly To use with R and other grass modules.

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.pos

==== r.stream.preview ====

: In order to find a value of upslope area to be used as input to extract the river network using r.stream.extract or r.watershed, it is common to proceed by tentatives. [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.preview r.stream.preview] is useful for quickly display results for various tentatives of threshold values.

: '''Author:''' Margherita Di Leo

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.preview/

==== r.stream.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.stream.stats r.stream.stats] calculate Hortonian statistics for Stahler or Horton stream network created by r.stream.order. It uses r.watershed direction map, DEM and r.stream.order's Stahler or Horton stream network as input. It outputs calculated statistics to standard output.

: '''Author:''' Jarek Jasiewicz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.stream.stats

==== r.surf.nnbathy ====

: [http://www.sieczka.org/programy_en.html r.surf.nnbathy] interpolates a surface from a raster input using Pavel Sakov's [http://code.google.com/p/nn-c/ nn] natural neighbor interpolation library. Provides triangulation, Sibson natural neighbor interpolation and non-Sibsonian interpolation.

: '''Author:''' Maciej Sieczka

==== r.surf.volcano ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.surf.volcano r.surf.volcano] creates an artificial surface resembling a seamount or cone volcano. The user can alter the size and shape of the mountain and optionally roughen its surface. Available decay functions are polynomial, Gaussian, Lorentzian, logarithmic, and exponential.

: '''Author:''' Hamish Bowman

==== r.terracost ====

[http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. '''Lead author''': Laura Toma

Available via SVN or {{cmd|g.extension}}:
svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.terracost

==== r.threshold ====

[http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.threshold/ r.threshold] Finds a first tentative value of upslope area to be used as input to extract the river network using r.stream.extract or r.watershed.

Available via SVN or {{cmd|g.extension}}:
svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.threshold

==== r.tileset ====

: ''{{cmd|r.tileset}} moved into main archive''

==== r.to.vect.lines ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.to.vect.lines r.to.vect.lines] is a module to sample raster rows at regular intervals and turn them into 3D lines. e.g. to display in [[NVIZ]] as a wiggle plot.
: It demonstrates the use of [[Python_Ctypes_Examples|ctypes]] to access the GRASS C libraries from within a Python script. (treat as a work in progress)

: '''Author:''' Hamish Bowman

==== r.traveltime ====

: [http://jesbergwetter.twoday.net/stories/4845555/ r.traveltime] computes the travel time of surface runoff to an outlet. The program starts at the basin outlet and calculates the travel time at each raster cell recursively. A drainage area related threhold considers even surface and also channel runoff. Travel times are derived by assuming kinematic wave approximation. The results can be used to derive a time-area function. This might be usefull for precipitation-runoff calculations (estimation of flood predictions) with a lumped hydrologic model (user-specified unit hydrograph).

: '''Author:''' Kristian Förster

==== r.univar.zonal ====

Note: This addon is only needed for GRASS 6.3, its functionality has been added to r.univar in 6.4+ and 7.

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.univar.zonal r.univar.zonal] is similar to {{cmd|r.univar}}, but calculates statistics separately for each category(zone) present in the separate input map used to define zones (zonal statistics). The output can be like the one of r.univar or in easier to read table format and can be written to a file.

: '''Author:''' Markus Metz

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.univar.zonal

==== r.viewshed ====

: r.viewshed is a module for extremely fast line of sight analysis (replaces the slow r.los). It is written in C language for GRASS versions 6.X/7.x.

: '''Author:''' Laura Toma, USA

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.viewshed

Once {{trac|390}} is solved, it will substitute r.los.

==== r.wavelets ====

: [http://www.ing.unitn.it/~grass/software.html r.wavelets]: This package contains wavelets decomposition and reconstruction modules for the GRASS GIS: r.owave.dec computes the orthogonal wavelet transform of a raster map. r.owave.rec reconstructs a raster map from an orthogonal wavelet transform. r.biowave.dec computes the biorthogonal wavelet transform of a raster map. r.biowave.rec reconstructs a raster map from a biorthogonal wavelet transform.

: '''Authors:''' Members of the University of Trento, Faculty of Engineering

==== r.wf ====

: [http://svn.osgeo.org/grass/grass-addons/grass6/raster/r.wf/ r.wf] produces the Width Function of a basin. The Width Function W(x) gives the number of the cells in a basin at a flow distance x from the outlet (it is also referred as distance-area function). The distance is not the euclidean one, but it is measured along the flowpath towards the outlet.

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.wf/

==== r.xtent ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.xtent r.xtent] computes a raster map layer representing the Voronoi diagram, weighted Voronoi diagram or a more complex territorial partitioning of space around points (centers) in a vector input map, based on the XTENT formula.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.xtent

==== r.zc.pl ====

: [http://les-ejk.cz/files/programs/zc.pl Zero crossing] is a simple Perl script, finds the ,,zero crossings`` from the Laplacian of Gaussian filter (see above). It is really very simple, the edges don't need to be really on that pixel, where they are detected, no interpolation is performed.

: '''Author:''' Jachym Cepicky

==== GIPE ====

: The GRASS Image Processing Environment (GIPE) has USLE, Energy-balance and radiance-reflectance correction models.

: '''Author:''' Yann Chemin (unless specified otherwise).

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/gipe

Remark: This is progressively moved to main GRASS SVN (aka GRASS 7)

:* r.hydro.CASC2D, ported from GRASS 5.x version, is temporarily here waiting to return to main GRASS.

:* r.soiltex2prop creates porosity, Saturated Hydraulic conductivity (Ksat) and wetting front pressure head (Hf) from percentage of sand and clay after Rawls et al., 1990. This is a must for r.hydro.CASC2D.

:* i.biomass creates biomass growth map from fPAR, lightuse efficiency, water availability (or evap.fraction), Lat, doy and tsw.

:* i.dn2ref.l7, r.dn2ref.ast create top of atmosphere reflectance for Landsat 7ETM+ and ASTER. These modules also have a flag for radiance output. Updated i.dn2ref.l7 to read .met calibration file.

:* i.dn2full.l[5,7] is an attempt to get all bands of Landsat[5,7] calibrated and corrected to either reflectance or temperature, reads only the .met file.

:* i.dn2potrad.l[5,7] is an attempt to get ET potential from DN of Landsat 7 (Careful! No Atmospheric correction!).

:* i.eb.* are a set of 10+ GRASS modules that together perform the main functions of the SEBAL model (Bastiaanssen, 1995). Those functions include (but are not limited to) Soil heat flux, sensible heat flux, net radiation, evaporative fraction at satellite overpass, diurnal actual evapotranspiration, momentum roughness length, etc. These modules are also part of any Energy-Balance related processing.

:* i.evapo.potrad creates diurnal Potential evapotranspiration assuming all net radiation becomes ET, according to SEBAL model (Bastiaanssen, 1995). This module also has a flag for diurnal net radiation as required by SEBAL in i.eb.eta.

:* i.evapo.SENAY creates actual evapotranspiration following the regional method of Senay (2007).

:* i.lmf creates a Local Maximum Fitting on the temporal dimension of the multi-date input dataset, working, but more precision still to be added.

:* i.vi.mpi is the mpi version of i.vi for cluster GRASS GIS education (no speed up here!) '''Author:''' Shamim Akhter

:* i.modis.stateqa extracts State Quality Assessment information from Modis 500m (MOD09A) products.

:* i.water creates a Water Mask from NDVI and Albedo, or specifically for Modis: NDVI and Band 7.

:* i.wi creates a given Water Index (only one so far).

==== HydroFOSS ====

: HydroFOSS - a GIS embedded approach for Free & Open Source Hydrological modeling.

: '''Author:''' Massimiliano Cannata

svn co https://svn.osgeo.org/grass/grass-addons/HydroFOSS/

==== Hikereport ====

: python script that computes length, cumulative uphill and downhill, average slopes on an interactively drawn path. Based on r.profile's output.

: '''Author:''' Stefano Negri

http://tracce.wordpress.com/?attachment_id=71

=== Misc add-ons===

==== m.eigensystem ====

m.eigensystem - Computes eigen values and eigen vectors for square matrices.

: http://svn.osgeo.org/grass/grass-addons/grass6/misc/m.eigensystem/

: '''Author:''' Michael Shapiro

===Database add-ons===
==== db.join ====

: Table joining: join one table into another through common attributes

: '''Author:''' Markus Neteler. Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/database/db.join/
or
g.extension db.join

===General add-ons===

==== Compare GRASS maps ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass7/general/g.compare.md5 g.compare.md5] Script to check if two GRASS maps are identical

: '''Author:''' Luca Delucchi

==== GRASS create location scripts ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/general/grass_create_location grass_create_location.sh] Script to generate a new GRASS location from GIS file (e.g. geoTIFF or SHAPE), wktfile or EPSG code.

: '''Author:''' Markus Neteler

==== g.laptop.sh ====

: [http://www.gbd-consult.de/dassau/grass/g.laptop/g.laptop.sh g.laptop.sh] is an interactive shell script to extract raster and vector data from current Location into a new one. Data can be copied or extracted in current or original resolution and region extend. This script was written to extract smaller parts of a GRASS location to be able to present them on a laptop without the necessity to transfer huge data. Maps do not have to be in the same mapset.

: '''Author:''' Otto Dassau

==== Readline completion ====

: '''''Readline completion''''' for GRASS commands under the bash shell: [http://www.sorokine.info/grass-complete/ grass-complete] won't clutter the environment but needs to be installed; [http://dcalvelo.free.fr/grass/grass_rlcompleter.sh grass_rlcompleter.sh] needs almost no installation but will pollute the environment. Grass-Complete currently requires Bash version 2.05 for proper install.

: '''Author:''' Alexandre Sorokine (grass-complete), Daniel Calvelo (grass_rlcompleter.sh)

==== g.region.point ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/general/g.region.point g.region.point] is a shell script which resets the computational region to a square box around a given coordinate. It is intended for use within GRASS scripts to speed up processing by limiting expensive raster calculations to a small area of interest.

: '''Author:''' Hamish Bowman

==== g.linke_by_day ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.sun.tools/ g.linke_by_day] is a python script for [[r.sun]] which interpolates a Linke turbidity value for a given day of the year based on monthly values edited into the script.

: '''Author:''' Hamish Bowman

==== g.xlist ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/general/g.xlist g.xlist] is a C implementation of g.mlist. g.xlist searches for data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

==== g.xremove ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/general/g.xremove g.xremove] is a C implementation of g.mremove. g.xremove removes data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

==== g.region.ll ====

: [https://bitbucket.org/afrigeri/grass-addons g.region.ll] sets the region in a projected location using longitudes and latitudes.

: '''Author:''' Alessandro Frigeri

=== Imagery add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery

==== GIPE ====

GIPE (see also above in raster section) provides:
i.biomass, i.dn2potrad.l5, i.dn2potrad.l7, i.dn2ref.ast, i.eb.deltat, i.eb.disp, i.eb.eta, i.eb.evapfr, i.eb.g0, i.eb.h0, i.eb.h_SEBAL01, i.eb.h_SEBAL95, i.eb.h_iter, i.eb.molength, i.eb.netrad, i.eb.psi, i.eb.rah, i.eb.rohair, i.eb.ublend, i.eb.ustar, i.eb.wetdrypix, i.eb.z0m, i.eb.z0m0, i.evapo.PT, i.evapo.TSA, i.evapo.potrad, i.evapo.senay, i.evapo.time_integration, i.lmf, i.modis.stateqa, i.sattime, i.vi.grid, i.vi.mpi, i.water, i.wi

svn co https://svn.osgeo.org/grass/grass-addons/gipe/

: '''Author:''' Yann Chemin

==== i.despeckle ====

Applies SAR Speckle Filter to a raster power map. Currently LEE, KUAN, Enhanced Lee and GAMMA filter are implemented.

g.extension i.despeckle

==== i.histo.match ====

Performs histogram matching on the given input images.

svn co https://svn.osgeo.org/grass/grass-addons/grass7/imagery/i.histo.match

: '''Authors:''' Laura Zampa (PERL version), rewritten and updated by Luca Delucchi, Italy

==== i.homography ====

Rectifies an image by computing a coordinate transformation for each pixel in the image based on the control points created by i.linespoints. The approach uses homography extended for corresponding lines.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.homography

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on code written by Stefano Merler, ITC-irst, Italy

==== i.linespoints ====

An imagery command that enables the user to mark coordinate system points as well as lines on an image to be rectified and then input the coordinates of each point for creation of a coordinate transformation matrix. The transformation matrix is needed as input for the GRASS program i.homography.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.linespoints

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on i.points

==== i.landsat.dehaze ====

Bandwise haze correction using tasscap4 (haze) and linear regression of a Landsat scene.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.landsat.dehaze

: '''Author:''' Markus Neteler

==== i.landsat.toar ====

Transform calibrated digital number of Landsat products to top-of-atmosphere radiance or top-of-atmosphere reflectance and temperature (band 6 of the sensors TM and ETM+). Optionally, used to calculate the at-surface radiance or reflectance with atmospheric correction (DOS method).

Available also in GRASS 7 and GRASS 6.5.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.landsat.toar

: '''Author:''' E. Jorge Tizado

==== i.landsat.acca ====

Implements the Automated Cloud-Cover Assessment (ACCA) Algorithm from Irish (2000) with the constant values for pass filter one from Irish et al. (2006). To do this, it needs Landsat band numbers 2, 3, 4, 5, and 6 (or band 61 for Landsat-7 ETM+) which have already been processed from DN into reflectance and band-6 temperature with i.landsat.toar).

Available also in GRASS 7.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.landsat.acca

: '''Author:''' E. Jorge Tizado

==== i.points.auto ====

This module allows a search of GCP's on two raster-maps with differents levels of automation. The ''manual'' search is the default search, so it's possible to determine the GCP's manually with the mouse (like {{cmd|i.points}}). ''Semiautomated'' search: The user determines with the mouse some correspondent areas (with a discrete precision) in the two maps and the module searches itself the GCP's in these areas. ''Automated'' search: At the start of module the user has to load the maps that the algorithm uses to the search, so it is recommended to use the maps filtered with the filters DIVERSITY or STDDEV (of GRASS) with a window of 3x3 or 5x5 pixels. However, the algorithm sometimes works well with the original maps too.

Note: This code is basically an improved i.points (from 2004). Subsequent changes in i.points haven's been ported here yet.

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.points.auto

: '''Authors:''' based on i.points; additions by Ivan Michelazzi, Luca Miori (MSc theses at ITC-irst); Supervisors: Markus Neteler, Stefano Merler, ITC-irst 2003, 2004. [http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=37 PDF article]

==== i.points.reproj ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/imagery/i.points.reproj i.points.reproj] is a shell script that will use cs2cs to reproject the target coordinates of a group's POINTS file. By running i.rectify directly to the new target projection, a generation of resampling data loss can be avoided (versus i.rectify + r.proj). On the other hand, i.rectify does not calculate cell resolution well if the map is to be rotated ([http://intevation.de/rt/webrt?serial_num=3296 bug #3296]), in those cases i.rectify+r.proj may be the better option.

: '''Author:''' Hamish Bowman

==== i.plr.py ====

: [[I.plr.py|Probabilistic Label Relaxation]], written in Python

: '''Author:''' Georg Kaspar

==== i.pr ====

: Image classification: implements k-NN (multiclass), classification trees (multiclass), maximum likelihood (multiclass), Support Vector Machines (binary), bagging versions of all the base classifiers, AdaBoost for binary trees and support vector machines. It allows feature manipulation (normalization, principal components,...). It also implements feature selection techniques (RFE, E-RFE,...), statistical tests on variables, tools for resampling (cross-validation and bootstrap) and cost-sensitive techniques for trees and support vector machines.

: '''Author:''' Stefano Merler. Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.pr

==== i.spec.sam ====

: Spectral Angle mapping

: '''Author:''' Markus Neteler. Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.spec.sam/

==== i.spec.unmix ====

: Spectral unmixing

: '''Author:''' Markus Neteler. Available via SVN or {{cmd|g.extension}}:

svn co https://svn.osgeo.org/grass/grass-addons/grass6/imagery/i.spec.unmix/

==== i.topo.corr ====
: i.topo.corr is used to topographically correct reflectance from imagery files, e.g. obtained with i.landsat.toar (see above), using a sun illumination terrain model. This illumination model represents the cosine of the incident angle, i.e. the angle between the normal to the ground and the sun rays. It can be obtained with {{cmd|r.sun}} (parameter incidout), and then calculating its cosine with float precision. Correction methods: cosine, minnaert, percent, c-factor.

--> the module has been included in main GRASS (GRASS 6.4 and later)

: '''Author:''' E. Jorge Tizado

==== i.warp ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/imagery/i.warp i.warp] is a shell script that will use gdalwarp to rectify a raw input image using thin plate splines. The map should be imported into GRASS with r.in.gdal and GCPs set with i.points. Input is the raw image (GeoTIFF, JPEG, etc). Output is a GeoTIFF in the imagery group's target location's map projection. Requires a recent (early 2006) version of GRASS 6.1, or newer.

: '''Author:''' Hamish Bowman

=== Display add-ons ===

See also

svn co http://svn.osgeo.org/grass/grass-addons/grass6/display

==== d.barb ====

[http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.barb d.barb] is a C module that will draw wind barbs, straw plots, and arrow plots from raster array or sparse vector point data. It can use either direction + magnitude, or u + v components as the input, and can produce a legend key. (''work in progress, but it's mostly there'')

: '''Author:''' Hamish Bowman

==== d.edit.rast ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.edit.rast d.edit.rast] edits cells in an existing raster map displayed on the current monitor.

: '''Author:''' Huidae Cho

==== d.frame.quarter ====

: ('''obsolete''') [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.frame.split d.frame.quarter] is a shell script that will split the display into four quadrants (or sixths) using ''d.frame''. Individual frames are named ''uno, dos, tres, cuatro'', and ''full_screen''.
: Replaced by {{cmd|d.split.frame}} in main.

: '''Author:''' Hamish Bowman

==== d.frame.split ====

: ''d.frame.split moved into main archive as {{cmd|d.split.frame}}''

==== d.frontline ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.frontline d.frontline] is a shell script that draws frontlines on the graphics monitor using ''d.graph'' module and different types of symbols. Also it optionally saves frontline graphics to ''d.graph'' commands file and/or ''ps.map'' file (for later use with the "read" ''ps.map'' instruction)

: '''Author:''' Alexander Muriy

==== d.hyperlink ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/d.hyperlink.tar.bz2 d.hyperlink] is an interactive shell script that allows the viewing of hyperlinked images from a vector's attribute table in an external image viewer. Queries can be made via SQL statements or interactive mouse-clicking. The attribute table must be pre-populated with a column containing the image to link the vector to; the user also specifies the image folder in the current MAPSET where the images are located. The script currently supports gimp, Eye of Gnome, gthumb, gpdf, and Inkscape image viewers.

: '''Author: '''Eric Patton

==== d.mark ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.shortcuts d.mark] is a shell script that quickly displays a marker on the display at a given coordinate.

: '''Author:''' Hamish Bowman

==== d.region.box ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.region.box d.region.box] is a shell script that quickly displays a box around the current region.

: '''Author:''' Hamish Bowman

==== d.stations ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.shortcuts d.stations] is a shell script that quickly displays vector points (or sites for GRASS 5.4 and below).

: '''Author:''' Hamish Bowman

==== d.varea ====

: [http://trac.osgeo.org/grass/browser/grass-addons/grass6/display/d.shortcuts d.varea] is a shell script that quickly displays vector areas.

: '''Author:''' Hamish Bowman

==== d.zoom.keys ====

[https://raw.github.com/amuriy/GRASS-scripts/master/d.zoom.keys d.zoom.keys] is a shell (+awk) script that allows to change the current geographic region settings interactively, with a keyboard. Can use navigation in X-monitor (requires <xev> and <xdotool>) or terminal.

NOTE: tested normally only on Linux (Ubuntu 10.04), on other systems <awk> and other tools may behave differently.

: '''Author:''' Alexander Muriy

Also available via SVN or {{cmd|g.extension}}:

https://svn.osgeo.org/grass/grass-addons/grass6/display/d.zoom.keys/

==== pd-GRASS ====

: [http://www.ornl.gov/sci/gist/software/grass/ pd-GRASS]: Parallel Display for GRASS GIS

: '''Author:''' Alex Sorokine

==== [[IconSymbols]] ====

* [[IconSymbols|Symbols]] which can be used with ''d.vect, d.graph'', and ''ps.map''.

==== p.in.labels ====

: [http://tekmap.ns.ca/blog/import_label p.in.labels] is a program to import ASCII xyz (where z is a label) files as GRASS labels. Reads from stdin or existing file.

: '''Author:''' Bob Covill

=== Postscript add-ons ===

* ''See also [[ps.map scripts|ps.map samples and templates]]''.

==== ps.atlas ====

: [http://les-ejk.cz/programs/grass/ps.atlas ps.atlas] is a shell script that makes more maps on current region according to input *.psmap file. General map can be stored as vector file. The resulting *.eps maps can be automatically converted to *.pdf files.

: '''Author:''' Jachym Cepicky

==== ps.output ====

: [https://trac.osgeo.org/grass/browser/grass-addons/grass6/postscript/ps.output ps.output] is much like {{cmd|ps.map}} but with advanced decorations and ability for translucency. Here you can find a [[Ps.output|tutorial]].

: '''Author:''' Jorge Tizado

==== [[AreaFillPatterns]] ====

* Hatches for ps.map's vareas

=== wxGUI add-ons ===

===GRASS and UMN Mapserver===

* [http://www.mail-archive.com/mapserver-users@lists.umn.edu/msg00086.html See interesting posting]
* See wiki [[GRASS and MapServer]] page

==GRASS 7.x (in development)==

* See [[AddOns/GRASS7]]

==GRASS 5.x (old)==

See also
http://grass.osgeo.org/outgoing/

svn co https://svn.osgeo.org/grass/grass-addons/grass5/

=== Sites addons ===

* [http://www.tigers.ru/grass_docs/progs/DESCRIPTION.html Parallelized s.surf.idw] using MPI. ([http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fwww.tigers.ru%2Fgrass_docs%2Fprogs%2FDESCRIPTION.html&lp=ru_en&btnTrUrl=Translate babelfish translation])
: '''Author''': Alexei Popov, Russia.

=== Raster addons ===

* [http://www.valledemexico.ambitiouslemon.com/gwmodelling.html r.gmtg] The groundwater modelling tool for grass. A module to use MODFLOW within GRASS. '''Author''': Jaime Carrera

* [http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. For GRASS 5.3. '''Lead author''': Laura Toma
: Newer version available via SVN or {{cmd|g.extension}}:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==GRASS 4.x (very old)==

===Raster add-ons===

* MAGICAL Software: The MAGICAL software comprises a suite of three programs that provide a multi-agent simulation extension for the GRASS GIS software. http://www.ucl.ac.uk/~tcrnmar/simulation/magical/magical.html

[[Category:Community]]
[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

AddOns

2011-08-17T13:10:38Z

⚠️Sbl: script r.out.maxent_swd added

This page contains references to user contributions and add-ons (the original GRASS GIS software can be downloaded [http://grass.osgeo.org/download/ here]).

__TOC__

== AddOns source code repository ==

The AddOns source code is hosted in [http://svn.osgeo.org/grass/grass-addons/ GRASS-AddOns SVN repository].

To checkout:

svn checkout <nowiki>https://svn.osgeo.org/grass/grass-addons/</nowiki> grass-addons

Please read [http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository How to get write access to the GRASS-Addons-SVN repository] and contact the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list if you would like to host your module there.

== Building and installing Addons ==

See the [[Compile and Install#Addons|compile and install]] wiki page.

In GRASS 6.4 and newer you can use the {{cmd|g.extension}} module, e.g. to install <tt>r.fuzzy.system</tt> run:

g.extension extension=r.fuzzy.system

To remove installed Addons run

g.extension extension=r.fuzzy.system operation=remove

== Adding something new ==

Please announce your add-on to the GRASS users' mailing list so that others may be aware of your work. Also please consider adding your module to one of the [[Applications]] pages.

=== Copyright and licensing information ===

''Please be sure to include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.''

e.g. at the top of a shell script:
<pre>
#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################
#
# REQUIREMENTS:
# - avcimport: http://avce00.maptools.org

[script follows]
</pre>

=== Coding standards ===

Please have a look at our [http://grass.osgeo.org/grass63/source/SUBMITTING_SCRIPTS Shell script coding standards] before submitting here.

There are other coding standards given for modules written in C, Tcl/Tk, and Python''(?)'' located in the GRASS source code.

=== Documenting your code ===

You can have an help page template auto-generated by using the GRASS [[module command line parser | command line parser]] with the <tt>--html-description</tt> command line option. Please, see also the [http://grass.ibiblio.org/grass63/manuals/html63_user/g.parser.html g.parser help page]

== Miscellaneous Add-ons ==

* [http://trac.osgeo.org/grass/browser/grass-addons/misc/utm_which_zone utm_which_zone.sh] is a shell script to determine UTM zone from Lat/Lon input. Requires [http://www.octave.org Octave] or Matlab to be installed. A shell-only version is [http://dcalvelo.free.fr/grass/utm_which_zone_sh.sh available] which only requires awk. '''Authors''': Hamish Bowman (Octave part), Markus Neteler (shell script wrapper), Daniel Calvelo (sh+awk version)

* Perl scripts for converting data forth and back between Excel files and PostgreSQL: [http://dcalvelo.free.fr/grass/pg2xls.pl pg2xls.pl] reads data from PostgreSQL and produces an excel workbook; [http://dcalvelo.free.fr/grass/xls2sql.pl xls2sql.pl] reads excel files and outputs SQL statements to be fed into an RDBMS. Both scripts need modules from [http://www.cpan.org CPAN], especially [http://search.cpan.org/dist/Spreadsheet-ParseExcel/ Spreadsheet::ParseExcel] for xls2sql.pl and [http://search.cpan.org/~tmtm/Spreadsheet-WriteExcel-FromDB Spreadsheet::WriteExcel::FromDB] and its dependencies for pg2sql.pl. Check the source headers for more info. '''Authors:''' Daniel Calvelo (xls2sql.pl), Markus Neteler (pg2xls.pl)

* [http://dream.lrrl.arch.tu-muenchen.de/~wqual/perl/dbf2sql.tgz dbf2sql] is a Perl script for translating dbf-tables into a sql-command. dbf-tables are read using dbfdump-command from dbd-xbase-perl module ([http://search.cpan.org/~janpaz/DBD-XBase-0.241/ dbd::xbase] and [http://search.cpan.org/~jv/Getopt-Long-2.35/lib/Getopt/Long.pm getopt::long] have to be installed from CPAN first). There are problems, if the last column of the table contains characters. Suggestions for improvements welcome! '''Author:'''Wolfgang Qual

* [http://www.igc.usp.br/pessoais/guano/downloads/azimuth2.c azimuth2.c] is a small C program to calculate the azimuth and length of vector lines exported by GRASS-GIS as ASCII files (like this: v.out.ascii input=vector output=ascii format=standard). It is useful for create rose diagrams of lineament maps. Improvements on the original code after suggestions by Örs Téglásy, Hungary. '''Author:''' Carlos Henrique Grohmann

* [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 ann.*] is the set of GRASS modules (in python) which implements artificial neural network using FANN library. The package requires Fast Artificial Neural Network Library ([http://leenissen.dk/fann/wp/ FANN]) v2.x. '''Author:''' Pawel Netzel

==GRASS 6.x (current)==

=== Vector add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/vector

==== v.adehabitat.clusthr, v.adehabitat.kernelUD, v.adehabitat.mcp ====

: Tools to calculate home ranges of animals
: '''Author:''' Clement Calenge

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/vector/adehabitat

==== v.append ====

: [http://web.archive.org/web/20060914172621/http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.append v.append] is a shell script combining two vector files AND their associated attribute tables. The vector files should be of the same type and, for best results, should have identically formatted attribute tables.
: ''Note'': also module ''v.patch'' can be used for this task.

: '''Author:''' Michael Barton

==== v.autokrige ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.autokrige/v.autokrige.py v.autokrige] achieves automatic ordinary kriging from GRASS sites (vector point data), using R with spgrass6 (RGRASS) and automap packages.

: '''Author:''' Mathieu Grelier

==== v.breach ====

: [http://www.sieczka.org/programy_en.html v.breach] creates vector maps of lines and points of continously lowering elevation down the input watercourses, based on the input raster DEM.

: '''Author:''' Maciej Sieczka

==== v.colors ====

: {{cmd|v.colors}} ''moved into main archive''

==== v.count.points.sh ====

: [http://wiki.iosa.it/dokuwiki/spatial_analysis:feature_count v.count.points.sh] counts point features in areas, generates table good as input to d.vect.chart.

: '''Author:''' Stefano Costa

==== v.digatt ====

: [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt v.digatt] (shell script) Interactively assign numeric table attributes to series of vector objects. It is meant to be effective by avoiding to type in the attribute value for all single objects again and again. The user is prompted for typing in an attribute value which is assigned to all objects selected by mouseclick afterwards. Next the display is redrawn after updating the table column. Zooming allows to change the region before the old value can be reused or a new one can be typed in (or copied by mouse from another object) in order to assign it to the next series of objects etc. It is tested not very extensively yet. Therefore better work with a copy of your map and consider using v.digit or d.what.vect -e alternatively. [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt.png screenshot].

: '''Author:''' Andreas Philipp

==== v.dip ====

: [http://marcin.slodkowski.googlepages.com/v.dip.tgz v.dip] creates points of thickness vectors from the vectors of strike and dip angles. The v.dip is the main ANSI C core program. Program so-called v.dip can run without GRASS environment.

: '''Author:''' Marcin Slodkowski

==== v.flip ====

: [http://www.sieczka.org/programy_en.html v.flip] flips the direction of selected vector lines (redundant since GRASS 6.3 - there is "v.edit tool=flip").

: '''Author:''' Maciej Sieczka

==== v.group ====

: [http://www.shockfamily.net/cedric/grass/v.group v.group] generates a new vector map with the same geometry as an existing map. The new map has categories and a table based on grouping by the values in certain columns of the existing map's table. The values in these columns are preserved in the table for the new map. It's like a v.reclass that preserves data.

: '''Author:''' Cedric Shock

==== v.in.redwg ====

: v.in.redwg imports DWG files into GRASS.

:'''Author:''' Rodrigo Rodrigues da Silva

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.redwg

==== v.in.gama ====

: Converts [http://www.gnu.org/software/gama/ GNU GaMa] XML output file to a GRASS vector map layer.

:'''Author:''' Martin Landa

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.gama

==== v.in.geodesic ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.geodesic v.in.geodesic] is a shell script which will create a new vector map containing a great circle line. The user may either define a beginning and end coordinate, or define a starting coordinate along with initial azimuth and desired line length.

: '''Author:''' Hamish Bowman

==== v.in.geoplot ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.geoplot v.in.geoplot] converts a [http://www.geoscan-research.co.uk/page9.html/ Geoplot] ASCII export file to a GRASS vector map layer.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.geoplot

==== v.in.gshhs ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.gshhs v.in.gshhs] imports [http://www.soest.hawaii.edu/pwessel/gshhs/index.html GSHHS] shorelines into a GRASS vector map. GSHHS data are automatically reprojected to the current location.

:'''Authors:''' several, updated to GRASS 6 by Markus Metz

==== v.in.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.marxan v.in.marxan] is a python script that imports Marxan output data for display in a vector grid file prepared using v.out.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.in.mbsys_fnv ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.mbsys_fnv v.in.mbsys_fnv] imports [[MB-System]] navigation files into a GRASS vector map. You can choose from swath area coverage, track lines (including outer port/starboard edges), all bounds as points, etc. An attribute database is created containing the vital statistics of the specified feature such as track length or swath coverage (geodesic), start stop time and location, pitch, roll, heave, etc. See also the [[#v.in.p190]] addon.

:'''Author:''' Hamish Bowman

==== v.in.ncdc ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.ncdc v.in.ncdc] imports an [http://www.ncdc.noaa.gov NCDC] stn file (station data) into a GRASS vector map.

: '''Author:''' Huidae Cho

==== v.in.postgis ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.postgis/v.in.postgis.py v.in.postgis] Create a GRASS layer from any sql query on PostGIS data.

: '''Author:''' Mathieu Grelier

==== v.in.osm ====

: [http://kripton.kripserver.net/software/v.in.osm/ v.in.osm]: OpenStreetMap import into GRASS. Yet only supports deprecated API 0.4, will be modified to work with API 0.5 some time soon.

: '''Author:''' Jannis Achstetter

: See also [http://hamish.bowman.googlepages.com/gpsdrivefiles#osm osm2grass.sh] by H Bowman

==== v.in.osm2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.osm2 v.in.osm2]: OpenStreetMap import into GRASS. Supports current API 0.6, downloads using the [http://wiki.openstreetmap.org/wiki/Xapi Xapi] interface and imports using GpsBabel 1.3.5 or newer. GpsBabel restricts to either nodes or ways being imported at a time, not both. Use {{cmd|v.patch}} to rejoin them. (''work in progress'')

: '''Author:''' Hamish Bowman

==== v.in.ovl ====

: [http://grasslab.gisix.com/scripts/v.in.ovl/ v.in.ovl] is a shell script that imports an ASCII vector file created with TOP10|25|50 or similar products.

: '''Author:''' Peter Löwe

==== v.in.p190 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.p190 v.in.p190] is a shell script that imports 'Centre of Source' "S" navigation data from seismic P1/90 (UKOOA) data files and writes it either GRASS vector points or vector lines format. Optionally it will export the navigation data into .csv text files as well. ''Currently in the functional prototype stage, some assembly is required. See inside the shell script for details.'' For working with SEG-Y data, see also the [[#v.in.mbsys_fnv]] addon.

: '''Author:''' Hamish Bowman

==== v.krige ====

: [[V.krige_GSoC_2009 | v.krige]] aims to integrate R functions for kriging (packages automap, gstat, geoR) in a trasparent way. '''Moved into trunk/devbr6 code (r40048)'''

: '''Author:''' Anne Ghisla, as Google Summer of Code 2009 project

: See also [[GRASS_AddOns#v.autokrige]] by Mathieu Grelier

==== Spatial Analysis Tools ====

===== v.lda.py =====

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.lda.py v.lda.py] is a Python script for calculating Ian Johnson's (U. Sidney) Local Density Analysis values. This can be used in two ways. When only one vector points file is entered, it serves to measure clustering of point data at different neighborhood radii. When two different point files are entered, it measures the the co-occurence of the points from the two files. There is an option to export the data into a cvs format file for easy plotting in a spreadsheet or statistical program like R.

===== v.nn.py =====
: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.nn.py v.nn.py] is a Python script for calculating the nearest neighbor coefficient of a single vector points file--as an index of clustering--or of two points files--to provide an index of the correspondence between the points in one file and points in a different file.

==== v.line.center ====

: [http://www.sieczka.org/programy_en.html v.line.center] creates a points vector map with each point located in the middle of the length of the input vector line.

: '''Author:''' Maciej Sieczka

==== v.lmeasure ====

: [http://web.archive.org/web/20060827192321/http://ngeo.de/grassstuff/v.lmeasure v.lmeasure] and [http://web.archive.org/web/20060827060303/http://ngeo.de/grassstuff/v.revlmeasure v.revlmeasure] are two perl scripts that place equidistant vector points along a given arbitrary vector line starting from the beginning or end of the vector line, respectively. Resulting vector points are labeled with the distance from origin.

: '''Author:''' Mats Schuh

==== v.mkhexgrid ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.mkhexgrid v.mkhexgrid] is a python script that creates a hexagonal grid the size of the selected region using user specified side lengths.

: '''Author:''' Trevor Wiens

==== v.out.ascii.db ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.db v.out.ascii.db] is a shell script for exporting vector point data coordinates and selected attribute columns to either a file or to the console.
: ''Superseded in GRASS 6.4 by the new v.out.ascii columns= option.''

: '''Author:''' Hamish Bowman

==== v.out.ascii.mat ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.mat v.out.ascii.mat] is a shell script for exporting vector polygon and polyline data into an ASCII text file suitable for loading into Matlab (or [http://www.gnu.org/software/octave/ Octave]).

: '''Author:''' Hamish Bowman

==== v.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.gmt v.out.gmt] is a shell script that exports a polygon vector file into GMT xy file. psbasemap code was copied from Hamish's r.out.gmt.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== v.out.kml ====

: [http://grasslab.gisix.com/scripts/v.out.kml/ v.out.kml] is a shell script that exports a vector file into a KML file for Google Earth or Worldwind. see also [[#r.out.kml|r.out.kml]] and [[#r.out.gmap|r.out.gmap]]

: '''Author:''' Peter Löwe

==== v.out.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.marxan v.out.marxan] is a python script that prepares vector layers and exports GRASS vector attributes and adjacency information as Marxan input files. Output from Marxan simulations can be imported using v.in.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.out.svg ====

: [http://svg.cc/grass/index.html v.out.svg] is a module that exports SVG notation along with optional attribute data directly from GRASS 6.x vector layers. Now part of [http://svn.osgeo.org/grass/grass/trunk/vector/v.out.svg/ grass6-svn].

: '''Author:''' Klaus Förster

==== v.points.cog ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.points.cog v.points.cog] is a shell script which will create a new point at the center of gravity of each cluster of input points or centroids, grouped by attribute. Among other things this is useful for labeling swarms of points.

: '''Author:''' Hamish Bowman

==== v.profile ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.profile v.profile] is vector map profiling tool similar to r.profile. This module will print out distance and attributes to points/lines along profiling line. It's also usefull to determine places where raster profile crosses vector features (i.e. where to place river marker on river walley crossection).

: '''Author:''' Maris Nartiss

==== v.random.cover ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.random.cover v.random.cover] is a shell script for creating random points constrained within an irregularly shaped vector area. (v.random places points only in current region rectangle). Optionally the user can upload raster values at the points. See also '<tt>r.random cover= vector_output=</tt>'

: '''Author:''' Hamish Bowman

==== v.rasterbounds ====

: [http://les-ejk.cz/programs v.rasterbounds] is a shell script for creating polygon-vector file of rasterfile boundaries. The best version of GRASS is 6.1+. If you are using GRASS < 6.1, you have to be in the same mapset as your raster maps are from.

: '''Author:''' Jachym Cepicky

==== v.rast.stats2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.rast.stats2 v.rast.stats2] is an adapted version of the GRASS module v.rast.stats. It uses the grass addon [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar.zonal r.univar.zonal] to speed up calculation of univariate statistics from a GRASS raster map based on vector polygons.

: '''Authors:''' Markus Neteler, Otto Dassau

==== v.sample.buffer [Currently unavailable. Being re-written in python. Target for inclusion in addons svn is January 2011]====
v.sample.buffer is a shell script that samples rasters in buffers of a specified size around features in a specified vector file. Sampling results are added as attributes to the vector file. This script was designed for sampling vegetation indices and DEM derived attributes for bird point counts. Sampling results can be one or more basic statistics such as mean, range, max, etc.

: '''Author:''' Trevor Wiens

==== v.select.region ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/v.select.region.tar.bz2 v.select.region] is a shell script that prints out the names of all vectors matching an input search pattern that has geometry (points, line, areas) that fall within a region bounded by an existing vector map, or within the current Grass region.

: '''Author:''' Eric Patton

==== v.selmany ====

: [http://svn.osgeo.org/grass/grass-addons/vector/v.selmany/v.selmany v.selmany] is a shell script that allows to interactively select a set of vector objects on a given layer, then assign them attribute values in a connected database table. The script runs on the command line prompt and within a graphic monitor ; it does not work with DBF driver.

: '''Author:''' Vincent Bain

==== v.surf.icw ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.surf.icw v.surf.icw] is an IDW interpolation method using true distance cost instead of euclidean shortest distance, i.e. ''as the fish swims around an island'' not ''as the bird flies''. This will cleanly travel around hard barriers and a cost surface map may be used to model expensive-cross barriers. Input data points do not need direct line of sight to be considered, but should be kept to less than one hundred as the module becomes very computationally expensive. A number of radial basis function options are available. ([http://grass.osgeo.org/wiki/Image:Inlets_03_SurfSal_icw_big.png screenshot])

: '''Author:''' Hamish Bowman

==== v.surf.idwpow ====

: [http://www.geospatial.it/allegri/grass/v.surf.idwpow.zip v.surf.idwpow] integrates the common v.surf.idw algorithm with the exponential parameter for the distance weights

: '''Author:''' Giovanni Allegri

==== v.surf.krige [deprecated: use v.autokrige instead] ====

: v.surf.krige is a script that do a surface interpolation from vector point data by Kriging method. The interpolated value of a cell is determined by using an omnidirectional variogram model fitted starting from model parameter given by user shown from the experimental semi variogram produced by v.variogram. The script can perform also the Leave-One-out cross validation to test the variogram model "fitted by eye" and an automatic fitted variogram model. The cross validation helps the user to choose the best variogram model to interpolate own data.

: '''Author:''' Pierluigi De Rosa.

==== v.strahler ====

: [http://www.pois.org/florian/downloads/grass/v.strahler.tgz v.strahler] is a module that calculates the Strahler Order for all lines of a given dendritic network.

: '''Author:''' Florian Kindl. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.strahler

==== v.swathwidth ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.swathwidth v.swathwidth] creates a vector map representing the sea bottom coverage of a multibeam (swath) sonar survey.
: ([http://david.p.finlayson.googlepages.com/swathwidth Screenshots])

: '''Authors:''' David Finlayson, Hamish Bowman

==== v.thickness ====

: [http://marcin.slodkowski.googlepages.com/v.thickness.tgz v.thickness] creates points of thickness vectors from the vectors of strike and dip angles.The v.thickness is GUI GRASS script for v.dip.

: '''Author:''' Marcin Slodkowski

==== v.transect.kia ====

: [https://svn.osgeo.org/grass/grass-addons/vector/v.transect.kia v.transect.kia] calculates kilometric abundance indexes (KIA), a common indirect presence index used in wildlife monitoring along line transect surveys.
: Path lenghts can be corrected by draping on a DEM, different type of point objects can be weighted according to their relative importance, and paths can be segmented using a further polygon vector (to calculate, say, abundances per elevation range or per habitat class).
: The module is written in bash and needs a GRASS install compiled with sqlite support.

: '''Author:''' Clara Tattoni and Damiano G. Preatoni

==== v.trees3d ====

: [http://les-ejk.cz/programs/ v.trees3d] is a module for making 3D trees from input vector point file.

: '''Author:''' Jachym Cepicky

==== v.trimesh ====
: [http://www.valledemexico.ambitiouslemon.com/vtrimesh.html v.trimesh] creates a triangular mesh from a vector map using areal constraints for refinement. It uses Jonathan Shewchuk's Triangle library.

: '''Author:''' Jaime Carrera

==== v.what.rast.buffer ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.what.rast.buffer v.what.rast.buffer] is a script that calculates univariate statistics of raster map(s) from buffers around vector points. Results are written to a file. Resolution is taken from each input map.
: ''see also the [http://starspan.casil.ucdavis.edu StarSpan] software

: '''Author:''' Hamish Bowman

==== v.variogram [deprecated: use v.autokrige instead] ====

: v.variogram is a script that create an omnidirectional experimental semi-variogram. This scripts require R-statistics software installed on your machine. Now the script is updated to run on spgrass6 >= 0.3 and sp >= 0.9 [http://grass.osgeo.org/pipermail/statsgrass/2006-October/000455.html reply].

: '''Author:''' Ivan Marchesini, Pierluigi De Rosa.

==== v.vect.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.vect.stats v.vect.stats] counts the number of points falling into each polygon and optionally calculates statistics from numeric point attributes for each polygon. v.vect.stats is a C module and works with GRASS 6.4 and higher (see enclosed patches for 6.5 and 7.0).

: '''Author:''' Markus Metz

==== AniMove ====

: [http://www.faunalia.it/animov/ AniMove] is software for analysis of animal movement and ranging behaviour using QGIS+GRASS+R.

:'''Authors:''' Support by Faunalia.it

==== Utilities ====

===== Shapemerge =====

: [http://perrygeo.googlecode.com/svn/trunk/gis-bin/shpmerge.sh shpmerge] merges all the shapefiles in the current directory into a single output shapefile

:'''Authors:''' Perrygeo

=== Raster add-ons ===

See also

svn co <nowiki>https://svn.osgeo.org/grass/grass-addons/raster</nowiki>

==== Raplat ====

GRASS-RaPlaT: The Radio Planning Tool for GRASS GIS system developed by support of Slovenian largest mobile operator Mobitel. It is especially designed for radio coverage calculation of GSM/UMTS systems, but can be applied also to other wireless systems in the frequency range 400 MHz – 2.4 GHz (e.g. TETRA, WiFi). Its structure is modular and characterized by high level of flexibility and adaptability.

* Documentation: http://commsys.ijs.si/en/component/content/article/54-software/149-user-manual
* Software: http://commsys.ijs.si/en/software/grass-raplat

: '''Author:''' Department of Communication Systems, Jozef Stefan Institue, Jamova 39, SI-1000 Ljubljana, Slovenia

==== r.area ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.area r.area] Very simple module. Calculate area size (in cells) for every individual category in input raster map and write number of cells as the value of each cell in the area. Optionally write a binary coverage map and set a minimum area threshold. Works well with {{cmd|r.clump}}.

: '''Author:''' Jarek Jasiewicz

==== r.basin ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.basin/ r.basin] Generates the main morphometric parameters of the basin starting from the digital elevation model and the coordinates of the basin's closing section.

: '''Author:''' Margherita Di Leo, Massimo Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.basin/

==== r.bilateral ====

: [http://les-ejk.cz/files/programs/grass/r.bilateral.tgz r.bilateral] Bilateral filter is an edge-preserving filter, which combines domain and range filtering. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.broscoe ====

r.broscoe.sh calculates waerden test and t test statistics for some values of threshold area on a single basin, according to A.J.Broscoe theory (1959).
See v.strahler package

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.strahler/

==== r.boxcount ====

: r.boxcount and r.boxcount.sh calculate the fractal dimension for a given map. These are versions for grass6 of [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake's modules] for grass43.

: '''Authors:''' Mark Lake, grass6 port: Florian Kindl.

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount/
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount.sh/

==== r.burn.frict ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.burn.frict r.burn.frict] converts vector geometries to raster cells, using a simple anti-aliasing method to close "gaps" between diagonal cells. Useful for "burning" vector geometries into a friction surface, making sure that simulated movement does not "slip" through converted cells that have only diagonal neighbours.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.burn.frict

==== r.clump2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.clump2 r.clump2] is a C module similar to r.clump. Differences are: diagonally adjacent cells are also clumped but can be excluded, NULL (nodata) cells are always excluded, and selective clumping with start coordinates is supported.

: '''Author:''' Markus Metz

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.clump2

==== r.colors.out_vtk ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.out_vtk r.colors.out_vtk] is a shell script used to export the color table associated with a raster map layer to a {{wikipedia|VTK}} XML file. (see also [[Help with 3D]])

: '''Author:''' Hamish Bowman

==== r.colors.quantiles ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.quantiles/r.colors.quantiles r.colors.quantiles] is a shell script used to create raster colors rules based on nquantiles. It uses R and spgrass6 package (RGRASS).

: '''Authors:''' Mathieu Grelier

==== r.colors.stddev ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.colors.stddev] ''moved into main archive''

==== r.convergence ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.convergence r.convergence] calculate topographic convergence index, useful to detect lineamets represented by chanell/ridge system

: '''Author:''' Jarek Jasiewicz

==== r.cpt2grass ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.cpt2grass] is a GRASS script for importing a [http://www.soest.hawaii.edu/gmt/ GMT] .cpt color table into GRASS. It can save to a text file suitable for r.colors or automatically apply the color table to a raster map. For a large collection of GMT .cpt files see http://sview01.wiredworkplace.net/pub/cpt-city/
: Other palette ideas from [http://geography.uoregon.edu/datagraphics/color_scales.htm Univ. Oregon] and [http://oceancolor.gsfc.nasa.gov/PRODUCTS/colorbars.html NASA/Goddard's OceanColor] (latter partially translated for use with GRASS on the [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.tools/palettes grass-addons SVN]).

: '''Author:''' Hamish Bowman

==== r.csr ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.csr r.csr] integrates several Grass programs to produce colored, shaded-relief rasters in one step. Accepts single or multiple elevation/bathymetry maps as input; optionally will fill data holidays with 3x3 median filter, multiple times, if required; can apply color maps from a) input raster, b) another raster in MAPSET, or c) from a rules file; otherwise, rainbow colorbar is applied. Output colored, shaded-relief rasters can optionally be exported to tiff format if the appropriate flag is given. Shading parameters can be modified, though useful defaults are given.

: '''Author:''' Eric Patton

==== r.cva ====

: [http://www.ucl.ac.uk/~tcrnmar/GIS/r.cva.html r.cva] is a cumulative viewshed analysis module. It is an advanced version of the {{cmd|r.los}} program.

: '''Author:''' [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake]

==== r.denoise ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.denoise r.denoise] denoises (smooths/despeckles) topographic data, particular DEMs derived from radar data (including SRTM), using Xianfang Sun's [http://www.cs.cf.ac.uk/meshfiltering/index_files/Page342.htm denoising algorithm]. It is designed to preserve sharp edges and to denoise with minimal changes to the original data. See the [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise/r.denoise.html manual pages] for details. Further information on Sun's denoising algorithm, including an example, is available [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise here].

: '''Author:''' John Stevenson

==== r.dominant_dir.m and r.calc_terraflow_dir.m ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.terraflow.tools dominant_dir.m and calc_terraflow_dir.m] are two Matlab scripts for determining the dominant flow direction from a r.terraflow MFD map and converting into a GRASS aspect map for use with d.rast.arrow, etc.

: '''Author:''' Hamish Bowman

==== r.diversity ====
: [http://svn.osgeo.org/grass/grass-addons/raster/r.diversity/ r.diversity] calculates selected diversity indices by calling various r.li commands.This script uses the [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.pielou.html Pielou], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.renyi.html Renyi], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.shannon.html Shannon] and [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.simpson.html Simpson] indices. The output is a map for each index.

: '''Author:''' Luca Delucchi, Duccio Rocchini

==== r.eucdist ====

: [http://david.p.finlayson.googlepages.com/r.eucdist r.eucdist] creates a raster map estimating the euclidean distance from known cells.

: '''Author:''' David Finlayson

==== r.fragment ====

: [http://www.chrisgarstin.com/stuff/r.fragment r.fragment] fragments a raster into a user-defined set of smaller tiles according to an input number of rows and columns.
: '''Author:''' Eric Patton

==== r.fuzzy ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy r.fuzzy] Calculates membership of every cell in raster according membership function defined by user.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.logic ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy.logic r.fuzzy.logic] Perform fuzzy operators (AND, OR, NOT, IMP) on membership's map using T-norms and T-conorms for 6 most popular families.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.system ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy.system r.fuzzy.system] Perform full fuzzy clasificationwith 6 most popular fuzzy logic families and few methods of deffuzification.
: '''Author:''' Jarek Jasiewicz

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.fuzzy.system

==== r.game_of_life ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.game_of_life r.game_of_life] is a shell script which runs Conway's classic Game of Life using GRASS raster modules. It is meant to demonstrate how easy it is to program cellular automata in GRASS as well as various 3D raster volume and time series visualization techniques.

: '''Author:''' Hamish Bowman

==== r.gauss ====

: [http://www.les-ejk.cz/files/programs/grass/r.gauss.tgz r.gauss] is Gaussian and Laplacian of Gaussian filter for GRASS. It is written in C language.

:'''Author:''' Jachym Cepicky

==== r.gradgrid4 ====

: [http://www.uibk.ac.at/geographie/personal/mergili/gradgrid4.zip gradgrid4] is a tool for interpolating values of discrete data points to a raster map, applying a local regression approach with a predictor raster. The model is based on shell and python scripts as well as an R batchfile. It was tested on Fedora Core 6 with GRASS 6.2.1 and R 2.5.1, but should work under most UNIX systems. After unzipping the gradgrid4 folder, store it at any place in your local file system. In the subfolder docs you can find a manual and a publication draft with a detailed description of the concept and the example of an application. The subfolder testloc constitutes a GRASS location with test data.

: '''Author:''' Martin Mergili

==== r.hazard.flood ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.hazard.flood/ r.hazard.flood] is an implementation of a fast procedure to detect flood prone areas. The exposure to flooding may be delineated by adopting a topographic index (TIm) computed from a DEM. The portion of a basin exposed to flood inundation is generally characterized by a TIm higher than a given threshold, tau. The threshold is automatically determinated from the cellsize. The proposed procedure may help in the delineation of flood prone areas especially in basins with marked topography. The use of the modified topographic index should not be considered as an alternative to standard hydrological-hydraulic simulations for flood mapping, but it may represent a useful and rapid tool for a preliminary delineation of flooding areas in ungauged basins and in areas where expensive and time consuming hydrological-hydraulic simulations are not affordable or economically convenient.

: '''Author:''' Margherita Di Leo

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.hazard.flood/

==== r.in.mb ====

: [http://blogs.tekmap.ns.ca/archives/458 r.in.mb] is a "GRASS/[[MB-System]] program designed to import ''mbio'' compatible multibeam sonar data directly into the GRASS GIS. The program is a modified version of {{cmd|r.in.xyz}}. Instead of reading an ASCII XYZ file, ''r.in.mb'' reads an MB-System compatible list file." It can do automatic reprojection and minor hole filling. The default is to import bathymetry data, but optionally amplitude or sidescan sonar data can be loaded instead.

: '''Author:''' Bob Covill

==== r.in.onearth ====

: [http://www-pool.math.tu-berlin.de/~soeren/grass/modules/ r.in.onearth] for download and import satellite images direct from the NASA onearth WMS server into GRASS.

: '''Author:''' Soeren Gebbert

==== r.in.swisstopo ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.in.swisstopo/ r.in.swisstopo] for importing swisstopo digital elevation model data into GRASS raster maps.

: '''Author:''' Jürgen Hansmann

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.in.swisstopo/

==== r.in.wms (.py) ====

: [http://les-ejk.cz/files/programs/grass/r.in.wms.tgz r.in.wms] for download and import maps direct from WMS servers into GRASS. This script is written in Python Programming language. Note GRASS 6.2+ provides a shell script version of r.in.wms, take care of which one is actually being run.

: '''Author:''' Jachym Cepicky

==== r.inund.fluv ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.inund.fluv/ r.inund.fluv]This command allows to obtain a fluvial potentially inundation map given a high-resolution DTM of the area surrounding the river and a water surface profile calculated through an 1-D hydrodinamic model.

: '''Authors:''' Roberto Marzocchi, Bianca Federici, Domenico Sguerso

==== r.isoregions ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.isoregions/r.isoregions r.isoregions] allows isoregions creation from a GRASS raster map.

: '''Authors:''' Mathieu Grelier

==== r.interp.mask ====

: [http://david.p.finlayson.googlepages.com/r.interp.mask r.interp.mask] Creates a user-specified buffer around interpolation points that can be used as a MASK to prevent or clip excessive extrapolation artifacts. This works much better than a standard convex hull around the points.

: '''Author:''' David Finlayson

==== r.ipso ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.ipso/ r.ipso] Produces the ipsometric and ipsographic curve related to a digital elevation model and prints the percentiles

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.ipso/

==== r.li ====

: [http://www.faunalia.it/download/r_li/ r.li] is a more flexible and faster replacement of the old r.le. '''''Moved into 6.3-SVN'''''.

: '''Authors:''' Claudio Porta, Davide Spano, Serena Pallecchi, [http://www.faunalia.it Faunalia]

==== r.local_max.pl ====

: [http://les-ejk.cz/files/programs/local_max.pl Local maxima] is a Perl script for <code>r.mapcalc</code>. It detects local maxima of the image.

: '''Author:''' Jachym Cepicky

==== r.mandelbrot ====

: [http://grasslab.gisix.com/scripts/r.mandelbrot r.mandelbrot] is a shell script to calculate the Mandelbrot set.- for GRASS versions 6.X.

: '''Author:''' Peter Löwe

==== r.maxent.lambdas ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.maxent.lambdas r.maxent.lambdas] is a shell script to compute raw and/or logistic prediction maps from a lambdas file produced with MaxEnt 3.3.3e. See also [[#r.out.maxent_swd]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.maxent.lambdas/

==== mcda====

: mcda suite is a toolset for geographics multi-criteria decision aiding and data analysis based on ELECTRE (r.mcda.electre), REGIME (r.mcda.regime) and FUZZY (r.mcda.fuzzy) algorithm. The module r.roughset is also included for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/

==== r.mlv ====

: [http://les-ejk.cz/files/programs/grass/r.mlv.tgz r.mlv] is Mean of least variance filter for GRASS. It is an edge-preserving (or even edge-enhacing) filter, which should serve for removing additive noise from images. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.obstruction, r.planning.static, r.planning.cinematic ====

: [http://www.ing.unitn.it/~grass/software.html r.obstruction, r.planning.static, r.planning.cinematic]: r.obstruction creates a polar obstruction map from a DTM. r.planning.static performs a static planning for GPS and Glonass surveys using the obstruction map created with r.obstruction. r.planning.cinematic performs a cinematic planning for GPS and Glonass surveys. (University of Trento, Faculty of Engineering)

: '''Author:''' Daniele Carli, Dimitri D'Inca', Gianluca Fruet, Domenico Sguerso, Paolo Zatelli

==== r.out.jpeg ====

: [http://www.geospatial.it/allegri/grass/r.out.jpeg_ r.out.jpeg] is a simple GRASS script to export georeferenced JPEG images from rasters, keeping the associated color table. It is a two-step export: first a ppm file is created, then it is converted to jpeg usgin the "convert" command from ImageMagick

: '''Author:''' Giovanni Allegri

==== r.out.geoserver ====

: [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 r.out.geoserver] exports GRASS raster layer to [http://geoserver.org GeoServer] and publishes it using WMS. The modul is a shell script. It uses: r.out.gdal, curl, xmlstarlet and GeoServer REST interface.

: '''Author:''' Pawel Netzel

==== r.out.gmap ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmap r.out.gmap] outputs GRASS raster map into set of image tiles
following the tiling scheme of Google Maps and Microsoft Virtual Earth. Read more in the OSGeo Journal [http://www.osgeo.org/journal Volume 5 (2009, to appear)] see also [[#r.out.kml|r.out.kml]] and [[#v.out.kml|v.out.kml]]

: '''Author:''' Tomas Cebecauer

==== r.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt r.out.gmt] is a GRASS script for exporting a GRASS raster map into a [http://www.soest.hawaii.edu/gmt/ GMT] grid file. It also creates a GMT color table from the data and can generate some GMT commands for plotting a postscript file. (code is experimental, but functional) see also http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview

: '''Authors:''' Hamish Bowman, Dylan Beaudette

==== r.out.gmt2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt2 r.out.gmt2] is a modified version of Hamish's r.out.gmt. Added options for title, xlabel, ylabel, comment, and map width. Removed any settings that can be changed by gmtset for more flexibility.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== r.out.kap_template ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.kap_template r.out.kap_template] is a shell script that exports a raster map into a GeoTiff and a metadata text file suitable for use with KAP (BSB) raster nautical chart converter programs such as <tt>tif2bsb</tt> (after verifying that you are legally entitled to use such a tool).
: '''''This is EXPERIMENTAL software. NOT FOR NAVIGATIONAL USE.'''''
: For an easy to use data viewer, see also the [http://www.opencpn.org OpenCPN] free navigational software.

: '''Author:''' Hamish Bowman

==== r.out.kml ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.kml r.out.kml] is a shell script that exports a raster map into a KML file and image for Google Earth or Worldwind. See also [[#v.out.kml|v.out.kml]] and [[#r.out.gmap|r.out.gmap]].

: '''Author:''' Hamish Bowman

==== r.out.maxent_swd ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.out.maxent_swd r.out.maxent_swd] is a shell script to produce a set of SWD files as input to MaxEnt 3.3.3e using r.stats. See also [[#r.maxent.lambdas]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.out.maxent_swd/

==== r.pack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.pack r.pack] and [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.unpack r.unpack] are two GRASS scripts for transferring raster maps to another computer as a single compressed file including color table etc.
: An earlier version has been renamed as [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.pack/experiment r.pack.mat] and [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.unpack/experiment r.unpack.mat].

: '''Author:''' Hamish Bowman

==== r.pi ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.pi/ r.pi] (raster patch index) provides various functions to analyse spatial attributes of a landscape. It has a focus on patch-based indices but delivers class-based indices as well. r.le and its successor r.li provide landscape indices.

: '''Authors:''' Programming: Elshad Shirinov, Scientific concept: Dr. Martin Wegmann

==== r.prominence ====

: '''r.prominence''' calculates the average difference between a central cell and its neighbors. It approximated the terrain 'ruggedness' by looking at average differences in elevation within a given neighborhood.

: '''Author:''' Benjamin Ducke

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.prominence/

==== r.refine ====

: [http://www.bowdoin.edu/~ltoma/research.html r.refine]: reduces a DEM to a TIN (takes as input a grid DEM and an error margin and simplifies it to the desired accuracy into a TIN)
Available via the source code repository [https://github.com/jonrtodd/r.refine]
: '''Authors:''' Laura Toma and Jonathan Todd

==== r.rifs ====

: [http://www.ucl.ac.uk/~tcrnmar/ r.rifs]: r.rifs generates a raster map and/or image of a fractal by means of the specified random iterated function system.

: '''Author:''' Mark Lake

==== r.roughness ====

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.sh r.roughness.sh] is a shell script to calculate the surface roughness of a DEM, using r.surf.area and v.surf.rst. (for GRASS versions 6.1 and above)

[http://www.igc.usp.br/pessoais/guano/downloads/r.roughness60 r.roughness60] - for GRASS versions 6.0.X

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.area r.roughness.window.area] - calculate surface roughness as the ratio of real (surface) area and planar area, using a moving-window approach.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector r.roughness.window.vector] - calculate surface roughness as vector dispersion, using a moving-window approach. Resulting maps are: Vector Strength (R) and Inverted Fisher's k parameter.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector.html r.roughness.window.vector.html] - provisional help page for r.roughness.window.vector.

: '''Author:''' Carlos Henrique Grohmann

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.roughness/

==== r.roughset ====

: r.roughset is a module for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/r.roughset/

==== r.seg ====

: '''r.seg''' performs image segmentation and discontinuity detection (based on the Mumford-Shah variational model).
: The module generates a piece-wise smooth approximation of the input raster map and a raster map of the discontinuities of the output approximation. The discontinuities of the output approximation are preserved from being smoothed.
: See [http://www.ing.unitn.it/~vittia/sw here] for details and examples.

Available [http://www.ing.unitn.it/~vittia/sw here] and with improvements via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.seg/

: '''Author''' Alfonso Vitti

==== r.smoothpatch ====

: [http://david.p.finlayson.googlepages.com/r.smoothpatch r.smoothpatch] creates a composite of two rasters using a distance-weighted average across the transition to smooth the edges.

: '''Author:''' David Finlayson

==== r.soils.texture ====

: r.soils.texture is a module to define soils texture from sand and clay raster file with a schema text file (now FAO,USDA and ISSS are available). It is written in C language. - for GRASS versions 6.x - For bugs and suggest: g_massa@libero.it

:'''Author:''' Gianluca Massei

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.soils.texture/

==== r.stack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stack r.stack] is a shell script used to patch all the raster maps in a time series (or burst 3D raster) together into a vertical stack, to aid mutli-map analyses in modules where group input is not yet available.

: '''Author:''' Hamish Bowman

==== r.stream.angle ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.angle r.stream.angle] Divide stream network into stright line segments according users input. It extends Module uses as input direction and stream network map produced by r.watershed and stream.extract or custom user input. See description for details.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.angle

==== r.stream.basins ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.basins r.stream.basins] delineate basins according users input. It extends r.water.outlet funcionality to extracting more than one basin at one step. Module uses as input direction map produced stream network produced by r.stream.extract, r.watershed, r.stream order or custom user input. More in tutorial on grass-wiki pages.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.basins

==== r.stream.del ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.del r.stream.del] Calculates downslope length of first order streams and delete them if it length (in pixels) is lower than the treeshold. It also join false segments left by deletion into one with category of upper. It uses r.watershed direction map and r.watershed stream map as input. The module is added only for r.watershed module, r.stream.extract has deleting short streams build-in. During development of r.stream.* it will be probably abandoned due to duplicate functionality

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.del

==== r.stream.distance ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.distance r.stream.distance] Calculates downslope distance and downslope elevation difference between current cell and stream or outlet cells. It uses r.watershed direction map, r.watershed or r.stream.extract stream map and optionally DEM as input.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.distance

==== r.stream.extract ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.extract r.stream.extract] extracts topologically clean stream networks from input elevation and optionally accumulation maps. Output is available as raster and vector and can be used as input for the other r.stream.* modules by Jarek Jasiewicz.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.extract

==== r.stream.order ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.order r.stream.order] orders stream network outputed by r.watershed or r.stream.extract according Sthrahler, Shreve, Horton and Hack ordering systems. It require as input stream and direction map and optionally accumulation map. It handle both SFD nad MFD modes but all data must come from the same procedure.

: '''Author:''' Jarek Jasiewicz, Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.order

==== r.stream.pos ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.pos r.stream.pos] Helper module for calculating local stream network properties and linear geostatistics. Mostly To use with R and other grass modules.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.pos

==== r.stream.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.stats r.stream.stats] calculate Hortonian statistics for Stahler or Horton stream network created by r.stream.order. It uses r.watershed direction map, DEM and r.stream.order's Stahler or Horton stream network as input. It outputs calculated statistics to standard output.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.stats

==== r.surf.nnbathy ====

: [http://www.sieczka.org/programy_en.html r.surf.nnbathy] interpolates a surface from a raster input using Pavel Sakov's [http://code.google.com/p/nn-c/ nn] natural neighbor interpolation library. Provides triangulation, Sibson natural neighbor interpolation and non-Sibsonian interpolation.

: '''Author:''' Maciej Sieczka

==== r.surf.volcano ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.surf.volcano r.surf.volcano] creates an artificial surface resembling a seamount or cone volcano. The user can alter the size and shape of the mountain and optionally roughen its surface. Available decay functions are polynomial, Gaussian, Lorentzian, logarithmic, and exponential.

: '''Author:''' Hamish Bowman

==== r.terracost ====

[http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. '''Lead author''': Laura Toma

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==== r.tileset ====

: ''{{cmd|r.tileset}} moved into main archive''

==== r.traveltime ====

: [http://jesbergwetter.twoday.net/stories/4845555/ r.traveltime] computes the travel time of surface runoff to an outlet. The program starts at the basin outlet and calculates the travel time at each raster cell recursively. A drainage area related threhold considers even surface and also channel runoff. Travel times are derived by assuming kinematic wave approximation. The results can be used to derive a time-area function. This might be usefull for precipitation-runoff calculations (estimation of flood predictions) with a lumped hydrologic model (user-specified unit hydrograph).

: '''Author:''' Kristian Förster

==== r.univar.zonal ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar.zonal r.univar.zonal] is similar to r.univar, but calculates statistics separately for each category(zone) present in the separate input map used to define zones (zonal statistics). The output can be like the one of r.univar or in easier to read table format and can be written to a file. This addon is only needed for GRASS 6.4, its functionality has been added to r.univar in 6.5 and 7.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.univar.zonal

==== r.viewshed ====

: r.viewshed is a module for extremely fast line of sight analysis (replaces the slow r.los). It is written in C language for GRASS versions 6.X/7.x.

: '''Author:''' Laura Toma, USA

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.viewshed

Once {{trac|390}} is solved, it will substitute r.los.

==== r.wavelets ====

: [http://www.ing.unitn.it/~grass/software.html r.wavelets]: This package contains wavelets decomposition and reconstruction modules for the GRASS GIS: r.owave.dec computes the orthogonal wavelet transform of a raster map. r.owave.rec reconstructs a raster map from an orthogonal wavelet transform. r.biowave.dec computes the biorthogonal wavelet transform of a raster map. r.biowave.rec reconstructs a raster map from a biorthogonal wavelet transform.

: '''Authors:''' Members of the University of Trento, Faculty of Engineering

==== r.wf ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.wf/ r.wf] produces the Width Function of a basin. The Width Function W(x) gives the number of the cells in a basin at a flow distance x from the outlet (it is also referred as distance-area function). The distance is not the euclidean one, but it is measured along the flowpath towards the outlet.

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.wf/

==== r.xtent ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.xtent r.xtent] computes a raster map layer representing the Voronoi diagram, weighted Voronoi diagram or a more complex territorial partitioning of space around points (centers) in a vector input map, based on the XTENT formula.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.xtent

==== r.zc.pl ====

: [http://les-ejk.cz/files/programs/zc.pl Zero crossing] is a simple Perl script, finds the ,,zero crossings`` from the Laplacian of Gaussian filter (see above). It is really very simple, the edges don't need to be really on that pixel, where they are detected, no interpolation is performed.

: '''Author:''' Jachym Cepicky

==== GIPE ====

: The GRASS Image Processing Environment (GIPE) has USLE, Energy-balance and radiance-reflectance correction models.

: '''Author:''' Yann Chemin (unless specified otherwise).

svn co https://svn.osgeo.org/grass/grass-addons/imagery/gipe

Remark: This is progressively moved to main GRASS SVN (aka GRASS 7)

:* r.hydro.CASC2D, ported from GRASS 5.x version, is temporarily here waiting to return to main GRASS.

:* r.soiltex2prop creates porosity, Saturated Hydraulic conductivity (Ksat) and wetting front pressure head (Hf) from percentage of sand and clay after Rawls et al., 1990. This is a must for r.hydro.CASC2D.

:* i.biomass creates biomass growth map from fPAR, lightuse efficiency, water availability (or evap.fraction), Lat, doy and tsw.

:* i.dn2ref.l7, r.dn2ref.ast create top of atmosphere reflectance for Landsat 7ETM+ and ASTER. These modules also have a flag for radiance output. Updated i.dn2ref.l7 to read .met calibration file.

:* i.dn2full.l[5,7] is an attempt to get all bands of Landsat[5,7] calibrated and corrected to either reflectance or temperature, reads only the .met file.

:* i.dn2potrad.l[5,7] is an attempt to get ET potential from DN of Landsat 7 (Careful! No Atmospheric correction!).

:* i.eb.* are a set of 10+ GRASS modules that together perform the main functions of the SEBAL model (Bastiaanssen, 1995). Those functions include (but are not limited to) Soil heat flux, sensible heat flux, net radiation, evaporative fraction at satellite overpass, diurnal actual evapotranspiration, momentum roughness length, etc. These modules are also part of any Energy-Balance related processing.

:* i.evapo.potrad creates diurnal Potential evapotranspiration assuming all net radiation becomes ET, according to SEBAL model (Bastiaanssen, 1995). This module also has a flag for diurnal net radiation as required by SEBAL in i.eb.eta.

:* i.evapo.SENAY creates actual evapotranspiration following the regional method of Senay (2007).

:* i.lmf creates a Local Maximum Fitting on the temporal dimension of the multi-date input dataset, working, but more precision still to be added.

:* i.vi.mpi is the mpi version of i.vi for cluster GRASS GIS education (no speed up here!) '''Author:''' Shamim Akhter

:* i.modis.stateqa extracts State Quality Assessment information from Modis 500m (MOD09A) products.

:* i.water creates a Water Mask from NDVI and Albedo, or specifically for Modis: NDVI and Band 7.

:* i.wi creates a given Water Index (only one so far).

==== HydroFOSS ====

: HydroFOSS - a GIS embedded approach for Free & Open Source Hydrological modeling.

: '''Author:''' Massimiliano Cannata

svn co https://svn.osgeo.org/grass/grass-addons/HydroFOSS/

==== Hikereport ====

: python script that computes length, cumulative uphill and downhill, average slopes on an interactively drawn path. Based on r.profile's output.

: '''Author:''' Stefano Negri

http://tracce.wordpress.com/?attachment_id=71

=== Misc add-ons===

==== m.eigensystem ====

m.eigensystem - Computes eigen values and eigen vectors for square matrices.

: http://svn.osgeo.org/grass/grass-addons/misc/m.eigensystem/

: '''Author:''' Michael Shapiro

===Database add-ons===
==== db.join ====

: Table joining: join one table into another through common attributes

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/database/db.join/
or
g.extension db.join

===General add-ons===

==== GRASS create location scripts ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/grass_create_location grass_create_location.sh] Script to generate a new GRASS location from GIS file (e.g. geoTIFF or SHAPE), wktfile or EPSG code.

: '''Author:''' Markus Neteler

==== g.laptop.sh ====

: [http://www.gbd-consult.de/dassau/grass/g.laptop/g.laptop.sh g.laptop.sh] is an interactive shell script to extract raster and vector data from current Location into a new one. Data can be copied or extracted in current or original resolution and region extend. This script was written to extract smaller parts of a GRASS location to be able to present them on a laptop without the necessity to transfer huge data. Maps do not have to be in the same mapset.

: '''Author:''' Otto Dassau

==== Readline completion ====

: '''''Readline completion''''' for GRASS commands under the bash shell: [http://www.sorokine.info/grass-complete/ grass-complete] won't clutter the environment but needs to be installed; [http://dcalvelo.free.fr/grass/grass_rlcompleter.sh grass_rlcompleter.sh] needs almost no installation but will pollute the environment. Grass-Complete currently requires Bash version 2.05 for proper install.

: '''Author:''' Alexandre Sorokine (grass-complete), Daniel Calvelo (grass_rlcompleter.sh)

==== g.region.point ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.region.point g.region.point] is a shell script which resets the computational region to a square box around a given coordinate. It is intended for use within GRASS scripts to speed up processing by limiting expensive raster calculations to a small area of interest.

: '''Author:''' Hamish Bowman

==== g.linke_by_day ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.sun.tools/ g.linke_by_day] is a python script for [[r.sun]] which interpolates a Linke turbidity value for a given day of the year based on monthly values edited into the script.

: '''Author:''' Hamish Bowman

==== g.xlist ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xlist g.xlist] is a C implementation of g.mlist. g.xlist searches for data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

==== g.xremove ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xremove g.xremove] is a C implementation of g.mremove. g.xremove removes data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

=== Imagery add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/imagery

==== GIPE ====

GIPE (see also above in raster section) provides:
i.biomass, i.dn2potrad.l5, i.dn2potrad.l7, i.dn2ref.ast, i.eb.deltat, i.eb.disp, i.eb.eta, i.eb.evapfr, i.eb.g0, i.eb.h0, i.eb.h_SEBAL01, i.eb.h_SEBAL95, i.eb.h_iter, i.eb.molength, i.eb.netrad, i.eb.psi, i.eb.rah, i.eb.rohair, i.eb.ublend, i.eb.ustar, i.eb.wetdrypix, i.eb.z0m, i.eb.z0m0, i.evapo.PT, i.evapo.TSA, i.evapo.potrad, i.evapo.senay, i.evapo.time_integration, i.lmf, i.modis.stateqa, i.sattime, i.vi.grid, i.vi.mpi, i.water, i.wi

svn co https://svn.osgeo.org/grass/grass-addons/gipe/

: '''Author:''' Yann Chemin

==== i.homography ====

Rectifies an image by computing a coordinate transformation for each pixel in the image based on the control points created by i.linespoints. The approach uses homography extended for corresponding lines.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.homography

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on code written by Stefano Merler, ITC-irst, Italy

==== i.linespoints ====

An imagery command that enables the user to mark coordinate system points as well as lines on an image to be rectified and then input the coordinates of each point for creation of a coordinate transformation matrix. The transformation matrix is needed as input for the GRASS program i.homography.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.linespoints

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on i.points

==== i.landsat.toar ====

Transform calibrated digital number of Landsat products to top-of-atmosphere radiance or top-of-atmosphere reflectance and temperature (band 6 of the sensors TM and ETM+). Optionally, used to calculate the at-surface radiance or reflectance with atmospheric correction (DOS method).

Available also in GRASS 7.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.toar

: '''Author:''' E. Jorge Tizado

==== i.landsat.acca ====

Implements the Automated Cloud-Cover Assessment (ACCA) Algorithm from Irish (2000) with the constant values for pass filter one from Irish et al. (2006). To do this, it needs Landsat band numbers 2, 3, 4, 5, and 6 (or band 61 for Landsat-7 ETM+) which have already been processed from DN into reflectance and band-6 temperature with i.landsat.toar).

Available also in GRASS 7.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.acca

: '''Author:''' E. Jorge Tizado

==== i.points.auto ====

This module allows a search of GCP's on two raster-maps with differents levels of automation. The ''manual'' search is the default search, so it's possible to determine the GCP's manually with the mouse (like {{cmd|i.points}}). ''Semiautomated'' search: The user determines with the mouse some correspondent areas (with a discrete precision) in the two maps and the module searches itself the GCP's in these areas. ''Automated'' search: At the start of module the user has to load the maps that the algorithm uses to the search, so it is recommended to use the maps filtered with the filters DIVERSITY or STDDEV (of GRASS) with a window of 3x3 or 5x5 pixels. However, the algorithm sometimes works well with the original maps too.

Note: This code is basically an improved i.points (from 2004). Subsequent changes in i.points haven's been ported here yet.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.points.auto

: '''Authors:''' based on i.points; additions by Ivan Michelazzi, Luca Miori (MSc theses at ITC-irst); Supervisors: Markus Neteler, Stefano Merler, ITC-irst 2003, 2004. [http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=37 PDF article]

==== i.points.reproj ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.points.reproj i.points.reproj] is a shell script that will use cs2cs to reproject the target coordinates of a group's POINTS file. By running i.rectify directly to the new target projection, a generation of resampling data loss can be avoided (versus i.rectify + r.proj). On the other hand, i.rectify does not calculate cell resolution well if the map is to be rotated ([http://intevation.de/rt/webrt?serial_num=3296 bug #3296]), in those cases i.rectify+r.proj may be the better option.

: '''Author:''' Hamish Bowman

==== i.plr.py ====

: [[I.plr.py|Probabilistic Label Relaxation]], written in Python

: '''Author:''' Georg Kaspar

==== i.pr ====

: Image classification: implements k-NN (multiclass), classification trees (multiclass), maximum likelihood (multiclass), Support Vector Machines (binary), bagging versions of all the base classifiers, AdaBoost for binary trees and support vector machines. It allows feature manipulation (normalization, principal components,...). It also implements feature selection techniques (RFE, E-RFE,...), statistical tests on variables, tools for resampling (cross-validation and bootstrap) and cost-sensitive techniques for trees and support vector machines.

: '''Author:''' Stefano Merler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.pr

==== i.spec.sam ====

: Spectral Angle mapping

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.sam/

==== i.spec.unmix ====

: Spectral unmixing

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.unmix/

==== i.topo.corr ====
: i.topo.corr is used to topographically correct reflectance from imagery files, e.g. obtained with i.landsat.toar (see above), using a sun illumination terrain model. This illumination model represents the cosine of the incident angle, i.e. the angle between the normal to the ground and the sun rays. It can be obtained with {{cmd|r.sun}} (parameter incidout), and then calculating its cosine with float precision. Correction methods: cosine, minnaert, percent, c-factor.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.topo.corr

: '''Author:''' E. Jorge Tizado

==== i.warp ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.warp i.warp] is a shell script that will use gdalwarp to rectify a raw input image using thin plate splines. The map should be imported into GRASS with r.in.gdal and GCPs set with i.points. Input is the raw image (GeoTIFF, JPEG, etc). Output is a GeoTIFF in the imagery group's target location's map projection. Requires a recent (early 2006) version of GRASS 6.1, or newer.

: '''Author:''' Hamish Bowman

=== Display add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/display

==== d.barb ====

[http://trac.osgeo.org/grass/browser/grass-addons/display/d.barb d.barb] is a C module that will draw wind barbs, straw plots, and arrow plots from raster array or sparse vector point data. It can use either direction + magnitude, or u + v components as the input, and can produce a legend key. (''work in progress, but it's mostly there'')

: '''Author:''' Hamish Bowman

==== d.edit.rast ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.edit.rast d.edit.rast] edits cells in an existing raster map displayed on the current monitor.

: '''Author:''' Huidae Cho

==== d.frame.quarter ====

: ('''obsolete''') [http://trac.osgeo.org/grass/browser/grass-addons/display/d.frame.split d.frame.quarter] is a shell script that will split the display into four quadrants (or sixths) using ''d.frame''. Individual frames are named ''uno, dos, tres, cuatro'', and ''full_screen''.
: Replaced by {{cmd|d.split.frame}} in main.

: '''Author:''' Hamish Bowman

==== d.frame.split ====

: ''d.frame.split moved into main archive as {{cmd|d.split.frame}}''

==== d.frontline ====

: [http://cloud.github.com/downloads/amuriy/GRASS-scripts/d.frontline d.frontline] is a shell script that draws frontlines on the graphics monitor using ''d.graph'' module and different types of symbols. Also it optionally saves frontline graphics to ''d.graph'' commands file and/or ''ps.map'' file (for later use with the "read" ''ps.map'' instruction)

: '''Author:''' Alexander Muriy

==== d.hyperlink ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/d.hyperlink.tar.bz2 d.hyperlink] is an interactive shell script that allows the viewing of hyperlinked images from a vector's attribute table in an external image viewer. Queries can be made via SQL statements or interactive mouse-clicking. The attribute table must be pre-populated with a column containing the image to link the vector to; the user also specifies the image folder in the current MAPSET where the images are located. The script currently supports gimp, Eye of Gnome, gthumb, gpdf, and Inkscape image viewers.

: '''Author: '''Eric Patton

==== d.mark ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.mark] is a shell script that quickly displays a marker on the display at a given coordinate.

: '''Author:''' Hamish Bowman

==== d.region.box ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.region.box d.region.box] is a shell script that quickly displays a box around the current region.

: '''Author:''' Hamish Bowman

==== d.stations ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.stations] is a shell script that quickly displays vector points (or sites for GRASS 5.4 and below).

: '''Author:''' Hamish Bowman

==== d.varea ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.varea] is a shell script that quickly displays vector areas.

: '''Author:''' Hamish Bowman

==== pd-GRASS ====

: [http://www.ornl.gov/sci/gist/software/grass/ pd-GRASS]: Parallel Display for GRASS GIS

: '''Author:''' Alex Sorokine

==== [[IconSymbols]] ====

* [[IconSymbols|Symbols]] which can be used with ''d.vect, d.graph'', and ''ps.map''.

=== Postscript add-ons ===

* ''See also [[ps.map scripts|ps.map samples and templates]]''.

==== ps.atlas ====

: [http://les-ejk.cz/programs/grass/ps.atlas ps.atlas] is a shell script that makes more maps on current region according to input *.psmap file. General map can be stored as vector file. The resulting *.eps maps can be automatically converted to *.pdf files.

: '''Author:''' Jachym Cepicky

==== ps.output ====

: [https://trac.osgeo.org/grass/browser/grass-addons/postscript/ps.output ps.output] is much like {{cmd|ps.map}} but with advanced decorations and ability for translucency. Here you can find a [[Ps.output|tutorial]].

: '''Author:''' Jorge Tizado

==== [[AreaFillPatterns]] ====

* Hatches for ps.map's vareas

=== wxGUI add-ons ===

===GRASS and UMN Mapserver===

* [http://www.mail-archive.com/mapserver-users@lists.umn.edu/msg00086.html See interesting posting]
* See wiki [[GRASS and MapServer]] page

==GRASS 5.x (old)==

===Vector add-ons===

* See here: http://grass.osgeo.org/download/addons.php

===Raster add-ons===

* See here: http://grass.osgeo.org/download/addons.php

* [http://www.valledemexico.ambitiouslemon.com/gwmodelling.html r.gmtg] The groundwater modelling tool for grass. A module to use MODFLOW within GRASS. '''Author''': Jaime Carrera

* [http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. For GRASS 5.3. '''Lead author''': Laura Toma
:Newer version available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==GRASS 4.x (very old)==

===Raster add-ons===

* MAGICAL Software: The MAGICAL software comprises a suite of three programs that provide a multi-agent simulation extension for the GRASS GIS software. http://www.ucl.ac.uk/~tcrnmar/simulation/magical/magical.html

[[Category:Community]]
[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

AddOns

2011-08-17T13:05:58Z

⚠️Sbl: added script r.maxent.lambdas

This page contains references to user contributions and add-ons (the original GRASS GIS software can be downloaded [http://grass.osgeo.org/download/ here]).

__TOC__

== AddOns source code repository ==

The AddOns source code is hosted in [http://svn.osgeo.org/grass/grass-addons/ GRASS-AddOns SVN repository].

To checkout:

svn checkout <nowiki>https://svn.osgeo.org/grass/grass-addons/</nowiki> grass-addons

Please read [http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository How to get write access to the GRASS-Addons-SVN repository] and contact the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list if you would like to host your module there.

== Building and installing Addons ==

See the [[Compile and Install#Addons|compile and install]] wiki page.

In GRASS 6.4 and newer you can use the {{cmd|g.extension}} module, e.g. to install <tt>r.fuzzy.system</tt> run:

g.extension extension=r.fuzzy.system

To remove installed Addons run

g.extension extension=r.fuzzy.system operation=remove

== Adding something new ==

Please announce your add-on to the GRASS users' mailing list so that others may be aware of your work. Also please consider adding your module to one of the [[Applications]] pages.

=== Copyright and licensing information ===

''Please be sure to include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.''

e.g. at the top of a shell script:
<pre>
#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################
#
# REQUIREMENTS:
# - avcimport: http://avce00.maptools.org

[script follows]
</pre>

=== Coding standards ===

Please have a look at our [http://grass.osgeo.org/grass63/source/SUBMITTING_SCRIPTS Shell script coding standards] before submitting here.

There are other coding standards given for modules written in C, Tcl/Tk, and Python''(?)'' located in the GRASS source code.

=== Documenting your code ===

You can have an help page template auto-generated by using the GRASS [[module command line parser | command line parser]] with the <tt>--html-description</tt> command line option. Please, see also the [http://grass.ibiblio.org/grass63/manuals/html63_user/g.parser.html g.parser help page]

== Miscellaneous Add-ons ==

* [http://trac.osgeo.org/grass/browser/grass-addons/misc/utm_which_zone utm_which_zone.sh] is a shell script to determine UTM zone from Lat/Lon input. Requires [http://www.octave.org Octave] or Matlab to be installed. A shell-only version is [http://dcalvelo.free.fr/grass/utm_which_zone_sh.sh available] which only requires awk. '''Authors''': Hamish Bowman (Octave part), Markus Neteler (shell script wrapper), Daniel Calvelo (sh+awk version)

* Perl scripts for converting data forth and back between Excel files and PostgreSQL: [http://dcalvelo.free.fr/grass/pg2xls.pl pg2xls.pl] reads data from PostgreSQL and produces an excel workbook; [http://dcalvelo.free.fr/grass/xls2sql.pl xls2sql.pl] reads excel files and outputs SQL statements to be fed into an RDBMS. Both scripts need modules from [http://www.cpan.org CPAN], especially [http://search.cpan.org/dist/Spreadsheet-ParseExcel/ Spreadsheet::ParseExcel] for xls2sql.pl and [http://search.cpan.org/~tmtm/Spreadsheet-WriteExcel-FromDB Spreadsheet::WriteExcel::FromDB] and its dependencies for pg2sql.pl. Check the source headers for more info. '''Authors:''' Daniel Calvelo (xls2sql.pl), Markus Neteler (pg2xls.pl)

* [http://dream.lrrl.arch.tu-muenchen.de/~wqual/perl/dbf2sql.tgz dbf2sql] is a Perl script for translating dbf-tables into a sql-command. dbf-tables are read using dbfdump-command from dbd-xbase-perl module ([http://search.cpan.org/~janpaz/DBD-XBase-0.241/ dbd::xbase] and [http://search.cpan.org/~jv/Getopt-Long-2.35/lib/Getopt/Long.pm getopt::long] have to be installed from CPAN first). There are problems, if the last column of the table contains characters. Suggestions for improvements welcome! '''Author:'''Wolfgang Qual

* [http://www.igc.usp.br/pessoais/guano/downloads/azimuth2.c azimuth2.c] is a small C program to calculate the azimuth and length of vector lines exported by GRASS-GIS as ASCII files (like this: v.out.ascii input=vector output=ascii format=standard). It is useful for create rose diagrams of lineament maps. Improvements on the original code after suggestions by Örs Téglásy, Hungary. '''Author:''' Carlos Henrique Grohmann

* [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 ann.*] is the set of GRASS modules (in python) which implements artificial neural network using FANN library. The package requires Fast Artificial Neural Network Library ([http://leenissen.dk/fann/wp/ FANN]) v2.x. '''Author:''' Pawel Netzel

==GRASS 6.x (current)==

=== Vector add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/vector

==== v.adehabitat.clusthr, v.adehabitat.kernelUD, v.adehabitat.mcp ====

: Tools to calculate home ranges of animals
: '''Author:''' Clement Calenge

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/vector/adehabitat

==== v.append ====

: [http://web.archive.org/web/20060914172621/http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.append v.append] is a shell script combining two vector files AND their associated attribute tables. The vector files should be of the same type and, for best results, should have identically formatted attribute tables.
: ''Note'': also module ''v.patch'' can be used for this task.

: '''Author:''' Michael Barton

==== v.autokrige ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.autokrige/v.autokrige.py v.autokrige] achieves automatic ordinary kriging from GRASS sites (vector point data), using R with spgrass6 (RGRASS) and automap packages.

: '''Author:''' Mathieu Grelier

==== v.breach ====

: [http://www.sieczka.org/programy_en.html v.breach] creates vector maps of lines and points of continously lowering elevation down the input watercourses, based on the input raster DEM.

: '''Author:''' Maciej Sieczka

==== v.colors ====

: {{cmd|v.colors}} ''moved into main archive''

==== v.count.points.sh ====

: [http://wiki.iosa.it/dokuwiki/spatial_analysis:feature_count v.count.points.sh] counts point features in areas, generates table good as input to d.vect.chart.

: '''Author:''' Stefano Costa

==== v.digatt ====

: [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt v.digatt] (shell script) Interactively assign numeric table attributes to series of vector objects. It is meant to be effective by avoiding to type in the attribute value for all single objects again and again. The user is prompted for typing in an attribute value which is assigned to all objects selected by mouseclick afterwards. Next the display is redrawn after updating the table column. Zooming allows to change the region before the old value can be reused or a new one can be typed in (or copied by mouse from another object) in order to assign it to the next series of objects etc. It is tested not very extensively yet. Therefore better work with a copy of your map and consider using v.digit or d.what.vect -e alternatively. [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt.png screenshot].

: '''Author:''' Andreas Philipp

==== v.dip ====

: [http://marcin.slodkowski.googlepages.com/v.dip.tgz v.dip] creates points of thickness vectors from the vectors of strike and dip angles. The v.dip is the main ANSI C core program. Program so-called v.dip can run without GRASS environment.

: '''Author:''' Marcin Slodkowski

==== v.flip ====

: [http://www.sieczka.org/programy_en.html v.flip] flips the direction of selected vector lines (redundant since GRASS 6.3 - there is "v.edit tool=flip").

: '''Author:''' Maciej Sieczka

==== v.group ====

: [http://www.shockfamily.net/cedric/grass/v.group v.group] generates a new vector map with the same geometry as an existing map. The new map has categories and a table based on grouping by the values in certain columns of the existing map's table. The values in these columns are preserved in the table for the new map. It's like a v.reclass that preserves data.

: '''Author:''' Cedric Shock

==== v.in.redwg ====

: v.in.redwg imports DWG files into GRASS.

:'''Author:''' Rodrigo Rodrigues da Silva

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.redwg

==== v.in.gama ====

: Converts [http://www.gnu.org/software/gama/ GNU GaMa] XML output file to a GRASS vector map layer.

:'''Author:''' Martin Landa

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.gama

==== v.in.geodesic ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.geodesic v.in.geodesic] is a shell script which will create a new vector map containing a great circle line. The user may either define a beginning and end coordinate, or define a starting coordinate along with initial azimuth and desired line length.

: '''Author:''' Hamish Bowman

==== v.in.geoplot ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.geoplot v.in.geoplot] converts a [http://www.geoscan-research.co.uk/page9.html/ Geoplot] ASCII export file to a GRASS vector map layer.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.geoplot

==== v.in.gshhs ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.gshhs v.in.gshhs] imports [http://www.soest.hawaii.edu/pwessel/gshhs/index.html GSHHS] shorelines into a GRASS vector map. GSHHS data are automatically reprojected to the current location.

:'''Authors:''' several, updated to GRASS 6 by Markus Metz

==== v.in.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.marxan v.in.marxan] is a python script that imports Marxan output data for display in a vector grid file prepared using v.out.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.in.mbsys_fnv ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.mbsys_fnv v.in.mbsys_fnv] imports [[MB-System]] navigation files into a GRASS vector map. You can choose from swath area coverage, track lines (including outer port/starboard edges), all bounds as points, etc. An attribute database is created containing the vital statistics of the specified feature such as track length or swath coverage (geodesic), start stop time and location, pitch, roll, heave, etc. See also the [[#v.in.p190]] addon.

:'''Author:''' Hamish Bowman

==== v.in.ncdc ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.ncdc v.in.ncdc] imports an [http://www.ncdc.noaa.gov NCDC] stn file (station data) into a GRASS vector map.

: '''Author:''' Huidae Cho

==== v.in.postgis ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.postgis/v.in.postgis.py v.in.postgis] Create a GRASS layer from any sql query on PostGIS data.

: '''Author:''' Mathieu Grelier

==== v.in.osm ====

: [http://kripton.kripserver.net/software/v.in.osm/ v.in.osm]: OpenStreetMap import into GRASS. Yet only supports deprecated API 0.4, will be modified to work with API 0.5 some time soon.

: '''Author:''' Jannis Achstetter

: See also [http://hamish.bowman.googlepages.com/gpsdrivefiles#osm osm2grass.sh] by H Bowman

==== v.in.osm2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.osm2 v.in.osm2]: OpenStreetMap import into GRASS. Supports current API 0.6, downloads using the [http://wiki.openstreetmap.org/wiki/Xapi Xapi] interface and imports using GpsBabel 1.3.5 or newer. GpsBabel restricts to either nodes or ways being imported at a time, not both. Use {{cmd|v.patch}} to rejoin them. (''work in progress'')

: '''Author:''' Hamish Bowman

==== v.in.ovl ====

: [http://grasslab.gisix.com/scripts/v.in.ovl/ v.in.ovl] is a shell script that imports an ASCII vector file created with TOP10|25|50 or similar products.

: '''Author:''' Peter Löwe

==== v.in.p190 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.p190 v.in.p190] is a shell script that imports 'Centre of Source' "S" navigation data from seismic P1/90 (UKOOA) data files and writes it either GRASS vector points or vector lines format. Optionally it will export the navigation data into .csv text files as well. ''Currently in the functional prototype stage, some assembly is required. See inside the shell script for details.'' For working with SEG-Y data, see also the [[#v.in.mbsys_fnv]] addon.

: '''Author:''' Hamish Bowman

==== v.krige ====

: [[V.krige_GSoC_2009 | v.krige]] aims to integrate R functions for kriging (packages automap, gstat, geoR) in a trasparent way. '''Moved into trunk/devbr6 code (r40048)'''

: '''Author:''' Anne Ghisla, as Google Summer of Code 2009 project

: See also [[GRASS_AddOns#v.autokrige]] by Mathieu Grelier

==== Spatial Analysis Tools ====

===== v.lda.py =====

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.lda.py v.lda.py] is a Python script for calculating Ian Johnson's (U. Sidney) Local Density Analysis values. This can be used in two ways. When only one vector points file is entered, it serves to measure clustering of point data at different neighborhood radii. When two different point files are entered, it measures the the co-occurence of the points from the two files. There is an option to export the data into a cvs format file for easy plotting in a spreadsheet or statistical program like R.

===== v.nn.py =====
: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.nn.py v.nn.py] is a Python script for calculating the nearest neighbor coefficient of a single vector points file--as an index of clustering--or of two points files--to provide an index of the correspondence between the points in one file and points in a different file.

==== v.line.center ====

: [http://www.sieczka.org/programy_en.html v.line.center] creates a points vector map with each point located in the middle of the length of the input vector line.

: '''Author:''' Maciej Sieczka

==== v.lmeasure ====

: [http://web.archive.org/web/20060827192321/http://ngeo.de/grassstuff/v.lmeasure v.lmeasure] and [http://web.archive.org/web/20060827060303/http://ngeo.de/grassstuff/v.revlmeasure v.revlmeasure] are two perl scripts that place equidistant vector points along a given arbitrary vector line starting from the beginning or end of the vector line, respectively. Resulting vector points are labeled with the distance from origin.

: '''Author:''' Mats Schuh

==== v.mkhexgrid ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.mkhexgrid v.mkhexgrid] is a python script that creates a hexagonal grid the size of the selected region using user specified side lengths.

: '''Author:''' Trevor Wiens

==== v.out.ascii.db ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.db v.out.ascii.db] is a shell script for exporting vector point data coordinates and selected attribute columns to either a file or to the console.
: ''Superseded in GRASS 6.4 by the new v.out.ascii columns= option.''

: '''Author:''' Hamish Bowman

==== v.out.ascii.mat ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.mat v.out.ascii.mat] is a shell script for exporting vector polygon and polyline data into an ASCII text file suitable for loading into Matlab (or [http://www.gnu.org/software/octave/ Octave]).

: '''Author:''' Hamish Bowman

==== v.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.gmt v.out.gmt] is a shell script that exports a polygon vector file into GMT xy file. psbasemap code was copied from Hamish's r.out.gmt.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== v.out.kml ====

: [http://grasslab.gisix.com/scripts/v.out.kml/ v.out.kml] is a shell script that exports a vector file into a KML file for Google Earth or Worldwind. see also [[#r.out.kml|r.out.kml]] and [[#r.out.gmap|r.out.gmap]]

: '''Author:''' Peter Löwe

==== v.out.marxan ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.marxan v.out.marxan] is a python script that prepares vector layers and exports GRASS vector attributes and adjacency information as Marxan input files. Output from Marxan simulations can be imported using v.in.marxan.
: ''see also the [http://www.uq.edu.au/marxan/ Marxan]

: '''Author:''' Trevor Wiens

==== v.out.svg ====

: [http://svg.cc/grass/index.html v.out.svg] is a module that exports SVG notation along with optional attribute data directly from GRASS 6.x vector layers. Now part of [http://svn.osgeo.org/grass/grass/trunk/vector/v.out.svg/ grass6-svn].

: '''Author:''' Klaus Förster

==== v.points.cog ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.points.cog v.points.cog] is a shell script which will create a new point at the center of gravity of each cluster of input points or centroids, grouped by attribute. Among other things this is useful for labeling swarms of points.

: '''Author:''' Hamish Bowman

==== v.profile ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.profile v.profile] is vector map profiling tool similar to r.profile. This module will print out distance and attributes to points/lines along profiling line. It's also usefull to determine places where raster profile crosses vector features (i.e. where to place river marker on river walley crossection).

: '''Author:''' Maris Nartiss

==== v.random.cover ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.random.cover v.random.cover] is a shell script for creating random points constrained within an irregularly shaped vector area. (v.random places points only in current region rectangle). Optionally the user can upload raster values at the points. See also '<tt>r.random cover= vector_output=</tt>'

: '''Author:''' Hamish Bowman

==== v.rasterbounds ====

: [http://les-ejk.cz/programs v.rasterbounds] is a shell script for creating polygon-vector file of rasterfile boundaries. The best version of GRASS is 6.1+. If you are using GRASS < 6.1, you have to be in the same mapset as your raster maps are from.

: '''Author:''' Jachym Cepicky

==== v.rast.stats2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.rast.stats2 v.rast.stats2] is an adapted version of the GRASS module v.rast.stats. It uses the grass addon [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar.zonal r.univar.zonal] to speed up calculation of univariate statistics from a GRASS raster map based on vector polygons.

: '''Authors:''' Markus Neteler, Otto Dassau

==== v.sample.buffer [Currently unavailable. Being re-written in python. Target for inclusion in addons svn is January 2011]====
v.sample.buffer is a shell script that samples rasters in buffers of a specified size around features in a specified vector file. Sampling results are added as attributes to the vector file. This script was designed for sampling vegetation indices and DEM derived attributes for bird point counts. Sampling results can be one or more basic statistics such as mean, range, max, etc.

: '''Author:''' Trevor Wiens

==== v.select.region ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/v.select.region.tar.bz2 v.select.region] is a shell script that prints out the names of all vectors matching an input search pattern that has geometry (points, line, areas) that fall within a region bounded by an existing vector map, or within the current Grass region.

: '''Author:''' Eric Patton

==== v.selmany ====

: [http://svn.osgeo.org/grass/grass-addons/vector/v.selmany/v.selmany v.selmany] is a shell script that allows to interactively select a set of vector objects on a given layer, then assign them attribute values in a connected database table. The script runs on the command line prompt and within a graphic monitor ; it does not work with DBF driver.

: '''Author:''' Vincent Bain

==== v.surf.icw ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.surf.icw v.surf.icw] is an IDW interpolation method using true distance cost instead of euclidean shortest distance, i.e. ''as the fish swims around an island'' not ''as the bird flies''. This will cleanly travel around hard barriers and a cost surface map may be used to model expensive-cross barriers. Input data points do not need direct line of sight to be considered, but should be kept to less than one hundred as the module becomes very computationally expensive. A number of radial basis function options are available. ([http://grass.osgeo.org/wiki/Image:Inlets_03_SurfSal_icw_big.png screenshot])

: '''Author:''' Hamish Bowman

==== v.surf.idwpow ====

: [http://www.geospatial.it/allegri/grass/v.surf.idwpow.zip v.surf.idwpow] integrates the common v.surf.idw algorithm with the exponential parameter for the distance weights

: '''Author:''' Giovanni Allegri

==== v.surf.krige [deprecated: use v.autokrige instead] ====

: v.surf.krige is a script that do a surface interpolation from vector point data by Kriging method. The interpolated value of a cell is determined by using an omnidirectional variogram model fitted starting from model parameter given by user shown from the experimental semi variogram produced by v.variogram. The script can perform also the Leave-One-out cross validation to test the variogram model "fitted by eye" and an automatic fitted variogram model. The cross validation helps the user to choose the best variogram model to interpolate own data.

: '''Author:''' Pierluigi De Rosa.

==== v.strahler ====

: [http://www.pois.org/florian/downloads/grass/v.strahler.tgz v.strahler] is a module that calculates the Strahler Order for all lines of a given dendritic network.

: '''Author:''' Florian Kindl. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.strahler

==== v.swathwidth ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.swathwidth v.swathwidth] creates a vector map representing the sea bottom coverage of a multibeam (swath) sonar survey.
: ([http://david.p.finlayson.googlepages.com/swathwidth Screenshots])

: '''Authors:''' David Finlayson, Hamish Bowman

==== v.thickness ====

: [http://marcin.slodkowski.googlepages.com/v.thickness.tgz v.thickness] creates points of thickness vectors from the vectors of strike and dip angles.The v.thickness is GUI GRASS script for v.dip.

: '''Author:''' Marcin Slodkowski

==== v.transect.kia ====

: [https://svn.osgeo.org/grass/grass-addons/vector/v.transect.kia v.transect.kia] calculates kilometric abundance indexes (KIA), a common indirect presence index used in wildlife monitoring along line transect surveys.
: Path lenghts can be corrected by draping on a DEM, different type of point objects can be weighted according to their relative importance, and paths can be segmented using a further polygon vector (to calculate, say, abundances per elevation range or per habitat class).
: The module is written in bash and needs a GRASS install compiled with sqlite support.

: '''Author:''' Clara Tattoni and Damiano G. Preatoni

==== v.trees3d ====

: [http://les-ejk.cz/programs/ v.trees3d] is a module for making 3D trees from input vector point file.

: '''Author:''' Jachym Cepicky

==== v.trimesh ====
: [http://www.valledemexico.ambitiouslemon.com/vtrimesh.html v.trimesh] creates a triangular mesh from a vector map using areal constraints for refinement. It uses Jonathan Shewchuk's Triangle library.

: '''Author:''' Jaime Carrera

==== v.what.rast.buffer ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.what.rast.buffer v.what.rast.buffer] is a script that calculates univariate statistics of raster map(s) from buffers around vector points. Results are written to a file. Resolution is taken from each input map.
: ''see also the [http://starspan.casil.ucdavis.edu StarSpan] software

: '''Author:''' Hamish Bowman

==== v.variogram [deprecated: use v.autokrige instead] ====

: v.variogram is a script that create an omnidirectional experimental semi-variogram. This scripts require R-statistics software installed on your machine. Now the script is updated to run on spgrass6 >= 0.3 and sp >= 0.9 [http://grass.osgeo.org/pipermail/statsgrass/2006-October/000455.html reply].

: '''Author:''' Ivan Marchesini, Pierluigi De Rosa.

==== v.vect.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.vect.stats v.vect.stats] counts the number of points falling into each polygon and optionally calculates statistics from numeric point attributes for each polygon. v.vect.stats is a C module and works with GRASS 6.4 and higher (see enclosed patches for 6.5 and 7.0).

: '''Author:''' Markus Metz

==== AniMove ====

: [http://www.faunalia.it/animov/ AniMove] is software for analysis of animal movement and ranging behaviour using QGIS+GRASS+R.

:'''Authors:''' Support by Faunalia.it

==== Utilities ====

===== Shapemerge =====

: [http://perrygeo.googlecode.com/svn/trunk/gis-bin/shpmerge.sh shpmerge] merges all the shapefiles in the current directory into a single output shapefile

:'''Authors:''' Perrygeo

=== Raster add-ons ===

See also

svn co <nowiki>https://svn.osgeo.org/grass/grass-addons/raster</nowiki>

==== Raplat ====

GRASS-RaPlaT: The Radio Planning Tool for GRASS GIS system developed by support of Slovenian largest mobile operator Mobitel. It is especially designed for radio coverage calculation of GSM/UMTS systems, but can be applied also to other wireless systems in the frequency range 400 MHz – 2.4 GHz (e.g. TETRA, WiFi). Its structure is modular and characterized by high level of flexibility and adaptability.

* Documentation: http://commsys.ijs.si/en/component/content/article/54-software/149-user-manual
* Software: http://commsys.ijs.si/en/software/grass-raplat

: '''Author:''' Department of Communication Systems, Jozef Stefan Institue, Jamova 39, SI-1000 Ljubljana, Slovenia

==== r.area ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.area r.area] Very simple module. Calculate area size (in cells) for every individual category in input raster map and write number of cells as the value of each cell in the area. Optionally write a binary coverage map and set a minimum area threshold. Works well with {{cmd|r.clump}}.

: '''Author:''' Jarek Jasiewicz

==== r.basin ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.basin/ r.basin] Generates the main morphometric parameters of the basin starting from the digital elevation model and the coordinates of the basin's closing section.

: '''Author:''' Margherita Di Leo, Massimo Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.basin/

==== r.bilateral ====

: [http://les-ejk.cz/files/programs/grass/r.bilateral.tgz r.bilateral] Bilateral filter is an edge-preserving filter, which combines domain and range filtering. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.broscoe ====

r.broscoe.sh calculates waerden test and t test statistics for some values of threshold area on a single basin, according to A.J.Broscoe theory (1959).
See v.strahler package

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.strahler/

==== r.boxcount ====

: r.boxcount and r.boxcount.sh calculate the fractal dimension for a given map. These are versions for grass6 of [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake's modules] for grass43.

: '''Authors:''' Mark Lake, grass6 port: Florian Kindl.

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount/
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount.sh/

==== r.burn.frict ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.burn.frict r.burn.frict] converts vector geometries to raster cells, using a simple anti-aliasing method to close "gaps" between diagonal cells. Useful for "burning" vector geometries into a friction surface, making sure that simulated movement does not "slip" through converted cells that have only diagonal neighbours.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.burn.frict

==== r.clump2 ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.clump2 r.clump2] is a C module similar to r.clump. Differences are: diagonally adjacent cells are also clumped but can be excluded, NULL (nodata) cells are always excluded, and selective clumping with start coordinates is supported.

: '''Author:''' Markus Metz

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.clump2

==== r.colors.out_vtk ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.out_vtk r.colors.out_vtk] is a shell script used to export the color table associated with a raster map layer to a {{wikipedia|VTK}} XML file. (see also [[Help with 3D]])

: '''Author:''' Hamish Bowman

==== r.colors.quantiles ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.quantiles/r.colors.quantiles r.colors.quantiles] is a shell script used to create raster colors rules based on nquantiles. It uses R and spgrass6 package (RGRASS).

: '''Authors:''' Mathieu Grelier

==== r.colors.stddev ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.colors.stddev] ''moved into main archive''

==== r.convergence ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.convergence r.convergence] calculate topographic convergence index, useful to detect lineamets represented by chanell/ridge system

: '''Author:''' Jarek Jasiewicz

==== r.cpt2grass ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.cpt2grass] is a GRASS script for importing a [http://www.soest.hawaii.edu/gmt/ GMT] .cpt color table into GRASS. It can save to a text file suitable for r.colors or automatically apply the color table to a raster map. For a large collection of GMT .cpt files see http://sview01.wiredworkplace.net/pub/cpt-city/
: Other palette ideas from [http://geography.uoregon.edu/datagraphics/color_scales.htm Univ. Oregon] and [http://oceancolor.gsfc.nasa.gov/PRODUCTS/colorbars.html NASA/Goddard's OceanColor] (latter partially translated for use with GRASS on the [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.tools/palettes grass-addons SVN]).

: '''Author:''' Hamish Bowman

==== r.csr ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.csr r.csr] integrates several Grass programs to produce colored, shaded-relief rasters in one step. Accepts single or multiple elevation/bathymetry maps as input; optionally will fill data holidays with 3x3 median filter, multiple times, if required; can apply color maps from a) input raster, b) another raster in MAPSET, or c) from a rules file; otherwise, rainbow colorbar is applied. Output colored, shaded-relief rasters can optionally be exported to tiff format if the appropriate flag is given. Shading parameters can be modified, though useful defaults are given.

: '''Author:''' Eric Patton

==== r.cva ====

: [http://www.ucl.ac.uk/~tcrnmar/GIS/r.cva.html r.cva] is a cumulative viewshed analysis module. It is an advanced version of the {{cmd|r.los}} program.

: '''Author:''' [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake]

==== r.denoise ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.denoise r.denoise] denoises (smooths/despeckles) topographic data, particular DEMs derived from radar data (including SRTM), using Xianfang Sun's [http://www.cs.cf.ac.uk/meshfiltering/index_files/Page342.htm denoising algorithm]. It is designed to preserve sharp edges and to denoise with minimal changes to the original data. See the [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise/r.denoise.html manual pages] for details. Further information on Sun's denoising algorithm, including an example, is available [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise here].

: '''Author:''' John Stevenson

==== r.dominant_dir.m and r.calc_terraflow_dir.m ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.terraflow.tools dominant_dir.m and calc_terraflow_dir.m] are two Matlab scripts for determining the dominant flow direction from a r.terraflow MFD map and converting into a GRASS aspect map for use with d.rast.arrow, etc.

: '''Author:''' Hamish Bowman

==== r.diversity ====
: [http://svn.osgeo.org/grass/grass-addons/raster/r.diversity/ r.diversity] calculates selected diversity indices by calling various r.li commands.This script uses the [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.pielou.html Pielou], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.renyi.html Renyi], [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.shannon.html Shannon] and [http://grass.osgeo.org/grass64/manuals/html64_user/r.li.simpson.html Simpson] indices. The output is a map for each index.

: '''Author:''' Luca Delucchi, Duccio Rocchini

==== r.eucdist ====

: [http://david.p.finlayson.googlepages.com/r.eucdist r.eucdist] creates a raster map estimating the euclidean distance from known cells.

: '''Author:''' David Finlayson

==== r.fragment ====

: [http://www.chrisgarstin.com/stuff/r.fragment r.fragment] fragments a raster into a user-defined set of smaller tiles according to an input number of rows and columns.
: '''Author:''' Eric Patton

==== r.fuzzy ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy r.fuzzy] Calculates membership of every cell in raster according membership function defined by user.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.logic ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy.logic r.fuzzy.logic] Perform fuzzy operators (AND, OR, NOT, IMP) on membership's map using T-norms and T-conorms for 6 most popular families.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.system ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy.system r.fuzzy.system] Perform full fuzzy clasificationwith 6 most popular fuzzy logic families and few methods of deffuzification.
: '''Author:''' Jarek Jasiewicz

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.fuzzy.system

==== r.game_of_life ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.game_of_life r.game_of_life] is a shell script which runs Conway's classic Game of Life using GRASS raster modules. It is meant to demonstrate how easy it is to program cellular automata in GRASS as well as various 3D raster volume and time series visualization techniques.

: '''Author:''' Hamish Bowman

==== r.gauss ====

: [http://www.les-ejk.cz/files/programs/grass/r.gauss.tgz r.gauss] is Gaussian and Laplacian of Gaussian filter for GRASS. It is written in C language.

:'''Author:''' Jachym Cepicky

==== r.gradgrid4 ====

: [http://www.uibk.ac.at/geographie/personal/mergili/gradgrid4.zip gradgrid4] is a tool for interpolating values of discrete data points to a raster map, applying a local regression approach with a predictor raster. The model is based on shell and python scripts as well as an R batchfile. It was tested on Fedora Core 6 with GRASS 6.2.1 and R 2.5.1, but should work under most UNIX systems. After unzipping the gradgrid4 folder, store it at any place in your local file system. In the subfolder docs you can find a manual and a publication draft with a detailed description of the concept and the example of an application. The subfolder testloc constitutes a GRASS location with test data.

: '''Author:''' Martin Mergili

==== r.hazard.flood ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.hazard.flood/ r.hazard.flood] is an implementation of a fast procedure to detect flood prone areas. The exposure to flooding may be delineated by adopting a topographic index (TIm) computed from a DEM. The portion of a basin exposed to flood inundation is generally characterized by a TIm higher than a given threshold, tau. The threshold is automatically determinated from the cellsize. The proposed procedure may help in the delineation of flood prone areas especially in basins with marked topography. The use of the modified topographic index should not be considered as an alternative to standard hydrological-hydraulic simulations for flood mapping, but it may represent a useful and rapid tool for a preliminary delineation of flooding areas in ungauged basins and in areas where expensive and time consuming hydrological-hydraulic simulations are not affordable or economically convenient.

: '''Author:''' Margherita Di Leo

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.hazard.flood/

==== r.in.mb ====

: [http://blogs.tekmap.ns.ca/archives/458 r.in.mb] is a "GRASS/[[MB-System]] program designed to import ''mbio'' compatible multibeam sonar data directly into the GRASS GIS. The program is a modified version of {{cmd|r.in.xyz}}. Instead of reading an ASCII XYZ file, ''r.in.mb'' reads an MB-System compatible list file." It can do automatic reprojection and minor hole filling. The default is to import bathymetry data, but optionally amplitude or sidescan sonar data can be loaded instead.

: '''Author:''' Bob Covill

==== r.in.onearth ====

: [http://www-pool.math.tu-berlin.de/~soeren/grass/modules/ r.in.onearth] for download and import satellite images direct from the NASA onearth WMS server into GRASS.

: '''Author:''' Soeren Gebbert

==== r.in.swisstopo ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.in.swisstopo/ r.in.swisstopo] for importing swisstopo digital elevation model data into GRASS raster maps.

: '''Author:''' Jürgen Hansmann

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.in.swisstopo/

==== r.in.wms (.py) ====

: [http://les-ejk.cz/files/programs/grass/r.in.wms.tgz r.in.wms] for download and import maps direct from WMS servers into GRASS. This script is written in Python Programming language. Note GRASS 6.2+ provides a shell script version of r.in.wms, take care of which one is actually being run.

: '''Author:''' Jachym Cepicky

==== r.inund.fluv ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.inund.fluv/ r.inund.fluv]This command allows to obtain a fluvial potentially inundation map given a high-resolution DTM of the area surrounding the river and a water surface profile calculated through an 1-D hydrodinamic model.

: '''Authors:''' Roberto Marzocchi, Bianca Federici, Domenico Sguerso

==== r.isoregions ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.isoregions/r.isoregions r.isoregions] allows isoregions creation from a GRASS raster map.

: '''Authors:''' Mathieu Grelier

==== r.interp.mask ====

: [http://david.p.finlayson.googlepages.com/r.interp.mask r.interp.mask] Creates a user-specified buffer around interpolation points that can be used as a MASK to prevent or clip excessive extrapolation artifacts. This works much better than a standard convex hull around the points.

: '''Author:''' David Finlayson

==== r.ipso ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.ipso/ r.ipso] Produces the ipsometric and ipsographic curve related to a digital elevation model and prints the percentiles

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.ipso/

==== r.li ====

: [http://www.faunalia.it/download/r_li/ r.li] is a more flexible and faster replacement of the old r.le. '''''Moved into 6.3-SVN'''''.

: '''Authors:''' Claudio Porta, Davide Spano, Serena Pallecchi, [http://www.faunalia.it Faunalia]

==== r.local_max.pl ====

: [http://les-ejk.cz/files/programs/local_max.pl Local maxima] is a Perl script for <code>r.mapcalc</code>. It detects local maxima of the image.

: '''Author:''' Jachym Cepicky

==== r.mandelbrot ====

: [http://grasslab.gisix.com/scripts/r.mandelbrot r.mandelbrot] is a shell script to calculate the Mandelbrot set.- for GRASS versions 6.X.

: '''Author:''' Peter Löwe

==== r.maxent.lambdas ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.maxent.lambdas r.maxent.lambdas] is a shell script to compute raw and/or logistic prediction maps from a lambdas file produced with MaxEnt 3.3.3e.)] See also [[#r.out.maxent_swd]]

: '''Author:''' Stefan Blumentrath, [http://www.nina.no NINA]

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.maxent.lambdas/

==== mcda====

: mcda suite is a toolset for geographics multi-criteria decision aiding and data analysis based on ELECTRE (r.mcda.electre), REGIME (r.mcda.regime) and FUZZY (r.mcda.fuzzy) algorithm. The module r.roughset is also included for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/

==== r.mlv ====

: [http://les-ejk.cz/files/programs/grass/r.mlv.tgz r.mlv] is Mean of least variance filter for GRASS. It is an edge-preserving (or even edge-enhacing) filter, which should serve for removing additive noise from images. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.obstruction, r.planning.static, r.planning.cinematic ====

: [http://www.ing.unitn.it/~grass/software.html r.obstruction, r.planning.static, r.planning.cinematic]: r.obstruction creates a polar obstruction map from a DTM. r.planning.static performs a static planning for GPS and Glonass surveys using the obstruction map created with r.obstruction. r.planning.cinematic performs a cinematic planning for GPS and Glonass surveys. (University of Trento, Faculty of Engineering)

: '''Author:''' Daniele Carli, Dimitri D'Inca', Gianluca Fruet, Domenico Sguerso, Paolo Zatelli

==== r.out.jpeg ====

: [http://www.geospatial.it/allegri/grass/r.out.jpeg_ r.out.jpeg] is a simple GRASS script to export georeferenced JPEG images from rasters, keeping the associated color table. It is a two-step export: first a ppm file is created, then it is converted to jpeg usgin the "convert" command from ImageMagick

: '''Author:''' Giovanni Allegri

==== r.out.geoserver ====

: [http://www.wgug.org/index.php?option=com_content&view=article&id=56&Itemid=9 r.out.geoserver] exports GRASS raster layer to [http://geoserver.org GeoServer] and publishes it using WMS. The modul is a shell script. It uses: r.out.gdal, curl, xmlstarlet and GeoServer REST interface.

: '''Author:''' Pawel Netzel

==== r.out.gmap ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmap r.out.gmap] outputs GRASS raster map into set of image tiles
following the tiling scheme of Google Maps and Microsoft Virtual Earth. Read more in the OSGeo Journal [http://www.osgeo.org/journal Volume 5 (2009, to appear)] see also [[#r.out.kml|r.out.kml]] and [[#v.out.kml|v.out.kml]]

: '''Author:''' Tomas Cebecauer

==== r.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt r.out.gmt] is a GRASS script for exporting a GRASS raster map into a [http://www.soest.hawaii.edu/gmt/ GMT] grid file. It also creates a GMT color table from the data and can generate some GMT commands for plotting a postscript file. (code is experimental, but functional) see also http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview

: '''Authors:''' Hamish Bowman, Dylan Beaudette

==== r.out.gmt2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt2 r.out.gmt2] is a modified version of Hamish's r.out.gmt. Added options for title, xlabel, ylabel, comment, and map width. Removed any settings that can be changed by gmtset for more flexibility.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== r.out.kap_template ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.kap_template r.out.kap_template] is a shell script that exports a raster map into a GeoTiff and a metadata text file suitable for use with KAP (BSB) raster nautical chart converter programs such as <tt>tif2bsb</tt> (after verifying that you are legally entitled to use such a tool).
: '''''This is EXPERIMENTAL software. NOT FOR NAVIGATIONAL USE.'''''
: For an easy to use data viewer, see also the [http://www.opencpn.org OpenCPN] free navigational software.

: '''Author:''' Hamish Bowman

==== r.out.kml ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.kml r.out.kml] is a shell script that exports a raster map into a KML file and image for Google Earth or Worldwind. See also [[#v.out.kml|v.out.kml]] and [[#r.out.gmap|r.out.gmap]].

: '''Author:''' Hamish Bowman

==== r.pack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.pack r.pack] and [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.unpack r.unpack] are two GRASS scripts for transferring raster maps to another computer as a single compressed file including color table etc.
: An earlier version has been renamed as [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.pack/experiment r.pack.mat] and [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.unpack/experiment r.unpack.mat].

: '''Author:''' Hamish Bowman

==== r.pi ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.pi/ r.pi] (raster patch index) provides various functions to analyse spatial attributes of a landscape. It has a focus on patch-based indices but delivers class-based indices as well. r.le and its successor r.li provide landscape indices.

: '''Authors:''' Programming: Elshad Shirinov, Scientific concept: Dr. Martin Wegmann

==== r.prominence ====

: '''r.prominence''' calculates the average difference between a central cell and its neighbors. It approximated the terrain 'ruggedness' by looking at average differences in elevation within a given neighborhood.

: '''Author:''' Benjamin Ducke

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.prominence/

==== r.refine ====

: [http://www.bowdoin.edu/~ltoma/research.html r.refine]: reduces a DEM to a TIN (takes as input a grid DEM and an error margin and simplifies it to the desired accuracy into a TIN)
Available via the source code repository [https://github.com/jonrtodd/r.refine]
: '''Authors:''' Laura Toma and Jonathan Todd

==== r.rifs ====

: [http://www.ucl.ac.uk/~tcrnmar/ r.rifs]: r.rifs generates a raster map and/or image of a fractal by means of the specified random iterated function system.

: '''Author:''' Mark Lake

==== r.roughness ====

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.sh r.roughness.sh] is a shell script to calculate the surface roughness of a DEM, using r.surf.area and v.surf.rst. (for GRASS versions 6.1 and above)

[http://www.igc.usp.br/pessoais/guano/downloads/r.roughness60 r.roughness60] - for GRASS versions 6.0.X

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.area r.roughness.window.area] - calculate surface roughness as the ratio of real (surface) area and planar area, using a moving-window approach.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector r.roughness.window.vector] - calculate surface roughness as vector dispersion, using a moving-window approach. Resulting maps are: Vector Strength (R) and Inverted Fisher's k parameter.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector.html r.roughness.window.vector.html] - provisional help page for r.roughness.window.vector.

: '''Author:''' Carlos Henrique Grohmann

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.roughness/

==== r.roughset ====

: r.roughset is a module for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/r.roughset/

==== r.seg ====

: '''r.seg''' performs image segmentation and discontinuity detection (based on the Mumford-Shah variational model).
: The module generates a piece-wise smooth approximation of the input raster map and a raster map of the discontinuities of the output approximation. The discontinuities of the output approximation are preserved from being smoothed.
: See [http://www.ing.unitn.it/~vittia/sw here] for details and examples.

Available [http://www.ing.unitn.it/~vittia/sw here] and with improvements via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.seg/

: '''Author''' Alfonso Vitti

==== r.smoothpatch ====

: [http://david.p.finlayson.googlepages.com/r.smoothpatch r.smoothpatch] creates a composite of two rasters using a distance-weighted average across the transition to smooth the edges.

: '''Author:''' David Finlayson

==== r.soils.texture ====

: r.soils.texture is a module to define soils texture from sand and clay raster file with a schema text file (now FAO,USDA and ISSS are available). It is written in C language. - for GRASS versions 6.x - For bugs and suggest: g_massa@libero.it

:'''Author:''' Gianluca Massei

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.soils.texture/

==== r.stack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stack r.stack] is a shell script used to patch all the raster maps in a time series (or burst 3D raster) together into a vertical stack, to aid mutli-map analyses in modules where group input is not yet available.

: '''Author:''' Hamish Bowman

==== r.stream.angle ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.angle r.stream.angle] Divide stream network into stright line segments according users input. It extends Module uses as input direction and stream network map produced by r.watershed and stream.extract or custom user input. See description for details.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.angle

==== r.stream.basins ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.basins r.stream.basins] delineate basins according users input. It extends r.water.outlet funcionality to extracting more than one basin at one step. Module uses as input direction map produced stream network produced by r.stream.extract, r.watershed, r.stream order or custom user input. More in tutorial on grass-wiki pages.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.basins

==== r.stream.del ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.del r.stream.del] Calculates downslope length of first order streams and delete them if it length (in pixels) is lower than the treeshold. It also join false segments left by deletion into one with category of upper. It uses r.watershed direction map and r.watershed stream map as input. The module is added only for r.watershed module, r.stream.extract has deleting short streams build-in. During development of r.stream.* it will be probably abandoned due to duplicate functionality

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.del

==== r.stream.distance ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.distance r.stream.distance] Calculates downslope distance and downslope elevation difference between current cell and stream or outlet cells. It uses r.watershed direction map, r.watershed or r.stream.extract stream map and optionally DEM as input.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.distance

==== r.stream.extract ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.extract r.stream.extract] extracts topologically clean stream networks from input elevation and optionally accumulation maps. Output is available as raster and vector and can be used as input for the other r.stream.* modules by Jarek Jasiewicz.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.extract

==== r.stream.order ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.order r.stream.order] orders stream network outputed by r.watershed or r.stream.extract according Sthrahler, Shreve, Horton and Hack ordering systems. It require as input stream and direction map and optionally accumulation map. It handle both SFD nad MFD modes but all data must come from the same procedure.

: '''Author:''' Jarek Jasiewicz, Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.order

==== r.stream.pos ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.pos r.stream.pos] Helper module for calculating local stream network properties and linear geostatistics. Mostly To use with R and other grass modules.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.pos

==== r.stream.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.stats r.stream.stats] calculate Hortonian statistics for Stahler or Horton stream network created by r.stream.order. It uses r.watershed direction map, DEM and r.stream.order's Stahler or Horton stream network as input. It outputs calculated statistics to standard output.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.stats

==== r.surf.nnbathy ====

: [http://www.sieczka.org/programy_en.html r.surf.nnbathy] interpolates a surface from a raster input using Pavel Sakov's [http://code.google.com/p/nn-c/ nn] natural neighbor interpolation library. Provides triangulation, Sibson natural neighbor interpolation and non-Sibsonian interpolation.

: '''Author:''' Maciej Sieczka

==== r.surf.volcano ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.surf.volcano r.surf.volcano] creates an artificial surface resembling a seamount or cone volcano. The user can alter the size and shape of the mountain and optionally roughen its surface. Available decay functions are polynomial, Gaussian, Lorentzian, logarithmic, and exponential.

: '''Author:''' Hamish Bowman

==== r.terracost ====

[http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. '''Lead author''': Laura Toma

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==== r.tileset ====

: ''{{cmd|r.tileset}} moved into main archive''

==== r.traveltime ====

: [http://jesbergwetter.twoday.net/stories/4845555/ r.traveltime] computes the travel time of surface runoff to an outlet. The program starts at the basin outlet and calculates the travel time at each raster cell recursively. A drainage area related threhold considers even surface and also channel runoff. Travel times are derived by assuming kinematic wave approximation. The results can be used to derive a time-area function. This might be usefull for precipitation-runoff calculations (estimation of flood predictions) with a lumped hydrologic model (user-specified unit hydrograph).

: '''Author:''' Kristian Förster

==== r.univar.zonal ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar.zonal r.univar.zonal] is similar to r.univar, but calculates statistics separately for each category(zone) present in the separate input map used to define zones (zonal statistics). The output can be like the one of r.univar or in easier to read table format and can be written to a file. This addon is only needed for GRASS 6.4, its functionality has been added to r.univar in 6.5 and 7.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.univar.zonal

==== r.viewshed ====

: r.viewshed is a module for extremely fast line of sight analysis (replaces the slow r.los). It is written in C language for GRASS versions 6.X/7.x.

: '''Author:''' Laura Toma, USA

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.viewshed

Once {{trac|390}} is solved, it will substitute r.los.

==== r.wavelets ====

: [http://www.ing.unitn.it/~grass/software.html r.wavelets]: This package contains wavelets decomposition and reconstruction modules for the GRASS GIS: r.owave.dec computes the orthogonal wavelet transform of a raster map. r.owave.rec reconstructs a raster map from an orthogonal wavelet transform. r.biowave.dec computes the biorthogonal wavelet transform of a raster map. r.biowave.rec reconstructs a raster map from a biorthogonal wavelet transform.

: '''Authors:''' Members of the University of Trento, Faculty of Engineering

==== r.wf ====

: [http://svn.osgeo.org/grass/grass-addons/raster/r.wf/ r.wf] produces the Width Function of a basin. The Width Function W(x) gives the number of the cells in a basin at a flow distance x from the outlet (it is also referred as distance-area function). The distance is not the euclidean one, but it is measured along the flowpath towards the outlet.

: '''Authors:''' Margherita Di Leo, Massimo Di Stefano, Francesco Di Stefano

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.wf/

==== r.xtent ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.xtent r.xtent] computes a raster map layer representing the Voronoi diagram, weighted Voronoi diagram or a more complex territorial partitioning of space around points (centers) in a vector input map, based on the XTENT formula.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.xtent

==== r.zc.pl ====

: [http://les-ejk.cz/files/programs/zc.pl Zero crossing] is a simple Perl script, finds the ,,zero crossings`` from the Laplacian of Gaussian filter (see above). It is really very simple, the edges don't need to be really on that pixel, where they are detected, no interpolation is performed.

: '''Author:''' Jachym Cepicky

==== GIPE ====

: The GRASS Image Processing Environment (GIPE) has USLE, Energy-balance and radiance-reflectance correction models.

: '''Author:''' Yann Chemin (unless specified otherwise).

svn co https://svn.osgeo.org/grass/grass-addons/imagery/gipe

Remark: This is progressively moved to main GRASS SVN (aka GRASS 7)

:* r.hydro.CASC2D, ported from GRASS 5.x version, is temporarily here waiting to return to main GRASS.

:* r.soiltex2prop creates porosity, Saturated Hydraulic conductivity (Ksat) and wetting front pressure head (Hf) from percentage of sand and clay after Rawls et al., 1990. This is a must for r.hydro.CASC2D.

:* i.biomass creates biomass growth map from fPAR, lightuse efficiency, water availability (or evap.fraction), Lat, doy and tsw.

:* i.dn2ref.l7, r.dn2ref.ast create top of atmosphere reflectance for Landsat 7ETM+ and ASTER. These modules also have a flag for radiance output. Updated i.dn2ref.l7 to read .met calibration file.

:* i.dn2full.l[5,7] is an attempt to get all bands of Landsat[5,7] calibrated and corrected to either reflectance or temperature, reads only the .met file.

:* i.dn2potrad.l[5,7] is an attempt to get ET potential from DN of Landsat 7 (Careful! No Atmospheric correction!).

:* i.eb.* are a set of 10+ GRASS modules that together perform the main functions of the SEBAL model (Bastiaanssen, 1995). Those functions include (but are not limited to) Soil heat flux, sensible heat flux, net radiation, evaporative fraction at satellite overpass, diurnal actual evapotranspiration, momentum roughness length, etc. These modules are also part of any Energy-Balance related processing.

:* i.evapo.potrad creates diurnal Potential evapotranspiration assuming all net radiation becomes ET, according to SEBAL model (Bastiaanssen, 1995). This module also has a flag for diurnal net radiation as required by SEBAL in i.eb.eta.

:* i.evapo.SENAY creates actual evapotranspiration following the regional method of Senay (2007).

:* i.lmf creates a Local Maximum Fitting on the temporal dimension of the multi-date input dataset, working, but more precision still to be added.

:* i.vi.mpi is the mpi version of i.vi for cluster GRASS GIS education (no speed up here!) '''Author:''' Shamim Akhter

:* i.modis.stateqa extracts State Quality Assessment information from Modis 500m (MOD09A) products.

:* i.water creates a Water Mask from NDVI and Albedo, or specifically for Modis: NDVI and Band 7.

:* i.wi creates a given Water Index (only one so far).

==== HydroFOSS ====

: HydroFOSS - a GIS embedded approach for Free & Open Source Hydrological modeling.

: '''Author:''' Massimiliano Cannata

svn co https://svn.osgeo.org/grass/grass-addons/HydroFOSS/

==== Hikereport ====

: python script that computes length, cumulative uphill and downhill, average slopes on an interactively drawn path. Based on r.profile's output.

: '''Author:''' Stefano Negri

http://tracce.wordpress.com/?attachment_id=71

=== Misc add-ons===

==== m.eigensystem ====

m.eigensystem - Computes eigen values and eigen vectors for square matrices.

: http://svn.osgeo.org/grass/grass-addons/misc/m.eigensystem/

: '''Author:''' Michael Shapiro

===Database add-ons===
==== db.join ====

: Table joining: join one table into another through common attributes

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/database/db.join/
or
g.extension db.join

===General add-ons===

==== GRASS create location scripts ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/grass_create_location grass_create_location.sh] Script to generate a new GRASS location from GIS file (e.g. geoTIFF or SHAPE), wktfile or EPSG code.

: '''Author:''' Markus Neteler

==== g.laptop.sh ====

: [http://www.gbd-consult.de/dassau/grass/g.laptop/g.laptop.sh g.laptop.sh] is an interactive shell script to extract raster and vector data from current Location into a new one. Data can be copied or extracted in current or original resolution and region extend. This script was written to extract smaller parts of a GRASS location to be able to present them on a laptop without the necessity to transfer huge data. Maps do not have to be in the same mapset.

: '''Author:''' Otto Dassau

==== Readline completion ====

: '''''Readline completion''''' for GRASS commands under the bash shell: [http://www.sorokine.info/grass-complete/ grass-complete] won't clutter the environment but needs to be installed; [http://dcalvelo.free.fr/grass/grass_rlcompleter.sh grass_rlcompleter.sh] needs almost no installation but will pollute the environment. Grass-Complete currently requires Bash version 2.05 for proper install.

: '''Author:''' Alexandre Sorokine (grass-complete), Daniel Calvelo (grass_rlcompleter.sh)

==== g.region.point ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.region.point g.region.point] is a shell script which resets the computational region to a square box around a given coordinate. It is intended for use within GRASS scripts to speed up processing by limiting expensive raster calculations to a small area of interest.

: '''Author:''' Hamish Bowman

==== g.linke_by_day ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.sun.tools/ g.linke_by_day] is a python script for [[r.sun]] which interpolates a Linke turbidity value for a given day of the year based on monthly values edited into the script.

: '''Author:''' Hamish Bowman

==== g.xlist ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xlist g.xlist] is a C implementation of g.mlist. g.xlist searches for data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

==== g.xremove ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xremove g.xremove] is a C implementation of g.mremove. g.xremove removes data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

=== Imagery add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/imagery

==== GIPE ====

GIPE (see also above in raster section) provides:
i.biomass, i.dn2potrad.l5, i.dn2potrad.l7, i.dn2ref.ast, i.eb.deltat, i.eb.disp, i.eb.eta, i.eb.evapfr, i.eb.g0, i.eb.h0, i.eb.h_SEBAL01, i.eb.h_SEBAL95, i.eb.h_iter, i.eb.molength, i.eb.netrad, i.eb.psi, i.eb.rah, i.eb.rohair, i.eb.ublend, i.eb.ustar, i.eb.wetdrypix, i.eb.z0m, i.eb.z0m0, i.evapo.PT, i.evapo.TSA, i.evapo.potrad, i.evapo.senay, i.evapo.time_integration, i.lmf, i.modis.stateqa, i.sattime, i.vi.grid, i.vi.mpi, i.water, i.wi

svn co https://svn.osgeo.org/grass/grass-addons/gipe/

: '''Author:''' Yann Chemin

==== i.homography ====

Rectifies an image by computing a coordinate transformation for each pixel in the image based on the control points created by i.linespoints. The approach uses homography extended for corresponding lines.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.homography

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on code written by Stefano Merler, ITC-irst, Italy

==== i.linespoints ====

An imagery command that enables the user to mark coordinate system points as well as lines on an image to be rectified and then input the coordinates of each point for creation of a coordinate transformation matrix. The transformation matrix is needed as input for the GRASS program i.homography.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.linespoints

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on i.points

==== i.landsat.toar ====

Transform calibrated digital number of Landsat products to top-of-atmosphere radiance or top-of-atmosphere reflectance and temperature (band 6 of the sensors TM and ETM+). Optionally, used to calculate the at-surface radiance or reflectance with atmospheric correction (DOS method).

Available also in GRASS 7.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.toar

: '''Author:''' E. Jorge Tizado

==== i.landsat.acca ====

Implements the Automated Cloud-Cover Assessment (ACCA) Algorithm from Irish (2000) with the constant values for pass filter one from Irish et al. (2006). To do this, it needs Landsat band numbers 2, 3, 4, 5, and 6 (or band 61 for Landsat-7 ETM+) which have already been processed from DN into reflectance and band-6 temperature with i.landsat.toar).

Available also in GRASS 7.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.acca

: '''Author:''' E. Jorge Tizado

==== i.points.auto ====

This module allows a search of GCP's on two raster-maps with differents levels of automation. The ''manual'' search is the default search, so it's possible to determine the GCP's manually with the mouse (like {{cmd|i.points}}). ''Semiautomated'' search: The user determines with the mouse some correspondent areas (with a discrete precision) in the two maps and the module searches itself the GCP's in these areas. ''Automated'' search: At the start of module the user has to load the maps that the algorithm uses to the search, so it is recommended to use the maps filtered with the filters DIVERSITY or STDDEV (of GRASS) with a window of 3x3 or 5x5 pixels. However, the algorithm sometimes works well with the original maps too.

Note: This code is basically an improved i.points (from 2004). Subsequent changes in i.points haven's been ported here yet.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.points.auto

: '''Authors:''' based on i.points; additions by Ivan Michelazzi, Luca Miori (MSc theses at ITC-irst); Supervisors: Markus Neteler, Stefano Merler, ITC-irst 2003, 2004. [http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=37 PDF article]

==== i.points.reproj ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.points.reproj i.points.reproj] is a shell script that will use cs2cs to reproject the target coordinates of a group's POINTS file. By running i.rectify directly to the new target projection, a generation of resampling data loss can be avoided (versus i.rectify + r.proj). On the other hand, i.rectify does not calculate cell resolution well if the map is to be rotated ([http://intevation.de/rt/webrt?serial_num=3296 bug #3296]), in those cases i.rectify+r.proj may be the better option.

: '''Author:''' Hamish Bowman

==== i.plr.py ====

: [[I.plr.py|Probabilistic Label Relaxation]], written in Python

: '''Author:''' Georg Kaspar

==== i.pr ====

: Image classification: implements k-NN (multiclass), classification trees (multiclass), maximum likelihood (multiclass), Support Vector Machines (binary), bagging versions of all the base classifiers, AdaBoost for binary trees and support vector machines. It allows feature manipulation (normalization, principal components,...). It also implements feature selection techniques (RFE, E-RFE,...), statistical tests on variables, tools for resampling (cross-validation and bootstrap) and cost-sensitive techniques for trees and support vector machines.

: '''Author:''' Stefano Merler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.pr

==== i.spec.sam ====

: Spectral Angle mapping

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.sam/

==== i.spec.unmix ====

: Spectral unmixing

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.unmix/

==== i.topo.corr ====
: i.topo.corr is used to topographically correct reflectance from imagery files, e.g. obtained with i.landsat.toar (see above), using a sun illumination terrain model. This illumination model represents the cosine of the incident angle, i.e. the angle between the normal to the ground and the sun rays. It can be obtained with {{cmd|r.sun}} (parameter incidout), and then calculating its cosine with float precision. Correction methods: cosine, minnaert, percent, c-factor.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.topo.corr

: '''Author:''' E. Jorge Tizado

==== i.warp ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.warp i.warp] is a shell script that will use gdalwarp to rectify a raw input image using thin plate splines. The map should be imported into GRASS with r.in.gdal and GCPs set with i.points. Input is the raw image (GeoTIFF, JPEG, etc). Output is a GeoTIFF in the imagery group's target location's map projection. Requires a recent (early 2006) version of GRASS 6.1, or newer.

: '''Author:''' Hamish Bowman

=== Display add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/display

==== d.barb ====

[http://trac.osgeo.org/grass/browser/grass-addons/display/d.barb d.barb] is a C module that will draw wind barbs, straw plots, and arrow plots from raster array or sparse vector point data. It can use either direction + magnitude, or u + v components as the input, and can produce a legend key. (''work in progress, but it's mostly there'')

: '''Author:''' Hamish Bowman

==== d.edit.rast ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.edit.rast d.edit.rast] edits cells in an existing raster map displayed on the current monitor.

: '''Author:''' Huidae Cho

==== d.frame.quarter ====

: ('''obsolete''') [http://trac.osgeo.org/grass/browser/grass-addons/display/d.frame.split d.frame.quarter] is a shell script that will split the display into four quadrants (or sixths) using ''d.frame''. Individual frames are named ''uno, dos, tres, cuatro'', and ''full_screen''.
: Replaced by {{cmd|d.split.frame}} in main.

: '''Author:''' Hamish Bowman

==== d.frame.split ====

: ''d.frame.split moved into main archive as {{cmd|d.split.frame}}''

==== d.frontline ====

: [http://cloud.github.com/downloads/amuriy/GRASS-scripts/d.frontline d.frontline] is a shell script that draws frontlines on the graphics monitor using ''d.graph'' module and different types of symbols. Also it optionally saves frontline graphics to ''d.graph'' commands file and/or ''ps.map'' file (for later use with the "read" ''ps.map'' instruction)

: '''Author:''' Alexander Muriy

==== d.hyperlink ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/d.hyperlink.tar.bz2 d.hyperlink] is an interactive shell script that allows the viewing of hyperlinked images from a vector's attribute table in an external image viewer. Queries can be made via SQL statements or interactive mouse-clicking. The attribute table must be pre-populated with a column containing the image to link the vector to; the user also specifies the image folder in the current MAPSET where the images are located. The script currently supports gimp, Eye of Gnome, gthumb, gpdf, and Inkscape image viewers.

: '''Author: '''Eric Patton

==== d.mark ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.mark] is a shell script that quickly displays a marker on the display at a given coordinate.

: '''Author:''' Hamish Bowman

==== d.region.box ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.region.box d.region.box] is a shell script that quickly displays a box around the current region.

: '''Author:''' Hamish Bowman

==== d.stations ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.stations] is a shell script that quickly displays vector points (or sites for GRASS 5.4 and below).

: '''Author:''' Hamish Bowman

==== d.varea ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.varea] is a shell script that quickly displays vector areas.

: '''Author:''' Hamish Bowman

==== pd-GRASS ====

: [http://www.ornl.gov/sci/gist/software/grass/ pd-GRASS]: Parallel Display for GRASS GIS

: '''Author:''' Alex Sorokine

==== [[IconSymbols]] ====

* [[IconSymbols|Symbols]] which can be used with ''d.vect, d.graph'', and ''ps.map''.

=== Postscript add-ons ===

* ''See also [[ps.map scripts|ps.map samples and templates]]''.

==== ps.atlas ====

: [http://les-ejk.cz/programs/grass/ps.atlas ps.atlas] is a shell script that makes more maps on current region according to input *.psmap file. General map can be stored as vector file. The resulting *.eps maps can be automatically converted to *.pdf files.

: '''Author:''' Jachym Cepicky

==== ps.output ====

: [https://trac.osgeo.org/grass/browser/grass-addons/postscript/ps.output ps.output] is much like {{cmd|ps.map}} but with advanced decorations and ability for translucency. Here you can find a [[Ps.output|tutorial]].

: '''Author:''' Jorge Tizado

==== [[AreaFillPatterns]] ====

* Hatches for ps.map's vareas

=== wxGUI add-ons ===

===GRASS and UMN Mapserver===

* [http://www.mail-archive.com/mapserver-users@lists.umn.edu/msg00086.html See interesting posting]
* See wiki [[GRASS and MapServer]] page

==GRASS 5.x (old)==

===Vector add-ons===

* See here: http://grass.osgeo.org/download/addons.php

===Raster add-ons===

* See here: http://grass.osgeo.org/download/addons.php

* [http://www.valledemexico.ambitiouslemon.com/gwmodelling.html r.gmtg] The groundwater modelling tool for grass. A module to use MODFLOW within GRASS. '''Author''': Jaime Carrera

* [http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. For GRASS 5.3. '''Lead author''': Laura Toma
:Newer version available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==GRASS 4.x (very old)==

===Raster add-ons===

* MAGICAL Software: The MAGICAL software comprises a suite of three programs that provide a multi-agent simulation extension for the GRASS GIS software. http://www.ucl.ac.uk/~tcrnmar/simulation/magical/magical.html

[[Category:Community]]
[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]