I am not sure I understand, A little greater than the data bounding box - can you provide more information? How does it behave if you zoom out further still?
The DB2 code should get a filter and be able to do whatever processing it needs to in order to make a useful query. Many datastore use a visitor to go over the filter expression and "guess" a bounding box from the BBOX and Geometry Spatial Filters the filter contains. -- Jody Garnett On Sat, 30 May 2020 at 05:00, David Adler <dwa12...@gmail.com> wrote: > When using the GeoTools tutorial sample to display a map, modified for > DB2, the query generated creates a filter a little greater than the data > bounding box. This is time-consuming to process, checking if each > feature is within the query area where a straight table-scan of all the > data would be much much faster. When the DB2 filter code gets control, > it doesn't have access to the data bounding box in order to change the > behavior, as far as I can tell. > > Is this behavior expected? > > > -- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
