The GeoTools 8.x branch started out as 2.8.x with a quick proposal to change the project version number policy. The major technical direction is the addition of "live" documentation using sphinx.

RnD and proposals completed for the 8.x branch:

• Allow build with Maven 2 or Maven 3
• Clean up FeatureEvents — What changed where
• Describe Function with FunctionName — describe a function
• Detailed Argument and Return Info for FunctionName — Modifying FunctionName to support detailed info about argument/return parameters.
• Function lookup using qualified Name — a function by any other name
• Introduction of getInfo — What is this? No really...
• Java 6 — I can haz 6?
• Join Support — Adding joins to query api
• MapContext Refactor — the map is back
• New ILIKE statement — improving the search conditions
• ResourceId — who what where when
• Skip GeoTools 3 — GeoTools 8-SNAPSHOT
• Sphinx Documentation Process — Sphinx documentation process
• Support Multi-Valued Attributes in Filter Comparison Operators — filter x-path
• Temporal Filters — Temporal filter support based on FES 2.0 spec
• Transition to GitHub — git ready
• Upgrade to 8.0

Usability Targets

Documentation

Our initial research into the use of Sphinx has gone well; and was able to provide us a website for the 2.7.x series.
Jody Garnett has ported the wiki Developers Guide and User Guide over to this format.

Additional help is needed to capture more of the code examples in Java files so that we can always include code that compiles.

Simplification

We missed a few opportunities for simplification in 2.7.x:

• :white_check_mark: Query - done in 2.7.x
• :white_check_mark: FeatureLock - done in 2.7.x
• Transaction

Research Targets

Application Schema

The work on Application Schema support by the AuScope team is wrapping up.

One thing this missed was the production of classes for us mere mortals working with Java code (rather than xml schema).

So the shopping list for java developers is:

• A FeatureTypeBuilder - that is able to produce application schema compatible feature types.
• FeatureCollection support classes to assist with implementations
• Something like ContentDataStore that can be used as a starting point

Geometry (Geodetic/3D)

We continue to have inquery into a data model for 3D Geometry, and more importantly geodetic geometry.

We looked at working with the deegree3 project on the java-collab list for 2.7.x and nothing came of it. As such I expect we will need to go it our own.

N-Dimensional GridCoverage

This continues to be a research topic, in particular to work with netCDF data.