Google Summer Of Code Ideas List

Below is a list of topics for a Google summer of code project. However, several of those topics need to be evaluated for their fitness, i.e. a sufficient degree of innovation. We also need to look which of those topics would enhance OpenJUMP Vector editing and analysis strength, and which topics are urgently needed to complete the set of standard GIS functionality.

Notes:

1. GSofC student applications are from *March 29th to April 9th*. (Mentoring applications are due March 8th-12th)
2. All projects require a "decent" knowledge of programming in JAVA. Certain topics require even advanced Java knowledge (i.e. the topics involving databases). An introduction to development with OpenJUMP will be given by us.
3. The time of the GSofC is given from May 24th to August 16th, i.e. three months

List of Possible Topics 2010

• Continuing work on the JTIN library that allows OpenJUMP to work with TIN data. Special focus on publishing functional plug-ins for existing code, and on enhancing JTIN to work with extra-large data sources - JTin should use now JTS 1.11 functions. (sstein - Priority Topic, lbecker +1)
• Work on adding support for "external" tables (non-spatial features) in OpenJUMP.
• Work on routing plug-in for OpenJUMP.
• Work on upgrades of OpenJUMP core. This would include adding support for new Java language features and splitting the program "model" from the GUI. E.g. implementing a docking framework.
• Work on angle and direction support for JTS Warped library. (sstein: not sure what is meant here)
• Work on precision CAD drawing and modification tools for OpenJUMP.
• Work on support for cartographic map production from OpenJUMP using open source tools like Scribus and Inkscape. (Focus on enabling export of Inkscape compatible SCG from OpenJUMP.)
• Integrate cartographic projections support into OpenJUMP core (using deegree, geotools or Proj4J libraries). (sstein - Priority Topic, lbecker +1)
• Continuing Work on an abstract data layer and a model that allows to store data in the H2 database. This way OpenJUMP should be enabled to work also with large datasets and not only datasets that can be load into the memory. (sstein - Priority Topic, lbecker +1).
• Implementation of (explorative) statistics tools (charts and graphs) for data analysis and reporting (see for instance GeoDa and JFreeChart).
• Implementing build-in write support for databases such as SpatialLite, PostGIS, Oracle and MySQL that allows all-at-once but also incremental writing (see gvSIG implementations).
• Continuing developments of a Web Processing Service (WPS) plugin for OpenJUMP and a server based on OpenJUMP functionality (see WebGEN by Moritz Neun and Theodor Foerster). (sstein - Priority Topic).
• Integration of a help system for (analysis) functions.
• Improving text labeling options (see gvSIG plugin).
• Creating a draft and proptype of "OpenJUMP Mobile" for data creation and editing in the field. This involves in particular the design of a new GUI that allows to use existing mechanisms.
• Extend OJs core so that annotations can be stored including images and web links (similar to Google Maps Push Pins).
• Implement a default-settings/ini-file system to allow OpenJUMP to be used in larger business operations. (sstein: not sure if that is a 3 months task)
• Multi criteria decision analysis Tools for OpenJUMP
• JEQL for OpenJUMP (?)
• Integrating Sextantes toolbox model and Flow-Chart-Modeller in OpenJUMP

If you are interested in one of those topics please write to Landon (sunburned.surveyor[.at.]gmail.com) or Stefan (sstein[.at.]geo.uzh.ch) or even better: write both.