[GRASS-dev] GSoC 2017 - SOS tools

2017-03-08 Thread Ondřej Pešek
Hello everyone,

I am Ondrej Pesek, a student at CTU in Prague (studying master studies in
geomatics) and I would like to participate in GSoC 2017.

I am most interested in the SOS topic [1]. I will work during summer in
NINA where I should work with istSOS, So I'm thinking about istSOS also in
this topic.

I prefer something in python as I made my bachelor thesis in python (aerial
data shift on a trajectory - plugin for QGIS) and I participated in last
GSoC (PyQt based GUI for GRASS), but I have also basic knowledge of C++ and
now I'm trying to get little bit familiar with Java.
I have no experiences with SOS but I'm open to learn new skills.

Looking forward to your reply.

Have a nice day,
Ondrej


[1] https://trac.osgeo.org/grass/wiki/GSoC/2017#SOStools
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2017 - SOS tools

2017-03-08 Thread Luca Delucchi
On 8 March 2017 at 11:09, Ondřej Pešek  wrote:
> Hello everyone,
>

Hi Ondrej

> I am Ondrej Pesek, a student at CTU in Prague (studying master studies in
> geomatics) and I would like to participate in GSoC 2017.
>
> I am most interested in the SOS topic [1]. I will work during summer in NINA
> where I should work with istSOS, So I'm thinking about istSOS also in this
> topic.
>

happy to see someone interested... maybe your supervisor in NINA could
be also the co-mentor or he could be the mentor and me as co-mentor
;-)

> I prefer something in python as I made my bachelor thesis in python (aerial
> data shift on a trajectory - plugin for QGIS) and I participated in last
> GSoC (PyQt based GUI for GRASS), but I have also basic knowledge of C++ and
> now I'm trying to get little bit familiar with Java.
> I have no experiences with SOS but I'm open to learn new skills.
>

If you want to follow my idea, I suggest you to start to work with SOS
specially through owslib to see what is the limit of this library and
to be able to prepare a good GSOC timetable, the first weeks could be
spent to improve owslib.
For example this issue [0] could be useful to implement

I (or someone I know) can provide a server or you could install easily
istSOS on your computer and make tests using it.

Please ask me for any issue, privately or here...

> Looking forward to your reply.
>
> Have a nice day,
> Ondrej
>

[0] https://github.com/geopython/OWSLib/issues/347

-- 
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 2017 - SOS tools

2017-03-30 Thread Ondřej Pešek
Hi,

here is my draft on GSoC page [1]. I have discussed it with Luca and also
with Stefan Blumentrath and Matteo De Stefano (potential co-mentors).

Feel free to comment, discuss and suggest. If there aren't any remarks, I
will mark it as final at the weekend.

[1]
https://docs.google.com/document/d/1KL_YoaLNQGHakHAtDOiPyPFIwptvFkbTQax8nYX1M20/edit?usp=sharing

Regards,
Ondrej

2017-03-08 11:35 GMT+01:00 Luca Delucchi :

> On 8 March 2017 at 11:09, Ondřej Pešek  wrote:
> > Hello everyone,
> >
>
> Hi Ondrej
>
> > I am Ondrej Pesek, a student at CTU in Prague (studying master studies in
> > geomatics) and I would like to participate in GSoC 2017.
> >
> > I am most interested in the SOS topic [1]. I will work during summer in
> NINA
> > where I should work with istSOS, So I'm thinking about istSOS also in
> this
> > topic.
> >
>
> happy to see someone interested... maybe your supervisor in NINA could
> be also the co-mentor or he could be the mentor and me as co-mentor
> ;-)
>
> > I prefer something in python as I made my bachelor thesis in python
> (aerial
> > data shift on a trajectory - plugin for QGIS) and I participated in last
> > GSoC (PyQt based GUI for GRASS), but I have also basic knowledge of C++
> and
> > now I'm trying to get little bit familiar with Java.
> > I have no experiences with SOS but I'm open to learn new skills.
> >
>
> If you want to follow my idea, I suggest you to start to work with SOS
> specially through owslib to see what is the limit of this library and
> to be able to prepare a good GSOC timetable, the first weeks could be
> spent to improve owslib.
> For example this issue [0] could be useful to implement
>
> I (or someone I know) can provide a server or you could install easily
> istSOS on your computer and make tests using it.
>
> Please ask me for any issue, privately or here...
>
> > Looking forward to your reply.
> >
> > Have a nice day,
> > Ondrej
> >
>
> [0] https://github.com/geopython/OWSLib/issues/347
>
> --
> 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 2017 - SOS tools

