Hi guys,
I am trying to use point overlay to get a point count over polygons, but everytime the Point Area Overlay transformer seems explode the multi-parts polygons. Is there anyway i can avoid this?
Thanks!
Solved
Points on Area Overlay: count points on multipart features
+5- Contributor
- 22 replies
Best answer by gio
@sangli
You can also use a spatialrelator for this. The geometry will not be exploded.
If you have points as supplier (test = contains), you can us a listelementcounter to count the elements in the list.
If you have points as requestor (test = Within), you can use a Statistics calculator grouped by the area id to count the points within.
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.
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.
- 7843 replies
Hi @sangli, currently there is no way to prevent exploding (de-aggregating) input multi-part areas, unfortunately. A possible workaround is: use the Aggregator to aggregate the output areas.
- Group By: <set unique ID attribute of original areas>
- Attributes to Sum: <set the Overlap Count Attribute specified in the PoinOnAreaOverlayer>
If the original area features don't have unique ID attribute, you can use a Counter to add sequential number to the features as temporary ID before inputting them to the PointOnAreaOverlayer.
+15- Contributor
- 2252 replies
- Best Answer
@sangli
You can also use a spatialrelator for this. The geometry will not be exploded.
If you have points as supplier (test = contains), you can us a listelementcounter to count the elements in the list.
If you have points as requestor (test = Within), you can use a Statistics calculator grouped by the area id to count the points within.
+5- Contributor
- 22 replies
Hi @sangli, currently there is no way to prevent exploding (de-aggregating) input multi-part areas, unfortunately. A possible workaround is: use the Aggregator to aggregate the output areas.
- Group By: <set unique ID attribute of original areas>
- Attributes to Sum: <set the Overlap Count Attribute specified in the PoinOnAreaOverlayer>
If the original area features don't have unique ID attribute, you can use a Counter to add sequential number to the features as temporary ID before inputting them to the PointOnAreaOverlayer.