2.5.x

GeoTools 2.5.x is focused on switching to new feature model; we have a list of QA tasks to confirm the work is complete - but our scope has been met for this release.

• Status
  • Issues Summary
• Planning
  • Technical Goals
  • Sponsor Goals
  • Unsponsored Goals
• Acceptance Tests
  • GeoServer Acceptance
  • UDIG Acceptance
  • Technical Debt

Change proposals completed for the 2.5.x branch:

• FeatureCollection for Java 5
• Graduate from OSGeo — The last step for OSGeo graduation
• Change to SimpleFeature — Expected refactoring, performed during the FOSS4G code sprint
• Handling of Unsupported Modules — got code?
• DataAccess super class for DataStore — introduce org.opengis.geoapi.Feature
• GeomeryFactoryFinder Proposal — Do you know where your geometry is?
• Module renaming
• Support GetGMLObject
• Svn Cleanup 2008 — SVN CLEANUP
• Switch from JSR-108 to JSR-275 for Units — JSR-275 is ready
• Upgrade to 2.5
• Use of FilterCapabilities — what filters are available?
• Raster Symbolizer support — Refactoring the actual Raster Symbolizer architecture / Implementing the needed functionalities
• Dynamic SLD Graphic objects — Programmatically extending SLD Graphic capabilities

Planning

Reports:

• 2007 Q1
• 2007 Q2
• See Proposals above

Technical Goals

The goals of the 2.5 release are:

• ✅ Switch to the new Feature Model
• ✅ Upgrade to Java 5

Sponsor Goals

The following represents sponsored work targeted for GeoTools 2.5:

• ✅ ISO Geometry implementation available as a supported module

In many cases this work is available as an unsupported module for GeoTools 2.4.

Unsponsored Goals

The following work is critical to the success of GeoTools but has not attracted sponsorship - if you can help out please jump on the mailing list and let us know.

• User Guide
  • ✅ http://docs.codehaus.org/display/GEOTDOC/Home
  • ⛔ clean out old user docs
• OSGeo Iccubation
  • ✅ (c) Open Source GeoSpatial Foundation
  • ✅ Review of source code

Acceptance Tests

✅ GeoServer Acceptance

GeoServer has performed a round of profiling and has brought the new feature model within 10-20% of the prior performance.

⛔ UDIG Acceptance

uDig trunk has returned to using GeoTools trunk; as such the following will need to be sorted out before 2.5.x can go out the door (the functionality was dropper or suffered code rot between GeoTools 2.2 and GeoTools 2.5).

We cannot release a version of uDig using 2.5.x until:

1. ✅ Shapefile Deadlock - threading issues that prevented editing a shapefile while it was being read in a seperate thread. This prevents any GeoServer later that 1.4.1 working as a WFS-T backed by a shapefile (postGIs and so on work fine).

   • ✅ This issue was resolved as a complete rewrite by Jesse in January of 2008.

2. Aggregate Functions - literally functions that operate on a FeatureCollection

   • ✅ Min / Max / Sum etc...
   • ⛔ Classification Functions (as used by uDig to power the Style Themer)

The following technical debt really effects the project (rendering some datastore useless):

1. Filter 1.1 / GeoAPI Filter Transition: Use FitlerFactory2 etc...

   • SAX Parser
   • DOM Parser
   • XDO Parser
   • XML-XSD Parser
   • StyleFactory / SLD classes

2. FilterVisitor Transition

   • ✅ Utility FilterVistitors (for Duplicating / finding Feature Ids etc...)
   • SQL Generation: PrePostFilterVisitor

3. Feature Event Notifications from Feature Store

   • Shapefile
   • Postgis
   • Arcsde
   • Oracle
   • Property

⛔ Technical Debt

There is a Technical Debt page with details of some "undone" work (often work left over when a commercial funding ended for a specific task).