The 3DForcer should work, but have you looked at the actual output value from the StatisticsCalculator? Does it have a value or is it empty?

@david_r I forgot to mention that I get the minimum value from the staticscalculator from point data. This minimum value describes at which height the polygons should be.

ps: I do get a value in the staticscalculator.

Can you post a workflow? How are you joining the output from the statistics calculator to the polygon data?

At this moment i'm trying to join the different columns so I can set the value to the elevation parameter. I don't know if this a good approach or not. Tips are always welcome.

Hi @andreasb! I might be over simplifying this, but "...I have to replace this elevation attribute value..." caught my attention. Sounds like you are trying to replace an existing elevation attribute in your polygon data. If so, after you get the minimum elevation from the point data using the StatisticsCalculator, try:

• merging the attributes from the points to the polygon dataset (i.e. FeatureMerger, FeatureJoiner, SpatialRelator).
• You can replace the existing elevation attribute with the minimum elevation value you generated with the StatisticsCalculator using an AttributeManager.

I would use the FeatureMerger rather than the Joiner in this case, because you can use a fixed value as the key. So place a FeatureMerger. The Area features are the Requestor. Point Features StatisticsCalculator:Summary is the supplier. Set the join keys to a fixed value (like set both of them to the letter A or number 1). That should pass the point stats values on to the area features, after which the 3DForcer should be fine.