[GRASS-dev] GSoC project for cloud and shadow detection - request of feedback

[Roberta Fagandini]

Hi all!

I'd like to share with you my GSoC project about an automatic procedure for
the detection of clouds and shadows in Sentinel 2 images.
I'm very interested in knowing what the community thinks of it, so any
suggestion, help, idea, opinion is welcome!

Below you can find the links to my GSoC proposal [0], wiki page [1]
and github repository [2].
Here's [3] the link to the workflow schema of the procedure
(unfortunately it is necessary to open it with a google drive app,
diagram.io [4], to see all the pages).

Thanks in advance for your time and feedback!

Roberta

[0]
https://docs.google.com/document/d/1mQyouqbHGHugn5DjEDZI3hc1eU_bT_b0qLJPPwkt_hk/edit?usp=sharing
[1] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection
[2] https://github.com/RobiFag/GRASS_clouds_and_shadows
[3]
https://drive.google.com/file/d/1KYEKvNBurBFHw1xUTLjM0PW80Z-7br81/view?usp=sharing
[4] http://diagram.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Project

[sharry gill]

Hello,

Thanks for suggestions!
Here is the draft proposal with improvements: Link  to proposal


Thank You
Supreet Singh
https://singhsupreet.github.io/

On Sat, Mar 10, 2018 at 2:09 PM, Margherita Di Leo 
wrote:

> After designing the tool, you should spend some time and reconsider what
> you have written in the timeline, which currently says absolutely nothing
> about the actual implementation, as you use generic sentences about writing
> "the code" and compiling "the code".
> Please, take a look at former years student proposals to get a hint of how
> to structure a meaningful proposal, how to design your project and how to
> split up the project in milestones for your timeline.
>
> Thanks and regards,
>
> On Sat, 10 Mar 2018 at 09:21, Margherita Di Leo 
> wrote:
>
>> Hi,
>>
>> I see that you have indicated in the first week: to design the tool,
>> actually you should be doing this now, as well as compiling the source
>> code, which you put in the bonding period. Rationale: how do you/we know
>> that you will be able to develop such tool if you haven't neither designed
>> it, nor compiled the source code and studied basic documentation.
>>
>> Thanks
>>
>> On Sat, 10 Mar 2018 at 07:10, sharry gill 
>> wrote:
>>
>>> Hi,
>>>
>>> Here is the draft proposal, I fixed it: Link To Proposal
>>> 
>>>
>>> If any improvements are required, please let me know.
>>>
>>> Thank You
>>> Supreet Singh
>>> https://singhsupreet.github.io/
>>>
>>> On Wed, Mar 7, 2018 at 9:49 PM, Luca Delucchi 
>>> wrote:
>>>
 On 7 March 2018 at 09:08, sharry gill  wrote:
 >
 > Hello,

 hi,

 >
 > May be this is poasible that, if we allow user only to select
 modules, and
 > flags will be automatic.

 yes, so please improve your proposal..

 --
 ciao
 Luca

 www.lucadelu.org

>>>
>>> ___
>>> 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

Re: [GRASS-dev] GSoC Project

[Margherita Di Leo]

After designing the tool, you should spend some time and reconsider what
you have written in the timeline, which currently says absolutely nothing
about the actual implementation, as you use generic sentences about writing
"the code" and compiling "the code".
Please, take a look at former years student proposals to get a hint of how
to structure a meaningful proposal, how to design your project and how to
split up the project in milestones for your timeline.

Thanks and regards,

On Sat, 10 Mar 2018 at 09:21, Margherita Di Leo  wrote:

> Hi,
>
> I see that you have indicated in the first week: to design the tool,
> actually you should be doing this now, as well as compiling the source
> code, which you put in the bonding period. Rationale: how do you/we know
> that you will be able to develop such tool if you haven't neither designed
> it, nor compiled the source code and studied basic documentation.
>
> Thanks
>
> On Sat, 10 Mar 2018 at 07:10, sharry gill 
> wrote:
>
>> Hi,
>>
>> Here is the draft proposal, I fixed it: Link To Proposal
>> 
>>
>> If any improvements are required, please let me know.
>>
>> Thank You
>> Supreet Singh
>> https://singhsupreet.github.io/
>>
>> On Wed, Mar 7, 2018 at 9:49 PM, Luca Delucchi 
>> wrote:
>>
>>> On 7 March 2018 at 09:08, sharry gill  wrote:
>>> >
>>> > Hello,
>>>
>>> hi,
>>>
>>> >
>>> > May be this is poasible that, if we allow user only to select modules,
>>> and
>>> > flags will be automatic.
>>>
>>> yes, so please improve your proposal..
>>>
>>> --
>>> ciao
>>> Luca
>>>
>>> www.lucadelu.org
>>>
>>
>> ___
>> 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

