- All Known Subinterfaces:
@XmlElement("Filter") public interface FilterDefines a constraint that can be checked against an instance of an object (Usually a Feature).
This is an abstract super type of the Filters defined by the Filter specification; you are not free to define your own filters. For extensibility please explore the definition of your own
Often a filter is used to to define a set feature instances that are to be operated upon. The operating set can be comprised of one or more enumerated features or a set of features defined by specifying spatial and non-spatial constraints on the geometric and scalar properties of a feature type.
Roughly speaking, a filter encodes the information present in the
WHEREclause of a SQL statement. There are various subclasses of this class that implement many types of filters, such as simple property comparisons or spatial queries.
The second use of Filter focuses on expressing constraints (or Facets). This use places restrictions on the allowable and is captured as part of schema information FeatureType. This is similar to the XML concept of "facets".
- GeoAPI 2.0
All Methods Instance Methods Abstract Methods Modifier and Type Method Description
accept(FilterVisitor visitor, Object extraData)Accepts a visitor.
evaluate(Object object)Give an object, this method determines if the test(s) represented by this filter object are passed.
static final IncludeFilter INCLUDEPlaceholder Filter that evaulates to
true. Filtering a set with
Filter.INCLUDEresults in the origional set.
static final ExcludeFilter EXCLUDEPlaceholder Filter that evaulates to
false. Filtering a set with
Filter.EXCLUDEresults in the empty Set.
boolean evaluate(Object object)Give an object, this method determines if the test(s) represented by this filter object are passed. This ability is used to allow Queries against both Features and and non spatial data (such as Record) and to express constraints on permissable data values.
trueif the test(s) are passed for the provided object