- Discussion about the suitability of the proposed change on the talk side of this wiki page; discussion of the possible method on this side of the page.
That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.
Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python
Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.
I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)
So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:
1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch
for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.
There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...
Current repository layout
Proposed repository layout
Toolbox is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using g.extension
g.extension toolbox=hydrology operation=add
Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.
Give the possibility with a flag (like -a) to install also modules from addons related that toolbox
g.extension -a toolbox=hydrology operation=add
g.extension toolbox=hydrology operation=remove
- list of modules of selected toolbox
g.extension -l toolbox=hydrology
User can also add/remove selected module
g.extension module=r.stream.angle operation=add
List of toolboxes
||All `r3.*` modules
||All `db.*` modules
||v.krige maybe other
||r.watershed, r.terraflow, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
||All `i.*` modules, selected r.* modules
||All `r.li.*` modules, maybe other
||All `v.lidar.*` modules, v.surf.bspline, r.in.xyz
|Linear Reference Systems
||All `v.lrs.*` modules
||All `v.net.*` modules, maybe other
||A lot of basic `r.*` modules (like r.buffer, r.reclass, r.fillnull...)
||Different kind of analysis: soil (r.sun,), terrain (r.slope.aspect, r.los), geomorphometry (r.param.scale)
||A lot of basic `v.*` modules (like v.buffer, v.centroid, v.overlay...)
HM comment: do we need import/export Toolbox for all of the specialized *.in* and *.out.* commands? gdal/ogr commands should be in core.
List of modules (trunk)
List of selected AddOns modules
See GRASS AddOns for full list of available modules. Feel free to extend this list.
How to implement
- add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional
- create a script to generate a xml file for each toolbox
- add toolbox option in g.extension to read the xml and install the modules