[SoC] [Report #2] Kriging with GRASS and R: v.autokrige port
to wxPython and more
a.ghisla at gmail.com
Sat Jun 13 04:45:48 EDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Michael Barton ha scritto:
> The wxPython interface looks good. I'd stick with the notebook over
> choicebook because you can easily see the options with a notebook
> without clicking anything.
> We use a flatnotebook control for the GRASS GUI if you'd like to make
> this visually compatible (not obligatory, though aesthetically
> consistent). We use the V8 style tab and some nice colors too. You can
> look at the GUI code for ideas if you want.
Yes, I saw that code in Layer Manager, going to integrate in kriring
> If someone does not have one of the programs installed, does the error
> message suggest the needed URL to get it?
I don't know if the popup message is a good place to store all the info
about missing dependencies. I plan to make the error message point to
exhaustive documentation page(s) of the module, but I'm open to any
> On Jun 11, 2009, at 9:50 AM, Anne Ghisla wrote:
> Hello all,
> there are some important news about the module!
> First of all, the interface is almost finished. See a screenshot on the
> wiki page .
> The layout includes a notebook with a page for each R package (automap,
> gstat and geoR), with the available options. Another layout could be a
> chiocebox wht the three packages on the top of Kriging section, that
> redraws the section accourding to the user's choice.
> Let me know which one do you prefer, feel free also to suggest something
> The R-GRASS integration is on its way: autofitting the variogram on a
> map obtained from a DEM sample  works in the proof of concept. rpy2
> is extremely helpful and does not require much more code than the
> original R code. More to come in the next days.
> The idea for variogram fitting is to plot the variogram in a new frame
> and add some controls like sliders and/or text boxes to fill up with
> nugget, sill and range values. This will involve Python graphics, not R,
> as the former is more flexible.
> Comments, suggestions, critics are welcome!
> best regards and happy coding to everyone,
>  http://grass.osgeo.org/wiki/V.autokrige_GSoC_2009
>  http://casoilresource.lawr.ucdavis.edu/drupal/node/442
SoC mailing list
SoC at lists.osgeo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the SoC