gt-main class holds a number of internal and abstract classes useful to those implementing support for additional
These classes should be moved to
gt-main when time permits.
gt-main module provides many well known classes covered in the public documentation:
A few public exceptions:
AbstractDataStore is an old base class for
DataStore implementations, currently used only by
PropertyDataStore (Old). All new stores use
This class is helpful starting point, however we have taken the lessons learned and wrapped them up in
ContentDataStore covered in the gt-main documentation.
The following classes are related:
DefaultFeatureResults- the original name of
There are a large number of DataStore helper classes in
Conformance test case:
These managers, with their supporting readers and writers are responsible for
AbstractDataStorebeing able wrap transaction and locking support around you work.
You can store a
TransactionStateDiffin a Transaction, the
DiffFeatureWriterswill collect any changes for you in memory which you can review when the user calls commit.
Lots of abstract and utility classes are available when working with
FeatureCollections often form a pair with the iterator they use to make contents available:
And the lower level iterator helpers:
SimpleFeatureIteratorImpl- used by
DefaultFeatureCollectionto access all contents
NoContentIterator- used to throw an exception on next()
Low-level implementation support for implementing
These readers wrap around your simple
FeatureReader and add additional functionality such as filtering:
A few even work on iterators:
Where general facilities are available we need
Sub-zero: These are not used in practice they were intended to be used for attribute level operations; in practice everyone works
directly with features. The only place where they are used is with the Shapefile implementation where they are used to “join” the attributes
Wrappers used by
DataUtilities to morph to
Open Web Services¶
Some of the data structures used by open web services such as WMS and WFS are defined here.
Some of the SAX, DOM and Transform classes for handling are defined in
Their use for XML and GML handling will be covered in
gt-xml module documentation.
gt-main interfaces for
Style are a straight extension of the
gt-api interfaces. Please note these implementations are not threadsafe - extensive copy constructors have been provided if you need to copy these data structures for use in an isolated thread.
The Filter classes in
gt-main are deprecated; and have been so since GeoTools 2.3. We are having trouble removing all the existing test cases that depend on these old Filter definitions.