[GRASS-dev] GSoC introduction Roberta Fagandini

[Roberto Marzocchi]

Nice! The last step of the script you have written in python works as you
expected.

Now it is important to draw a diagram (or schema ) as a summary for you (you
have worked a lot in the last few months) and to share it with Moritz and
Markus.

After that, test, test and test ;-) for validation/calibration of the
automatic procedure.

R

2018-05-03 18:48 GMT+02:00 Roberta Fagandini <robifagandini a gmail.com>:

>
> 2018-05-03 14:03 GMT+02:00 Moritz Lennert <mlennert a club.worldonline.be>:
>
>> Hi Roberta,
>>
>
> Hi Moritz and Roberto!
>
>
>>
>> On 25/04/18 18:03, Roberta Fagandini wrote:
>>
>>>
>>>
>>> 2018-04-25 16:03 GMT+02:00 Moritz Lennert <mlennert a club.worldonline.be
>>> <mailto:mlennert a club.worldonline.be>>:
>>>     Looking at your bash scripts, I think the first thing to do during
>>>     this bonding period is, as you planned yourself, to get familiar
>>>     with the writing of GRASS modules in Python. You can have a look at
>>>     existing scripts [1, 2] to get feeling for this works and how to
>>>     structure addon code in order to make it directly installable with
>>>     g.extension.
>>>
>>>     You can find the actual function definitions and documentation of
>>>     the GRASS Python scripting library at [3]. The functions in that
>>>     library should be more than enough to translate your scripts into a
>>>     (or several) modules.
>>>
>>>     Be aware that GRASS modules create their own GUI. So, unless you
>>>     need some interactive features in your modules, you will not have to
>>>     program your own GUI.
>>>
>>>
>>> Thank you for your precious suggestions! I'll start studying how to
>>> write a GRASS module in Python in the next days and at the same time I will
>>> keep on testing the procedures so as to show you some results and fix some
>>> open points.
>>>
>>>
>>>     Something else you should probably do during this bonding time is to
>>>     elaborate a schema of your algorithm, so that it is easier to
>>>     understand what it does at each step.
>>>
>>>
>>> Yes, this could be very useful also for me in order to better organize
>>> and put in order everything!
>>>
>>>
>> Have you advanced on any of this ? Do you have any questions ? Please
>> don't hesitate to ask on the mailing list.
>>
>
> Yes, I started working with GRASS Python scripting library. I'm following
> the link [0] you suggested, I'm also looking at other existing GRASS
> scripts [1,2] and moreover, Roberto gave me one of his scripts as an
> example. I have just committed the first version of the python script I'm
> working on, it works and I'm quite satisfied ;-)
> Tomorrow I want to elaborate the schema of the algorithm and at the same
> time, I have to keep testing the procedure. As I wrote in the bash file,
> shadows detection seems to be strongly land cover dependent therefore I
> think it is necessary to test the procedure using several images sensed in
> different seasons, latitude, etc.
>
> Anyway, I'll commit some results tomorrow so as to show you something more
> concrete!
>
>>
>> Best wishes,
>> Moritz
>>
>
> Best regards,
> Roberta
>
> [0] https://grass.osgeo.org/grass75/manuals/libpython/script_intro.html
> [1] https://trac.osgeo.org/grass/browser/grass/trunk/scripts
> [2] https://trac.osgeo.org/grass/browser/grass-addons/grass7
>
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180503/c415b15e/attachment.html>