public class WFSContentComplexFeatureSource extends Object implements FeatureSource<FeatureType,Feature>
| Constructor and Description |
|---|
WFSContentComplexFeatureSource(Name typeName,
WFSClient client,
WFSContentDataAccess dataAccess)
Initialises a new instance of the class WFSContentComplexFeatureSource.
|
| Modifier and Type | Method and Description |
|---|---|
void |
addFeatureListener(FeatureListener listener)
Registers a listening object that will be notified of changes to this
FeatureSource. |
ReferencedEnvelope |
getBounds()
Get the spatial bounds of the feature data.
|
ReferencedEnvelope |
getBounds(Query query)
Get the spatial bounds of the features that would be returned by the given
Query. |
int |
getCount(Query query)
Gets the number of the features that would be returned by the given
Query, taking into account any settings for max features and
start index set on the Query. |
DataAccess<FeatureType,Feature> |
getDataStore()
Returns the data source, as a
DataAccess object, providing this FeatureSource. |
FeatureCollection<FeatureType,Feature> |
getFeatures()
Get features using the default Query.ALL.
|
FeatureCollection<FeatureType,Feature> |
getFeatures(Filter filter)
Get features based on the specified filter.
|
FeatureCollection<FeatureType,Feature> |
getFeatures(Query query)
Get features based on the query specified.
|
ResourceInfo |
getInfo()
Returns information describing this
FeatureSource which may include title,
description and spatial parameters. |
Name |
getName()
Returns the name of the features (strictly, the name of the
AttributeDescriptor for
the features) accessible through this FeatureSource. |
QueryCapabilities |
getQueryCapabilities()
Enquire what what query capabilities this
FeatureSource natively supports. |
FeatureType |
getSchema()
Retrieves the schema (feature type) that will apply to features retrieved from this
FeatureSource. |
Set<RenderingHints.Key> |
getSupportedHints()
Returns the set of hints that this
FeatureSource supports via Query requests. |
void |
removeFeatureListener(FeatureListener listener)
Removes an object from this
FeatureSource's listeners. |
public WFSContentComplexFeatureSource(Name typeName, WFSClient client, WFSContentDataAccess dataAccess)
typeName - The name of the feature you want to retrieve.client - The WFSClient responsible for making the WFS requests.dataAccess - The data access object.public FeatureCollection<FeatureType,Feature> getFeatures(Filter filter) throws IOException
getFeatures in interface FeatureSource<FeatureType,Feature>filter - the filter to select features; must not be null (use Filter.INCLUDE instead)FilterIOException - if the underlying data source cannot be accessed.Filterpublic FeatureCollection<FeatureType,Feature> getFeatures() throws IOException
getFeatures in interface FeatureSource<FeatureType,Feature>QueryIOException - if the underlying data source cannot be accessed.public FeatureCollection<FeatureType,Feature> getFeatures(Query query) throws IOException
getFeatures in interface FeatureSource<FeatureType,Feature>query - DataAccess query for requested information, such as typeName, maxFeatures and
filter.QueryIOException - if the underlying data source cannot be accessed.Querypublic Name getName()
FeatureSourceAttributeDescriptor for
the features) accessible through this FeatureSource.
The value returned by this method can be different to that returned by featureSource.getSchema().getType().getName(). This is because there is a distinction
between the name applied to features and the name of a feature type. When working with SimpleFeature and SimpleFeatureType, for example with a shapefile data source, it is
common practice for feature and feature type names to be the same. However, this is not the
case more generally. For instance, a database can contain two tables with the same structure.
The feature name will refer to the table while the feature type name refers to the schema
(table structure).
getName in interface FeatureSource<FeatureType,Feature>FeatureSourcepublic ResourceInfo getInfo()
FeatureSourceFeatureSource which may include title,
description and spatial parameters. Note that in the returned ResourceInfo object,
the distinction between feature name and schema (feature type) name applies as discussed for
FeatureSource.getName().getInfo in interface FeatureSource<FeatureType,Feature>public DataAccess<FeatureType,Feature> getDataStore()
FeatureSourceDataAccess object, providing this FeatureSource.getDataStore in interface FeatureSource<FeatureType,Feature>FeatureSourcepublic QueryCapabilities getQueryCapabilities()
FeatureSourceFeatureSource natively supports. For
example, whether queries can return sorted results.getQueryCapabilities in interface FeatureSource<FeatureType,Feature>FeatureSourcepublic void addFeatureListener(FeatureListener listener)
FeatureSourceFeatureSource.addFeatureListener in interface FeatureSource<FeatureType,Feature>listener - the new listenerpublic void removeFeatureListener(FeatureListener listener)
FeatureSourceFeatureSource's listeners.removeFeatureListener in interface FeatureSource<FeatureType,Feature>listener - the listener to removepublic FeatureType getSchema()
FeatureSourceFeatureSource.
For a homogeneous data source such as a shapefile or a database table, this schema be that of all features. For a heterogeneous data source, e.g. a GML document, the schema returned is the lowest common denominator across all features.
getSchema in interface FeatureSource<FeatureType,Feature>FeatureSourcepublic ReferencedEnvelope getBounds() throws IOException
FeatureSource
getBounds(Query.ALL).
It is possible that this method will return null if the calculation of bounds is judged to
be too costly by the implementing class. In this case, you might call
getFeatures().getBounds() instead.
getBounds in interface FeatureSource<FeatureType,Feature>null if the bounds are unknown
or too costly to calculate.IOException - on any errors calculating the boundspublic ReferencedEnvelope getBounds(Query query) throws IOException
FeatureSourceQuery.
It is possible that this method will return null if the calculation of bounds is judged to
be too costly by the implementing class. In this case, you might call
getFeatures(query).getBounds() instead.
getBounds in interface FeatureSource<FeatureType,Feature>query - the query to select featuresnull if the bounds are unknown
or too costly to calculate.IOException - on any errors calculating the boundspublic int getCount(Query query) throws IOException
FeatureSourceQuery, taking into account any settings for max features and
start index set on the Query.
It is possible that this method will return -1 if the calculation
of number of features is judged to be too costly by the implementing class.
In this case, you might call getFeatures(query).size()
instead.
Example use:
int count = featureSource.getCount();
if( count == -1 ){
count = featureSource.getFeatures( "typeName", count ).size();
}getCount in interface FeatureSource<FeatureType,Feature>query - the query to select featuresQuery;
or -1 if this cannot be calculated.IOException - if there are errors getting the countpublic Set<RenderingHints.Key> getSupportedHints()
FeatureSourceFeatureSource supports via Query requests.
Note: the existence of a specific hint does not guarantee that it will always be honored by the implementing class.
getSupportedHints in interface FeatureSource<FeatureType,Feature>RenderingHints#Key objects; may be empty but never nullHints.FEATURE_DETACHED,
Hints.JTS_GEOMETRY_FACTORY,
Hints.JTS_COORDINATE_SEQUENCE_FACTORY,
Hints.JTS_PRECISION_MODEL,
Hints.JTS_SRID,
Hints.GEOMETRY_DISTANCE,
Hints.FEATURE_2DCopyright © 1996–2019 Geotools. All rights reserved.