[GRASS-dev] On post-processing a raster map's mapcalc related history string

Vaclav Petras wenzeslaus at gmail.com
Thu Aug 23 16:09:47 PDT 2018

On Thu, Aug 23, 2018 at 5:40 AM Nikos Alexandris <nik at nikosalexandris.net>
> Is there an elegant alternative?

As for your script design/coding approach:

You were concerned about nice history at one point. You can wrap it, not
just in a plain script, but in a module. Then you can hide any particulars
of the implementation and write proper history in the module. This avoids
changing history which would lead to history not being representative of
what actually happened (provenance is the keyword here).

If you actually publish the module or not that's a different question. Your
script/code is needed to reproduce the data in anyway since you want to
change history and additionally it would be reasonable to use your
script/code to actually reproduce, so then the only difference is number of
files and interface of the scripts (some custom solution versus module).

Splitting your code would also make sense because you are saying it is
quite long.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180823/528963dc/attachment.html>

More information about the grass-dev mailing list