[GRASS-dev] GSoC introduction Roberta Fagandini

Hi Moritz and Roberto!
Here [0] you can find the schema of the algorithm!

I committed [1] the first results of the procedure. In this case, I used the image S2A_MSIL1C_20171025T095101_N0206_R079_T33SVB_20171025T134153 (Sicily). I have already tested the procedure using other two or three images but I want to keep on testing!
If you have any suggestions about the testing phase please let me know! As I wrote in another mail, I have the intention of trying out the procedure using several images sensed in different seasons, latitude, etc.

Best wishes
Roberta

[0] https://drive.google.com/file/d/1KYEKvNBurBFHw1xUTLjM0PW80Z-7br81/view?usp=sharing

[1] https://github.com/RobiFag/GRASS_clouds_and_shadows

···

2018-05-03 22:06 GMT+02:00 Roberto Marzocchi <roberto.marzocchi@gmail.com>:

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 :wink: for validation/calibration of the automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert <mlennert@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@club.worldonline.be mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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

Hi Roberta,

On 07/05/18 18:00, Roberta Fagandini wrote:

Hi Moritz and Roberto!
Here [0] you can find the schema of the algorithm!

Thanks ! I think the most interesting part would actually be the details of the two detection procedures, so it would be good to detail them :-).

And I see that you have committed a first python script as well. Great !

I committed [1] the first results of the procedure. In this case, I used the image S2A_MSIL1C_20171025T095101_N0206_R079_T33SVB_20171025T134153 (Sicily). I have already tested the procedure using other two or three images but I want to keep on testing!
If you have any suggestions about the testing phase please let me know! As I wrote in another mail, I have the intention of trying out the procedure using several images sensed in different seasons, latitude, etc.

For GSoC, don't forget that you are in bonding period right now, so IMHO the most important is to get the schema out and discuss it with the community and to familiarize yourself with GRASS programming. Now that you have managed to program a Python script, you should look into how to make this into a module, i.e. how to use the parser instructions, how to create a Makefile and things like that.

The actual coding and testing of results can come during coding period starting next week.

Best wishes,
Moritz

Best wishes
Roberta

[0] https://drive.google.com/file/d/1KYEKvNBurBFHw1xUTLjM0PW80Z-7br81/view?usp=sharing
[1] https://github.com/RobiFag/GRASS_clouds_and_shadows

2018-05-03 22:06 GMT+02:00 Roberto Marzocchi <roberto.marzocchi@gmail.com <mailto:roberto.marzocchi@gmail.com>>:

    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 :wink: for validation/calibration of
    the automatic procedure.

    R

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

        2018-05-03 14:03 GMT+02:00 Moritz Lennert
        <mlennert@club.worldonline.be
        <mailto:mlennert@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@club.worldonline.be
                <mailto:mlennert@club.worldonline.be>
                <mailto:mlennert@club.worldonline.be
                <mailto:mlennert@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 :wink:
        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
        <https://grass.osgeo.org/grass75/manuals/libpython/script_intro.html&gt;
        [1]https://trac.osgeo.org/grass/browser/grass/trunk/scripts
        <https://trac.osgeo.org/grass/browser/grass/trunk/scripts&gt;
        [2]https://trac.osgeo.org/grass/browser/grass-addons/grass7
        <https://trac.osgeo.org/grass/browser/grass-addons/grass7&gt;

2018-05-08 9:59 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

Hi Roberta,

Hi Moritz!

On 07/05/18 18:00, Roberta Fagandini wrote:

Hi Moritz and Roberto!
Here [0] you can find the schema of the algorithm!

Thanks ! I think the most interesting part would actually be the details
of the two detection procedures, so it would be good to detail them :-).

Yes, I will add all the rules from the procedure file. Then I'd like to
send a new mail with all the links related to the project (wiki, github and
schema) to the grass dev list asking for feedback, hints, etc. What do you
think?

And I see that you have committed a first python script as well. Great !

Yes, but it's only a test :wink: since I have to get familiar with the GRASS
Python scripting library, I tried to do something that could be useful
during the coding period.

