GRASS SoC Ideas 2008

From GRASS-Wiki
Revision as of 13:58, 12 March 2008 by Paul K (talk | contribs) (3D Visualization)

Jump to: navigation, search


This is the GRASS page for Google Summer of Code 2008. Here we will list project ideas and and other information related to the GRASS GSoC projects.


Required Steps

  • List ideas
  • Assign Mentors to Ideas
  • Notify OSGeo
  • Process Student Applications. Deadline XXX
  • April 14th: Accepted Students Announced
  • SVN branches and access for students
    • Create a Wiki page for each accepted project, to be used as a progress reporting tool
  • Coding begins...
  • Students and mentors: Complete the Mid-term survey.
  • Final commit and packaging for Google.


Here are some ideas you can base your application on


These project ideas have to do with the new GUI of GRASS

3D Visualization

3-D visualization in GRASS is currently achieved using the ageing "Nviz" tool. Nviz is a hybrid Tcl/TK and C application, which makes extending and improving it a very complicated task. GRASS is moving to a new wxPython-based GUI and the task of 3-D visualization needs to be integrated with this new GUI.

This is potentially a very large task, but in 3 months we would expect to have a workable demo (but release quality code ;)) to display surface(s) in 2D and smoothly transfer the view into 3D. GUI needs to be consistent with the new wxPython GUI for GRASS.

NVIZ is itself a frontend to the underlying OpenGL gsurf library (part of GRASS) which reads GRASS datasets and interfaces with OpenGL at a C API level. It is anticipated that this approach will be retained with the new GUI. Thus one approach to the task might be to "clean and tidy" this library and develop a modular interface to it, i.e. to develop individual GRASS modules to access the 3-D visualization functionality directly without having to use NVIZ. This would make the 3-D visualization capabilities of GRASS "scriptable" and possible to run in a modular way from any GUI toolkit. The development of a wxPython frontend would then be a simple exercise in user interface design and consistent with the way the GUI interfaces with other GRASS modules (other than v.digit, which is also a hybrid C application).

Other approaches may also be possible. You should keep in mind that the code has to be very well documented (even insanely well) to facilitate better expandability.

Willing to Mentor:Wolf Bergenheim, Michael Barton, Paul Kelly

Color management

GRASS has good color management features, but lacks a good UI to mange colors.

Your job would be to extend the wxPython GUI to

  1. Create a color and interval editor tool which should be able to create files which are compatible with r.reclass, r.colors and friends.
  2. A similar tool for vector data would also be very nice, which would simply store the colors in the GRASSRGB column of the attribute table.
  3. For added fun a C library that implements things such as "natural breaks" and others which could then also be used by r.reclass, v.reclass and possibly other modules that need to break number ranges into discrete classes.

Willing to Mentor:Wolf Bergenheim, Michael Barton


GRASS has excellent SQL support, however many people who are using GRASS are not SQL gurus.

Your job would be to create a SQL query builder to help build SQL queries. Additional cool features are welcome!

Willing to Mentor:Wolf Bergenheim, Michael Barton


Currently GRASS has no native support for Kriging. Kriging is done either with the R package or with the GStat package. Both are command driven and thus a GUI could be created to control the program. R could be maybe called directly or via a script to do the variograms etc.

Your job would be to grate a GUI (in wxPython) that can:

  1. Do Kriging based on gstat.
    • Create and edit GStat command files
    • Call gstat to do variogram analysis
    • Call gstat to do the actual Kriging.
  2. Do Kriging based or R
    • Create and edit R scripts
    • Call R to do variogram analysis. For efficiency the R environment should be done
    • Call R to do the actual Kriging. This includes importing the result back to GRASS.

Willing to Mentor:Wolf Bergenheim, Michael Barton


GRASS is mainly focused on Analysis, but it also has good map making tools. These tools lack a good GUI.

Your job would be to create a GUI for the tool which creates postscript maps. This would be a first step towards a graphical cartography tool for GRASS

Willing to Mentor: Michael Barton, Hamish Bowman


Your job would be to make v.what take xy coordinates (single xy or line of xy's with a buffer distance to find stuff within that buffer distance of the coordinates; set of at least 3 xy's to ID a polygon and find the stuff within it).

Willing to Mentor: Michael Barton


These projects involve the GRASS raster library.


GRASS can link to external vectors (as well as importing them) vi the GDAL OGR library. On the raster side on is unfortunately limited to importing raster maps.

Your job would be to create this r.external too for GRASS.

This project will be done in cooperation with GDAL.

Willing to Mentor: Wolf Bergenheim (GRASS), Frank Warmerdam (GDAL)

Raster Database

In GRASS vector maps can be connected to a database table as an attribute table. Many commercial GIS packages also allow this for raster maps.

Your job would be to implement this connection.

Willing to Mentor: Wolf Bergenheim

Raster Objects

Implement an equivalent of eCognition's object-based classification (in contrast to pixel-based classification)


These ideas relate to the Vector library of GRASS.

v.buffer and v.parallel

These two modules are broken and need to be reimplemented.

Willing to Mentor: Wolf Bergenheim

Implement file based spatial index

Read "Keep topology and spatial index in file instead of in memory" in Radim's Vector ToDo Willing to Mentor: Wolf Bergenheim

v.voronoi / v.delauny

These modules need to be reimplemented as they are quite old an sub-optimal. There are many good algorithms that can be used.

v.generalize take two

Last year Daniel Bundala created the v.generalize module, and implemented many line generalization algorithms.

This year we'd like to expand the module with implementing algorithms to do the following methods (as defined by McMAster)

  • merging
  • exaggeration
  • collapse
  • point aggregation

Willing to Mentor: Wolf Bergenheim


Extend v.overlay to allow all types of overlay operations for all types of vector (i.e. also points and lines)

Willing to Mentor: Wolf Bergenheim

Uniforming vector modules

GRASS has over 100 vector modules (many of which have multiple functions), and many of these modules very different input parameters, and lach where= and cats= parameters.

Your job would be to clean up these modules and that way ease the learning curve of GRASS

Willing to Mentor: Wolf Bergenheim

Guidelines for Students

How do you maximize your chances of getting picked? First read the Google SoC FAQ. Then talk to us about your idea. Try emailing the mentor directly, or come and talk to us in IRC (#grass).

Accepted Ideas