OSGeo - User contributions [en]

Google Summer of Code 2016 Accepted

2016-08-17T10:55:39Z

Wiki-Martidi: /* 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]
|[https://github.com/martidi/opencv_dsm/tree/imageStack GitHub]
|-
|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]]

Google Summer of Code 2016 Accepted

2016-08-17T10:54:42Z

Wiki-Martidi: /* 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]
|[https://github.com/martidi/opencv_dsm/tree/imageStack]
|-
|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]]

Google Summer of Code 2016 Accepted

2016-05-03T10:53:33Z

Wiki-Martidi: /* 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'''
|'''Links'''
|-
|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]
|-
|GDAL
|GDAL DWG support
|Alexandr Borzykh
|Dmitry Baryshnikov
|Even Rouault
|[https://github.com/sandyre/libopencad Github]
[https://wiki.osgeo.org/wiki/GDALDWG_SoC_2016 Wiki]
|-
|GRASS GIS
|Complete basic cartography suite in GRASS GIS wxGUI Map Display
|Adam Laža
|Anna Petrasova
|Vaclav Petras
|...
|-
|GRASS GIS
|GRASS GIS - Additional segmentation algorithms for i.segment
|Bo Yang
|Moritz Lennert
|Markus Neteler
|[https://wiki.osgeo.org/wiki/User_talk:Hao2309 Wiki]
|-
|GRASS GIS
|GRASS GIS - PyQt implementation of GUI forms generated automatically from XML
|Ondřej Pešek
|Vaclav Petras
|Anna Petrasova
|...
|-
|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
|Oscar Martinez
|Joaquin del Cerro
|[[GvSIG-Educational-Games_GSoC_2016|Wiki]]
|-
|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]
|-
|istSOS
|Android istSOS client
|Cioloboc FlorinDaniel
|Mirko Cardoso
|Milan Antonovic
|...
|-
|istSOS
|istSOS Web API
|Luka Glušica
|Massimiliano Cannata
|Milan Antonovic
|[https://wiki.osgeo.org/wiki/IstSOS_Web_API Wiki]
|-
|istSOS
|VistSOS: the istSOS Data Visualization Framework
|Felipe Poveda
|Milan Antonovic
|Massimiliano Cannata
|...
|-
|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]]
|-
|OpenLayers3 - Google maps
|OGC protocols support within OL3-Google-Maps
|Samuel Lapointe
|Alexandre Dube
|Jessica Lapointe
| [[OL3-GoogleMaps_GSoC_2016|Wiki]]
|-
|One bus Away
|One bus Away Quick start
|Brendan Egan
|Og Crudden
|Stefan Steiner
|...
|-
|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]
|-
|PyWPS
|Web-based administration & process management for PyWPS
|Jan Rudolf
|Jonas Eberle
|Jachym Cepicky
|...
|-
|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]
|-
|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]
|-
|}

See the [https://summerofcode.withgoogle.com/organizations/6273632556810240/ accepted projects on Google's platform].

[[Category: Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T14:59:32Z

Wiki-Martidi: /* OSSIM - Tool for DSM generation using tri-stereo optical imagery */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a picture of me @ https://www.dropbox.com/s/59dfmpz8kwapmsf/2015-12-03%2015.54.15.jpg?dl=0)
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T12:46:52Z

