FOSS4G 2009 Code Sprint

Organizing Contacts

• Jody Garnett, Tyler Mitchell

Code Sprint - what's that?

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

Venue

For map and more details see File:FOSS4G 2009 Code Sprint Information.pdf

• Date: Saturday 24 October (the day after the conference).
• Time: 9am-5pm
• Where: University of Technology Sydney – Ultimo Campus, Level 3, Building 6
• Rooms: CB06.03.19, CB06.03.20, CB06.03.21

More than 80 attendees are expected!

Motivation and Direction

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

• http://www.infrae.com/about/activities/sprintathon/tips
• http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
• Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

Summary of Workgroups

List of Workgroups here, more info follows...

• PostGIS
• uDig & friends
• The desktop comparison tasks list
• OSGeo in general, especially Marketing & Education
• Geometry (note project info below, being held at different venue)
• Live DVD
• OpenLayers
• MapServer
• Mapbender

To participate, start a section below for your project.

PostGIS

Coordinator:

• Paul Ramsey

Attending:

• Person 1
• Person 2

Goals:

• Bug fixes and clean-up for a 1.5 release.

uDig & friends

Coordinator:

• Andrea Antonello

Attending:

• Andrea Antonello
• Silvia Franceschi
• Jody Garnett
• add yourself here...

Goals:

• database datastores
• style editors
• define install/update mechanisms for plugin projects (JGrass, BeeGIS, Axios)
• mosaic support for udig

The desktop comparison tasks list

Attending, for which project

• uDig Silvia Franceschi
• QGis ?
• gvSig ?
• GRASS Clara Tattoni, Marco Ciolli, Paolo Zatelli

(for inspiration of tasks, see Applications)

Feel free to add ideas here:

• vector data visualization
  • load a shapefile for quick visualization (with prj, without prj, with topology, without topology)
  • load a particularly large shapefile
  • load a dwg
  • load a dxf (2D and 3D)
  • ...

• vector data editing
  • create new geometry layers
  • add an attribute of the geometry as new column to the dataset
  • show existing editing tools (snap, intersections, merge, etc)
  • vector analysis
  • topologic analysis
  • network analysis
  • linear reference system
  • ...

• raster data visualization
  • load a tiff (GRASS: import vs register with r.external)
  • load a jpg
  • load an ecw
  • load a Mrsid
  • load a GRASS raster
  • load a mosaic of images
  • ...

• raster data editing
  • map calculations on raster data
  • cost surfaces
  • hydro flow
  • geomorphometry
  • solar energy calculations
  • ...

• databases
  • SQL queries
  • visualization of spatial data from PostGIS
  • visualization of spatial data from SQLite
  • visualization of spatial data from Oracle spatial
  • visualization of spatial data from ArcSDE
  • visualization of spatial data from MySQL
  • visualization of spatial data from H2spatial
  • create new datasets in the above databases
  • convert between table with x,y[,z] and vector map
  • ...

• web service visualization and query
  • load a WMS dataset, query its information
  • load a WFS dataset, query its information
  • load and edit a WFS-T dataset
  • load a WCS dataset
  • WPS
  • ...

• scripting engines
  • batch mode executions of commands
  • supported languages
  • ...

• printing
  • support for printing
  • support for storing printing layouts
  • ...

See also

• Stefan Steiniger, Geoffrey J. Hay. Ecological Informatics 4 (2009) 183–195, Free and open source geographic information tools for landscape ecology. (DOI and preprint PDF)

OSGeo in general, especially Marketing & Education

Coordinator:

• Tyler Mitchell

Attending:

• Arnulf Christl
• Daniel Kastl
• ...

Goals: For all those who are around during this day but not going to do coding and want to talk more generally about OSGeo directions, etc. Likely follow-up from BoF events

• Review marketing and outreach ideas and needs.
• Work on the OSGeo presentation, create derivateives for different presentation lenghts and audiences
• Compile, update and comit templates for presentations
• Talk:The Future of OSGeo, collect and organize opinions from the OSGeo Discuss mailing list.

Geometry

Venue:

• This sprint will occur at Intersect the time axis on Sunday 25 October at an alternate venue - as such we ask anyone attending to RSVP (we are limited to 12 people)

Coordinator:

• Ben Caradoc-Davies

Attending:

• Ben Caradoc-Davies
• Jody Garnett
• Andrea Aimee
• Andrea Antonello
• Silvia Franceschi
• ...

Goals:

• Progress ISO 19107 / GML 3D geometry collaboration (OSGeom). See <java-collab@lists.osgeo.org> for more.

Plan:

Some subset of Markus Schneider's proposal:

1. DONE - Remove all topological and spatial analysis methods in the interfaces from the SVN for now, so we can focus on sanitising the model.
2. Add factories. I would like to add two factories similar to the ones in the deegree 3 SVN:
   • SFS geometries:
     • http://download.deegree.org/deegree3/nightly/core/javadoc/org/deegree/geometry/SimpleGeometryFactory.html
   • ISO 19107/GML 3
     • http://download.deegree.org/deegree3/nightly/core/javadoc/org/deegree/geometry/GeometryFactory.html
   • In deegree 3, these factories are bound to a JTS-based implementation. As we only have interfaces for the geometry types in the osgeom repository for now (and no implementations), I would create interfaces from the factories.
3. Add a basic implementation that is just a bean representation without operations. We could finally start to add JUnit tests then.
4. Add GML parsers/exporters. I understood that one may want to keep this aspect out of the repository, but I don't see how we could test the difficulties in representing GML geometries (e.g external xlinks) without this. It also would make setting up geometries for testing much easier. Maybe we could keep the GML parsing/exporting isolated from the rest of the code.
5. Of course we would take on the operations subject again, when we find consensus here.

Live DVD

Coordinator: Cameron Shorter

• .

Attending:

• .

Goals:

• Brainstorm ideas for improvements to the LiveDVD
• Set guidelines in place for build
  • Documentation guidelines
  • Desktop layout
• Target other distribution media

OpenLayers

Coordinator:

• .

Attending:

• Roald de Wit
• Bart van den Eijnden
• Person 3

Goals:

OpenLayers bug fixes. Describe any additional goals here.

MapServer

Coordinator:

• Daniel Morissette

Attending:

• Person 1
• Person 2

Goals:

• Work on the 5.6.0 release, including:
  • Testing the current beta/release candidate
  • Bug fixes
  • Release of 5.6.0-RC1 (depending on how beta4 went)
  • Work on documentation

• Discuss new features, future work

Project

Coordinator:

• .

Attending:

• Person 1
• Person 2

Goals:

Describe goals ...