Google Summer of Code 2015 Results

 @

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


 * GDAL - Faza Mahamood: Integration of GDAL utilities into GDAL core library


 * GRASS GIS - Matej Krejci: Improved Metadata for GRASS GIS


 * gvSIG - Eva Rodríguez: Port Network Analysis Extension to gvSIG 2.x branch


 * istSOS - Luca Ambrosini: Scalability for Big data processing for istSOS


 * JGRASSTOOLS - Silvia Franceschi: Development of a simple 1D hydraulic model for JGRASSTOOLS


 * MapServer: Samuel Lapointe: Add productivity tools to MapServer's ScribeUI


 * Opticks - Tom Van den Eynde: Image Enhancement/Background Suppression for Opticks


 * OTP - Nipuna Gunathilake: GTFS-Realtime validation tool for Open Trip Planner


 * OSGeo-Live - Massimo Di Stefano: Integration of geospatial OSS in educational notebooks


 * OSSIM - Martina Di Rita: OSSIM tool for DSM generation using tri-stereo and SAR imagery


 * pgRouting: Sarthak Agarwal: New osm2pgrouting import tool to import OpenStreetMap (OSM) data in pgRouting


 * PyWPS - Calin Ciociu: REST interface for PyWPS 4


 * QGIS - Marcus Santos: QGIS - Multithread support on QGIS Processing toolbox

Example: software XYZ - title of my GSoC project
Student1
 * Mentors: Mentor1; Mentor2; OtherMentors?
 * Brief description of the idea. e.g. "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 following instructions here".
 * 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.

ScribeUI - 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/