Opened 8 years ago
Closed 8 years ago
#3136 closed task (fixed)
move v.krige to addons
Reported by: | martinl | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 7.2.0 |
Component: | Addons | Version: | unspecified |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | Unspecified |
Description
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.
Change History (8)
comment:1 by , 8 years ago
Priority: | normal → blocker |
---|
comment:2 by , 8 years ago
follow-up: 4 comment:3 by , 8 years ago
Yes, I think we could need, it could be a next year GSoC.
Here some link to Python libraries if needed PyKrige, simple kriging or another simple implementation
comment:4 by , 8 years ago
Replying to lucadelu:
Yes, I think we could need, it could be a next year GSoC.
Here some link to Python libraries if needed PyKrige, simple kriging or another 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.
comment:8 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
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
...
Replying to martinl:
+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.