|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
See:
Description
| Display | |
|---|---|
| org.geotoolkit.display.axis | Support for drawable axis with graduation. |
| org.geotoolkit.display.shape | A set of Java2D shapes and a few utility methods. |
| org.geotoolkit.gui.headless | A set of non-graphical classes sending informations to the standard output stream or through emails. |
| org.geotoolkit.gui.swing | Miscellaneous widgets. |
| org.geotoolkit.gui.swing.coverage | Widgets related to grid coverages. |
| org.geotoolkit.gui.swing.event | Events fired from the org.geotoolkit.gui.swing package. |
| org.geotoolkit.gui.swing.image | Widgets related to rendered images. |
| org.geotoolkit.gui.swing.referencing | Widgets relative to the referencing package. |
| org.geotoolkit.gui.swing.tree | Workaround for the missing javax.swing.tree.TreeNode.getUserObject()
method. |
| Geometry | |
|---|---|
| org.geotoolkit.geometry | Basic geometric objects. |
| Feature and filter | |
|---|---|
| org.geotoolkit.storage | Place holder for future DataStore services. |
| Coverage and Raster | |
|---|---|
| org.geotoolkit.coverage | Coverage implementation. |
| org.geotoolkit.coverage.grid | GridCoverage2D implementation. |
| org.geotoolkit.coverage.io | Provides GridCoverageReader implementations for creating
GridCoverage2D instances from a datasource. |
| org.geotoolkit.coverage.processing | Coverage processor implementations. |
| org.geotoolkit.coverage.processing.operation | Implementations of operations. |
| org.geotoolkit.coverage.sql | A schema for storing coverages metadata in a SQL database. |
| org.geotoolkit.image | Helper classes for building images. |
| org.geotoolkit.image.io | Base classes for extensions to ImageReader and
ImageWriter for spatial data. |
| org.geotoolkit.image.io.metadata | Spatial (usually geographic) informations encoded in images as metadata. |
| org.geotoolkit.image.io.mosaic | Support for reading and creating mosaics of geographically referenced images. |
| org.geotoolkit.image.io.plugin | Extensions to ImageReader and ImageWriter for binary
files and text files. |
| org.geotoolkit.image.io.stream | Services provider for image input streams. |
| org.geotoolkit.image.jai | A set of Java Advanced Imaging operations. |
| Numerical calculation and processing | |
|---|---|
| org.geotoolkit.math | A set of mathematical objects and algebraic utilities. |
| org.geotoolkit.measure | Measures (like angles) and their formatters. |
| org.geotoolkit.nature | Algorithms related to the observations of natural phenomenons. |
| org.geotoolkit.process | Operation applied to some given data to achieve whatever analyze or model transformation. |
| Utilities | |
|---|---|
| org.geotoolkit.console | Defines main methods to be invoked from the java command in a shell. |
| org.geotoolkit.factory | Utility classes which enable dynamic binding to factory implementations at runtime. |
| org.geotoolkit.io | Extensions to standard Java Reader and Writer for I/O operations. |
| org.geotoolkit.io.wkt | Well Known Text (WKT) parsing and formatting. |
| org.geotoolkit.lang | Annotations relative to Java language patterns applied in the Geotk library. |
| org.geotoolkit.util | Simple data objects and miscellaneous utilities. |
| org.geotoolkit.util.collection | Addition to the collection framework. |
| org.geotoolkit.util.converter | Performs conversions between instances of different classes. |
| org.geotoolkit.util.logging | Extensions to the Java logging framework. |
| org.geotoolkit.xml | Provides methods for marshalling and unmarshalling Geotk objects in XML. |
Overview of Geotoolkit.org (abridged Geotk).
Geotk requires Java 6 Standard Edition. There is no additional requirement for metadata and referencing modules. But the coverage module requires the Java Advanced Imaging extension (see Running Geotk for download information). While not mandatory, users are encouraged to declare JavaDB in their classpath in order to take advantage of the embedded EPSG database. JavaDB is bundled in the Oracle distribution of JDK.
Geotk does not require explicit initialization and shutdown for most cases.
However a few services behave better when managed in an initialization - shutdown
cycle. The Setup class provides a central place for initialization
and shutdown, but developers can also gain more control by invoking themselves the various methods
identified by the Configuration annotation.
The @version javadoc tag gives the last Geotk version when
the code of this class got a significant change. For example if a class is annotated
with @version 3.00, then this class got no significant change since the release
of Geotoolkit.org 3.00 in June 2009.
The @since javadoc tag gives the Geotk version when the annotated
element (class, method, etc.) was first introduced. If the declared version is the same
than the class @version, then that element is under development and uncommitted:
it may change in any future snapshot and it will become stable only after the next release.
Stable API (for example those annotated as @since 2.4) will not
change lightly. If a stable API need to be removed, it is first annotated as @deprecated
and will be removed only in a future release.
The code were contributed by authors from different organisations. The organisation name appears between parenthesis after the author name, sometime in abbreviated form. More than one organisation may be listed for the same author if he continued to work on the code while moving to an other organisation. The organisation names used in this documentation are:
Geomatys Geomatys. Geosolutions Geosolutions. HSRS Help Service Remote Sensing. IRD Institut de Recherche pour le Développement. MPO Ministère des Pêches et Océans Canada. OpenGeo OpenGeo. Refractions Refractions Research. TOPP The Open Planning Project. UBC University of British Columbia. UWB University of West Bohemia. USGS U.S. Geological Survey. Actually not a direct contributor to Geotk, but their C/C++ code in the Proj4 project were used as a basis for the map projections.
Implementations of GeoAPI
interfaces usually (but not always) begin with Default or Abstract prefix. The later is used
when a class is abstract according ISO specification; the class is not necessarily abstract in the Java sense. For
example AbstractCS is abstract according ISO (users should always specify a
more accurate subclasses), but can still be instantiated in Java. Actually it is instantiated in some
exceptional cases (especially during WKT parsing) when the actual coordinate system type is really unknown.
The Default or Abstract prefix cover the majority of cases for GeoAPI
implementations, but there is a few exceptions. Implementations working only in space having a fixed number
of dimensions are suffixed with 1D, 2D, 3D or 4D. The general implementation
- if any - is prefixed with General. Example: Envelope2D and
GeneralEnvelope.
Classes that are not GeoAPI implementation are usually not prefixed by any of the above.
Geotk uses the Java logging by default, but
can redirect its logging to Log4J or Apache's common-loggins. See org.geotoolkit.util.logging
for details.
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||