I committed [1] the first results of the procedure. In this case, I used
the image S2A_MSIL1C_20171025T095101_N0206_R079_T33SVB_20171025T134153
(Sicily). I have already tested the procedure using other two or three
images but I want to keep on testing!
If you have any suggestions about the testing phase please let me know!
As I wrote in another mail, I have the intention of trying out the
procedure using several images sensed in different seasons, latitude, etc.

For GSoC, don't forget that you are in bonding period right now, so IMHO
the most important is to get the schema out and discuss it with the
community and to familiarize yourself with GRASS programming. Now that you
have managed to program a Python script, you should look into how to make
this into a module, i.e. how to use the parser instructions, how to create
a Makefile and things like that.

The actual coding and testing of results can come during coding period
starting next week.

You are right and I will investigate all these issues in the next days!
Today I want to update my wiki page with more details especially about the
timeline (as requested in the soc-list).

Best wishes,
Moritz

Best wishes,
Roberta

Best wishes
Roberta

[0] https://drive.google.com/file/d/1KYEKvNBurBFHw1xUTLjM0PW80Z-
7br81/view?usp=sharing
[1] https://github.com/RobiFag/GRASS_clouds_and_shadows

2018-05-03 22:06 GMT+02:00 Roberto Marzocchi <roberto.marzocchi@gmail.com
<mailto:roberto.marzocchi@gmail.com>>:

    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 :wink: for validation/calibration of
    the automatic procedure.

    R

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

        2018-05-03 14:03 GMT+02:00 Moritz Lennert
        <mlennert@club.worldonline.be
        <mailto:mlennert@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@club.worldonline.be
                <mailto:mlennert@club.worldonline.be>
                <mailto:mlennert@club.worldonline.be

                <mailto:mlennert@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 :wink:
        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_int
ro.html
        <https://grass.osgeo.org/grass75/manuals/libpython/script_in
tro.html>
        [1]https://trac.osgeo.org/grass/browser/grass/trunk/scripts
        <https://trac.osgeo.org/grass/browser/grass/trunk/scripts&gt;
        [2]https://trac.osgeo.org/grass/browser/grass-addons/grass7
        <https://trac.osgeo.org/grass/browser/grass-addons/grass7&gt;

On 08/05/18 13:38, Roberta Fagandini wrote:

2018-05-08 9:59 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>>:
    Thanks ! I think the most interesting part would actually be the
    details of the two detection procedures, so it would be good to
    detail them :-).

Yes, I will add all the rules from the procedure file. Then I'd like to send a new mail with all the links related to the project (wiki, github and schema) to the grass dev list asking for feedback, hints, etc. What do you think?

Good idea.

:slight_smile:

Moritz

Hi Moritz and Roberto!
Here [0] you can find the updated version of the project wiki page! Tomorrow I’ll better detail the procedure schema and then I’ll share everything with the grass dev list asking for feedback.
At the same time, I want to follow the procedure for access to the GRASS-Addons-SVN repository (maybe another thing to do during the bonding period ).

Roberta

[0] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection

···

2018-05-08 13:42 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

On 08/05/18 13:38, Roberta Fagandini wrote:

2018-05-08 9:59 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be mailto:[mlennert@club.worldonline.be](mailto:mlennert@club.worldonline.be)>:
Thanks ! I think the most interesting part would actually be the
details of the two detection procedures, so it would be good to
detail them :-).

Yes, I will add all the rules from the procedure file. Then I’d like to send a new mail with all the links related to the project (wiki, github and schema) to the grass dev list asking for feedback, hints, etc. What do you think?

Good idea.

:slight_smile:

Moritz

Hi Roberta and Moritz!

SCHEMA: Roberta has already written the rules in the schema, but I think you need to open it with a google drive app called diagram.io

New mail to GRASS-DEV : +1

R

···

2018-05-08 18:10 GMT+02:00 Roberta Fagandini <robifagandini@gmail.com>:

Hi Moritz and Roberto!
Here [0] you can find the updated version of the project wiki page! Tomorrow I’ll better detail the procedure schema and then I’ll share everything with the grass dev list asking for feedback.
At the same time, I want to follow the procedure for access to the GRASS-Addons-SVN repository (maybe another thing to do during the bonding period ).

Roberta

[0] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection

2018-05-08 13:42 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

On 08/05/18 13:38, Roberta Fagandini wrote:

