OSGeo - User contributions [en]

Google Summer of Code 2018 Accepted

2018-04-23T18:22:51Z

Wiki-Masterflorin:

Google Summer of Code 2018 Accepted

2018-04-23T18:21:42Z

Wiki-Masterflorin:

Google Summer of Code 2018 Accepted

2018-04-23T18:21:03Z

Wiki-Masterflorin:

Google Summer of Code Application 2018

2018-01-22T17:54:28Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Application Status ==

'''''On-going''''' (OSGeo's application is due 23 January [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=01&day=23&hour=17&min=0&sec=0%2018.00UTC 17:00 UTC])

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': http://osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C/C++, standards, python, sql, database
* '''Topic Tags''': Mapping, citizen science, gis, geospatial, open science
* '''Ideas List''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers.
</pre>

* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
</pre>

* '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Google+ url''': https://plus.google.com/communities/105969056638310510633
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2018 will be our 12th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 180 students in total through the GSoC program). Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
* '''How many potential mentors have agreed to mentor this year?''' 11 - 15
* '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Administrative).
* '''How will you help your students stay on schedule to complete their projects?''': We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
* '''How will you get your students involved in your community during GSoC?''': Each student is expected to discuss openly the proposal with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment. We aim to foster closer communication by engaging our all students and community mentors through a accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, encourage different perspectives within the open source geospatial community.
* '''How will you keep students involved with your community after GSoC?''': We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''
Year: pass/total
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''What year was your project started?''' 2006

* '''Where does your source code live?''' OSGeo is an umbrella organization that entails several projects. Each project has their own repository either on github or on OSGeo's servers

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences each year all around the world. We believe the future leaders of the geospatial industry are these students.

[Back to [[Google Summer of Code 2018]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2018

2018-01-09T12:55:02Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Application Status ==

'''''Completed''''' (OSGeo's application is due 23 January [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=01&day=23&hour=17&min=0&sec=0%2018.00UTC 17:00 UTC])

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Website URL''': http://osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C++, standards, python, C, sql
* '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science)
* '''Ideas List''': link to Ideas wiki page: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers.
</pre>
* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
</pre>
* '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/IRC
* '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Google+ url''': https://plus.google.com/communities/105969056638310510633
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2017 will be our 11th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 167 students in total through the GSoC program). Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
* '''How many potential mentors have agreed to mentor this year?''' 20+
* '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Administrative).
* '''How will you help your students stay on schedule to complete their projects?''': We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
* '''How will you get your students involved in your community during GSoC?''': Each student is expected to discuss openly the proposal with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment.
* '''How will you keep students involved with your community after GSoC?''': We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''
Year: pass/total
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation
* '''What year was your project started?''' The OSGeo foundation began in 2006, and we celebrated our 12th year as a foundation on 4 February (http://www.osgeo.org/node/1766).

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events each year all around the world. We believe the future leaders of the geospatial industry are these students.

[Back to [[Google Summer of Code 2018]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2018

2018-01-09T12:51:45Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Application Status ==

'''''Completed''''' (OSGeo's application is due 23 January [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=01&day=23&hour=17&min=0&sec=0%2018.00UTC 17:00 UTC])

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Website URL''': http://osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C++, standards, python, C, sql
* '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science)
* '''Ideas List''': link to Ideas wiki page: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers.
</pre>
* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
</pre>
* '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/IRC
* '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Google+ url''': https://plus.google.com/communities/105969056638310510633
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2017 will be our 11th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 167 students in total through the GSoC program). Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
* '''How many potential mentors have agreed to mentor this year?''' 20+
* '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Administrative).
* '''How will you help your students stay on schedule to complete their projects?''': We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
* '''How will you get your students involved in your community during GSoC?''': Each student is expected to discuss openly the proposal with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment.
* '''How will you keep students involved with your community after GSoC?''': We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''
Year: pass/total
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation
* '''What year was your project started?''' The OSGeo foundation began in 2006, and we celebrated our 11th year as a foundation on 4 February (http://www.osgeo.org/node/1766).

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events each year all around the world. We believe the future leaders of the geospatial industry are these students.

[Back to [[Google Summer of Code 2018]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2018

2018-01-09T12:49:18Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Application Status ==

'''''Completed''''' (OSGeo's application is due 23 January [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=01&day=23&hour=17&min=0&sec=0%2018.00UTC 17:00 UTC])

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Website URL''': http://osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C++, standards, python, C, sql
* '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science)
* '''Ideas List''': link to Ideas wiki page: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers.
</pre>
* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
</pre>
* '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/IRC
* '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Google+ url''': https://plus.google.com/communities/105969056638310510633
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2017 will be our 11th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 167 students in total through the GSoC program). Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
* '''How many potential mentors have agreed to mentor this year?''' 20+
* '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Administrative).
* '''How will you help your students stay on schedule to complete their projects?''': We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
* '''How will you get your students involved in your community during GSoC?''': Each student is expected to discuss openly the proposal with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment.
* '''How will you keep students involved with your community after GSoC?''': We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''
Year: pass/total
2017:
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation
* '''What year was your project started?''' The OSGeo foundation began in 2006, and we celebrated our 11th year as a foundation on 4 February (http://www.osgeo.org/node/1766).

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events each year all around the world. We believe the future leaders of the geospatial industry are these students.

[Back to [[Google Summer of Code 2018]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2018

2018-01-09T12:48:38Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Application Status ==

'''''Completed''''' (OSGeo's application is due 23 January [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=01&day=23&hour=17&min=0&sec=0%2018.00UTC 17:00 UTC])

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Website URL''': http://osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C++, standards, python, C, sql
* '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science)
* '''Ideas List''': link to Ideas wiki page: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers.
</pre>
* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
</pre>
* '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/IRC
* '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Google+ url''': https://plus.google.com/communities/105969056638310510633
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2017 will be our 11th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 167 students in total through the GSoC program). Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
* '''How many potential mentors have agreed to mentor this year?''' 20+
* '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Administrative).
* '''How will you help your students stay on schedule to complete their projects?''': We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
* '''How will you get your students involved in your community during GSoC?''': Each student is expected to discuss openly the proposal with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment.
* '''How will you keep students involved with your community after GSoC?''': We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''
Year: pass/total
2017:
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation
* '''What year was your project started?''' The OSGeo foundation began in 2006, and we celebrated our 11th year as a foundation on 4 February (http://www.osgeo.org/node/1766).

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events each year all around the world. We believe the future leaders of the geospatial industry are these students.

[Back to [[Google Summer of Code 2018]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Recommendations for Students

2018-01-09T12:41:08Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2018]] wiki page.
* Check out the [[Google_Summer_of_Code_2018_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ GOOGLE SUMMER OF CODE 2017 PROGRAM RULES].
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]
* If you are new to OSGeo, take the time to familiarize with the [http://www.osgeo.org/content/foundation/about.html Open Source Geospatial Foundation]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.
We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal.
Developers will then assist students in filling the proposal template (see below) and will prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successfull teamwork and interplay of project, mentors and students.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period?

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user:
* GIS programming and other software programming:

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://webchat.freenode.net IRC client]) 

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* https://gitter.im/pgRouting/pgrouting
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#geonode

[[Category: Google Summer of Code]]

Google Summer of Code 2018 Ideas

2018-01-08T21:01:05Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2018]] wiki page.

* See also ideas from [[Google Summer of Code 2016 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].
-----

== OSGeo Google Summer of Code 2018 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!

* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2017_Administrative]] wiki page.

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

If you are an OSGeo project lead about to add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2017 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look! -->

[[Image:logo-qgis.png|60px|right]]
* [https://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2017 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.




[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2017_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.

[[Image:Pycsw-logo.png|60px|right]]
* [https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017'''pycsw''' Ideas]: [http://pycsw.org pycsw] is an OGC CSW server implementation written in Python, and provides a metadata and catalogue component for spatial data infrastructures. The pycsw project is looking for students interested in Python and search, come join us!







[[Image:Logo-istSOS.png|100px|right]]
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2017/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.

[[Image:Pywps logo.png|80px|right]]
* [https://github.com/geopython/pywps/wiki/GSoC-2017-ideas '''PyWPS''' Ideas]: [http://pywps.org/ PyWPS] is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python. PyWPS enables integration, publishing and execution of Python processes via the WPS standard.








=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|500px|center]]

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']


* Feb 27: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 20: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* April 3: Student application deadline.
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 30: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 26 - 30: Phase 1 evaluation
* July 28: Phase 2 evaluation
* August 21-29: '''Pencils down!'''
* August 29 - September 5: Final evaluations
* September 6: Final results announced

[Back to [[Google Summer of Code 2017]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2018 Administrative

2018-01-08T20:52:15Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2018]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2018 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code 2018.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2018 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!



[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]

.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor''' (please write down the title of the idea, not link to ideas page!)
|-
|1
|Tom
|Kralidis
|tomkralidis
|tomkralidis at gmail.com
|pycsw
|[https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017 pycsw filter abstraction, Elasticsearch backend, admin HTTP API]
|-
|2
|Gabriele
|Prestifilippo
|gabry501
|gabriele.prestifilippo at gmail com
|ESA-NASA WebWorldWind
|HeatMap Layer, Plug-in, Create Your Own
|-
|3
|Vicky
|Vergara
|cvvergara
|vicky at georepublic de
|pgRouting
|Develop new functionality into pgRouting
|-
|4
|Daniel
|Kastl
|dkastl
|daniel at georepublic de
|pgRouting
|Connect more boost functions to pgRouting
|-
|5
|Rohith
|Reddy
|sankepallyrohithreddy
|rohithreddy2219 at gmail com
|pgRouting
|Connect more boost functions to pgRouting
|-
|6
|Patrick
|Hogan
|HamletAlive
|patrick.hogan at nasa gov
|ESA-NASA WebWorldWind
|CitySmart Urban Infrastructure Management
|-
|7
|Anna
|Petrasova
|
|kratochanna at gmail com
|GRASS GIS
|3D rendering, 3D viewer
|-
|8
|Vaclav
|Petras
|
|wenzeslaus at gmail com
|GRASS GIS
|Jupyter Notebook, Benchmarking, Testing, ...
|-
|9
|Jakub
|Balhar
|
|jakub at balhar net
|ESA-NASA WebWorldWind
|CitySmart Urban Infrastructure Management
|-
|10
|Alexandre
|Dubé
|
|adube at mapgears com
|OL3-Google-Maps
|Develop new features in the OL3-Google-Maps library
|-
|11
|Raphaël
|Gagnon
|
|rgagnon at mapgears com
|OL3-Google-Maps
|Develop new features in the OL3-Google-Maps library
|-
|12
|Stefan
|Steiniger
|
|sstein at geo-uzh-ch
|OpenTripPlanner
|Extending OpenTripPlanner with Real Time Modelling Functions
|-
|13
|Jorge
|Rocha
|[[User:Jgrocha|Jgrocha]]
|jgr@di.uminho.pt
|QGIS
|Improve QGIS style interoperability, by reading and writing cartographic styles from other projects.
|-
|14
|Massimiliano
|Cannata
|[[User:maxi71|maxi]]
|massimiliano.cannata at gmail com
|istSOS
|Data analysis and statistical tools from sensor data
|-
|15
|Milan
|Antonovic
|[[User:mantonovic|mantonovic]]
|milan.antonovic at gmail com
|istSOS
|Upgrade and finalize the istSOS JavaScript Core Library
|-
|16
|Martin
|Landa
|
|landa.martin at gmail com
|GRASS GIS
|GUI, rendering
|-
|17
|Alexander
|Bruy
|alexbruy
|alexander dot bruy at gmail dot com
|QGIS
|Processing Framework improvements
|-
|18
|Barry
|Rowlingson
|
|b.rowlingson at gmail com
|QGIS
|R/QGIS Interface for Mapping
|-

|19
|Maria Antonia
|Brovelli
|
|maria dot brovelli at polimi dot it
|ESA-NASA WebWorldWind
|CitySmart Urban Infrastructure Management
|-

|20
|Jonas
|Eberle
|
|jonas dot eberle at gmx dot de
|PyWPS
|Publishing data to MapServer and pycsw, Process chaining capabilities, Web-based administration & process management
|-

|21
|Joaquin
|Del Cerro
|
|jjdelcerro at gvsig dot org
|gvSIG
|Data model for visualizations in gvSIG
|-

|22
|Alvaro
|Anguix
|
|aanguix at gvsig dot com
|gvSIG
|Data model for visualizations in gvSIG
|-

|23
|Julia
|Wagemann
|
|wagemann dot julia at gmx dot de
|QGIS / GRASS GIS
|WCS 2.0 plugin for QGIS, Jupyter Notebook examples with QGIS / GRASS GIS
|-

|24
|Tais
|TaGri
|
|tgrippa at ulb dot ac dot be
|GRASS GIS
|Additional GUI tools for image analysis (co-mentor for content)
|-

|25
|Nadia
|Chaer
|
|nadiachaer at gmail dot com
|gvSIG
|Educational games addon for gvSIG Batoví/Educa
|-

|26
|Francisco
|Puga
|
|fpuga at icarto dot es
|gvSIG
|Educational games addon for gvSIG Batoví/Educa
|-
|27
|Sean
|Barbeau
|
|barbeau at cutr dot usf dot edu
|OpenTripPlanner/OneBusAway
|Bikeshare Information for Transportation Apps
|-
|27
|Óg
|Crudden
|
|og dot crudden at gmail dot com
|OpenTripPlanner/OneBusAway
|Bikeshare Information for Transportation Apps
|-
|28
|Aaron
|Brethorst
|
|aaron at brethorsting dot com
|OpenTripPlanner/OneBusAway
|Bikeshare Information for Transportation Apps
|-
|29
|Adam
|Steer
|
|adam dot steer at anu dot edu dot au
|QGIS / GRASS GIS
|WCS 2.0 plugin for QGIS, Jupyter Notebook examples with QGIS / GRASS GIS
|-
|30
|Luca
|Delucchi
|
|lucadeluge gmail com
|GRASS GIS
|SOS tool for GRASS GIS
|-
|31
|Matteo
|De Stefano
|
|matteo dot destefano at nina dot no
|GRASS GIS
|SOS tool for GRASS GIS
|-
|32
|Mario
|Carrera
|
|mcarrera at gvsig dot com
|gvSIG
|Data model for visualizations in gvSIG
|-
|33
|Gérald
|Fenoy
|
|gerald dot fenoy at geolabs dot fr
|ZOO-Project
|SOS datastore for MapMint
|-
|34
|Sittichai
|Choosumrong
|
|sittichai dot ocu at gmail dot com
|ZOO-Project
|SOS input for MapMint4ME
|-
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates. 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.

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Mentor Summit ==

Each year Google hosts the "Mentor Summit" event at their headquarters. The tentative date for this year is: [https://groups.google.com/forum/#!msg/google-summer-of-code-mentors-list/OTwNTCujKDA/HuhFQQauAgAJ October 13-15 2017]. This year we are developing guidelines for who can represent OSGeo at the summit: see [[Google Summer of Code 2017 Mentor Summit]]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2018

2018-01-08T20:46:27Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2018 page ==

* OSGeo's [[Google_Summer_of_Code_Application_2018|application]] to GSoC 2018, as a mentoring organization.
* If you are a '''student''', please visit our [[Google Summer of Code 2018 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code 2018 Administrative]] page.




See also older Google Summer of Code
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 160+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

Google Code In 2017 Tasks

2017-10-26T19:58:42Z

Wiki-Masterflorin:

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Interested Mentors =

Please '''first fill out the Google form''' mentioned at the top of: [[Google Code In 2017 Mentors]]

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;User Interface
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

[[Category:Google Code In]]

Google Code In 2017

2017-09-21T18:57:12Z

Wiki-Masterflorin:

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

Central page for administering OSGeo participation in Google Code In 2017

= Background =

* Google Code In program has been [https://opensource.googleblog.com/2017/09/announcing-google-code-in-2017.html officially announced]
* [https://developers.google.com/open-source/gci/ Google Code In main page]
* [https://developers.google.com/open-source/gci/how-it-works How Google Code-in Works]
* [https://developers.google.com/open-source/gci/resources/example-tasks Examples of Google Code-in Tasks]
* [https://developers.google.com/open-source/gci/resources/media Logo, flyer and presentation]
* [https://developers.google.com/open-source/gci/help/responsibilities Roles and responsibilities of Students, Mentors and Admins]

= Timeline =

* [https://developers.google.com/open-source/gci/timeline Full timeline]
* Oct 9 2017: Open source organizations can apply to be mentoring organizations (we should have mentors and tasks by then)
* Nov 28 2017: Contest opens for entries by student participants
* Jan 15 2018: Deadline for students to claim new tasks
* Jan 17 2018: All student work must be submitted; contest ends
* Jan 18 2018: Mentoring organizations complete all evaluations of students’ work
* Jan 31 2018: Grand Prize Winners and Finalists announced
* June (exact dates TBD): Grand Prize Winner’s Trip

= Administrators =

* [[Margherita Di Leo]] <libravatar email="diregola@gmail.com"/>
* [[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/>
* [[Florin Cioloboc]] <libravatar email="cioloboc.florin@gmail.com"/>

= Interested mentors / volunteers =

Willing mentors must write to gsoc-admin(at)osgeo.org and will be sent a form to fill in.

= Kickoff (virtual) meeting =

* 2017-09-25 at [https://www.timeanddate.com/worldclock/fixedtime.html?year=2017&month=09&day=25&hour=20&min=0 20.00 UTC]
* On IRC in the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])
* agenda:
** discuss ideas for tasks for the students
** plan to share mentor invites to all OSGeo projects

= Open questions =

* The [https://developers.google.com/open-source/gci/how-it-works how it works] page doesn't mention how the word of this gets out to students, or does Google handle that?? How is promotion to students handled?? (Jeff)
* Discuss the opportunity to create "virtual environments" for the students to play with, and eventually come up with a patch? For example, for tasks that would otherwise require access to sensitive systems, e.g. SAC, web pages, etc.. (madi)
* It is not clear to me if it's possible to use more than one bug tracker or we must use the osgeo tracker for all the projects (madi)
* Is it necessary for the students to pick from different "types" of tasks or they can decide to complete only one type? (madi)

[[Category:Google Code In]]

Google Summer of Code 2017 Improvements

2017-09-05T16:07:15Z

Wiki-Masterflorin:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==

* See also lesson learned from '''[[Google Summer of Code 2011 Improvements|2011]]'''; '''[[Google Summer of Code 2012 Improvements|2012]]'''; '''[[Google Summer of Code 2013 Improvements|2013]]'''; '''[[Google Summer of Code 2014 Improvements|2014]]''';'''[[Google Summer of Code 2015 Improvements|2015]]'''

* '''Add your idea here''': Explain it here.
Idea: Better bonding to community by sending the weekly report also to the developers mailing list (if it exists).?

* '''report template form'''
Having a standardized form to fill in weekly reports would help students, mentors and admins to keep track of deadlines without jumping from link to link...

* '''final report template'''
Creating a final report template in GIT would facilitate final reporting with all important,necessary and needed informations in the right place; just fork the template, fill in, it's done and submit the url.

*'''collective chat for students'''
Creating a common chat platform for students on e.g. Slack. This would help with staying in touch with them, communication could go faster between us Admins and mentors. Moreover, students could share resources between them, experiences how they managed to overcome certain difficulties, this came of great help for GSoC newtimers. If moderated correctly with a little bit of effort this can turn into a very good thing community-wise, bonding between students, increase collaboration, reinforce the ideas of an open source community.

== Topics to be discussed at the upcoming Mentor summit ==

Google mentor summit is a great occasion to meet other organizations and gsoc admins and share good practices, clarify doubts, discuss potential problems and possible improvements. There is always room for improvement! So please, list hereinafter suggestions on topics that you wish your OSGeo delegates should bring to mentor summit for discussion.

* '''emphasize bonding period''': Community bonding period is a good chance to learn how to communicate with and how to learn from the community. it seems this chance is very little used by students. How do other orgs motivate students to be active in community bonding period.

[[Category:Google Summer of Code]]

Google Summer of Code 2017 Improvements

2017-07-29T20:00:54Z

Wiki-Masterflorin: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:OSGeo_300_127_pixel.png|300px|link=http://www..."

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==

* See also lesson learned from '''[[Google Summer of Code 2011 Improvements|2011]]'''; '''[[Google Summer of Code 2012 Improvements|2012]]'''; '''[[Google Summer of Code 2013 Improvements|2013]]'''; '''[[Google Summer of Code 2014 Improvements|2014]]''';'''[[Google Summer of Code 2015 Improvements|2015]]'''

* '''Add your idea here''': Explain it here.

[[Category:Google Summer of Code]]

Google Summer of Code Recommendations for Students

2017-03-07T19:35:19Z

Wiki-Masterflorin: /* How to get in contact with your potential mentors */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.
* Check out the [[Google_Summer_of_Code_2017_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [https://flossmanuals.net/GSoCStudentGuide/ The Student's Guide to the Summer of Code]
* If you are new to OSGeo, take the time to familiarize with the [http://www.osgeo.org/content/foundation/about.html Open Source Geospatial Foundation]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.
We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal.
Developers will then assist students in filling the proposal template (see below) and will prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successfull teamwork and interplay of project, mentors and students.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period?

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user:
* GIS programming and other software programming:

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for GSoC 2016 to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://webchat.freenode.net IRC client]) 

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* https://gitter.im/pgRouting/pgrouting
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#geonode

[[Category: Google Summer of Code]]

Google Summer of Code 2017 Administrative

2017-01-24T14:06:21Z

Wiki-Masterflorin: /* Contacts */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.

This is the central page for OSGeo administrative information in Google Summer of Code 2017.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2017 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!



[[Image:Madi_BW_1.jpg|60px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:Hk grey.png|60px|Helmut Kudrnovsky]][[Image:Jeff_McKenna.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]][[Image:Macho.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]]
[[Image:FlorinCioloboc.jpg|100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|FlorinCioloboc]]

.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|
|
|
|
|
|
|-
|2
|
|
|
|
|
|
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2017 Administrative

2017-01-24T14:05:38Z

Wiki-Masterflorin: /* Contacts */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.

This is the central page for OSGeo administrative information in Google Summer of Code 2017.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2017 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:MasterFlorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!



[[Image:Madi_BW_1.jpg|60px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:Hk grey.png|60px|Helmut Kudrnovsky]][[Image:Jeff_McKenna.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]][[Image:Macho.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]]
[[Image:FlorinCioloboc.jpg|100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|FlorinCioloboc]]

.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|
|
|
|
|
|
|-
|2
|
|
|
|
|
|
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2017 Administrative

2017-01-24T13:57:27Z

Wiki-Masterflorin: /* Contacts */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.

This is the central page for OSGeo administrative information in Google Summer of Code 2017.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2017 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes Florin-Daniel Cioloboc, [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!



[[Image:Madi_BW_1.jpg|60px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:Hk grey.png|60px|Helmut Kudrnovsky]][[Image:Jeff_McKenna.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]][[Image:Macho.jpg|60px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]]
[[Image:FlorinCioloboc.jpg|100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|FlorinCioloboc]]

.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|width=30px|'''Number'''
|width=100px|'''Name'''
|width=100px|'''Surname'''
|width=100px|'''Nickname (IRC)'''
|width=250px|'''email'''
|'''Software community'''
|'''Idea(s) you are available to mentor'''
|-
|1
|
|
|
|
|
|
|-
|2
|
|
|
|
|
|
|}

== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* ...

=== Bad ideas ===

* ...

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]

* OSGeo Applications: [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

User:Masterflorin

2017-01-24T13:54:07Z

Wiki-Masterflorin:

GSoc '16 Participant - istSOS Community

Profile:

Bachelor in Geography 
Master in Geomatics

{| class="wikitable"
|-
! Info about me !!
|-
| Name || Florin Cioloboc
|-
| Job Title ||
|-
| Address ||
|-
| City || Cluj-Napoca
|-
| Country || Romania
|}

[[File:FlorinCioloboc.jpg|thumbnail|left|Yours truly]]

User:Masterflorin

2017-01-24T13:53:28Z

Wiki-Masterflorin:

User:Masterflorin

2017-01-24T13:53:22Z

Wiki-Masterflorin:

User:Masterflorin

2017-01-24T13:51:18Z

Wiki-Masterflorin:

File:FlorinCioloboc.jpg

2017-01-24T13:50:13Z

Wiki-Masterflorin:

User:Masterflorin

2017-01-24T13:36:38Z

Wiki-Masterflorin:

Android istSOS

2016-08-23T06:49:54Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

''Mentors'': Mirko Cardoso, Milan Antonovic

Project website: https://masterflorin.github.io/gsoc16-istsos/

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Last report: 8 - 15 August ====

'''Brief description:'''

My project focused on developing an Android Client for the istSOS community.

'''The state of the project as it was BEFORE your GSoC:'''

istSOS was only available as a platform that could be self-configured, developed in Python and my goal was to extend the possibilities of using istSOS in the Java-Android direction.

'''The addition that your project brought to the software:'''

In my project, I developed a core API Wrapper that exposes the communication of the core features of istSOS in Java, therefore developers can use the core in order to customize and develop applications specifically for their needs.

Secondly, the library was adapted in order to suit the needs for Android development. This is where I developed a showcase demo-type that implements the core functionality for the app.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android demo is built so that developers can see an example of how to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-23T06:48:44Z

Wiki-Masterflorin: /* Who will use results of this project */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

''Mentors'': Mirko Cardoso, Milan Antonovic

Visit project website: https://masterflorin.github.io/gsoc16-istsos/

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Last report: 8 - 15 August ====

'''Brief description:'''

My project focused on developing an Android Client for the istSOS community.

'''The state of the project as it was BEFORE your GSoC:'''

istSOS was only available as a platform that could be self-configured, developed in Python and my goal was to extend the possibilities of using istSOS in the Java-Android direction.

'''The addition that your project brought to the software:'''

In my project, I developed a core API Wrapper that exposes the communication of the core features of istSOS in Java, therefore developers can use the core in order to customize and develop applications specifically for their needs.

Secondly, the library was adapted in order to suit the needs for Android development. This is where I developed a showcase demo-type that implements the core functionality for the app.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android demo is built so that developers can see an example of how to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-22T11:06:20Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

''Mentors'': Mirko Cardoso, Milan Antonovic

Visit project website: https://masterflorin.github.io/gsoc16-istsos/

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Last report: 8 - 15 August ====

'''Brief description:'''

My project focused on developing an Android Client for the istSOS community.

'''The state of the project as it was BEFORE your GSoC:'''

istSOS was only available as a platform that could be self-configured, developed in Python and my goal was to extend the possibilities of using istSOS in the Java-Android direction.

'''The addition that your project brought to the software:'''

In my project, I developed a core API Wrapper that exposes the communication of the core features of istSOS in Java, therefore developers can use the core in order to customize and develop applications specifically for their needs.

Secondly, the library was adapted in order to suit the needs for Android development. This is where I developed a showcase demo-type that implements the core functionality for the app.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T21:22:18Z

Wiki-Masterflorin: /* Week 12: 8 - 15 August */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

''Mentors'': Mirko Cardoso, Milan Antonovic

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Last report: 8 - 15 August ====

'''Brief description:'''

My project focused on developing an Android Client for the istSOS community.

'''The state of the project as it was BEFORE your GSoC:'''

istSOS was only available as a platform that could be self-configured, developed in Python and my goal was to extend the possibilities of using istSOS in the Java-Android direction.

'''The addition that your project brought to the software:'''

In my project, I developed a core API Wrapper that exposes the communication of the core features of istSOS in Java, therefore developers can use the core in order to customize and develop applications specifically for their needs.

Secondly, the library was adapted in order to suit the needs for Android development. This is where I developed a showcase demo-type that implements the core functionality for the app.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T21:03:24Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

''Mentors'': Mirko Cardoso, Milan Antonovic

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:57:22Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:57:12Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper.

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:56:40Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* Test and adapt the Java Core in Android context

* Develop an Android demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:56:19Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into 3 parts:

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* Test and adapt the Java Core in Android context

* Develop an Android showcase demo

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:54:23Z

Wiki-Masterflorin: /* Schedule */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==
Initial development plan for the project

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android client (20 June - 23 August)
**Design and requirements analysis
**Coding/Implementation
**Testing, bug fixing, documentation

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:48:25Z

Wiki-Masterflorin: /* Repositories */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:45:23Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

''istSOS repositories''

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

''Forks of the repositories''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:41:16Z

Wiki-Masterflorin: /* Implementation details */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

'''istSOS repositories'''

Java Core: https://github.com/istSOS/java-core

Android demo: https://github.com/istSOS/android-demo

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:39:41Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:39:17Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:IstSOS Android client.png|thumbnail|right|Android client]]
The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:38:29Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:Https://wiki.osgeo.org/wiki/File:IstSOS Android client.png|thumbnail|right|Android client]]
The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:35:48Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:https://wiki.osgeo.org/images/f/fc/IstSOS_Android_client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:34:47Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

[[File:Https://wiki.osgeo.org/wiki/File:IstSOS Android client.png|thumbnail|right|Android client]]

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-14T20:33:49Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

<gallery>
https://wiki.osgeo.org/wiki/File:IstSOS_Android_client.png|Android istSOS client
</gallery>

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

File:IstSOS Android client.png

2016-08-14T20:32:05Z

Wiki-Masterflorin:

Android istSOS

2016-08-08T11:58:54Z

Wiki-Masterflorin: /* Weekly reports */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

====Week 12: 8 - 15 August ====

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Android istSOS

2016-08-08T11:57:35Z

Wiki-Masterflorin: /* Introduction */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

The end goal of the project is to develop an Android-based library for the istSOS project. In order to achieve that objective, a main goal will be to develop an easy-to-use library in Java based on the istSOS, suitable for Android development.

This way, developers can create and customize their own apps depending on the needs of their projects. As it is essential for users to access in real time current and historic sensor data the application will show sensors location, metadata, observed properties, data visualization trough plots and infographics, alerts and notifications, features provided by the application's main core functionality.

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]

Google Summer of Code 2016 Accepted

2016-08-08T11:53:59Z

Wiki-Masterflorin: /* Accepted Proposals */

<center>
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.

== Accepted Proposals ==

This year OSGeo accepted 22 students working on the following projects.

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|'''Community'''
|'''Project'''
|'''Student'''
|'''1st mentor'''
|'''2nd mentor'''
|'''Wiki page'''
|'''Repository'''
|-
|GDAL
|Introduce Triangulated Surface, Polyhedral Surface and Triangle API in the OGRGeometry core and implement their support in OGR drivers for GDAL
|Avyav Kumar Singh
|Rob Emanuele
|Even Rouault
|[https://github.com/avyavkumar/gdal/wiki Github]
|[https://github.com/avyavkumar/gdal Github]
|-
|GDAL
|GDAL DWG support
|Alexandr Borzykh
|Dmitry Baryshnikov
|Even Rouault
|[https://wiki.osgeo.org/wiki/GDALDWG_SoC_2016 Wiki]
|[https://github.com/sandyre/libopencad Github]
|-
|GRASS GIS
|Complete basic cartography suite in GRASS GIS wxGUI Map Display
|Adam Laža
|Anna Petrasova
|Vaclav Petras
|[https://trac.osgeo.org/grass/wiki/GSoC/2016/BasicCartographySuiteInGRASS Trac]
|[https://github.com/lazaa32/SoC16 GitHub]
|-
|GRASS GIS
|GRASS GIS - Additional segmentation algorithms for i.segment
|Bo Yang
|Moritz Lennert
|Markus Neteler
|[https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms Trac]
|[https://trac.osgeo.org/grass/browser/sandbox/bo/i.segment.gsoc2016 Sandbox]
|-
|GRASS GIS
|GRASS GIS - PyQt implementation of GUI forms generated automatically from XML
|Ondřej Pešek
|Vaclav Petras
|Anna Petrasova
|[https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI Trac]
|
|-
|GRASS GIS
|GRASS GIS - WEBGRASS
|Mayank Agrawal
|Rashad Kanavath
|Massimo Di Stefano
|[https://github.com/mayank33/webgrass/wiki Wiki]
|
|-
|gvSIG
|Add tests and educational games support to gvSIG Educa.
|Carlos I. Colombana
|Óscar Martínez
|Joaquín del Cerro
|[https://wiki.osgeo.org/wiki/GvSIG-Educational-Games_GSoC_2016#Project Wiki]
|[https://github.com/nacho0605/GSoC/tree/master/GSoC_2016 GitHub]
|
|-
|gvSIG
|Development of a model for woody debris flooding hazard in gvSIG
|Silvia Franceschi
|Andrea Antonello
|Riccardo Rigon
|[https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2016 github]
|[https://github.com/silviafranceschi/jgrasstools github]
|
|-
|istSOS
|Android istSOS client
|Florin-Daniel Cioloboc
|Mirko Cardoso
|Milan Antonovic
|[https://wiki.osgeo.org/wiki/Android_istSOS Wiki]
|[https://github.com/istSOS/java-core Github-Core] [https://github.com/masterflorin/java-core Fork]
[https://github.com/istSOS/android-demo Github-Android] [https://github.com/masterflorin/android-demo Fork]
|-
|istSOS
|istSOS Web API
|Luka Glušica
|Massimiliano Cannata
|Milan Antonovic
|[https://wiki.osgeo.org/wiki/IstSOS_Web_API Wiki]
|[https://github.com/istSOS/javascript-core GitHub] [https://github.com/WebPractice-LukaG/javascript-core Fork]
|-
|istSOS
|VistSOS: the istSOS Data Visualization Framework
|Felipe Poveda
|Milan Antonovic
|Massimiliano Cannata
|[https://wiki.osgeo.org/wiki/VistSOS_Data_Visualization_Framework Wiki]
|[https://github.com/felipe07/vistsos GitHub]
|-
|NASA World Wind
|NASA Web World Wind - Multidimensional Visualization Tool for Environmental Variables
|Gabriele Prestifilippo
|Jakub Balhar
|Patrick Hogan
|[[NASA Web WorldWind Multidimension Visualization Tool GSoC 2016|Wiki]]
|[https://github.com/GabrielePrestifilippo/EST-WA-Javascript GitHub]
|-
|OpenLayers3 - Google maps
|OGC protocols support within OL3-Google-Maps
|Samuel Lapointe
|Alexandre Dube
|Jessica Lapointe
|[[OL3-GoogleMaps_GSoC_2016|Wiki]]
|[https://github.com/mapgears/ol3-google-maps GitHub] [https://github.com/samuellapointe/ol3-google-maps Fork]
|-
|OneBusAway/Transitime
|Tansitime Quickstart application
|Brendan Egan
|Og Crudden
|Stefan Steiner
|[https://github.com/Egan109/core/wiki/Transitime-QuickStart-Gsoc-2016 Wiki]
|[https://github.com/Egan109/core Github]
|-
|OSSIM
|A complete photogrammetric OSSIM tool for automatic DSMs generation using multi-view optical and SAR images
|Martina Di Rita
|Oscar Kramer
|Dave Burken
|[https://trac.osgeo.org/ossim/wiki/GSoC_2016 Wiki]
|
|-
|pgRouting
|Flow Algorithms for pgRouting
|Andrea Nardelli
|Daniel Kastl
|Vicky Vergara
|[https://github.com/Illedran/pgrouting/wiki/GSoC-2016-Flow Github Wiki]
|
|-
|pgRouting
|Implementation of a framework which supports addition of contraction techniques for pgRouting
|Sankepally Rohith Reddy
|Vicky Vergara
|Daniel Kastl
|[https://github.com/sankepallyrohithreddy/pgrouting/wiki/GSoc-2016-Contraction Github Wiki]
|
|-
|PyWPS
|Remote Output Storage for PyWPS
|Vikas Mishra
|Jachym Cepicky
|Jonas Eberle
|[https://wiki.osgeo.org/wiki/User:Vikasmishra95 Wiki]
|[https://github.com/mishravikas/pywps Github]
|-
|PyWPS
|Web-based administration & process management for PyWPS
|Jan Rudolf
|Jonas Eberle
|Jachym Cepicky
|[https://wiki.osgeo.org/wiki/GSoC_2016_Web_administration_and_process_management_for_PyWPS Wiki]
|[https://github.com/jan-rudolf/pywps Forked PyWPS] [https://github.com/jan-rudolf/gsoc-python-process-control Support app 1] [https://github.com/jan-rudolf/gsoc-pywps-app Support app 2]
|-
|QGIS
|QGIS Styles, Symbols, and SVG Markers Sharing Repository
|Akbar Gumbira
|Alessandro Pasotti
|Anita Graser
|[[QGIS Sharing Repository|Wiki]]
|
|-
|ZOO-Project
|Bringing pyModis to the web through ZOO-Project
|Chingchai Humhong
|Luca Delucchi
|Gerald Fenoy
|[http://zoo-project.org/trac/wiki/Bringing_pyModis_to_the_web_through_ZOO-Project_GSoC_2016 Wiki]
|[https://github.com/chingchai/pyModis/tree/gsoc-2016/zoo-pymodis/ Github]
|-
|ZOO-Project
|Implementing WPS for Geopaparazzi field data collection tool using ZOO-Project: Simplifying integration of field data and GIS
|Niroshan Sanjaya
|Gerald Fenoy
|Andrea Antonello
|[http://zoo-project.org/trac/wiki/IMPLEMENTING_WPS_FOR_GEOPAPARAZZI_FIELD_DATA_COLLECTION_TOOL_USING_ZOO-PROJECT%3ASIMPLIFYING_INTEGRATION_OF_FIELD_DATA_AND_GIS Wiki]
|[https://github.com/niroshansb/GSoC2016 Github]
|-
|}

See the [https://summerofcode.withgoogle.com/organizations/6273632556810240/ accepted projects on Google's platform].

[[Category: Google Summer of Code]]

Android istSOS

2016-08-08T11:47:30Z

Wiki-Masterflorin: /* Week 11: 1 - 7 August */

{| {{Prettytable}}
| This is where I'll be posting information about the Android istSOS client GSoC 2016 project to the OSGeo community.
|}

==Introduction==

==Implementation details==

The android istSOS client project is divided into two reusable library and a reference implementation application.

* istSOS Java Core Library which is mainly an REST API wrapper. It will expose in Java language the communication with the istSOS WA REST interface.

* istSOS Android Tools, a graphical library used to show istSOS metadata and observations in Android.

* istSOS admin for android, a graphical library used to show istSOS data observations in Android.

==Schedule==

*Community bonding (23 April - 23 May)
**Read istSOS documentation
**Set up work environment (Linux, istSOS, IDE, Android Studio etc.)
**Read documentation on Android and get the basics
**Be active on the mailing list

*istSOS Java Core (23 May - 18 June)
**Requirements Analysis
**Development of core architecture
**Coding/Implementation

*istSOS Android Tools (20 June - 23 July)
**Design and requirements analysis
**Coding/Implementation

*istSOS Admin for Android (25 July - 23 August)
**Design and requirements analysis
**Coding prototype
**Testing, more coding, bug fixing

==Weekly reports==

==== Week 1: 23 - 29 May ====

'''What did you get done this week?'''

This week, I had the task to work together with fellow GSoC student Luka Glusica to identify all the HTTP requests for the istSOS REST API.
I've also read some documentation related to event handling during REST requests.

'''What do you plan on doing next week?'''

To finish the architecture of the Java core library, and start the development.

'''Are you blocked on anything?'''

No, not at the moment.

==== Week 2: 30 May - 5 June ====

'''What did you get done this week?'''

Worked on the architecture of the core diagram. It took a bit more time than initially expected but in the end it all got sorted out, enough for starting to code and test.

'''What do you plan on doing next week?'''
Try to implement most functionalities for the proposed classes. I should have a pretty decent amount of implementation by the end of this week.

Update the personal GSoC wiki page on OSGeo wiki.

'''Are you blocked on anything?'''

Not really, the diagrams part went a bit too slow. I started to code a little late but I'll catch up some speed soon.

==== Week 3: 6 - 12 June ====

'''What did you get done this week?'''

I've been focusing on getting the istSOS, Server and Database classes to work, in order to handle requests to istSOS as part of the Java Core e.g. create, delete services on server, connect and validate connection to database among many other.

I've also took more time to update my OSGeo wiki page with links to the github repos, as well as more information about what my project is. At the same time, I'll include my weekly reports on that page.

'''What do you plan on doing next week?'''
Tweaking the work so far, as well as focusing on implementing features related to services, procedures. I also plan to improve the way it handles configuration settings.

'''Are you blocked on anything?'''

I was a couple of days ago but with guidance from my mentor I've managed to overcome that obstacle.

==== Week 4: 13 - 19 June ====

'''What did you get done this week?'''

Unfortunately, as I had to focus on finishing my master thesis, I did little work this week, thus I've only managed to create additional methods in Service class for GET requests, updated several classes and made some slight improvements.

'''What do you plan on doing next week?'''

On the recommendation of my mentors, I should prepare the worked done so far for some more thorough testing.

Apart from that, continue on implementing the classes and methods as planned.

'''Are you blocked on anything?'''

Not really, just fell a bit behind than expected.

==== Week 5: 20 - 26 June ====

'''What did you get done this week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''What do you plan on doing next week?'''

After a meeting with my mentors, they suggested me to make use of AsyncHttpClient and Gson libraries from now on in the project as well as converting the project to Gradle in order to handle dependencies. Therefore I started reorganizing my work which is quite helpful in the long run. Already ran some basic tests with it.

'''Are you blocked on anything?'''

Not at the moment.

==== Week 6: 27 June - 3 July ====

'''What did you get done this week?'''

I tested and fixed some of the methods and adjusted the classes, as well as implementing some of the functionality I didn't manage to do last week.

This week I had to take a few days in order to prepare and support the oral defense for my master thesis.

'''What do you plan on doing next week?'''

Implement the remaining functionalities, then create a basic documentation (I plan to do it in the GitHub Wiki) on how to use the Java Core library.

During the next week I will also start planning for development the Android Tools library.

'''Are you blocked on anything?'''

Not at the moment.

====Week 7: 4 - 10 July ====

'''What did you get done this week?'''

At the suggestion of my mentors, I've started reimplementing some functions following a new pattern, therefore I had to really dig deep this week got get it done. This new implementation style is a lot more compatible for the Android part of the project, there it was necessary. The good news, I'm pretty close now to finishing the JavaCore part.

'''What do you plan on doing next week'''

Done some tests, properly document the library and try to go to the next stage.

'''Are you blocked on anything?'''

Unfortunately, I haven't transitioned to the Android part yet. I wouldn't consider this a block or a setback, as it definitively helped me improve the library and avoiding future problems.

====Week 8: 11 - 17 July ====

'''What did you get done this week?'''

Wrapped up the Java Core by implementing the remaining methods. As a result, the class structure has been reconfigured compared to previous plans, therefore some features were removed as they were not deemed necessary, while others got some improvements. This helped maintain a cleaner structure.

I've managed to write some tests, write a proper README, opened up a wiki for showing examples how to use the Java core.

'''What do you plan on doing next week?'''

I'll have a discussion with my mentors and see how to proceed to the next phase. Other than that, I'll add more documentation, improve the wiki, bug fixing if necessary.

Investigate how to adapt the library for Android part.

'''Are you blocked on anything?'''

Not at the moment.

====Week 9: 18 - 24 July ====

'''What did you get done this week?'''

Had a discussion with the mentors for the Android phase. The first step was to compile the library and integrate it into Android project in order to test it.

My fault was that this week I was traveling for a couple of days, didn't manage my time properly, while also having only some temporary internet led to not accomplishing this week as much as I could have.

'''What do you plan on doing next week?'''

Continue testing the library functionalities in Android context such as executing the requests for observation data, inserting observation.

'''Are you blocked on anything?'''

Not at the moment, I know what I have to do.

====Week 10: 25 - 31 July ====

'''What did you get done this week?'''

At the suggestion of my mentors I started to make a tutorial/showcase of
how to use the Java-Core. Besides, this helped me re-evaluate what I've done so far and actually fixed some minor bugs.

Recompiled the Java core and integrated into Android project where I began to make a test run of how the library works. I had a couple of issues with integrating the Java Core to Android as it was developed on Java 8, it took some time to figure a solution on how to overcome the incompatibilities but with the guidance of my mentors I managed to do it.

'''What do you plan on doing next week?'''

After I finish with fixing the APK building I'll continue with Android development using the library then make a user guide/tutorial on how to use it.

'''Are you blocked on anything?'''

Unfortunately, I'm having issue with building the APK as I'm getting an erro of DuplicateFilesException. Tried a couple of methods but nothing worked out so far.

====Week 11: 1 - 7 August ====

'''What did you get done this week?'''

Previously, I had the problem with the Java Core being in the Android. Fortunately, this problem was solved this week with the help of my mentor. The difficulty lied in the fact that AsyncHTTPClient is not supported in Android, a library I used for handling async tasks. As a result, the core as adapted to make use of another library.

This allowed me to return to the Android part and develop further. I made a design of the app prototype, then I implemented some of the core functionalities.

'''What do you plan on doing next week?'''

Finish implementing the core features into the app, test it, document it, make a tutorial on how to develop in Android using the library.

'''Are you blocked on anything?'''

Everything is fine.

==Who will use results of this project==

* Main goal is to develop an easy-to-use library for developers
* Java Core is to be an independent library, as in being able to be implemented in other projects
* Android Tools and Admin Library are built so that developers are able to build and customize their own applications depending on their needs

==Repositories==

If you want to check how the project is going, code-wise, below I'll give you the links on where to go:

'''Main istSOS repository''' (here is where everything will end up)

Java Core: https://github.com/istSOS/java-core

Android: https://github.com/istSOS/android-demo

'''Personal forks of the repositories'''

Java Core: https://github.com/masterflorin/java-core

Android: https://github.com/masterflorin/android-demo

==Student's biography==

My name is Florin Cioloboc. Currently, I'm a MSc Geomatics student at Babes-Bolyai University in Cluj-Napoca, Romania.

Programming/GIS/Technical skills
* Java, Python, little bit of C++, and R, familiar with HTML & CSS
* I use Eclipse, Sublime Text, Anaconda, Canopy,
* Comfortable working on both Windows and Linux
* Open Source GIS: QGIS, GeoServer, PostgreSQL, PostGIS
* Familiar with Git and GitHub, Vagrant, VirtualBox
* Currently learning Android (docs, specs, Android Studio, GenyMotion etc.)

[[Category:Google Summer of Code]]