Package org.geotools.api.data
package org.geotools.api.data
Defines the DataStore API via which all data is imported or exported.
All DataStores (e.g. PostGIS, Shapefile(tm), GML...) must provide implementations of the DataStore interface and the DataStoreFactorySpi interface. These interfaces allow new types of datastore to be plugged into applications which use GeoTools without the need to modify any code.
Example:
FeatureStore postgis = new PostGisDataStore( ... );
Query all = Query.ALL;
FeatureType roadType = postgis.getFeatureType( "roads" );
// reader 1 streams over all roads
FeatureReader reader1 = postgis.getFeatureReader( roadsType, all, Transaction.AUTO_COMMIT );
// allRoads = featureResults is a prepaired query of all roads
FeatureSource roads = postgis.getFeatureSource( "roads" );
FeatureResults allRoads = roads.getFeatures( all );
// reader 2 & 3 streams over all roads in the same manner as reader 1
FeatureReader reader2 = allRoads.reader();
FeatureReader reader3 = allRoads.reader();
// bounds1 returns the bounding box of roads, may be null depending on expense
Envelope bounds1 = roads.getBounds( all );
// bounds2 returns the bounding box of roads, may actually calculate by going over the entire dataset
Envelope bounds 2 = allRoads.getBounds();
-
ClassDescriptionThe low-level attribute reading API.- Added hasNext to support the FeatureWriter API. - Changed order of writer parameters to match Collections, JDBC API. - Added IOExceptions on all methods. - Do we want AttributeWriters to know about the schema and perform validation??Provide batch notification on Commit / Rollback.An iterator backed by some resource that needs closing when done using itThis is the top-level interface for access to
FeatureData
.Constructs a live DataAccess from a set of connection parameters.Data class used to capture Parameter requirements.Enable programs to find all available DataAccess implementations, including the DataStore ones.Thrown when there is an error in a datasource.This represents a physical source of feature data, such as a shapefiles or database, where the features will be instances ofSimpleFeature
.Factory used to construct a DataStore from a set of parameters.Enable programs to find all available datastore implementations.Interface for wrapping feature readers which delegate to another feature reader.Interface for wrapping feature writers which delegate to another feature writer.Represents all events triggered by DataStore instances (typically change events).Interface to be implemented by all listeners of FeatureEvents.Used in conjuction withFeatureLocking
to lock features during a transaction.Indicates a lock contention, and attempt was made to modify or aquire with out Authroization.Provides Feature based locking.Idea for a response from a high-level lock( Query ) function.The low-level interface for reading Features.This class provides a high-level API for operations on feature data.This interface extendsFeatureSource
, adding methods to add and remove features and to modify existing features.Provides the ability to write Features information.FeatureReader<SimpleFeatureType, SimpleFeature> customized for FeatureID handling.DataStore represents a single file of content.DataAccessFactory for working with formats based on a single URL.Most of this code was copied from DataStoreFinder.AFileGroupProvider.FileGroup
provider allowing to return aCloseableIterator
ofFileGroupProvider.FileGroup
s.A Group of Files consisting of a reference to a mainFile, plus a set of support Files (if any) and metadata map.ExtendsResourceInfo
with information about the file structure of the resourceExtendsServiceInfo
with information about the underlying file structureA delegate that finds the files managed by the directory store andA delegate that indicates which files can be managed by the delegate store, when setting up a DirectoryDataStoreRepresents the joining of two feature types within aQuery
.type of joinThis class describes a featureID based locking service.Parameter<T>A Parameter defines information about a valid process parameter.Encapsulates a request for data, typically as:Describes the query capabilities for a specific FeatureType, so client code can request which features are natively supported by a FeatureSource.An adapter interface allowing a hosting application to advertise DataStore instances to GeoTools.This interface defines methods to convey information about some resource such as title, keywords, description and spatial parameters.Information about a service.Used to lock feature content to protect against other threads (or depending on the source of data other applications) making modifications when you are not looking.FeatureReader for SimpleFeature content.FeatureSource explicitly working with SimpleFeatureCollection.FeatureWriter for updating SimpleFeature content.The controller for Transaction with FeatureStore.DataStore implementations can use this interface to externalize the state they require to implement Transaction Support.