Skip to main content
Question

AreaOnAreaOverlayer - merge attributes without actually merging the shapefiles

  • February 19, 2013
  • 8 replies
  • 88 views

robertr
Contributor
Forum|alt.badge.img+6

Hello,

I would like to make a spatial join between two areas. The expected result is to bring the attributtes from one, to the other, based on overlaps (the spatial join). 

Currently, I managed to do that, but the output shapefile is a combination between the two input files. I would like the output to have the same geometry as one of the input files, not both. 

To create a point shapefile from the supplier would mean that many requestors will not receive data because large areas that overlap them will end up as a centroid for each large area..

Can anyone help me out with this? 

Thank you all,

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.

8 replies

dustin
Influencer
Forum|alt.badge.img+36
  • Influencer
  • February 19, 2013
Try the SpatialRelator.  I believe this is what you need.

robertr
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • February 19, 2013

Thank you Cartoscro,

I was already trying it but in some places it does not work properly although the two sets of data overlap. The end result is empty. I will play around with the options in the SpatialRelator transformer


dustin
Influencer
Forum|alt.badge.img+36
  • Influencer
  • February 19, 2013
When I use the SpatialRelator for areas like you are describing, I will choose both the overlaps and intersects options.  I've had the same experience with it recognizing some relationship, and not others.  It seems to be more reliable when I choose both.

fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • February 19, 2013
Hi,

 

Depending on your geometry type the areaonarea or lineonarea transformers might also be of use. Naturally the spatialrelator also can do the job, its all about how to treat the geometric overlay result toward your desired result, aka dealing with the lists created.

 

Hope this helps.

  • February 20, 2013
AreaOnAreaOverlayer splits all areas where they intersect. Is that your problem? In that case SpatialRelator is definitely the better choice. Concerning what Cartoscro mentioned I agree, you can spend hours with the descriptions but it is sometimes easier to simply try what will happen setting some of the relationships. Maybe you should also use "touches"?

 

Submit

 

Kind regards,

 

Wolfgang

fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • February 20, 2013
I usually end up here to define the kind of test to use in the spatialrelator.

fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • February 20, 2013
correction:

 

See Spatial Relations Defined for more information on spatial predicates and an illustration of spatial relationships.

gio
Contributor
Forum|alt.badge.img+15
  • Contributor
  • September 24, 2013
U can use different spatial transformers to do that.

 

 

Using AoA is no problem.

 

If u want to keep only one featureset, just expose the featuretype attributes on the input files.

 

After the AoA u can test on this featuretype where they overlap (overlaps >1)

 

That way u can separate your inputfile after the AoA.

 

 

For complex relations it is often desirable to set up spatialrelations on your features.

 

AoA or an intersector=>SpatialRelator=> testers and or calculators.

 

Spatialrelator is very powerfull but can be complex.

 

Try getting your head around a custom Spatialpredicate using D9im..

 

Also you can calculate cardinality, wich is of great use often.

 

Pass criteria can be tested.