[GRASS-dev] [GRASS GIS] #3136: move v.krige to addons

#3136: move v.krige to addons
-------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
     Type: task | Status: new
Priority: normal | Milestone: 7.2.0
Component: Addons | Version: unspecified
Keywords: | CPU: Unspecified
Platform: Unspecified |
-------------------------+-------------------------
I suggest to move `v.krige` from main repository to addons before
releasing 7.2.0. The module is not mature enough, and relies on external
dependency (`rgrass7`). Such module should be distributed as addons and
not as a part of core distribution.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3136&gt;
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Changes (by neteler):

* priority: normal => blocker

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3136#comment:1&gt;
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by mlennert):

Replying to [ticket:3136 martinl]:
> I suggest to move `v.krige` from main repository to addons before
releasing 7.2.0. The module is not mature enough, and relies on external
dependency (`rgrass7`). Such module should be distributed as addons and
not as a part of core distribution.

+1

But this also means that GRASS GIS does not have any native kriging
anymore, only 2 extensions (v.krige and v.kriging). It would be great to
one day have a native implementation in core.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3136#comment:2&gt;
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by lucadelu):

Yes, I think we could need, it could be a next year GSoC.

Here some link to Python libraries if needed
[https://github.com/bsmurphy/PyKrige PyKrige],
[https://sourceforge.net/p/geoms2/wiki/Kriging/ simple kriging] or another
[http://connor-johnson.com/2014/03/20/simple-kriging-in-python/ simple
implementation]

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3136#comment:3&gt;
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by mlennert):

Replying to [comment:3 lucadelu]:
> Yes, I think we could need, it could be a next year GSoC.
>
> Here some link to Python libraries if needed
[https://github.com/bsmurphy/PyKrige PyKrige],
[https://sourceforge.net/p/geoms2/wiki/Kriging/ simple kriging] or another
[http://connor-johnson.com/2014/03/20/simple-kriging-in-python/ simple
implementation]

I would say that v.kriging is an excellent starting point as it provides a
native implementation in C, and provides 2D and 3D kriging. It could
probably be made a bit more grass-like, including by abandoning the use of
gnuplot and replacing it by a combination of v.kriging plus g.gui.kriging
or something like that, where the first works non-gui and the second
provides the necessary GUI elements. But I think that with a little
support from a more experienced GRASS C programmer, this could be made
into a core GRASS module (it already does work and provide results). Maybe
with an r.kriging as a corollary.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3136#comment:4&gt;
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by martinl):

In [changeset:"69397" 69397]:
{{{
#!CommitTicketReference repository="" revision="69397"
v.krige remove from core distribution (see #3136 for details)
}}}

--
Ticket URL: </ticket/3136#comment:5>
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by martinl):

In [changeset:"69398" 69398]:
{{{
#!CommitTicketReference repository="" revision="69398"
v.krige removed from core distribution (see #3136 for details)
}}}

--
Ticket URL: </ticket/3136#comment:6>
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

Comment (by martinl):

In [changeset:"69399" 69399]:
{{{
#!CommitTicketReference repository="" revision="69399"
v.krige moved to addons (see #3136 for details)
}}}

--
Ticket URL: </ticket/3136#comment:7>
GRASS GIS <https://grass.osgeo.org>

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: closed
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: fixed | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Changes (by martinl):

* status: new => closed
* resolution: => fixed

Comment:

`v.krige` and its GUI (`vkrige.py`) has been removed from trunk and
relbr72. The module `v.krige` is now part of addons. Since removal from
relbr70 is not planned, I am taking liberty to close this ticket. And,
yes, would be nice to have native implementation in G74, probably based on
`v.kriging`...

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/3136#comment:8&gt;
GRASS GIS <https://grass.osgeo.org>

2016-08-30 11:26 GMT+02:00 GRASS GIS <trac@osgeo.org>:

#3136: move v.krige to addons
--------------------------+-------------------------
  Reporter: martinl | Owner: grass-dev@…
      Type: task | Status: new
  Priority: blocker | Milestone: 7.2.0
Component: Addons | Version: unspecified
Resolution: | Keywords:
       CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------

I would say that v.kriging is an excellent starting point as it provides a
native implementation in C, and provides 2D and 3D kriging. It could
probably be made a bit more grass-like, including by abandoning the use of
gnuplot and replacing it by a combination of v.kriging plus g.gui.kriging
or something like that, where the first works non-gui and the second
provides the necessary GUI elements.

It would be great if v.kriging will become a native implementation once. I
still keep developing it - I have replaced kd-tree from PCL library by
R-tree implemented in GRASS GIS and now I must deal with optimization of
the final phase (interpolation itself). It takes too much time (PCL version
used to be too slow as well).

But I think that with a little
support from a more experienced GRASS C programmer, this could be made
into a core GRASS module (it already does work and provide results). Maybe
with an r.kriging as a corollary.

I would be grateful for any suggestions or advices.

Eva