Talk:GRASS Community Sprint Prague 2012

From GRASS-Wiki
Revision as of 08:52, 25 May 2012 by MilenaN (talk | contribs) (→‎Digitizing toolbar: added refresh problem)
Jump to navigation Jump to search


Martin Landa

Markus Neteler

  • Fundraising for this Community Sprint (with great help from Arnulf Christl)
  • PSC composition discussion

Wishes for the Community Sprint

  • Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
    • exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- rephrase title?
      • make use of existing grass modules list(s), like (this old) GRASS GIS 6.3 Command list (PDF document)
      • visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
      • ignore modules which cannot be visualised?
    • check if (and some-how) task-oriented visual examples could be build out of per-modules examples
    • setup specific styling rules (?)
      • only one descriptive sentence per module or task
      • visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
      • limited caption(s) describing visuals
    • end-up with some independent and beautiful TeXy PDF
    • visually enrich existing manuals and/or grass-wiki
    • or consider Sphinx
  • Review of the python + ctypes example scripts.
The examples given in the code for doc/python/, and on the Ctypes wiki page have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.
  • Extend r.colors documentation by an example for a user-generated logarithmic color table.

Testing by power users

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check


Discuss role and current composition of GRASS-PSC:

  • Every year members are requested to confirm to continue their work in the PSC.
  • After the Community Sprint 2012, the Chair will request updates to the RFC1 from the PSC members.
  • Answer within five business days needed.
  • In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
  • To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at RFC1).

Further issues:

  • Discuss Google Summer of Code (two students are here)
  • Discuss GRASS 6.4.3 and 7.0 release schedule
  • Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki (example)


there is Compilation on MS-Windows
  • Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013




  • continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

QGIS-Sextante-GRASS interface

Update the GDAL-GRASS interface to GRASS 7

Rules Based programming and Agent Based Modelling

  • Tutorial/Documentation on g.infer
  • r.agent in GRASS 7

Time series

Automated command user statistics

  • modify g.parser to write out the list of used commands (without parameters) into a text file for simple, automated command user statistics

Mobile: inventory of mobile and touch implementations

  • Geopaparazzi,
  • GRASS on Android (patches by MN)

Cloud computing

  • cluster usage best practices

GSoC 2012

  •* front end, WMS
  • Python API
  • Image Segmentation


  • PostGIS Topology support
  • New features for vector engine
  • Discuss Toolbox concept
  • Discuss how to implement GRASS Metadata Management

Model integration

GRASS modules fixes

  • i.atcorr debugging
    • Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
    • Under certain circumstances i.atcorr produces NULL data
  • GRASS 6.4.3 - Release critical issues to be fixed

Signal handling

  • The Python based scripts should catch CTRL-C to avoid that clutter is left behind and that ugly traceback is printed into the terminal.

Suggestion by Anne Ghisla (yet not working... ):

Index: lib/init/
--- lib/init/   (revision 51604)
+++ lib/init/   (working copy)
@@ -30,7 +30,12 @@
 import subprocess
 import re
 import platform
+import signal
+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
 # Variables substituted during build process
 if os.environ.has_key('GISBASE'):
     gisbase = os.environ['GISBASE']

  • Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

Fix wxGUI problems

A. Clerici: please fix:

  • ticket
  • ticket
  • wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
    • In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
    • In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
    • the option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
      • Load and display the aspect (Spearfish) map.
      • Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution.
      • Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map.
      • To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same
      • The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
  • Fix wx0..6 monitors


Optionally, have all-in-one GUI window (requested by many new users!):

Current wxGUI layout with detached window components
Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)

Proposed solution: wxLayoutAlgorithm(), see WxGUI#What_others_do

work on for GRASS7

Saving History

  • when using the wxGUI, it needs to write back to the shell history
`cat wxgui_history.log >> $MAPSET/.bash_history`
Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

Digitizing toolbar

  • missing string "Select vector map" from the drop-down widget on digitizing toolbar
on winGRASS, nightly build of 24th May
  • after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.