GRASS-Wiki - User contributions [en]

Support

2012-12-19T19:11:36Z

⚠️Rashadkm: /* Commercial support: Companies and Institutions which offer GRASS Support */

== GRASS Community ==

To reach the community, see [[GRASS Community]].

== Commercial support: Freelancers who offer GRASS Support ==

You need a person with programming skills? Check out this list:

* Seth Price <seth@pricepages.org> - low-level raster processing, code optimization, OpenCL
* Mohammed Rashad <rashadkm [at] gmail.com> - Add/Maintain modules(Python and C), UI development
* you
* ...

== Commercial support: Companies and Institutions which offer GRASS Support ==



{| class="wikitable sortable" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" | Country
! scope="col" | Name
! scope="col" | Competences
! scope="col" | Site
|-
| Germany
| GDF Hannover
| Project management, Data analysis
| http://www.gdf-hannover.de
|-
| Germany
| Geoinformatik Büro Dassau
| Project management, Training, Data analysis, Programming
| http://www.gbd-consult.de
|-
| Italy
| Fondazione Edmund Mach
| Project management, Data analysis, Programming
| http://gis.cri.fmach.it
|-
| India
| Lab for Spatial Informatics
| Project management, Data analysis, Programming, Training
| http://lsi.iiit.ac.in
|-
| your country
| ...
| ...
| ...
|}

