OSGeo - User contributions [en]

2008 Google SoC Application

2008-03-19T18:28:45Z

Wiki-Tkeitt:

'''This application has been sent'''

'''Don't bother to edit it any further'''

--[[User:Wolf|Wolf]] 18:11, 11 March 2008 (EDT)

==What is your Organization's Name?==
OSGeo - Open Source Geospatial Foundation

==What is your Organization's Homepage?==
http://www.osgeo.org/

==Describe your organization.==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 14 projects in particular.

==Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?==
We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects. Additionally we hope to spread the word of open source GIS in the universities.

==Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)==

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report.

OSGeo was formed in early 2006 and hadn't participated in GSoC before 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators are involved in this years OSGeo GSoC effort.

==If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)==

==What license does your project use?==
Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

==URL for your ideas page==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code

==What is the main development mailing list for your organization?==

OSGeo Wide - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)

'''Project lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geoserver-devel )
* GeoTools - geotools-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geotools-devel )
* uDig - udig-devel@lists.refractions.net ( http://lists.refractions.net/mailman/listinfo/udig-devel )
* MapGuide - mapguide-internals@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapguide-internals )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel )
* MapServer - mapserver-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapserver-dev )
* GDAL - gdal-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/gdal-dev )
* PostGIS - postgis-users@postgis.refractions.net ( http://postgis.refractions.net/mailman/listinfo/postgis-users )
* GRASS - grass-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/grass-dev )
* Mapbender - mapbender_dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapbender_dev )

==Where is the main IRC channel for your organization?==
irc://irc.freenode.net/#osgeo

'''Project irc channels:'''
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#udig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#mapbender

==Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)==

==Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)==
Frank Warmerdam (2007 administrator) - fwarmerdam at gmail.com

==About Your Mentors==
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
Mentors are selected by project steering comittees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.

===Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)===
* fwarmerdam []gmail.com (Frank Warmerdam) - GDAL, MapServer
* wolf[]bergenheim.net (Wolf Bergenheim) - GRASS
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
* euzuro []gmail.com (Erik Uzureau) - OpenLayers
* tim.schaub []gmail.com (Tim Schaub) - OpenLayers
* eric.c2c []gmail.com (Eric Lemoine) - OpenLayers
* bluecarto []gmail.com (Pierre Giraud) - OpenLayers
* shermange []gmail.com (Gary Sherman) - QGIS
* ottens []gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
* cameron.shorter []gmail.com (Cameron Shorter) - Mapbuilder, OpenLayers
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
* hobu.inc []gmail.com (Howard Butler) - MapServer, GDAL
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
* mloskot [] gmail.com (Mateusz Loskot) - GDAL
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
* woodbri []swoodbridge.com (Stephen Woodbridge) - MapServer
* astrid_emde []osgeo.org - Mapbender
* marko.samson []gmail.com - Mapbender
* christoph.baudson []wheregroup.com - Mapbender
* uli []osgeo.org - Mapbender
* lars.beck []wheregroup.com Mapbender
* vera.schulze []wheregroup.com Mapbender
* arkepp []gmail.com (Arne Kepp)- GeoServer / GeoTools / GeoWebcache
* andrea.aime []gmail.com (Andrea Aime) - GeoServer / GeoTools
* cdwinslow []gmail.com - (David Winslow) GeoServer / GeoTools
* sbenthall []gmail.com - (Seb Benthall) OpenLayers
* jody.garnett []gmail.com - (Jody Garnett) GeoTools / uDig
* andrea.antonello []gmail.com - (Andrea Antonello) JGrass / uDig
* tbadard []gmail.com (Thierry Badard) - GeOxygene, GeoKettle and GeoMondrian
* kneufeld []refractions.net (Kevin Neufeld) - PostGIS
* benjubb []gmail.com (Ben Jubb) - PostGIS, GEOS
* lorenzo []ominiverdi.com (Lorenzo Becchi) - OpenLayers
* tkeitt []gmail.com (Tim Keitt) - PostGIS, GDAL, QGIS

==About The Program==
===What is your plan for dealing with disappearing students?===

In order to minimize the likelyhood of disappearing students we will ensure that the OSGeo administrative contact and the mentor have full contact information (email, home phone, etc) so that we can keep in touch with them.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly progress reports, participation on public IRC channels and mailing lists will all help ensure ongoing commitment to the work.

===What is your plan for dealing with disappearing mentors?===
Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.

Further more the mentors are encouraged to actively involve the students in the community, but having the student interact with the mentor through the community channels rather then directly.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.
# Selecting students that have shown interest previously in the geospatial field.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

2007 Google SoC Project Milestones

2007-05-23T17:21:23Z

Wiki-Tkeitt: /* Project Information */

This page will be used to track the Milestones reached by each project particpating in the OSGeo Umbrella for the 2007 Google Summer of Code.

= Project Information =

{|border=1 align=center
| Student || Project || Primary Mentor/Contact || Alternate Mentor/Contact || Subscribed To Project Mailing List || Subscribed To OSGeo Mailing List || Repository Access
|-
| Daniel Bundala || GRASS - Line simplification & Smoothing Modules ([http://code.google.com/soc/osgeo/appinfo.html?csaid=3D7195C3927C616D Abstract])|| Wolf Bergenheim || - || Y || Y || Y
|-
| Maximilian Maldacker || GRASS - Shortest Path in Free Vector Space ([http://code.google.com/soc/osgeo/appinfo.html?csaid=FEF51B36978B92BF Abstract])|| Wolf Bergenheim || - || Y || Y || N
|-
| Klokan Petr Přidal || [[GDAL2Tiles_SoC_2007|GDAL - GDAL2Tiles, Tile Raster Driver]] || Howard Butler || - || Y || Y || N
|-
| Jens Oberender || [http://code.google.com/soc/osgeo/app.html?csaid=Ml0LEQJxRzMKMhJKHQ5FCXYEbxBSEg4ECSBSOUMBQAlV%0A GDAL - KML Read Support For Existing Driver] || Mateusz Loskot || - || Y || Y || Account created, not tested
|-
| Christophe Rousson || uDig - Data Caching || Ian Turton || Jesse || Y || Y || N
|-
| Eduin Yezid Carrillo Vega|| PostGIS - Materialized Views with Geometric Support|| Mark Leslie || Kevin Neufeld || Y || N || Y
|-
| Christopher Whitney || GeoServer - JTileCache || Justin Deoliveira || - || Y || Y || N
|-
| Petr Pridal || GDAL - Raster Driver For PNG/JPG Tile Structure || Howard Butler || ? || N || N || N
|-
| Daniele Romagnolil || GeoTools - Multi-Dimensional Raster Data Sources|| Simone Giannecchini || ? || N || N || N
|-
| Jan Jezek|| GeoTools and uDig - Transformation Algorithms || Jesse Eichar || N || N || N
|-
| Xing Lin || PostGIS - Coverage Model and Operations ([http://code.google.com/soc/osgeo/appinfo.html?csaid=2425D23F080CAAFB Abstract])|| Timothy Keitt|| (request to postgis-devel) || Y || Y || N
|-
| Anthony Manfredi || GeoServer - Style Edirot || Andrea Aime||? || N || N || N
|-
| Rui Li || uDig Interactive GeoRSS Tool || Richard Gould || ? || N || N || N
|-
| Philippe Vachon || GDAL - Synthetic RADAR Processor || Frank Warmerdam || Cancelled || N || N || N
|-
| Hans Haggstrom || GeoTools 3D Rendering Pipeline || Jody Garnett || Landon Blake || N || N || N
|-
| Adam Nowacki || GDAL - OCG WMS Driver || Daniel Morissette || ? || Y || Y || N
|-
| Michael Craig || 3D Rendering Pipeline Component For GIs Servers ||Jody Garnett || ? || N || N || N
|}

Note: Another similar table can be found here:
- http://docs.codehaus.org/display/GEOTOOLS/Summer+of+Code

= Navigation =
[http://wiki.osgeo.org/index.php/Google_Summer_of_Code OSGeo Google Summer of Code Home]

[http://code.google.com/soc/ 2007 Google Summer of Code Home]

List of [http://code.google.com/soc/osgeo/about.html OSGeo proposals for Summer of Code]

PostGIS SoC Ideas 2007

2007-03-15T16:58:19Z

Wiki-Tkeitt: /* Potential Mentors */

== Ideas for Google Summer of Code students wanting to work on PostGIS ==

=== Topology model and operations ===

The project consists in providing a standardized interface for storing topology information, that is sets of Edges, Nodes, Areas and their relations in constituting a Feature. There's already a [http://postgis.refractions.net/support/wiki/index.php?PostgisTopology draft implementation] of the model, what can be done is (in random order):

* Implementing topological operation directly using the topology model rather then converting input to simple Geometries.
* Import from / export to popular topology data formats (ie: TIGER)

=== Network model and operations ===

The project is aimed at providing a standardized interface for topological
network information storage and operations. Tipical use would be modeling
communication networks, composed by Links and Nodes, and performing
tasks such as least cost path finding.

==== Linking to CGAL Library ====

The [http://www.cgal.org/ Computational Geometry Algorithms Library] supports many algorithms for spatial analysis. Voronois, delaunays, etc.
==== Linking to Boost Graph Library ====

The [http://www.boost.org/libs/graph/doc/index.html Boost Graph Library] supports many algorithms for graph and network analysis. Because it uses a generic iterator-based interface, it can easily be grafted into other frameworks simply by providing the appropriate iterator classes.

=== Coverage model and operations ===

Allow storage and operations on coverage (raster-like) data.

=== GEOS performance improvements ===

The [http://geos.refractions.net/ GEOS] C++ library suffers from a design too closely bound to it's Java-implemented parent, [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]. This approach has introduced an unnecessary overhead throughout
the whole operations flow due to excessive dynamic polymorphism and heap allocations. Redesigning the most used subsystems could improve the overall performance. Random ideas:

* Redesign index classes using a templated approach.
* Enforce use of standard algorithms wherever appropriate.

== Potential Mentors ==

Developers in the PostGIS community who would be interested in supporting one of the above projects:
* [[User:Mloskot|Mateusz Loskot]] - mloskot[]gmail.com - interested in supporting ''GEOS performance improvements'' task
* [[User:Tkeitt|Tim Keitt]] - I'm interested in supporting "Network model and operations" and "Coverage model and operations" tasks

(please include your google account info)

== Other projects ==

Please see [[Google Summer of Code]]

PostGIS SoC Ideas 2007

2007-03-07T21:38:50Z

Wiki-Tkeitt: /* Linking to Boost Graph Library */

== Ideas for Google Summer of Code students wanting to work on PostGIS ==

=== Topology model and operations ===

The project consists in providing a standardized interface for storing topology information, that is sets of Edges, Nodes, Areas and their relations in constituting a Feature. There's already a [http://postgis.refractions.net/support/wiki/index.php?PostgisTopology draft implementation] of the model, what can be done is (in random order):

* Implementing topological operation directly using the topology model rather then converting input to simple Geometries.
* Import from / export to popular topology data formats (ie: TIGER)

=== Network model and operations ===

The project is aimed at providing a standardized interface for topological
network information storage and operations. Tipical use would be modeling
communication networks, composed by Links and Nodes, and performing
tasks such as least cost path finding.

==== Linking to Boost Graph Library ====

The [http://www.boost.org/libs/graph/doc/index.html Boost Graph Library] supports many algorithms for graph and network analysis. Because it uses a generic iterator-based interface, it can easily be grafted into other frameworks simply by providing the appropriate iterator classes.

=== Coverage model and operations ===

Allow storage and operations on coverage (raster-like) data.

=== GEOS performance improvements ===

The [http://geos.refractions.net/ GEOS] C++ library suffers from a design too closely bound to it's Java-implemented parent, [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]. This approach has introduced an unnecessary overhead throughout
the whole operations flow due to excessive dynamic polymorphism and heap allocations. Redesigning the most used subsystems could improve the overall performance. Random ideas:

* Redesign index classes using a templated approach.
* Enforce use of standard algorithms wherever appropriate.

== Potential Mentors ==

Developers in the PostGIS community who would be interested in supporting one of the above projects:
* [[User:Mloskot|Mateusz Loskot]] - I'm strongly interested in supporting ''GEOS performance improvements'' task
* [[User:Tkeitt|Tim Keitt]] - I'm interested in supporting "Linking PostGIS to the Boost Graph Library"

== Other projects ==

Please see [[Google Summer of Code]]

PostGIS SoC Ideas 2007

2007-03-07T21:37:15Z

Wiki-Tkeitt: /* Network model and operations */

== Ideas for Google Summer of Code students wanting to work on PostGIS ==

=== Topology model and operations ===

The project consists in providing a standardized interface for storing topology information, that is sets of Edges, Nodes, Areas and their relations in constituting a Feature. There's already a [http://postgis.refractions.net/support/wiki/index.php?PostgisTopology draft implementation] of the model, what can be done is (in random order):

* Implementing topological operation directly using the topology model rather then converting input to simple Geometries.
* Import from / export to popular topology data formats (ie: TIGER)

=== Network model and operations ===

The project is aimed at providing a standardized interface for topological
network information storage and operations. Tipical use would be modeling
communication networks, composed by Links and Nodes, and performing
tasks such as least cost path finding.

==== Linking to Boost Graph Library ====

The [http://www.boost.org/libs/graph/doc/index.html|Boost Graph Library] supports many algorithms for graph and network analysis. Because it uses a generic iterator-based interface, it can easily be grafted into other frameworks simply by providing the appropriate iterator classes.

=== Coverage model and operations ===

Allow storage and operations on coverage (raster-like) data.

=== GEOS performance improvements ===

The [http://geos.refractions.net/ GEOS] C++ library suffers from a design too closely bound to it's Java-implemented parent, [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]. This approach has introduced an unnecessary overhead throughout
the whole operations flow due to excessive dynamic polymorphism and heap allocations. Redesigning the most used subsystems could improve the overall performance. Random ideas:

* Redesign index classes using a templated approach.
* Enforce use of standard algorithms wherever appropriate.

== Potential Mentors ==

Developers in the PostGIS community who would be interested in supporting one of the above projects:
* [[User:Mloskot|Mateusz Loskot]] - I'm strongly interested in supporting ''GEOS performance improvements'' task
* [[User:Tkeitt|Tim Keitt]] - I'm interested in supporting "Linking PostGIS to the Boost Graph Library"

== Other projects ==

Please see [[Google Summer of Code]]

User:Tkeitt

2007-03-07T21:33:09Z

Wiki-Tkeitt:

My web site is [http://www.keittlab.org/]

PostGIS SoC Ideas 2007

2007-03-07T21:32:48Z

Wiki-Tkeitt: /* Potential Mentors */

== Ideas for Google Summer of Code students wanting to work on PostGIS ==

=== Topology model and operations ===

The project consists in providing a standardized interface for storing topology information, that is sets of Edges, Nodes, Areas and their relations in constituting a Feature. There's already a [http://postgis.refractions.net/support/wiki/index.php?PostgisTopology draft implementation] of the model, what can be done is (in random order):

* Implementing topological operation directly using the topology model rather then converting input to simple Geometries.
* Import from / export to popular topology data formats (ie: TIGER)

=== Network model and operations ===

The project is aimed at providing a standardized interface for topological
network information storage and operations. Tipical use would be modeling
communication networks, composed by Links and Nodes, and performing
tasks such as least cost path finding.

=== Coverage model and operations ===

Allow storage and operations on coverage (raster-like) data.

=== GEOS performance improvements ===

The [http://geos.refractions.net/ GEOS] C++ library suffers from a design too closely bound to it's Java-implemented parent, [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]. This approach has introduced an unnecessary overhead throughout
the whole operations flow due to excessive dynamic polymorphism and heap allocations. Redesigning the most used subsystems could improve the overall performance. Random ideas:

* Redesign index classes using a templated approach.
* Enforce use of standard algorithms wherever appropriate.

== Potential Mentors ==

Developers in the PostGIS community who would be interested in supporting one of the above projects:
* [[User:Mloskot|Mateusz Loskot]] - I'm strongly interested in supporting ''GEOS performance improvements'' task
* [[User:Tkeitt|Tim Keitt]] - I'm interested in supporting "Linking PostGIS to the Boost Graph Library"

== Other projects ==

Please see [[Google Summer of Code]]