Re: [GRASS-dev] GSoC Project

[Margherita Di Leo]

Hi,

I see that you have indicated in the first week: to design the tool,
actually you should be doing this now, as well as compiling the source
code, which you put in the bonding period. Rationale: how do you/we know
that you will be able to develop such tool if you haven't neither designed
it, nor compiled the source code and studied basic documentation.

Thanks

On Sat, 10 Mar 2018 at 07:10, sharry gill  wrote:

> Hi,
>
> Here is the draft proposal, I fixed it: Link To Proposal
> 
>
> If any improvements are required, please let me know.
>
> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>
> On Wed, Mar 7, 2018 at 9:49 PM, Luca Delucchi 
> wrote:
>
>> On 7 March 2018 at 09:08, sharry gill  wrote:
>> >
>> > Hello,
>>
>> hi,
>>
>> >
>> > May be this is poasible that, if we allow user only to select modules,
>> and
>> > flags will be automatic.
>>
>> yes, so please improve your proposal..
>>
>> --
>> ciao
>> Luca
>>
>> www.lucadelu.org
>>
>
> ___
> 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

Re: [GRASS-dev] GSoC Project

[sharry gill]

Hi,

Here is the draft proposal, I fixed it: Link To Proposal


If any improvements are required, please let me know.

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Wed, Mar 7, 2018 at 9:49 PM, Luca Delucchi  wrote:

> On 7 March 2018 at 09:08, sharry gill  wrote:
> >
> > Hello,
>
> hi,
>
> >
> > May be this is poasible that, if we allow user only to select modules,
> and
> > flags will be automatic.
>
> yes, so please improve your proposal..
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Project

[Luca Delucchi]

On 7 March 2018 at 09:08, sharry gill  wrote:
>
> Hello,

hi,

>
> May be this is poasible that, if we allow user only to select modules, and
> flags will be automatic.

yes, so please improve your proposal..

-- 
ciao
Luca

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

Re: [GRASS-dev] GSoC Project

[sharry gill]

On 7 Mar 2018 11:05, "Luca Delucchi"  wrote:



On 27 February 2018 at 10:29, sharry gill  wrote:

> Hello Luca,
>
>
Hi,

Hello,



> There will be a tool, in which the user enters the name of the module, and
> select the flags and parameters of the modules, and select which test to be
> done.
> after selecting these option, the user click "Create Test", then their
> will be a python file generated on the desktop, by using the python file
> user can test the module.
>
> And When the user will enter the module name, the window will extend and
> at the side it will show manual of the module.
>

ok, but since there are a lot of modules in GRASS it is better if the tool
will be able to work without the user choses. It should be more automatic
possible.


May be this is poasible that, if we allow user only to select modules, and
flags will be automatic.


> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>
>
-- 
ciao
Luca

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

Re: [GRASS-dev] GSoC Project

[Luca Delucchi]

On 27 February 2018 at 10:29, sharry gill  wrote:

> Hello Luca,
>
>
Hi,


> There will be a tool, in which the user enters the name of the module, and
> select the flags and parameters of the modules, and select which test to be
> done.
> after selecting these option, the user click "Create Test", then their
> will be a python file generated on the desktop, by using the python file
> user can test the module.
>
> And When the user will enter the module name, the window will extend and
> at the side it will show manual of the module.
>

ok, but since there are a lot of modules in GRASS it is better if the tool
will be able to work without the user choses. It should be more automatic
possible.


>
> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>
>
-- 
ciao
Luca

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

Re: [GRASS-dev] GSoC Project

[sharry gill]

Hello Luca,

There will be a tool, in which the user enters the name of the module, and
select the flags and parameters of the modules, and select which test to be
done.
after selecting these option, the user click "Create Test", then their will
be a python file generated on the desktop, by using the python file user
can test the module.

And When the user will enter the module name, the window will extend and at
the side it will show manual of the module.

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Tue, Feb 27, 2018 at 4:57 AM, Luca Delucchi  wrote:

> [image: Boxbe]  Luca Delucchi (
> lucadel...@gmail.com) is not on your Guest List
> 
> | Approve sender
> 
> | Approve domain
> 
>
> On 19 February 2018 at 14:40, sharry gill 
> wrote:
> > Hello,
> >
>
> Hi Sharry,
>
> > I created a draft of GSoC Proposal: Link To Proposal.
> > In the proposal is have a project idea:
> >
> > Title: Tool to create Automatic Module test writer in Python
> >
> >
> > Description of the idea :
> >
> > 1) First, there is an option of entering the name of module
> >
> > 2) After that, there will some options regarding which test the user
> wants
> > to write. (for eg:assertMinMax, RasterFitsUnivar etc)
> >
> > 3)Then there will be options for selecting flags and maps.
> >
> >
> > 4)Then the user will click "create the test" then a python file will be
> > provided to the user which contains the test.
> >
> > SAMPLE MOCKUP:  Link to image
> >
>
> please you should improve your description, it could be useful to
> create test automatically from each modules or execute test from
> manuals [0]
> Please ask if you have questions.
>
> >
> > Can I know which mentor will be mentoring me?
> >
>
> If the description will be improved I could co-mentoring
>
> > Thank You
> > Supreet Singh
> > https://singhsupreet.github.io/
> >
>
>
> [0] https://trac.osgeo.org/grass/wiki/GSoC/2018#
> Toolsforgeneratingunittestsfromexamplesinthemanual
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Project