2018-05-08 9:59 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be mailto:[mlennert@club.worldonline.be](mailto:mlennert@club.worldonline.be)>:
Thanks ! I think the most interesting part would actually be the
details of the two detection procedures, so it would be good to
detail them :-).

Yes, I will add all the rules from the procedure file. Then I’d like to send a new mail with all the links related to the project (wiki, github and schema) to the grass dev list asking for feedback, hints, etc. What do you think?

Good idea.

:slight_smile:

Moritz

On 09/05/18 09:41, Roberto Marzocchi wrote:

Hi Roberta and Moritz!

SCHEMA: Roberta has already written the rules in the schema, but I think you need to open it with a google drive app called diagram.io <http://diagram.io>

Right, a lot of hoops to jump through to finally being able to see it, but I got there. I'm not much of a user of Google services... :wink:

But IMHO the schema would be more helpful if it contained the actual rules. For example, in the cloud detection procedure, it says "First rule: blue-green-red", but this does not provide the actual decision rule. This would be helpful to have.

Moritz

Hi Moritz and Roberto!
As you may already know I sent the email to the PSC list asking for write access to the GRASS-Addons-SVN repository.

···

2018-05-09 10:58 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

On 09/05/18 09:41, Roberto Marzocchi wrote:

Hi Roberta and Moritz!

SCHEMA: Roberta has already written the rules in the schema, but I think you need to open it with a google drive app called diagram.io <http://diagram.io>

Right, a lot of hoops to jump through to finally being able to see it, but I got there. I’m not much of a user of Google services… :wink:

This app is not so bad but if you know a better tool, please let me know :slight_smile:

But IMHO the schema would be more helpful if it contained the actual rules. For example, in the cloud detection procedure, it says “First rule: blue-green-red”, but this does not provide the actual decision rule. This would be helpful to have.

I have just added all the rules. I would send the new email to the list if you agree. Is there any keyword to be inserted in the mail subject in order to require feedback or hints?

Thanks!
Roberta

Moritz

On 09/05/18 12:46, Roberta Fagandini wrote:

Hi Moritz and Roberto!
As you may already know I sent the email to the PSC list asking for write access to the GRASS-Addons-SVN repository.

Yes, thank you.

2018-05-09 10:58 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>>:

    On 09/05/18 09:41, Roberto Marzocchi wrote:

        Hi Roberta and Moritz!

        SCHEMA: Roberta has already written the rules in the schema, but
        I think you need to open it with a google drive app called
        diagram.io <http://diagram.io> <http://diagram.io>

    Right, a lot of hoops to jump through to finally being able to see
    it, but I got there. I'm not much of a user of Google services... :wink:

This app is not so bad but if you know a better tool, please let me know :slight_smile:

I don't know much in terms of online tools in general, so don't worry, just keeping using what works for you.

    But IMHO the schema would be more helpful if it contained the actual
    rules. For example, in the cloud detection procedure, it says "First
    rule: blue-green-red", but this does not provide the actual decision
    rule. This would be helpful to have.

I have just added all the rules.

Thanks !

Not sure I understand, though:

(blue > 0.08(blue))

will always be true. Or do you mean

(blue > 0.08)

?

I would send the new email to the list if you agree.

+1

Is there any keyword to be inserted in the mail subject in order to require feedback or hints?

You should definitely start a new thread. Mention your project theme and explicitely state that it is a request for feedback.

Moritz

2018-05-09 13:04 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

On 09/05/18 12:46, Roberta Fagandini wrote:

Hi Moritz and Roberto!
As you may already know I sent the email to the PSC list asking for write
access to the GRASS-Addons-SVN repository.

Yes, thank you.

2018-05-09 10:58 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be
<mailto:mlennert@club.worldonline.be>>:

    On 09/05/18 09:41, Roberto Marzocchi wrote:

        Hi Roberta and Moritz!

        SCHEMA: Roberta has already written the rules in the schema, but
        I think you need to open it with a google drive app called
        diagram.io <http://diagram.io> <http://diagram.io>

    Right, a lot of hoops to jump through to finally being able to see
    it, but I got there. I'm not much of a user of Google services... :wink:

This app is not so bad but if you know a better tool, please let me know
:slight_smile:

I don't know much in terms of online tools in general, so don't worry,
just keeping using what works for you.

    But IMHO the schema would be more helpful if it contained the actual
    rules. For example, in the cloud detection procedure, it says "First
    rule: blue-green-red", but this does not provide the actual decision
    rule. This would be helpful to have.

I have just added all the rules.

Thanks !

Not sure I understand, though:

(blue > 0.08(blue))

will always be true. Or do you mean

(blue > 0.08)

?

Sorry, I misspelled the rule..the right meaning is (blue > 0.08 *
max(blue)), I missed the max () function but I have already corrected the
schema.

I would send the new email to the list if you agree.

+1

Is there any keyword to be inserted in the mail subject in order to

require feedback or hints?

You should definitely start a new thread. Mention your project theme and
explicitely state that it is a request for feedback.

Ok thank you, I'll send the email after lunch!

Roberta

Moritz

On Wed, May 9, 2018 at 10:58 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 09/05/18 09:41, Roberto Marzocchi wrote:

Hi Roberta and Moritz!

SCHEMA: Roberta has already written the rules in the schema, but I think
you need to open it with a google drive app called diagram.io
<http://diagram.io>

Right, a lot of hoops to jump through to finally being able to see it, but
I got there. I'm not much of a user of Google services... :wink:

Alternative: https://www.draw.io/ (we use it a lot, just keep the
resulting XML file yourself or share it yourself)

But IMHO the schema would be more helpful if it contained the actual rules.
For example, in the cloud detection procedure, it says "First rule:
blue-green-red", but this does not provide the actual decision rule. This
would be helpful to have.

Yes...

Markus

Hi Roberta,

On top of the review linked by Vero, I thought I'd mention the Fmask
procedure -- it seems to give great results and there is a python
library on Github.

*Relevant GRASS GIS tickets*:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

*Papers*:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images
https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

*Software*:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful especially
for the second part of the procedure.
I'll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]
https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be <mailto:mlennert@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 :wink:
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

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn’t have great results. However, it is worth investigating better!
Thanks for all the references!

Roberta

···

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I’d mention the Fmask
procedure – it seems to give great results and there is a python
library on Github.

Relevant GRASS GIS tickets:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

Papers:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images
https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

Software:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful especially
for the second part of the procedure.
I’ll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]
https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Interesting to hear your results, Roberta -- the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn't have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I'd mention the Fmask
procedure -- it seems to give great results and there is a python
library on Github.

*Relevant GRASS GIS tickets*:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

*Papers*:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

*Software*:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:
>
>
> 2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:
>>
>> Hey Robi,
>
>
> Hi Vero!!
>
>>
>>
>> I just found this review [0]. It is for Landsat, but maybe some
>> insights
>> could be also useful for you (?)
>
>
> Thank you so much! I know this paper and it could be very useful
> especially
> for the second part of the procedure.
> I'll read it carefully!
>
>>
>>
>> Cheers :),
>> Vero
>
>
> Thanks!
> Robi
>
>>
>>
>> [0]
>>
>> https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series
>>
>> El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
>> (<roberto.marzocchi@gmail.com>) escribió:
>>>
>>> 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 :wink: for validation/calibration of the
>>> automatic procedure.
>>>
>>> R
>>>
>>> 2018-05-03 18:48 GMT+02:00 Roberta Fagandini
>>> <robifagandini@gmail.com>:
>>>>
>>>>
>>>> 2018-05-03 14:03 GMT+02:00 Moritz Lennert
>>>> <mlennert@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@club.worldonline.be
>>>>>> <mailto:mlennert@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 :wink:
>>>> 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
>>>
>>>
>>> _______________________________________________
>>> grass-dev mailing list
>>> grass-dev@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

Thank you, Pierre!! I will keep the community constantly updated on the progress of the module.
Every feedback is welcome so please do not hesitate to send me yours! :wink:

Roberta

···

2018-05-15 23:46 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Interesting to hear your results, Roberta – the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn’t have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I’d mention the Fmask
procedure – it seems to give great results and there is a python
library on Github.

Relevant GRASS GIS tickets:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

Papers:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

Software:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some
insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful
especially
for the second part of the procedure.
I’ll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]

https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be
mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Roberta,

Here in Norway we can do some “worst case” testing for your algorithm. Plenty of snow and clouds in the mountains, and heavily rugged terrain, that presumably has quite some effect on cloud shadows…

