Skip to main content
Question

Duplicate features emitted from the FeatureReader when 'Intersects' SpatialFilter is used

  • October 30, 2020
  • 2 replies
  • 63 views

dms2
Contributor
Forum|alt.badge.img+11
  • Contributor
  • 48 replies

I have a large polygon SDE feature class (>3M features) from which I only need polygons intersecting a few Oracle polygon features.

I've connected the Oracle features to the SDE FeatureReader's Initiator port and I'm using them to filter SDE data with the 'Initiator Intersects Result' spatial filter.

I've realized it returns duplicates when there's an SDE feature intersecting more than one (non overlapping) Initiator feature. So if an SDE feature intersects 3 Initiator features I get 3 copies of the SDE feature.

This is not what I would expect.

My only option is to use a DuplicatFilter right after the FeatureReader but when reading thousands of features this will slow down my translation.

Has anyone come across this same problem?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

nielsgerrits
VIP
Forum|alt.badge.img+60
  • 2938 replies
  • October 30, 2020

Yes I have, and the DuplicateFilter on objectid is a simple solution. It will cost time, mostly loading and a bit processing.

A faster solution is to do the query in the database, using a SQLExecutor.


dms2
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • 48 replies
  • October 30, 2020

Yes I have, and the DuplicateFilter on objectid is a simple solution. It will cost time, mostly loading and a bit processing.

A faster solution is to do the query in the database, using a SQLExecutor.

I'll try using a SQLExecutor. Thanks!