* See also the [http://www.osgeo.org/search_profile OSGeo Commercial Service Providers Index] (and those which are [http://www.osgeo.org/search_profile?SET=1&MUL_TECH%5B%5D=00015 GRASS-specific])

[[Category: FAQ]]

Support

2012-12-19T19:10:32Z

⚠️Rashadkm: /* Commercial support: Freelancers who offer GRASS Support */

== GRASS Community ==

To reach the community, see [[GRASS Community]].

== Commercial support: Freelancers who offer GRASS Support ==

You need a person with programming skills? Check out this list:

* Seth Price <seth@pricepages.org> - low-level raster processing, code optimization, OpenCL
* Mohammed Rashad <rashadkm [at] gmail.com> - Add/Maintain modules(Python and C), UI development
* you
* ...

== Commercial support: Companies and Institutions which offer GRASS Support ==



{| class="wikitable sortable" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" | Country
! scope="col" | Name
! scope="col" | Competences
! scope="col" | Site
|-
| Germany
| GDF Hannover
| Project management, Data analysis
| http://www.gdf-hannover.de
|-
| Germany
| Geoinformatik Büro Dassau
| Project management, Training, Data analysis, Programming
| http://www.gbd-consult.de
|-
| Italy
| Fondazione Edmund Mach
| Project management, Data analysis, Programming
| http://gis.cri.fmach.it
|-
| your country
| ...
| ...
| ...
|}

* See also the [http://www.osgeo.org/search_profile OSGeo Commercial Service Providers Index] (and those which are [http://www.osgeo.org/search_profile?SET=1&MUL_TECH%5B%5D=00015 GRASS-specific])

[[Category: FAQ]]

Project jobs

2012-12-03T05:10:29Z

⚠️Rashadkm: /* Interested people */

== Open jobs in the GRASS project ==

The growing infrastructure and extended user support requires more efforts to integrate user contributions and to keep things running. This page contains a list of jobs for which we seek volunteers. These jobs descriptions may appear a bit formal, but shall illustrate the needs.

=== Documentation manager ===

GRASS documentation (HTML/MAN pages) need to be frequently revisited and updated. Some pages are still lacking examples or clarity.

Skills:
* knowledge of standard HTML (ASCII editor is preferred over HTML editor)
* willingness to use plain text editors to write pages (to avoid that HTML cruft creeps in)
* familiarity (or willingness to learn use) with GRASS Web site SVN (see [[Working with SVN|instructions]])
* no programming skills required
* excellent knowledge of English language (native speaker preferred)
Tasks:
* update outdated manual pages
* homogenize style and layout
* add relevant graphics/screenshots with credits/CC license into page
* receive and merge contributions from external contributors; remove offensive HTML tags not understood by g.html2man (say: reduce to simple HTML - see [http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/SUBMITTING_DOCS instructions])
Estimated workload:
* in average: 1-x h per week

=== Web site contributors (open) ===

Several [[Web site]] contributors are desired to update pages and to improve the current structure. A future goal may be the move to a CMS system such as Drupal which would be a major effort.

Skills:
* knowledge of standard HTML (a single PHP function is used to construct menus)
* willingness to use plain text editors to write pages (to avoid that HTML cruft creeps in)
* familiarity (or willingness to learn use) with GRASS Web site SVN (see [[Working with SVN|instructions]])
* no programming skills required
Tasks:
* update outdated pages
* think about and implement '''"user stories"''' to make site more attractive
* think about and implement translation of important pages
* simplify structure
* add new screenshots with credits/CC license)
* regularly check if mirror sites work
Estimated workload:
* in average: 1-x h per week
Contact: Markus Neteler

=== Wiki manager (open) ===

The GRASS wiki (you are using it at the moment) requires continuous monitoring.

Skills:
* basic knowledge of mediawiki usage
* no programming skills required
Tasks:
* update outdated pages
* simplify structure where needed (merge pages)
* clean up [[:Special:Lonelypages|Orphaned pages]] (link, merge or remove)
* keep [[:Special:Categories|Categories]] up to date (add at bottom of pages where needed)
* keep an eye on spammers
Estimated workload:
* in average: 1h per week
Contact: Markus Neteler, [[User:Landa|Martin Landa]]

=== Graphic design lead (open) ===

We need someone with good graphic design skills to maintain the artwork used in the various GUIs and the web site. The initial priority is to rework the icons used in the various GUIs and clean up the screenshot gallery.

Skills:
* Graphic design, graphic design software
* Artistic
* A sufficient level of familiarity with the GIS in order to capture the precise meaning of a button's task in a simple picture.
* No programming experience needed, but it would be helpful if willing to (wx)Python in the long term.
* Manage binary files in SVN (fairly simple to learn)
Tasks:
* Create new icons for the various GUIs
* Work with website manager to create, solicit, and maintain screenshot gallery
* Work with the GUI team to perfect GUI layout and menu presentation.
* Help promotion and newsletter teams in preparing logo banners, layout ideas, etc.
Estimated workload:
* After initial work on icons: 1hr per week

=== Public relations manager ===

Despite the continuous growth of the user community, we seek "GRASS GIS awareness" especially for public administration and companies. A multi-language brochure is needed to promote GRASS in a more effective way. Funding for a high quality print is to be defined.

Skills:
* communication and design skills
Tasks:
* find like-minded people to form a GRASS promotion group
* communicate the existence of the GRASS project
* design of a multi-language brochure (both PDF and printed) in collaboration with the [http://wiki.osgeo.org/index.php?title=VisCom OSGeo-VisCom team]
* create material to illustrate the GRASS functionality
* contact public administration and professionals in a non-spammy way
* collect success stories and render them usable for the Web site

== Accepted positions (which were advertised here) ==

=== Translations manager ===

'''''NEWS: Kindly accepted by Jan '''''

The translations manager is responsible for maintaining the translation of GRASS messages
([http://grass.osgeo.org/devel/i18n.php translation page; [http://lists.osgeo.org/mailman/listinfo/grass-translations/ mailing list])

Skills:
* knowledge (or willingness to learn use) of translation tools (kbabel, poEDIT)
* familiarity (or willingness to learn use) with SVN (see [[Working with SVN|instructions]])
* no programming skills required
Tasks:
* work with GRASS branches and SVN-Head (latest GRASS)
* merging translation contributions (with 'msgmerge' of .po files or simply use [http://mpa.itc.it/markus/useful/po_merge.sh po_merge.sh])
* invite translators to contribute (ask regularly, find new), make them use recent GRASS
* create template files for new languages ('make pot')
* update existing translations '''after''' having received latest submissions from translators ('make update-po')
* keep headers of .po files intact and up-to-date
* add new translators to AUTHORS file in source code
Estimated workload:
* in average: 1-2h per week or less

== Interested people ==

While we have to figure out the process, here a list of interested people. Please add yourself:

* Dylan Beaudette: Web site contributor (familiar with Drupal CMS)
* Scott Mitchell: Web site contributor, could possibly do the translation job, if nobody with translation tool experience volunteers
* Brad Douglas: Public Relations contributor (co-maintainer)
* Mohammed Rashad: Documentation Manager( willing to accept)

== Existing jobs ==


;OSGeo Trac maintainers
:Markus Neteler, Martin Landa

;OSGeo SVN code repository
:Markus Neteler, Martin Landa, Howard Butler
;Main Web site/[http://svn.osgeo.org/grass/grass/trunk/doc/infrastructure.txt Infrastructure] manager
:Markus Neteler
;Mailing list manager
:Markus Neteler
;Translations manager
:Jan T...
;Wiki manager
:Markus Neteler, Martin Landa (see above for open position)
;Binaries packager
* Fedora RPMs: ?
* Mandriva RPMs: Buchan Milne
* OpenSUSE RPMs: Otto Dassau
* Debian: Francesco Lovergine and the [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl Debian GIS Project]
* Ubuntu: ...?
* winGRASS native: Helmut Kudrnovsky, Moritz Lennert, Benjamin Ducke, Huidae Cho, Paul Kelly, Tim Sutton (QGIS/GRASS bundle)
* MacOSX: William Kyngesburye

[[Category:Community]]

WxPython-based GUI for GRASS

2012-02-25T10:52:24Z

⚠️Rashadkm: /* GRASS Catalog */

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

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

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|-
|
[[Image:Wxnviz-volumes.png|300px|thumb|center|wxGUI: Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space]]
||
[[Image:wxgui-spatial-query.png|300px|thumb|center|wxGUI: Spatial query]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

== Video tutorials ==

=== Import vector data ===

* [[Import DXF]]
{{YouTube|eD2B1i9YxxQ|desc=Importing single shapefile}}
{{YouTube|ohbV_MR530Q|desc=Importing multiple shapefiles}}
{{YouTube|lJVBw78zYY0|desc=Importing SpatiaLite layers}}
{{YouTube|JoqIkL2VRVc|desc=Importing PostGIS layers into GRASS}}

=== Import raster data ===

Importing multiple GeoTIFF files:

<center>
{|
|
[[Image:WxGUI bulk raster import1.png|300px|thumb|Bulk import of GeoTIFF via menu]]
||
[[Image:WxGUI bulk raster import2.png|320px|thumb|Bulk import of GeoTIFF via menu (files are auto-selected)]]
|
|}
</center>

=== Link vector data (GRASS 7) ===

{{YouTube|eB3_SmE3E9Q|desc=Link PostGIS layers as GRASS vector maps}}

=== Map display ===

{{YouTube|PY8aytvfQqA|desc=Define legend and export to image}}

=== Georectifier ===

* Manual page of {{cmd|wxGUI.GCP_Manager|desc=GCP Manager}}

=== Graphical modeler ===

''Note:'' GRASS 6.4.2+ required.

See wxGUI [[WxGUI Modeler#Video Tutorials|Modeler]] page.

=== Layer Manager: Searching GRASS module ===

{{YouTube|Z9STgChNWcM|desc=Search for GRASS module (GRASS 6.4.2 required)}}

=== Map Calculator ===

{{YouTube|yMpVVRaVYeA|desc=Calculating NDVI}}

=== wxGUI 3D view mode (wxNviz) ===

See [[WxNviz#Video tutorials|wxNviz]] 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>

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

Manual page - {{cmd|wxGUI.Vector_Digitizer}}

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 not started yet.

* {{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.

* 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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

See also [[Georeferencing]].

; Tutorials

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

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

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

[[Image:Grass-atm-example.png|center|thumb|640px|Attributes queries in wxGUI]]
[[Image:Wxgui-attribute-table-manager.png|center|thumb|350px|Attribute Table Manager]]

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== 3D view mode ===

'''Status:''' under development (Google Summer of Code 2008/2010).

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:''' Under development.

===== First prototype (AddOns) =====

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.class wx.class]

<center>
{|
|-
| [[Image:wx.class1.png|350px|thumb|center|wx.class]]
| [[Image:wx.class2.png|350px|thumb|center|wx.class]]
| [[Image:wx.class3.png|350px|thumb|center|wx.class]]
|-
|}
</center>

Current Features:

* Does not require xterm
* works on windows which is not currently available

To be implemented:

* Proper view of histogram using python-matplotlib
* To work on other datset (currently works for nc_spm_08)
* Needs a code cleanup

===== Second prototype (trunk) =====

* [[wxIClass]]

=== Graphical Modeller ===

'''Status:''' under development.

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

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

=== Extension Manager ===

'''Status:''' under development

* [http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html wxGUI Extension Manager]

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

=== Map Calculator ===

'''Status:''' prototype implemented

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

=== GRASS Catalog ===

;'''Status:''' Under development.

* [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:''' Under development.

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

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

WxPython-based GUI for GRASS

2012-02-25T10:21:24Z

⚠️Rashadkm: /* GRASS Catalog added patch link */

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

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

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|-
|
[[Image:Wxnviz-volumes.png|300px|thumb|center|wxGUI: Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space]]
||
[[Image:wxgui-spatial-query.png|300px|thumb|center|wxGUI: Spatial query]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

== Video tutorials ==

=== Import vector data ===

* [[Import DXF]]
{{YouTube|eD2B1i9YxxQ|desc=Importing single shapefile}}
{{YouTube|ohbV_MR530Q|desc=Importing multiple shapefiles}}
{{YouTube|lJVBw78zYY0|desc=Importing SpatiaLite layers}}
{{YouTube|JoqIkL2VRVc|desc=Importing PostGIS layers into GRASS}}

=== Import raster data ===

Importing multiple GeoTIFF files:

<center>
{|
|
[[Image:WxGUI bulk raster import1.png|300px|thumb|Bulk import of GeoTIFF via menu]]
||
[[Image:WxGUI bulk raster import2.png|320px|thumb|Bulk import of GeoTIFF via menu (files are auto-selected)]]
|
|}
</center>

=== Link vector data (GRASS 7) ===

{{YouTube|eB3_SmE3E9Q|desc=Link PostGIS layers as GRASS vector maps}}

=== Map display ===

{{YouTube|PY8aytvfQqA|desc=Define legend and export to image}}

=== Georectifier ===

* Manual page of {{cmd|wxGUI.GCP_Manager|desc=GCP Manager}}

=== Graphical modeler ===

''Note:'' GRASS 6.4.2+ required.

See wxGUI [[WxGUI Modeler#Video Tutorials|Modeler]] page.

=== Layer Manager: Searching GRASS module ===

{{YouTube|Z9STgChNWcM|desc=Search for GRASS module (GRASS 6.4.2 required)}}

=== Map Calculator ===

{{YouTube|yMpVVRaVYeA|desc=Calculating NDVI}}

=== wxGUI 3D view mode (wxNviz) ===

See [[WxNviz#Video tutorials|wxNviz]] 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>

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

Manual page - {{cmd|wxGUI.Vector_Digitizer}}

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 not started yet.

* {{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.

* 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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

See also [[Georeferencing]].

; Tutorials

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

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

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

[[Image:Grass-atm-example.png|center|thumb|640px|Attributes queries in wxGUI]]
[[Image:Wxgui-attribute-table-manager.png|center|thumb|350px|Attribute Table Manager]]

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== 3D view mode ===

'''Status:''' under development (Google Summer of Code 2008/2010).

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:''' Under development.

===== First prototype (AddOns) =====

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.class wx.class]

<center>
{|
|-
| [[Image:wx.class1.png|350px|thumb|center|wx.class]]
| [[Image:wx.class2.png|350px|thumb|center|wx.class]]
| [[Image:wx.class3.png|350px|thumb|center|wx.class]]
|-
|}
</center>

Current Features:

* Does not require xterm
* works on windows which is not currently available

To be implemented:

* Proper view of histogram using python-matplotlib
* To work on other datset (currently works for nc_spm_08)
* Needs a code cleanup

===== Second prototype (trunk) =====

* [[wxIClass]]

=== Graphical Modeller ===

'''Status:''' under development.

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

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

=== Extension Manager ===

'''Status:''' under development

* [http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html wxGUI Extension Manager]

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

=== Map Calculator ===

'''Status:''' prototype implemented

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

=== GRASS Catalog ===

;'''Status:''' Under development.

* [http://lsi.iiit.ac.in/grass_addons/GRASSCatalog.tar.gz GRASS Catalog patch]

<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:''' Under development.

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

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

WxPython-based GUI for GRASS

2012-02-25T10:17:42Z

⚠️Rashadkm: /* GRASS Catalog */

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

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

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|-
|
[[Image:Wxnviz-volumes.png|300px|thumb|center|wxGUI: Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space]]
||
[[Image:wxgui-spatial-query.png|300px|thumb|center|wxGUI: Spatial query]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

== Video tutorials ==

=== Import vector data ===

* [[Import DXF]]
{{YouTube|eD2B1i9YxxQ|desc=Importing single shapefile}}
{{YouTube|ohbV_MR530Q|desc=Importing multiple shapefiles}}
{{YouTube|lJVBw78zYY0|desc=Importing SpatiaLite layers}}
{{YouTube|JoqIkL2VRVc|desc=Importing PostGIS layers into GRASS}}

=== Import raster data ===

Importing multiple GeoTIFF files:

<center>
{|
|
[[Image:WxGUI bulk raster import1.png|300px|thumb|Bulk import of GeoTIFF via menu]]
||
[[Image:WxGUI bulk raster import2.png|320px|thumb|Bulk import of GeoTIFF via menu (files are auto-selected)]]
|
|}
</center>

=== Link vector data (GRASS 7) ===

{{YouTube|eB3_SmE3E9Q|desc=Link PostGIS layers as GRASS vector maps}}

=== Map display ===

{{YouTube|PY8aytvfQqA|desc=Define legend and export to image}}

=== Georectifier ===

* Manual page of {{cmd|wxGUI.GCP_Manager|desc=GCP Manager}}

=== Graphical modeler ===

''Note:'' GRASS 6.4.2+ required.

See wxGUI [[WxGUI Modeler#Video Tutorials|Modeler]] page.

=== Layer Manager: Searching GRASS module ===

{{YouTube|Z9STgChNWcM|desc=Search for GRASS module (GRASS 6.4.2 required)}}

=== Map Calculator ===

{{YouTube|yMpVVRaVYeA|desc=Calculating NDVI}}

=== wxGUI 3D view mode (wxNviz) ===

See [[WxNviz#Video tutorials|wxNviz]] 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>

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

Manual page - {{cmd|wxGUI.Vector_Digitizer}}

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 not started yet.

* {{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.

* 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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

See also [[Georeferencing]].

; Tutorials

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

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

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

[[Image:Grass-atm-example.png|center|thumb|640px|Attributes queries in wxGUI]]
[[Image:Wxgui-attribute-table-manager.png|center|thumb|350px|Attribute Table Manager]]

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== 3D view mode ===

'''Status:''' under development (Google Summer of Code 2008/2010).

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:''' Under development.

===== First prototype (AddOns) =====

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.class wx.class]

<center>
{|
|-
| [[Image:wx.class1.png|350px|thumb|center|wx.class]]
| [[Image:wx.class2.png|350px|thumb|center|wx.class]]
| [[Image:wx.class3.png|350px|thumb|center|wx.class]]
|-
|}
</center>

Current Features:

* Does not require xterm
* works on windows which is not currently available

To be implemented:

* Proper view of histogram using python-matplotlib
* To work on other datset (currently works for nc_spm_08)
* Needs a code cleanup

===== Second prototype (trunk) =====

* [[wxIClass]]

=== Graphical Modeller ===

'''Status:''' under development.

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

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

=== Extension Manager ===

'''Status:''' under development

* [http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html wxGUI Extension Manager]

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

=== Map Calculator ===

'''Status:''' prototype implemented

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

=== GRASS Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<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:''' Under development.

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

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

File:GRASS Catalog2.png

2012-02-25T10:15:06Z

⚠️Rashadkm: grass catalog

grass catalog

File:GRASS Catalog1.png

2012-02-25T10:13:52Z

⚠️Rashadkm: new grass catalog

new grass catalog

WebGRASS

2012-01-26T08:00:46Z

⚠️Rashadkm:

{{ToModify}}

webGRASS currently allows to:
* upload a mapset/location
* select existing mapset and location
* load a vector map
* display vector/raster data
* do basic commands such as v.buffer

Need to be done
* link webGRASS with grass libraries and avoid process communication. If a process got break at some point its a mess
* imporve the command view interface
* allow user to import their own raster data(atleast any gdal supported)
* add suggestion popup for input map(raster and vector)
* read GRASS GIS data from a user through HTML5 File API
* allow user to download data in GRASS Format
* a lot more :)
Contact Us
* Anyone intersted in development please do contact
*Dr. K.S.Rajan(Project Guide) rajan [*] iiit.ac.in
*Rashad (Developer) rashadkm [*] gmail (dot) com

== Video demo version 1 ==
{{YouTube|ysoZHeKYncs}}

== Video demo latest version ==
{{YouTube|B71DQiCw86o}}

WebGRASS

2012-01-26T08:00:04Z

⚠️Rashadkm: minor edit

{{ToModify}}

webGRASS currently allows to:
* upload a mapset/location
* select existing mapset and location
* load a vector map
* display vector/raster data
* do basic commands such as v.buffer

Need to be done
* link webGRASS with grass libraries and avoid process communication. If a process got break at some point its a mess
* imporve the command view interface
* allow user to import their own raster data(atleast any gdal supported)
* add suggestion popup for input map(raster and vector)
* read GRASS GIS data from a user through HTML5 File API
* allow user to download data in GRASS Format
* a lot more :)
* Anyone intersted in development please do contact
*Dr. K.S.Rajan(Project Guide) rajan [*] iiit.ac.in
*Rashad (Developer) rashadkm [*] gmail (dot) com

== Video demo version 1 ==
{{YouTube|ysoZHeKYncs}}

== Video demo latest version ==
{{YouTube|B71DQiCw86o}}

WebGRASS

2012-01-26T07:59:24Z

⚠️Rashadkm:

{{ToModify}}

webGRASS currently allows to:
* upload a mapset/location
* select existing mapset and location
* load a vector map
* display vector/raster data
* do basic commands such as v.buffer

Need to be done
* link webGRASS with grass libraries and avoid process communication. If a process got break at some point its a mess
* imporve the command view interface
* allow user to import their own raster data(atleast any gdal supported)
* add suggestion popup for input map(raster and vector)
* read GRASS GIS data from a user through HTML5 File API
* allow user to download data in GRASS Format
* a lot more :)
* Anyone intersted in development please do contact
Dr. K.S.Rajan(Project Guide) rajan [*] iiit.ac.in
Rashad (Developer) rashadkm [*] gmail (dot) com

== Video demo version 1 ==
{{YouTube|ysoZHeKYncs}}

== Video demo latest version ==
{{YouTube|B71DQiCw86o}}

WebGRASS

2012-01-26T07:21:10Z

⚠️Rashadkm:

{{ToModify}}

webGRASS currently allows to:
* upload a mapset/location
* select existing mapset and location
* load a vector map
* display vector/raster data
* do basic commands such as v.buffer

Need to be done
* link webGRASS with grass libraries and avoid process communication. If a process got break at some point its a mess
* imporve the command view interface
* allow user to import their own raster data(atleast any gdal supported)
* add suggestion popup for input map(raster and vector)
* read GRASS GIS data from a user through HTML5 File API
* allow user to download data in GRASS Format
* a lot more :)
* Anyone intersted in development please do contact me rashadkm [*] gmail (dot) com

== Video demo version 1 ==
{{YouTube|ysoZHeKYncs}}

== Video demo latest version ==
{{YouTube|B71DQiCw86o}}

WebGRASS

2012-01-26T07:14:27Z

⚠️Rashadkm: Created page with "{{ToModify}} webGRASS currently allows to: * upload a mapset/location * select existing mapset and location * load a vector map * display vector/raster data * do basic comman..."

{{ToModify}}

webGRASS currently allows to:
* upload a mapset/location
* select existing mapset and location
* load a vector map
* display vector/raster data
* do basic commands such as v.buffer

Need to be done
* link webGRASS with grass libraries and avoid process communication. If a process got break at some point its a mess
* imporve the command view interface
* allow user to import their own raster data(atleast any gdal supported)
* add suggestion popup for input map(raster and vector)
* read GRASS GIS data from a user through HTML5 File API
* allow user to download data in GRASS Format
* a lot more :)
* Anyone intersted in development please do contact me rashadkm [*] gmail (dot) com

== Video demo old version ==
{{YouTube|ysoZHeKYncs}}

WxPython-based GUI for GRASS

2010-09-08T21:37:21Z

⚠️Rashadkm: added wx.class

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

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

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

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|-
|
[[Image:Wxnviz-volumes.png|300px|thumb|center|wxGUI: Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space]]
||
 
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

== HowTo ==

=== Import vector data ===

* [[Import DXF]]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-shp-file.html Importing single shapefile]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-shp-dir.html Importing multiple shapefiles]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-spatialite.html Importing SpatiaLite layers]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-postgis.html Importing PostGIS layers]

=== Georectifier ===

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

=== Graphical modeler ===

Note: GRASS 6.5+ required.

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-modeler-0.html Creating simple model]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-modeler-1.html Define intermediate data]

=== Layer Manager ===

Note: GRASS 6.5+ required.

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-search-module.html Searching GRASS module]

=== Map Calculator ===

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-mapcalc.html Calculating NDVI]

=== wxGUI 3D view mode (wxNviz) ===

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== 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>
{|
| [[Image:wxgrass-gis-manager-layer.png|350px|thumb|2007/12]] || [[Image:wxgrass-gis-manager-output.png|350px|thumb|2007/12]]
|-
| [[Image:Wxgrass rgb.png|350px|thumb|2008/02]] || [[Image:wxgui-layer-manager-70.png|350px|thumb|2010/08]]
|}
</center>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

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

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

See also [[Georeferencing]].

; Tutorials

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

[[Image:Wxgui-attribute-table-manager.png|center|thumb|350px|Attribute Table Manager]]

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development (Google Summer of Code 2008/2010).

See detailed information at [[wxNVIZ]] page and original TCL/TK {{cmd|version=64|nviz}} manual page.

[[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!''

=== Graphical Modeller ===

'''Status:''' under development.

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

=== Extension Manager ===

'''Status:''' under development

* [http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html wxGUI Extension Manager]

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

=== Map Calculator ===

'''Status:''' prototype implemented

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

=== Data Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<center>
{|
|-
| [[Image:Catalog.png|350px|thumb|center|Data Catalog ]]
| [[Image:Aspect.png|350px|thumb|center|Data 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
* ...

=== wx.class ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.class wx.class]

<center>
{|
|-
| [[Image:wx.class1.png|350px|thumb|center|wx.class]]
| [[Image:wx.class2.png|350px|thumb|center|wx.class]]
| [[Image:wx.class3.png|350px|thumb|center|wx.class]]
|-
|}
</center>

;Current Features:

* Does not require xterm
* works on windows which is not currently available

;To be implemented:

* Proper view of histogram using python-matplotlib
* To work on other datset (currently works for nc_spm_08)
* Needs a code cleanup

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

File:Wx.class3.png

2010-09-08T21:36:05Z

⚠️Rashadkm: Histogram drawn for a different training area

Histogram drawn for a different training area

File:Wx.class2.png

2010-09-08T21:34:40Z

⚠️Rashadkm: histogram drawn using wxpython paintDC

histogram drawn using wxpython paintDC

File:Wx.class1.png

2010-09-08T21:33:30Z

⚠️Rashadkm: wx.class region drawing

wx.class region drawing

GRASS Translation Team

2010-09-07T12:23:23Z

⚠️Rashadkm: /* Malayalam */

__NOTOC__
* Currently, [http://grass.osgeo.org/devel/i18n.php#statistics GRASS messages] are (partly) translated to 18 languages
: (cs,de,es,fr,hi,it,ja,ko,lv,mr,pl,pt_br,ru,sl,tr,vi,zh).

* Free [http://gdf-hannover.de/media.php?lg=en GRASS literature from GDF Hannover] is translated to five languages
: (cs, de, fr, zh_CN, en).

* [http://grass.osgeo.org/grass64/manuals/html64_user/index.html GRASS manual pages] are [[Updating GRASS Documentation#Translations|not yet translated]].

* Translation support pages:
: - [[GRASS messages translation]]
: - [[GRASS Translation Glossary]]
: - [[Updating GRASS Documentation#Translations]]
: - [http://grass.osgeo.org/devel/i18n.php#statistics Project translation statistics]

==Members of Translation Team==

''The list is yet incomplete (see [http://trac.osgeo.org/grass/browser/grass/trunk/translators.csv here] for full list)!''

__TOC__

===[http://grass.fsv.cvut.cz/wiki/index.php/Lokalizace Arabic]===

;Dr Alaa Ahmed Masoud
[[Image:Alaa5.jpg|100px|thumb|Dr Alaa Ahmed Masoud]]
* Location: Tanta, Egypt
* mail: alaamasoud@hotmail.com
* http://alaamasoud.tripod.com/

===[http://grass.fsv.cvut.cz/wiki/index.php/Lokalizace Czech]===
;Martin Landa
[[Image:Mlanda.png|thumb|Martin Landa]]
* Location: Prague, Czech Republic
* mail: landa.martin at gmail.com
* http://gama.fsv.cvut.cz/wiki/index.php/Martin_Landa

;Jáchym Čepický
[[Image:Jachym.png|thumb|Jáchym Čepický]]
* Location: Hannover, Germany
* mail: GRASS developers mailing list
* http://les-ejk.cz

;Záboj Hrázský
[[Image:Zaboj.png|100px|thumb|Záboj Hrázský]]
* Location: Sobětuchy, Czech Republic
* mail: GRASS developers mailing list
* http://

===German===
;Robert Nuske
* Location: Göttingen, Germany
* mail: GRASS User and Developer mailing list

;Stephan Holl
[[Image:Holl.png|100px|thumb|Stephan Holl]]
* Location: Hannover, Germany
* mail: GRASS developers mailing list
* http://www.holl-land.de/blog

;Otto Dassau
* Location: Hannover, Germany
* mail: GRASS User and Developer mailing list

===French===
;Vincent Bain
* Checks and corrections on GRASS 6 French documentation
* Location : France (Rhône-Alpes)
* mail : GRASS French Discussions List
* http://

;Daniel Calvelo Aros
* GRASS messages translation [2004-2005]
* Location : Peru
* mail : GRASS Translations List
* http://

;Laurent Courty
* GRASS messages translation [2005->], GRASS French glossary
* Location : France (Bourgogne)
* mail : GRASS Translations List
* http://

;Thierry Gonon
* MacOS GRASS start-up screens translation
* Location : France (Rhône-Alpes)
* mail : GRASS French Discussions List
* http://

;Jean-Denis Guiguère
* GRASS French glossary
* Location : Sherbrooke, Canada
* mail : GRASS Translations List
* http://www.usherbrooke.ca/geotel/temoignages/j_d_giguere.html

;Moritz Lennert
* GRASS 5 French tutorial for beginners (author & translator)
* Location : Bruxelles, Belgium
* mail : GRASS French Discussions List
* http://

;Eve Rousseau
* GRASS 6 French documentation, GRASS messages [2006->], glossary
* Location : France
* mail : GRASS Translations, GRASS French Discussions List
* http://www.portailsig.org/

;Emmanuel Sarraco
* GRASS messages translation [2004-2005]
* Location : France
* mail : GRASS Translations List
* http://

===Italian===
;Luca Delucchi
* Location : Genova/Trento (Italy)
* mail : lucadeluge at gmail.com
* http://www.lucadelu.org

===Malayalam===
;Mohammed Rashad
* Location: Kerala, India
* mail: rashadkm at gmail.com
* http://keralainfo.web4all.in

===Polish===
;Milena Nowotarska
* GRASS messages translation [2008-2010]
* Location : Szczecin, Poland
* mail : do.milenki AT gmail DOT com
* http://wiki.osgeo.org/wiki/Milena_Nowotarska

[[Category: Community]]

WxPython-based GUI for GRASS

2010-05-16T11:26:23Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

== HowTo ==

=== Import vector data ===

* [[Import DXF]]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-shp-file.html Importing single shapefile]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-shp-dir.html Importing multiple shapefiles]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-spatialite.html Importing SpatiaLite layers]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/import-postgis.html Importing PostGIS layers]

=== Georectifier ===

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

=== Graphical modeler ===

Note: GRASS 6.5+ required.

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-modeler-0.html Creating simple model]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-modeler-1.html Define intermediate data]

=== Layer Manager ===

Note: GRASS 6.5+ required.

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-search-module.html Searching GRASS module]

=== Map Calculator ===

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxgui-mapcalc.html Calculating NDVI]

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

See also [[Georeferencing]].

; Tutorials

* [http://gama.fsv.cvut.cz/~landa/grass/swf/georect.html Georectifing raster data]

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

[[Image:Wxgui-attribute-table-manager.png|center|thumb|350px|Attribute Table Manager]]

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical Modeller ===

'''Status:''' under development.

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

=== Extension Manager ===

'''Status:''' under development

* [http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html wxGUI Extension Manager]

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

=== Map Calculator ===

'''Status:''' prototype implemented

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

=== Data Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<center>
{|
|-
| [[Image:Catalog.png|350px|thumb|center|Data Catalog ]]
| [[Image:Aspect.png|350px|thumb|center|Data 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
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

GRASS Translation Team

2010-05-01T11:17:18Z

⚠️Rashadkm:

__NOTOC__
* Currently, [http://grass.osgeo.org/devel/i18n.php#statistics GRASS messages] are (partly) translated to 18 languages
: (cs,de,es,fr,hi,it,ja,ko,lv,mr,pl,pt_br,ru,sl,tr,vi,zh).

* Free [http://gdf-hannover.de/media.php?lg=en GRASS literature from GDF Hannover] is translated to five languages
: (cs, de, fr, zh_CN, en).

* [http://grass.osgeo.org/grass64/manuals/html64_user/index.html GRASS manual pages] are [[Updating GRASS Documentation#Translations|not yet translated]].

* Translation support pages:
: - [[GRASS messages translation]]
: - [[GRASS Translation Glossary]]
: - [[Updating GRASS Documentation#Translations]]
: - [http://grass.osgeo.org/devel/i18n.php#statistics Project translation statistics]

==Members of Translation Team==

''The list is yet incomplete (see [http://trac.osgeo.org/grass/browser/grass/trunk/translators.csv here] for full list)!''

__TOC__

===[http://grass.fsv.cvut.cz/wiki/index.php/Lokalizace Arabic]===

;Dr Alaa Ahmed Masoud
[[Image:Alaa5.jpg|100px|thumb|Dr Alaa Ahmed Masoud]]
* Location: Tanta, Egypt
* mail: alaamasoud@hotmail.com
* http://alaamasoud.tripod.com/

===[http://grass.fsv.cvut.cz/wiki/index.php/Lokalizace Czech]===
;Martin Landa
[[Image:Mlanda.png|thumb|Martin Landa]]
* Location: Prague, Czech Republic
* mail: landa.martin at gmail.com
* http://gama.fsv.cvut.cz/wiki/index.php/Martin_Landa

;Jáchym Čepický
[[Image:Jachym.png|thumb|Jáchym Čepický]]
* Location: Hannover, Germany
* mail: GRASS developers mailing list
* http://les-ejk.cz

;Záboj Hrázský
[[Image:Zaboj.png|100px|thumb|Záboj Hrázský]]
* Location: Sobětuchy, Czech Republic
* mail: GRASS developers mailing list
* http://

===German===
;Robert Nuske
* Location: Göttingen, Germany
* mail: GRASS User and Developer mailing list

;Stephan Holl
[[Image:Holl.png|100px|thumb|Stephan Holl]]
* Location: Hannover, Germany
* mail: GRASS developers mailing list
* http://www.holl-land.de/blog

;Otto Dassau
* Location: Hannover, Germany
* mail: GRASS User and Developer mailing list

===French===
;Vincent Bain
* Checks and corrections on GRASS 6 French documentation
* Location : France (Rhône-Alpes)
* mail : GRASS French Discussions List
* http://

;Daniel Calvelo Aros
* GRASS messages translation [2004-2005]
* Location : Peru
* mail : GRASS Translations List
* http://

;Laurent Courty
* GRASS messages translation [2005->], GRASS French glossary
* Location : France (Bourgogne)
* mail : GRASS Translations List
* http://

;Thierry Gonon
* MacOS GRASS start-up screens translation
* Location : France (Rhône-Alpes)
* mail : GRASS French Discussions List
* http://

;Jean-Denis Guiguère
* GRASS French glossary
* Location : Sherbrooke, Canada
* mail : GRASS Translations List
* http://www.usherbrooke.ca/geotel/temoignages/j_d_giguere.html

;Moritz Lennert
* GRASS 5 French tutorial for beginners (author & translator)
* Location : Bruxelles, Belgium
* mail : GRASS French Discussions List
* http://

;Eve Rousseau
* GRASS 6 French documentation, GRASS messages [2006->], glossary
* Location : France
* mail : GRASS Translations, GRASS French Discussions List
* http://www.portailsig.org/

;Emmanuel Sarraco
* GRASS messages translation [2004-2005]
* Location : France
* mail : GRASS Translations List
* http://

===Italian===
;Luca Delucchi
* Location : Genova/Trento (Italy)
* mail : lucadeluge at gmail.com
* http://www.lucadelu.org

===Malayalam===
;Mohammed Rashad
[[Image:rashadkm.png|thumb|Mohammed Rashad]]
* Location: Kerala, India
* mail: rashadkm at gmail.com
* http://keralainfo.web4all.in

File:Rashadkm.png

2010-05-01T11:14:12Z

⚠️Rashadkm:

WxPython-based GUI for GRASS

2010-02-03T17:51:36Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

[[Image:Wxgui-attribute-table-manager.png|right|thumb|350px|Attribute Table Manager]]

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<center>
{|
|-
|-
| [[Image:Catalog.png|thumb|300px|DataCatalog 3]]
|-
|}
</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.

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

=== 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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

File:Catalog.png

2010-02-03T17:47:47Z

⚠️Rashadkm: GRASS GIS DataCatalog

GRASS GIS DataCatalog

WxPython-based GUI for GRASS

2010-01-27T15:08:47Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

[[Image:Wxgui-attribute-table-manager.png|right|thumb|350px|Attribute Table Manager]]

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<center>
{|
|-
| [[Image:Data_catalog_4.png|thumb|300px|DataCatalog 1]] ||
[[Image:Data_catalog_5.png|thumb|300px|DataCatalog 2]]
|-
| [[Image:Data_catalog_6.png|thumb|300px|DataCatalog 3]]
|-
|}
</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.

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

=== 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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2010-01-27T15:07:55Z

⚠️Rashadkm: /* Data Catalog */ new displays

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

[[Image:Wxgui-attribute-table-manager.png|right|thumb|350px|Attribute Table Manager]]

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

<center>
{|
|-
| [[Image:Data_catalog_3.png|thumb|300px|DataCatalog 1]] ||
[[Image:Data_catalog_4.png|thumb|300px|DataCatalog 2]]
|-
| [[Image:Data_catalog_5.png|thumb|300px|DataCatalog 3]]
|-
|}
</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.

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

=== 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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

File:Data catalog 6.png

2010-01-27T15:05:24Z

⚠️Rashadkm: data catalog with no map layers

data catalog with no map layers

File:Data catalog 5.png

2010-01-27T15:04:24Z

⚠️Rashadkm: data catalog with vector digitizer tool & map display

data catalog with vector digitizer tool & map display

File:Data catalog 4.png

2010-01-27T15:02:38Z

⚠️Rashadkm: data catalog with simple map display

data catalog with simple map display

File:Data catalog 1.png

2010-01-27T14:56:55Z

⚠️Rashadkm: uploaded a new version of "File:Data catalog 1.png"

WxPython-based GUI for GRASS

2010-01-23T09:28:32Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

[[Image:Wxgui-attribute-table-manager.png|right|thumb|350px|Attribute Table Manager]]

;'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

;Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

[[Image:Data_catalog_1.png|right|thumb|300px|DataCatalog 1]]
[[Image:Data_catalog_2.png|left|thumb|300px|DataCatalog 1]]
[[Image:Aspect.png|center|thumb|300px|Data Catalog Map Dislay]]
[[Image:lsat_2002_10.png|center|thumb|300px|Data Catalog Another Map Display]]

;'''Status:''' Under development.

* [http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

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

;To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

=== 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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2010-01-22T15:05:29Z

⚠️Rashadkm: /* Data Catalog */ updated with screens

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.

[[Image:Data_catalog_1.png|left|thumb|520px|DataCatalog 1]]
[[Image:Data_catalog_2.png|right|thumb|520px|DataCatalog 1]]
[[Image:Aspect.png|center|thumb|900px|Map Dislay]]
[[Image:lsat_2002_10.png|center|thumb|900px|Another Map Display]]

[http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

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.

To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

File:Lsat 2002 10.png

2010-01-22T14:48:55Z

⚠️Rashadkm:

File:Aspect.png

2010-01-22T14:48:18Z

⚠️Rashadkm:

File:Data catalog 2.png

2010-01-22T14:47:09Z

⚠️Rashadkm:

File:Data catalog 1.png

2010-01-22T14:45:20Z

⚠️Rashadkm:

WxPython-based GUI for GRASS

2009-10-30T17:17:24Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.

[http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

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.

To be implemented:

* copy, move map layers in different mapsets.
* View DBF files as tables.
* Copy, delete, rename DBF files.
* Modify attribute tables.
* Viewing other formats.
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2009-10-30T16:53:49Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.

[http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog Data Catalog]

Design complex GUI for map layers management allowing:

* copy, delete, rename map layers (current mapset)
* copy, move map layers in different mapsets
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2009-10-30T16:51:37Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.

[http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog DataCatalog]
Design complex GUI for map layers management allowing:

* copy, delete, rename map layers (current mapset)
* copy, move map layers in different mapsets
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2009-10-30T16:50:30Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.
[http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/data_catalog DataCatalog]
Design complex GUI for map layers management allowing:

* copy, delete, rename map layers (current mapset)
* copy, move map layers in different mapsets
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2009-10-16T09:58:50Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' Under development.

Design complex GUI for map layers management allowing:

* copy, delete, rename map layers (current mapset)
* copy, move map layers in different mapsets
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]

WxPython-based GUI for GRASS

2009-10-16T09:57:27Z

⚠️Rashadkm: /* Data Catalog */

See also [[GRASS GUI]], [[GRASS and Python]] and [[GRASS SoC Ideas 2009‎]].

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.

== Screenshots ==

* [http://svn.osgeo.org/grass/grass-addons/screenshots/wxpython SVN]
* [http://grass.osgeo.org/screenshots/gui.php Website screenshot page]
* Various screenshots from [[:Category:WxGUI|GRASS-Wiki]]

=== GNU/Linux ===

<center>
{|
|
[[Image:Wxgui-startup-gnulinux.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-vdigit1-gnulinux.png|300px|thumb|Vector digitizer]]
|-
|
[[Image:Wxgui-atm0-gnulinux.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-vector-querying-gnulinux.png|300px|thumb|Querying vector map layers (attribute data)]]
|}
</center>

=== Mac OS ===

=== MS Windows ===

<center>
{|
|
[[Image:Wxgui-startup-windows1.png|300px|thumb|Start-up screen]]
||
[[Image:Wxgui-d-vect-windows.png|300px|thumb|GUI dialog d.vect]]
|-
|
[[Image:Wxgui-atm-windows.png|300px|thumb|Attribute Table Manager]]
||
[[Image:Wxgui-r-buffer-windows.png|300px|thumb|Running command (r.buffer)]]
|-
|
[[Image:Wxgui-vector-querying-windows.png|300px|thumb|Querying vector map layer (editable mode)]]
||
 
|}
</center>

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

<div align="center">
{|
|[[Image:wxgrass-gis-manager-layer.png|350px]] || [[Image:wxgrass-gis-manager-output.png|350px]]
|}
</div>

<div align="center">
[[Image:Wxgrass rgb.png|350px]]
</div>

=== 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>
{|
|-
| [[Image:Wxgrass-mapdisplay-0.png|thumb|350px|center]] ||
[[Image:Wxgui-mapdisplay-1.png|thumb|350px|center]]
|-
|}
</center>

=== Module GUIs ===

'''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>
<?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>

which is then used to generate:

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

=== Startup GUI ===

'''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]]

=== Cartography tools ===

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

==== GUI for ps.map ====

* [http://grass.osgeo.org/grass63/manuals/html63_user/ps.map.html ps.map] is a cartographic composer, intended to be a stand-alone hardcopy plot generator. It is not meant to be a '''Print''' button for the maps currently displayed in the map canvas, that will need it own controls.

* The GUI will prepare a semi-WYSIWYG + tree menu controls which can write a ps.map control file, and then run ps.map to create PostScript and PDF output directly. Loading a ps.map control file is harder and can happen later.

* For a start at a Tcl/Tk composer see gui/tcltk/d.m/print.tcl
: see also these discussions and pyGTK prototype by Jachym Cepicky
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/12469
:* http://thread.gmane.org/gmane.comp.gis.grass.devel/19368

* Start with most important mapping instructions
** paper
** scale
** maploc
** rast
** vects
** grids
** scalebar
** mapinfo
** text labels

===== Intelligent label placement in ps.map =====

* use PAL/JPAL [http://geosysin.iict.ch/PAL cartographic labelling library] (GPL, C++ language, JNI wrapper)

===== Outputs =====

* ps.map instructions file
* PostScript file [ps.map instructions tmp file]
* lpr [PostScript tmp file]
* PDF File (pstopdf? ps2pdf? GNU Ghostscript?) [PostScript tmp file]

===== Inputs =====

* Ability to load in saved ps.map scripts. I consider this to be a low priority, deal with it after map creation is fully functional. Start with scripts saved using the GUI, after that is working expand to load any ps.map instructions file.

===== Prototype g-ps.map =====
* [http://les-ejk.cz/files/programs/grass/gpsmap-0.1.2.tgz gpsmap-0.1.2.tgz]
* [http://les-ejk.cz/tmp/gpsmap.png g-ps.map Screenshot]
* [http://www.nabble.com/status-of-g-ps.map-tf4465835.html#a12733414 Jachym's posting]

==== Direct printing ====

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]] ||
[[Image:Wxgui-georectify-1.png|thumb|350px|center]]
|-
|}
</center>

=== Profile Analysis Tool ===

'''Status:''' prototype implemented.

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

=== Vector digitizer ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Vector_Digitizing_Tool.html Manual page].

See also [[GRASS Digitizing tool]].

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

<center>

{|
|-
| [[Image:WxDigit200804.png|thumb|300px|center|Vector digitizer (2008/04)]] ||
[[Image:Digit-01.png|thumb|300px|center|Vector digitizer (2007/11)]]
|-
| [[Image:WxGUI-vdigit-fill-area.png|thumb|300px|center|Vector digitizer - fill valid areas (closed boundary + centroid) (2008/07)]] ||
[[Image:WxGUI-vdigit-bg.png|thumb|300px|center|Vector digitizer - background raster maps with different opacity level (2008/07)]]
|-
|}
</center>

=== Raster digitizer ===

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

* r.digit (merge with v.digit?)
: Probably write a front end for [http://grass.osgeo.org/grass63/manuals/html63_user/r.in.poly.html r.in.poly], that's all the old r.digit is.
* d.rast.edit
: Idea: get cell center coords and new values from GUI interaction, then pass those through r.in.xyz, and r.patch the new values over the top of the old map.

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

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

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

* Read with one of r.category, r.describe, r.report, 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?

=== Ortho photos ===

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

* To replace i.ortho.photo and friends

=== Attribute table manager ===

'''Status:''' prototype implemented.

[http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Attribute_Table_Manager.html Manual page].

Allows:

* To browse attribute data, perform SQL select statements
* Modify attribute data, insert new records to attribute table, delete existing records
* Highlight selected items in Map Display Window
* Extract selected items into new vector map layer
* Modify attribute table - add, drop, rename columns
* Modify vector map layer DB connestion settings - add, remove or modify layers

[[Image:Wxgui-attribute-table-manager.png|center|thumb|600px|Attribute Table Manager]]

=== NVIZ replacement ===

'''Status:''' under development.

Detailed information [[wxNVIZ]].

=== Imagery tools ===

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

=== Graphical modeller ===

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

=== GEM integration ===

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

[http://trac.osgeo.org/grass/browser/grass/trunk/gem GEM] is GRASS Extension Manager. Or use the R packages approach.

=== Data Catalog ===

'''Status:''' development started.

Design complex GUI for map layers management allowing:

* copy, delete, rename map layers (current mapset)
* copy, move map layers in different mapsets
* ...

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

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

* Warning "widget class `GtkPizza' has no property named `row-ending-details'", http://trac.osgeo.org/grass/ticket/204

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

[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'' MDI (layout similar to QGIS or [http://sourceforge.net/dbimage.php?id=215336 GSDView] etc) (see figure below)
* implement ''optional'' magnetic docking of wxGUI windows to keep the windows closer
* 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>

'''What others do:'''
* QGIS: all basic parts in one frame with legend integrated: e.g. http://grass.osgeo.org/grass61/screenshots/images/qgis08_grass6_toolbox.png
* SAGA: several windows in one frame: http://www.saga-gis.uni-goettingen.de/html/images/bild8.gif and http://sourceforge.net/dbimage.php?id=44455

'''''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)

== HowTo ==

* [[Import DXF]]

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

[[Category:Development]]
[[Category:GUI]]
[[Category:Python]]