Thanks Moritz, that's one option although I dropping large blobs of text
strings into the script might not be very 'clean' (I also have three files
representing color rules, and three category files that are applied to the
8, 12 or 16 terrain classification results). If there is no alternative
I'll go with that (or create some additional python files containing the
strings that are imported), but I was wondering if there is a way to
package the typical GRASS rule files in the add-on.

Steve

On Sat, Aug 12, 2017 at 9:00 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> On 12/08/17 16:45, Steven Pawley wrote:
>
>> Hello,
>>
>> I'm getting around to completing my TODO list for the add-on
>> r.terrain.texture, which includes generating the additional terrain metrics
>> (terrain surface concavity and convexity), and calculating the nested 8,12
>> or 16 class terrain classification as per Iwahashi and Pike (2007).
>> Everything is working but the script uses r.mfilter, which I supply a
>> matrix filter to, stored as a text file.
>>
>> Is there a makefile command that can be used to bundle a text file with
>> the add on, which can then be found using set_path?
>>
>
> Can't you include the filter as a string directly in the code ?
>
> Moritz
>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to