Message-ID: <1265401280.5323.1369501511556.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5322_1882429612.1369501511555" ------=_Part_5322_1882429612.1369501511555 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document outlines several key features of the Geotools too= lkit. Geotools development is active and there are many ideas for future development. The features on the follo= wing page refer to current development on the SVN trunk. For features incl= uded in specific releases, see the following pages:
Geotools implements Open Geospatial Consortium (OGC) specifications as they are developed.
Geotools is associated with the GeoAPI project that is crea= ting interfaces for Java GIS projects. Many of these interfaces are impleme= nted in geotools with more implementations planned.
Data is the life blood of any GIS project, so geotools tries to support = as many data formats as possible.
The DataStore interface is used to access vector data.
Grid coverage (raster) data formats are accessed with the GridCoverageExcha= nge interface.
Data formats supported are:
See Grid Cov= erage Exchange Design for design notes about this new interface.
The following data formats are supported:
Depreciated DataSource raster implementations are:
Features are used to represent basic geographic elements in a vector sys= tem. These are composed of both geometries and attributes.
Java Topology Suite (JTS) is used as the cur= rent geometry model. This library is an implementation of the Simple Featur= es Specification for SQL, http://www.opengis.org/docs/99-0= 49.pdf. It also provides in memory spatial indexing support and robust topologic operations, though they are not used much at pre= sent in the codebase.
If you're willing to add some vector computation operations (for example= , overlay) please step up: we need someone willing to work on an operation = API and the associated implementations. See the Process API page for more information.
A grid coverage provides support for the raster data format, that is, a = georeferenced grid of numbers that can be used to represent data ranging fr= om satellite images, to digital elevation models, noise distribution and so= on. See also the OpenGIS specification about grid coverages, http://www.opengis.org/docs/01-004.pdf.
Grid coverages are based on the JAI library wh= ich provides support for data management, presentation, image data format a= ccess, tiling support, a framework for raster data processing with lots of = predefined operators.
The cts-coordtrans (CTS) module implements a subset of the OGC's Coordin= ate Transformation Services specification, http://www.open= gis.org/docs/01-009.pdf. It provides an implementation for general posi= tioning, coordinate reference systems, and coordinate transformations.
Types of transformations provided include datum shifts, map projections = (Mercator, Transverse Mercator, Lambert Conformal Conic, Albers Equal Area = Conic, Stereographic, Orthographic) and others.
Geotools has two renderer implementations:
Allows for symbolizing (colour, line thickness, opacity, etc.) of datase= ts. This is closely modeled on, and fully supporting, the OpenGIS Styled La= yer Descriptor specification, http://www.opengis.org/docs/= 02-070.pdf. These can be stored as XML documents.
Filters provide a way to specify a subset of features to operate on. Thi= s supports both attribute and spatial constraints and a method of storing t= hese as XML documents.
This is an implementation of the Filter Encoding specification, http://www.opengis.org/docs/02-059.pdf
This is currently an active area of development. See the GUI Architecture page for information a= bout where development is heading.
The Legend module was recently added. Also maps and some tools (zoom, pa= n, etc.) are present.
Allows the creation of graphs and networks based on MultiLineStrings or = arbitray Geometries and Spatial Relationships. Graphs can be walked using = the visitor pattern. Common walks, such as shortest route, are already avai= lable. Other walks may also be defined by the user.
This provides a method to validate features base on different constraint= s. Allows the definition of test suites based on validaiton plug-ins. Tests= suites (and indeed validaiton plug-ins) are configured using xml files.
A working validation Processor is provided as a demo.------=_Part_5322_1882429612.1369501511555--