Wiki-Martidi: /* OSSIM - Tool for DSM generation using tri-stereo optical imagery */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (You can find a picture of me @ https://www.dropbox.com/s/ibar4jtl03hxcmo/IMG_4873_k.jpg?dl=0)
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T12:44:17Z

Wiki-Martidi: /* OSSIM - Tool for DSM generation using tri-stereo optical imagery */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (https://www.dropbox.com/s/ibar4jtl03hxcmo/IMG_4873_k.jpg?dl=0)
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* GSoC Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code in https://github.com/martidi/opencv_dsm/tree/master following the instructions in README.md file

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T10:36:34Z

Wiki-Martidi: /* Description of the projects */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (https://www.dropbox.com/s/ibar4jtl03hxcmo/IMG_4873_k.jpg?dl=0)
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* Proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176
* Weekly reports: https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery
* Please test my code (https://github.com/martidi/opencv_dsm/tree/master) following instructions in README.md

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T10:28:11Z

Wiki-Martidi: /* Description of the projects */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (https://www.dropbox.com/s/ibar4jtl03hxcmo/IMG_4873_k.jpg?dl=0)
* '''Mentors:''' Oscar Kramer, David Burken
* '''Brief description of the idea:''' the work has been based on a previous GSoC project through which a tool, named DATE, for Digital Surface Model (DSM) generation from optical stereo-pair was developed within OSSIM framework. The idea was to improve and update DATE in order to generate DSMs from tri-stereo optical imagery and fix some bugs in the DSMs generation processing chain. DATE key features include the use of computer vision algorithms in order to improve the processing efficiency and make the DSMs generation process fully automatic.
* '''The state of the project as it was BEFORE this GSoC:''' before this GSoC it was not possible to process tri-stereo imagery and there was still some problem in finding the right quasi-epipolar geometry in the stereo version in order to compute a proper Disparity Map.
* '''Addition to the software:''' with DATE plug-in it is now possible to generate DSMs within OSSIM framework starting from stereo and tri-stereo satellite optical imagery. Furthermore, from the stereo processing side, I added an image preprocess filtering and I found a better solution for the quasi-epipolar geometry achievement.
'''Relevant links:'''
* Proposal: [[proposal|https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/martidi/5717271485874176]]
* Weekly reports: [[reports|https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery]]
* Please test my code ([[code|https://github.com/martidi/opencv_dsm/tree/master]]) following instructions in README.md

* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]

Google Summer of Code 2015 Results

2015-12-03T09:39:40Z

Wiki-Martidi: /* Description of the projects */

<center>
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
</center>

OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful:

* GDAL - Faza Mahamood: [https://github.com/fazam/gdal/tree/gdalinfo Integration of GDAL utilities into GDAL core library]

* GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]

* gvSIG - Eva Rodríguez: [https://redmine.gvsig.net/redmine/projects/gvsig-networkanalysis/wiki Port Network Analysis Extension to gvSIG 2.x branch]

* istSOS - Luca Ambrosini: [http://sourceforge.net/p/istsos/wiki/GSoC_2015_scalability/ Scalability for Big data processing for istSOS]

* JGRASSTOOLS - Silvia Franceschi: [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015 Development of a simple 1D hydraulic model for JGRASSTOOLS]

* MapServer: Samuel Lapointe: [https://github.com/mapgears/scribeui/wiki/Google-Summer-of-Code-2015 Add productivity tools to MapServer's ScribeUI]

* Opticks - Tom Van den Eynde: [http://drizzle-for-opticks-gsoc2015.blogspot.be/ Image Enhancement/Background Suppression for Opticks]

* OTP - Nipuna Gunathilake: [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki GTFS-Realtime validation tool for Open Trip Planner]

* OSGeo-Live - Massimo Di Stefano: [https://github.com/epifanio/IPython_notebooks/blob/master/OSGeo-live/osgeolive-gsoc-2015/Report/Weekly%20report%2013.ipynb Integration of geospatial OSS in educational notebooks]

* OSSIM - Martina Di Rita: [https://trac.osgeo.org/ossim/wiki/OSSIMtoolForDSMgenerationFromTristereoAndSARimagery OSSIM tool for DSM generation using tri-stereo and SAR imagery]

* pgRouting: Sarthak Agarwal: [https://github.com/pgRouting/pgrouting/wiki/GSoC-2015-Sarthak-Agarwal New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting]

* PyWPS - Calin Ciociu: [https://github.com/jachym/pywps-4/wiki/GSoC-2015 REST interface for PyWPS 4]

* QGIS - Marcus Santos: [https://qgisgsoc2015.wordpress.com/ QGIS - Multithread support on QGIS Processing toolbox]

== Description of the projects ==

=== Example: software XYZ - title of my GSoC project ===
Student1 (picture)
* Mentors: Mentor1; Mentor2; OtherMentors?
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

=== GDAL - Integration of GDAL utilities into GDAL core library ===
Faza Mahamood (Picture: https://drive.google.com/file/d/0B9gY4JeBmoKVZ2REcjcwVnl1Nk0/view?usp=sharing)
* Mentor: Even Rouault
* There is a need for calling GDAL utilities from code without involving system calls, to be able to work on in-memory datasets and use progress/cancellation callback functions.
* Before, inorder to use any functionalities of GDAL utilities in a program, the developer had to use system calls. Even then, the developer cannot work with in memory datasets.
* Now, the developers can easily have all the functionalities of GDAL utilities through dedicated functions which are part of GDAL core library. There is no system call involved and it works on in-memory datasets.
* Project: https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library

=== GRASS GIS - Improved Metadata for GRASS GIS ===
Matej Krejci (picture: http://tinyurl.com/pp69bwd)
* Mentors: Martin Landa, Angelos Tzotsos, Luca Delucchi
* Description: The first aim was to improve current package by adding a new functionality for extend metadata handling. The second goal was to implement module for interaction with metadata catalogue services (CSW).
* State of the project before GSoC: In 2014 during GSoC I have developed new GRASS GIS metadata management support based on ISO-INSPIRE. This package needed extension to meet the users requirements. In addition package for CSW searching was missing.
* Addition to the project: New module g.gui.cswbrowser based on graphical interface allows managing csw connections, setting filter and searching, browsing results and adding services to GRASS GIS have been implemented. For g.gui.metadata have been added support: exporting metadata reports to pdf, storing themes of metadata in SQL backend, publishing metadata to CSW and metadata support for Temporal datasets.
* Slide: https://grasswiki.osgeo.org/w/images/Find1.png

Links:
* Project: https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
* Development page 2015: https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
* source SVN: http://svn.osgeo.org/grass/grass-addons/grass7/gui/wxpython/wx.metadata/

=== JGrassTools - Development of a simplified 1D hydraulics model ===
Silvia Franceschi (picture: https://sites.google.com/a/hydrologis.com/home/_/rsrc/1348641375730/silviafranceschi/silli.jpg?height=320&width=234)
* Mentors: Andrea Antonello, Riccardo Rigon
* Description: The module developed during this GSoC2015 is SaintGeo, a simple 1D hydraulic model based on the equations of Saint Venant.
* State of the project before GSoC: There was an original implementation of the model in C language done during a master thesis by Angelo Zacchia and Riccardo Rigon. I did the porting in the JGrassTools library of the model together with the implementation of the code for reading and writing GIS layers as input and outputs.
* Addition to the project: The new model bases on GIS input layers instead of text files and has a graphical interface, directly provided by the integration in the JGrassTools library to specify the inputs and outputs files.
* Slide: https://github.com/moovida/jgrasstools/wiki/gsoqc2015imgs/a_profile_qin_monte_laterali_in_out10.png

Links:
* Project: http://www.jgrasstools.org
* Development page 2015: https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-2015
* Source: https://github.com/moovida/jgrasstools/tree/master/hortonmachine/src/main/java/org/jgrasstools/hortonmachine/modules/hydrogeomorphology/saintgeo

=== Mapserver - Add productivity tools to MapServer's ScribeUI ===
Samuel Lapointe (picture: https://goo.gl/photos/LbSwPeMrCG5V2K9t8)
* Mentors: Daniel Morissette; Jessica Lapointe
* Description: The goal of the project was to improve the error detection system, add the ability to export and import maps and add a way to generate a set of classes from data.
* State of the project before GSoC: When I wanted to debug a map that didn’t work, I had to check the generated Mapserver file to find the error. To create classes from a set of data, I had to analyse the data and create the classes using bounds I had manually calculated, and the only way to export a map was to use Git.
* Addition to the project: Now, I can see most syntax errors directly in the editor’s interface, I can use a menu to generate classes for a layer and I can export or import maps to share them with other users.
* Slide: https://drive.google.com/file/d/0B686XfUqwP1LMm5GaVV0ckZ1b2c/view?usp=sharing

Links:
* Project page: https://github.com/mapgears/scribeui
* Getting started: https://github.com/mapgears/scribeui/wiki/Getting-started-with-ScribeUI
* Demo: http://demo.scribeui.org/

=== Opticks – Image Enhancement/Background Suppression ===
Tom Van den Eynde (picture: https://goo.gl/photos/DKwS7Fq4ZWEmHfR46)
* Mentors: Trevor Clarke
* Brief description of the idea: The goal of the project was to implement the image enhancement algorithm Drizzle for both image and video input.
* The state of the project as it was before GSoC: In Opticks, when I wanted to use a low resolution image I had to resort to other software to first improve the quality or reduce the noise interference.
* The addition to the software: With the addition of the Drizzle algorithm, Opticks can enhance and improve the interpretability of images. Now, even low resolution or heavily noise polluted images can be used for various remote sensing applications.
* Slide: https://goo.gl/photos/szt3RW3X93v2ccZi9

Links:
* Project: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/tomvde/5733935958982656
* Blog: http://drizzle-for-opticks-gsoc2015.blogspot.be/
* Repository: https://github.com/Tom-VdE/Drizzle-plugin
* Instructions: https://github.com/Tom-VdE/Drizzle-plugin/blob/master/README.md

=== PyWPS-4 – REST Interface ===
Calin Cristian Nicolae Ciociu (picture: http://i.imgur.com/WglCPnz.jpg)
* Mentors: Jachym Cepicky, Luís de Sousa
* Brief description of the idea: My project added the ability to use a REST interface to control, add, remove processes and change configuration of PyWPS-4 instances.
* The state of the project as it was before GSoC: We had to create/delete the processes by accessing the storage of the server which required a restart of the server every time something got changed.
* The addition to the software: With the addition of the REST interface I wrote everyone who needs to update, delete, or add new processes and change configuration can do so without accessing the server.
* Slide: http://i.imgur.com/oYAHsgQ.png

Links:
* Project: http://www.google-melange.com/gsoc/project/details/google/gsoc2015/noctalin/5717271485874176
* Repository: https://github.com/jachym/pywps-4
* Instructions: https://github.com/PyWPS/pywps-4-demo/blob/master/README.rst

=== QGIS - Multithread Support on Processing Toolboxt ===
Marcus Santos (https://media.licdn.com/media/AAEAAQAAAAAAAATOAAAAJDA1Y2M0MWQ0LTMyYjMtNDlhMi05OWM3LWIxMDQ5YWM1ZTk2MA.jpg)
* Mentors: Victor Olaya, Alexander Bruy
* Description: This project consisted on making the QGIS Processing toolbox multi-threaded, allowing to have non blocking analysis/geoprocessing jobs, prevent crashes (when a QGIS module crashes for some reason) and also improve the user experience.
* The state of the project GSoC: Before the multithreading support, the user was only able to run one analysis at a time and there was no option to cancel the algorithm execution.
* The addition to the project: With multithreading support the user is allowed to cancel long geoprocessing jobs and also run several algorithms at the same time.
* Slide: https://www.dropbox.com/s/fmaxf97jkmf2cy1/slide.png?dl=0

Links:
* Project page: https://qgisgsoc2015.wordpress.com
* Repository: https://github.com/mvcsantos/QGIS
* Demo: https://www.youtube.com/watch?v=V-CJCnKw89U

=== OSSIM - Tool for DSM generation using tri-stereo optical imagery ===
Martina Di Rita (https://www.dropbox.com/s/ibar4jtl03hxcmo/IMG_4873_k.jpg?dl=0)
* Mentors: Oscar Kramer, David Burken
* Brief description of the idea. e.g. "[[link|My project]] focused on xxx".
* The state of the project as it was BEFORE your GSoC. For example, if you made a GUI, you can say: "In the software XYZ, when I wanted to use the tool xxx, I had to manually edit the file yyy. "
* The addition that your project brought to the software. In the same example: "With the GUI that I created, now it is possible to use the tool xxx via graphical user interface".
* Add all the links (hopefully permanent) to access the relevant code and documentation for the user to get started with testing your application. "Please test my [[code-repository|code]] following instructions [[some-link|here]]".
* [[Link_to_image|Slide]] The slide / image should serve to show the main elements of your project. It could be a flow chart, a screenshot, both, or whatever you think could serve for the scope. Remember: the aim is to showcase your project to people that are not necessarily familiar with the software.

[[Category:Google Summer of Code]]