2017-03-30 Thread massimo di stefano
Hi Ondrej, 
what about working on your gsoc 2016 idea?

I guess we all want the GSOC be an “instrument” to involve students in the 
project they chose and “hopefully” have them continuing what they started …
IMHO this “continuation” is very important and is a clear sign of how much the 
student cares about to the project itself.

I’ve had bad experience with gsoc, I know the students are not obligated in 
continuing to contribute to the project after the GSOC period .. but I think 
that’s what we hope. 
It is a very bad feeling when a mentor spent the whole summer following a 
student which then literally disappear after the application period  

for your idea i can see the following improvements:
- porting to qt5
- porting to py3 (only task.py need some twiking)
- complete the modules, I tried it and I found it incomplete.

I can co-mentor if interested.

Massimo.


> On Mar 8, 2017, at 5:09 AM, Ondřej Pešek  wrote:
> 
> Hello everyone,
> 
> I am Ondrej Pesek, a student at CTU in Prague (studying master studies in 
> geomatics) and I would like to participate in GSoC 2017. 
> 
> I am most interested in the SOS topic [1]. I will work during summer in NINA 
> where I should work with istSOS, So I'm thinking about istSOS also in this 
> topic. 
> 
> I prefer something in python as I made my bachelor thesis in python (aerial 
> data shift on a trajectory - plugin for QGIS) and I participated in last GSoC 
> (PyQt based GUI for GRASS), but I have also basic knowledge of C++ and now 
> I'm trying to get little bit familiar with Java. 
> I have no experiences with SOS but I'm open to learn new skills. 
> 
> Looking forward to your reply.
> 
> Have a nice day, 
> Ondrej
> 
> 
> [1] https://trac.osgeo.org/grass/wiki/GSoC/2017#SOStools 
> 
> ___
> 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 2017 - SOS tools

2017-03-30 Thread Helmut Kudrnovsky
Ondřej Pešek wrote
> Hello everyone,
> 
> I am Ondrej Pesek, a student at CTU in Prague (studying master studies in
> geomatics) and I would like to participate in GSoC 2017.
> 
> I am most interested in the SOS topic [1]. I will work during summer in
> NINA where I should work with istSOS, So I'm thinking about istSOS also in
> this topic.
> 
> I prefer something in python as I made my bachelor thesis in python
> (aerial
> data shift on a trajectory - plugin for QGIS) and I participated in last
> GSoC (PyQt based GUI for GRASS), but I have also basic knowledge of C++
> and
> now I'm trying to get little bit familiar with Java.
> I have no experiences with SOS but I'm open to learn new skills.
> 
> Looking forward to your reply.
> 
> Have a nice day,
> Ondrej
> 
> 
> [1] https://trac.osgeo.org/grass/wiki/GSoC/2017#SOStools
> 
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-dev

As mentioned on the SoC ML :

* There are *3 evaluation periods* this year where mentors are required to
complete an evaluation of their student. After the first 4 weeks of coding,
after 8 weeks of coding and then at the end (after 12 weeks of coding). The
evaluation forms are shorter than previous years so they should take less
time to complete.

Please check your timeline and may adapt there reflecting this requirements
for this year. 




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/GSoC-2017-SOS-tools-tp5311345p5315015.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2017 - SOS tools

2017-03-30 Thread Ondřej Pešek
Hi Massimo,

2017-03-30 14:50 GMT+02:00 massimo di stefano :
> Hi Ondrej,
> what about working on your gsoc 2016 idea?
>
> I guess we all want the GSOC be an “instrument” to involve students in the
> project they chose and “hopefully” have them continuing what they started …
> IMHO this “continuation” is very important and is a clear sign of how much
> the student cares about to the project itself.
>
> I’ve had bad experience with gsoc, I know the students are not obligated in
> continuing to contribute to the project after the GSOC period .. but I think
> that’s what we hope.
> It is a very bad feeling when a mentor spent the whole summer following a
> student which then literally disappear after the application period
>

Of course, I would like to continue in my 2016 GSoC project, but there
is a problem with my internship at the Norwegian Institute for Nature
Research (NINA), as mentioned in my proposal. I'm afraid that I won't
be able to handle working on two completely different projects.

But in NINA, I will be working on sensor data, especially with istSOS.
I (and potential co-mentors) can see quite significant overlap, so I
expect synergies and mutual benefits.

But my last year project is not dead, it's just... hmmm...
hibernating. I have done some small changes in November and I still
have some notes with what I would like to improve. The nearest
improvement is creating module from those scripts - I'm just playing
with pyGrass, so I hope that I have some time before the start of this
year project (or before my NINA internship, if not accepted).
Another nice goal should be using this code to GRASS plugin for QGIS,
because QGIS has PyQt based GUI, but it's the future.

