Skip to main content
Solved

PointOnPointOverlayer - Attribute Accumulation ?

  • November 29, 2016
  • 4 replies
  • 17 views
lifalin2016
Contributor
Forum|alt.badge.img+29

Hi,

I'm using PointOnPointOverlayer to match a set of anonymous points to a set of named points, wanting to transfer the "point name" of the latter to the former when they have identical coordinates.

However, I'm curious about the "Attribute Accumulation" setting, which doesn't make much sense to me.

Both sets of points are routed into the transformer via a single port, but the transformer nonetheless talks about "Original" and "Incoming" as if there is a requestor port and a supplier port (as in multiple other transformers).

I assume that the PointOnPointOverlayer makes a "full join" between all point features. Is this so ?

What should I expect from "Use Original" vs "Use Incoming" when I've chosen "Merge Incoming" as my mode ?

Cheers

Lars I.

Best answer by redgeographics

It seems that (probably per matching pair/group) the first feature coming in is deemed to be the "original" and all subsequent ones are "incoming". You can control the order of the readers in your workspace to influence this but if you do a lot of pre-processing before the overlay the order of the features may be affected.

A potential workaround in case you want more control:

If you grab the geometry of the points (maybe do an AnchoredSnapper first to make sure they match) and use that as a matching attribute in a FeatureMerger you have more control over what comes in and what goes out.

Hope this helps.

 

View original
-- Cheers, Lars I.
Did this help you find an answer to your question?

4 replies

lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • November 29, 2016
2016-11-29-13-07-32-vm-fme-forbindelse-til-fjernsk.png

 

Screendump of the transformer setting.

 

Using 2016.1

 

-- Cheers, Lars I.
lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • November 29, 2016
The same issue is with PointOnLineOverlayer, with the twist of having two inputs named "Point" and "Line", but an Attribute Accumulation that instead talks about "Original" and "Incoming".

 

 

From a little testing it seems that Point = Original and Line = Incoming (which btw is contrary to my expectation, as the transformer cuts lines), but the nomenclature makes little sense in any case.

 

-- Cheers, Lars I.
redgeographics
Celebrity
Forum|alt.badge.img+49
  • redgeographicsCelebrity
  • Celebrity
  • Best Answer
  • November 29, 2016

It seems that (probably per matching pair/group) the first feature coming in is deemed to be the "original" and all subsequent ones are "incoming". You can control the order of the readers in your workspace to influence this but if you do a lot of pre-processing before the overlay the order of the features may be affected.

A potential workaround in case you want more control:

If you grab the geometry of the points (maybe do an AnchoredSnapper first to make sure they match) and use that as a matching attribute in a FeatureMerger you have more control over what comes in and what goes out.

Hope this helps.

 

lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • November 29, 2016
Ok, I reread the docs for PointOnLineOverlayer. I was focused solely on the "Line" output, although it also has a "Point" output. "Original" is of course points when Point, and lines when Line.

 

-- Cheers, Lars I.

Reply


Helpful Members This Week

Community Stats

31,209
Posts
118,326
Replies
38,811
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.