[Luca Delucchi]

On 19 February 2018 at 14:40, sharry gill  wrote:
> Hello,
>

Hi Sharry,

> I created a draft of GSoC Proposal: Link To Proposal.
> In the proposal is have a project idea:
>
> Title: Tool to create Automatic Module test writer in Python
>
>
> Description of the idea :
>
> 1) First, there is an option of entering the name of module
>
> 2) After that, there will some options regarding which test the user wants
> to write. (for eg:assertMinMax, RasterFitsUnivar etc)
>
> 3)Then there will be options for selecting flags and maps.
>
>
> 4)Then the user will click "create the test" then a python file will be
> provided to the user which contains the test.
>
> SAMPLE MOCKUP:  Link to image
>

please you should improve your description, it could be useful to
create test automatically from each modules or execute test from
manuals [0]
Please ask if you have questions.

>
> Can I know which mentor will be mentoring me?
>

If the description will be improved I could co-mentoring

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>


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

-- 
ciao
Luca

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

[GRASS-dev] GSoC Project

[sharry gill]

Hello,

I created a draft of GSoC Proposal: Link To Proposal.

In the proposal is have a project idea:

Title: Tool to create Automatic Module test writer in Python


Description of the idea :

1) First, there is an option of entering the name of module

2) After that, there will some options regarding which test the user wants
to write. (for eg:assertMinMax, RasterFitsUnivar etc)

3)Then there will be options for selecting flags and maps.

4)Then the user will click "create the test" then a python file will be
provided to the user which contains the test.

SAMPLE MOCKUP:  Link to image


Can I know which mentor will be mentoring me?

Thank You
Supreet Singh
https://singhsupreet.github.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[jyoti misra]

Hello,
Sorry for the late reply. I was busy with exams last week.

I compiled the code from source, read a tutorial on grass gis and I am
fairly comfortable with grass environment.

I was looking into the Bug: Quotes not preserved in command after pressing
enter in GUI command console and tried it out on my machine. I was trying
to fix it and I think most probably it's some problem with regex search
which is deleting the quotes from the command.
I was looking into the code for fixing the bug but couldn't find the
relevant file to change. Could you please guide me with that.

Also for the enhancement: Button, documentation and perhaps something more
interactive for finding EPSG codes online rather then in GRASS GIS list I
was thinking of more interactive process of using EPSG -
1. We can merge epsg.io code into our existing structure. http://epsg.io/
2. We can add a button that will redirect users to epsg.io
I would like to have your suggestions on the same

I know I am running a bit late with the bug fixing but I can assure you I
won't disappoint you during the course of project.
I am very interested in doing GSOC under grass org as it will be an added
advantage to my ongoing research in computer science and spatial
informatics. I would be thankful if you could help me with submitting GSOC
proposal.

Regards
Jyoti

