V.krige GSoC 2009: Difference between revisions
⚠️AnneGhisla (talk | contribs) (updated state of the art and timeline) |
⚠️AnneGhisla (talk | contribs) mNo edit summary |
||
| 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 and Michael Barton | Anne Ghisla's [http://socghop.appspot.com/student_project/show/google/gsoc2009/osgeo/t124023165994 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 == | ||
* Writing the wxPython interface - have a look at it from svn: | |||
svn co https://svn.osgeo.org/grass/grass-addons/vector/v.autokrige2 v.autokrige2 | |||
It is now a bare grey square with a statusbar and a title. More to come :) | |||
Obtained ArcGIS availability for comparison of interface and functionality, because it is the widespread tool used for kriging | * Documenting. There are (have been) some GRASS modules that perform kriging, like: | ||
** v.surf.krige, v.variogram: no longer developed by authors, difficult to port. | |||
** s.surf.krig: deprecated since GRASS 6 series. | |||
** scripts including R and spgrass6: are the concrete basis upon which build the module. | |||
* Call for users has been done on gfoss.it, grass-it and grass-users, r-sig-geo and r-sig-ecology mailing lists. Thanks for Giovanni Manghi from | |||
GFOSS.pt and João Tiago for info. | |||
* Obtained ArcGIS availability for comparison of interface and functionality, because it is AFAIK the widespread tool used for kriging | |||
== Planned Timeline == | == Planned Timeline == | ||
Revision as of 15:21, 21 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
- Writing the wxPython interface - have a look at it from svn:
svn co https://svn.osgeo.org/grass/grass-addons/vector/v.autokrige2 v.autokrige2
It is now a bare grey square with a statusbar and a title. More to come :)
- Documenting. There are (have been) some GRASS modules that perform kriging, like:
- v.surf.krige, v.variogram: no longer developed by authors, difficult to port.
- s.surf.krig: deprecated since GRASS 6 series.
- scripts including R and spgrass6: are the concrete basis upon which build the module.
- Call for users has been done on gfoss.it, grass-it and grass-users, r-sig-geo and r-sig-ecology mailing lists. Thanks for Giovanni Manghi from
GFOSS.pt and João Tiago for info.
- Obtained ArcGIS availability for comparison of interface and functionality, because it is AFAIK the widespread tool used for kriging
Planned Timeline
Draft:
- create a wxPython interface with most used functions. Will follow Humane Interface rules [1].
- midterm deadline: have a wxPython interface that performs ordinary kriging.
[1] Jef Raskin, 2000: The Humane Interface: New Directions for Designing Interactive Systems (ISBN 0-201-37937-6)