Hi @hear_it_here, sounds strange. Is the number of points (200000) counted at the output port of the PointOnAreaOverlayer? Or is it counted after processing by some other transformers?
Hi @hear_it_here, sounds strange. Is the number of points (200000) counted at the output port of the PointOnAreaOverlayer? Or is it counted after processing by some other transformers?
These duplicates are coming right out of the point output port.
Just as an experiment, try running the points through a Deaggregator before the PointOnAreaOverlayer. It sounds as though you might have aggregate points ("multipoints" in Esri language) in your dataset at the same geographical location - I think aggregate features are automatically deaggregated by the Overlayer transformers in case some parts of the feature overlay and others don't.
If this is the problem, you can fix it by putting a Counter before the Point input to generate a unique ID, and then adding an Aggregator after the PointOnAreaOverlayer using the unique ID as the Group By. Or, since you're getting duplicate locations, a Matcher might be more useful here.
Just as an experiment, try running the points through a Deaggregator before the PointOnAreaOverlayer. It sounds as though you might have aggregate points ("multipoints" in Esri language) in your dataset at the same geographical location - I think aggregate features are automatically deaggregated by the Overlayer transformers in case some parts of the feature overlay and others don't.
If this is the problem, you can fix it by putting a Counter before the Point input to generate a unique ID, and then adding an Aggregator after the PointOnAreaOverlayer using the unique ID as the Group By. Or, since you're getting duplicate locations, a Matcher might be more useful here.
I agree, most likely suspect is that there were aggregate points going in. They do get deaggregated. If not, please be in touch with support@safe.com
See an example of this in:
testmultipointinoverlay.fmw (run with full inspection to see the results)
