Skip to main content
  • EN

I have three polygon shapefiles, they all contain a column called GUID, this column is unique, the shapefiles often overlap.

 

I also have a point shapefile, these points will generally fall within 1 or Many polygons.

 

I am trying to end up with a table similar to the one shown in my sketch.

 

Each point feature should have one or more GUID in it... I am sure there is a simple process to do this in FME, currently I have an overly complex looking scenario that isn't working, I am really over thinking this one.

 

example 

In my most basic theory this is how I was setting out to achieve what I want, but I don't think it is an efficient starting point...

 

image.png

You can do it with only one PoineOnAreaOverlayer. First, rename the three GUID attributes to have different names (eg pave_guid, seal_guid, segm_guid), then have the attribute accumulation on the PoineOnAreaOverlayer set to 'Merge Attributes'. That means that all attributes from area features will merge onto the points they overlap. There won't be any conflict between merging the guid attributes because they have unique names now.

If there is a chance a point will overlap two areas from the same layer, then you'll need to generate a list output on the points, and then decide from there how you want to represent that situation in your desired output.

You can do it with only one PoineOnAreaOverlayer. First, rename the three GUID attributes to have different names (eg pave_guid, seal_guid, segm_guid), then have the attribute accumulation on the PoineOnAreaOverlayer set to 'Merge Attributes'. That means that all attributes from area features will merge onto the points they overlap. There won't be any conflict between merging the guid attributes because they have unique names now.

If there is a chance a point will overlap two areas from the same layer, then you'll need to generate a list output on the points, and then decide from there how you want to represent that situation in your desired output.

Thank you, I will give that a go!

There are no overlapping features within the same layer, so the list should not be required.

Thanks again for the tip.

Reply


Community Stats

30,001
Posts
113,962
Replies
37,623
Members
Terms & ConditionsCookie settings