GRASS SoC Ideas 2011
This is the GRASS page for Google Summer of Code 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.
- OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
- Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
- More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers
See GSoC timeline
- √ Mentoring organization applications open (March 11)
- √ Accepted mentoring organizations announced (March 18)
- √ Interested students should initiate preliminary discussions with projects (March 18-27)
- √ Student applications open (March 28)
- √ Deadline for student's applications (April 8)
- Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.
- √ Mentor assignments and application reviews deadline (April 22)
- √ Accepted proposals announced (April 25)
- √ Community bonding time (getting to know the students)
- √ Work Begins (May 23)
- √ Midterm evaluation (July 11-15)
- √ Pencils down! (August 15)
- √ Final evaluations submitted to Google (August 22)
- √ Final results of GSoC 2011 announced (August 29)
- √ Students can begin submitting required code samples to Google (August 30)
- List ideas
- Assign Mentors to Ideas
- Notify OSGeo
- Mentors evaluate student applications
- Accepted students announced
- Students subscribe to the grass-dev mailing list and introduce themselves
- Mentor will create directory structure in the GRASS add-ons SVN for projects and setup access for students
- Coding begins...
- Students and mentors: Complete the Mid-term survey
- Final commit and packaging for Google
- Also review ideas from 2007, 2008, 2009, and 2010 which are still open.
- Project ideas of your own are also most welcome.
- Offer also (optional) "conventional" GUI layout: For some users, the current approach of separate windows (SDI) leads to a windows flooding. This is a common complaint especially from newbies. 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: example 1 and example 2. On a dual-screen this may sum up to 50cm of distance! The idea is to capture all those windows in one frame. For details, see WxGUI#Layout.
- Add WMS and/or TiledMapService and/or WMS-T layer support for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response. Accepted as WXGUI WMS service rendering GSoC 2011.
- Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules NVIZ's animation tools, and the Movies creation wiki page. (co-mentor Helena Mitasova). This was implemented outside GSoC as (GRASS Animation Tool) and (GRASS Mapswipe). , ,
- Develop a sophisticated GUI for r.stream modules. The advantage of such GUI is to allow the user to have a simple approach to a sophisticated thing like hydrology.
- Add OpenMP parallelization where appropriate, for example , , . It is important to understand which modules are processor bound, and concentrate on them. i.e. do not needlessly complicate the code of non-long running processor bound modules. A good working knowledge of ANSI C and OpenMP is required.
- r.in.modis a module to import MODIS products. It will be able to download tile/s and import it/them. It will create also the mosaic from original MODIS tiles and import it. (Proposed by lucadelu with MarkusN like mentor) Accepted as R.modis GSoC 2011, see also addon.
- Add OpenMP parallelization where appropriate, for example, and (co-mentor Helena Mitasova) . See above idea in the Raster section.
- Better support for wrap-around at 180 longitude: Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
- Add break lines support to interpolation modules (Geospatial Analysis - a comprehensive guide. 3rd edition for description. [*] well, some support exists, see . , , ). Current implementations provide no support to specify locations of cliffs or faults* thus leading to improper results within non-continous datasets. See
- Speed up wxGUI handling and 2D display of large point clouds (several million points)
- This is likely to include additional "Level-1 Vector" support in the backend modules (for which a working knowledge of ANSI C is req'd).
- GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
- We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
- In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
- Implement OpenMP (multithreading) as much as possible (where appropriate)
- Your idea here
Willing to Mentor: (your name here)
- Optimize OGSF (and NVIZ/wxNVIZ) to display large 3D point clouds with uninterupted tought speed. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
- Design and implement text displaying and styling in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
- Design and implement user-provided symbol support in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
- Add/fix missing features to wxNVIZ (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
- Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).
Willing to Mentor: Martin Landa (for 2), co-mentor for 1 and 4: Helena Mitasova, (your name here)
- implement color management for 3D rasters : r3.colors (implemented in 2011)
- develop r3.flow for computing 3D flow lines and 3D flow accumulation from 3D rasters (implemented in GSoC 2014)
- enhance volume interpolation module for handling of data in space-time cube, including computation of gradients and hypercurvatures
Willing to Mentor: co-mentor Helena Mitasova, (your name here)
- Design and implement modern metadata management system for GRASS to support OGC CSW and INSPIRE discovery a view services
- Design sophisticated Python scripting interface for GRASS based on GRASS Python Scripting Library
- Your idea here
Willing to Mentor: (your name here)
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 our dev-mailing list, or come and talk to us in IRC (#grass). You can also reach the mentors directly by emailing:
- The OSGeo SoC mailing list
- Wolf Bergenheim (wolf+grass at bergenheim.net)
Getting started with GRASS coding
- The source code is maintained in a SVN server which is easy to browse
- Please review the submitting files for our coding standards
- for C coding rules
- for Python coding rules
- for Documentantion coding rules
- There is lots of good info at the GRASS Developer's wiki
- See also the development section of the GRASS user's wiki
Guidelines for Mentors
- Unofficial book: http://www.booki.cc/gsoc-mentoring/
- Completion of wxGUI Nviz extension for 3D data visualization in GRASS GIS
- Graphical User Interface for the hydrological tools r.stream* in GRASS GIS
- GRASS WXGUI WMS service rendering
- r.in.modis for GRASS GIS