An OGC Web Map Server client implementation that can be used directly or as through the GridCoverageExchange API. Direct usage is recommended, as the GridCoverageExchange access for WMS is not well tested and is complicated to use. It supports WMS versions 1.0.0, 1.1.0, 1.1.1, and 1.3.0.

Grid coverage reader for image georeferenced by a world file. File format consists of consisting of a plain image and a "sidecar" world file to georeference the image, a and projection file file to indicate the coordinate reference system used.

This module provides access to tile services, notably OpenStreetMap and Bing Maps. It includes a TileLayer, for displaying tiles into a GeoTools map.

Provides widgets for map display and other GUI elements

Provides read and write support for GeoPackage SQLite format.

Datasource created to read ArcGrid raster format. Currently Serving as a prototype for the GridCoverageExchange API.

Implementation of GridCoverage. Provides support for rasters and some image processing like reprojection.

A parser that takes a Constraint Query Language input string and produces an equivalent org.opengis.filter.Filter.

Abstract datastore implementation and helper classes / apis to be extended by datastores backed by releational databases accesible via jdbc.

Provides HTTPClient with support for Multithreading.

Filter XML support for Geotools.

A set of Http clients created by a factory method.

Contains implementations of Coordinate Reference Systems (CRS), conversion and transformation services.

The main module contains the GeoTools public interfaces that are used by other GeoTools modules (and GeoTools applications). Where possible we make use industry standard terms as provided by OGC and ISO standards. The formal GeoTools public api consists of gt-metadata, jts and the gt-main module. The main module contains the default implementations that are available provided to other GeoTools modules using our factory system. Factories are obtained from an appropriate FactoryFinder, giving applications a chance configure the factory used using the Factory Hints facilities. FilterFactory ff = CommonFactoryFinder.getFilterFactory(); Expression expr = ff.add( expression1, expression2 ); If you find yourself using implementation specific classes chances are you doing it wrong: Expression expr = new AddImpl( expression1, expressiom2 );

Processes for handling of features and feature collections.

The render module contains a renderer built around the interface in api and main. This is a first class geotools module as creating a visual representation of features is considered key to most geospatial applications.

GML3 XML support for Geotools.

Supporting utilities for complex features.

DataStore for Oracle Database.

Standard interfaces implemented throughout the library.

Standard interfaces implemented throughout the library.

TODO

Schema based xml parsing. This module contains tools for creating bindings from xml types to java types. Schema modelling is based on Eclipse XSD.

Contains sample data for testing purpose.

Graph classes that builds and walk networks based on Feature relationships. The original graph package has been developed using the JUMP Feature API. Its intension is to be able to aid automated skeletonization of water bodies by computing directionality of generated skeletons. The work for the original JUMP based library has been funded by the BC Proventional Government department of BMGS. This library has been ported to geotools2 as part of the VWFS project sponcered by Geo Innovations.

DataStore using Java properties files, a useful reference implementation for test cases. This implementation is based on ContentDataStore and supports the use of ResourceId to support history.

Datasource created to read GeoTIFF raster format.