GRASS SoC Ideas 2012: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
mNo edit summary
(init)
Line 9: Line 9:


* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012|main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].
* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012|main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].
----
__TOC__
== About ==
This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.
* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]
Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* 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
== Timeline ==
* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''
== Required Steps ==
* List ideas
* Assign Mentors to Ideas
* Notify OSGeo
* Mentors evaluate student applications
* Accepted students announced
* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves
* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** 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
== Ideas ==
* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], [[GRASS SoC Ideas 2010#Ideas|2010]], and [[GRASS SoC Ideas 2011#Ideas|2011]]  which are still open'''.
* Project ideas of your own are also most welcome and often the best.
=== wxGUI ===
<ol>
<li> 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:  [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! The idea is to capture all those windows in one frame. For details, see [[WxGUI#Layout]].
<center>
[[Image:Wxgui_current.png|300px|thumb|left|Current wxGUI layout with detached window components]]
[[Image:Wxgui_proposal.png|300px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
</center>
<li> 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. [[WXGUI WMS service rendering GSoC 2011|GRASS WXGUI WMS service rendering project GSoC wiki page]]
<li> 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 {{cmd|xganim}}, {{cmd|r.out.mpeg}}, [[NVIZ]]'s animation tools, and the [[Movies]] creation wiki page. (co-mentor Helena Mitasova).
<li> 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.
</ol>
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')
=== Raster ===
# Add '''[[OpenMP]] parallelization''' where appropriate, for example {{cmd|r.cost}}, {{cmd|r.surf.contour}}, {{cmd|r.watershed}}. 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 [[User:lucadelu|lucadelu]] with [[User:Neteler|MarkusN]] like mentor)
# ''Your idea here''
'''Willing to Mentor:''' (''your name here'')
=== Vector ===
# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|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''' ({{cmd|v.surf.rst}}, {{cmd|v.surf.idw}}, {{cmd|v.surf.bspline}}). Current implementations provide no support to specify locations of cliffs or faults* thus leading to improper results within non-continous datasets. See [http://www.spatialanalysisonline.com/output/html/Breaklinesandnaturalboundaries.html Geospatial Analysis - a comprehensive guide. 3rd edition] for description. [*] well, some support exists, see {{AddonCmd|v.surf.icw}}.
# 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).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], (''your name here'')
=== Imagery ===
# 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''
See the [[Image_processing#Ideas_collection_for_improving_GRASS.27_Image_processing_capabilities|ideas for imagery improvement]] and [http://trac.osgeo.org/grass/wiki/Grass7/ImageryLib GRASS 7 ideas] wiki pages for more details.
'''Willing to Mentor:''' (''your name here'')
=== 3D visualization ===
# 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:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')
=== Volume modeling ===
# implement color management for 3D rasters : '''r3.colors'''
# develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures
'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')
=== Other ===
# Design and implement modern '''metadata management system''' for GRASS to support [http://www.opengeospatial.org/standards/cat OGC CSW] and INSPIRE discovery a view services
<!--
# Design '''GRASS toolboxes environment''', see [[GRASS repository layout proposal]] for detailed information. This would also include general clean up and organization of existing GRASS modules in trunk and add-ons.
-->
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html 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 [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)
=== Getting started with GRASS coding ===
* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{src|SUBMITTING_PYTHON|branch=trunk}} for Python coding rules
** {{src|SUBMITTING_DOCS|branch=trunk}} for Documentantion coding rules
* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki
== Guidelines for Mentors ==
* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
*
== Accepted Ideas ==
# ''Project name 1''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name 2''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)
[[Category:Development]]
[[Category:Community]]
[[Category:GSoC]]

Revision as of 11:01, 11 February 2012

@ @


About

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

Promotion: 

* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf (todo)


Timeline


Required Steps

  • List ideas
  • Assign Mentors to Ideas
  • Notify OSGeo
  • Mentors evaluate student applications
  • Accepted students announced
  • Mentor will create directory structure in the GRASS add-ons SVN for projects and setup access for students
    • Students must read and post agreement to RFC2 to the grass-psc mailing list to gain SVN access
    • 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

Ideas

  • Project ideas of your own are also most welcome and often the best.


wxGUI

  1. 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.
    Current wxGUI layout with detached window components
    Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
  2. 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. GRASS WXGUI WMS service rendering project GSoC wiki page
  3. 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 xganim, r.out.mpeg, NVIZ's animation tools, and the Movies creation wiki page. (co-mentor Helena Mitasova).
  4. 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.

Willing to Mentor: Martin Landa, Maris Nartiss, Markus Metz, (your name here)

Raster

  1. Add OpenMP parallelization where appropriate, for example r.cost, r.surf.contour, r.watershed. 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.
  2. 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)
  3. Your idea here

Willing to Mentor: (your name here)

Vector

  1. Add OpenMP parallelization where appropriate, for example, v.surf.rst and v.vol.rst (co-mentor Helena Mitasova) . See above idea in the Raster section.
  2. 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.
  3. Add break lines support to interpolation modules (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of cliffs or faults* thus leading to improper results within non-continous datasets. See Geospatial Analysis - a comprehensive guide. 3rd edition for description. [*] well, some support exists, see v.surf.icw.
  4. 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).

Willing to Mentor: Martin Landa, Markus Metz, (your name here)

Imagery

  1. 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.
  2. Implement OpenMP (multithreading) as much as possible (where appropriate)
  3. Your idea here

See the ideas for imagery improvement and GRASS 7 ideas wiki pages for more details.

Willing to Mentor: (your name here)

3D visualization

  1. 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.
  2. 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.
  3. 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.
  4. 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)
  5. 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)

Volume modeling

  1. implement color management for 3D rasters : r3.colors
  2. develop r3.flow for computing 3D flow lines and 3D flow accumulation from 3D rasters
  3. enhance volume interpolation module v.vol.rst for handling of data in space-time cube, including computation of gradients and hypercurvatures

Willing to Mentor: co-mentor Helena Mitasova, (your name here)

Other

  1. Design and implement modern metadata management system for GRASS to support OGC CSW and INSPIRE discovery a view services
  2. Design sophisticated Python scripting interface for GRASS based on GRASS Python Scripting Library
  3. 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:

Getting started with GRASS coding

  • The source code is maintained in a SVN server which is easy to browse
See also the development section of the GRASS user's wiki

Guidelines for Mentors


Accepted Ideas

  1. Project name 1
    Student: Your name here
    Mentor: Your mentor's name here
    Backup mentor: Your backup mentor's name here
    Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
  1. Project name 2
    Student: Someone else's name here
    Mentor: Their mentor's name here
    Backup mentor: Their backup mentor's name here
    Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)
Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=GRASS_SoC_Ideas_2012&oldid=14850"