Re: [GRASS-dev] storing full script as metadata

2008-06-09 Thread Glynn Clements
Yann Chemin wrote: Just wanted to keep exact track of the processing leading to a new layer. 1 - would it be feasible to store the whole processing line with parameters (i.e. r.something -a input=file_in output-file_out etc...) as metadata in the output file of a module ?

Re: [GRASS-dev] storing full script as metadata

2008-06-09 Thread Yann Chemin
2008/6/9 Glynn Clements [EMAIL PROTECTED]: Yann Chemin wrote: Just wanted to keep exact track of the processing leading to a new layer. 1 - would it be feasible to store the whole processing line with parameters (i.e. r.something -a input=file_in output-file_out etc...) as metadata in the

Re: [GRASS-dev] storing full script as metadata

2008-06-09 Thread Hamish
Yann Chemin wrote: well, since G_recreate_command passed it into the metadata, I guess already that is good. I was thinking more of a kind of command log, but with time-based separation of commands used in txt files. Whether they are stored inside a mapset would just be convenient. see

[GRASS-dev] storing full script as metadata

2008-06-08 Thread Yann Chemin
Hello, Just wanted to keep exact track of the processing leading to a new layer. 1 - would it be feasible to store the whole processing line with parameters (i.e. r.something -a input=file_in output-file_out etc...) as metadata in the output file of a module ? 2 - would it be interesting to