On Thu, Mar 12, 2015 at 9:10 AM, Vaclav Petras wenzesl...@gmail.com wrote:

 Hello.

 On Tue, Mar 10, 2015 at 3:46 PM, jyoti misra jyotimisra...@gmail.com
 wrote:
 
  Dear Sir/Madam,
 
  Myself Jyoti currently working under Dr. KS Rajan as a research student
 in Spatial Informatics Lab, IIIT hyderabad . I am currently working in Land
 Use modelling of Barrack valley region. Previously i have worked on
 Billboard placement optimization problem considering the spatial ,temporal
 and traffic features.
 
  I am interested in working with grass org under the project GUI plugin
 system for GRASS GIS. The project is interesting and I have some idea of
 the technologies requires for the project as i have already worked in
 Python , c/c++.

 Good. Now you should find some enhancements or bugs in GRASS GIS bug
 tracker [1] and implement or fix them before the application evaluation to
 show level of you proficiency [2, 3].

 You can also select from this list:

 Enhancement: Let users save/load SQL statements in wxGUI attribute table
 manager
 http://trac.osgeo.org/grass/ticket/1205

 Bug: Quotes not preserved in command after pressing enter in GUI command
 console
 http://trac.osgeo.org/grass/ticket/1435
 http://trac.osgeo.org/grass/ticket/1437

 Enhancement: Store map elements such as legend, text and scale bar in
 workspace file.
 http://trac.osgeo.org/grass/ticket/2484

 Enhancement: Possibility to automatically load last used workspace when
 GRASS GIS GUI starts
 http://trac.osgeo.org/grass/ticket/2604

 Enhancement: Store recently used workspaces and offer them in the menu
 http://trac.osgeo.org/grass/ticket/2604

 Enhancement: Implement georeferenced image output for Save display...
 function in GUI and d.out.file module (and its wxGUI implementation)
 http://trac.osgeo.org/grass/ticket/977

 Bug: Undefined settings variable issue in bivariate scatterplot tool
 http://trac.osgeo.org/grass/ticket/2247

 Enhancement: Button, documentation and perhaps something more interactive
 for finding EPSG codes online rather then in GRASS GIS list
 http://trac.osgeo.org/grass/ticket/26

 However, you can explore the open issues on GRASS GIS bug tracker
 yourself. Just keep in mind that this GSoC project would be in Python and
 wxPython. You can attempt to solve more of these tasks, the more the
 better. In any case, the thing you select and do should be in Python and
 should sufficiently represent your skills. Draft implementation of non-GUI
 (model) part of the plugin system would be helpful to understand the issues
 which you should address in the application.

 In any case, start with compiling GRASS GIS from source code (trunk) from
 Subversion repository [4], reading tips for students [5] and going through
 instructions for other students [6, 7] (you can use Nabble [8] for that).

 Also read Submitting rules [9] and how-to [10] for wxGUI development. Also
 learn how to do basic tasks in GRASS GIS graphical user interface (called
 wxGUI), use e.g. GRASS wiki or the manual as learning resource.

 Please, always create a new thread on mailing list for distinct topics.

 Best,
 Vaclav

 [1] https://trac.osgeo.org/grass/query
 [2]
 http://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
 [3] http://lists.osgeo.org/pipermail/soc/2015-March/002908.html
 [4] http://trac.osgeo.org/grass/wiki/DownloadSource
 [5] http://trac.osgeo.org/grass/wiki/GSoC/2015#Tipsforstudents
 [6] http://lists.osgeo.org/pipermail/grass-dev/2015-March/074420.html
 [7] http://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html
 [8] http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
 [9] 