Looking forward to following your project from the side!

Kind regards,

Stefan

···

Thank you, Pierre!! I will keep the community constantly updated on the progress of the module.

Every feedback is welcome so please do not hesitate to send me yours! :wink:

Roberta

2018-05-15 23:46 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Interesting to hear your results, Roberta – the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn’t have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I’d mention the Fmask
procedure – it seems to give great results and there is a python
library on Github.

Relevant GRASS GIS tickets:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

Papers:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

Software:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some
insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful
especially
for the second part of the procedure.
I’ll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]

https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be
mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Stefan!!

···

2018-05-16 16:22 GMT+02:00 Stefan Blumentrath <Stefan.Blumentrath@nina.no>:

Hi Roberta,

Here in Norway we can do some “worst case” testing for your algorithm. Plenty of snow and clouds in the mountains, and heavily rugged terrain, that presumably has quite some effect on cloud shadows…

Thank you so much!!
The cases you describe are “the best cases” for me, clouds and snow are hard to distinguish and shadows are strongly dependent on land use/cover.
Now I’m working on the python script, as soon as it is ready I will share it with the community and commit it to my GitHub repository [0]

From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Roberta Fagandini
Sent: onsdag 16. mai 2018 16.01
To: Pierre Roudier <pierre.roudier@gmail.com>
Cc: grass-dev <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] GSoC introduction Roberta Fagandini

Thank you, Pierre!! I will keep the community constantly updated on the progress of the module.

Every feedback is welcome so please do not hesitate to send me yours! :wink:

Roberta

2018-05-15 23:46 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Interesting to hear your results, Roberta – the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn’t have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I’d mention the Fmask
procedure – it seems to give great results and there is a python
library on Github.

Relevant GRASS GIS tickets:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

Papers:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

Software:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com> wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some
insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful
especially
for the second part of the procedure.
I’ll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]

https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be
mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Looking forward to following your project from the side!

If you want you can follow the project progress on my wiki page [1]

Kind regards,

Stefan

Keep in touch!
best wishes

Roberta

[0] https://github.com/RobiFag/GRASS_clouds_and_shadows
[1] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection

Hi Stefan and Roberta,

We can probably help too -- I work on Antarctic datasets: relief,
clouds, and very cold, white surface!

Cheers,

P

On 17 May 2018 at 02:22, Stefan Blumentrath <Stefan.Blumentrath@nina.no> wrote:

Hi Roberta,

Here in Norway we can do some “worst case” testing for your algorithm.
Plenty of snow and clouds in the mountains, and heavily rugged terrain, that
presumably has quite some effect on cloud shadows…

Looking forward to following your project from the side!

Kind regards,

Stefan

From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Roberta
Fagandini
Sent: onsdag 16. mai 2018 16.01
To: Pierre Roudier <pierre.roudier@gmail.com>
Cc: grass-dev <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] GSoC introduction Roberta Fagandini

Thank you, Pierre!! I will keep the community constantly updated on the
progress of the module.

Every feedback is welcome so please do not hesitate to send me yours! :wink:

Roberta

2018-05-15 23:46 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Interesting to hear your results, Roberta -- the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn't have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I'd mention the Fmask
procedure -- it seems to give great results and there is a python
library on Github.

*Relevant GRASS GIS tickets*:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

*Papers*:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

*Software*:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com>
wrote:
>
>
> 2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:
>>
>> Hey Robi,
>
>
> Hi Vero!!
>
>>
>>
>> I just found this review [0]. It is for Landsat, but maybe some
>> insights
>> could be also useful for you (?)
>
>
> Thank you so much! I know this paper and it could be very useful
> especially
> for the second part of the procedure.
> I'll read it carefully!
>
>>
>>
>> Cheers :),
>> Vero
>
>
> Thanks!
> Robi
>
>>
>>
>> [0]
>>
>>
>> https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series
>>
>> El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
>> (<roberto.marzocchi@gmail.com>) escribió:
>>>
>>> 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 :wink: for validation/calibration of the
>>> automatic procedure.
>>>
>>> R
>>>
>>> 2018-05-03 18:48 GMT+02:00 Roberta Fagandini
>>> <robifagandini@gmail.com>:
>>>>
>>>>
>>>> 2018-05-03 14:03 GMT+02:00 Moritz Lennert
>>>> <mlennert@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@club.worldonline.be
>>>>>> <mailto:mlennert@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 :wink:
>>>> 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
>>>
>>>
>>> _______________________________________________
>>> grass-dev mailing list
>>> grass-dev@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Pierre,

