It does split the filter but issue is with where the feature is
constructed.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
On Tue, May 21, 2013 at 6:23 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
[Moved from the user list]
This is where the arcsde module suffers from not being one of the jdbc
modules, where this problem is solved be keeping two feature types: the
one used for handling the query
If you extract from arcSDE with a spatial filter, (BBOX,POLYGON) then it
is filtered twice. The query to arcSDE has the spatial constraint so the
correct no. of records is returned. However, in
FilteringFeatureReader.hasNext() we have: while
(featureReader.hasNext()) { peek =
[Moved from the user list]
This is where the arcsde module suffers from not being one of the jdbc
modules, where this problem is solved be keeping two feature types: the
one used for handling the query and the one to be returned. Have a look
in gt-jdbc