Re: [GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[Vaclav Petras]

On Wed, Mar 25, 2015 at 2:20 AM, jyoti misra jyotimisra...@gmail.com
wrote:

 I was looking into the Bug: Quotes not preserved in command after
 pressing enter in GUI command console and tried it out on my machine. I
 was trying to fix it and I think most probably it's some problem with regex
 search which is deleting the quotes from the command.
 I was looking into the code for fixing the bug but couldn't find the
 relevant file to change. Could you please guide me with that.

 It will be probably one of those:

http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/gconsole.py
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/gcmd.py
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/prompt.py
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/pystc.py
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/goutput.py
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/lmgr/frame.py


 Also for the enhancement: Button, documentation and perhaps something
 more interactive for finding EPSG codes online rather then in GRASS GIS
 list I was thinking of more interactive process of using EPSG -
 1. We can merge epsg.io code into our existing structure. http://epsg.io/


This is not desirable. Although there might be some places to get inspired
from what the system offers while GRASS system lacks.


 2. We can add a button that will redirect users to epsg.io


This is the most simple and straightforward way how to implement this.
Button can just open a web browser. There is a standard way in wxPython to
do this.


 I would like to have your suggestions on the same


Alternative is to somehow use their URLs (or API if there is some) to do
some search or show additional information about the projection. This needs
a more detailed analysis of the problem. The button mentioned before would
be a good start. Even with a simple button, the opened URL could also
include something like currently searched URL.

Vaclav
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[jyoti misra]

I was looking into the files you sent and I think I am going in the right
direction. I will try to complete the task as soon as possible.

As for the enhancement I was thinking of creating a search box in our
current structure that takes the users query and redirects it to the result
page of espg.io with the query. For e.g. if I search India redirect URL
will be http://epsg.io/?q=india.
But where exactly do I need to make the changes? Please help me with that.

Regards
Jyoti

On Wed, Mar 25, 2015 at 6:59 PM, Vaclav Petras wenzesl...@gmail.com wrote:


 On Wed, Mar 25, 2015 at 2:20 AM, jyoti misra jyotimisra...@gmail.com
 wrote:

 I was looking into the Bug: Quotes not preserved in command after
 pressing enter in GUI command console and tried it out on my machine. I
 was trying to fix it and I think most probably it's some problem with regex
 search which is deleting the quotes from the command.
 I was looking into the code for fixing the bug but couldn't find the
 relevant file to change. Could you please guide me with that.

 It will be probably one of those:


 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/gconsole.py
 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/gcmd.py

 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/prompt.py

 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/pystc.py

 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/gui_core/goutput.py
 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/lmgr/frame.py


 Also for the enhancement: Button, documentation and perhaps something
 more interactive for finding EPSG codes online rather then in GRASS GIS
 list I was thinking of more interactive process of using EPSG -
 1. We can merge epsg.io code into our existing structure. http://epsg.io/


 This is not desirable. Although there might be some places to get inspired
 from what the system offers while GRASS system lacks.


 2. We can add a button that will redirect users to epsg.io


 This is the most simple and straightforward way how to implement this.
 Button can just open a web browser. There is a standard way in wxPython to
 do this.


 I would like to have your suggestions on the same


 Alternative is to somehow use their URLs (or API if there is some) to do
 some search or show additional information about the projection. This needs
 a more detailed analysis of the problem. The button mentioned before would
 be a good start. Even with a simple button, the opened URL could also
 include something like currently searched URL.

 Vaclav


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

Re: [GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[Vaclav Petras]

On Wed, Mar 25, 2015 at 10:51 AM, jyoti misra jyotimisra...@gmail.com
wrote:

 As for the enhancement I was thinking of creating a search box in our
 current structure that takes the users query and redirects it to the result
 page of espg.io with the query. For e.g. if I search India redirect URL
 will be http://epsg.io/?q=india.


There is no user location information available in GRASS GIS, wxPython or
standard Python packages as far as I know. So this seems quite challenging.


 But where exactly do I need to make the changes? Please help me with that.


http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/location_wizard
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[Vaclav Petras]

On Wed, Mar 25, 2015 at 4:13 PM, jyoti misra jyotimisra...@gmail.com
wrote:

 Hello,

 Hi,

please keep conversation on the mailing list, so other people can follow or
participate.


 Regarding Bug : Quotes not preserved in command after pressing enter in
 GUI command console
 My idea:

- Find the code which is taking command as input and passing it to
RunCommand function.
- Most probably error is in reading the input from stdin and storing
it in variable.
- Code might be running some regex search(or something similar) to
remove everything expect alphanumeric characters from the command string.
- My approach to fix this bug is to find that point and study for the
cause of error and fix it.

 Regarding enhancements to add epsg code :
 My idea as described earlier :

- Add a button and a text box to the current implementation of
wizard.py which will take location as an input and redirect the user to
epsg.io with the url epsg.io/?q=location .
- This is will require to read the input from the user and appending
it to epsg.io URL.
- User can then select among the different search results on the
espg.io page he is redirected to.

 But with both tasks I am getting same problem, the code is very big and
 there are many files to look into, and I'm not able to find the exact place
 to do the corrections/enhancements. I know what to do in both situations
 but lack the complete and exact knowledge of GRASS code structure. Can you
 please guide me to the exact line of code where the changes have to be made.

Sorry, I cannot do that. If I would know where (and how) to fix it I would
already do that. You must understand that although now this serves as an
exercise for GSoC, it is a real issue which is in GRASS. Also, for the GSoC
you will need to understand the existing code to certain extended to be
able to incorporate your code and to fix the bugs which can emerge in both
new and existing code.

Vaclav

 Regards,

 Jyoti
 On Wed, Mar 25, 2015 at 8:40 PM, Vaclav Petras wenzesl...@gmail.com
 wrote:

 On Wed, Mar 25, 2015 at 10:51 AM, jyoti misra jyotimisra...@gmail.com
 wrote:

 As for the enhancement I was thinking of creating a search box in our
 current structure that takes the users query and redirects it to the result
 page of espg.io with the query. For e.g. if I search India redirect URL
 will be http://epsg.io/?q=india.


 There is no user location information available in GRASS GIS, wxPython or
 standard Python packages as far as I know. So this seems quite challenging.


 But where exactly do I need to make the changes? Please help me with
 that.



 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/location_wizard



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

Re: [GRASS-dev] GSOC project proposal

[Vaclav Petras]

On Wed, Mar 11, 2015 at 11:36 AM, sarthak agarwal sarthak0...@gmail.com
wrote:

 I have used Grass directly installing from the ppa .. I was trying to
compile it from the source and i'm getting error .Below is the error.log
content.

  GRASS GIS 7.0.1svn r64826 compilation log

Note that for development you will need trunk, not release branch.

  --
  Errors in:
  /home/sarthak/grass-7.0.svn/display/d.path
  /home/sarthak/grass-7.0.svn/display/d.vect
...
  /home/sarthak/grass-7.0.svn/vector/v.neighbors
...
  /home/sarthak/grass-7.0.svn/ps/ps.map
 --
  In case of errors please change into the directory with error and run
'make'.
  If you get multiple errors, you need to deal with them in the order they
  appear in the error log. If you get an error building a library, you
will
  also get errors from anything which uses the library.
  --

What compilation guide have you used? What it is saying when you do what it
wants?


 Can you please suggest me a way to solve it. Also i was looking for
r.in.proj' folder in the source code but couldn't find it . It was there on
the link you send but not on the svn repo. Should i directly copy the files
from there to the local repo.


These two modules are in addons. Compare the SVN repo with the Trac URLs
and you will find how to get them.

 Source code for r.in.proj and v.in.proj:
 https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.in.proj
 https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.proj


Please, stay on mailing list.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSOC project proposal: GUI plugin system for GRASS GIS

[Vaclav Petras]

Hello.

On Tue, Mar 10, 2015 at 3:46 PM, jyoti misra jyotimisra...@gmail.com
wrote:

 Dear Sir/Madam,

 Myself Jyoti currently working under Dr. KS Rajan as a research student
in Spatial Informatics Lab, IIIT hyderabad . I am currently working in Land
Use modelling of Barrack valley region. Previously i have worked on
Billboard placement optimization problem considering the spatial ,temporal
and traffic features.

 I am interested in working with grass org under the project GUI plugin
system for GRASS GIS. The project is interesting and I have some idea of
the technologies requires for the project as i have already worked in
Python , c/c++.

Good. Now you should find some enhancements or bugs in GRASS GIS bug
tracker [1] and implement or fix them before the application evaluation to
show level of you proficiency [2, 3].

You can also select from this list:

Enhancement: Let users save/load SQL statements in wxGUI attribute table
manager
http://trac.osgeo.org/grass/ticket/1205

Bug: Quotes not preserved in command after pressing enter in GUI command
console
http://trac.osgeo.org/grass/ticket/1435
http://trac.osgeo.org/grass/ticket/1437

Enhancement: Store map elements such as legend, text and scale bar in
workspace file.
http://trac.osgeo.org/grass/ticket/2484

Enhancement: Possibility to automatically load last used workspace when
GRASS GIS GUI starts
http://trac.osgeo.org/grass/ticket/2604

Enhancement: Store recently used workspaces and offer them in the menu
http://trac.osgeo.org/grass/ticket/2604

Enhancement: Implement georeferenced image output for Save display...
function in GUI and d.out.file module (and its wxGUI implementation)
http://trac.osgeo.org/grass/ticket/977

Bug: Undefined settings variable issue in bivariate scatterplot tool
http://trac.osgeo.org/grass/ticket/2247

Enhancement: Button, documentation and perhaps something more interactive
for finding EPSG codes online rather then in GRASS GIS list
http://trac.osgeo.org/grass/ticket/26

However, you can explore the open issues on GRASS GIS bug tracker yourself.
Just keep in mind that this GSoC project would be in Python and wxPython.
You can attempt to solve more of these tasks, the more the better. In any
case, the thing you select and do should be in Python and should
sufficiently represent your skills. Draft implementation of non-GUI (model)
part of the plugin system would be helpful to understand the issues which
you should address in the application.

In any case, start with compiling GRASS GIS from source code (trunk) from
Subversion repository [4], reading tips for students [5] and going through
instructions for other students [6, 7] (you can use Nabble [8] for that).

Also read Submitting rules [9] and how-to [10] for wxGUI development. Also
learn how to do basic tasks in GRASS GIS graphical user interface (called
wxGUI), use e.g. GRASS wiki or the manual as learning resource.

Please, always create a new thread on mailing list for distinct topics.

Best,
Vaclav

[1] https://trac.osgeo.org/grass/query
[2]
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
[3] http://lists.osgeo.org/pipermail/soc/2015-March/002908.html
[4] http://trac.osgeo.org/grass/wiki/DownloadSource
[5] http://trac.osgeo.org/grass/wiki/GSoC/2015#Tipsforstudents
[6] http://lists.osgeo.org/pipermail/grass-dev/2015-March/074420.html
[7] http://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html
[8] http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
[9] http://trac.osgeo.org/grass/wiki/Submitting/wxGUI
[10] http://grasswiki.osgeo.org/wiki/WxGUI_Programming_Howto

 Please guide me in the project and provide some docs and links where i
can proceed with solving it. Also I want to know whether someone is already
committed to this Project or not?

 Regards,
 Jyoti Misra
 Btech and Ms by research in Spatial Informatics
 International Institute Of Information Technology ,Hyderabad

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

[GRASS-dev] GSOC project proposal

[Sarthak Agarwal]

Dear Sir/Madam,

Myself Sarthak currently working under Dr. KS Rajan as a research student in 
Spatial Informatics Lab, IIIT hyderabad . I am currently working in spatial 
databases by optimizing the performance of mongoDb for spatial databases. 
Previously i have worked on Billboard placement optimization problem 
considering the spatial ,temporal and traffic features.

I am interested in working with grass org under the project New easy-to-use 
command line interface for GRASS GIS. The problem looks interesting to me. I 
am familiar with the technologies needed for this project.As i have already 
worked in c++ and python .

Can you please provide me with some more literature and links to understand the 
underlying concept behind the problem and a direction to solve it. Also I want 
to know whether someone is already committed to this Project or not? 

Regards,
Sarthak Agarwal
Btech and Ms by research in Spatial Informatics
International Institute Of Information Technology ,Hyderabad
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC project proposal

[Vaclav Petras]

On Mon, Mar 9, 2015 at 6:32 PM, sarthak agarwal sarthak0...@gmail.com
wrote:

 Dear Sir/Madam,

 Myself Sarthak currently working under Dr. KS Rajan as a research student
 in Spatial Informatics Lab, IIIT hyderabad . I am currently working in
 spatial databases by optimizing the performance of mongoDb for spatial
 databases. Previously i have worked on Billboard placement optimization
 problem considering the spatial ,temporal and traffic features.

 I am interested in working with grass org under the project New
 easy-to-use command line interface for GRASS GIS*. *The problem looks
 interesting to me. I am familiar with the technologies needed for this
 project.As i have already worked in c++ and python .


Hi,

this sounds good. You should find some enhancement or bug in GRASS GIS bug
tracker [1] and implement or fix before the application evaluation it to
show level of you proficiency [2, 3].

For example an enhancement ticket #1204 related to invoking GRASS. The wish
is to start grass7 command with a wxGUI workspace file as a parameter [4].

Another option is to continue in implementing of related #2579, enhancement
to provide command line parameter to execute modules. However, the big
issue there is more the discussion about the interface rather then the
implementation itself which is partially done already.

More challenging option is to implement some part of the GSoC project, e.g.
for rasters or for PostGIS vectors. This is of course highly related task
but it can be tricky and what you need is something which is working well
before the application evaluation. More smaller tasks might a better idea.

To understand how projections (coordinate systems) work in GRASS GIS (see
below), it might be advantageous for you to implement r3.proj module which
would project 3D rasters from one GRASS Location to another. r.proj module
is in C but for start r3.proj module could be in Python and would use
r.proj in the background (similar idea can be ussed for GRASS imagery
groups and temporal datasets which also don't have their proj module).
Further, you could try to write r3.in.proj module which would import 3D
raster data in one projection to GRASS Database with another projection
(see source code of r.in.proj). See below for more resources on this topic.

Writing tests for related things such as #2579, or modules r.in.proj,
v.in.proj or the other modules mentioned below might be quite good
introduction to the topic but to show your skill you might want to combine
it with some other task which would involve actual coding.

However, you can explore the open issues on GRASS GIS bug tracker yourself.
Just keep in mind that this GSoC project would be in Python, so the thing
you select be in Python.

In any case, start with compiling GRASS GIS from source code from
Subversion repository [6].

[1] https://trac.osgeo.org/grass/query
[2]
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
[3] http://lists.osgeo.org/pipermail/soc/2015-March/002908.html
[4] https://trac.osgeo.org/grass/ticket/1204
[5] http://trac.osgeo.org/grass/ticket/2579
[6] http://trac.osgeo.org/grass/wiki/GSoC/2015#Tipsforstudents


 Can you please provide me with some more literature and links to
 understand the underlying concept behind the problem and a direction to
 solve it.


Start with running GRASS GIS and playing with data in different projections
in case you are not familiar with GRASS GIS already. Read through the
related manual page [7] and/or tutorials online on getting your data into
GRASS Database.

Definitively read the code from various projects and other things linked in
the GSoC idea [8]. Go through the modules related to importing, linking,
exporting and projecting data, some of them are linked below. Look also at
how GRASS GIS can connect to PostGIS [9].

[7] http://grass.osgeo.org/grass70/manuals/helptext.html
[8]
http://trac.osgeo.org/grass/wiki/GSoC/2015#Neweasy-to-usecommandlineinterfaceforGRASSGIS
[9] http://grasswiki.osgeo.org/wiki/PostGIS

Related modules:
http://grass.osgeo.org/grass70/manuals/r.in.gdal.html
http://grass.osgeo.org/grass70/manuals/v.in.ogr.html
http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html
http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html
http://grass.osgeo.org/grass70/manuals/r.proj.html
http://grass.osgeo.org/grass70/manuals/v.proj.html
http://grass.osgeo.org/grass70/manuals/r.external.html
http://grass.osgeo.org/grass70/manuals/v.external.html

Source code for r.in.proj and v.in.proj:
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.in.proj
https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.proj


Also I want to know whether someone is already committed to this Project or
 not?

 No, at least nobody wrote to the mailing list.

Best,
Vaclav

Regards,
 Sarthak Agarwal
 Btech and Ms by research in Spatial Informatics
 International Institute Of Information Technology ,Hyderabad

Re: [GRASS-dev] GSoc Project on GRASS

[Hamish]

Naveen wrote:
 I am a M.S. by research student from Lab for Spatial Informatics,
 International Institute of Information and Technology, Hyderabad, India.

 Last year I had proposed idea on GRASS magic extension for the IPython
 Notebook in GSOC-2013. 
 But unfortunately the idea didn't get selected. Would it be a
 good idea to propose the same project this year also?

Hi Naveen,

Probably reusing the exact same proposal as last year may not improve results, 
but an enhanced and rewritten proposal could be interesting to look at. Also 
remember that Google lets you submit multiple proposals (maybe up to about 
5(?)) so if you really wanted to work on the iPython extension, but are not 
sure if it matches the dev team's current needs and priorities, you could 
always make multiple proposals. I'd be careful not to put too many applications 
in though, often it is better to invest the time in a couple high-quality 
proposals instead of putting in a whole bunch of applications which aren't as 
well developed.


Massimo (epi) is our iPython Notebook expert, it would be good to discuss any 
ideas with him.



regards,
Hamish

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

Re: [GRASS-dev] GSoc Project on GRASS

[Markus Neteler]

On Thu, Feb 6, 2014 at 11:35 PM, Naveen Panwar panwar...@gmail.com wrote:
 Hello all,

 I am a M.S. by research student from Lab for Spatial Informatics,
 International Institute of Information and Technology, Hyderabad, India.

 Last year I had proposed idea on GRASS magic extension for the IPython
 Notebook in GSOC-2013.
 But unfortunately the idea didn't get selected. Would it be a good idea to
 propose the same project this year also?

 OR if there is another idea based on python and better suited for me, I am
 willing to contribute.

Please add your ideas to

http://trac.osgeo.org/grass/wiki/GSoC/2014

Best
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoc Project on GRASS

[Naveen Panwar]

Hello all,

I am a M.S. by research student from Lab for Spatial Informatics,
International Institute of Information and Technology, Hyderabad, India.

Last year I had proposed idea on GRASS magic extension for the IPython
Notebook http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013 in
GSOC-2013.
But unfortunately the idea didn't get selected. Would it be a good idea to
propose the same project this year also?

OR if there is another idea based on python and better suited for me, I am
willing to contribute.

It would be a great help if I can get suggestions on this.

Thanking you in advance.

--
Regards,
*Naveen Panwar*
IIIT-Hyderabad, India.
+91-9030736015

http://lsi.iiit.ac.in/naveen.panwar
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC Project: Temporal Algebra for GRASS

[Thomas Leppelt]

Hi all,

in my previous mail I forgot to introduce myself. My name is Thomas Leppelt
and I'm a PhD student at the Thuenen-Institute in Germany. I'm working
together with Soeren Gebbert, who is my mentor in our Google Summer of Code
project 2013. Our aim for this summer is to develop a temporal algebra for
raster and vector maps in GRASS. You can find some more details on the GSoC
page:

https://google-melange.appspot.com/gsoc/project/google/gsoc2013/mastho/5001

It is the first time for me to develop software for an open source project.
So I'm very curious and I hope that we can contribute a little piece of
software in collaboration with the community.

Best regards

Thomas
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Project: Temporal Algebra for GRASS

[Blumentrath, Stefan]

Hi Sören and Thomas

The last few days I explored a little bit the possibilities of the temporal GIS 
framework in GRASS 7.
I have to say, that I already now love it though I just have touched the 
surface of it possibilities!!! All who contributed to this development, thank 
you very much, you really did an amazing job! And I am really looking forward 
to the forthcoming improvements in the GSoC 2013 project!

The way I acquainted myself with the concept of the new tools was through 
Sörens presentation at the geostats course. What I would found really valuable 
would be a collection of more real life examples, where and how the tools are 
used in practice and for different purposes. Is there already a wiki page 
(which I am not aware of) with examples like how to calculate Growing Degree 
Days, Drought periods (in the context of climate data) and stuff like that?

Cheers
Stefan


From: grass-dev-boun...@lists.osgeo.org 
[mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Thomas Leppelt
Sent: 13. juni 2013 11:37
To: grass-dev@lists.osgeo.org
Subject: [GRASS-dev] GSoC Project: Temporal Algebra for GRASS

Hi all,
in my previous mail I forgot to introduce myself. My name is Thomas Leppelt and 
I'm a PhD student at the Thuenen-Institute in Germany. I'm working together 
with Soeren Gebbert, who is my mentor in our Google Summer of Code project 
2013. Our aim for this summer is to develop a temporal algebra for raster and 
vector maps in GRASS. You can find some more details on the GSoC page:

https://google-melange.appspot.com/gsoc/project/google/gsoc2013/mastho/5001
It is the first time for me to develop software for an open source project. So 
I'm very curious and I hope that we can contribute a little piece of software 
in collaboration with the community.

Best regards

Thomas
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev