Package org.geotools.api.filter

Interface FilterVisitor

All Known Implementing Classes:
AbstractFilterToMongo, AbstractFilterVisitor, AbstractFinderFilterVisitor, AbstractSearchFilterVisitor, BBOXExpandingFilterVisitor, BindingFilterVisitor, CapabilitiesFilterSplitter, CollectionFeatureMemberFilterVisitor, ComplexFilterSplitter, DB2FilterToSQL, DefaultCRSFilterVisitor, DefaultFilterVisitor, DuckDBFilterToSQL, DuplicatingFilterVisitor, ExtractBoundsFilterVisitor, FilterAttributeExtractor, FilterCompliancePreProcessor, FilterEncodingPreProcessor, FilterToCQL2Json, FilterToMongo, FilterToSQL, FilterTransformer.FilterTranslator, FilterVisitorSupport, FixBBOXFilterVisitor, GeometryDefaulter, GeometryTransformationVisitor, GeoParquetFilterToSQL, GeoPkgFilterToSQL, H2FilterToSQL, H2GISFilterToSQL, H2GISPSFilterToSql, HanaFilterToSQL, IdCollectorFilterVisitor, IdFinderFilterVisitor, IndexCombinedFilterTransformerVisitor, IndexedFilterDetectorVisitor, IndexUnmappingVisitor, InformixFilterToSQL, InvertAxisFilterVisitor, IsFullySupportedFilterVisitor, IsSupportedFilterVisitor, JdbcMultipleValueEncoder, JoinInfo.JoinQualifier, JsonPointerFilterSplittingVisitor, LiteralDemultiplyingFilterVisitor, MetaBufferEstimator, MongoFilterSplitter, MultipleValueExtractor, MySQLFilterToSQL, NamespaceAwareAttributeRenameVisitor, NestedFilterToSQL, NullFilterVisitor, OperatorNameFilterVisitor, OracleFilterToSQL, PostgisFilterToSQL, PostgisPSFilterToSql, PostPreProcessFilterSplittingVisitor, PreparedFilterToSQL, PropertyNameResolvingVisitor, ReprojectingFilterVisitor, SchemaIndexedFilterDetectorVisitor, SimplifyingFilterVisitor, SingleStoreFilterToSQL, SingleStoreLargeGeometryPreProcessor, SpatialFilterVisitor, SQLServerFilterToSQL, StyleAttributeExtractor, StyleAttributeExtractorTruncated, TemporalFilterVisitor, TeradataFilterToSQL, TimeRangeVisitor, UnmappingFilterVisitor, Utils.BBOXFilterExtractor, VectorMosaicPostPreFilterSplitter
public interface FilterVisitor
Visitor with visit methods to be called by Filter.accept(...).

Consider: It is unclear if this visitor should be applied directly to Filter, or should be walked accross the data structure by hand. The standard complient structure is well defined, and this should negate the need for a formal visitor (we don't have internal structure we are hiding).

There is still a very valid use for FilterVisitor, a instance may implement both FilterVisitor and ExpressionVisitor and ExpressionVisitory in one direction, and a FilterVisitor and a StyleVisitor in the other. The ability to directly focus on transforming data within a larger structure is something a normal data walk can not accomplish in a scalable manner.

Since:
GeoAPI 2.0
Author:
Chris Dillard (SYS Technologies)