···

2018-05-16 23:42 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Stefan and Roberta,

We can probably help too – I work on Antarctic datasets: relief,
clouds, and very cold, white surface!

Thank you so much, I really appreciate it!

Here the link to my wiki page [0] and github repository [1] to follow the project progress.

[0] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection
[1] https://github.com/RobiFag/GRASS_clouds_and_shadows

Cheers,

P

Keep in touch!
best wishes

Roberta

On 17 May 2018 at 02:22, Stefan Blumentrath <Stefan.Blumentrath@nina.no> wrote:

Hi Roberta,

Here in Norway we can do some “worst case” testing for your algorithm.
Plenty of snow and clouds in the mountains, and heavily rugged terrain, that
presumably has quite some effect on cloud shadows…

Looking forward to following your project from the side!

Kind regards,

Stefan

From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Roberta
Fagandini
Sent: onsdag 16. mai 2018 16.01
To: Pierre Roudier <pierre.roudier@gmail.com>
Cc: grass-dev <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] GSoC introduction Roberta Fagandini

Thank you, Pierre!! I will keep the community constantly updated on the
progress of the module.

Every feedback is welcome so please do not hesitate to send me yours! :wink:

Roberta

2018-05-15 23:46 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Interesting to hear your results, Roberta – the reason I brought this
up is that some of my colleagues (non-GRASS users :frowning: ) tried it very
successfully.

Happy to follow up with them if need be,

P

On 15 May 2018 at 22:03, Roberta Fagandini <robifagandini@gmail.com> wrote:

Hi Pierre!
Thank you so much for your hints!
I have already tested Fmask with Sentinel 2 images but I didn’t have great
results. However, it is worth investigating better!
Thanks for all the references!

Roberta

2018-05-15 0:51 GMT+02:00 Pierre Roudier <pierre.roudier@gmail.com>:

Hi Roberta,

On top of the review linked by Vero, I thought I’d mention the Fmask
procedure – it seems to give great results and there is a python
library on Github.

Relevant GRASS GIS tickets:

https://trac.osgeo.org/grass/ticket/3473
https://trac.osgeo.org/grass/ticket/3283

Papers:

https://www.researchgate.net/publication/270596187_Improvement_and_expansion_of_the_Fmask_algorithm_Cloud_cloud_shadow_and_snow_detection_for_Landsats_4-7_8_and_Sentinel_2_images

https://www.researchgate.net/publication/324836341_Improvement_of_the_Fmask_algorithm_for_Sentinel-2_images_Separating_clouds_from_bright_surfaces_based_on_parallax_effects

Software:

http://pythonfmask.org/en/latest/
https://github.com/prs021/fmask

Hopefully this is helpful,

Pierre

On 7 May 2018 at 19:49, Roberta Fagandini <robifagandini@gmail.com>
wrote:

2018-05-06 21:52 GMT+02:00 Veronica Andreo <veroandreo@gmail.com>:

Hey Robi,

Hi Vero!!

I just found this review [0]. It is for Landsat, but maybe some
insights
could be also useful for you (?)

Thank you so much! I know this paper and it could be very useful
especially
for the second part of the procedure.
I’ll read it carefully!

Cheers :),
Vero

Thanks!
Robi

[0]

https://www.researchgate.net/publication/324975294_Cloud_and_Cloud_Shadow_Detection_for_Landsat_Images_The_Fundamental_Basis_for_Analyzing_Landsat_Time_Series

El jue., 3 may. 2018 a las 22:06, Roberto Marzocchi
(<roberto.marzocchi@gmail.com>) escribió:

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 :wink: for validation/calibration of the
automatic procedure.

R

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

2018-05-03 14:03 GMT+02:00 Moritz Lennert
<mlennert@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@club.worldonline.be
mailto:[mlennert@club.worldonline.be](mailto:mlennert@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 :wink:
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


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev