GeoTools 2.4.x is currently under active development on trunk; and should be considered unstable. The GeoTools 2.4.x branch is focused on: Quaility Assurance – particularly for datastores Consistency – focus on consistent use of Factories The real goal here is to fix the problems that prevented the Feature Model Branch from merging successfully. For more information please review GTSteering.pdf and 2007 Q1.

Overview Resources Status Planning Details

Resources GTSteering.pdf 2007 Q1 Add a dispose method to DataStore API Add hints support to Query object — Query,Hint,Generalization,Fetch Allow redirection to alternate logging API — You are debugging GeoTools, in a J2EE application, do you know where your logs are? Catalog Improvements Change handling and stability keeping procedures — Keep trunk stabled like an elephant Cleaning up dependencies between various modules and coverage Connection pool subsystem upgrade DataSource Hint for EPSG — Publish / Find / Bind for EPSG Authority Expression Improvements Fix the Docs — documentation for users Provide Parsers in a consistent fashion — lexify this (bad object pun) ReferencingFactoryFinder incompatible change SQLEncoder Upgrade to GeoAPI Filters Tile Server Client Update Style Interfaces to use GeoAPI Filter — Keeping stylish Upgrade to 2.4 XML-XSD To Supported

Downloads Avaiable 2.4 Downloads: 2.4.0 2.4.1 2.4.2 2.4.4 2.4-M0 2.4-M1 2.4-M2 2.4-M3 2.4-M4 2.4-RC0

Status

The following issues are critical and represent steps that must be taken before 2.4-RC0 can be released.

jira.codehaus.org (0 issues)
Pr	Key	Summary

The following issues are critical and represent steps that must be taken before 2.4.0 can be released.

jira.codehaus.org (0 issues)
Pr	Key	Summary

For the complete list of tasks scheduled for the 2.4.x release:

• 0 issues

Volunteers are needed - in particular help is needed for:

• Feature Model Preparation

Planning

• GTSteering.pdf
• 2007 Q1
• 2007 Q2

Goals

The following steps are to be taken as part of the 2.4 development effort.

• Reduction of supported library to working data sources
  • test: DataStore Conformance Test
  • test: coverage check - developers guide requirement
  • test: GeoResourceInfo implementation
• move other plugins to community section
• Clear support for use of factories at at the datastore level
  • test: ability to create POJO from shapefile
• Creation of Grid Coverage data access API
  • test: Service and GeoResource handles

Sponsor Goals

The Refractions/uDig focus is on data source quality - specifically:

• Performance suitable for anlaysis work
  • O( log N ) performance on data source opperations
  • O( 1 ) on metadata requests such as bounds
  • Event notification
• Storage of common types (boolean, TM_Instant,etc...)

For GeoServer/GeoSolutions the focus is on GridCoverage formats:

• Additional Formats (shared with 2.3.x branch)
• (started) Definition of a API for Grid Covearge discovery and access
  • need to ensure Service/GeoResouce handle compatibility

For GeoServer/Social Change Australia (transitional work to revised FM):

• need Factory injection situtation cleared up
  • delegate to "FeatureBuilder" interface

For TOPP/GeoServer the focus is again on quality:

• QA and consistency to keep the library from falling apart

For Axios/GeoServer/uDig there are a few key fixes:

• (done) Parsing support for common literal types (boolean, temporal, etc)

Unsponsored Goals

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

• User Guide
  • (started) http://www.geotools.fr/manual/geotools.xhtml
  • (started) http://docs.codehaus.org/display/GEOTDOC/Home
  • clean out old user docs
• OSGeo Iccubation completion
  • providence review
  • (ongoing) (c) Open Source GeoSpatial Foundation
• XML Parsing
  • GTXML QA checks and Documentation requirements for inclusion in 2.4

Details

Project Structure

We have changed the project structure .. the chief change is the creation of an "unsupported" directory:

• modules for research projects
• modules that do not meet project policies; such as user documentation or test coverage