In other words, there needs to be one FLOOR_ID with it's respective POINT and LINESTRING per row. Please see the screenshot below. Thanks
Solved
How do you arrange the output of this transformer so a POINT Z and LINESTRING Z are on the same feature (row) per their respective FLOOR_ID?
+12- Contributor
Best answer by takashi
Hi @larue , if you intend to aggregate each pair of two rows having common FLOOR_ID so that the resulting row will have two geometry attributes (POINT and LINESTRING), this workflow is a possible way.
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.
- Best Answer
Hi @larue , if you intend to aggregate each pair of two rows having common FLOOR_ID so that the resulting row will have two geometry attributes (POINT and LINESTRING), this workflow is a possible way.
+12- Contributor
Hi @larue , if you intend to aggregate each pair of two rows having common FLOOR_ID so that the resulting row will have two geometry attributes (POINT and LINESTRING), this workflow is a possible way.
Hi @Takashi Iijima ,
Once again, you get me out of a jam! I was doing exactly this configuration, but what tripped me up was not setting "Across Output Ports" in the Attribute Filter.
I have been trying to master this type of manipulation, but am not sure what you call it in a search. Is this...Attribute manipulation? Feature wrangling? It does not seem to be related to Lists, which is what you would call it in Dynamo. Are there tutorials out there?
Many thanks,
Loren