Skip to main content
Archived

PointCloudCoercer: Add an option not to convert color components to "fme_color"

Related products:Transformers
  • September 5, 2018
  • 0 replies
  • 20 views

takashi
Celebrity

***Note from Migration:***

Original Title was: PointCloudCoercer: Add an option not to convert color components to "fme_color" automatically


The PointCloudCoercer (Output Geometry: Individual Points) automatically converts color components - color_red, color_green, and color_blue to "fme_color", if you have set parameters to preserve the color components as attributes.

In some cases it might be convenient, but I found that it would just make worse the performance if you want to extract the color components individually. In my case, the workspace has to save every point including components into a MongoDB collection.

Firstly, I split "fme_color" generated by the PointCloudCoercer into three parts and restored original values, then wrote the points into DB. It took a long time.

Next, I renamed the color components with the PointCloudComponentRenamer beforehand not to generate undesired "fme_color". Result, writing speed with the second method was faster than the first method, 2+ times.

It would be better if the PointCloudCoercer would have an option to extract color components as is, without converting them to "fme_color" automatically.

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.