Skip to main content
  • EN

Is there a way to get AreaBuilder to produce results closer to Pro's geoprocessing? It seems that whenever I give FME lines similar to the example below, it builds one polygon and calls it a day unless I specify an absurdly high snapping tolerance, in which case it produces garbage (e. g. a 1m tolerance would create a small extra triangle in the middle of the northern line where the small /\\ is, but still leave the large area empty; 5m would create a large jaggy polygon. The example is roughly 100m across, btw.). The polygon parameters have no effect, neither do the snapping types. The lines are 2D, I've also included a 2DForcer before the AreaBuilder to make 100% sure it doesn't even get Z coordinates, but to no effect.

​

Pro, with all of the line vertices displayed and filled areas (three separate polygons, as expected):

pro_area_verticesFME, with one polygon ☹️

fme_area

When I have situations like this, I normally run the lines through an Intersector first, and get better results.

When I have situations like this, I normally run the lines through an Intersector first, and get better results.

Intersector unfortunately didn't help, but I got it to work applying the idea using a chopper to extract all vertices, then using a PointOnLineOverlayer with 0.01 tolerance, then the AreaBuilder with Endpoint snapping tolerance at 0.01 as well.

 

fme_area_v02

Reply


Community Stats

30,186
Posts
114,572
Replies
37,849
Members
Terms & ConditionsCookie 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.