Skip to main content
Solved

"Spatial cross/outer join" ?

  • November 2, 2016
  • 2 replies
  • 50 views
lifalin2016
Supporter
Forum|alt.badge.img+39

Hi,

I have two data sources with polygons. I need to match every single polygon from first dataset to every single polygon in second dataset. Output should be any pair that have their two polygons intersect.

I've tried to utilize SpatialFilter, but that doesn't do what I want. It only matche some polygons to each other.

I've had a look at SpatialRelator, but it still has assymetric inputs (Requestor, Supplier), so I think it'll work as SpatialFilter. Besides it requires some attribute condition which I can't meet.

What is the best way to make this M-by-N "spatial cross/outer join" ?

Cheers

 

Lars I.

Best answer by takashi

Hi @lifalin2016, I think the SpatialRelator is what you are looking for. Have a look at the list attribute called "_relationships" by default, which contains every attributes of all the Supplier features that are spatially related to the Requestor feature.

-- Cheers, Lars I.
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

takashi
Celebrity
  • takashiCelebrity
  • Best Answer
  • November 2, 2016

Hi @lifalin2016, I think the SpatialRelator is what you are looking for. Have a look at the list attribute called "_relationships" by default, which contains every attributes of all the Supplier features that are spatially related to the Requestor feature.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
lifalin2016
Supporter
Forum|alt.badge.img+39
  • lifalin2016Supporter
  • Author
  • Supporter
  • November 2, 2016

Thanks Takashi,

I did look into the SpatialRelator in the meantime, and ended up with a custom transformer like this:

So your suggestion was spot on :-)

My only issue is that I can't seem to get the list of relationship tests to work as a transformer published parameter (type Choice), so it's sofar hardcoded in the SpatialRelator in the custom transformer :-S

Cheers

 

Lars I

-- Cheers, Lars I.

Community Stats

32,154
Posts
122,047
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.