GRASS-Wiki - User contributions [en]

Talk:Compile and Install Ubuntu

2014-03-04T18:23:10Z

⚠️Vesnikos: /* Dependencies */

==Current==

* Slowly improving appearance
* Aiming to split content in two pages--[[User:NikosA|Nikos]] 03:46, 29 December 2012 (PST)

Please

* '''add comments in this page''' and keep the wiki-page clean --[[User:NikosA|Nikos]] 13:40, 3 November 2012 (PDT)
* use time stamps when adding comments in _this_ page! --[[User:NikosA|Nikos]] 10:11, 1 April 2011 (PDT)
* in order to improve readability, for code blocks add
** <nowiki><source lang="bash">source code</source></nowiki>
** and <nowiki><source lang="bash" enclose="none">checkinstall</source></nowiki> for inline pieces of code --[[User:NikosA|Nikos]] 03:40, 29 December 2012 (PST)

== Dependencies ==

* Should libreadline5 and libreadline5-dev be changed to libreadline6 and libreadline6-dev for newer versions of Ubuntu?
** Probably yes. --[[User:NikosA|Nikos]] 13:37, 3 November 2012 (PDT)

* Comment removed from the wiki-page itself and copy-pasted here: ''(caveat: allegedly works for me - can someone please confirm? //Stefan )'' --[[User:NikosA|Nikos]] 13:37, 3 November 2012 (PDT)

* libhdf4g-run has been superseded in recent versions of Ubuntu. This should be noted in the article.

* Instead of specifically searching (dependency-)packages to be installed, '''sudo apt-get build-dep''' could be used. It seems it works for ''proj4'', ''geos'', ''gdal'', ''grass'' (tested on Kubuntu Maverick 64-bit). --[[User:NikosA|Nikos]] 10:09, 1 April 2011 (PDT)
**While using build-dep is a pain free way, I think there should be also a one liner that helps install all the depenencies; The motivation behind this is that I want to build graass against custom dependecies, and I don't want to polute my system with any vanilia libraries from the default repocitoy.[[User:Vesnikos|Vesnikos]] ([[User talk:Vesnikos|talk]]) 10:23, 4 March 2014 (PST)

== GDAL ==

* Option --with-sqlite is not recognised and should be deleted.

* Should libxerces-c-dev be made one of the dependencies? --with-xerces=yes returns a warning that library files are not found.

== checkinstall ==

Folks, please keep the instructions of installing by using checkinstall. It is a very good way to keep things "cleaner" when it comes to uninstall stuff. Instead of removing the instruction(s) for checkinstall, add the (traditional way) "make install" instruction.

Except if there is a good reason for not using checkinstall. If there is, please explain.--[[User:NikosA|Nikos]] 04:06, 24 November 2010 (PST)

Talk:Compile and Install Ubuntu

2014-03-04T18:20:10Z

⚠️Vesnikos: /* Dependencies */

==Current==

* Slowly improving appearance
* Aiming to split content in two pages--[[User:NikosA|Nikos]] 03:46, 29 December 2012 (PST)

Please

* '''add comments in this page''' and keep the wiki-page clean --[[User:NikosA|Nikos]] 13:40, 3 November 2012 (PDT)
* use time stamps when adding comments in _this_ page! --[[User:NikosA|Nikos]] 10:11, 1 April 2011 (PDT)
* in order to improve readability, for code blocks add
** <nowiki><source lang="bash">source code</source></nowiki>
** and <nowiki><source lang="bash" enclose="none">checkinstall</source></nowiki> for inline pieces of code --[[User:NikosA|Nikos]] 03:40, 29 December 2012 (PST)

== Dependencies ==

* Should libreadline5 and libreadline5-dev be changed to libreadline6 and libreadline6-dev for newer versions of Ubuntu?
** Probably yes. --[[User:NikosA|Nikos]] 13:37, 3 November 2012 (PDT)

* Comment removed from the wiki-page itself and copy-pasted here: ''(caveat: allegedly works for me - can someone please confirm? //Stefan )'' --[[User:NikosA|Nikos]] 13:37, 3 November 2012 (PDT)

* libhdf4g-run has been superseded in recent versions of Ubuntu. This should be noted in the article.

* Instead of specifically searching (dependency-)packages to be installed, '''sudo apt-get build-dep''' could be used. It seems it works for ''proj4'', ''geos'', ''gdal'', ''grass'' (tested on Kubuntu Maverick 64-bit). --[[User:NikosA|Nikos]] 10:09, 1 April 2011 (PDT)
**While using build-dep is a pain free way, I think there should be also a one liner that helps install all the depenencies; The motivation behind this is that I want to build graass against custom dependecies, and I don't want to polute my system with any vanilia libraries from the default repocitoy.

== GDAL ==

* Option --with-sqlite is not recognised and should be deleted.

* Should libxerces-c-dev be made one of the dependencies? --with-xerces=yes returns a warning that library files are not found.

== checkinstall ==

Folks, please keep the instructions of installing by using checkinstall. It is a very good way to keep things "cleaner" when it comes to uninstall stuff. Instead of removing the instruction(s) for checkinstall, add the (traditional way) "make install" instruction.

Except if there is a good reason for not using checkinstall. If there is, please explain.--[[User:NikosA|Nikos]] 04:06, 24 November 2010 (PST)

WxPython-based GUI for GRASS

2013-02-06T09:14:31Z

⚠️Vesnikos: /* Platform specific */ added windows 7 python values

Browse also wxGUI related [[:Category:WxGUI|articles or screenshots]].

See also [[GRASS GUI]], and [[GRASS and Python]].

For developer-related issues see [http://trac.osgeo.org/grass/wiki/wxGUIDevelopment Trac wxGUI page].

__TOC__

== Overview ==

* [http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.html Manual page]
* A nice summary of the progress to date, written by Jachym Cepicky:
** [http://www.les-ejk.cz/english/wxgrass-new-grass-gui-1 Part 1]
** [http://www.les-ejk.cz/english/wxgrass-new-grass-gui-2 Part 2]
* [[User:Landa|Martin Landa]]: [http://gama.fsv.cvut.cz/~landa/publications/2008/gis-ostrava-08/paper/landa-grass-gui-wxpython.pdf New GUI for GRASS GIS based on wxPython] ([http://gis2008.com/indexe.html GIS Ostrava 2008], January 27-30, 2008, Ostrava, Czech Republic)
* [[User:Landa|Martin Landa]], Cristina Moretto, Michele Zanolli, Luca Manganelli and Markus Neteler: [http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/paper/grass-gfoss-tn.pdf wxPython-based GUI for GRASS GIS] ([http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/prezentazione/perugia-grass-gui-wxpython.pdf presentation]) ([http://www.grassmeeting2008.unipg.it IX Meeting degli Utenti Italiani di GRASS - GFOSS], February 20-22, Perugia, Italy)

=== Requirements ===

* [http://svn.osgeo.org/grass/grass/trunk/gui/wxpython/README README]

=== Development ===

Do you want to help with the development?

* basic Python programming ability required
* GUI programming experience welcomed (especially wxPython)
* GRASS user (or better developer) experience

How to get [http://trac.osgeo.org/grass/wiki/HowToContribute write access] to the GRASS SVN repository.

See example of wxGUI module in trunk: {{src|doc/gui/wxpython/example/}}

== Screenshots ==

* See [[WxGUI Screenshots|Screenshots]] page
* [[:Category:WxGUI|Screenshots from GRASSWiki]]
* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/user-interface Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

== Video tutorials ==

* See [[wxGUI/Video tutorials|Video tutorials]] page

== Components ==

=== Core components ===

==== Layer Manager ====

'''Status:''' prototype implemented.

The '''GRASS GIS Layer Manager''' provides an interactive graphical interface to GRASS commands. The Layer Manager includes a set of pull-down menus for all GRASS GIS functions (analysis, file I/O, GIS configuration and management), toolbar that manage display map layers in map display windows, layer tree in which map layers to display are organized, command output window and integrated command line prompt.

<center>
<gallery perrow=2 widths=300 heights=200>
Image:wxgrass-gis-manager-layer.png|2007/12
Image:wxgrass-gis-manager-output.png|2007/12
Image:Wxgrass rgb.png|2008/02
Image:wxgui-layer-manager-70.png|2010/08
Image:wxgui-pyshell.png|2011/06 - Embedded interactive Python Shell
</gallery>
</center>

==== Import tool ====

The GUI offers a convenient tool for single map and bulk import:

* see [[Importing data]]

==== Map display window ====

'''Status:''' prototype implemented.

Each '''Map display window''' has a unique set of layers to display and region setting (zoom). The map display window includes main toolbar with basic tools including zooming, panning, data querying, simple analyse functions (measure, profile, histogram, etc.), overlay management, etc. From main toolbar are accessible additional toolbars, currently only Digitization tool is available. Under development is Georectification tool.

<center>
<gallery perrow=2 widths=300 heights=200>
Image:Wxgrass-mapdisplay-0.png
Image:Wxgui-mapdisplay-1.png
</gallery>
</center>

==== GUI dialogs ====

'''Status:''' prototype implemented.

Generated from XML using <tt>--interface-description</tt>.

E.g. <tt>d.rgb --help</tt>
<pre>
Description:
Displays three user-specified raster map layers as red, green, and blue overlays in the active graphics frame.

Keywords:
display

Usage:
d.rgb [-ox] red=name green=name blue=name [--verbose] [--quiet]

Flags:
-o Overlay (non-null values only)
-x Don't add to list of commands in monitor
--v Verbose module output
--q Quiet module output

Parameters:
red Name of raster map to be used for <red>
green Name of raster map to be used for <green>
blue Name of raster map to be used for <blue>
</pre>

becomes with <tt>d.rgb --interface-description</tt>

<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task SYSTEM "[http://trac.osgeo.org/grass/browser/grass/trunk/gui/xml/grass-interface.dtd grass-interface.dtd]">
<task name="d.rgb">
<description>
Displays three user-specified raster map layers as red, green, and blue overlays in the active graphics frame.
</description>
<keywords>
display
</keywords>
<parameter name="red" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <red>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<parameter name="green" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <green>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<parameter name="blue" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <blue>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<flag name="o">
<description>
Overlay (non-null values only)
</description>
</flag>
<flag name="x">
<description>
Don't add to list of commands in monitor
</description>
</flag>
<flag name="verbose">
<description>
Verbose module output
</description>
</flag>
<flag name="quiet">
<description>
Quiet module output
</description>
</flag>
</task>
</source>

which is then used to generate:

[[Image:wxgrass-d-rgb.png|center|600px]]

==== Startup GUI (welcome screen) ====

'''Status:''' prototype implemented.

Start new GRASS session with

grass -wxpython

[[Image:Wxgrass-startup.png|center|400px]]

==== Location wizard ====

'''Status:''' prototype implemented.

Wizard for creating new GRASS project location based on:

* Coordinate system
* EPSG code
* Georeferenced file
* PROJ.4 string
* XY

See also [[GRASS Location Wizard]].

[[Image:Wxgui-location-wizard.png|center|thumb|600px|Location wizard]]

=== Digitizer ===

==== Vector digitizer ====

'''Status:''' prototype implemented.

See also {{cmd|wxGUI.Vector_Digitizer|desc=manual page}}

See also [[GRASS Digitizing tool]] and [[wxGUI Vector Digitizer]].

Replacement of <tt>v.digit</tt> module integrated into Map display window ([http://svn.osgeo.org/grass/grass-promo/screenshots/wxpython/digitization Screenshots]).

<center>

<gallery perrow=2 widths=300 heights=200>
Image:WxDigit200804.png|Vector digitizer (2008/04)
Image:Digit-01.png|Vector digitizer (2007/11)
Image:WxGUI-vdigit-fill-area.png|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)
Image:WxGUI-vdigit-bg.png|Vector digitizer - background raster maps with different opacity level (2008/07)
Image:WxGUI-vdigit-win0.png|Vector digitizer on MS Windows (2011/01)
Image:Wxgui-vdigit-dupl.png|Vector digitizer - checking for duplicates (2011/02)
</gallery>

</center>

==== Raster digitizer ====

'''Status:''' development started in GRASS 7

* {{cmd|r.digit}} (merge with {{cmd|v.digit}}?)
: Probably write a front end for {{cmd|r.in.poly}}, that's all the old {{cmd|r.digit}} is.
* {{cmd|d.rast.edit}}
: Idea: get cell center coords and new values from GUI interaction, then pass those through {{cmd|r.in.xyz}}, and {{cmd|r.patch}} the new values over the top of the old map.
: Current status:

[[Image:D_rast_edit_grass7.png|center|thumb|500px|Raster map editor in GRASS 7]]

* merge with Georectifier? (i.points, i.vpoints)

===== Category Labels =====

* Write with new {{cmd|r.category}} import tool
** ''Back-end component complete: {{cmd|r.category}} module is now updated to handle a rules= file and other goodies like dynamic labels''

* Read with one of {{cmd|r.category}}, {{cmd|r.describe}}, {{cmd|r.report}}, {{cmd|r.stats}}, ???
** probably need to add a new flag to one of those to print flat <tt>"%d %s", cat, label</tt>
: or read the cats/ file directly, it's already flat ascii.

* how to deal with FP maps & cats?

=== Cartography tools ===

==== GUI for {{Cmd|ps.map}} ====

'''Status:''' under development (Anna Kratochvilova).

<center>
{|
|-
| [[Image:CartographicComposer.png|350px|thumb|Cartographic Composer: draft mode]]
| [[Image:CCPreview.png|350px|thumb|Cartographic Composer: preview]]
|-
|}
</center>

<center>More info at '''[[WxGUI Cartographic Composer]]'''.</center>

-----

==== Direct printing ====

'''Status:''' development not started yet.

Implement direct printing of map canvas content using GRASS PS driver or Cairo driver.

* [http://trac.gispython.org/projects/PCL/wiki Python Cartographic Lab]
* [http://wiki.osgeo.org/wiki/OSGeo_Cartographic_Library OSGeo Cartographic Library]
** http://lists.osgeo.org/pipermail/discuss/2008-April/003337.html
** http://www.intevation.de/pipermail/freegis-list/2007-April/003142.html
* [http://wiki.osgeo.org/wiki/OSGeo_map_symbol_set OSGeo Map Symbol Set]
* [http://www.gdal.org/ogr/ogr_feature_style.html OGR - Feature Style Specification]
* [http://trac.osgeo.org/mapguide/wiki/MapGuideRfc14 MapGuide RFC 14 - Cartographic Stylization Engine]

* [http://www.iho.shom.fr/PUBLICATIONS/download.htm#special S-52 standard for nautical chart (ENC) symbology] and cartography from the [http://www.iho.shom.fr/ International Hydrographic Bureau]
** [http://openev.cvs.sourceforge.net/openev/contrib/S52/ GPL library implementing the S-52 standard] (OpenEV)

* [http://www.opengeospatial.org/standards/symbol OpenGIS Symbology Encoding Implementation Specification]

* [http://geosysin.iict.ch/trac/wiki/Index4extJPAL PAL]

=== Georectifier ===

'''Status:''' prototype implemented.

<center>
{|
|-
| [[Image:Wxgui-georectify-0.png|thumb|350px|center|Georectifier (old interface)]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center|Georectifier (old interface)]]
|-
|}
</center>

[[Image:Georectifier berlin.png|thumb|Georectification of historical maps using a simplified OpenStreetmap reference (example Berlin) - new interface|450px|center]]

See also [[Georeferencing]].

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

<center>
{|
|-
| [[Image:Wxgui-profile-0.png|thumb|350px|center]] ||
[[Image:Wxgui-profile-1.png|thumb|350px|center]]
|-
|}
</center>

=== Attribute table manager ===

'''Status:''' prototype implemented.

See [[wxGUI Attribute Table Manager]] page and also {{cmd|wxGUI.Attribute_Table_Manager|desc=manual page}}.

[[Image:Grass-atm-example.png|center|thumb|640px|Attribute queries in wxGUI]]

=== 3D view mode ===

'''Status:''' prototype implemented (Google Summer of Code 2008/2010/2011).

See detailed information at [[wxNVIZ]] page and classic Tcl/Tk [[NVIZ]] pages.

[[Image:Wxnviz-volumes.png|640px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space.]]

=== Imagery tools ===

'''Status:''' (re)development not started in earnest yet. Some behind-the-scenes code has been prepared, but not much.
: ''Volunteers welcome!''

==== Ortho photos ====

'''Status:''' development not started yet.

* To replace {{cmd|i.ortho.photo}} and friends

==== wx.iclass ====

'''Status:''' prototype implemented.


* See [[wxIClass]] page

=== Graphical Modeller ===

'''Status:''' prototype implemented.

[[File:WxGUI-modeler-if-else-0.png|500px|center]]

See [[wxGUI Graphical Modeler]] page for more information.

=== Extension Manager ===

'''Status:''' prototype implemented

Settings | Addons extensions | Install extension from addons

{{YouTube|buxsHVHLDBI|desc=wxGUI Extension Manager}}

[[Image:wxgui-em.png|center|thumb|500px|wxGUI Extension Manager]]

=== Raster Calculator ===

'''Status:''' prototype implemented

[[Image:wxgui-mapcalc.png|center|thumb|500px|wxGUI Map Calculator]]

See also [[wxGUI/Video tutorials#Raster calculator|video tutorials]].

=== GRASS Catalog ===

'''Status:''' under development (in AddOns)

* [http://lsi.iiit.ac.in/grass_addons/ GRASS Catalog files]

<center>
{|
|-
| [[Image:GRASS Catalog1.png|350px|thumb|center|GRASS Catalog ]]
| [[Image:GRASS Catalog2.png|350px|thumb|center|GRASS Catalog]]
|-
|}
</center>

;Current Features:

* copy, delete, rename map layers (raster & vector) in current mapset.
* view raster & vector map layers from any location and any mapset.
* Provides a GUI wrapper for r.info & v.info grass commands while viewing map layers in mapwindow.
* Can connect with OssimPlanet using PlanetSasha
* Add and Remove maps from GRASS GIS to OssimPlanet(Send to OssimPlanet/Remove from OssimPlanet)

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Create a properties window to display Coordinate system & projection for each map
* ...

Alternative: http://code.google.com/p/wxgis/

=== r.li.setup GUI ===
'''Status:''' available as {{cmd|g.gui.rlisetup|version=70}}

Porting of {{cmd|r.li.setup}} in wxPython.
Some screenshots of developing version

<center>
<gallery perrow=2 widths=300 heights=200>
Image:Rlisetup_first_frame.png | The first windows where you can select existing configuration file or create new one
Image:Rlisetup wizard first page.png | First window of wizard
Image:Rlisetup wizard keybord sampling frame.png | Choose the sampling frame
Image:Rlisetup_wizard_sampling_areas.png ‎| Choose the type of sampling area
</gallery>
</center>

=== Help browser ===

'''Status:''' development not started yet.

For browsing manual pages is currently used web browser, the goal is to design integrated help system.
: HB: ''We used to have one of these for viewing the help pages of Tcl/Tk NVIZ. We dropped it because it was a pain to maintain and generally outside our core mission so a distraction.''

=== Map Swipe ===

'''Status:''' prototype implemented.

This tool enables you to compare two raster maps covering the same area (e.g. compare maps from different year).

;Current features:
* orientation of swipe line can be horizontal or vertical
* zooming works in the same way as in [[#Map_display_window | Map Display]]

See more '''examples''' and videos at [[WxGUI Map Swipe]] page.

[[Image:Tsunami japan2011 sendai.jpg|center|thumb|500px|wxGUI Map Swipe for disaster management: Tsunami Japan 2011]]

=== Animation Tool ===

'''Status:''' prototype implemented in GRASS 7.

Animation tool is a replacement for {{cmd|xganim}}. It allows to animate a series of GRASS raster maps or a space time raster dataset ([http://trac.osgeo.org/grass/wiki/Grass7/TemporalExtension see GRASS GIS temporal extension]).

[[Image:WxGUI animation tool.jpg|center|500px|wxGUI animation tool]]

;Current features:

* display up to 4 synchronized animations
* control the animation speed
* interactively change active frame using a slider
* visualize space time datasets with unequally spaced intervals
* animate 3d view (partially implemented)

Animation Tool can be launched from Layer Manager menu (File -> Animation Tool) or through command line ({{cmd|g.gui.animation|version=70}}).

{{YouTube|zVyTV1wF32M|desc=wxGUI Animation Tool}}
{{YouTube|oTQ963mC9JE|desc=wxGUI Animation Tool - both 2D and 3D view}}

=== Vector Network Analysis Tool ===

'''Status:''' prototype implemented.

See more examples and video at [[WxGUI Vector Network Analysis Tool]] page.

== Known issues ==

* See and report in trac: [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&component=wxGUI&order=priority List of open issues]

=== Platform specific ===

For the GUI to know what platform it's on, and therefore apply platform specific commands (e.g. append '.exe' to programs) it has to test what platform it is running on. Here we take the experimental approach to learning what's best to use. Please add or generalize this list as you can.

Platform information - start Python from the command line then issue

<source lang="python">
import sys
sys.platform

import os
os.name
os.environ['OS']

import platform
platform.system()
</source>

* Results:

{| border="1" class="wikitable" style="text-align:center"
! Platform
! sys.platform
! os.name
! os.environ['OS']
! platform.system()
|-
| 32bit GNU/Linux
| linux2
| posix
| ''n/a''
| Linux
|-
| 64bit GNU/Linux
| linux2
| posix
| ''n/a''
| Linux
|-
| 32bit Mac OSX (PowerPC G4)
| darwin
| posix
| ''n/a''
| Darwin
|-
| 64bit Mac OSX (Intel)
| [1] see note
| ?
| ?
| ?
|-
| 32bit MS Windows XP
| win32
| nt
| Windows_NT
| Windows
|-
| 64bit MS Windows Vista
| win32
| nt
| Windows_NT
| Windows
|-
| 32bit MS Windows XP (Cygwin)
| win32
| ?
| ?
| ?
|-
| 64bit MS Windows 7
| win32
| nt
| Windows_NT
| Windows
|-
|}

[1] On Fri, May 29, 2009 at 10:49 PM, William Kyngesburye wrote:
: ''Right now the GUI only runs 32bit, even if the rest of GRASS is 64bit, because it's not yet possible for wxPython to be 64bit. It comes out the same as PPC 32bit - no distinction between ppc/intel or 32/64 bit, it's all darwin. (yes, I checked, and I have a custom 64bit python executable to verify)''

== General GUI Design ==

=== Layout ===

For some users, the current approach of separate windows (SDI) leads to a windows flooding. Especially on large monitors or dual screen systems catching the wxGUI windows can be tedious when they appear on separate monitors (depends on windows manager, the much used KDE scatters typically the wxGUI windows all over the screen real estate). Almost each task generates a new wxGUI window which is freely floating around on the screen: [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-03.png example 1] and [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-01.png example 2]. On a dual-screen this may sum up to 50cm of distance!

'''Proposed solutions:'''
* implement ''optional'' layout similar to QGIS (with a legend attached to each display) or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of the layer manager and display windows to keep the windows closer
* do not allow module windows to stay open. That is, get rid of the apply button and force each window to close when OK is pressed (QGIS/ArcGIS approach). This leaves only the display(s) and single legend/layer manager on desktop.
* If you otherwise wish to continue using your current WM, file a bug report with them asking for better multi-head support and get the problem fixed at the source. (there probably already is a bug filed with tips in it)

<center>
{|
|-
| [[Image:Wxgui_current.png|350px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|350px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
|-
|}
</center>

'''New solution: see [[WxGUI#Data_Catalog]] above.'''

====What others do====

'''SDI: (each document opened in application occupies a window on the desktop)'''
* GRASS: display window for each document (i.e., set of maps displayed) opened on desktop; one legend/layer manager window for all display windows; ; each module/function opens a separate window on the desktop
* QGIS: display window for each document (i.e., set of maps displayed) opened on the desktop; legend/layer manager window attached to each display window; each module/function opens a separate window on the desktop (e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png)
* ArcGIS: similar to QGIS with combined legend/display for each document (set of maps displayed); each module/function opens a separate window on the desktop (e.g. http://upload.wikimedia.org/wikipedia/en/9/92/ArcMap.jpg)
* MapInfo (pre Pitney Bowes): each document opens a map display window on the desktop; single legend/toolbox opened on the desktop controls all visible documents (i.e., map displays); each module/function opens a separate window on the desktop (similar to current GRASS layout)

'''MDI: (a single frame is opened for the application on the desktop; all documents opened inside the application frame)'''
* SAGA: single application frame opened on the desktop; all documents (display windows) open inside application frame; one legend/layer manager for all display windows; each module/function opens a separate window inside the frame (http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455)
* Ossim: single application frame opened on the desktop; all documents (display windows) open inside application frame; one legend/layer manager for all display windows; each module/function opens a separate window inside the frame (http://www.ossim.org/OSSIM/Albums/Pages/ImageLinker.html)
* Idrisi: similar to SAGA and Ossim (http://www.clarklabs.org/products/idrisi-taiga.cfm)
* MapInfo (Pitney Bowes): Seems to be like Saga (http://www.pbinsight.com/support/training/video-tutorials/)

'''''See also'''''
* Solution to the problem: [http://www.wxwidgets.org/manuals/stable/wx_wxlayoutalgorithm.html wxLayoutAlgorithm]
* [http://en.wikipedia.org/wiki/Multiple_document_interface Multiple document interface] (MDI, windows reside under a single parent window)
* [http://en.wikipedia.org/wiki/Single_document_interface Single document interface] (SDI, separate windows, currently used for wxGUI)
* and [http://en.wikipedia.org/wiki/Human_interface_guidelines Human interface guidelines] (HIG)

== Useful links ==

* [http://www.poromenos.org/tutorials/python 10 minutes Python tutorial] for programmers of other languages

== References ==

* [[User:Landa|Martin Landa]]: [http://gama.fsv.cvut.cz/~landa/publications/2008/gis-ostrava-08/paper/landa-grass-gui-wxpython.pdf New GUI for GRASS GIS based on wxPython] ([http://gis2008.com/indexe.html GIS Ostrava 2008], January 27-30, 2008, Ostrava, Czech Republic)
* [[User:Landa|Martin Landa]], Cristina Moretto, Michele Zanolli, Luca Manganelli and Markus Neteler: [http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/paper/grass-gfoss-tn.pdf wxPython-based GUI for GRASS GIS] ([http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/prezentazione/perugia-grass-gui-wxpython.pdf presentation]) ([http://www.grassmeeting2008.unipg.it IX Meeting degli Utenti Italiani di GRASS - GFOSS], February 20-22, Perugia, Italy)

{{wxGUI}}

WxPython-based GUI for GRASS

2013-02-06T09:11:36Z

⚠️Vesnikos: /* Map Swipe */ typo correction

Browse also wxGUI related [[:Category:WxGUI|articles or screenshots]].

See also [[GRASS GUI]], and [[GRASS and Python]].

For developer-related issues see [http://trac.osgeo.org/grass/wiki/wxGUIDevelopment Trac wxGUI page].

__TOC__

== Overview ==

* [http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.html Manual page]
* A nice summary of the progress to date, written by Jachym Cepicky:
** [http://www.les-ejk.cz/english/wxgrass-new-grass-gui-1 Part 1]
** [http://www.les-ejk.cz/english/wxgrass-new-grass-gui-2 Part 2]
* [[User:Landa|Martin Landa]]: [http://gama.fsv.cvut.cz/~landa/publications/2008/gis-ostrava-08/paper/landa-grass-gui-wxpython.pdf New GUI for GRASS GIS based on wxPython] ([http://gis2008.com/indexe.html GIS Ostrava 2008], January 27-30, 2008, Ostrava, Czech Republic)
* [[User:Landa|Martin Landa]], Cristina Moretto, Michele Zanolli, Luca Manganelli and Markus Neteler: [http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/paper/grass-gfoss-tn.pdf wxPython-based GUI for GRASS GIS] ([http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/prezentazione/perugia-grass-gui-wxpython.pdf presentation]) ([http://www.grassmeeting2008.unipg.it IX Meeting degli Utenti Italiani di GRASS - GFOSS], February 20-22, Perugia, Italy)

=== Requirements ===

* [http://svn.osgeo.org/grass/grass/trunk/gui/wxpython/README README]

=== Development ===

Do you want to help with the development?

* basic Python programming ability required
* GUI programming experience welcomed (especially wxPython)
* GRASS user (or better developer) experience

How to get [http://trac.osgeo.org/grass/wiki/HowToContribute write access] to the GRASS SVN repository.

See example of wxGUI module in trunk: {{src|doc/gui/wxpython/example/}}

== Screenshots ==

* See [[WxGUI Screenshots|Screenshots]] page
* [[:Category:WxGUI|Screenshots from GRASSWiki]]
* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/user-interface Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

== Video tutorials ==

* See [[wxGUI/Video tutorials|Video tutorials]] page

== Components ==

=== Core components ===

==== Layer Manager ====

'''Status:''' prototype implemented.

The '''GRASS GIS Layer Manager''' provides an interactive graphical interface to GRASS commands. The Layer Manager includes a set of pull-down menus for all GRASS GIS functions (analysis, file I/O, GIS configuration and management), toolbar that manage display map layers in map display windows, layer tree in which map layers to display are organized, command output window and integrated command line prompt.

<center>
<gallery perrow=2 widths=300 heights=200>
Image:wxgrass-gis-manager-layer.png|2007/12
Image:wxgrass-gis-manager-output.png|2007/12
Image:Wxgrass rgb.png|2008/02
Image:wxgui-layer-manager-70.png|2010/08
Image:wxgui-pyshell.png|2011/06 - Embedded interactive Python Shell
</gallery>
</center>

==== Import tool ====

The GUI offers a convenient tool for single map and bulk import:

* see [[Importing data]]

==== Map display window ====

'''Status:''' prototype implemented.

Each '''Map display window''' has a unique set of layers to display and region setting (zoom). The map display window includes main toolbar with basic tools including zooming, panning, data querying, simple analyse functions (measure, profile, histogram, etc.), overlay management, etc. From main toolbar are accessible additional toolbars, currently only Digitization tool is available. Under development is Georectification tool.

<center>
<gallery perrow=2 widths=300 heights=200>
Image:Wxgrass-mapdisplay-0.png
Image:Wxgui-mapdisplay-1.png
</gallery>
</center>

==== GUI dialogs ====

'''Status:''' prototype implemented.

Generated from XML using <tt>--interface-description</tt>.

E.g. <tt>d.rgb --help</tt>
<pre>
Description:
Displays three user-specified raster map layers as red, green, and blue overlays in the active graphics frame.

Keywords:
display

Usage:
d.rgb [-ox] red=name green=name blue=name [--verbose] [--quiet]

Flags:
-o Overlay (non-null values only)
-x Don't add to list of commands in monitor
--v Verbose module output
--q Quiet module output

Parameters:
red Name of raster map to be used for <red>
green Name of raster map to be used for <green>
blue Name of raster map to be used for <blue>
</pre>

becomes with <tt>d.rgb --interface-description</tt>

<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task SYSTEM "[http://trac.osgeo.org/grass/browser/grass/trunk/gui/xml/grass-interface.dtd grass-interface.dtd]">
<task name="d.rgb">
<description>
Displays three user-specified raster map layers as red, green, and blue overlays in the active graphics frame.
</description>
<keywords>
display
</keywords>
<parameter name="red" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <red>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<parameter name="green" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <green>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<parameter name="blue" type="string" required="yes" multiple="no">
<description>
Name of raster map to be used for <blue>
</description>
<keydesc>
<item order="1">name</item>
</keydesc>
<gisprompt age="old" element="cell" prompt="raster" />
</parameter>
<flag name="o">
<description>
Overlay (non-null values only)
</description>
</flag>
<flag name="x">
<description>
Don't add to list of commands in monitor
</description>
</flag>
<flag name="verbose">
<description>
Verbose module output
</description>
</flag>
<flag name="quiet">
<description>
Quiet module output
</description>
</flag>
</task>
</source>

which is then used to generate:

[[Image:wxgrass-d-rgb.png|center|600px]]

==== Startup GUI (welcome screen) ====

'''Status:''' prototype implemented.

Start new GRASS session with

grass -wxpython

[[Image:Wxgrass-startup.png|center|400px]]

==== Location wizard ====

'''Status:''' prototype implemented.

Wizard for creating new GRASS project location based on:

* Coordinate system
* EPSG code
* Georeferenced file
* PROJ.4 string
* XY

See also [[GRASS Location Wizard]].

[[Image:Wxgui-location-wizard.png|center|thumb|600px|Location wizard]]

=== Digitizer ===

==== Vector digitizer ====

'''Status:''' prototype implemented.

See also {{cmd|wxGUI.Vector_Digitizer|desc=manual page}}

See also [[GRASS Digitizing tool]] and [[wxGUI Vector Digitizer]].

Replacement of <tt>v.digit</tt> module integrated into Map display window ([http://svn.osgeo.org/grass/grass-promo/screenshots/wxpython/digitization Screenshots]).

<center>

<gallery perrow=2 widths=300 heights=200>
Image:WxDigit200804.png|Vector digitizer (2008/04)
Image:Digit-01.png|Vector digitizer (2007/11)
Image:WxGUI-vdigit-fill-area.png|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)
Image:WxGUI-vdigit-bg.png|Vector digitizer - background raster maps with different opacity level (2008/07)
Image:WxGUI-vdigit-win0.png|Vector digitizer on MS Windows (2011/01)
Image:Wxgui-vdigit-dupl.png|Vector digitizer - checking for duplicates (2011/02)
</gallery>

</center>

==== Raster digitizer ====

'''Status:''' development started in GRASS 7

* {{cmd|r.digit}} (merge with {{cmd|v.digit}}?)
: Probably write a front end for {{cmd|r.in.poly}}, that's all the old {{cmd|r.digit}} is.
* {{cmd|d.rast.edit}}
: Idea: get cell center coords and new values from GUI interaction, then pass those through {{cmd|r.in.xyz}}, and {{cmd|r.patch}} the new values over the top of the old map.
: Current status:

[[Image:D_rast_edit_grass7.png|center|thumb|500px|Raster map editor in GRASS 7]]

* merge with Georectifier? (i.points, i.vpoints)

===== Category Labels =====

* Write with new {{cmd|r.category}} import tool
** ''Back-end component complete: {{cmd|r.category}} module is now updated to handle a rules= file and other goodies like dynamic labels''

* Read with one of {{cmd|r.category}}, {{cmd|r.describe}}, {{cmd|r.report}}, {{cmd|r.stats}}, ???
** probably need to add a new flag to one of those to print flat <tt>"%d %s", cat, label</tt>
: or read the cats/ file directly, it's already flat ascii.

* how to deal with FP maps & cats?

=== Cartography tools ===

==== GUI for {{Cmd|ps.map}} ====

'''Status:''' under development (Anna Kratochvilova).

<center>
{|
|-
| [[Image:CartographicComposer.png|350px|thumb|Cartographic Composer: draft mode]]
| [[Image:CCPreview.png|350px|thumb|Cartographic Composer: preview]]
|-
|}
</center>

<center>More info at '''[[WxGUI Cartographic Composer]]'''.</center>

-----

==== Direct printing ====

'''Status:''' development not started yet.

Implement direct printing of map canvas content using GRASS PS driver or Cairo driver.

* [http://trac.gispython.org/projects/PCL/wiki Python Cartographic Lab]
* [http://wiki.osgeo.org/wiki/OSGeo_Cartographic_Library OSGeo Cartographic Library]
** http://lists.osgeo.org/pipermail/discuss/2008-April/003337.html
** http://www.intevation.de/pipermail/freegis-list/2007-April/003142.html
* [http://wiki.osgeo.org/wiki/OSGeo_map_symbol_set OSGeo Map Symbol Set]
* [http://www.gdal.org/ogr/ogr_feature_style.html OGR - Feature Style Specification]
* [http://trac.osgeo.org/mapguide/wiki/MapGuideRfc14 MapGuide RFC 14 - Cartographic Stylization Engine]

* [http://www.iho.shom.fr/PUBLICATIONS/download.htm#special S-52 standard for nautical chart (ENC) symbology] and cartography from the [http://www.iho.shom.fr/ International Hydrographic Bureau]
** [http://openev.cvs.sourceforge.net/openev/contrib/S52/ GPL library implementing the S-52 standard] (OpenEV)

* [http://www.opengeospatial.org/standards/symbol OpenGIS Symbology Encoding Implementation Specification]

* [http://geosysin.iict.ch/trac/wiki/Index4extJPAL PAL]

=== Georectifier ===

'''Status:''' prototype implemented.

<center>
{|
|-
| [[Image:Wxgui-georectify-0.png|thumb|350px|center|Georectifier (old interface)]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center|Georectifier (old interface)]]
|-
|}
</center>

[[Image:Georectifier berlin.png|thumb|Georectification of historical maps using a simplified OpenStreetmap reference (example Berlin) - new interface|450px|center]]

See also [[Georeferencing]].

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

<center>
{|
|-
| [[Image:Wxgui-profile-0.png|thumb|350px|center]] ||
[[Image:Wxgui-profile-1.png|thumb|350px|center]]
|-
|}
</center>

=== Attribute table manager ===

'''Status:''' prototype implemented.

See [[wxGUI Attribute Table Manager]] page and also {{cmd|wxGUI.Attribute_Table_Manager|desc=manual page}}.

[[Image:Grass-atm-example.png|center|thumb|640px|Attribute queries in wxGUI]]

=== 3D view mode ===

'''Status:''' prototype implemented (Google Summer of Code 2008/2010/2011).

See detailed information at [[wxNVIZ]] page and classic Tcl/Tk [[NVIZ]] pages.

[[Image:Wxnviz-volumes.png|640px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space.]]

=== Imagery tools ===

'''Status:''' (re)development not started in earnest yet. Some behind-the-scenes code has been prepared, but not much.
: ''Volunteers welcome!''

==== Ortho photos ====

'''Status:''' development not started yet.

* To replace {{cmd|i.ortho.photo}} and friends

==== wx.iclass ====

'''Status:''' prototype implemented.


* See [[wxIClass]] page

=== Graphical Modeller ===

'''Status:''' prototype implemented.

[[File:WxGUI-modeler-if-else-0.png|500px|center]]

See [[wxGUI Graphical Modeler]] page for more information.

=== Extension Manager ===

'''Status:''' prototype implemented

Settings | Addons extensions | Install extension from addons

{{YouTube|buxsHVHLDBI|desc=wxGUI Extension Manager}}

[[Image:wxgui-em.png|center|thumb|500px|wxGUI Extension Manager]]

=== Raster Calculator ===

'''Status:''' prototype implemented

[[Image:wxgui-mapcalc.png|center|thumb|500px|wxGUI Map Calculator]]

See also [[wxGUI/Video tutorials#Raster calculator|video tutorials]].

=== GRASS Catalog ===

'''Status:''' under development (in AddOns)

* [http://lsi.iiit.ac.in/grass_addons/ GRASS Catalog files]

<center>
{|
|-
| [[Image:GRASS Catalog1.png|350px|thumb|center|GRASS Catalog ]]
| [[Image:GRASS Catalog2.png|350px|thumb|center|GRASS Catalog]]
|-
|}
</center>

;Current Features:

* copy, delete, rename map layers (raster & vector) in current mapset.
* view raster & vector map layers from any location and any mapset.
* Provides a GUI wrapper for r.info & v.info grass commands while viewing map layers in mapwindow.
* Can connect with OssimPlanet using PlanetSasha
* Add and Remove maps from GRASS GIS to OssimPlanet(Send to OssimPlanet/Remove from OssimPlanet)

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Create a properties window to display Coordinate system & projection for each map
* ...

Alternative: http://code.google.com/p/wxgis/

=== r.li.setup GUI ===
'''Status:''' available as {{cmd|g.gui.rlisetup|version=70}}

Porting of {{cmd|r.li.setup}} in wxPython.
Some screenshots of developing version

<center>
<gallery perrow=2 widths=300 heights=200>
Image:Rlisetup_first_frame.png | The first windows where you can select existing configuration file or create new one
Image:Rlisetup wizard first page.png | First window of wizard
Image:Rlisetup wizard keybord sampling frame.png | Choose the sampling frame
Image:Rlisetup_wizard_sampling_areas.png ‎| Choose the type of sampling area
</gallery>
</center>

=== Help browser ===

'''Status:''' development not started yet.

For browsing manual pages is currently used web browser, the goal is to design integrated help system.
: HB: ''We used to have one of these for viewing the help pages of Tcl/Tk NVIZ. We dropped it because it was a pain to maintain and generally outside our core mission so a distraction.''

=== Map Swipe ===

'''Status:''' prototype implemented.

This tool enables you to compare two raster maps covering the same area (e.g. compare maps from different year).

;Current features:
* orientation of swipe line can be horizontal or vertical
* zooming works in the same way as in [[#Map_display_window | Map Display]]

See more '''examples''' and videos at [[WxGUI Map Swipe]] page.

[[Image:Tsunami japan2011 sendai.jpg|center|thumb|500px|wxGUI Map Swipe for disaster management: Tsunami Japan 2011]]

=== Animation Tool ===

'''Status:''' prototype implemented in GRASS 7.

Animation tool is a replacement for {{cmd|xganim}}. It allows to animate a series of GRASS raster maps or a space time raster dataset ([http://trac.osgeo.org/grass/wiki/Grass7/TemporalExtension see GRASS GIS temporal extension]).

[[Image:WxGUI animation tool.jpg|center|500px|wxGUI animation tool]]

;Current features:

* display up to 4 synchronized animations
* control the animation speed
* interactively change active frame using a slider
* visualize space time datasets with unequally spaced intervals
* animate 3d view (partially implemented)

Animation Tool can be launched from Layer Manager menu (File -> Animation Tool) or through command line ({{cmd|g.gui.animation|version=70}}).

{{YouTube|zVyTV1wF32M|desc=wxGUI Animation Tool}}
{{YouTube|oTQ963mC9JE|desc=wxGUI Animation Tool - both 2D and 3D view}}

=== Vector Network Analysis Tool ===

'''Status:''' prototype implemented.

See more examples and video at [[WxGUI Vector Network Analysis Tool]] page.

== Known issues ==

* See and report in trac: [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&component=wxGUI&order=priority List of open issues]

=== Platform specific ===

For the GUI to know what platform it's on, and therefore apply platform specific commands (e.g. append '.exe' to programs) it has to test what platform it is running on. Here we take the experimental approach to learning what's best to use. Please add or generalize this list as you can.

Platform information - start Python from the command line then issue

<source lang="python">
import sys
sys.platform

import os
os.name
os.environ['OS']

import platform
platform.system()
</source>

* Results:

{| border="1" class="wikitable" style="text-align:center"
! Platform
! sys.platform
! os.name
! os.environ['OS']
! platform.system()
|-
| 32bit GNU/Linux
| linux2
| posix
| ''n/a''
| Linux
|-
| 64bit GNU/Linux
| linux2
| posix
| ''n/a''
| Linux
|-
| 32bit Mac OSX (PowerPC G4)
| darwin
| posix
| ''n/a''
| Darwin
|-
| 64bit Mac OSX (Intel)
| [1] see note
| ?
| ?
| ?
|-
| 32bit MS Windows XP
| win32
| nt
| Windows_NT
| Windows
|-
| 64bit MS Windows Vista
| win32
| nt
| Windows_NT
| Windows
|-
| 32bit MS Windows XP (Cygwin)
| win32
| ?
| ?
| ?
|}

[1] On Fri, May 29, 2009 at 10:49 PM, William Kyngesburye wrote:
: ''Right now the GUI only runs 32bit, even if the rest of GRASS is 64bit, because it's not yet possible for wxPython to be 64bit. It comes out the same as PPC 32bit - no distinction between ppc/intel or 32/64 bit, it's all darwin. (yes, I checked, and I have a custom 64bit python executable to verify)''

== General GUI Design ==

=== Layout ===

For some users, the current approach of separate windows (SDI) leads to a windows flooding. Especially on large monitors or dual screen systems catching the wxGUI windows can be tedious when they appear on separate monitors (depends on windows manager, the much used KDE scatters typically the wxGUI windows all over the screen real estate). Almost each task generates a new wxGUI window which is freely floating around on the screen: [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-03.png example 1] and [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-01.png example 2]. On a dual-screen this may sum up to 50cm of distance!

'''Proposed solutions:'''
* implement ''optional'' layout similar to QGIS (with a legend attached to each display) or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of the layer manager and display windows to keep the windows closer
* do not allow module windows to stay open. That is, get rid of the apply button and force each window to close when OK is pressed (QGIS/ArcGIS approach). This leaves only the display(s) and single legend/layer manager on desktop.
* If you otherwise wish to continue using your current WM, file a bug report with them asking for better multi-head support and get the problem fixed at the source. (there probably already is a bug filed with tips in it)

<center>
{|
|-
| [[Image:Wxgui_current.png|350px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|350px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
|-
|}
</center>

'''New solution: see [[WxGUI#Data_Catalog]] above.'''

====What others do====

'''SDI: (each document opened in application occupies a window on the desktop)'''
* GRASS: display window for each document (i.e., set of maps displayed) opened on desktop; one legend/layer manager window for all display windows; ; each module/function opens a separate window on the desktop
* QGIS: display window for each document (i.e., set of maps displayed) opened on the desktop; legend/layer manager window attached to each display window; each module/function opens a separate window on the desktop (e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png)
* ArcGIS: similar to QGIS with combined legend/display for each document (set of maps displayed); each module/function opens a separate window on the desktop (e.g. http://upload.wikimedia.org/wikipedia/en/9/92/ArcMap.jpg)
* MapInfo (pre Pitney Bowes): each document opens a map display window on the desktop; single legend/toolbox opened on the desktop controls all visible documents (i.e., map displays); each module/function opens a separate window on the desktop (similar to current GRASS layout)

'''MDI: (a single frame is opened for the application on the desktop; all documents opened inside the application frame)'''
* SAGA: single application frame opened on the desktop; all documents (display windows) open inside application frame; one legend/layer manager for all display windows; each module/function opens a separate window inside the frame (http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455)
* Ossim: single application frame opened on the desktop; all documents (display windows) open inside application frame; one legend/layer manager for all display windows; each module/function opens a separate window inside the frame (http://www.ossim.org/OSSIM/Albums/Pages/ImageLinker.html)
* Idrisi: similar to SAGA and Ossim (http://www.clarklabs.org/products/idrisi-taiga.cfm)
* MapInfo (Pitney Bowes): Seems to be like Saga (http://www.pbinsight.com/support/training/video-tutorials/)

'''''See also'''''
* Solution to the problem: [http://www.wxwidgets.org/manuals/stable/wx_wxlayoutalgorithm.html wxLayoutAlgorithm]
* [http://en.wikipedia.org/wiki/Multiple_document_interface Multiple document interface] (MDI, windows reside under a single parent window)
* [http://en.wikipedia.org/wiki/Single_document_interface Single document interface] (SDI, separate windows, currently used for wxGUI)
* and [http://en.wikipedia.org/wiki/Human_interface_guidelines Human interface guidelines] (HIG)

== Useful links ==

* [http://www.poromenos.org/tutorials/python 10 minutes Python tutorial] for programmers of other languages

== References ==

* [[User:Landa|Martin Landa]]: [http://gama.fsv.cvut.cz/~landa/publications/2008/gis-ostrava-08/paper/landa-grass-gui-wxpython.pdf New GUI for GRASS GIS based on wxPython] ([http://gis2008.com/indexe.html GIS Ostrava 2008], January 27-30, 2008, Ostrava, Czech Republic)
* [[User:Landa|Martin Landa]], Cristina Moretto, Michele Zanolli, Luca Manganelli and Markus Neteler: [http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/paper/grass-gfoss-tn.pdf wxPython-based GUI for GRASS GIS] ([http://gama.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/prezentazione/perugia-grass-gui-wxpython.pdf presentation]) ([http://www.grassmeeting2008.unipg.it IX Meeting degli Utenti Italiani di GRASS - GFOSS], February 20-22, Perugia, Italy)

{{wxGUI}}

Talk:GRASS Community Sprint Genova 2013

2013-02-03T19:25:19Z

⚠️Vesnikos:

== Reports ==

=== [[User:Wenzeslaus|Vaclav Petras]] ===

* publishing tips for wxGUI development ([[wxGUI Programming Howto]])
* wxGUI refactoring status page (http://trac.osgeo.org/grass/wiki/wxGUIDevelopment/Refactoring)
* discussing the purpose of wiki, trac, etc. (http://titanpad.com/NzPV3h8k1E)

=== [[User:lucadelu|Luca Delucchi]] ===

* commit small fix in i.histo.match (thanks to Nikos Alexandris) {{rev|54833}}
* update example for wxpython gui {{rev|54837}} - {{rev|54875}}

=== [[User:NikosA|Nikos Alexandris]] ===

* adding categories to GRASS-wiki pages ''and'' into category pages (trying to [http://www.mediawiki.org/wiki/Help:Category#Managing_the_category_hierarchy create/manage categories hierachy])
* scratching on ideas about retouching the GRASS-Wiki main page [http://grasswiki.osgeo.org/wiki/User:NikosA/GRASS-Wiki_MainPage]

=== [[User:vesnikos|Ves Nikos]] ===

* Translating grass GUI into greek

== Press release ==

... in 2013 ...

== Notes for the organizers ==

See [[Talk:GRASS_Community_Sprint_Prague_2011#Notes_for_the_organizers]]

== Not to forget about ==

First day:
* presentation of participants

First or second day:
* group photo

GRASS Community Sprint Genova 2013

2013-01-07T10:10:01Z

⚠️Vesnikos:

The GRASS GIS team will organize a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' from '''2-7 Feb, 2013'''. The sprint is at the same time of the [http://geomorfolab.arch.unige.it/genova2013/index.php?lang=en XIV Meeting degli Utenti Italiani Grass e Gfoss], 6-9 Feb 2013, University of Genova, Dipartimento di Scienze per l'Architettura della Scuola Politecnica, [http://en.wikipedia.org/wiki/Genoa Genova], [http://en.wikipedia.org/wiki/Italy Italy].

== Purpose ==

This next edition of the GRASS GIS community sprint 2013 is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. The '''community''' sprint is a get-together for GRASS project members and supporters and related [http://www.osgeo.org/ OSGeo] projects to make decisions and tackle larger problems. 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.

For this meeting, we welcome people committed to improving the GRASS GIS and related projects. This includes developers, document writers, wish and bug reporters, translators etc.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for '''sponsors''' to cover costs such as meals or 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/]'''

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

The third 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. 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.

== Timing ==

'''When''': 2-7 Feb, 2013

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''': 6 days

== Venue ==

For the 2nd and 3rd of February we are hosted by the [http://www.alid.it ALID association] at Circolo Zenzero in [http://osm.org/go/xX0m6qo~B-- Via Torti 35, Genova] (in Italy universities are closed during weekends).

From 4th to 7th at University of Genova, Dipartimento di Scienze per l'Architettura della Scuola Politecnica, Genova, Italy.

'''[http://geomorfolab.arch.unige.it/ Geomorfolab]''',
Dipartimento di Scienze per l'Architettura,
Scuola Politecnica - Università degli Studi di Genova,
[http://osm.org/go/xX0ml6cj7-- Stradone S. Agostino 37, 16128 Genova]

Rooms: TBD

== Accommodation and Costs ==

* Bed and breakfast (in negotiation) - close to venue
* New youth hostel, http://www.manenahostel.it/ - close to venue
* List of [http://geomorfolab.arch.unige.it/genova2013/index.php?option=com_content&view=article&id=42&Itemid=18 Site of XIV Meeting degli utenti italiani GRASS e GFOSS]
* more to be added...

== Weather and Common Item Prices ==

== Agenda ==

=== Timeline ===

==== Saturday, 2 Feb ====
* Kick-off in the [http://www.alid.it ALID association] at Circolo Zenzero in [http://osm.org/go/xX0m6qo~B-- Via Torti 35, Genova]
* Participants presentation
* Dinner: at Circolo Zenzero

==== Sunday, 3 Feb ====
* 9:00-evening
* Meeting again in the at Circolo Zenzero

List of topics:
* TBD
* Dinner: at Circolo Zenzero

==== Monday, 4 Feb ====
* 9:00-evening
* Meeting at University of Genova, Dipartimento di Scienze per l'Architettura della Scuola Politecnica, Genova, Italy at the '''[http://geomorfolab.arch.unige.it/ Geomorfolab]''', [http://osm.org/go/xX0ml6cj7-- Stradone S. Agostino 37, 16128 Genova]

List of topics:
* TBD

==== Tuesday, 5 Feb ====
* 9:00-evening
* Meeting again at University of Genova, Geomorfolab

List of topics:
* TBD

==== Wednesday, 6 Feb ====
* 9:00-evening
* Meeting again at University of Genova, Geomorfolab

List of topics:
* TBD
* Group photo!!
* Prepare press release

==== Thursday, 7 Feb ====
* 9:00-evening
* Meeting again at University of Genova, Geomorfolab

List of topics:
* TBD
* Prepare short presentations for Friday at the Italian GFOSS meeting
* Finish and publish press release

Closing of community sprint

==== Friday, 8 Feb ====
* Two hours of time for '''presenting Community Sprint results''' at Italian GFOSS meeting ([http://geomorfolab.arch.unige.it/genova2013/index.php?option=com_content&view=article&id=29&Itemid=21&lang=en venue])

== Participation ==

=== In person ===

{|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|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topic'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| Feb 2
| Feb 10
|
| L
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|Italy
|
|
|
| M + S
|
|-
|3
|[[User:Madi|Margherita Di Leo]]
|Italy
|
|
|
| L
|
|-
|4
|[[User:pcav|Paolo Cavallini]]
|Italy
|
|
|
| L
|
|-
|5
|[[User:lcasagrande|Luca Casagrande]]
|Italy
|
|
| GRASS Tutorial with Open Data from Italy
| L
|
|-
|6
|[[User:Annakrat|Anna Kratochvilova]]
|Czech Republic
|
|
|
| M
|
|-
|7
|Vaclav Petras
|Czech Republic
|
|
|
| M
|
|-
|8
|[[User:pietro|Pietro Zambelli]]
|Italy
|
|
|
| M
|
|-
|9
|[[User:Landa|Martin Landa]]
|Czech Republic
| Feb 2
| Feb 10
| [[wxGUI]], vector architecture, GRASS 7 development
| L
| Probably unable to come :-(
|-
|10
|[[User:Maxi|Massimiliano Cannata]]
|Italy
|
|
|
| XL
|
|-
|11
|[[User:NikosA|Nikos Alexandris]]
|Greece
|
|
| GRASS-wiki, (re-)working on the idea for a practical & visual guide to GRASS-GIS
| M
| Will try to be there!
|-
|12
|[[User:AnneGhisla|Anne Ghisla]]
|Italy
|
|
| fix v.krige, examine i.atcorr problems with RapidEye
| M
| Almost sure of participation
|-
|13
|[[User:vesnikos|Ves Nikos]]
|Greece
|
|
|
| L
| Will try and come with Nikos Alexandris
|-
|}

=== Via IRC chat ===

: [irc://freenode/grass #grass] on Freenode

For details, see [[IRC]]

=== Collaborative document scratching ===

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed ([http://en.wikipedia.org/wiki/File:L_plug.jpg Italy])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

Also during the event :)

== FAQ ==

* How was it last time?
** Very cool, see [[GRASS Community Sprint Prague 2012]]!
* ''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?''
** Not at all: 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 dot com></tt> or [[User:Neteler|Markus Neteler]]

[[Category: Workshops]]

Import TRMM

2010-11-17T21:21:27Z

⚠️Vesnikos: small typo

TRMM data are usually delivered in a specific HDF format which is (partially) supported from GDAL 1.8+ (so, {{cmd|r.in.gdal}} would in theory work, see also below for rotation problem).

However, it is easier to get instead binary grids from here:

ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B43_V6/

The format is explained [ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B43_V6/3B43.ctl here]. Hence, to import gridded TRMM into a Lat-long location with is done via

# generally
r.in.bin -f -b north=50 south=-50 east=180 west=-180 rows=400 cols=1440 ....

e.g.
r.in.bin -f -b input=3B43.100101.6.precipitation.bin output=3B43.100101.6.precipitation \
north=50 south=-50 east=180 west=-180 rows=400 cols=1440

Optionally convert then from mm/hr to some other time unit.

=== Getting rotated maps in TRMM-HDF? ===

The TRMM 3B43 HDF files are rotated by 90° (clockwise), so north is right and west is up. The included datasets "precipitation" and "error" can be dumped from the HDF files to a binary or ASCII file with the "hdp" tool which should be on any system that has the HDF4 library installed.

Rotate "precipitation" with
hdp dumpsds -r 4 -d -o <outfile> -b <TRMM_3B43.hdf>

and "error" with
hdp dumpsds -r 5 -d -o <outfile> -b <TRMM_3B43.hdf>

These are rotated and need to be rotated back. The (properly oriented) binary grids are much easier to handle than the original HDF files.

[[Category: FAQ]]