GIS represents one of the last great frontiers (along with BI) where the data volume lets everyone work on real computer science.

This is a great field, and as long as you are not in europe there is enough public data to make things interesting for the open source developer.

(I actually like any form of programming in the large, distributing computing, design, ...)

Here are a couple of the open source projects I am known to work on:

Contact:

•  jodygarnett
• jgarnett@refractions.net

What am I doing now ...

• Working on fixing up the feature model to be used by GeoAPI and JUMP. My brain hurts trying to keep up with the ISO specs and variations in the wild ...
• Working in South Africa building a bridge to an area of commercial GIS often over looked by the open source community - Smallworld. Pretty slick concepts too bad about the 2 tiered architecture
• Other then that I am living the dream

Blog at weblogs.java.net

Jody Garnett's Blog
GeoHack Starting up an industry specific blog - GeoHack
Community 1 Maven 0 Eclipse -1 I cottoned on to the current blog fest on the merits of Maven. I have been running with Maven since version 1.0; but mostly I recommend going into Maven (or any build system) with a couple of friends, nothing wastes time like a build system.
Java at FOSS4G wrap up Article GeoTools was really well represented at this years Free and Open Source Geospatial conference.
FOSS4G 2007 2 days and counting The Free and Open Source Software for Geospatial conference is ramping up and Java should be everywhere. I have the privileged of working with a number of people doing presentations this year - and it has been great watching the GeoServer project (running Java EE) catch up to the long time king of the hill MapServer (written in C).
JSR-275 And why GeoTools does not care yet The deadline for JSR0275 is coming up on July 8th, as one of the top users of the JSR108 (which was withdrawn) you would think GeoTools would care about what is going on ... here is why we don't: Java 1.4

Tasks and Tracking

Here is what Jira thinks I should be doing: