Skip to main content
Solved

Overlap issue

  • January 13, 2022
  • 6 replies
  • 8 views

Forum|alt.badge.img

Hello everyone,

So I have two data set (Set A & Set B). I want to find how many B polygons are overlapped on A.

 

I am able to find the overlapped polygon attribute by using spatial relator (by explode the list).

 

However, the geometry of the exposed list is not correct. They all have the same geometry (from the test filter transformer).

 

Is there anyway that I can have both correct attribute and geometry?

 

Thank you for your help.

Best answer by takashi

Hi @zacharylee1204​ , the SpatialRelator outputs the input Requestor features containing attributes/lists collected from spatially related Supplier features, so the ListExploder gives an identical geometry to every output features exploded from the same list.

If you need to transfer geometries of the related Supplier features to the resulting features, consider using the pair of GeometryExtractor and GeometryReplacer.

(1) Save the geometry of Supplier as its attribute with the GeometryExtractor, before the SpatialRelator.

(2) In the SpatialRelator, accumulate the geometry attributes from related Suppliers into the list.

(3) Restore the geometry with the GeometryReplacer, after the ListExploder.

In this case, "FME Binary" is the best geometry encoding type for the GeometryExtractor/Replacer.

Hope this helps.

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.

6 replies

redgeographics
Celebrity
Forum|alt.badge.img+59
  • Celebrity
  • 3699 replies
  • January 13, 2022

Can you also show what your two input datasets look like?

 


Forum|alt.badge.img
  • Author
  • 53 replies
  • January 13, 2022

So basically I use the buildingcs for the linkage. At the end, the list exploder shows the correct numbers of overlapped polygon (in attribute). However, they all show the same geometry polygon.


Forum|alt.badge.img
  • Author
  • 53 replies
  • January 13, 2022

So basically I use the buildingcs for the linkage. At the end, the list exploder shows the correct numbers of overlapped polygon (in attribute). However, they all show the same geometry polygon.

No idea why all show the same geometry


takashi
Celebrity
  • 7842 replies
  • Best Answer
  • January 13, 2022

Hi @zacharylee1204​ , the SpatialRelator outputs the input Requestor features containing attributes/lists collected from spatially related Supplier features, so the ListExploder gives an identical geometry to every output features exploded from the same list.

If you need to transfer geometries of the related Supplier features to the resulting features, consider using the pair of GeometryExtractor and GeometryReplacer.

(1) Save the geometry of Supplier as its attribute with the GeometryExtractor, before the SpatialRelator.

(2) In the SpatialRelator, accumulate the geometry attributes from related Suppliers into the list.

(3) Restore the geometry with the GeometryReplacer, after the ListExploder.

In this case, "FME Binary" is the best geometry encoding type for the GeometryExtractor/Replacer.

Hope this helps.


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3422 replies
  • January 13, 2022

No idea why all show the same geometry

If you are wanting your output to contain the supplier geometry rather than the requestor, i would use a GeometryExtractor prior to the SpatialRelator on your suppliers, include that in the list and then you can use a GeometryReplacer to rebuild the supplier geometries.

 

 


Forum|alt.badge.img
  • Author
  • 53 replies
  • January 14, 2022

Thank you all, it works! :)