> for your idea i can see the following improvements:
> - porting to qt5
> - porting to py3 (only task.py need some twiking)
> - complete the modules, I tried it and I found it incomplete.
>

Yes, I'm planning also py3. But I didn't contemplated about qt5, I
have to study it first.
Please, feel free to create an issue on the github page [1]. I welcome
your comments and opinions.

>
> Massimo.
>
>

[1] https://github.com/pesekon2/GRASS-Qt-based-GUI/issues

Ondrej 

  https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail";
target="_blank">https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif";
width="46" height="29" style="width: 46px; height: 29px;" />
Bez virů. https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail";
target="_blank" style="color: #4453ea;">www.avast.com   



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

Re: [GRASS-dev] GSoC 2017 - SOS tools

2017-05-11 Thread Ondřej Pešek
Hello everyone,

I'm glad to hear that my project (SOS tools in GRASS GIS) was accepted! I'm
looking forward to work on this project.

I have created wikipage for this project on Trac [1], repository will be
setted in the following days.

[1] https://trac.osgeo.org/grass/wiki/GSoC/2017/SOSInGRASS

2017-03-31 0:33 GMT+02:00 Ondřej Pešek :

> Hi Massimo,
>
> 2017-03-30 14:50 GMT+02:00 massimo di stefano :
> > Hi Ondrej,
> > what about working on your gsoc 2016 idea?
> >
> > I guess we all want the GSOC be an “instrument” to involve students in
> the
> > project they chose and “hopefully” have them continuing what they
> started …
> > IMHO this “continuation” is very important and is a clear sign of how
> much
> > the student cares about to the project itself.
> >
> > I’ve had bad experience with gsoc, I know the students are not obligated
> in
> > continuing to contribute to the project after the GSOC period .. but I
> think
> > that’s what we hope.
> > It is a very bad feeling when a mentor spent the whole summer following a
> > student which then literally disappear after the application period
> >
>
> Of course, I would like to continue in my 2016 GSoC project, but there
> is a problem with my internship at the Norwegian Institute for Nature
> Research (NINA), as mentioned in my proposal. I'm afraid that I won't
> be able to handle working on two completely different projects.
>
> But in NINA, I will be working on sensor data, especially with istSOS.
> I (and potential co-mentors) can see quite significant overlap, so I
> expect synergies and mutual benefits.
>
> But my last year project is not dead, it's just... hmmm...
> hibernating. I have done some small changes in November and I still
> have some notes with what I would like to improve. The nearest
> improvement is creating module from those scripts - I'm just playing
> with pyGrass, so I hope that I have some time before the start of this
> year project (or before my NINA internship, if not accepted).
> Another nice goal should be using this code to GRASS plugin for QGIS,
> because QGIS has PyQt based GUI, but it's the future.
>
> > for your idea i can see the following improvements:
> > - porting to qt5
> > - porting to py3 (only task.py need some twiking)
> > - complete the modules, I tried it and I found it incomplete.
> >
>
> Yes, I'm planning also py3. But I didn't contemplated about qt5, I
> have to study it first.
> Please, feel free to create an issue on the github page [1]. I welcome
> your comments and opinions.
>
> >
> > Massimo.
> >
> >
>
> [1] https://github.com/pesekon2/GRASS-Qt-based-GUI/issues
>
> Ondrej  style="border-top: 1px solid #D3D4DE;">
> 
>href="https://www.avast.com/sig-email?utm_medium=email&;
> utm_source=link&utm_campaign=sig-email&utm_content=webmail"
> target="_blank"> src="https://ipmcdn.avast.com/images/icons/icon-envelope-
> tick-round-orange-animated-no-repeat-v1.gif"
> width="46" height="29" style="width: 46px; height: 29px;" />
> Bez virů.  href="https://www.avast.com/sig-email?utm_medium=email&;
> utm_source=link&utm_campaign=sig-email&utm_content=webmail"
> target="_blank" style="color: #4453ea;">www.avast.com
>  
> 
> 
>  height="1">
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2017 - SOS tools

2017-05-12 Thread Moritz Lennert

Hi Ondřej,

On 11/05/17 19:15, Ondřej Pešek wrote:

Hello everyone,

I'm glad to hear that my project (SOS tools in GRASS GIS) was accepted!


Congratulations !


I'm looking forward to work on this project.


And we are looking forward to see the results ! :-)

Don't hesitate to discuss anything you need on this list.

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