V.krige GSoC 2009: Difference between revisions
m (ops, typo in category name) |
⚠️AnneGhisla (talk | contribs) (updated with comentor and documentation info) |
||
| Line 1: | Line 1: | ||
=== v.autokrige: Python porting and wxPython GUI addition === | === v.autokrige: Python porting and wxPython GUI addition === | ||
Anne Ghisla's Google Summer of Code 2009 project, mentored by Martin Landa | Anne Ghisla's Google Summer of Code 2009 project, mentored by Martin Landa and Michael Barton | ||
== Aim of the project == | == Aim of the project == | ||
| Line 9: | Line 9: | ||
== State of the art == | == State of the art == | ||
Documenting. | Documenting. There are (have been) some GRASS modules that perform kriging, like v.surf.krige, v.variogram and s.surf.krig that deserve consideration, as well as scripts including R and spgrass6. | ||
== Planned Timeline == | == Planned Timeline == | ||
Revision as of 12:38, 13 May 2009
v.autokrige: Python porting and wxPython GUI addition
Anne Ghisla's Google Summer of Code 2009 project, mentored by Martin Landa and Michael Barton
Aim of the project
As GRASS presently lacks kriging capability, it is performed via an add-on, v.autokrige, that delegates analysis to R (package automap). This module is written in bash and has the classical autogenerated GUI. The project aims to rewrite the module in Python, creating a new GUI in wxPython that allows the user to refine parameters. I therefore plan to examinate present v.autokrige code and port it into Python, possibly improving it at the same time, and add a wxPython GUI. All time left will be dedicated to addition of further functionality, in respect of the most needed.
State of the art
Documenting. There are (have been) some GRASS modules that perform kriging, like v.surf.krige, v.variogram and s.surf.krig that deserve consideration, as well as scripts including R and spgrass6.
Planned Timeline
ToDo